WO2021151375A1 - Transceiving method and transceiving apparatus - Google Patents

Abstract

Provided are a transceiving method and a transceiving apparatus, which facilitate the transceiving of some TLV streams. A receiving apparatus comprises a TLV stream extraction mechanism, an IP obtaining mechanism, and a PLT extraction mechanism. The TLV stream extraction mechanism obtains some TLV streams; the IP obtaining mechanism extracts, from the TLV streams, a TLV packet comprising NTP data, and obtains, from a UDP/IP packet comprised in the TLV packet, an IP address; and the PLT extraction mechanism determines a PLT by using the IP address.

Description

Transceiving method and transceiving device

This application requires the priority of the Japanese patent application filed with the Japanese Patent Office on January 31, 2020, the application number is 2020-015882, the invention title is "Transceiving method, transmitting and receiving device", and the Japanese patent filed on January 31, 2020 Office, the application number is 2020-015885, the title of the invention is "receiving method, receiving device" Japanese patent application priority, the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of the present application relate to a transceiving method and a transceiving device.

Background technique

Regarding advanced broadband digital satellite broadcasting, in order to determine the multicast group including the source IP address of the UDP/IP packet (packet) that transmits the PLT, it is sent and used in the TV receiving device corresponding to the reception. AMT. However, in the part of the TLV stream that the television receiving device outputs to external devices through a high-speed digital interface, etc., under the current standard specifications and operating regulations, the output of AMT is not required. For example, when the signal source of the service is an advanced BS, because there is only one IP data stream for MMTP packet transmission, the packet ID of the MMTP packet is uniquely determined.

In addition, channel settings necessary for setting up a television receiver are usually performed based on AMT information.

Prior technical literature

Non-patent literature

Non-Patent Document 1: ARIBSTD-B392.3 "Regulations on the Operation of Advanced Broadband Digital Satellite Broadcasting"

Non-Patent Document 2: ARIBSTD-B631.9 Edition "Standard Specification for Receiving Devices for Advanced Broadband Digital Satellite Broadcasting"

Summary of the invention

However, when the signal source of the service output through the partial TLV stream is a 110-degree CS, there are multiple IP data streams for MMTP packet transmission. In this case, because the packet ID of the same MMTP packet may be used in different IP data streams, it cannot always be identified if it is not combined with UDP/IP information (hereinafter, only described as IP information). Uniquely determined. Therefore, AMT that indicates IP information such as the source IP address of the UDP/IP packet that transmits the PLT is necessary. As mentioned above, there may be situations where there is a mixture of AMT and non-existence in some TLV streams, and the external device receiving part of the TLV stream needs to correspond to the two situations, etc.

In addition, the transmission interval of AMT is a long 10 seconds, and AMT is used to sequentially receive and scan the full TLV stream in the target broadcast media during channel setting, so it takes time to set the channel.

The problem to be solved by this application is to provide a transceiving method and transceiving device that simplify the transceiving of part of the TLV stream. In addition, another problem to be solved by this application is to provide a receiving method and receiving device for receiving TLV streams at a high speed.

The receiving device of an embodiment of the present application includes a TLV stream extraction mechanism, an IP acquisition mechanism, and a PLT extraction mechanism. The TLV stream extraction mechanism acquires part of the TLV stream, and the IP acquisition mechanism extracts TLV packets including NTP data from the part of the TLV stream. In addition, the IP address is obtained from the UDP/IP packet contained in the TLV packet, and the PLT extraction organization uses the IP address to determine the PLT.

In addition, the receiving device of an embodiment of the present application includes a TLV stream extraction mechanism, an IP address acquisition mechanism, and a PLT extraction mechanism. The TLV stream extraction mechanism receives the broadcast signal based on the MMT/TLV method and acquires the TLV stream. The acquisition mechanism obtains the TLV stream from the TLV The IP address is obtained from the UDP/IP packet containing the NTP data contained in the stream, and the PLT extraction mechanism uses the IP address to determine the PLT.

Description of the drawings

FIG. 1 is a diagram showing an example of a television receiver corresponding to digital broadcasting based on the MMT/TLV method and an electronic device that receives partial TLV streams according to an embodiment;

2 is a block diagram showing an example of the functional structure of a television receiving device corresponding to digital broadcasting based on the MMT/TLV method according to the embodiment;

3 is a block diagram showing an example of the functional configuration of a TLV/MMT separation processing unit in the television receiving device of the embodiment;

4A is a diagram showing an example of a multiplexing structure of TLV streams processed by the television receiving device of the embodiment;

4B is a diagram showing an example of the configuration of each packet stored in the TLV stream of the embodiment;

4C is a diagram showing an example of the header information of the UDP/IP packet stored in the TLV stream of the embodiment;

5 is a block diagram showing an example of the functional configuration of a partial TLV stream generating unit in the television receiving device of the embodiment;

6 is a block diagram showing an example of the functional structure of an electronic device that receives a partial TLV stream according to the embodiment;

FIG. 7 is a block diagram showing an example of the functional structure of a partial TLV stream processing unit of the electronic device of the embodiment;

8A is a flowchart showing an example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment;

8B is a flowchart showing another example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment;

9 is a flowchart showing an example of processing operations of the partial TLV generation unit in the television receiving device of the embodiment;

10 is a flowchart showing an example of processing operations of a partial TLV stream processing unit in the electronic device of the embodiment;

FIG. 11A is a diagram showing the data structure of the AMT of the embodiment;

FIG. 11B is a diagram showing the IP version of the embodiment;

11C is a diagram showing the data structure of the PLT of the embodiment;

FIG. 11D is a diagram showing the reference relationship between PLT and MPT according to the embodiment.

Description of Reference Signs

1...TV receiver, 2A...electronic equipment, 3A...interface, 11...TLV stream extraction unit, 12...TLV/MMT separation processing unit, 13...content output unit, 14...partial TLV stream generation unit, 15...presentation unit, 16... Peripheral functions, 17... System bus, 18... Remote control, 21... Interface unit, 22... Part of the TLV stream processing unit, 23... Decoding processing unit, 24... Content output unit, 25... Prompting unit, 26... Control unit, 120...TLV stream selection processing unit, 121...TLV packet separation unit, 122...TLV-SI extraction unit, 123...NTP extraction processing unit, 124...IP/UDP header decompression unit, 125...IP/UDP packet separation unit, 126... MMTP packet separation unit, 127...MMT-SI extraction unit, 128...service/resource selection control unit, 141...MMT-SI generation unit, 142...MMT-SI update unit, 143...MMTP packet generation unit, 144...IP/UDP Packet generation unit, 145...TLV packet generation unit, 146...TLV packet multiplexing unit, 147...TLV-SI generation unit, 221...TLV packet separation unit, 222...TLV-SI extraction unit, 223...NTP extraction processing unit, 224 ...IP/UDP header decompression unit, 225...IP/UDP packet separation unit, 226...MMTP packet separation unit, 227...MMT-SI extraction unit.

Detailed ways

Hereinafter, embodiments will be described with reference to the drawings.

Implementation

FIG. 1 is a diagram showing an example of a television receiver corresponding to digital broadcasting based on the MMT/TLV method and an electronic device that receives partial TLV streams according to the embodiment.

