EP2637412B1 - Appareil et procédé de réception d'un signal de diffusion numérique - Google Patents

Appareil et procédé de réception d'un signal de diffusion numérique Download PDF

Info

Publication number
EP2637412B1
EP2637412B1 EP11838174.8A EP11838174A EP2637412B1 EP 2637412 B1 EP2637412 B1 EP 2637412B1 EP 11838174 A EP11838174 A EP 11838174A EP 2637412 B1 EP2637412 B1 EP 2637412B1
Authority
EP
European Patent Office
Prior art keywords
video
view
camera
information
viewpoint
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.)
Active
Application number
EP11838174.8A
Other languages
German (de)
English (en)
Other versions
EP2637412A2 (fr
EP2637412A4 (fr
Inventor
Jongyeul Suh
Jeehyun Choe
Joonhui Lee
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.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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 LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP2637412A2 publication Critical patent/EP2637412A2/fr
Publication of EP2637412A4 publication Critical patent/EP2637412A4/fr
Application granted granted Critical
Publication of EP2637412B1 publication Critical patent/EP2637412B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N13/00—Stereoscopic video systems; Multi-view video systems; Details thereof
    • H04N13/10—Processing, recording or transmission of stereoscopic or multi-view image signals
    • H04N13/106—Processing image signals
    • H04N13/172—Processing image signals image signals comprising non-image signal components, e.g. headers or format information
    • H04N13/178—Metadata, e.g. disparity information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N13/00—Stereoscopic video systems; Multi-view video systems; Details thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N13/00—Stereoscopic video systems; Multi-view video systems; Details thereof
    • H04N13/10—Processing, recording or transmission of stereoscopic or multi-view image signals
    • H04N13/194—Transmission of image signals

Definitions

  • the present invention relates to a method of receiving a digital broadcasting signal including a 3D video and apparatus therefor, and more particularly, to a method of outputting a 3D video data in a screen by receiving the digital broadcasting signal including the 3D video having a plurality of viewpoints and apparatus therefor.
  • a 3 dimensional video provides a 3D effect using a principle of stereo vision of two eyes. Since a human feels perspective via parallax of two eyes, in other word, binocular parallax due to a space between two eyes apart from each other about 65 mm, the 3D video may provide the 3D effect and the perspective in a manner of providing a video, which makes a left eye and a right eye see a related plane video, respectively.
  • the 3D video display method includes a stereoscopic technique, a volumetric technique, a holographic technique, and the like.
  • the stereoscopic technique provides a left view image supposed to be watched by a left eye and a right view image supposed to be watched by a right eye.
  • the stereoscopic technique enables to recognize a 3D video effect in a manner of making the left eye and the right eye watch the left view image and the right view image respectively using a polarized glasses or a display device itself.
  • the aforementioned 3D video is a video considering a single viewpoint only. In order to provide a viewer with the 3D video capable of being watched from a plurality of viewpoints, it is further necessary to separately provide additional information as well as a plurality of 3D videos.
  • a viewing environment of the 3D multi-view display corresponds to a condition of which the multi-view was filmed, a viewer may be able to enjoy an intended 3D effect. Otherwise, distortion of a screen and inconvenience of watching may occur.
  • Document WO 2010/071283 A1 may be construed to disclose a digital broadcasting reception apparatus capable of displaying a stereoscopic image, comprising: a de-multiplexing unit for de-multiplexing a received digital broadcast signal; a PSIP or PSI/SI processor for extracting extended-view video information from the de-multiplexed digital broadcast signal; a decoder for decoding an extended-view video stream and a base-view video stream from the de-multiplexed digital broadcast signal; and an output formatting unit for formatting the extended-view video stream and the base-view video stream based on the extended-view video information.
  • the extended-view video information includes the information about at least one of: the relative positional relationship between a camera that has created the extended-view video stream and a camera that has created the base-view video stream, the number of the extended-view video streams, and the arrangement structure of the cameras.
  • the relative positional relationship indicates at least one of: the direction of the camera which has created the extended-view video stream with respect to the camera which has created the base-view video stream, and the distance between the two cameras.
  • Document US 2010/189173 A1 may be construed to disclose a method comprising encoding a first view component of a first view of a multi-view bitstream; and encoding a second view component of a second view; wherein the encoding of the second view component enables generating of a reference picture list for the second view component to include at least one of the following: (a) a first field view component based on the first view component or (b) a first complementary field view component pair including the first view component.
  • Document EP 2 544 447 A2 constitutes prior art under Article 54(3) EPC and may be construed to disclose a method of transmitting digital broadcasting content for providing 2D content or 3D content.
  • the method includes: encoding content including at least one from among the 2D content and the 3D content and generating an elementary stream including encoded data of the content; generating service additional information including electronic program guide (EPG) information of the digital broadcasting content and inserting at least one, into the service additional information, from among 2D/3D content identification information representing a method of reproducing the 2D content or the 3D content, 2D/3D content link information representing a relationship between the 2D content and the 3D content, and EPG 3D reproduction information for reproducing an EPG screen, on which EPG information is displayed, in 3D; and multiplexing the elementary stream and the service additional information and then generating a transport stream.
  • EPG electronic program guide
  • the present invention intends to solve the aforementioned problem.
  • a technical task that the present invention intends to achieve is to provide a method of receiving a digital broadcasting signal and apparatus therefor enabling to display a 3D video to watch the 3D video in a plurality of viewpoints in a manner of receiving a digital broadcasting signal including a 3D video of multi-view without experiencing the aforementioned problem.
  • a digital broadcasting signal receiving device includes a tuner configured to receive a digital broadcasting signal including a plurality of video streams implementing a multi-view 3D video and a signaling data, a signaling data processor configured to decode the digital broadcasting signal including an information table in which includes a multi-view 3D video information converting a video image of a plurality of the video streams into the multi-view 3D video, a decoder configured to decode a plurality of the video streams using the multi-view 3D video information, and a formatter configured to output video images of the decoded video streams as the multi-view 3D video.
  • the digital broadcasting signal receiving device further includes a multi-view output control unit configured to display the multi-view 3D video output in consideration of a relative position of each viewpoint.
  • a multi-view output control unit configured to display the multi-view 3D video output in consideration of a relative position of each viewpoint.
  • the multi-view 3D video information of the digital broadcasting signal receiving device includes at least one selected from the group consisting of the number of viewpoint, a camera arrangement method, priority of each viewpoint, a viewing angle provided by the multi-view 3D video, distance between cameras, or an identifier of a different camera forming a 3D video together according to each viewpoint.
  • the multi-view 3D video information of the digital broadcasting signal receiving device is included in the information table in a form of a descriptor.
  • the priority of each viewpoint of the digital broadcasting signal receiving device filters a part of a plurality of the video streams according to the priority if the number of viewpoint capable of being displayed in a receiver is less than the number of viewpoints included in the digital broadcasting signal.
  • a method of receiving a digital broadcasting signal includes the steps of receiving a digital broadcasting signal including a plurality of video streams implementing a multi-view 3D video and a signaling data, decoding the digital broadcasting signal including an information table in which includes a multi-view 3D video information converting a video image of a plurality of the video streams into the multi-view 3D video, decoding a plurality of the video streams using the multi-view 3D video information, and outputting video images of the decoded video streams as the multi-view 3D video.
  • the multi-view 3D video information of the digital broadcasting signal receiving device is included in the information table in a form of a descriptor.
  • the priority of each viewpoint of the digital broadcasting signal receiving device filters a part of a plurality of the video streams according to the priority if the number of viewpoint capable of being displayed in a receiver is less than the number of viewpoints included in the digital broadcasting signal.
  • a method of receiving a digital broadcasting signal includes the steps of receiving a digital broadcasting signal including a plurality of video streams implementing a multi-view 3D video and a signaling data, decoding the digital broadcasting signal including an information table in which includes a multi-view 3D video information converting a video image of a plurality of the video streams into the multi-view 3D video, decoding a plurality of the video streams using the multi-view 3D video information, and outputting video images of the decoded video streams as the multi-view 3D video
  • the method of receiving a digital broadcasting signal further includes the step of displaying the multi-view 3D video output in consideration of a relative position of each viewpoint.
  • the multi-view 3D video information of the method of receiving a digital broadcasting signal includes at least one selected from the group consisting of the number of viewpoint, a camera arrangement method, priority of each viewpoint, a viewing angle provided by the multi-view 3D video, distance between cameras, or an identifier of a different camera forming a 3D video together according to each viewpoint.
  • the multi-view 3D video information of the method of receiving a digital broadcasting signal is included in the information table in a form of a descriptor.
  • the priority of each viewpoint of the method of receiving a digital broadcasting signal filters a part of a plurality of the video streams according to the priority if the number of viewpoint capable of being displayed in a receiver is less than the number of viewpoints included in the digital broadcasting signal.
  • a method of receiving a digital broadcasting signal and apparatus therefor has an effect as follows.
  • a 3D video can be watched from a plurality of viewpoints in a digital broadcasting receiver.
  • a producer may be able to reproduce a 3D effect intended by the producer in case of displaying a 3D video signal of multi-view in a digital broadcasting receiver.
  • a user interface can be provided according to each viewpoint in case of displaying a 3D video signal of multi-view in a digital broadcasting receiver.
  • each output screen may be able to output a fixed 3D viewpoint in a manner of designating the fixed 3D viewpoint or may be able to display a 3D viewpoint of which a user wants in a manner of selecting in a multi-view display.
  • terminologies used in the present specification are selected from general terminologies used currently and widely in consideration of functions, they may be changed in accordance with intentions of technicians engaged in the corresponding fields, customs, advents of new technologies and the like. Occasionally, some terminologies may be arbitrarily selected by the applicant(s). In this case, the meanings of the arbitrarily selected terminologies shall be described in the corresponding part of the detailed description of the specification. Therefore, terminologies used in the present specification need to be construed based on the substantial meanings of the corresponding terminologies and the overall matters disclosed in the present specification rather than construed as simple names of the terminologies.
  • the method of expression for a 3 dimensional video may include a stereoscopic technique considering two viewpoints and a multiple view image technique (or a multi-view technique) considering more than 3 viewpoints.
  • a conventional single view image technique may be called a monoscopic video technique.
  • the stereoscopic technique uses a pair of image, i.e., a left view image and a right view image obtained by photographing a same subject with a left camera and a right camera, which are away a certain distance from each other.
  • the multi-view technique uses more than 3 images obtained by photographing with 3 or more cameras having a certain distance and angle.
  • a multi-view 3D video may be able to provide a user with a 3D video in a variety of viewpoints in a manner of selecting 2 images included in the 3D video of each of the viewpoints among the aforementioned 3 or more images.
  • This is called a 3D video service and can be used as a same meaning with a multiview service in the following description.
  • FIG. 1 is a diagram of a video element of a multi-view 3D video service according to one embodiment of the present invention.
  • a camera ID is assigned to each of the video streams.
  • a 2D legacy video service includes one video stream by one camera 1010 and a 3D video service includes two video streams filmed by two cameras 1010/1020.
  • a multi-view 3D video service includes four video streams filmed by 4 cameras 1010/1020/1030/1040.
  • FIG. 1 shows an example of 4 cameras, the present invention may be non-limited to the number of camera of embodiment and may be applicable to a multi-view 3D service filmed by 3 or more cameras.
  • each stream may include a camera parameter 1011/1021/1031/1041 according to each of the streams.
  • each of the streams may include an intrinsic and extrinsic camera parameter.
  • the intrinsic camera parameter is information informing characteristic of the camera itself and may include information related to optical characteristics of a lens.
  • the extrinsic camera parameter may include geometric position information on a practical or a virtual camera.
  • a 3D video service or a multi-view 3D video service includes a video configuration information 1050/1060, which corresponds to a metadata to combine each of the video streams into a 3D video, except the video streams.
  • the video configuration information includes information for providing the 3D video service or the multi-view 3D video service using each of the streams. The informations included in the video configuration information shall be explained in detail in the following description.
  • a camera view stream belonging to the multiview service may correspond to a video image itself or the information on depth and the like.
  • FIG. 2 is a diagram of a type of camera arrangement to film a multi-view 3D video according to one embodiment of the present invention.
  • FIG. 2(a) is a diagram of a type of circular convergent.
  • each of triangles means individual cameras, respectively.
  • An oval means an object.
  • the type of circular convergent has a form that the cameras surround the object as its center.
  • Camera-to-object distance which is one of meta information for the multi-view 3D video service intended to provide to a receiving side by the present invention, means a distance between the filmed object and an image plane of a camera forming a video on the basis of a center of a plurality of camera arrangements. According to the type of circular convergent, camera-to-object distance values of all cameras are identical.
  • FIG. 2(b) is a diagram of a type of linear convergent.
  • Each camera is linearly arranged and takes a picture of the object in a manner of controlling an angle of coverage to the object at the position of each of the cameras.
  • the camera-to-object distance is defined as a distance between an image plane of a central camera and the object. The distance from a different camera to the object can be calculated from the above camera-to-object distance and a distance from each camera to the central camera.
  • FIG. 2(c) is a diagram of a type of linear parallel.
  • Each camera is linearly arranged and takes a picture of a front at the position of each of the cameras.
  • the type of linear parallel does not control the angle of coverage to the object.
  • the images taken from the cameras of different positions according to each of the aforementioned types require an additional metadata to be combined into a multi-view 3D video by a receiver.
  • FIG. 3 is a diagram of a metadata for a multi-view 3D video service according to one embodiment of the present invention. Detail content is as follows.
  • Number of 3D views is provided at a program level and means the number of 3D viewpoint provided by a 3D video program.
  • Camera arrangement type is provided at the program level and indicates the type of camera arrangement described in FIG. 2 . As mentioned earlier, there exist the circular convergent type, the linear convergent type, and the linear parallel type.
  • Supported angle of view is provided at the program level and indicates a total viewing angle covered by a 3D video provided by a 3D video program or distance information of the camera positioned at the both ends of a camera arrangement.
  • the total viewing angle can be calculated by combining with a value of the camera-to-object distance.
  • a supported angle of view type can be added to the metadata.
  • Camera-to-object distance is provided at the program level.
  • the camera-to-object distance indicates a distance between the filmed object and an image plane of a central camera forming a video of a plurality of camera arrangements.
  • the camera arrangement such as the type of circular convergent, all cameras have an identical distance from the object.
  • View ID is provided by a unit of 3D viewpoint and indicates a unique identifier for each of the 3D viewpoints.
  • Depth range is provided by a unit of 3D viewpoint and indicates a minimum and maximum disparity of a 3D video provided by each of the 3D viewpoints. Or, the depth range indicates a depth budget of each of the 3D viewpoints.
  • Left camera position is provided by a unit of 3D viewpoint and indicates a position of a camera obtained a data corresponding to a left video included in the 3D viewpoint and indicates a distance or an angle on the basis of a center of a camera arrangement.
  • a negative number (-) means that the camera is positioned in the left of the center
  • a positive number (+) means that the camera is positioned in the right of the center.
  • the left camera position is expressed by a distance value.
  • the left camera position is expressed by an angle value.
  • Right camera position is provided by a unit of 3D viewpoint and indicates a position of a camera obtained a data corresponding to a right video included in the 3D viewpoint and indicates a distance or an angle on the basis of a center of a camera arrangement.
  • a negative number (-) means that the camera is positioned in the left of the center
  • a positive number (+) means that the camera is positioned in the right of the center.
  • the right camera position is expressed by a distance value.
  • the right camera position is expressed by an angle value.
  • Left camera ID is provided by a unit of 3D viewpoint and means an identifier (ID) of a camera obtained a data corresponding to a left video in the process of making the 3D viewpoint.
  • ID an identifier
  • a purpose of the left camera ID is to identify a position of a camera. As described in FIG 1 , in order to precisely identify a physical position of the camera, an intrinsic parameter and extrinsic parameter for the corresponding camera are separately transmitted.
  • Right camera ID is provided by a unit of 3D viewpoint and means an identifier (ID) of a camera obtained a data corresponding to a right video in the process of making the 3D viewpoint.
  • ID an identifier
  • a purpose of the right camera ID is to identify a position of a camera. As described in FIG 1 , in order to precisely identify a physical position of the camera, an intrinsic parameter and extrinsic parameter for the corresponding camera are separately transmitted.
  • FIG 4 is a diagram of a filming condition of a multi-view 3D video and a corresponding metadata according to one embodiment of the present invention.
  • FIG 4 (a) indicates values of each metadata according to the filming condition of the multi-view 3D video.
  • 4 cameras take a picture of an identical object and each of the cameras can be expressed as a camera 0 4010, a camera 1 4020, a camera 2 4030, and a camera 3 4040.
  • Supported angle of view is determined by an angle formed by the camera 0 4010, the camera 3 4040 positioned at the both ends of a camera arrangement and the object.
  • this value is expressed by 'A'.
  • This value can also be expressed by a distance between the cameras positioned at the both ends of the camera arrangement.
  • Center of camera array is determined by a center position between the camera 1 4020 and the camera 2 4030 positioned at the center. A distance from the center of camera array to the object can be determined as the camera-to-object distance. In the diagram, this value is expressed as 'D'.
  • the camera-to-object distance is determined by a distance between the object and an image plane of a camera positioned at the middle of the camera arrangement.
  • a position of each camera can be expressed by a distance from the center of camera array to each of the camera.
  • the camera 0 4010 and the camera 3 4040 have a value of ⁇ K' and the camera 1 4020 and the camera 2 4030 have a value of 'L'.
  • FIG 4 (b) is an example of metadata value for the aforementioned filming condition.
  • each viewpoint needs a video taken by two cameras to apply a binocular disparity
  • each of the viewpoints is provided by the camera 0 4010 and the camera 1 4020, the camera 1 4020 and the camera 2 4030, and the camera 2 4030 and the camera 3 4040, respectively. This shall be described in the following description according to each of the viewpoints.
  • supported angle of view type has a value of '0'
  • supported angle of view is expressed by an angle value.
  • the supported angle of view has a value of 'A' in FIG. 4 (a) .
  • the supported angle of view is expressed by a distance value.
  • the supported angle of view has a value of '2K', which corresponds to a distance value between cameras positioned at both ends, respectively.
  • Camera-to-object distance is determined by 'D' value, which corresponds to a distance from a center of the camera arrangement to the object.
  • An identifier (view ID) for a viewpoint has values of 0, 1, and 2 from the left viewpoint.
  • Information on each of the viewpoints includes a depth range, position of left/right cameras, and information on the identifiers of the left/right cameras.
  • the depth range includes min_disparity0 value indicating a minimum disparity and max_disparity0 value indicating a maximum disparity. Since the view ID 0 is a viewpoint including the camera 0 4010 and the camera 1 4020, a left camera position value corresponds to - K, which is a position of the camera 0. In this case, a negative number expression means that the corresponding camera is positioned at the left of the center of the camera arrangement.
  • Right camera position value has a value of - L, which is a position of the camera 1.
  • Left camera ID has a value of '0' corresponding to the ID of the camera 0 and right camera ID has a value of'1' corresponding to the ID of the camera 1.
  • the depth range includes min_disparity1 value indicating a minimum disparity and max_disparity1 value indicating a maximum disparity.
  • a left camera position value corresponds to - L, which is a position of the camera 1.
  • Right camera position value has a value of L, which is a position of the camera 2.
  • a positive number expression means that the corresponding camera is positioned at the right of the center of the camera arrangement.
  • Left camera ID has a value of '1' corresponding to the ID of the camera 1 and right camera ID has a value of '2' corresponding to the ID of the camera 2.
  • the depth range includes min_disparity2 value indicating a minimum disparity and max_disparity2 value indicating a maximum disparity. Since the view ID 2 is a viewpoint including the camera 2 4030 and the camera 3 4040, a left camera position value corresponds to L, which is a position of the camera 2. Right camera position value has a value of K, which is a position of the camera 3. Left camera ID has a value of '2' corresponding to the ID of the camera 2 and right camera ID has a value of '3' corresponding to the ID of the camera 3.
  • FIG. 5 is a diagram of a method of signaling a multi-view 3D service using a PMT according to one embodiment of the present invention.
  • the aforementioned metadata for the multi-view 3D video service can be included in a program map table (PMT) in a descriptor form.
  • PMT program map table
  • the PMT includes the following.
  • the table_id field is 8 bit field and TS_program_map_section is always set to a value oaf '0* 02'.
  • the section_syntax_indicator field is 1 bit field and is set to '1'.
  • the section_length field consists of 12 bits and first two bits are corresponding to '00'. This field indicates the number of bytes of a section and indicates a length from the right after this field to a CRC. The value of this field is not greater than 1021.
  • the program_number field consists of 16 bits. This field indicates a program to which the program_map_PID is applicable. One program definition is transmitted by one TS_program_map_section only. This connotes that the program definition is not greater than 1016.
  • the version_number field consists of 5 bits and indicates a version of a virtual channel. A version value increases by '1' on every change in a VCT. If the version value reaches '31', the next version value becomes '0'. The value of this field should be a same value of the same field of the MGT.
  • the current_next_indicator field consists of 1 bit. In case that the VCT is currently applicable, the value is set to '1'. If the value is set to '0', it means that the VCT is not applicable yet and the next table is valid.
  • the section_number field is set to '0 * 00'.
  • the last_section_number field is set to '0 * 00'.
  • the PCR_PID field consists of 13 bits. This field means a PID of TS including a PCR field, which is valid for a program mentioned by a program number.
  • the program_info_length field may consist of 12 bits and first two bits are corresponding to '00' value. The rest of 10 bits express a descriptor, which follows this field, as the number of bytes.
  • the stream_type field may consist of 8 bits and indicate a type of program element transmitted by a packet having a PID value of a basic PID.
  • the elementary_PID field may consist of 13 bits and indicate a PID of TS including a related program element.
  • the ES_info_length field may consist of 12 bits and first two bits are corresponding to '00'. The rest of 10 bits express a descriptor of a related program element, which follows this field, as the number of bytes.
  • the CRC_32 field indicates a CRC value making a register in a decoder to be zero output.
  • a method of including metadata for a multi-view 3D video service in the aforementioned PMT can be classified into 2 ways.
  • the multiview_descriptor is situated at a position of a descriptor 5010 right after the program_info_length field in the PMT and includes information on a corresponding program.
  • the multiview_descriptor may be able to include information on a whole of a service and each element stream.
  • a broadcasting receiving side may be able to recognize whether a multi-view 3D video service is provided by checking the existence of the multiview_descriptor. Detail information included in the multiview_descriptor shall be described in FIG 6 .
  • the multiview_service_descriptor may be able to include a common information on a service shared by all elements or a whole of a service and may be situated at a position of first descriptor 5010 in the PMT table.
  • the multiview_element_descriptor may include the information on each element stream included in a multi-view 3D video service and may be situated at a position of a second descriptor 5020 in the PMT table. Detail information included in the multiview_service_descriptor and the multiview_element_descriptor shall be described in FIG 7 .
  • FIG 6 is a diagram of detail information included in Multiview_descriptior according to one embodiment of the present invention.
  • the multiview_descriptor may include each 3D viewpoint included in a multi-view 3D video program in the PMT or information on common characteristics of a whole of the multi-view 3D video service. This means a descriptor of a program or a service level.
  • the multiview_descriptor can be effectively used in case that a plurality of streams are simultaneously received and then displayed at once. And, in case that only one stream information is known, the multiview_descriptor enables to recognize whether the stream is included in which 3D viewpoints.
  • the descriptor_tag is 8 bit field and identifies a type of a descriptor.
  • the multiview_descriptor of the present invention has a value of '0 * TBD'.
  • the descriptor_length is 8 bit counter and expresses the number of byte right after the descriptor_length field.
  • the num_3D_views is 8 bit field and means a total number of a 3D viewpoint provided by a multi-view 3D video program.
  • the camera_arrangement_type is 2 bit field and expresses a kind of arrangement of a plurality of cameras in a corresponding multi-view program. If a corresponding value is ⁇ 00', '01', '10', and '11', the camera_arrangement_type may be able to express a circular convergent type, a linear convergent type, a linear parallel type, and other type, respectively.
  • the supported_angle_of_view_type is 1 bit field and expresses a form of expression of the supported_angle_of_view field. If a corresponding value is '0', it means that the supported_angle_of_view is expressed by an angle unit and if a corresponding value is '1', it means that the supported_angle_of_view is expressed by a distance unit.
  • the supported_angle_of_view is 8 bit field and indicates a whole of viewing angle covered by a 3D video provided by a corresponding multi-view 3D video program or information on a distance between the cameras positioned at both ends of a camera arrangement.
  • the whole of viewing angle can be calculated by combining a value of a camera_to_object_distance in the following. If a value of the supported_angle_of_view is '0', it means a viewing angle and if the value of the supported_angle_of_view is '1', it means a distance from the cameras of both ends of a camera arrangement to a center point.
  • the camera_to_object_distance is 8 bit field and means a distance between an image plane forming a video and a filmed object on the basis of a center of a multi-view camera arrangement.
  • the camera_to_object_distance means the distance between the image plane forming a video of a center camera of a plurality of camera arrangements and the filmed object.
  • the camera arrangement such as the circular convergent type, all cameras have an identical distance from the object.
  • the following fields correspond to the information provided to each viewpoint of a multi-view 3D video service via a for-loop.
  • the 3D_view_ID is provided by a unit of 3D viewpoint and is 8 bit field. This field indicates a unique identifier making each 3D viewpoint to be identified in a program level.
  • the 3D-view_priority is provided by a unit of 3D viewpoint and is 8 bit field. This field indicates priority of each viewpoint. If the number of viewpoint (num_3D_views) provided by a multi-view 3D video service is greater than the number of viewpoint capable of being displayed in a receiver, the 3D-view_priority may be able to provide information on which viewpoint is preferentially displayed among a plurality of the viewpoints.
  • the left_PID is provided by a unit of 3D viewpoint and is 13 bit field.
  • the left_PID means a PID of a left video included in a corresponding 3D viewpoint.
  • the right_PID is provided by a unit of 3D viewpoint and is 13 bit field.
  • the right_PID means a PID of a right video included in a corresponding 3D viewpoint.
  • the left_cam_ID is provided by a unit of 3D viewpoint and is 8 bit field.
  • the left_cam_ID means an identifier (ID) of a camera obtained a data of an elementary stream corresponding to a left video in a process of making a corresponding 3D viewpoint.
  • the right_cam_ID is provided by a unit of 3D viewpoint and is 8 bit field.
  • the right_cam_ID means an identifier (ID) of a camera obtained a data of an elementary stream corresponding to a right video in a process of making a corresponding 3D viewpoint.
  • the left_cam_position is provided by a unit of 3D viewpoint and is 8 bit field.
  • the left_cam_position indicates a position of a camera obtained data corresponding to a left video included in a corresponding 3D viewpoint and indicates a distance or angle on the basis of a center of a camera arrangement.
  • the right_cam_position is provided by a unit of 3D viewpoint and is 8 bit field.
  • the right_cam_position indicates a position of a camera obtained data corresponding to a right video included in a corresponding 3D viewpoint and indicates a distance or angle on the basis of a center of a camera arrangement.
  • a negative number (-) means that a camera is positioned at a left of the center and a positive number (+) means that a camera is positioned at a right of the center.
  • a relative position from the center of the camera arrangement is expressed by a distance value.
  • the relative position from the center of the camera arrangement is expressed by a relative angle value.
  • the min_disparity is provided by a unit of 3D viewpoint and is 8 bit field.
  • the min_disparity means a depth budget (depth range) of each 3D viewpoint. In particular, it indicates a minimum disparity value provided by a corresponding 3D viewpoint.
  • the max_disparity is provided by a unit of 3D viewpoint and is 8 bit field.
  • the max_disparity means a depth budget (depth range) of each 3D viewpoint. In particular, it indicates a maximum disparity value provided by a corresponding 3D viewpoint.
  • FIG. 7 is a diagram of detail information included in Multiview_service_descriptor and Multiview_element_descriptor according to ne embodiment of the present invention.
  • FIG. 7 (a) is a diagram of the Multiview_service_descriptor providing common information of a multi-view 3D video service.
  • the multiview_service_descriptor includes information on the descriptor_tag, the descriptor_length, the num_3D_views, the camera_arrangement_type, the supported_angle_of_view_type, the supported_angle_of_view, the camera_to_object_distance.
  • FIG. 7 (b) is a diagram of the multiview_element_descriptor providing information on each element stream of a multi-view 3D video service.
  • the multiview_element_descriptor includes detail information on each element stream.
  • the multiview_element_descriptor includes information on the descriptor_tag, the descriptor_length, the camera_ID, the camera_position, the number_3D_views, the 3D_view_ID, the 3D_view_priority, the left_right_view, the other_camera_ID, the min_disparity, the max_disparity.
  • the camera_ID is 8 bit field and an identifier (ID) identifying a camera used to obtain a data of a corresponding element stream.
  • the camera_position is 8 bit field and indicates a position of a camera used to obtain a data of a corresponding element stream.
  • a negative number (-) means a left and a positive number (+) means a right on the basis of a camera positioned at the center of a camera arrangement.
  • the camera_position indicates a relative angle value on the basis of the camera positioned at the center of the camera arrangement.
  • the camera_position indicates a relative position value on the basis of the camera positioned at the center.
  • the center of the arranged cameras becomes a criterion.
  • the number_3D_views is 3 bit field and indicates the number of 3D viewpoint including a corresponding element stream.
  • the number_3D_views may have different value according to each element stream. For instance, in FIG. 4 (b) , if the camera_id corresponds to '1', the corresponding stream can be included in two 3D viewpoints, i.e., the view ID 0 and the view ID 1. In this case, the value of the number_3D_views indicates '2'.
  • the 3D_view_ID is 8 bit field and indicates an identifier of a 3D viewpoint to which a corresponding element stream is belonged. It is possible to know that the corresponding element stream is included in which 3D viewpoint by this field.
  • the 3D_view_priority is 8 bit field and may be able to specify the priority of the 3D viewpoint to which a corresponding element stream is belonged. As described in FIG. 6 , this value can be used to determine which viewpoint is preferentially displayed in case that the number of viewpoint capable of being displayed by a receiver is limited.
  • the left_right_view is 1 bit field and indicates whether a corresponding element stream is included in a left video or a right video in a current 3D viewpoint to which the corresponding element stream is belonged. In case that this field has a value of '0', it indicates the left video. In case that this field has a value of '1', it indicates the right video.
  • the other_camera_ID is 8 bit field and indicates an identifier of a camera used to obtain a data of an element stream making a pair with a current element stream to generate a corresponding 3D viewpoint. Since this field plays a role in distinguishing a different element stream, it is possible to replace this field with a value of a PID, a camera position, or the like.
  • the min_disparity and the max_disparity are 8 bit fields, respectively. These fields indicate a depth budget (depth range) of each 3D viewpoint. In particular, these fields may mean a minimum/maximum disparity of a 3D video provided by the each 3D viewpoint.
  • FIG. 8 is a diagram of a multi-view video service signaling using an SDT according to one embodiment of the present invention.
  • the SDT (service description table) is a table explaining services included in a specific transport stream in DVB-SI. It is possible to inform a receiver that a corresponding service is a multi-view 3D video service via a service_type in a service descriptor included in a descriptor of the SDT.
  • the service_type shall be described in detail in FIG. 9 .
  • this descriptor is called a multiview _descriptor and the information included in the multiview_descriptor shall be described in FIG 12 .
  • Each field included in the STD is defined as follows.
  • the table_id field is 8 bit field and indicates that this section belongs to a service description table.
  • the section_syntax_indicator is 1 bit field and is set to '1'.
  • the section_length is 12 bit field and first two bits of the section_length are set to '00'. This field indicates the number of bytes of a section from right after this field to CRC. This field cannot be greater than 1021 and a total length of the section becomes maximum 1024 bytes.
  • the transport_stream_id is 16 bit field and plays a label role of distinguishing a transport stream (TS).
  • the version_number is 5 bit field and indicates a version number of a sub_table. A version number increases by '1' on every change in the sub_table. If the version value reaches '31', the next version value becomes '0'.
  • the current_next_indicator is 1 bit field. In case that the sub_table is currently applicable, the current_next_indicator field is set to '1'. If it is set to '0', it means that the sub_table is not applicable yet and the next table is valid.
  • the section_number is 8 bit field.
  • the section_number field indicates the number of a section.
  • First section may have a value of '0 * 00'. The value increases by '1' on every additional section having a same table_id, transport_stream_id, and original_network_id.
  • the last_section_number is 8 bit field and indicates the number of the last section (in particular, the highest section_number) of a corresponding sub_table, which includes this section as a part.
  • the original_network_id is 16 bit field and is a label for checking a network_id of a transport system.
  • the service_id is 16 bit field and plays a label role of distinguishing a service from a different service included in the TS. This field is same with the program_number field of the program_map_section.
  • the EIT_schedule_flag is 1 bit field. If the EIT_schedule_flag field is set to '1', it may indicate that EIT schedule information for a corresponding service is included in current TS. If the field is set to '0', it may indicate that the EIT schedule information is not included in the TS.
  • the EIT_present_following_flag is 1 bit field. If the EIT_present_following_flag field is set to '1', it may indicate that EIT_present_following information for a corresponding service is included in current TS. If the field is set to '0', it may indicate that the EIT_present_following information is not included in the TS.
  • the running_status is 3 bit field and indicates a service status.
  • the free_CA_mode is 1 bit field. If the free CA mode field is set to '0', it indicates that all element streams of a corresponding service are not scrambled. If the field is set to '0', it means that one or more streams are controlled by a CA system.
  • the descriptor_loop_length is 12 bit field and indicates a total length of a following descriptor as byte unit.
  • the descriptor may include the descriptor for a service and may be able to include the service_type and the multiview_descriptor of the present invention aforementioned in the foregoing description.
  • the CRC_32 is 32 bit field and indicates a CRC value making a register in a decoder to be zero output.
  • FIG. 9 is a diagram of a service type included in an SDT according to one embodiment of the present invention.
  • FIG. 9 (a) is a diagram of a value of a legacy service type (service_type).
  • the service_type may be able to indicate a kind of service supportable by DVB.
  • the present invention defines such a new service type as a Stereoscopic Multi-view Service to support a multi-view 3D video service.
  • the value of the service_type is included in the Service Descriptor of the DVB and may be then able to be included in the aforementioned Descriptor Loop of the SDT in FIG. 8 .
  • FIG. 10 is a diagram of a component descriptor according to one embodiment of the present invention.
  • the DVB signals in a manner of adding a component descriptor as shown in FIG. 10 to the descriptor loop of the SDT.
  • the stream_content is 4 bit field and distinguishes a kind of stream. For instance, a video, an audio, EBU-data, or the like can be included.
  • the component_type is 8 bit field and describes each of video, audio, and EBU-data components.
  • the component_tag is 8 bit field and has a same value with the component_tag field of a stream identifier descriptor for a component stream.
  • the present invention may be able to define a stream_content and a component_type as shown in FIG. 11 to distinguish each of 3D viewpoints for the Stereoscopic Multi-view Service, which corresponds to a multi-view 3D video service.
  • FIG. 11 is a diagram of stream-content and component_type to indicate a multi-view 3D video service in a DVB broadcasting system according to one embodiment of the present invention.
  • a legacy MPEG-2 video or a H.264/AVC video codec can be used.
  • a codec providing a more enhanced performance e.g., a HEVC and the like, this can be signaled using the stream_content field.
  • the type of stream obtained from each camera may include a video and a metadata such as a depth map.
  • the video may include a stream capable of using a codec corresponding to a base layer or a stream coded by an enhancement layer (in case of the H.264/AVC, MVC or SVC extension), which should perform an inter-view prediction from the base layer.
  • an enhancement layer in case of the H.264/AVC, MVC or SVC extension
  • the type of corresponding stream is signaled using the component_type.
  • the classification for each type is as follows.
  • the multiview metadata component means a stream resulted from compressing a non-image data such as the depth map using a video codec.
  • the multiview video component means a video data. Specifically, a video belongs to not a base view but an enhancement view.
  • the multiview video component means a stream requiring a restoration via an inter-view, an interlayer prediction, or the like.
  • a frame rate or an aspect ratio of a corresponding component follows a property of a video component of a corresponding base view.
  • Video component types mean video component streams corresponding to the base view.
  • Information on a basic aspect ratio, frame rate and the like is included in this component type and 2D service is signaled using this component type in case of providing the 2D service.
  • FIG. 12 is a diagram of a multi-view service descriptor according to one embodiment of the present invention.
  • the multiview descriptor is situated at the position of descriptor right after a descriptors_loop_length field in the SDT and may include common information on a multi-view 3D video service and the information on each elementary stream to which belongs to the common information.
  • the multiview descriptor may include the descriptor_tag, the descriptor_length, the num_3D_views, the camera_arrangement_type, the supported_angle_of_view_type, the supported_angle_of_view, the camera_to_object_distance, the number_elements, the component_tag, the camera_ID, the camera_position, the number_3D_views, the 3D_view_priority, the 3D_view_ID, the left_right_view, the other_camera_ID, the min_disparity, the max_disparity.
  • the component_tag is used to indicate a connection relationship between the component descriptor and an ES (elementary stream) on an ES_loop of the PMT. It is able to indicate the connection relationship between the component descriptor in the SDT and a 3D_complementary_video_descriptor_SDT in a manner of having an identical value in the component_tag field in the stream identifier descriptor by the ES_loop descriptor of the PMT.
  • each element may include a plurality of informations via a loop and information on a plurality of 3D views capable of being generated is provided to each of the elements via the loop.
  • priority between the 3D views can be specified by the 3D_view_priority field. If it corresponds to a scenario that a receiver directly decides the priority of the 3D view capable of being generated in consideration of information on camera position, the 3D_view_priority field can be omitted.
  • the camera_pos field is provided information from the descriptor. It is possible to omit this field at this time. Since the camera_ID and the other_camera_ID field can be used to identify an element stream, the camera_ID and the other_camera_ID field may replace the PID.
  • the receiver may be able to provide a multi-view 3D video service using the multi view descriptor.
  • FIG 13 is a diagram of a signaling of a multi-view 3D video service and an additional service type using a TVCT according to one embodiment of the present invention.
  • TVCT is a table including the property of virtual channels included in a transport stream in PSIP of ATSC.
  • a service_type field and a multiview_descriptor() can be transmitted in a manner of being included in the TVCT.
  • Detail content of the multiview_descriptor() included in the TVCT shall be described in FIG. 14 .
  • the content included in the TVCT is as follows.
  • the table_id field indicates a type of a table section. For instance, in order to indicate the TVCT, its value should be '0 * C8'.
  • the section_syntax_indicator field is configured with 1 bit and its value is fixed to '1'.
  • the private_indicator field is set to '1'.
  • the section_length field consists of 12 bits and first two bits correspond to '00'. This field indicates the number of bytes of a section and indicates a length from the right after this field to a CRC. The value of this field cannot be greater than 1021.
  • the transport_stream_id field is configured with 16 bits and it is a MPEG-2 transport stream (TS) ID. It is possible to distinguish from a different TVCT by this field.
  • TS MPEG-2 transport stream
  • the version_number field indicates a version of a virtual channel.
  • a version value increases by '1' on every change in a VCT. If the version value reaches '31', the next version value becomes '0'.
  • the value of this field should be a same value of the same field of the MGT.
  • the current_next_indicator field is configured with 1 bit. In case that the VCT is currently applicable, the value is set to '1'. If the value is set to '0', it means that the VCT is not applicable yet and the next table is valid.
  • the section_number field indicates the number of section.
  • the value of the first section of the TVCT is '0 * 00' and increases by '1' on every additional section.
  • the last_section_number field means the number of the last section. In particular, it means the number of section having a highest section_number in the total of the TVCT.
  • the protocol_version field plays a role of permitting a kind of table different from the table defined by the current protocol in the future.
  • '0' is the only valid value in the current protocol. The value except '0' shall be used in a later version for a structurally different table.
  • the num_channels_in_section field indicates the number of virtual channel in the VCT section. Its value is restricted by the length of a section.
  • the short_name field indicates the name of a virtual channel.
  • the major_channel_number is 10 bit field and indicates a major channel number of a virtual channel defined in a corresponding order in for statement.
  • Each of the virtual channels consists of a major channel number and a minor channel number.
  • the major channel number plays a role of a reference number to a corresponding virtual channel for a user together with the minor channel number.
  • the major channel number has values ranging from 1 to 99 and a pair of major/minor channel numbers does not have a duplicated value in the TVCT.
  • the minor_channel_number is 10 bit field and has values ranging from 0 to 999.
  • the minor channel number operates as a two-part channel number together with the major channel number.
  • a service type is either ATSC_digital_television or ATSC_audio_only
  • the minor channel number has values ranging from 1 to 99.
  • a pair of major/minor channel numbers does not have a duplicated value in the TVCT.
  • the modulation_mode field indicates a modulation mode of a transport carrier, which is related to a corresponding virtual channel.
  • a value of the carrier_frequency field is '0'. Although the carrier frequency is permitted to be checked using this field, it is contradicted.
  • the channel_TSID field has values ranging from '0 * 0000' to '0 * FFFF' and it is an MPEG-2 TSID, which is related to a TS delivering MPEG-2 program referenced by this virtual channel.
  • the program_number field attaches a virtual channel defined in the TVCT to MPEG-2 PROGRAM ASSOCIATION and TS PROGRAM MAP TABLE.
  • the ETM_location field indicates existence and location of an extended text message (ETM).
  • the access_controlled field is a 1 bit Boolean flag. If the flag is '1', it is able to indicate that an access of an event related to a corresponding virtual channel is restricted. If the flag is '0', it indicates that the access is not restricted.
  • the hidden field is a 1 bit Boolean flag. If a flag is '1', although a corresponding number is directly inputted by a user, an access is not permitted. A hidden virtual channel is skipped in case that a user surfs channels and can be seen as it is not defined.
  • the hide_guide field is a Boolean flag. If it is set to '0' for a hidden channel, a virtual channel and an event of the hidden channel can be seen in EPG display. If a hidden bit is not set, this field is ignored. Hence, non-hidden channel and its event belong to the EPG display irrespective of the state of a hide_guide bit.
  • the service_type field checks a service type delivered by a corresponding virtual channel.
  • the service_type field can be used to inform a receiver that a corresponding service is a multi-view 3D service in the present invention.
  • the value of the service_type field is exemplified as '0 * 13' in the present invention, it may be non-limited.
  • the service type can be defined as the multi-view 3D video service (ATSC Multi-view service).
  • the source_id field checks a programming source related to a virtual channel.
  • a source may be one selected from the group consisting of a video, a text, data, or an audio programming.
  • the source id '0' is a reserved value and values ranging from '0 * 0001' to '0 * OFFF' have a sole value in the TS, which delivers the VCT. And, values ranging from '0 * 1000' to '0 * FFFF' have a sole value in a region level.
  • the descriptor_length field expresses a length of a descriptor, which follows a corresponding virtual channel, as a byte unit.
  • a descriptor is not included or more than one descriptor can be included in descriptor ().
  • the information on elementary stream constructing a multi-view 3D video service can be included in the descriptor () in a form of the multiview_descriptor in the present invention.
  • the additional_descriptors_length field expresses a total length of following VCT descriptor list as a byte unit.
  • the CRC_32 field indicates a CRC value making a register in a decoder to be zero output.
  • FIG 14 is a diagram of a multi-view 3D video service descriptor according to one embodiment of the present invention.
  • the multiview descriptor is positioned in the TVCT and includes common information on the multi-view 3D video service of a corresponding virtual channel and the information on the elementary stream to which belongs to the common information.
  • the multiview descriptor may include the descriptor_tag, the descriptor_length, the PCR_PID, the num_3D_views, the camera_arrangement_type, the supported_angle_of_view_type, the supported_angle_of_view, the camera_to_object_distance, the number_elements, the elementary_PID, the camera_ID, the camera_position, the number_3D_views, the 3D_view_priority, the 3D_view_ID, the left_right_view, the other_camera_ID, the min_disparity, the max_disparity.
  • the PCR_PID is 13 bit field and indicates PID of transport stream packets including a PCR (program clock reference) field.
  • the elementary_PID is 13 bit field and corresponds to a packet identifier for an elementary stream.
  • the receiver may be able to provide a multi-view 3D video service using the multi view descriptor.
  • FIG. 15 is a diagram of an independent table to provide a multi-view 3D video service information according to one embodiment of the present invention.
  • FIG. 15 indicates a multiview service section and information on a multi-view 3D video service can be transmitted not a form of a descriptor of PSI/SI section but a form of an independent table.
  • the multiview service section may include a table_id, a section_syntax_indicator, a section_length, a transport_stream_id, a version_number, a current_next_indicator, a section_number, a last_section_number, a corresponding_program_number, a number_of_3D_views_in_section, a camera_arrangement_type, a supported_angle_of_view_type, a supported_angle_of_view, a camera_to_object_distance, a 3D_view_ID, a 3D_view_priority, a left_elementary_PID, a left_camera_ID, a left_camera_position, a right_elementary_PID, a right_camera_ID, a right_camera_position, a min_disparity, a max_disparity.
  • the multiview service section provides information on a corresponding left/right view stream by a unit of 3D view.
  • the corresponding_program_number field is used to interlock the information provided by the multiview service section with a practical channel or a service.
  • corresponding program information can be interlocked with reference to the PMT corresponding to the program_number indicated by the corresponding_program_number field. It is possible to directly interlock with a virtual channel of ATSC or a service of DVB as well.
  • FIG. 16 is a diagram of a floor plan of a single 3DTV display case according to one embodiment of the present invention.
  • the single 3DTV display receiver is able to watch 3D viewpoints (3D view) different from each other (for instance, different watching angle for an identical content) in a manner of selecting the 3D viewpoints via one 3D display frame.
  • the receiver Since the receiver is able to display one viewpoint at a time, a viewer is able to watch a preferable 3D view using such a user interface as a remote control arrow key, a screen touch, other sensor, or the like in the middle of watching.
  • a user is watching a view ID 1.
  • the user is able to watch a view ID 0 or a view ID 2 via the aforementioned method.
  • FIG. 17 is a diagram of a floor plan of a multi-view 3DTV display case according to one embodiment of the present invention.
  • FIG 17 (a) is a bird's-eye diagram of a case that one viewer is watching 3D views different from each other according to a watching angle or a position of the viewer.
  • the viewer in case that the viewer is positioned at a left, a front, or a right of a display, the viewer is able to watch a video of view ID 0, view ID 1, or view ID 2, respectively.
  • FIG. 17 (b) is a bird's-eye diagram of a case that three viewers are watching 3D views different from each other according to a watching angle or a position of the viewers.
  • a user 0 positioned at the left of a display watches a video of view ID 0 and a user 1 positioned at the front of the display watches a video of view ID 1.
  • a user 2 positioned at the right of the display watches a video of view ID 2.
  • the view ID according to a position may be randomly modified and may be non-limited to the aforementioned case.
  • FIG. 18 is a flowchart of a case of receiving a multi-view 3D video service information using a multiview descriptor of a PMT according to one embodiment of the present invention.
  • Filming environment information (a camera arrangement structure, distance between a camera and an object, and a provided total viewing angle) of a multiview service and the number of 3D views provided by the service can be identified via the multiview descriptor.
  • the number of 3D views included in a multiview 3DTV service and PID_L/PID_R information of a left/right video stream included by each of the 3D views are identified via the multiview descriptor.
  • Table 1 One embodiment in case of a multiview service providing three 3D views and four elementary streams is shown in Table 1 as follows. [Table 1] 3D_view_ID 3D_view_priority PID_L,PID_R Cam_ID_L, Cam_ID_R Cam_pos_L,Cam_pos_R Min_disparity, Max_disparity 0 1 PID 0, PID 1 CID 0, CID 1 Cpos 0, Cpos 1 Min 0, Max 0 1 0 PID 1, PID 2 CID 1, CID 2 Cpos 1, Cpos 2 Min 1, Max 1 2 2 PID 2, PID 3 CID 2, CID 3 Cpos 2, Cpos 3 Min 2, Max 2
  • a mapping to the information provided via the TVCT is performed using the program_number field. By doing this, it is able to know which virtual channel provides a corresponding program.
  • elementary streams related to the 3D views corresponding to a range ranging from 0 to 'N - 1' are filtered in by parsing a 3D_view_priority value for each of the 3D views.
  • the elementary streams related to the 3D views of which the 3D_view_priority value is greater than the 'N' are all filtered out. Since the elementary streams greater than the number of 3D views capable of being outputted are unable to be displayed in the end even if they are decoded.
  • a left video and a right video for each of 3D views are mapped in a manner of combining with the decoded signal using a left_right_view field and the like included in the multiview descriptor.
  • a relative position of a corresponding 3D view is calculated in consideration of a position of a camera for the left and right video stream included in each of the 3D views.
  • Each of the 3D views is displayed as a multi-viewpoint output in consideration of the relative position of the 3D views obtained from the above step.
  • a viewpoint is switched by identifying a PID of a video stream for a left/right video of a new 3D view selected by a viewer using the information on a multiview service, which is ready in advance.
  • the number of 3D views provided by a display device is less than the number of 3D views provided by a program, it may be outputted based on the 3D_view_priority or may follow a camera position, user's selection, or the like.
  • FIG 19 is a flowchart of a case of receiving a multi-view 3D video service information using a multiview service descriptor and a multiview element descriptor of a PMT according to one embodiment of the present invention.
  • multiview 3DTV multi-view 3D video
  • a mapping to the information provided via the TVCT is performed using the program_number field. By doing this, it is able to know which virtual channel provides a corresponding program.
  • Filming environment information of a multiview service and the number of 3D views provided by the service can be identified via the multiview service descriptor.
  • the filming environment information may include a camera arrangement structure, distance between a camera and an object, and a provided total viewing angle.
  • the 3D view-related information may include whether a current stream belongs to which side among a left/right in a corresponding 3D view, other stream camera ID for another stream included by the corresponding 3D view, and disparity range of each of the views.
  • elementary streams related to the 3D views corresponding to a range ranging from 0 to 'N - 1' are filtered in by parsing a 3D_view_priority value for each of the 3D views.
  • the elementary streams related to the 3D views of which the 3D_view_priority value is greater than the 'N' are all filtered out. Since the elementary streams greater than the number of 3D views capable of being outputted are unable to be displayed in the end even if they are decoded.
  • a left video and a right video for each of 3D views are mapped in a manner of combining with the decoded signal using a left_right_view field and the like included in the multiview descriptor.
  • a relative position of a corresponding 3D view is calculated in consideration of a position of a camera for the left and right video stream included in each of the 3D views.
  • Each of the 3D views is displayed as a multi-viewpoint output in consideration of the relative position of the 3D views obtained from the above step.
  • the elementary streams of a view intended to watch are obtained using the 3D_view_ID, the 3D_view_priority, or the camera_position information. Following procedures are identical to the steps after the step of mapping the left/right video in a manner of filtering in.
  • FIG. 20 is a flowchart of a case of receiving a multi-view 3D video service information using a multiview descriptor of an SDT according to one embodiment of the present invention.
  • a corresponding service provides a multi-view 3D video service (multiview stereoscopic 3DTV service) using the service_type field of the service descriptor of the PMT. Or, it may be able to recognize a 3D video service by the existence of the multiview descriptor.
  • Filming environment information of a multiview 3D video service and the number of 3D views provided by the service can be identified via the multiview descriptor.
  • the filming environment information may include a camera arrangement structure, distance between a camera and an object, and a provided total viewing angle.
  • the number of 3D views included in a multiview 3D video service and PID_L/PID_R information of a left/right video stream included by each of the 3D views are identified via the multiview descriptor.
  • the 3D view can be separately designated by a receiver or can be determined in a manner of considering higher priority with reference to the 3D_view_priority field value.
  • a component_tag of elementary streams related to the 3D views corresponding to a range ranging from 0 to 'N - 1' are obtained only by parsing a 3D_view_priority value for each of the 3D views.
  • the elementary streams related to the 3D views of which the 3D_view_priority value is greater than the 'N' are all filtered out. Since the elementary streams greater than the number of 3D views capable of being outputted are unable to be displayed in the end even if they are decoded.
  • the PMT having the program_number field coincident with a value of service_id of the SDT is searched and then parsed.
  • a corresponding PID information is received in a manner of searching for the component_tag value of a stream identifier descriptor of an ES descriptor loop coincident with the previously obtained component_tag values of each of the streams among the elementary streams of the PMT.
  • the streams corresponding to each of the PIDs are decoded.
  • a left video and a right video for each of 3D views are mapped in a manner of combining with the decoded signal using a left_right_view field and the like included in the multiview descriptor.
  • a relative position of a corresponding 3D view is calculated in consideration of a position of a camera for the left and right video stream included in each of the 3D views.
  • Each of the 3D views is displayed as a multi-viewpoint output in consideration of the relative position of the 3D views obtained from the above step.
  • component_tag information of the streams included in the viewpoint intended to watch is received using the camera_ID or the camera_position information.
  • the viewpoint can be switched by executing the following steps after the step of searching for and parsing the PMT having the program_number field.
  • FIG. 21 is a flowchart of a case of receiving a multi-view 3D video service information using a multiview descriptor of a TVCT according to one embodiment of the present invention.
  • a corresponding virtual channel provides a multi-view 3D video service (multiview stereoscopic 3DTV service) using the service_type field of the TVCT. Or, it may be able to recognize a multiview service by the existence of the multiview descriptor while using a service_type of ATSC digital television identical to legacy broadcasting.
  • Filming environment information of a multiview service and the number of 3D views provided by the service can be identified via the multiview descriptor.
  • the filming environment information may include a camera arrangement structure, distance between a camera and an object, and a provided total viewing angle.
  • the number of 3D views included in a multiview 3D video service and PID_L/PID_R information of a left/right video stream included by each of the 3D views are identified via the multiview descriptor.
  • the 3D view can be separately designated by a receiver or can be determined in a manner of considering higher priority with reference to the 3D_view_priority field value.
  • a PID of the elementary streams related to the 3D views corresponding to a range ranging from 0 to 'N - 1' are obtained only by parsing a 3D_view_priority value for each of the 3D views.
  • the elementary streams related to the 3D views of which the 3D_view_priority value is greater than the 'N' are all filtered out. Since the elementary streams greater than the number of 3D views capable of being outputted are unable to be displayed in the end even if they are decoded.
  • the streams corresponding to each of the PID are decoded.
  • a left video and a right video for each of 3D views are mapped in a manner of combining with the previously decoded signal using a len_right_view field and the like included in the multiview descriptor.
  • a relative position of a corresponding 3D view is calculated in consideration of a position of a camera for the left and right video stream included in each of the 3D views.
  • Each of the 3D views is displayed as a multi-viewpoint output in consideration of the relative position of the 3D views obtained from the above step.
  • PID information of the streams included in the viewpoint intended to watch is received using the camera_ID or the camera_position information.
  • the viewpoint can be switched by executing the following steps after the step of decoding the streams corresponding to the PID.
  • FIG. 22 is a flowchart of a case of receiving a multi-view 3D video service information using a multiview event descriptor of an EIT according to one embodiment of the present invention.
  • Information on the multiview service provided via a corresponding event is identified with reference to a multiview event descriptor provided for each event of the EIT.
  • the information on whether a 3D multiview service is provided for the corresponding event can be expressed in a broadcast guide (EPG).
  • EPG broadcast guide
  • the number of 3D views included in the corresponding event and the information on such a filming environment as a total viewing angle and the like are identified via a multiview event descriptor.
  • a 3D receiver may display these informations in the broadcast guide or may be able to perform a preparation operation for an effective 3D rendering in a manner of comparing the multiview display specifications of the 3D receiver with the specifications required by the event.
  • the preparation operation may include an operation of presetting a 3D multiview controller module in consideration of a camera arrangement, a camera distance, the number of views, and the like.
  • a message like 'All 3D views provided by the present broadcasting may be not supported by the receiver of your own' can be outputted in a guide screen or in the middle of watching the corresponding event.
  • the receiver may be able to make preparation in advance for a possible discontinuity of the number of 3D views on an event boundary using the information of the multiview event descriptor.
  • FIG 23 is a diagram of a multiview event descriptor according to one embodiment of the present invention.
  • the multiview event descriptor in FIG. 23 may include a descriptor_tag, a descriptor_length, a num_3D_views, a camera_arrangement_type, a supported_angle_of_view_type, a supported_angle_of_view, a camera_to_object_distance, and a number_elements.
  • FIG. 24 is a diagram of a 3D receiver providing a multi-view 3D video service according to one embodiment of the present invention.
  • a broadcast signal receiver may be able to include a tuner and demodulator 24010, a demultiplexor 24020, a signal data processor 24030, a multiview information processor 24040, a plurality of video decoders 24050/24051/24052, a plurality of selectors 24060/24061/24062, a plurality of formatter 24070/24071/24072, and/or a multiview output control unit 24080.
  • the tuner and demodulator 24010 is configured to tune a received broadcast signal and may be able to output a demodulated broadcast signal to the demultiplexor 24020 after performing a demodulation for a tuned broadcast signal.
  • the tuner 24010 may be able to perform a VSB (vestigial side band) demodulation, an OFDM (orthogonal frequency division multiplexing) demodulation, or the like.
  • the demultiplexor 24020 is configured to extract a video stream PID from a signaling data and configured to output to a plurality of the video decoder 24050/24051/24052 in a manner of extracting a video stream or a metadata component from a decoded broadcast signal using the corresponding video stream PID.
  • a base video component is inputted in a base video decoder 24050 and a multi-view video component or a metadata component can be inputted in a 2nd video decoder 24051/24052.
  • the signaling data processor is configured to parse a signaling data from a signal outputted from the demultiplexor 24020 and configured to output the signaling data.
  • the signaling data may include a PSI, a PSIP, a DVB-SI, and the like.
  • a part of the signaling data is used in a manner of being inputted in the video decoder 24050/24051/24052 and a part of the signaling data can be inputted in the multiview information processor 24040.
  • the multiview information processor 24040 is configured to parse information on the multi-view 3D video service among the signal data inputted from the signaling data processor 24030. This parsed information is inputted to the video decoders 24050/24051/24052 or the selectors 24060/24061/24062 and used as the information to generate the multi-view 3D video service.
  • a plurality of the video decoders 24050/24051/24052 are configured to decode the components inputted from the demultiplexor 24020.
  • the base video decoder 24050 is configured to decode a base video component and the 2nd video decoders 24051/24052 may be able to decode a multi-view video component or a metadata component.
  • a plurality of the video decoders 24050/24051/24052 may be able to utilize the informations inputted from the signaling processor 24030 or the multiview information processor 24040.
  • a plurality of the selectors 24060/24061/24062 may be able to select two video signals corresponding to a left and a right video of each viewpoint among the plurality of video signals outputted from a plurality of the video decoders 24050/24051/24052.
  • this is an operation of mapping a 3D viewpoint of a reception signal to a viewpoint of a receiving device.
  • the information on the multi-view 3D video service outputted from the multiview information processor 24040 can be used.
  • a plurality of the formatters 24070/24071/24072 may be able to output a 3D video in a manner of receiving the left video and the right video of each viewpoint from a plurality of the selectors 24060/24061/24062 and performing a 3D format conversion and the like.
  • 3D videos of each viewpoint outputted from a plurality of the formatters 24070/24071/24072 can be displayed as a multi-view output in a manner of being controlled by the multiview output control unit 24080.
  • a user is able to watch a plurality of viewpoints included in the multi-view 3D video service simultaneously or selectively.
  • FIG. 25 is a diagram of an environment of a multi-view 3D video service according to one embodiment of the present invention.
  • a multiview 3D television provides an environment for simultaneously displaying four viewpoints. Users may be able to watch 3D viewpoints different from each other at their own position. In particular, it may be able to watch a 3D viewpoint 1, 2, 3, and 4 at the position 1, 2, 3, and 4, respectively. Each of the viewpoints can be generated by two videos, which corresponds to the left and right video.
  • FIG 26 is a diagram of a user interface to watch a multi-view 3D video according to one embodiment of the present invention.
  • FIG. 26 shows an interface to check a position of each user. It may be able to simply check the number of a 3D viewpoint being outputted on every screen of each position. It is able to check the information on a current position when a confirmation button or a separately assigned button is pushed. Although a user watches a same television, a graphic screen outputted according to the position of the user may be different. In particular, it is possible to output an UI corresponding to the position of the user.
  • FIG. 26 (a) indicates a screen outputted at the position 2 only and FIG. 26 (b) indicates a screen outputted at the position 4 only.
  • FIG. 27 is a diagram of a user interface in accordance with a position of a user according to one embodiment of the present invention.
  • User interfaces for EPG, volume adjustment, checking a current state, and the like can be commonly applied to all regions or angles irrespective of a position. Hence, there is no problem even if the related user interface is shared in all positions. Yet, in case that a configuration different from each other is needed according to the positions, if the configuring process is simultaneously displayed in all positions, it may cause chaos.
  • An example of a case that configurations different from each other are needed according to the positions may include a selection of a 3D view per position, the selection of use a subtitle or a caption, the selection of language in case of using a subtitle or a caption, and the like.
  • a user A launches a menu to change a configuration in relation to the position of the user A
  • the rest of users i.e., a user B and a user C have to watch the menu screen launched by the user A although the user B and the user C need not change any configuration.
  • buttons per position it is possible to separately launch a user interface according to each 3D view and to display unique information only corresponding to an output screen.
  • FIG 28 is a diagram of a user interface designating a mapping between a position of a user and an output 3D viewpoint according to one embodiment of the present invention.
  • a user may be able to randomly select a 3D view to be outputted in a corresponding position. As shown in FIG. 28 , the user selects one 3D view among all 3D views provided in a program. Each 3D view of the user interface is able to display a video together with the number of corresponding viewpoint. An initial setting value may be the currently outputting 3D view. There may exist a brief explanation on a corresponding viewpoint on every viewpoint.
  • FIG. 29 is a diagram of a user interface of a keyword mode according to one embodiment of the present invention.
  • 3D views of all positions and other selections can be configured in one position. Since this is a configuration commonly applied to all screens, the user interface can be displayed by a 2D view in a manner of performing a flattening besides a method of displaying by a 3D view.
  • an enter button is pushed after a position of a screen to be adjusted is selected, it moves to the screen capable of configuring the selection for the position.
  • a user interface screen corresponding to FIG 27 and FIG 28 can be sequentially activated.
  • the initial setting value is set to the position by which a current remote control is operated, it may be able to minimize the number of pushing the remote control. Yet, in this case, it is necessary to identify a current position of the remote control.
  • a process of storing a combination of each 3D viewpoint, position of camera, PID value, and the like to provide a user interface for a multi-view 3D video service is as follows.
  • the signal data processor and the multiview information processor receive the information on the whole of the multiview service and the information related to each of the 3D views, these informations can be used for the user interface.
  • these informations can be used for the user interface.
  • a user may be able to refer the informations.
  • FIG. 30 is a diagram of mapping of a 3D viewpoint in accordance with each position in case that the 3D viewpoint provided by a program corresponds to 5 according to one embodiment of the present invention.
  • a different embodiment for the process of storing a combination of each 3D viewpoint, position of camera, PID value, and the like is as follows.
  • the multiview information processor parses the multiview descriptor included in the PSI, the SI, or the PSIP section.
  • a relative position of each 3D view is identified in a manner of analyzing the content of the multiview descriptor.
  • the classification is performed in a manner of calculating an average value of the positions of a left and right camera according to each viewpoint and then listing the average value from a smaller value in ascending order and then mapping a 3D viewpoint to each of the average values.
  • the 'u + 1' is used since the 'u' starts from '0' and a cam position number shown in FIG. 30 starts from '1'.
  • the cam position number is matched with the number shown in FIG. 30 .
  • a user may selectively display the multiview description information corresponding to the 3D view ID in response to the selection.
  • a center information, min or max disparity information are depicted as an example.
  • FIG. 31 is a diagram of a metadata and a 3D viewpoint in accordance with a position according to one embodiment of the present invention.
  • a scenario of a case that a receiver selects a 3D view to be outputted in a specific position is as follows.
  • a case that the specific position corresponds to a position #2 and the 3D view to be outputted corresponds to a 2nd 3D view, in other word, a case of selecting '3D view ID 1' is explained as an example.
  • the information may include PID value of an included video stream, and the like.
  • a corresponding video ES is filtered based on '0 * 1A01' and '0 * 1A02', which correspond to the PID values identified in the previous step.
  • the left and right video included in a 3D video can be designated to the position #2 as shown in FIG. 31 (b) .
  • FIG 32 is a diagram of a 3D receiver providing a multi-view video service according to one embodiment of the present invention.
  • a broadcast signal receiver may be able to include a tuner and demodulator 32010, a demultiplexor 32020, a signal data processor 32030, a multiview information processor 32040, a plurality of video decoders 32050/32051/32052, a plurality of selectors 32060/32061/32062, a plurality of formatter 32070/32071/32072, a multiview output control unit 32080, and/or a user interface 32090.
  • the tuner and demodulator 32010 is configured to tune a received broadcast signal and may be able to output a demodulated broadcast signal to the demultiplexor 32020 after performing a demodulation for a tuned broadcast signal.
  • the tuner 32010 may be able to perform a VSB (vestigial side band) demodulation, an OFDM (orthogonal frequency division multiplexing) demodulation, or the like.
  • the demultiplexor 32020 is configured to extract a video stream PID from a signaling data and configured to output to a plurality of the video decoder 32050/32051/32052 in a manner of extracting a video stream or a metadata component from a decoded broadcast signal using the corresponding video stream PID based on the PID for a 3D viewpoint selected by the user interface (UI).
  • a base video component is inputted in a base video decoder 32050 and a multi-view video component or a metadata component can be inputted in a 2nd video decoder 32051/32052.
  • the signaling data processor 32030 is configured to parse a signaling data from a signal outputted from the demultiplexor 32020 and configured to output the signaling data.
  • the signaling data may include a PSI, a PSIP, a DVB-SI, and the like.
  • a part of the signaling data is used in a manner of being inputted in the video decoder 32050/32051/32052 and a part of the signaling data can be inputted in the multiview information processor 32040.
  • the signaling data may be able to include the information on the 3D viewpoint selected by the user interface 32090.
  • the multiview information processor 32040 is configured to parse the information on the multi-view 3D video service for the viewpoint selected by the user interface 32090 among the signal data inputted from the signaling data processor 32030. This parsed information is inputted to the video decoders 32050/32051/32052 or the selectors 32060/32061/32062 and used as the information to generate the multi-view 3D video service.
  • a plurality of the video decoders 32050/32051/32052 are configured to decode the components inputted from the demultiplexor 32020.
  • the base video decoder 32050 is configured to decode a base video component and the 2nd video decoders 32051/32052 may be able to decode a multi-view video component or a metadata component.
  • a plurality of the video decoders 32050/32051/32052 may be able to utilize the informations inputted from the signaling processor 32030 or the multiview information processor 32040.
  • a plurality of the selectors 32060/32061/32062 may be able to select two video signals corresponding to a left and a right video of each viewpoint among the plurality of video signals outputted from a plurality of the video decoders 32050/32051/32052.
  • this is an operation of mapping a 3D viewpoint of a reception signal to a viewpoint of a receiving device.
  • a selection for the two video signals corresponding to the left and right video can be performed based on the 3D viewpoint selected by the user interface 32090.
  • the information on the multi-view 3D video service outputted from the multiview information processor 32040 can be used.
  • a plurality of the formatters 32070/32071/32072 may be able to output a 3D video in a manner of receiving the left video and the right video of each viewpoint from a plurality of the selectors 32060/32061/32062 and performing a 3D format conversion and the like.
  • 3D videos of each viewpoint outputted from a plurality of the formatters 32070/32071/32072 can be displayed as a multi-view output in a manner of being controlled by the multiview output control unit 32080.
  • a user is able to watch a plurality of viewpoints included in the multi-view 3D video service simultaneously or selectively.
  • the present invention can be applied to an overall digital broadcasting system or a part of the digital broadcasting system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Library & Information Science (AREA)
  • Testing, Inspecting, Measuring Of Stereoscopic Televisions And Televisions (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Claims (13)

  1. Dispositif de réception de signal de radiodiffusion numérique, comprenant :
    un syntoniseur (24010, 32010) configuré pour recevoir un signal de radiodiffusion numérique incluant une pluralité de flux vidéo mettant en oeuvre une vidéo 3D multivue et des données de signalisation ;
    un processeur (24030, 32030) de données de signalisation configuré pour décoder les données de signalisation incluant une table de description de service, SDT, d'informations de service, SI, dans des systèmes de radiodiffusion numérique de vidéos, DVB, dans lesquelles un descripteur de composant spécifiant un type d'un flux est inclus,
    dans lequel le descripteur de composant comprend une information de contenu de flux étant un champ à 4 bits et une information de type de composant étant un champ à 8 bits,
    et dans lequel une combinaison de l'information de contenu de flux et de l'information de type de composant est utilisée pour indiquer le flux transportant une vue d'amélioration codée par un codage vidéo multivue, MVC, pour la vidéo 3D multivue, dans lequel la vue d'amélioration est transportée par un flux qui est différent d'un flux transportant une vue de base, dans lequel chacun de la pluralité des flux vidéo inclus dans le signal de radiodiffusion inclut des paramètres intrinsèques et extrinsèques de caméra pour chaque caméra respectivement ;
    un décodeur (24050, 24051, 24052, 32050, 32051, 32052) configuré pour décoder une pluralité des flux vidéo en utilisant la SDT ; et
    un formateur (24070, 24071, 24072, 32070, 32071, 32072) configuré pour délivrer en sortie les images vidéo des flux vidéo décodés comme la vidéo 3D multivue.
  2. Dispositif de réception de signal de radiodiffusion numérique selon la revendication 1, dans lequel le dispositif de réception de signal de radiodiffusion numérique comprend en outre une unité (24080, 32080) de commande de sortie de multivue configurée pour afficher la vidéo 3D multivue délivrée en sortie en prenant en considération une position relative de chaque point de vue.
  3. Dispositif de réception de signal de radiodiffusion numérique selon la revendication 1, dans lequel la SDT inclut en outre des informations de vidéo 3D multivue pour convertir les flux vidéo en la vidéo 3D multivue, et les informations de vidéo 3D multivue comprennent au moins un choisi parmi le groupe consistant en le nombre de points de vue, un procédé d'agencement de caméras, une priorité de chaque point de vue, un angle de vue fourni par la vidéo 3D multivue, une distance entre caméras, ou un identifiant d'une caméra différente formant une vidéo 3D ensemble en fonction de chaque point de vue.
  4. Dispositif de réception de signal de radiodiffusion numérique selon la revendication 3, dans lequel les informations de vidéo 3D multivue sont contenues dans la SDT sous une forme d'un descripteur.
  5. Dispositif de réception de signal de radiodiffusion numérique selon la revendication 3, dans lequel, si le nombre de points de vue aptes à être affichés dans un récepteur est inférieur au nombre de points de vue inclus dans le signal de radiodiffusion numérique, la priorité de chaque point de vue filtre une partie d'une pluralité des flux vidéo en fonction de la priorité.
  6. Dispositif de réception de signal de radiodiffusion numérique selon la revendication 1, comprenant en outre :
    un module (32090) d'interface utilisateur configuré pour afficher une interface utilisateur de sélection de position pour recevoir une entrée d'utilisateur sélectionnant une position d'un écran et afficher une interface utilisateur de sélection de vue 3D pour recevoir une entrée d'utilisateur sélectionnant une vue 3D destinée à être délivrée en sortie à la position de l'écran.
  7. Procédé de réception d'un signal de radiodiffusion numérique, comprenant les étapes de :
    réception d'un signal de radiodiffusion numérique incluant une pluralité de flux vidéo mettant en oeuvre une vidéo 3D multivue et des données de signalisation ;
    décodage des données de signalisation incluant une table de description de service, SDT, d'informations de service, SI, dans des systèmes de radiodiffusion numérique de vidéos, DVB, dans lesquelles un descripteur de composant spécifiant un type d'un flux est inclus,
    dans lequel le descripteur de composant comprend une information de contenu de flux étant un champ à 4 bits et une information de type de composant étant un champ à 8 bits,
    dans lequel une combinaison de l'information de contenu de flux et de l'information de type de composant est utilisée pour indiquer le flux transportant une vue d'amélioration qui est codée par un codage vidéo multivue, MVC, pour la vidéo 3D multivue, dans lequel la vue d'amélioration est transportée par un flux qui est différent d'un flux transportant une vue de base, dans lequel chacun de la pluralité des flux vidéo inclus dans le signal de radiodiffusion inclut des paramètres intrinsèques et extrinsèques de caméra pour chaque caméra respectivement ;
    décodage d'une pluralité des flux vidéo en utilisant la SDT ; et
    délivrance en sortie d'images vidéo des flux vidéo décodés comme la vidéo 3D multivue.
  8. Procédé selon la revendication 7, comprenant en outre l'étape d'affichage de la vidéo 3D multivue délivrée en sortie en prenant en considération une position relative de chaque point de vue.
  9. Procédé selon la revendication 7, dans lequel la SDT inclut en outre des informations de vidéo 3D multivue pour convertir les flux vidéo en la vidéo 3D multivue, et les informations de vidéo 3D multivue comprennent au moins un choisi parmi le groupe consistant en le nombre de points de vue, un procédé d'agencement de caméras, une priorité de chaque point de vue, un angle de vue fourni par la vidéo 3D multivue, une distance entre caméras, ou un identifiant d'une caméra différente formant une vidéo 3D ensemble en fonction de chaque point de vue.
  10. Procédé selon la revendication 9, dans lequel les informations de vidéo 3D multivue sont contenues dans la SDT sous une forme d'un descripteur.
  11. Procédé selon la revendication 10, dans lequel, si le nombre de points de vue aptes à être affichés dans un récepteur est inférieur au nombre de points de vue inclus dans le signal de radiodiffusion numérique, la priorité de chaque point de vue filtre une partie d'une pluralité des flux vidéo en fonction de la priorité.
  12. Procédé selon la revendication 6, comprenant en outre :
    l'affichage d'une interface utilisateur de sélection de position pour recevoir une entrée d'utilisateur sélectionnant une position d'un écran ; et
    l'affichage d' une interface utilisateur de sélection de vue 3D pour recevoir une entrée d'utilisateur sélectionnant une vue 3D destinée à être délivrée en sortie à la position de l'écran.
  13. Support lisible par ordinateur comprenant des parties de code qui, lorsqu'elles sont exécutées sur un processeur, configurent le processeur pour mettre en oeuvre toutes les étapes d'un procédé selon l'une quelconque des revendications 7 à 12.
EP11838174.8A 2010-11-02 2011-10-26 Appareil et procédé de réception d'un signal de diffusion numérique Active EP2637412B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US40951510P 2010-11-02 2010-11-02
US41925510P 2010-12-03 2010-12-03
PCT/KR2011/008010 WO2012060569A2 (fr) 2010-11-02 2011-10-26 Appareil et procédé de réception d'un signal de diffusion numérique

Publications (3)

Publication Number Publication Date
EP2637412A2 EP2637412A2 (fr) 2013-09-11
EP2637412A4 EP2637412A4 (fr) 2014-12-24
EP2637412B1 true EP2637412B1 (fr) 2017-08-23

Family

ID=46024911

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11838174.8A Active EP2637412B1 (fr) 2010-11-02 2011-10-26 Appareil et procédé de réception d'un signal de diffusion numérique

Country Status (4)

Country Link
EP (1) EP2637412B1 (fr)
KR (1) KR20140000685A (fr)
CN (1) CN103202025B (fr)
WO (1) WO2012060569A2 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104584547B (zh) * 2012-06-05 2017-03-08 Lg电子株式会社 用于处理3d广播服务的广播信号的方法和装置
JPWO2015037473A1 (ja) * 2013-09-11 2017-03-02 ソニー株式会社 画像処理装置および方法
KR101797504B1 (ko) 2013-10-29 2017-11-15 엘지전자 주식회사 Hevc 기반의 ip 방송 서비스 제공을 위한 방송 신호 송수신 방법 및 장치
CN105657517A (zh) * 2016-02-02 2016-06-08 上海逗屋网络科技有限公司 用于播放多人交互视频的方法及设备
CN105721947B (zh) * 2016-02-02 2019-05-10 上海逗屋网络科技有限公司 提供目标多人交互视频的方法及服务器
CN106791795A (zh) * 2017-01-03 2017-05-31 京东方科技集团股份有限公司 3d视频流的发送方法及发送装置、接收方法及接收装置
CN107645647A (zh) * 2017-09-21 2018-01-30 京信通信系统（中国）有限公司 一种多路音视频传输方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2544447A2 (fr) * 2010-04-02 2013-01-09 Samsung Electronics Co., Ltd. Procédé et appareil d'envoi de contenu de radiodiffusion numérique pour fournir du contenu bidimensionnel et tridimensionnel, et procédé et appareil de réception de contenu de radiodiffusion numérique

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100424401B1 (ko) * 2001-11-02 2004-03-24 전자부품연구원 검색기능을 포함한 3차원 입체영상을 위한 다시점영상통신 시스템
KR100703715B1 (ko) * 2005-05-17 2007-04-06 한국전자통신연구원 다시점 3차원 동영상 송수신 시스템
KR101154051B1 (ko) * 2008-11-28 2012-06-08 한국전자통신연구원 다시점 영상 송수신 장치 및 그 방법
CA2744408C (fr) * 2008-12-18 2014-09-09 Lg Electronics Inc. Procede de reception de diffusion numerique capable d'afficher une image stereoscopique, et appareil de reception de diffusion numerique utilisant un tel procede
WO2010086500A1 (fr) * 2009-01-28 2010-08-05 Nokia Corporation Procédé et appareil de codage et de décodage vidéo
WO2010117129A2 (fr) * 2009-04-07 2010-10-14 Lg Electronics Inc. Emetteur de diffusion, récepteur de diffusion et procédé de traitement de données vidéo 3d de ces émetteur et récepteur
JP4984184B2 (ja) * 2009-04-08 2012-07-25 ソニー株式会社 再生装置および再生方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2544447A2 (fr) * 2010-04-02 2013-01-09 Samsung Electronics Co., Ltd. Procédé et appareil d'envoi de contenu de radiodiffusion numérique pour fournir du contenu bidimensionnel et tridimensionnel, et procédé et appareil de réception de contenu de radiodiffusion numérique

Also Published As

Publication number Publication date
CN103202025A (zh) 2013-07-10
KR20140000685A (ko) 2014-01-03
EP2637412A2 (fr) 2013-09-11
EP2637412A4 (fr) 2014-12-24
WO2012060569A2 (fr) 2012-05-10
WO2012060569A3 (fr) 2012-06-28
CN103202025B (zh) 2016-11-02

Similar Documents

Publication Publication Date Title
EP2439954B1 (fr) Procédé de réception de diffusion numérique fournissant un service d'intégration d'images bidimensionnelles et d'images tridimensionnelles, et dispositif de réception de diffusion numérique utilisant un tel procédé
CN102292997B (zh) 广播接收机及其视频数据处理方法
EP2352302B1 (fr) Procédé de réception de diffusion numérique capable d'afficher une image stéréoscopique, et appareil de réception de diffusion numérique utilisant un tel procédé
EP2637412B1 (fr) Appareil et procédé de réception d'un signal de diffusion numérique
CN102388620B (zh) 广播接收机和三维视频数据处理方法
CA2819141C (fr) Dispositif et procede de reception de signal de diffusion tridimensionnelle a plusieurs vues
CN102484729A (zh) 广播发送器、广播接收器及其3d视频数据处理方法

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130529

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20141126

RIC1 Information provided on ipc code assigned before grant

Ipc: H04N 13/00 20060101AFI20141120BHEP

17Q First examination report despatched

Effective date: 20160614

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170310

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 922478

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170915

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011040963

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20170823

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 922478

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171123

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171124

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171123

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171223

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011040963

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20171123

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20180629

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171026

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171031

26N No opposition filed

Effective date: 20180524

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20171031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171031

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171031

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171026

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171026

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171123

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20111026

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170823

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230905

Year of fee payment: 13