The television receiving device 1 receives a broadcasting signal of digital broadcasting based on the MMT/TLV method, and obtains content transmitted by the broadcasting signal (or also described as a service). The electronic devices 2A, 2B, 2C (when no special distinction is required, they are called electronic devices 2) have interfaces 3A, 3B, and 3C that can communicate with the television receiving device 1, respectively (when no special distinction is needed, they are called As interface 3), the content sent through the broadcast signal is acquired through the interface 3, and the display output is performed. In addition, in the present embodiment, the number of electronic devices 2 is assumed to be three, but depending on the interface of the television receiver 1, it can be any number of one or more.

The electronic device 2 has the capability (resolution, frame rate, etc.) capable of using all or part of the content transmitted by the television receiving device 1. The electronic device 2 may be, for example, a tablet computer terminal, a monitor, a television receiving device, and the like. In addition, as long as it has an interface capable of communicating with the television receiver 1, the electronic device 2 may also be a smart phone.

The interfaces 3A, 3B, and 3C (referred to as interface 3 if no special distinction is required) are interfaces for data communication between the television receiving device 1 and the electronic device 2, and may be wired or wireless. In addition, as the interface 3, a network conforming to DLNA (registered trademark) (Digital Living Network Alliance) or its extension method may also be used, so that the television receiving device 1 and the electronic device 2 can communicate.

FIG. 2 is a block diagram showing an example of the functional configuration of a television receiving device corresponding to digital broadcasting of the MMT/TLV method according to the embodiment.

The television receiver 1 receives a broadcast signal of digital broadcasting based on the MMT/TLV method, and presents the content transmitted by the broadcast signal to the user from a monitor and a speaker.

The TLV stream extraction section 11 includes a tuner section 111, a demodulation section 112, a descrambling section 113, and a CAS module 114, and receives broadcast signals, and outputs a TLV stream as digital data.

The tuner 111 extracts a signal of a desired frequency band (broadcast channel) from a broadcast signal received through a wired method such as an antenna not shown or through an optical line based on cable broadcast, and performs frequency conversion and the like as necessary, and Output to the demodulation unit 112. The demodulation unit 112 performs demodulation, error correction decoding, etc. on the input broadcast signal, and obtains and outputs digital data in the form of TLV (Type Length Value). The acquired digital data is usually encrypted based on scrambling, and the descrambling unit 113 descrambles the scrambled digital data (scrambling data) and outputs it as a TLV stream. The CAS module 114 holds a secret key and the like required when the descrambling unit 113 descrambles the scrambled data, and provides it to the descrambling unit 113 as needed.

The TLV/MMT separation processing unit 12 obtains encoded asset data (hereinafter referred to as encoded resource data) that constitute various control signals and services (content) from the TLV stream output by the TLV stream extraction unit 11, And output. The TLV/MMT separation processing unit 12 can also convert the input TLV stream into an IP/UDP stream, further into an MMT (MPEG Media Transport) stream, and separate it into coded resource data and SI (as control information data). Signaling Information: Signaling information) data. In addition, the TLV/MMT separation processing unit 12 may separate and output the time information data in the NTP format stored in the IP/UDP format from the TLV stream. In addition, the TLV/MMT separation processing unit 12 may also output the TLV packet (or the extracted TLV stream) extracted from the input TLV stream.

The content output unit 13 decodes the encoded resource data and outputs content data such as sound, image, and text.

The sound decoding unit 131 decodes and plays the encoded sound data in the encoded resource data, and outputs sound content data. The image decoding unit 132 decodes and plays the encoded image data in the encoded resource data, and outputs the image content data.

In addition, the encoded character data in the encoded resource data is decoded and reproduced by a character decoding unit (not shown), and is output as character content data.

The output processing unit 133 adjusts the output time, display method, etc. of the image content data (may include audio content data, text content data, etc.), and outputs it. In addition, the output processing unit 133 may also obtain the NTP data (time information data) output by the TLV/MMT separation processing unit 12, and play a clock synchronization signal to use it for time control.

In addition to the encoded resource data, control data and various commands from the control unit 163 described later may be input to the various decoding units described above. The control data may also be control information related to the broadcast system, such as information related to broadcast programs, control information related to multiplexing of UDP/IP packets. Various decoding units may use SI data to select resource data of the program and content data designated by the control unit 163, and decode the selected resource data to obtain content data.

The partial TLV stream generation unit 14 extracts and edits the resource data and control information data that constitute the selected content (broadcast program) from the TVL stream and MMT stream separated and obtained in the TLV/MMT separation processing unit 12, and generates Part of the TLV stream.

The presentation unit 15 presents the content data output by the content output unit 13 as content to the user. The speaker unit 151 outputs audio content data, text content data, and the like as sounds. The display unit 152 is, for example, a monitor, and displays image content data, text content data, and the like.

The peripheral function 16 includes a user interface unit 161, an interface unit 162, and a control unit 163.

The user interface unit 161 is, for example, a switch, a button, or the like provided in the main body of the television receiver 1, the speaker unit 151, the display unit 152, and the like. The user can also perform various settings and adjustments, such as screen adjustment, volume adjustment, and channel selection, on the television receiving device 1 via the user interface unit 161.

The interface unit 162 is various interfaces between the television receiver 1 and the outside, and may include, for example, infrared communication, mouse, keyboard, Ethernet, DLNA (registered trademark), HDMI (registered trademark), Wifi (registered trademark), and Various wired and wireless communication interfaces such as 5th generation mobile communication (5G). The interface unit 162 includes a communication interface constituted by the interface 3. The interface unit 162 generates frame data corresponding to a predetermined communication protocol for the input digital data, and transmits it based on a medium such as wired or wireless. In addition, it demodulates a signal received through a wired or wireless medium to obtain digital data, and decomposes the frame data in accordance with the communication protocol to output the digital data. The interface unit 162 may also have a function of encrypting and decrypting digital data such as scrambling.

The control unit 163 may also control various functions inside the television receiver 1 based on control signals input from the user interface unit 161, the interface unit 162, and the like.

The system bus 17 is a data transmission path for data exchange between various functions in the television receiving device 1, and is, for example, a serial bus. In addition, the data interaction between various functions in the television receiving device 1 is not limited to the system bus 17, and may be other transmission paths.

The remote control 18 is a remote control attached to the television receiving device 1, and the user can use the remote control 18 to perform various operations on the television receiving device 1. For example, if the user makes an operation designation through the remote control 18, a control command is output from the remote control. The control command is received by the television receiver 1 via the infrared communication of the interface unit 162. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes the received control command, extracts it as control information, and controls various functions in the television receiver 1 based on the control information.

3 is a block diagram showing an example of the functional configuration of a TLV/MMT separation processing unit in the television receiving device of the embodiment.

The TLV/MMT separation processing unit 12 has the function of separating the TLV stream into IP/UDP packets, MMT packets, and into coded resource data and SI data as control information data, and therefore uses the relationship of each stream, packet, data, etc. To illustrate the functional structure.

4A is a diagram showing an example of the multiplexing structure of the TLV stream processed by the television receiving device of the embodiment, which complies with ARIB TR-B392.3 Edition (Volume 5), Volume 4, Advanced Broadband CS Digital Broadcasting SI Operation Regulations 13 chapter.

The display box 50 shows a transponder as a physical layer. The transponder is installed in the CS satellite (Communication Satellite), and outputs the broadcast wave signal of the advanced broadband CS digital broadcast.

The display box 51 shows the layer of the TLV stream sent by the transponder shown in the display box 50.

The display box 52 shows the layer of UDP/IP stored in the TLV stream shown in the display box 51.

The display box 53 shows the TLV-NIT (Network Information Table) stored in the TLV stream shown in the display box 51. TLV-NIT is a part of TLV-SI stored in the TLV stream. The TLV-NIT stores various transponders in the broadcast media, the physical structure of the TLV stream transmitted here, the designated service or which TLV stream the designated content belongs to, and other information used for location resolution of the TLV stream.

The display box 54 shows the AMT (Address Map Table) stored in the TLV stream shown in the display box 51. AMT is also a part of TLV-SI stored in the TLV stream. The AMT stores all the services in the TLV stream and transmits the IP data stream of the PLT (a collection of UDP/IP packets with the same IP protocol type, source and destination IP addresses, and source and destination UDP port numbers). ) IP information such as the source IP address.

The display box 55 shows the flow of UDP/IP packets dedicated to the NTP format transmitted through the layer of the UDP/IP flow shown in the display box 52. The part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as the IP header in some cases). The display box 551 can also be regarded as the payload of the UDP/IP packet, and the NTP data is stored in the display box 551.

The display box 56 shows the layer of MMTP transmitted through the layer of the UDP/IP flow shown in the display box 52.

The display box 57 shows a UDP/IP stream (IP data stream) dedicated to SI data stored in the TLV stream shown in the display box 51. In particular, the part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as the IP header in some cases). In addition, the part of the display frame 57 above the display frame 56 can also be regarded as data transmitted in the form of an MMTP packet as the payload of the UDP/IP packet. Stores and transmits control signal data common to all services in the TLV stream including PLT, that is, content (program).

The display frame 58A, the display frame 58B, and the display frame 58C (referred to as the display frame 58 unless otherwise distinguished) respectively show the UDP/IP stream (IP data stream) of each service stored in the TLV stream. . In particular, the part of the display frame 55 that overlaps the display frame 52 can also be regarded as the header of the UDP/IP packet (also referred to as an IP header in some cases). The upper part of the display frame 58 than the display frame 56 can also be regarded as data transmitted in the form of MMTP packets as the payload of the UDP/IP packet. The UDP/IP stream (IP data stream) of the display frame 58A, the display frame 58B, and the display frame 58C usually stores different services (service 1, service 2, service 3 in the figure), that is, different content (program ) Associated data. The IP information in the UDP/IP stream (IP data stream) in the display frame 58A, the display frame 58B, and the display frame 58C is different, especially the IP address of the respective transmission source is different.

The display box 59 shows the same UDP/IP flow as the display box 58, and particularly shows the UDP/IP flow shared by the service. For example, in the UDP/IP streams of display box 58A, display box 58B, and display box 58C, service 1, service 2, and service 3 are respectively sent, and in the UDP/IP stream of display box 59, service 1, service 2, and Data shared by all or part of service 3 (in the figure, subtitle superimposed MPU is shown). The IP information of the UDP/IP stream in the display frame 59, especially the IP address of the transmission source, is different from the IP address of the transmission source of the UDP/IP stream in the display frame 58A, 58B, and 58C.

Returning to FIG. 3, the functional structure of the TLV/MMT separation processing unit 12 will be described.

For example, when a plurality of TLV streams are transmitted on one transponder, the TLV stream selection processing unit 120 selects a TLV stream in which content (program) designated by the user is transmitted based on the data of TLV-NIT.

The TLV packet separation unit 121 separates the TLV stream output from the TLV stream selection processing unit 120 into TLV-SI data (display box 53, display box 54), and UDP/UDP/ which stores NTP data (display box 55) for each TLV packet. Three systems of IP packets and UDP/IP packets storing MMTP packets (display box 53, display box 54). The TLV packet separation unit 121 divides the TLV stream based on the packet identifier (identifier: packet_type) stored in the header of the TLV stream (or TLV header in some cases), which is not shown, in the TLV stream layer of the display box 51. Divided into 3 systems.

The TLV-SI extraction unit 122 extracts the TLV-NIT and AMT output by the TLV packet separation unit 121, and outputs them.

The NTP extraction processing unit 123 extracts NTP information from the UDP/IP packet in the display frame 55 output by the TLV packet separation unit 121, and outputs it. The extracted NTP information is used to broadcast on the receiver's system clock.

The IP header decompression unit 124 processes the IP header (corresponding to the display box 52) of the UDP/IP packet in the header compression method of the MMTP packet (display box 53 and display box 54) output by the TLV packet separation unit 121. Specifically, there are two types of IP headers attached to MMTP packets: headers including IP information including IP addresses and port numbers (the lower part of Figure 4C, which is also referred to as full header in some cases); and The header that does not contain the IP information (the middle section of FIG. 4C, which is also called the compressed header in some cases). The full-head IP packet is specified to be transmitted at least once every 500 [msec]. The IP header decompression unit 124 uses the full header information received in the past for each UDP/IP packet (IP data stream) that has the same IP information, and converts the UDP/IP packet with a compressed header (sometimes also called To compress the UDP/IP packet), convert it into a full-head UDP/IP packet (also referred to as UDP/IP packet in some cases) and output. Alternatively, it is also possible to output the compressed UDP/IP packet as a series of UDP/IP streams for each IP data stream.

The IP/UDP packet separation unit 125 selects the UDP/IP stream (IP data stream) input from the IP header decompression unit 124, and separates the UDP/IP packet of the selected UDP/IP stream, thereby extracting the MMTP packet, and outputting the MMTP Packet flow (also called MMTP flow in some cases). In more detail, the IP/UDP packet separation unit 125 uses the CID included in the IP header to select a UDP/IP stream (IP data stream). In Figure 4A, the display boxes 57, 58, 59 are transmitting MMTP streams. When the IP/UDP packet separation unit 125 selects to separate the UDP/IP packet, it may also use the IP information stored in the AMT, the IP information stored in the PLT, MPT, etc. obtained in the subsequent processing.

The IP/UDP packet separation unit 125 also outputs in the form of a TLV packet selected from the received TLV packets. The output TLV packet may be a TLV packet input to the IP/UDP header decompression unit 124 (a TLV packet in which a compressed IP packet that has not been converted into a full header is stored).

The MMTP packet separation unit 126 outputs control signal data and coded resource data based on the MMTP stream input from the IP/UDP packet separation unit 125. In FIG. 4A, the image MPU, sound MPU, subtitle MPU, application MPU, and subtitle superimposition MPU of the display frame 58 in the display frame 58 are equivalent to encoding resource data. In addition, the data other than the coded resource data of the display frame 58 and the data of the display frame 57 correspond to control signal data.

The MMT-SI extraction unit 127 extracts and outputs control information such as PLT and MPT based on MMT-SI, which is the control signal data input from the MMTP packet separation unit 126. In the PLT, the packet ID of the MMTP packet of the MPT corresponding to the full service (or content) transmission in the TLV stream (refer to the MMTP packet 63 in FIG. 4B) is stored, and the stored UDP/IP packet is further stored. The IP information, headed by the source IP address, is used to resolve the location of MPT transmission. In the MPT, information for location resolution for resource transmission, such as the packet ID of the MMTP for each resource constituting the service, is stored. The information stored in PLT and MPT may also be used in the IP/UDP packet separation unit 125. In addition, the MMT-SI extraction unit 127 extracts and outputs EPG information and the like from the MMT-SI.

The service/resource selection control unit 128 receives information from each function in the television receiving device 1, and outputs a control signal based on the received information, or extracts and outputs further detailed information. In addition, when the user has issued a control command to the television receiving device 1 via the remote control 18, the control unit 163 outputs the analyzed control command to the service/resource selection control unit 128. The service/resource selection control unit 128 outputs control signals and detailed information to each function in accordance with control commands.

4B is a diagram showing an example of the structure of each packet stored in the TLV stream of the embodiment.

The TLV packet 61 is composed of a header and a payload, and fixed bits, packet_type and length as identifiers are stored in the header.

The UDP/IP packet 62 is composed of an IP/UDP header and an IP/UDP payload. In particular, the identifiers CID, SN, CID_header_type are stored in the IP/UDP header of the header compressed IP packet. The "partial IPv6 header/partial/UDP header" of the IP/UDP header contains header information used in the full header.

The MMTP packet 63 is composed of an MMTP header and an MMTP payload, and a packet_id as an identifier is stored in the MMTP header. The UDP/IP packet 62 is stored in the payload of the TLV packet 61, and the MMTP packet 63 is stored in the IP/UDP payload. Data such as resource data and SI data are stored in the MMTP payload.

4C is a diagram showing an example of the header information of the UDP/IP packet stored in the TLV stream of the embodiment, and is a detailed view of the header information of the UDP/IP packet 62 in FIG. 4B. As shown in Figure 4C, in the header compressed IP/UDP packet, the source IP address (source_address) and the destination IP address (destination_address) are configured in the IP/UDP header. In addition, for a normal IP/UDP packet, the source IP address (source_address) and the destination IP address (destination_address) are arranged in the IP header. NTP transmission does not apply IP header compression, and is usually transmitted at 33msec intervals. MMTP packet transmission uses IP header compression and is transmitted in full headers at 500msec intervals.

The source IP address (source_address) in the NTP dedicated IP data stream and the source address in the SI dedicated IP data stream use the same source IP address (source_address).

Specifically, in the NTP dedicated IP data flow and SI dedicated IP data flow in FIG. 4A, Src.add0 is used as the source IP address, and in the data flow of service 1 in FIG. 4A, the source IP address is used Src.add1, in the data stream of service 2, use Src.add2 as the source IP address, and in the data stream of service 3, use Src.add3 as the source IP address.

Therefore, based on the IP/UDP packet transmission source IP address (source_address) of the NTP dedicated IP data stream, the IP/UDP packet of the SI can be determined from the multiplexed stream.

Fig. 5 is a block diagram showing an example of a functional configuration of a partial TLV stream generating unit in the television receiving device of the embodiment.

The partial TLV stream generating unit 14 of the present embodiment generates not only coded resource data and MMT-SI control signal data, but also generates a TLV packet including NTP data, and outputs it as a partial TLV stream.

The MMT-SI generation unit 141 selects and extracts necessary information from the control information extracted and output by the MMT-SI extraction unit 127, and generates partial control information for the TLV stream based on the extracted information (in separate processing from the TLV/MMT When the control signal data of the section 12 is distinguished, it is referred to as partial control signal data). Specifically, for example, MH-SIT (Selection Information Table) and MH-DIT (Discontinuity Information Table) specified in ARIBSTD-B63. Generally, the control information for partial TLV streams is less than the control information extracted by the MMT-SI extraction unit 127 (that is, the control information for broadcast signal transmission).

The MMT-SI update unit 142 updates the contents of PLT or MPT stored in the payload of the UDP/IP packet (MMTP packet). The PLT included in the TLV stream (TLV stream transmitted by a broadcast signal) output by the TLV stream extraction unit 11 contains information about the full service. When sending as a partial TLV stream, it is necessary to update the PLT to the only included PLT. Information about the specified service. The same applies to MPT. When transmitting as a partial TLV stream, it is necessary to update the MPT to include only the information of the specified resource data.

The MMTP packet generation unit 143 uses the partial control signal data for the TLV stream input from the MMT-SI generation unit 141 as a payload, and adds predetermined MMTP header information to generate and output an MMTP packet.

The IP/UDP packet generation unit 144 outputs the UDP/IP packet input from the MMT-SI update unit 142 as it is. In addition, the MMTP packet input from the MMTP packet generation unit 143 is used as the payload, and the header information of the UDP/IP packet input from the MMT-SI update unit 142 is referred to, while the values of CID and SN are integrated, the IP header, UDP header to generate and output UDP/IP packets.

The TLV packet generating unit 145 adds a TLV header to the UDP/IP packet input from the IP/UDP packet generating unit 144 to generate and output a TLV packet.

The TLV packet multiplexing unit 146 multiplexes TLV packets input from each function, and outputs it as a partial TLV stream. Specifically, a TLV packet containing NTP data, a TLV packet output by the TLV packet generating unit 145, and a TLV packet containing resource data are input to the TLV packet multiplexing unit 146 and output as a partial TLV stream. The partial TLV stream is transmitted from the interface unit 163 as a partial TLV stream signal in accordance with a predetermined communication method.

The TLV-SI generating unit 147 generates TLV-SI information in the mainland including the information of the AMT, and outputs it to the TLV packet multiplexing unit 146. However, in this embodiment, since TLV-SI information is not multiplexed in some TLV streams, this function may not be provided. In addition, for example, it may also be set such that the user can set from the remote control 18 whether the TLV-SI information is included or not included in the partial TLV stream.

6 is a block diagram showing an example of the functional structure of an electronic device that receives a partial TLV stream according to the embodiment.

The electronic device 2 receives part of the TLV stream signal sent by the television receiver 1 through the interface unit 21. The interface unit 21 includes a communication interface constituted by the interface 3. The interface unit 21 extracts digital data from the received partial TLV stream signal and outputs it as a partial TLV stream. The interface unit 21 generates frame data corresponding to a predetermined communication protocol for the input digital data, and transmits it based on a medium such as wired or wireless. In addition, it demodulates signals received through wired, wireless and other media to obtain digital data, and decomposes the frame data corresponding to the communication protocol, and outputs the digital data. The interface unit 21 may also have encryption and decryption functions such as scrambling. The interface unit 21 in this embodiment can communicate with the interface unit 162 based on, for example, DLNA (registered trademark) or its extended method.

The partial TLV stream processing unit 22 processes the partial TLV stream input from the interface unit 21, and obtains and outputs coded resource data and SI data. The coded resource data is input to the decoding processing unit 23 together with the SI data, and converted into content data such as images, sounds, and texts. The converted content data is output to the content output unit 24. The content output unit 24 adjusts the output time, display method, etc. of the content data, and outputs to the presentation unit 25.

The presentation unit 25 is, for example, a signal display device (monitor), a speaker, etc., and outputs as images, audio, text, etc. based on the input content data.

The control unit 26 controls each function of the electronic device 2. For example, the control unit 26 performs connection establishment of external communication via various interfaces including the interface unit 21.

In addition, in FIG. 6, data interaction (including control) can also be performed between functional modules that are not connected to the control unit 26.

FIG. 7 is a block diagram showing an example of the functional configuration of a partial TLV stream processing unit of the electronic device according to the embodiment.

The functional structure of part of the TLV stream processing unit 22 in FIG. 7 is explained using the data layer of the TLV stream in FIG. 4A.

The partial TLV stream processing unit 22 separates the partial TLV stream into IP/UDP packets and MMT packets, and obtains and outputs coded resource data and SI data as control signal data. The function of the partial TLV stream processing unit 22 is the same as the function of the TLV/MMT separation processing unit 12 of the television receiver 1.

The TLV packet separation unit 221 separates the part of the TLV stream input from the interface unit 21 into TLV-SI data (equivalent to display box 53 and display box 54 in FIG. 4A), and stores NTP data (equivalent to display box 55) UDP/IP packets and UDP/IP packets storing MMTP packets (equivalent to display box 56) are three systems. The TLV packet separation unit 221 divides the partial TLV stream into three systems based on the packet identifier (identifier: packet_type) stored in the TLV header (refer to the TLV packet in FIG. 4B) in the TLV stream layer of the display box 51.

If the TLV-SI output by the TLV packet separation unit 221 exists, the TLV-SI extraction unit 222 may also extract and output necessary information from the TLV-SI. However, in this embodiment, because TLV-SI is not required, and usually TLV-SI is not included in part of the TLV stream, this function may not be available.

The NTP extraction processing unit 223 extracts and outputs NTP data from the UDP/IP packet in the display frame 55 output from the TLV packet separation unit 221. In addition, the NTP extraction processing unit 223 extracts the IP address of the transmission source of the NTP data from the UDP/IP packet in which the NTP data is stored.

The IP header decompression unit 224 processes the IP header (equivalent to the display box 52) of the UDP/IP packet in the header compression format of the MMTP packet (equivalent to the display box 56) output by the TLV packet separation unit 221. Specifically, there are two types of IP headers attached to MMTP packets: headers including IP information including IP addresses and port numbers (or full headers in some cases); and headers that do not include IP information ( In some cases, it is also called compression header). The IP header decompression unit 224 uses the information of all IP headers received in the past for each UDP/IP packet (IP data stream) with the same IP information to convert the UDP/IP packet with a compressed header (or in some cases) Called compressed UDP/IP packets) are converted into full-headed UDP/IP packets (also called UDP/IP packets in some cases), and output. Or, according to each IP data stream, the compressed UDP/IP packet can be output as a series of UDP/IP streams.

The IP/UDP packet separation unit 225 separates the UDP/IP packet input from the IP header decompression unit 224, extracts the MMTP packet, and outputs a stream of MMTP packets (also referred to as an MMTP stream in some cases). When the IP/UDP packet separation unit 225 in this embodiment selectively separates UDP/IP packets, it uses the IP address information stored in the UDP/IP packet that transmits NTP, and the PLT, MPT, etc. obtained in the subsequent processing. Information stored in.

The MMTP packet separation unit 226 outputs control signal data and coded resource data based on the MMTP stream input from the IP/UDP packet separation unit 225.

The MMT-SI extraction unit 227 extracts and outputs control information such as PLT and MPT from MMT-SI, which is the control signal data input from the MMTP packet separation unit 226. The information stored in PLT and MPT may also be used in the IP/UDP packet separation unit 225.

An operation example of the system of this embodiment will be described. 8A is a flowchart showing an example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment. Fig. 8B is a flowchart showing another example of the processing operation of the TLV/MMT separation processing unit in the television receiving device of the embodiment.

In FIG. 8A, in order to specify a service (content) for output as a partial TLV stream from the television receiving apparatus 1, the user performs a specified operation through the remote control 18. The remote control 18 outputs a control command for specifying a service, and the interface unit 162 of the television receiver 1 receives the control command. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes the control command to extract information (designated service information) of the service designated by the user, and outputs it to the service/resource selection control unit 128. The service/resource selection control unit 128 outputs the designated service information (service_id) to the TLV/MMT separation processing unit 12 (step S11). In the TLV/MMT separation processing unit 12, the TLV stream selection processing unit 120 selects the TLV stream storing the designated service based on the TLV-NIT extracted by the TLV-SI extraction unit 122 and the designated service information, and outputs it to the TLV packet separation Section 121 (Step S12).

The TLV packet separation unit 121 separates the TLV stream input from the TLV stream selection processing unit 120 into three systems based on the packet identifier (identifier: packet_type) stored in the header shown in the TLV packet 61 of FIG. 4B (step S13). Specifically, according to the different types of data stored in the payload of the TLV packet, it is separated into three types: TLV-SI data, UDP/IP packet storing NTP data, and header compressed UDP/IP packet storing MMTP packet. System, and input to the TLV-SI extraction unit 122, the NTP extraction processing unit 123, and the IP header decompression unit 124, respectively.

The TLV-SI extraction unit 122 extracts TLV-NIT data and AMT data, and outputs them to the service/resource selection control unit 128 (step S14). The NTP extraction processing unit 123 extracts the NTP data stored in the UDP/IP packet, and outputs it to the service/resource selection control unit 128 (step S15). At the same time, the NTP extraction processing unit 123 outputs the input TLV packet as it is (step S15). The TLV packet including the header compressed UDP/IP packet in which the MMTP packet is stored is input to the IP header decompression unit 124 and the IP/UDP packet separation unit 125 and processed (step S16). The IP/UDP packet separation unit 125 uses the CID of the IP header information of the input TLV packet (refer to UDP/IP packet 62 in FIG. 4B) and the IP information input from the service/resource selection control unit 128 to confirm the IP data flow (step S17). The correspondence between the input IP information and the CID can be judged by comparing with the IP information recorded in the full header. If it is not confirmed that the IP data stream is an IP data stream selected based on the IP information, the next TLV packet is confirmed (No in step S18, S13). If it is confirmed that the IP data stream is the IP data stream selected based on the IP information, the subsequent processing is performed (Yes in step S18). The TLV packet of the selected IP data stream is input to the MMTP packet separation unit 126, and the packet_id of the MMTP header is confirmed (step S19). The MMTP packet separation unit 126 confirms the packet_id, and when the selected MMT-SI is stored in the input TLV packet, that is, when the PLT, the MPT related to the service_id specified by the user, and the specified MMT-SI are stored Next, output the UDP/IP packet stored in the input TLV packet (Yes in step S20, S21). The MMTP packet separation unit 126 confirms packet_id, and if the selected MMT-SI is not stored in the input TLV packet, it confirms whether the selected resource is stored in the input TLV packet (No in S20, step S22) . The MMTP packet separation unit 126 extracts the MPT of service_id that identifies the service selected by the user from the PLT of the MMT-SI extracted in step S20. The MMTP packet separation unit 126 can specify the resources constituting the service specified by the user based on the extracted information of the MPT. The MMTP packet separation unit 126 confirms the MPT information of the MMT-SI extracted in step S20 and the packet_id of the input TLV packet, and if the selected resource is stored in the input TLV packet, that is, in the storage When there is a resource of service_id specified by the user, the input TLV packet is output (Yes in step S22, step S23). In step S23, the TLV packet output by the MMTP packet separation unit 126 is the TLV packet input to the IP header decompression unit 124. On the other hand, the MMTP packet separation unit 126 confirms the MPT information of the MMT-SI extracted in step S20 and the packet_id of the input TLV packet, and if the selected resource is not stored in the input TLV packet, The TLV packet is discarded (step S24).

In addition, steps S18 to S20 of the above-mentioned flow are supplemented. First, in order to obtain PLT, determine the IP information of the SI dedicated IP data stream based on the information of the AMT and select the IP information. Since the packet_id of the PLT is fixed at 0x0000 (fixed value), the PLT can be extracted through the processing of the MMTP packet separation unit 126 and the MMT-SI extraction unit 127.

Next, based on the acquired PLT, the IP information of the IP data stream to be transmitted to the MPT of the service specified by the user is determined, and the IP information is selected. Since the packet_id of the MPT is also described in the PLT, the MPT can be extracted through the processing of the MMTP packet separation unit 126 and the MMT-SI extraction unit 127. In addition, because each resource constituting the service is also included in the same IP data stream, and each packet_id is also described in the MPT, the resource can be extracted through the processing of the MMTP packet separation unit 126.

In addition, as needed, refer to the MPT to determine the IP information of the service common IP data stream, and select the IP information. Since this IP information and packet_id are also described in the MPT, the resource can be extracted through the processing of the MMTP packet separation unit 126. The step S20 of the above-mentioned flow will be described in detail. The MMTP packet separation unit 126 extracts and outputs control signal data from the input TLV packet, UDP/IP header analysis information, and the like. The output control signal data is input to the MMT-SI extraction unit 127, and the MMT-SI extraction unit 127 receives from the service/resource selection control unit 128 IP information such as the IP address of the designated service source stored in the AMT, and based on the received Information to extract PLT. The MMT-SI extraction unit 127 outputs the extracted PLT to the service/resource selection control unit 128. Furthermore, the MMT-SI extraction unit 127 extracts MPT based on the extracted PLT. The step S22 of the above-mentioned flow will be described in detail. The MMT-SI extraction unit 127 outputs the extracted MPT to the service/resource selection control unit 128. The MMTP packet separation unit 126 extracts encoded resource data from the input MMTP packet (TLV packet) based on the extracted MPT.

In addition, in FIG. 8B, in order to designate the start of scanning from the television receiving device 1, the user performs a designation operation through the remote control 18. The remote control 18 outputs a control command for specifying a service, and the interface unit 162 of the television receiver 1 receives the control command. The interface unit 162 outputs the received control command to the control unit 163, and the control unit 163 analyzes the control command to extract information (designated service information) of the service designated by the user, and outputs it to the service/resource selection control unit 128. The service/resource selection control unit 128 outputs the designated service information (service_id) to the TLV/MMT separation processing unit 12 (step S11). In the TLV/MMT separation processing unit 12, the TLV stream selection processing unit 120 selects a TLV stream and outputs it to the TLV packet separation unit 121 (step S12).

The TLV packet separation unit 121 separates the TLV stream input from the TLV stream selection processing unit 120 into three systems ( Step S13). Specifically, they are separated into three systems: TLV-SI data, UDP/IP packets storing NTP data, and UDP/IP packets storing MMTP packets, and input to the TLV-SI extraction unit 122 and the NTP extraction processing unit, respectively. 123. In the IP header decompression unit 124.

The TLV-SI extraction unit 122 extracts TLV-NIT data. In addition, the NTP extraction processing unit 123 extracts the NTP data from the IP header of the UDP/IP packet in which the NTP data is stored, and extracts the transmission source IP address of the NTP data from the header information of the UDP/IP packet (step S14). The operating regulations stipulate that the source IP address of the NTP data is the same as the source address of the UDP/IP packet of the dedicated IP data stream that transmits the SI data (control information data) of the PLT, and the other IP information is a fixed value. Therefore, the IP address of the SI dedicated IP data stream that transmits the PLT is determined (step S15). In this way, all services in the TLV stream can be received, and all TLV streams in the media (network) are sequentially executed based on the information of the TLV-NIT, thereby enabling scanning processing.

FIG. 9 is a flowchart showing an example of the processing operation of the partial TLV generation unit in the television receiving device of the embodiment.

In the partial TLV stream generating unit 14, the TLV packet of the resource data is input to the TLV packet multiplexing unit 146 (step S101). In the partial TLV stream generating unit 14, the control signal data is input to the MMT-SI generating unit 141. The MMT-SI generating unit 141 generates partial control signal data for output included in the partial TLV stream, namely MH-SIT, MH-DIT, etc., and outputs it to the MMTP packet generating unit 143 (step S102A). In addition, PLT and MPT in the control signal data input to the partial TLV stream generation unit 14 are input to the MMT-SI update unit 142, and the content is updated as necessary, and is output to the IP/UDP packet generation unit 144 (step S102B). The partial TLV stream generating unit 14 inputs the received TLV packet storing the NTP data to the TLV packet multiplexing unit 146 (step S103).

The MMTP packet generating unit 143 converts the input partial control signal data into an MMTP packet, and outputs it to the IP/UDP packet generating unit 144 (step S104). Here, when distinguishing from the MMTP packet input to the MMTP packet separation unit 126, the MMTP packet output in step S104 is referred to as a partial MMTP packet. The IP/UDP packet generation unit 144 adds an IP header, a UDP header, etc. to the input partial MMTP packet, generates a UDP/IP packet, and outputs the UDP/IP packet to the TLV packet generation unit 145 (step S105). In addition, in step S102B, the UDP/IP packet input from the MMT-SI update unit 142 is output as it is (step S105). When distinguishing from the UDP/IP packet input to the IP/UDP packet separation unit 125, the UDP/IP packet output in step S105 is referred to as a partial UDP/IP packet.

Part of the UDP/IP packet is input to the TLV packet generating unit 145, and the TLV packet generating unit 145 uses the part of the UDP/IP packet as a payload and adds necessary TLV-SI and TLV headers to generate a TLV packet (step S106). When distinguishing from the TLV packet input to the TLV packet separation unit 121, the TLV packet output in step S106 is referred to as a partial TLV packet. The generated part of the TLV packet, the resource data obtained in step S101A and step S103, and the TLV packet including NTP are input to the TLV packet multiplexing unit 146. The TLV packet multiplexing unit 146 outputs the input TLV packet as a partial TLV stream. From the interface unit 162 via the interface 3, a communication method such as DLNA (registered trademark) or an extended method is used to output the partial TLV stream as a partial TLV stream signal (step S107).

10 is a flowchart showing an example of processing operations of a partial TLV stream processing unit in the electronic device of the embodiment.

In the electronic device 2, part of the TLV stream signal output from the television receiver 1 is received through the interface unit 21. The interface unit 21 obtains the partial TLV stream by performing processing such as demodulation on the partial TLV stream signal. The obtained partial TLV stream is input to the TLV packet separation unit 221 of the partial TLV stream processing unit 22 (step S201). The TLV packet separation unit 221 divides the part of the TLV stream into a stream of TLV-SI data, UDP/IP packets of NTP data, and a stream of MMTP packets stored in the TLV header based on the packet identifier (identifier: packet_type) stored in the TLV header of the partial TLV stream. UDP/IP packet flow and other systems (step S202). The TLV-SI data is input to the TLV-SI extraction unit 222, and the TLV-SI extraction unit 222 extracts data necessary for processing part of the TLV stream. In addition, in the example of this embodiment, TLV-SI data is not included in some TLV streams.

The UDP/IP packet of the NTP data is input to the NTP extraction processing unit 223, and the NTP extraction processing unit 223 extracts the NTP data (step S203). In addition, the NTP extraction processing unit 223 extracts the transmission source IP address of the NTP data from the IP header of the UDP/IP packet storing the NTP data (step S204). While performing steps S203 and S204, the UDP/IP stream storing the MMTP packet is input to the IP header decompression unit 224 and converted into a full-head UDP/IP packet. The converted full-head UDP/IP packet is input to the IP/UDP packet separation unit 225, and the IP/UDP packet separation unit 225 extracts the MMTP packet, and outputs it to the MMTP packet separation unit 226 (step S205). The MMTP packet separation unit 226 inputs, among the input MMTP packets, an MMTP packet with an IP header storing an IP address that matches the source IP address of the NTP data, to the MMT-SI extraction unit 227 (step S206). Through step S206, the UDP/IP packet of the dedicated IP data stream for SI data (control information data) is extracted. In more detail, the operating regulations stipulate that the source IP address of the NTP data is the same as the source address of the UDP/IP packet of the dedicated IP data stream that transmits the SI data (control information data) of the PLT. Other IP information It is a fixed value. Therefore, it is possible to extract the PLT by extracting the MMTP packet with the packet_id of 0x0000 attached with the IP header that matches the source IP address of the NTP data. In addition, in the selection of the IP data stream dedicated to the transmission of the SI data (control information data) of the PLT, it is also possible to use AMT instead of the above-mentioned IP header of the UDP/IP packet storing the NTP data. Therefore, the partial TLV stream processing unit 22 may also use the IP header of the UDP/IP packet storing the NTP data when the AMT cannot be detected from the received partial TLV stream.

The MMT-SI extraction unit 227 extracts PLT from the input MMTP packet (step S207). In more detail, the packet ID is used to extract the PLT from the UDP/IP packet dedicated to the desired SI data extracted in step S206.

Furthermore, the MMT-SI extraction unit 227 extracts the MPT based on the information described in the extracted PLT (step S208). The MMTP packet separation unit 226 extracts coded resource data from the input MMTP packet based on the extracted MPT (step S209). The extracted encoded resource data is output to the content output unit 24 (step S210).

The content output unit 24 decodes the encoded resource data, etc., and outputs content data such as sound, image, and text (step S210). The output content data is presented to the user as content such as images, sounds, texts, etc. from a speaker or a monitor in the presentation unit 25 (step S211).

According to the above sequence, the electronic device 2 receives part of the TLV stream sent by the television receiver 1, and the user can use the electronic device 2 to watch the content. In this embodiment, the television receiver 1 as the source device transmits part of the TLV stream in a manner that does not include the AMT storing the source IP address of the SI dedicated IP data stream. However, the electronic device 2 passes from the storage The IP header information of the NTP UDP/IP packet included in the part of the TLV stream takes out the source IP address of the SI dedicated IP data stream, so that the content data sent using the part of the TLV stream can be obtained. In the specification of advanced broadband digital satellite broadcasting, it is not necessary to include AMT in some TLV streams. Therefore, there will be cases where AMT exists and there is no AMT in some TLV streams. According to this embodiment, regardless of the presence or absence of AMT in the partial TLV stream, the reception and playback process of the service can be performed during the reception and playback process of inputting the corresponding partial TLV stream.

In addition, in the electronic device 2 that receives part of the TLV stream, it is possible that the AMT-compatible situation and the non-AMT-compatible situation may occur. According to this embodiment, even in such a case, it is possible to use an electronic device that does not have an AMT-related function installed to receive a part of the TLV stream.

According to the above processing, it is possible to detect whether the television receiver 1 is receiving the TLV stream of the designated channel (program). Generally, in the specifications of advanced-width digital satellite broadcasting, the AMT contained in the TLV stream is used to determine the channel. This is because compared with the sending interval of AMT (10 seconds), the sending interval of NTP (33msec) is very short. According to this embodiment, by using the IP address of NTP, it is possible to detect the designated channel at a higher speed. In addition, the time required for it can be greatly shortened.

In addition, the present embodiment describes the reception processing in the advanced width CS, but also in the advanced width BS, the IP address of the IP data stream transmitting the PLT can be specified without relying on AMT, and the scanning processing can be executed at a high speed.

Below, AMT and PLT related to the above-mentioned embodiment are shown. Based on ARIBSTD-B60.

FIG. 11A is a diagram showing the data structure of the AMT according to the embodiment. The data included in the AMT is shown together with the number of bits and the data flag in each row. The content of each data is as follows.

·Table_id (table ID): set to 0xFE, which means that the table is identified according to the extended value of the table ID.

· Section_syntax_indicator (segment syntax indicator): set to "1" indicating the extended form.

Section_length (section length): specifies the number of bytes from the end of the section length field to the last section including CRC_32.

·Table_id_extension (table identification extension): set to 0x0000 representing the address mapping table.

· Version_number (version number): set to the area of the version number written to the table. Add 1 when the information in the table changes. When its value becomes 31, it returns to 0 next time.

·Current_next_indicator (current follow-up indication): In the case of "1", it means that the table is currently valid. In the case of "0", it means that the sent table has not been applied yet, and it is a scheduled table that becomes effective next.

·Section_number (section number): indicates the number of the section. The segment number of the first segment is 0x00. Each time a segment with the same table ID and table ID extension is added, the segment number is increased by 1.

Last_section_number (final section number): Specifies the number of the last section (ie, the section with the largest section number) of the table to which the section belongs.

·Num_of_service_id (number of service IDs): indicates the number of service_id described in the address mapping table.

·Service_id (service identification): plays the role of a label used to identify the service. It has the same function as the service ID described in the service catalog descriptor.

·Ip_version (IP version): Indicates the version of the IP package described in the directory, which is coded according to Table 5-3.

FIG. 11B is a diagram showing the IP version of the embodiment.

When the IP version is 0, it means IPv4, and when the IP version is 1, it means IPv6.

·Service_loop_length (service loop length): represents the bytes from after this field to before the next service identification field.

·Src_address_32 (send source IPv4 address): Describe the source IP address of the IPv4 packet that constitutes the service.

·Src_address_mask_32 (sender IPv4 address mask): For the IP address specified in the sender IPv4 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 32.

·Dst_address_32 (destination IPv4 address): Describe the destination IP address of the IPv4 packet that constitutes the service.

·Dst_address_mask_32 (destination IPv4 address mask): For the IP address specified in the destination IPv4 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 32. In addition, the multicast group that constitutes the service is set to both the source IPv4 address recognized as valid based on the source IPv4 address mask and the destination IPv4 address recognized as valid based on the destination IPv4 address mask. The address matches the multicast group.

·Src_address_128 (sender IPv6 address): Describe the source IP address of the IPv6 packet that constitutes the service.

·Src_address_mask_128 (sender IPv6 address mask): For the IP address specified in the sender IPv6 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 128.

·Dst_address_128 (destination IPv6 address): Describe the destination IP address of the IPv6 packet that constitutes the service.

·Dst_address_mask_128 (destination IPv6 address mask): For the IP address specified in the destination IPv6 address, specify the number of bits from the beginning (MSB) that becomes valid. Cannot take a value greater than 128. In addition, the multicast group that constitutes the service is set to both the source IPv6 address recognized as valid based on the source IPv6 address mask and the destination IPv6 address recognized as valid based on the destination IPv6 address mask. The address matches the multicast group.

·Private_data_byte: store individually defined data.

CRC_32(CRC): set to comply with ITU-T recommendation H.222.0.

FIG. 11C is a diagram showing the data structure of the PLT (Package Table of Contents) according to the embodiment. The data included in the PLT is shown in each row together with the number of bits and the data flag. PLT shows a list of IP data streams and packet IDs for transmitting PA messages of MMT packets provided as broadcast services, and a list of IP data streams for transmitting IP services. The descriptor stored in the PLT is set to the descriptor specified in the specification.

The contents of each data included in the PLT are as follows.

· Num_of_package (number of packages): indicates the number of packages that record location information in this table.

·MMT_package_id_length (package ID length): Express the length of package ID bytes in byte units.

·MMT_package_id_byte (package ID byte): indicates the package ID.

· MMT_general_location_info (location information): Represents the location information for transmitting the PA message of the package indicated by the package ID.

·Num_of_ip_delivery (number of IP release streams): indicates the number of IP services with location information recorded in this table.

·Transport_file_id (transport file ID): represents a label used to uniquely identify the file to be transferred.

·Location_type (location type): indicates the type of location information. 0x01 means IPv4 data flow, 0x02 means IPv6 data flow, and 0x05 means URL.

·Ipv4_src_addr (send source IPv4 address): indicates the source address of the IPv4 data stream.

·Ipv4_dst_addr (destination IPv4 address): Represents the destination address of the IPv4 data flow.

·Dst_port (destination port number): Represents the destination port number of the IP data stream.

·Ipv6_src_addr (send source IPv6 address): indicates the source address of IPv6 data flow.

·Ipv6_dst_addr (destination IPv6 address): Represents the destination address of the IPv6 data flow.

URL_length (URL length): indicates the bytes of the URL when the location information is indicated by the URL.

·URL_byte (URL byte): Represents the URL of the IP service.

· Descriptor_loop_length (descriptor length): represents the full bytes of the following descriptor.

Descriptor (descriptor area): Set as an area for the descriptor that shows the detailed information of the IP service.

FIG. 11D is a diagram showing the reference relationship between PLT and MPT according to the embodiment.

The MMTP packet with a packet ID of 0x0000 indicates the transmission of a PA message (the PA message shown on the left side of FIG. 11D). When multiple packets are multiplexed, the PA message includes a packet directory table (PLT). The package list table provides a list of package IDs of MMTP packages that transmit PA messages including MPTs of other packages. Therefore, by parsing the package directory table, it is possible to specify the MMTP package that transmits the PA message including the MPT as the entry point of the service based on the package ID.

According to the above-mentioned embodiments, there is provided a transceiving method and transceiving device that make the transceiving of partial TLV streams easy. In addition, according to the above-mentioned embodiments, there is provided a receiving method and a receiving device capable of receiving TLV streams at a high speed.

Although several embodiments of the present application have been described, these embodiments are shown as examples and are not intended to limit the scope of the application. These new embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the scope of the application. These embodiments and their modifications are included in the scope and gist of the application, and are included in the application described in the scope of protection and the equivalent scope thereof. In addition, among the constituent elements of the technical solution, even when the constituent elements are expressed by dividing them, or by combining a plurality of them, or by combining them, they belong to the scope of the present application. In addition, a plurality of embodiments may be combined, and examples constructed by the combination also belong to the scope of the application.

In addition, in some cases, the drawings schematically show the width, thickness, shape, etc. of each part in comparison with the actual form in order to make the description clearer. In the block diagram, data and signals are exchanged between modules that are not connected or even if they are connected without showing the direction of the arrow. The functions shown in the block diagrams, the processes shown in the flowcharts, and the sequence diagrams can also be realized by hardware (IC chip, etc.) or software (programs, etc.) or a combination of hardware and software. In addition, when the technical solution is expressed as control logic, when it is expressed as a program containing instructions to be executed by a computer, and when it is expressed as a computer-readable storage medium in which the instructions are recorded, it can also be expressed Apply the device of this application. In addition, there are no limitations on the names and terms used, and even if they are other expressions, if they have substantially the same content and the same subject, they are also included in this application.

Claims (9)

1. A sending device, wherein the sending device includes:

   TLV stream extraction mechanism, which receives broadcast signals based on the MMT/TLV method to obtain TLV streams;

   NTP extraction mechanism, which extracts TLV packets including NTP data from the TLV stream; and

   A partial TLV stream generating mechanism, which generates a partial TLV stream in a manner that includes the TLV packet.
2. The transmitting device according to claim 1, wherein:

   The partial TLV stream generation mechanism makes the partial TLV stream not include AMT data.
3. The transmitting device according to claim 2, wherein:

   The sending device is provided with a setting mechanism capable of setting whether the partial TLV stream includes AMT data,

   The partial TLV stream generating mechanism generates the partial TLV stream based on the setting content from the setting mechanism.
4. A method for sending partial TLV streams, in which,

   Extract the TLV packet including the NTP data from the TLV stream, and generate a part of the TLV stream by including the TLV packet.
5. A device for receiving a partial TLV stream, the partial TLV stream is a partial TLV stream generated from a TLV stream obtained by receiving a broadcast signal based on the MMT/TLV mode, wherein,

   The receiving device includes:

   An obtaining mechanism, which obtains IP information including an IP address from a UDP/IP packet including NTP data included in the partial TLV stream; and

   A PLT extraction agency that uses the IP information to determine the PLT.
6. The receiving device according to claim 5, wherein:

   If there is no AMT in the part of the TLV stream, the obtaining mechanism obtains the IP information including the IP address from the UDP/IP packet including the NTP data.
7. A method for receiving a partial TLV stream, wherein the partial TLV stream is a partial TLV stream generated from a TLV stream obtained by receiving a broadcast signal based on the MMT/TLV method,

   Obtain the IP information including the IP address from the UDP/IP packet including the NTP data, the NTP data included in the partial TLV stream,

   The IP information is used to determine the PLT.
8. A receiving device, wherein the receiving device includes:

   TLV stream extraction mechanism, which receives broadcast signals based on the MMT/TLV method and obtains TLV streams;

   An obtaining organization, which obtains an IP address from a UDP/IP packet contained in the TLV stream, where the UDP/IP packet contains NTP data; and

   The PLT extraction agency, which uses the IP address to determine the PLT.
9. A method for receiving TLV streams, in which,

   Receive broadcast signals based on the MMT/TLV method and obtain TLV streams;

   Obtaining an IP address from a UDP/IP packet contained in the TLV stream, where the UDP/IP packet contains NTP data;

   The IP address is used to determine the PLT.

Images