JP2005071330A - Information processor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processor capable of controlling setting of an information delivery route between devices from a program (an application program). <P>SOLUTION: A device manager 2205f of a broadcast receiver has: a device basic information management part 3201 holding the number and the kinds of the devices dealt by the device manager 2205f, and information about the device itself; a device object management part 3202 managing one-to-one correspondence of the device and an object expressing the device; a device physical connection management part 3203 managing physical connection information about the device in a hardware configuration; a device logical connection management part 3204 managing a logical connection state of the device; a device logical connection part 3205 logically connecting the device; and a device logical connection release part 3206 releasing the logical connection of the device. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus that executes a program. In particular, the present invention relates to a mechanism for executing a program that uses a plurality of devices unique to the broadcast receiving apparatus in the broadcast receiving apparatus.

  On the hardware of a broadcast receiving apparatus represented by a television or STB (Set Top Box), a plurality of devices having different functions are connected to each other so that the other output becomes the other input, and a series of “information” A configuration that realizes a large function by forming a "passing path" is adopted. For example, in the case where video / audio is output to a screen by a digital broadcast receiving device, for example, on hardware, a broadcast signal is input, and filtering is performed using tuning information such as frequency as a key to perform MPEG2 (Motion Picture Expert Group). -2) “Tuner device” that outputs a transport stream, and inputs an MPEG2 transport stream, selects an MPEG2 transport stream packet (hereinafter referred to as TS packet) that transmits desired video / audio, and matches the TS “TS decoder device” that outputs a PES (Packetized Elementary Stream) packet containing video and audio data that the packet transmits, and the PES packet as an input "AV decoder devices" that decode video and audio data and output them in a screen displayable state are connected in the order described to form a series of "information transfer paths", and each device performs its function Enables video / audio to be displayed on the screen.

In such a broadcast receiving apparatus, there may be a plurality of devices of the same type in order to parallelize processing. For example, there are two tuner devices and two AV decoder devices, which are connected to the TS decoder device, and the TS decoder device can establish an "information passing path" with any combination of multiple tuner devices and AV decoder devices. In the case of having such a capability, an “information passing path 1” is established between the tuner device A and the AV decoder device A across the TS decoder device, and the TS decoder device is connected between the tuner device B and the AV decoder device B. It is possible to establish “Information Passing Path 2” with In such a case, the “information transfer path 1” and the “information transfer path 2” are capable of demodulating an MPEG2 transport stream from a broadcast signal completely independently of each other and simultaneously decoding a plurality of video / audio data. It becomes possible to realize a function called “Picture In Picture (hereinafter referred to as PIP)” for simultaneously displaying two types of video and audio on one screen. In such a device, it is not always necessary to realize PIP, and it is usually possible to switch between single video screen display and PIP display by a user's remote control input or the like. For example, Patent Document 1 is given as a representative example of a method of using each device in such a case. The present invention devised a method for realizing PIP in a broadcast receiving apparatus having two tuner devices, one AV decoder, and one PIP data processing device. In this invention, the two tuners are positioned as “main tuner” and “insert screen tuner”, and the PIP display uses the “insert screen tuner” to display the already selected video / audio over the entire screen. The video / audio of the selection candidate can be output to a designated area on the screen.
JP-A-8-289220

  Currently, a specification called DVB-MHP (Digital Video Broadcasting-Multimedia Home Platform) for operating an application on a broadcast receiving apparatus has been defined in Europe and has already been started. On the other hand, in the United States, the OCAP (OpenCable Application Platform) specification is being formulated based on the DVB-MHP specification, and the operation is scheduled to start in FY2005. Similar specifications are being developed and used in other countries. A broadcast receiving device that complies with such an application execution specification has a function of executing a program obtained using a technique such as downloading from a broadcast signal. A typical example of such a program is a game or an EPG (Electrical Program Guide) application.

  As a program to be executed on a broadcast receiving apparatus capable of executing the program, an application that simultaneously displays a plurality of video / audio on one screen, such as the above-described PIP and high function EPG, is naturally assumed. In order to simultaneously output multiple images / audio on one screen, as represented by the example described in the above-mentioned patent, it is necessary to appropriately control multiple devices, especially the setting of “information transfer route” for each device. There is a need to do. The OCAP / DVB-MHP API (Application Program Interface) already has functions for individually operating a tuner device, a TS decoder device, an AV decoder device, etc., and it is not possible to implement such an application at present. Not possible. However, the current specification does not have a function for setting an “information passing path” between devices. For example, it is impossible to specify that an “information passing path” is established between a tuner device A of a plurality of tuner devices and a TS decoder device B of a plurality of TS decoder devices. . In the OCAP / DVB-MHP, for example, when outputting video / audio, first, tuning information such as frequency is given to the tuner device, and the MPEG2 transport stream transmitting the video / audio to be output is set to be demodulated. Next, an identifier of video / audio to be output to the AV decoder is set. Then, a program called “middleware” (hereinafter referred to as “OCAP / DVB-MHP middleware”) that realizes a function defined in the OCAP / DVB-MHP specification using a function installed in the OS of the broadcast receiving apparatus is stored in the AV decoder. A tuner device that outputs an MPEG2 transport stream including the video / audio indicated by the designated identifier is searched for in the broadcast receiving apparatus. If it exists, an “information passing path” is implicitly established between the two devices with the TS decoder.

  Such a specification frees the program from complicated processing related to device management, and at first glance seems to be beneficial to the program. However, from the opposite viewpoint, since the middleware implicitly establishes the “information passing path”, it means that the program cannot manage the “information passing path”. For example, consider the hardware configuration shown in FIG. In FIG. 52, there are two tuners (tuner 101a and tuner 101b), two AV decoders (AV decoder 103a and AV decoder 103b), and these are connected by the TS decoder 102. Is a digital broadcast receiving apparatus. Consider running a PIP program on this hardware. In FIG. 52, since there are two tuners and two AV decoders on the hardware, all of them are occupied between the tuner 101a and the AV decoder 103a, and between the tuner 101b and the AV decoder 103b via the TS decoder 102. If two “information transfer paths” are established, a PIP program capable of changing two images completely independently can be realized. However, the current OCAP / DVB-MHP middleware does not have a function for establishing an “information transfer path” between devices, and the AV decoder has issued a decode request by designating video and audio by the PIP program. The “information transfer path” is implicitly established through the TS decoder between the tuner that is demodulating the MPEG2 transport stream including the video and the audio. Therefore, for example, when a decoding request for video and audio in the same MPEG2 transport stream is issued to two AV decoders, an “information transfer path” is established between the two AV decoders and the same tuner. It is possible. In the example of FIG. 52, an “information transfer path” is set between the tuner 101a and the AV decoder 103a and between the tuner 101a and the AV decoder 103b via the TS decoder 102. In such a case, the implementation of the OCAP / DVB-MHP middleware continues to maintain the “information transfer path” between the AV decoder and the tuner once established, and for a decode request for the AV decoder issued thereafter, If the first established “information passing path” is used, the PIP program can only use one tuner thereafter, and the two AV decoders can only use the video in the same MPEG2 transport stream at the same time. Cannot be decoded.

  In this way, the technique for prompting the middleware to establish an “information passing path” between the implicit devices reduces the burden on the device control of the program and at the same time reduces the flexibility on the device management. Further, as shown in the example using FIG. 52, the dependency of the program operation on the middleware implementation is increased, which may cause instability that the operation differs depending on the environment.

  Therefore, the present invention has been made in view of the above circumstances, and an object thereof is to provide an information processing apparatus that can control setting of an information transfer path between devices from a program (application program).

  In order to achieve the above object, an information processing apparatus according to the present invention is an information processing apparatus including a plurality of devices that execute a predetermined function, and manages program execution means for executing a program and information related to the device. And device management means for setting an information transfer path between the devices, wherein the device management means sets an information transfer path between the devices based on a request from a program executed by the program execution means An information path setting unit is provided.

  As a result, the program executed by the program execution means can set an information transfer path on hardware.

  Here, the device management unit further includes a device identifier notification unit that notifies the program of a device identifier for identifying the device based on a request from the program executed by the program execution unit, The information path setting unit may set information transfer paths in a specified order between devices specified by using the plurality of device identifiers by the program.

  The information path setting unit may set an information transfer path between the specified devices when two devices are specified using the two device identifiers by the program.

  The information path setting unit sets an information transfer path between the specified devices in a specified order when two or more devices are specified by using two or more device identifiers by the program. May be.

  As a result, the program can specify the device and set the information transfer path on the hardware in detail.

  The device identifier notifying unit may notify the program of a device identifier corresponding to the type of device specified by the program.

  As a result, the program can acquire only the device identifier of the device that matches the type of device that the program wants to use.

  The device identifier notifying unit may notify the program of device identifiers corresponding to all devices for which an information transfer path can be set with a device specified by the device identifier specified by the program. Good.

  As a result, the program can acquire a device identifier representing a device capable of setting an information transfer path with the designated device.

  Further, the device identifier notifying unit notifies the program of device identifiers corresponding to all devices for which an information transfer path is set with a device specified by the device identifier specified by the program. Also good.

  As a result, the program can acquire a device identifier representing a device for which an information transfer path has already been set with the designated device.

  In addition, the device identifier notification unit can set an information transfer path with a device specified by the device identifier specified by the program, and corresponds to a device that is not yet part of the information transfer path. The device identifier may be notified to the program.

  As a result, the program can acquire a device identifier representing a device that can immediately set an information transfer path with the designated device.

  The device management means further includes a device shareability notification unit that notifies the program whether or not a device specified by a device identifier specified by the program is included in a plurality of information transfer paths. Also good.

  Thus, the program can acquire a determination result as to whether or not the specified device can be included in a plurality of information transfer paths.

  Here, the device shareability notification unit may notify the program of the availability by notifying the maximum number of information transfer paths that can include the device.

  As a result, the program can acquire the number of information transfer paths that can include the specified device, and can determine whether the device can be included in a plurality of information transfer paths.

  Further, the device management means further has a function of specifying a device necessary for realizing the large function based on a function identifier specified by the program and indicating the large function realized by the plurality of devices. An interpretation unit may be provided, and the information path setting unit may set an information transfer path between the devices specified by the function interpretation unit.

  As a result, it is possible to set an information transfer path without specifying an individual device.

  Further, when the program makes a request to the device management means, the program may resume processing synchronously in response to a response from the device management means.

  As a result, the program executed by the program execution means can easily know the end timing of the information path setting process.

  Further, when the program makes a request to the device management unit, the program may execute processing asynchronously regardless of a response from the device management unit.

  As a result, the program executed by the program execution means can proceed with its own separate processing while the information processing apparatus performs the information path setting process.

The information path setting unit does not need to set a new information transfer path when any of the plurality of devices specified by the program has already been set as a part of another information transfer path. Good.
This makes it possible to protect the already set information transfer path from unintended changes.

  In addition, the information path setting unit may notify the program of a processing result indicating whether the information transfer path is successfully set or failed between a plurality of devices specified by the program.

  As a result, the program executed by the program execution means can obtain the processing result of the information transfer path.

  In addition, when the information path setting unit fails to set an information transfer path between a plurality of devices specified by the program, the information path setting unit may notify the program of the reason for the failure.

  As a result, the program executed by the program execution means can acquire the reason why the information transfer path setting process has failed.

The device management unit may further include an information path cancellation unit that cancels the setting of an information transfer path set between the devices based on a request from a program executed by the program execution unit.
As a result, the program can cancel the set information transfer path.

  Here, the device management unit further includes a device identifier notification unit that notifies the program of a device identifier for identifying the device based on a request from the program executed by the program execution unit, The information path cancellation unit may cancel the setting of the information transfer path set in the specified order between the devices specified by using the plurality of device identifiers by the program.

  The information path cancellation unit may cancel the setting of the information transfer path set between the specified devices when two devices are specified by using the two device identifiers by the program.

Further, the information path cancellation unit, when two or more devices are specified by using two or more device identifiers by the program, the information passing set in the specified order between the two or more devices The route may be canceled.
As a result, the program can specify the device and release the set information transfer path.

  Further, the device management means further has a function of specifying a device necessary for realizing the large function based on a function identifier specified by the program and indicating the large function realized by the plurality of devices. The information path cancellation | release part may be provided with the interpretation part, and may cancel | release the information delivery path | route set between the said devices specified by the said function interpretation part.

  As a result, it is possible to cancel the set information transfer path without designating individual devices.

In addition, the information path cancellation unit may notify the program of a processing result indicating whether the setting of the information transfer path set between a plurality of devices designated by the program has succeeded or failed. Good.
As a result, the program can obtain the release processing result of the information transfer path.

  In addition, the information path cancellation unit may notify the program of the reason for failure when it fails to cancel the setting of an information transfer path set between a plurality of devices designated by the program.

  As a result, the program can acquire the reason why the information transfer path release processing has failed.

  The device management means further includes a device number notifying unit for notifying the program of the number of devices existing on the information processing apparatus based on a request from a program executed by the program execution means. May be.

  Thus, the program can acquire the number of devices existing on the information processing apparatus.

  The device number notifying unit may notify the program of the number of devices corresponding to the device type specified by the program.

  Thus, the program can acquire the number of devices that match the type of device that the program wants to use.

The device management means further notifies the program whether or not an information transfer path can be set between the devices based on a request from the program executed by the program execution means. A route setting availability notification unit may be provided.
As a result, the program can obtain in advance a determination as to whether or not an information transfer path can be set.

  Here, the device management unit further includes a device identifier notification unit that notifies the program of a device identifier for identifying the device based on a request from the program executed by the program execution unit, The route setting availability notification unit notifies the program whether or not an information transfer route can be set in a specified order between devices specified by the program using a plurality of device identifiers. Also good.

  As a result, the program can obtain in advance a determination as to whether or not it is possible to specify a device and set an information transfer path.

  The path setting availability notification unit may determine whether an information transfer path can be set between the specified devices when two devices are specified using the device identifier by the program. May be notified to the program.

  As a result, the program can obtain a determination as to whether or not an information transfer path can be set between the two devices.

  The path setting availability notification unit sets information passing paths between the specified devices in the specified order when two or more devices are specified by the program using two or more device identifiers. It may be notified to the program whether or not it is possible.

  As a result, the program can acquire a determination as to whether or not an information transfer path can be set between two or more devices.

  Further, the device management means further has a function of specifying a device necessary for realizing the large function based on a function identifier specified by the program and indicating the large function realized by the plurality of devices. An interpretation unit may be provided, and the route setting availability notification unit may notify the program whether or not an information transfer route can be set between the devices specified by the function interpretation unit.

  Accordingly, it is possible to obtain a determination as to whether or not a necessary information transfer path can be set without specifying an individual device.

  In addition, the device management unit is further configured to notify the program whether or not an information transfer route is set between the devices based on a request from the program executed by the program execution unit. May be provided.

  As a result, the program can acquire a determination as to whether an information transfer path has already been set between devices.

  Here, the device management unit further includes a device identifier notification unit that notifies the program of a device identifier for identifying the device based on a request from the program executed by the program execution unit, The path state notification unit may notify the program whether or not an information transfer path is set in a specified order between devices specified by using the device identifier by the program.

  As a result, the program can specify a device and obtain a determination as to whether or not an information transfer path has already been set between the devices.

  In addition, when two devices are specified using the two device identifiers by the program, the path state notification unit notifies the program whether or not an information transfer path is set between the specified devices. May be.

  As a result, the program can acquire a determination as to whether or not an information transfer path has already been set between the two devices.

  In addition, when two or more devices are specified by using two or more device identifiers by the program, the path status notification unit sets an information transfer path between the specified devices in the specified order. The program may be notified of whether or not

  As a result, the program can acquire a determination as to whether or not an information transfer path has already been set between two or more devices.

  Further, the device management means further has a function of specifying a device necessary for realizing the large function based on a function identifier specified by the program and indicating the large function realized by the plurality of devices. An interpretation unit may be provided, and the route setting availability notification unit may notify the program whether or not an information transfer route is set between the devices specified by the function interpretation unit.

  Accordingly, it is possible to obtain a determination as to whether or not an information transfer path has already been set between necessary devices without designating individual devices.

In addition, the information path setting unit always prioritizes the information transfer path requested first when the setting of the information transfer path including the same device is requested by a plurality of programs executed by the program execution unit. May be set.
This makes it possible to resolve device conflicts between a plurality of programs.

  Further, the program execution means may manage priorities among a plurality of programs and compare the priorities of the programs using the priorities.

  As a result, when a device conflict occurs between a plurality of programs, it is possible to perform consistent device management in which a program having a higher priority is given a right to use the device.

  The information path setting unit always prioritizes the information transfer path of the high priority program when the setting of the information transfer path including the same device is requested by a plurality of programs executed by the program execution unit. May be set.

  As a result, when a device conflict occurs between a plurality of programs, a program having a higher priority can preferentially set an information transfer path.

  In addition, when the information path setting unit is requested to set an information transfer path including a device set as the information transfer path by another program having a higher priority after setting the information transfer path, While setting the information transfer path requested by another program, it may be notified to the program that requested the first information transfer path.

  As a result, the low priority program that requested the first information transfer path can know that the device in the information transfer path has been stolen.

  In addition, when the device included in the first information transfer route and configured the information transfer route requested by the other program becomes usable again, the information route setting unit You may notify the program which requested | required the first information delivery path | route that it can be reused.

  As a result, the low-priority program that requested the first information transfer path can know that the stolen device can be reused.

  In addition, the information path setting unit may include the first information transfer path when the device included in the first information transfer path and constituting the information transfer path requested by the other program becomes available again. The information transfer path may be reset, and the reset may be notified to the program that requested the first information transfer path.

  As a result, the low priority program that requested the first information transfer route can reuse the stolen device and know that the information transfer route has been reset.

  The device management means preferably controls the device according to a request from the program and notifies the program of information related to the device according to a request from the program.

  That is, the device management means is middleware, and can control setting of an information transfer path between devices from a program executed by the program execution means.

  Furthermore, the present invention can be realized not only as such an information processing apparatus, but also as an information processing method including characteristic means included in such an information processing apparatus as steps, or by performing these steps as a computer. It can also be realized as a program to be executed. Needless to say, such a program can be distributed via a recording medium such as a CD-ROM or a transmission medium such as the Internet.

  As is apparent from the above description, according to the information processing apparatus of the present invention, it is possible to control setting of an information transfer path between devices from a program (application program).

(Embodiment 1)
The present invention assumes three types of operation modes, ie, a satellite system, a terrestrial system, and a cable system, as a target broadcast system. A satellite system uses a satellite to transmit a broadcast signal to a broadcast receiver, a terrestrial wave system uses a terrestrial signal transmitter to transmit a broadcast signal to the broadcast receiver, and a cable system uses a cable head end In this mode, a broadcast signal is transmitted to a broadcast receiving apparatus. Since the present invention does not have a direct relationship with the difference between the broadcasting systems, it can be applied regardless of the broadcasting system.

  An embodiment of a broadcasting system according to the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the relationship between devices constituting a broadcasting system, and includes a broadcasting station side system 201, three terminal devices A211, a terminal device B212, and a terminal device C213. For the connection 221 between the broadcasting station side system and each terminal device, both wired and wireless cases exist. For example, in a cable system, a broadcasting station side system and each terminal device are coupled by wire. On the other hand, there is no wired connection between the broadcasting station side system and each terminal device in the satellite / terrestrial wave system in the downstream direction (from the broadcasting station side system to each terminal device), and the broadcast signal uses radio waves. Is transmitted. As for the upstream direction (from each terminal device to the broadcasting station side system), there are cases of both wire connection using a telephone line, wired Internet, and wireless connection using wireless communication. Each terminal device receives information such as user input. Send to the broadcasting station system. In the present embodiment, three terminal devices are coupled to one broadcasting station side system, but the present invention can be applied even if an arbitrary number of terminal devices are coupled to the broadcasting station side system. .

  The broadcast station side system 201 transmits information such as video / audio / data broadcasting data included in a broadcast signal to a plurality of terminal devices. The broadcast signal is transmitted using a frequency within a frequency band determined by a broadcast system operation default or a law of a country / region where the broadcast system is operated.

  As an example, a predetermined example of broadcast signal transmission related to a cable system is shown. In the cable system shown in this example, the frequency band used for broadcast signal transmission is divided and used for the data content and the transmission direction (upstream and downstream). FIG. 2 is a table showing an example of frequency band division. Frequency bands are roughly classified into two types, Out Of Band (abbreviated as OOB) and In-Band. 5 to 130 MHz is allocated to the OOB, and is mainly used for data exchange between the broadcasting station side system 201 and the terminal device A 211, the terminal device B 212, and the terminal device C 213. 130 MHz to 864 MHz is assigned to In-Band and is mainly used for broadcast channels including video and audio. QPSK modulation is used for OOB, and QAM64 or QAM256 modulation is used for In-Band. The modulation technique is a well-known technique that is not very related to the present invention, and thus detailed description thereof is omitted. FIG. 3 is an example of a more detailed use of the OOB frequency band. 70 MHz to 74 MHz are used for data transmission from the broadcast station side system 201, and all the terminal devices A 211, terminal devices B 212, and terminal devices C 213 receive the same data from the broadcast station side system 201. On the other hand, 10.0 MHz to 10.1 MHz is used for data transmission from the terminal device A 211 to the broadcasting station side system 201, and 10.1 MHz to 10.2 MHz is used for data transmission from the terminal device B 212 to the broadcasting station side system 201. The 10.2 MHz to 10.3 MHz is used for data transmission from the terminal device C 213 to the broadcast station side system 201. Thereby, data unique to each terminal device can be transmitted from each terminal device A 211, terminal device B 212, and terminal device C 213 to the broadcasting station side system 201. FIG. 4 is an example of use for the In-Band frequency band. 150-156 MHz and 156-162 MHz are assigned to TV channel 1 and TV channel 2, respectively, and thereafter, TV channels are assigned at intervals of 6 MHz. After 310 MHz, radio channels are allocated in 1 MHz units. Each of these channels may be used as an analog broadcast or a digital broadcast. In the case of digital broadcasting, it is transmitted in a TS packet format based on the MPEG2 specification, and various data broadcasting data can be transmitted in addition to audio and video.

  The broadcast station side system 201 includes a QPSK modulation unit, a QAM modulation unit, and the like in order to transmit an appropriate broadcast signal to the terminal device using these frequency bands. Moreover, in order to receive the data from a terminal device, it has a QPSK demodulator. The broadcast station side system 201 is considered to have various devices related to the modulation unit and the demodulation unit. However, since the present invention mainly relates to the terminal device, detailed description thereof is omitted.

  The terminal device A 211, the terminal device B 212, and the terminal device C 213 receive and reproduce the broadcast signal from the broadcast station side system 201. In addition, data specific to each terminal device is transmitted to the broadcast station side system 201. The three terminal devices have the same configuration in this embodiment.

  In this example, details of an example relating to cable system operation are introduced, but the present invention can also be applied to other forms of satellites, terrestrial systems, and cable systems. In the satellite and terrestrial systems, the broadcasting station side system and each terminal device are connected in both wired / wireless cases as described above. Further, the frequency band, frequency interval, modulation method, configuration of the broadcasting station side system, etc. Although they differ depending on the type and operation of the broadcasting system, they are not related to the present invention, and the present invention is applicable no matter how they are defined.

  The broadcast station side system 201 modulates the MPEG2 transport stream and transmits it by including it in the broadcast signal. The broadcast receiving apparatus receives a broadcast signal, demodulates it, reproduces an MPEG2 transport stream, extracts necessary information from it, and uses it. In order to explain the function and connection structure of devices existing in the digital broadcast receiving apparatus, the structure of the MPEG2 transport stream will be briefly described first.

  FIG. 5 is a diagram showing the structure of a TS packet. The TS packet 600 has a length of 188 bytes and includes a header 601, an adaptation field 602, and a payload 603. The header 601 holds TS packet control information. It has a length of 4 bytes and a configuration represented by 604. This field has a field described as “Packet ID (hereinafter referred to as PID)”, and the TS packet is identified by the value of this PID. The adaptation field 602 holds additional information such as time information. The presence of the adaptation field 602 is not essential and may not exist. The payload 603 holds information transmitted by the TS packet, such as video / audio and data for data broadcasting.

  FIG. 6 is a schematic diagram of an MPEG2 transport stream. The TS packet 701 and the TS packet 703 hold PID 100 in the header, and hold information related to video 1 in the payload. The TS packet 702 and the TS packet 705 hold the PID 200 in the header, and hold information related to the data 1 in the payload. The TS packet 704 holds the PID 300 in the header, and holds information related to the audio 1 in the payload.

  The MPEG2 transport stream 700 is composed of continuous TS packets such as TS packets 701 to 705. The TS packet holds various information such as video, audio, and data for data broadcasting in its payload. The broadcast receiving apparatus receives TS packets, extracts information held in each TS packet, reproduces video and audio, and uses data such as program scheduling information. At this time, TS packets having the same PID hold the same type of information. Also in FIG. 6, both the TS packet 701 and the TS packet 703 transmit information about the video 1, and the TS packet 702 and the TS packet 705 both transmit information about the data 1.

  Video and audio are expressed in a format called a PES (Packetized Elementary Stream) packet. When the PES packet is actually transmitted, it is divided and stored in the TS packet. FIG. 7 shows an example of division when transmitting a PES packet. Since the PES packet 801 is large to be stored and transmitted in the payload in one TS packet, it is divided into a PES packet division A 802a, a PES packet division B 802b, and a PES packet division C 802c, and three TS packets 803-3 having the same PID 805 is transmitted. Depending on the operation, the PES packet may transmit not only video / audio but also subtitle data called a subtitle.

  Information such as program organization information and data for data broadcasting is expressed using a format called MPEG2 section. The MPEG2 section is divided and stored in TS packets when actually transmitted. FIG. 8 shows an example of division when the MPEG2 section is transmitted. Since the MPEG2 section 901 is large to be stored and transmitted in the payload in one TS packet, it is divided into section division A 902a, section division B 902b, and section division C 902c, and is transmitted by three TS packets 903 to 905 having the same PID. Is done.

  FIG. 9 represents the structure of the MPEG2 section. The MPEG2 section 1000 includes a header 1001 and a payload 1002. The header 1001 holds control information of the MPEG2 section. The configuration is represented by a header configuration 1003. The payload 1002 holds data transmitted by the MPEG2 section 1000. The table_id existing in the header structure 1003 expresses the type of the MPEG2 section, and the table_id_extension is an extension identifier used to distinguish between MPEG2 sections having the same table_id. As an example of use of the MPEG2 section, FIG. 10 shows a case where program organization information is transmitted. In this example, as described in the row 1104, information necessary for demodulating the broadcast signal is described in the MPEG2 section whose table_id is 64 in the header structure 1003, and the MPEG2 section is assigned 16 as the PID. It is transmitted by TS packet.

  As described above, the MPEG2 transport stream has a hierarchical structure in order to transmit various information. The broadcast receiving apparatus needs to extract information included in the MPEG2 transport stream existing in the broadcast signal while following the hierarchical structure of the MPEG2 transport stream, and is equipped with a device for that purpose. The devices are physically connected to each other so that one output is the other input. Furthermore, when there are multiple devices of the same type, they are not only physically connected, but also to which device of the same type of device is input, or from which device of the same type of device is output. It is necessary to establish an “information transfer route” that indicates whether or not to receive the information. For example, even in an environment where there are multiple tuners, one TS decoder, and multiple AV decoders, and TS decoders are "physically" connected to all tuners and all AV decoders, When decoding video and audio, it is necessary to establish a “information transfer path” by “logically” connecting a single tuner and a single AV decoder via a TS decoder. Hereinafter, the terms “physical connection”, “logical connection”, and “device logical connection path” used in all the embodiments are defined.

  “Physical connection” and “physical connection” indicate that devices are connected on hardware. “Device A and device B are“ physically connected ”” means that device A and device B are connected on hardware.

  “Logical connection” and “logical connection” indicate that the devices are not only “physically connected” but also constitute an “information transfer path”. Device A and device B are “logically connected” so that the output information of device A becomes the input information of device B, or the output information of device B becomes the input information of device A , "Data transfer path" is established.

“Device logical connection path” refers to the “data transfer path” itself.
The device A and the device B being “physically connected” is a minimum condition for the devices A and B to be “logically connected”. When device A and device B are not “physically connected”, it is impossible to “logically connect” device A and device B. When device A and device B are “logically connected”, naturally device A and device B are “physically connected”.

Hereinafter, a situation that is a premise of the present embodiment will be described.
FIG. 11 is a block diagram showing a general hardware configuration of the digital broadcast receiving apparatus. The terminal device 1200 includes a tuner 1201, a TS decoder 1202, an AV decoder 1203, a speaker 1204, a display 1205, a CPU 1206, a secondary storage unit 1207, a primary storage unit 1208, a ROM 1209, and an input unit 1210.

  A tuner 1201 is a device that demodulates a broadcast signal that is modulated and transmitted in the broadcast station side system 201 in accordance with tuning information including a frequency specified by the CPU 1206. The MPEG2 transport stream obtained by demodulating the tuner 1201 is transmitted to the TS decoder 1202.

  The TS decoder 1202 is a device having a function of selecting a PES packet or an MPEG2 section that matches a specified condition from the MPEG2 transport stream based on a specification of a PID specified by the CPU 1206, a section selection condition, or the like. The PES packet selected by the TS decoder 1202 is transferred to the AV decoder 1203. The MPEG2 section selected by the TS decoder 1202 is transferred to the primary storage unit 1208 by DMA (Direct Memory Access) and used by a program executed by the CPU 1206. In addition to the PES packet and MPEG2 section selection function, the TS decoder 1202 performs an encrypted (scrambled) PES packet and MPEG2 section descrambling function, and an input MPEG2 transport stream. And a function of transferring to another device physically connected to the TS decoder 1202.

  The AV decoder 1203 is a device having a function of decoding digitally encoded video and audio. An AV signal obtained by decoding by the AV decoder 1203 is transmitted to the speaker 1204 and the display 1205. Note that the AV decoder 1203 may not always be able to decode video and audio at the same time. There may be a video decoder and an audio decoder alone. Note that the AV decoder 1203 may have a decoding function for subtitle data depending on circumstances.

The speaker 1204 and the display 1205 are devices having a function of outputting audio and video transmitted from the AV decoder 1203, respectively.
The CPU 1206 executes a program that operates on the broadcast receiving apparatus. When the program executed by the CPU 1206 is included in the ROM 1209, downloaded from a broadcast signal or network and held in the primary storage unit 1208, downloaded from the broadcast signal or network and stored in the secondary storage unit 1207 Etc. exist. The tuner 1201, TS decoder 1202, AV decoder 1203, speaker 1204, display 1205, secondary storage unit 1207, primary storage unit 1208, ROM 1209, and input unit 1210 are controlled in accordance with instructions of the program to be executed.

  The secondary storage unit 1207 erases information when the terminal device 1200 is turned off, such as a non-volatile memory such as a FLASH-ROM, a HDD (Hard Disk Drive), a rewritable medium such as a CD-R or a DVD-R. The information is stored by an instruction from the CPU 1206. This is used to store data that is not needed to be deleted when the terminal device 1200 is turned off.

  The primary storage unit 1208 is configured by a RAM or the like, and is a device having a function of temporarily storing information in accordance with instructions from the CPU 1206 and DMA-capable devices. Information held in the primary storage unit 1208 is erased when the terminal device 1200 is powered off.

  The ROM 1209 is a non-rewritable memory device, and specifically includes a ROM, a CD-ROM, a DVD, and the like. The ROM 1209 stores a program executed by the CPU 1206.

  Specifically, the input unit 1210 includes a front panel and a remote controller, and receives input from the user. FIG. 12 shows an example in which the input unit 1210 is configured with a front panel. The front panel 1300 includes seven buttons, an up cursor button 1301, a down cursor button 1302, a left cursor button 1303, a right cursor button 1304, an OK button 1305, a cancel button 1306, and an EPG button 1307. When the user presses the button, the CPU 1206 is notified of the identifier of the pressed button.

  In FIG. 11, the display 1205 and the speaker 1204 are expressed so as to be included in the broadcast receiving apparatus. However, the broadcast receiving apparatus may not include the display 1205 and the speaker 1204 and may output only an AV signal to the outside. Exists. The locations of the display 1205 and the speaker 1204 are not related to the present invention, and the present invention can be applied to both types.

  Next, FIG. 13 shows a hardware configuration example when a plurality of devices exist on the terminal device. The terminal device 1400 includes a tuner 1401, a TS decoder 1402, an AV decoder 1403, a speaker 1404, a display 1405, a CPU 1406, a secondary storage unit 1207, a primary storage unit 1208, a ROM 1209, and an input unit 1210. The difference between FIG. 11 and FIG. 13 is that there are two tuners (tuner 1401a and tuner 1401b) in the portion expressed by tuner 1401, and two AV decoders (AV decoder 1403a and AV in the portion expressed by AV decoder 1403). The presence of a decoder 1403b). A device that exists in the terminal device 1400 and is identified by the same number as in FIG. 11 performs the same operation as in the case of FIG. Hereinafter, differences between the hardware configuration in FIG. 11 and the hardware configuration in FIG. 13 will be described.

  The tuner 1401a and the tuner 1401b are devices that demodulate a broadcast signal that is modulated and transmitted by the broadcasting station side system 201 in accordance with tuning information including a frequency specified by the CPU 1406, and can operate independently of each other. MPEG2 transport streams obtained by demodulating the tuners 1401a and 1401b are transmitted to the TS decoder 1402, respectively.

In the example of the hardware configuration shown in FIG. 13, two tuners are used. However, the present invention can be applied without depending on the number of tuners.
Similar to the TS decoder 1202, the TS decoder 1402 is a device having a function of selecting a PES packet or an MPEG2 section that matches a designated condition from an input MPEG2 transport stream based on designation of a PID, a section filter condition, and the like. . In the hardware configuration shown in FIG. 13, the TS decoder 1402 receives MPEG2 transport streams from two tuners 1401a and 1401b, and can select PES packets and MPEG2 sections for each of them. . Further, in the hardware configuration of FIG. 13, the TS decoder 1402 can send selected PES packets to the two AV decoders of the AV decoder 1403a and the AV decoder 1403b.

  In the hardware configuration example of FIG. 13, the number of MPEG2 transport stream inputs of the TS decoder 1402 is 2, but the present invention can be applied without depending on this number. In this hardware configuration, the number of PES packets output to the AV decoder of the TS decoder 1402 is 2, but the present invention can be applied without depending on this number. Even if there are a plurality of TS decoders 1402 themselves, the present invention is applicable.

  The AV decoder 1403a and the AV decoder 1403b are devices having a function of decoding encoded video data and encoded audio data included in an input PES packet. Video and audio AV signals obtained by decoding by the AV decoder 1403a and AV decoder 1403b are transmitted to a display 1405 and a speaker 1404, respectively. In the hardware configuration example of FIG. 13, there are two AV decoders 1403 a and 1403 b in the broadcast receiving apparatus 1400, and it is possible to independently decode the PES packets output from the TS decoder 1402.

Although the number of AV decoders is 2 in the hardware configuration example of FIG. 13, the present invention can be applied without depending on this number.
The speaker 1404 and the display 1405 are devices each having a function of outputting audio and video. In this embodiment, AV signals are input from two AV decoders, and the output form is determined by an instruction from the CPU 1406. For example, only the AV signal output by the AV decoder 1403a is output, the video output by the AV decoder 1403b is displayed in full screen, and the video output by the AV decoder 1403a is displayed in the lower right quarter before the video output by the AV decoder 1403b. It can be specified to be displayed.

  The CPU 1406 executes a program that operates on the broadcast receiving apparatus 1400. The program executed by the CPU 1406 is included in the ROM 1209, downloaded from a broadcast signal or network and stored in the primary storage unit 1208, downloaded from the broadcast signal or network, and stored in the secondary storage unit 1207, etc. Exists. The tuner 1401, TS decoder 1402, AV decoder 1403, speaker 1404, display 1405, secondary storage unit 1207, primary storage unit 1208, ROM 1209, and input unit 1210 are controlled in accordance with instructions of the program to be executed. When there are a plurality of devices of the same type, such as the tuner 1401 and AV decoder 1403 in the hardware configuration of FIG. 13, the CPU 1406 can individually specify and control each of them.

  In the hardware configuration shown in FIGS. 11 and 13, each device is included in the terminal device by default at the time of shipment. However, in order to add a device not mounted on the terminal device and to improve the function of the device mounted on the terminal device, an adapter mounted with the device to be added may be further given to the terminal device. . FIG. 14 shows an example of such a hardware configuration. The terminal device 1500 includes a tuner 1501, a TS decoder 1502, an AV decoder 1203, a speaker 1204, a display 1205, a CPU 1506, a secondary storage unit 1207, a primary storage unit 1208, a ROM 1209, and an input unit 1210. A device that is mounted on the terminal device 1500 and is identified by the same number as in FIG. 11 has the same function as in FIG. The terminal device 1500 is provided with an adapter 1511. A device having a function to be added to the terminal device 1500 is mounted on the adapter 1511. The adapter 1511 that appears in the hardware configuration example of FIG. 14 receives an MPEG2 transport stream, and descrambles TS packets having a PID specified by the CPU 1506 with respect to TS packets included in the input MPEG2 transport stream. Holds the device (descrambler) that performs (decryption). In order to operate the device held by the adapter 1511, it is necessary to input the MPEG2 transport stream demodulated by the tuner 1501 to the adapter 1511. Therefore, the tuner 1501 inputs the demodulated MPEG2 transport stream to the adapter 1511. The adapter 1511 transmits the MPEG2 transport stream to the TS decoder 1502 after descrambling the TS packet designated by the CPU 1506 in the input MPEG2 transport stream. The TS decoder 1502 processes the MPEG2 transport stream input from the adapter 1511 in the same manner that the TS decoder 1202 in FIG. 11 can process the MPEG2 transport stream input from the tuner 1201. Is possible. The CPU 1506 can communicate with or control not only devices existing in the terminal device 1500 but also devices in the adapter 1511.

  In the hardware configuration shown in FIG. 14, the adapter 1511 includes a descrambler, but the present invention can be applied without depending on the type and number of devices held by the adapter 1511. Further, in the hardware configuration shown in FIG. 14, the adapter 1511 is configured to receive the MPEG2 transport stream from the tuner 1501 and transmit the MPEG2 transport stream to the TS decoder 1502. The present invention can be applied even if a device mounted on the adapter 1511 is inserted into any part of the device. For example, the present invention can be applied even if the adapter 1511 includes an AV decoder, the adapter 1511 receives a PES packet from the TS decoder 1502, and outputs an AV signal to the display 1205 and the speaker 1204. Also, the interface between the terminal device 1500 and the adapter 1511 is generally PCMCIA (Personal Computer Memory Card International Association), but the present invention is not related to the interface type, so it can be applied to any interface. Is possible. Further, since the terminal device 1500 does not depend on the number of adapters that can be physically connected at the same time, the present invention can be applied even if it can be physically connected to a plurality of adapters.

  Next, FIG. 15 illustrates a hardware configuration example in the case where an adapter is further added to a terminal device having a plurality of devices. The terminal device 1600 includes a tuner 1601, a TS decoder 1602, an AV decoder 1403, a speaker 1404, a display 1405, a CPU 1606, a secondary storage unit 1207, a primary storage unit 1208, a ROM 1209, and an input unit 1210. The devices that are installed in the terminal device 1600 and that are identified by the same numbers as those in FIG. 11 or FIG. 13 have the same functions as those in FIG. 11 or FIG. The terminal device 1600 is provided with an adapter 1611. A device having a function to be added to the terminal device 1600 is mounted on the adapter 1611. The adapter 1611 appearing in the hardware configuration example of FIG. 15 is equipped with a descrambler like the adapter 1511. The descrambler installed in 1611 receives a plurality of MPEG2 transport stream inputs and outputs a plurality of MPEG2 transport streams. Since there are two tuners in the hardware configuration shown in FIG. 15, the MPEG2 transport stream output from the tuners 1601a and 1601b is input to the adapter 1611. The descrambler mounted on the adapter 1611 performs descrambling processing on the two input MPEG2 transport streams, and transmits the processed two MPEG2 transport streams to the TS decoder 1602. The TS decoder 1602 can process two input MPEG2 transport streams in the same way that the TS decoder 1402 in FIG. 13 can process the MPEG2 transport streams output by the tuners 1401a and 1401b. The CPU 1606 can communicate with or control not only devices in the terminal device 1600 but also devices in the adapter 1611.

  In the hardware configuration shown in FIG. 15, the same number of MPEG2 transport streams as the number of tuners 1601 are transmitted to the adapter 1611 that needs to input MPEG2 transport streams. It is not necessary to input the stream to the adapter 1611. For example, the present invention can be applied to a configuration in which only the tuner 1601a is input to the adapter 1611. Further, the present invention does not depend on the format of information between the terminal device 1600 and the adapter 1611. For example, before inputting to the adapter 1611, the terminal device 1600 side inputs “bit stream that can be interpreted by the adapter 1611” created by synthesizing the MPEG2 transport stream output from the tuner 1601 a and the tuner 1601 b to the adapter 1611. The processed bit stream output from the adapter 1611 may be separated into two MPEG2 transport streams before being input to the TS decoder 1602.

  As an example of the adapter, a POD used in the US cable system will be described. FIG. 16 shows the hardware configuration of the terminal device to which the POD 1711 is assigned. Devices that exist in the terminal apparatus 1700 and are identified by the same numbers as those in FIG. 11 or FIG. 14 have the same functions as those in FIG. 11 or FIG. The POD 1711 is equipped with a descrambler, and similarly to the adapter 1511 in FIG. 14, the MPEG2 transport stream is input from the tuner 1701 and the descrambled MPEG2 transport stream is output to the TS decoder 1702. Also, in the US cable system, as shown in FIGS. 2 and 3, various information is transmitted in the upstream and downstream directions using a frequency band called OOB. At this time, since the format of the information transmitted from the broadcasting station side system 201 to the terminal device is different from the format of the information interpretable by the terminal device 1700, it is impossible to exchange information as it is. The POD 1711 includes a device that converts the format of upstream and downstream information transmitted by the OOB. Information transmitted by OOB is modulated by the QPSK modulation method. This modulation method is a known technique and will not be described in detail. The terminal apparatus includes a QPSK demodulator 1712 and a QPSK modulator 1713. The CPU 1706 can control not only devices in the terminal device 1700 but also devices in the POD 1711.

  Regarding the information reception of the terminal device 1700 in the downlink direction, first, the QPSK demodulator 1712 demodulates the downlink signal transmitted from the broadcast station side system 201 by OOB, and inputs the generated bit stream to the POD 1711. The POD 1711 extracts information specified by the CPU 1706 from various information included in the bit stream, converts the information into a format interpretable by a program operating on the CPU 1706, and provides the CPU 1706 with the information.

  Regarding information transmission of the terminal device 1700 in the upstream direction, first, the CPU 1706 transmits information to be transmitted to the broadcasting station side system 201 to the POD 1711. The POD 1711 converts information input from the CPU 1706 into a format that can be interpreted by the broadcasting station side system 201, and transmits the converted information to the QPSK modulator 1713. The QPSK modulator 1713 performs QPSK modulation on the information input from the POD 1711 and transmits it to the broadcast station side system 201.

  Using each device appearing in FIG. 11 to FIG. 16, the broadcast receiving apparatus has a function of outputting video / audio included in the broadcast signal to the screen and data such as program organization information included in the broadcast signal. The function to extract and present to the user is realized. These functions are realized by physically and logically connecting various devices existing in the broadcast receiving apparatus in an appropriate form and in an appropriate order, and appropriately using the functions of these devices. FIG. 17 is a conceptual diagram representing the physical connection order, processing contents, and input / output data format of each device. The terminal device 1800 includes a tuner 1801, a PID filter 1802, a section filter 1803, a descrambler 1804, an AV decoder 1805, a display / speaker 1806, and a primary storage unit 1807. The devices appearing in FIG. 17 correspond one-to-one or one-to-many with the devices appearing in FIG.

A tuner 1801 corresponds to the tuner 1201, receives a broadcast signal, and outputs an MPEG2 transport stream.
Within the TS decoder 1202, there are three types of devices that process MPEG2 transport streams: a PID filter 1802, a section filter 1803, and a descrambler 1804. These functions are described in detail here.

  The PID filter 1802 extracts a TS packet having a PID designated by the CPU 1206 from the input MPEG2 transport stream, and further extracts a PES packet and an MPEG2 section existing in the payload. For example, a case where the PES packet 801 is extracted in the situation shown in FIG. First, the CPU 1206 sets the PID 100 in the PID filter 1802 and issues a request to extract the PES packet. Then, the PID filter extracts TS packets 803 to 805 whose PID is 100 from TS packets flowing in the MPEG2 transport stream, and further, PES packet division A 802a included in the extracted payloads of the TS packets 803 to 805, The PES packet division B 802 b and the PES packet division C 802 c are extracted and connected to form a PES packet 801. One or more PID filters 1802 exist in the TS decoder 1202.

  The descrambler 1804 descrambles the PES packet output from the PID filter 1802 and the MPEG2 section. Even when the PES packet and the MPEG2 section are encrypted, they are divided and transmitted as in FIGS. The descrambler 1804 can specify the encrypted PES packet and the TS packet that transmits the MPEG2 section according to the PID designation of the CPU 1206, and then performs descrambling processing using the descrambling key designated by the CPU 1206. . The method for obtaining the descrambling key is not relevant to the present invention, and thus the description thereof is omitted. The descrambler 1804 outputs the descrambled PES packet to the AV decoder 1805 and the descrambled MPEG2 section to the section filter 1803. The descrambling is a process that is applied only to the encrypted PES packet and the MPEG2 section, and the descrambler 1804 receives the PES packet and the MPEG2 section from the PID filter only when necessary by the instruction of the CPU 1206, and performs the descrambling process. Do. The unscrambled PES packet and the MPEG2 section are directly output from the PID filter 1802 to the AV decoder 1805 and the section filter 1803, respectively. One or more descramblers 1804 exist in the TS decoder 1202.

  The section filter 1803 extracts the MPEG2 section that matches the section filter condition designated by the CPU 1206 from the input MPEG2 section, and DMA-transfers it to the primary storage unit 1807. The MPEG2 section held in the primary storage unit 1807 is read by the CPU 1206 and used. For example, a case where an MPEG2 section holding tuning information is acquired in FIG. 10 is taken as an example. The CPU 1206 first sets the PID 16 in the PID filter 1802 and issues a request to acquire a section. The PID filter 1802 extracts a section from the TS packet whose PID is 16, and provides the section filter 1803 with the section. Next, the CPU 1206 requests the section filter 1803 to extract a section whose table_id is 64. The section filter 1803 extracts a section whose table_id is 64 from the MPEG2 section input by the PID filter 1802 and DMA-transfers it to the primary storage unit 1807. One or more section filters 1803 exist in the TS decoder 1202.

  The AV decoder 1805 corresponds to the AV decoder 1203, inputs a PES packet, and outputs an AV signal to the display / speaker 1806. A display / speaker 1806 corresponds to the display 1205 and the speaker 1204, receives an AV signal, outputs video to the display 1205, and outputs audio to the speaker 1204.

The primary storage unit 1807 corresponds to the primary storage unit 1208, receives an MPEG2 section, and can refer to the contents of a program executed by the CPU 1206.
The procedure for outputting video and audio to a display and a speaker, respectively, will be exemplified using the representation of FIG. A broadcast signal input to the broadcast receiving apparatus is first demodulated into an MPEG2 transport stream by a tuner 1801. Next, the PID filter 1802 extracts a PES packet containing video and audio information transmitted by a TS packet having a PID designated by the CPU 1206. If necessary, the PES packet is transmitted to the descrambler 1804 and subjected to descrambling processing. Thereafter, the PES packet is input to the AV decoder 1805 and decoded to output an AV signal. After that, the AV signal is input to the display and speaker 1806, and video and audio can be reproduced.

  The procedure for extracting data such as program scheduling information from a broadcast signal will be exemplified using the expression of FIG. A broadcast signal input to the broadcast receiving apparatus is first demodulated into an MPEG2 transport stream by a tuner 1801. Next, the PID filter 1802 extracts an MPEG2 section containing data transmitted by a TS packet having a PID designated by the CPU 1206. If necessary, the MPEG2 section is transmitted to the descrambler 1804 to be descrambled. Further, the MPEG2 section is input to the section filter 1803, and only the MPEG2 section meeting the section filter condition designated by the CPU 1206 is output. Thereafter, the MPEG2 section is input to the primary storage unit 1807 and provided to the CPU 1206.

  Note that FIG. 17 is conceptually illustrated as a broadcast receiving apparatus having a display / speaker 1806 as in FIG. 11, but there is a type in which the display / speaker 1806 does not include the broadcast receiving apparatus and exists outside. The present invention is applicable to both types. In the conceptual diagram shown in FIG. 17, the descrambler 1804 exists in the TS decoder 1202, but may exist outside the TS decoder depending on the hardware configuration. Even in that case, the present invention is applicable.

  Next, FIG. 18 shows a conceptual diagram corresponding to a hardware configuration including a plurality of tuners and AV decoders shown in FIG. The terminal device 1900 includes a tuner 1901a and a tuner 1901b, a PID filter 1902, a section filter 1803, a descrambler 1904, an AV decoder 1905a and an AV decoder 1905b, a display / speaker 1906, and a primary storage unit 1807. The devices in FIG. 18 that are identified by the same numbers as those in FIG. 17 have the same functions as those in FIG. The devices appearing in FIG. 18 correspond one-to-one or one-to-many with the devices appearing in FIG. In FIG. 18, there are two tuners, a tuner 1901a and a tuner 1901b, and two AV decoders, an AV decoder 1905a and an AV decoder 1905b. In FIG. 13, the TS decoder 1402 can input a plurality of MPEG2 transport streams and output a plurality of PES packets. Also in FIG. 18, “information” can be freely combined with a plurality of tuners and a plurality of AV decoders. It is possible to establish a delivery route. The PID filter 1902 in the TS decoder 1402 can extract the PES packet and the MPEG2 section from the MPEG2 transport stream input from either the tuner 1901a or the tuner 1901b. The AV decoder 1905a and the AV decoder 1905b A PES packet can be output to either. Regarding the descrambler 1904, a PES packet can be output to both the AV decoder 1905a and the AV decoder 1905b.

  Next, FIG. 19 shows a conceptual diagram corresponding to the hardware configuration shown in FIG. 14 to which the adapter is physically connected. The terminal device 2000 includes a tuner 2001, a PID filter 2002, a section filter 1803, an AV decoder 1805, a display / speaker 1806, and a primary storage unit 1807. Further, an adapter 1511 is physically connected to the terminal device 2000, and the adapter 1511 has a descrambler 2004. The device identified by the same number as in FIG. 17 has the same function as in FIG. 17 differs from the terminal in FIG. 17 in the physical and logical connection locations and functions of the descrambler. In FIG. 17, the descrambler 1804 exists in the TS decoder 1202, and descrambles the PES packet output from the PID filter 1802 and the MPEG2 section using the descrambling key designated by the CPU 1206. On the other hand, in FIG. 19, the descrambler 2004 is directly and physically connected to the tuner 2001, and an MPEG2 transport stream demodulated by the tuner 2001 is input. The descrambler 2004 extracts a TS packet having a PID designated by the CPU 1506, extracts a key necessary for descrambling from the MPEG2 transport stream, and performs descrambling. The MPEG2 transport stream that has been descrambled by the descrambler 2004 is input to the TS decoder, and thereafter, the processing flows in the same manner as in FIG. The PID filter 2002 can extract the TS packet and configure the PES packet and the MPEG2 section with respect to the MPEG2 transport stream input from the descrambler 2004.

  Next, FIG. 20 shows a conceptual diagram when an adapter is physically connected to a device having a plurality of tuners and AV decoders, as shown in FIG. The terminal device 2100 includes a tuner 2101a and a tuner 2101b, a PID filter 2102, a section filter 1803, AV decoders 1905a and 1905b, a display / speaker 1906, and a primary storage unit 1807. Further, an adapter 1611 is physically connected to the terminal device 2100, and the adapter 1611 has a descrambler 2104. The device identified by the same number as in FIG. 17 or FIG. 18 has the same function as that in FIG. 17 or FIG. The difference from FIG. 18 is the physical and logical connection locations and functions of the descrambler 2104. The function of the descrambler 2104 is the same as that of the descrambler 2004 except that a plurality of MPEG2 transport streams can be input / output. The tuner 2101 a and the tuner 2101 b input the MPEG2 transport stream to the descrambler 2104. The descrambler 2104 inputs the descrambled MPEG2 transport stream to the TS decoder 1602. The PID filter 2102 can extract a TS packet and configure a PES packet and an MPEG2 section for any MPEG2 transport stream input from the descrambler 2104.

The hardware configuration in which the POD shown in FIG. 16 is present is the same as that shown in FIG.
Next, a conceptual relationship between the hardware and software described above will be described. FIG. 21 is a conceptual diagram showing the relationship between hardware and software.

  As shown in FIG. 21, the terminal apparatus executes hardware 2211 as a lower layer, OCAP instruction group 2214 that is an API as a middle layer, and controls OCAP software (middleware) 2212 that controls the hardware 2211, and OCAP as an upper layer. An OCAP application program 2213 that provides a predetermined operation using an instruction group 2214 or the like is provided.

Next, the program operation procedure on the terminal device will be described. FIG. 22 is an example of a configuration diagram of a program stored in the ROM 1209 and executed by the CPU 1206.
The program 2200 includes a plurality of subprograms, and specifically includes an OS 2201, an EPG 2202, a Java (registered trademark) VM 2203, a service manager 2204, and a Java library 2205.

  Here, the OS 2201, JavaVM 2203, and Java library 2205 are classified as OCAP software 2212 in FIG. 21. Further, the EPG 2202 and the service manager 2204 are classified into the OCAP application program 2213 in FIG. In this embodiment, the OS 2201 and the like are also classified as the OCAP software 2212, but they may be handled as separate layers.

  The OS 2201 is a subprogram that is activated by the CPU 1206 when the terminal device 1200 is powered on. The OS 2201 is an abbreviation for an operating system, and Linux, Windows (registered trademark), and the like are examples. The OS 2201 is a generic name for known techniques including a kernel 2201a and a library 2201b that execute other subprograms in parallel, and detailed description thereof is omitted. In the present embodiment, the kernel 2201a of the OS 2201 executes EPG 2202 and Java VM 2203 as subprograms. Further, the library 2201b provides a plurality of functions for controlling the constituent elements held by the terminal device 1200 to these subprograms.

  The tuning function is introduced as an example of the function. The tuning function receives tuning information including a frequency from another subprogram and passes it to the tuner 1201. The tuner 1201 can perform demodulation processing based on the given tuning information, and can deliver the demodulated MPEG2 transport stream to the TS decoder 1202. As a result, other subprograms can control the tuner 1201 through the library 2201b.

  The EPG 2202 includes a program display unit 2202a that displays a list of programs to the user and receives input from the user, and a playback unit 2202b that performs channel selection. Here, EPG is an abbreviation for Electric Program Guide. The EPG 2202 is activated by the kernel 2201a when the power of the terminal device 1200 is turned on. In the activated EPG 2202, the program display unit 2202a waits for an input from the user through the input unit 1210 of the terminal device 1200. Here, when the input unit 1210 is configured by the front panel shown in FIG. 12, when the user presses the EPG button 1307 of the input unit 1210, the identifier of the EPG button is notified to the CPU 1206. The program display unit 2202a of the EPG 2202 which is a subprogram operating on the CPU 1206 receives this identifier and displays the program information on the display 1205. FIGS. 23A and 23B are examples of the program guide displayed on the display 1205. FIG. Referring to FIG. 23A, program information is displayed on the display 1205 in a grid pattern. A column 2301 displays time information. A column 2302 displays a channel name “Channel 1” and a program broadcast in a time zone corresponding to the time in the column 2301. In “Channel 1”, the program “News 9” is broadcast from 9:00 to 10:30, and “Movie AAA” is broadcast from 10:30 to 12:00. Similarly to the column 2302, the column 2303 displays the channel name “channel 2” and the program broadcast in the time zone corresponding to the time in the column 2301. The program “Movie BBB” is broadcast from 9:00 to 11:00, and “News 11” is broadcast from 11:00 to 12:00. Reference numeral 2330 denotes a cursor. The cursor 2330 moves when the left cursor 1303 and the right cursor 1304 on the front panel 1300 are pressed. When the right cursor 1304 is pressed in the state of FIG. 23A, the cursor 2330 moves to the right, and becomes as shown in FIG. In addition, when the left cursor 1303 is pressed in the state of FIG. 23B, the cursor 2330 moves to the left, as shown in FIG.

  When the OK button 1305 on the front panel 1300 is pressed in the state of FIG. 23A, the program display unit 2202a notifies the playback unit 2202b of the identifier of “channel 1”. When the OK button 1305 on the front panel 1300 is pressed in the state of FIG. 23B, the program display unit 2202a notifies the playback unit 2202b of the identifier of “Channel 2”.

  Further, the program display unit 2202a periodically stores the program information to be displayed in the primary storage unit 1208 or the secondary storage unit 1207 from the broadcasting station side system 201. In general, it takes time to acquire program information from a broadcasting station side system. When the EPG button 1307 of the input unit 1210 is pressed, the program information stored in advance in the primary storage unit 1208 or the secondary storage unit 1207 is displayed, so that the program guide can be displayed quickly.

  The playback unit 2202b plays back the channel using the received channel identifier. The relationship between the channel identifier and the channel is stored in advance in the secondary storage unit 1207 as channel information. FIG. 24 is an example of channel information stored in the secondary storage unit 1207. Channel information is stored in tabular form. A column 2401 is a channel identifier. A column 2402 is a channel name. A column 2403 is tuning information. Here, the tuning information includes a frequency, a transfer rate, a coding rate, and the like, and is a value given to the tuner 1201. A column 2404 is a program number. The program number is a number for identifying a PMT defined in the MPEG2 standard. The PMT will be described later. Each row of rows 2411 to 2414 is a set of an identifier of each channel, a channel name, tuning information, and a program number. The row 2411 is a set including an identifier “1”, a channel name “channel 1”, tuning information having a frequency “150 MHz”, and a program number “101”. The playback unit 2202b delivers the received channel identifier to the service manager as it is to play back the channel.

  Further, when the user presses the upper cursor 1301 and the lower cursor 1302 of the front panel 1300 during playback, the playback unit 2202b receives the pressed notification from the input unit 1210 through the CPU 1206 and changes the channel being played back. . First, the playback unit 2202b stores the identifier of the channel currently being played back in the primary storage unit 1208. FIGS. 25A, 25B, and 25C are examples of channel identifiers stored in the primary storage unit 1208. FIG. In FIG. 25A, the identifier “3” is stored, and referring to FIG. 24, it is shown that the channel with the channel name “TV 3” is being reproduced. When the user presses the up cursor 1301 in the state of FIG. 25A, the playback unit 2202b refers to the channel information of FIG. 24 and plays back the channel with the channel name “channel 2” which is the previous channel in the table. In order to switch, the identifier “2” of the channel name “channel 2” is delivered to the service manager. At the same time, the channel identifier “2” stored in the primary storage unit 1208 is rewritten. FIG. 25B shows a state where the channel identifier has been rewritten. In addition, when the user presses the down cursor 1302 in the state of FIG. 25A, the playback unit 2202b refers to the channel information of FIG. 24 and sets the channel with the channel name “TV Japan” as the next channel in the table. In order to switch playback, the identifier “4” of the channel name “TV Japan” is delivered to the service manager. At the same time, the channel identifier “4” stored in the primary storage unit 1208 is rewritten. FIG. 25C shows a state where the channel identifier has been rewritten.

  The Java VM 2203 is a Java virtual machine that sequentially analyzes and executes a program written in the Java (TM) language. A program written in the Java language is compiled into an intermediate code called byte code that does not depend on hardware. The Java virtual machine is an interpreter that executes this bytecode. Some Java virtual machines also translate the bytecode into an execution format that can be understood by the CPU 1206, and then deliver the code to the CPU 1206 for execution. The Java VM 2203 is activated by designating a Java program to be executed by the kernel 2201a. In the present embodiment, the kernel 2201a designates the service manager 2204 as a Java program to be executed. Details of the Java language are described in many books such as the book “Java Language Specification (ISBN 0-201-63451-1)”. The details are omitted here. The detailed operation of JavaVM itself is described in many books such as “Java Virtual Machine Specification (ISBN 0-201-6451-X)”. The details are omitted here.

  The service manager 2204 is a Java program written in the Java language, and is sequentially executed by the Java VM 1203. The service manager 2204 can call or be called by another subprogram not described in the Java language through JNI (Java Native Interface). JNI is also described in many books such as the book “Java Native Interface”. The details are omitted here.

The service manager 2204 receives the channel identifier from the playback unit 2202b through JNI.
The service manager 2204 first hands over the channel identifier to the Tuner 2205c in the Java library 2205 and requests tuning. The Tuner 2205c refers to channel information stored in the secondary storage unit 1207 and acquires tuning information. Now, when the service manager 2204 hands over the channel identifier “2” to the Tuner 2205c, the Tuner 2205c refers to the row 2412 in FIG. 24 and acquires the corresponding tuning information “156 MHz”. The Tuner 2205c delivers tuning information to the tuner 1201 through the library 2201b of the OS 2201. The tuner 1201 demodulates the signal transmitted from the broadcasting station side system 201 according to the given tuning information, and delivers it to the TS decoder 1202.

  Next, the service manager 2204 requests the CA 2205d in the Java library 2205 to descramble. The CA 2205d gives information necessary for decoding to the descrambler 1804 in the TS decoder 1202 through the library 2201b of the OS 2201.

Next, the service manager 2204 gives a channel identifier to the JMF 2205a in the Java library 2205 and requests the reproduction of video / audio.
First, the JMF 2205a first acquires a PID for specifying video and audio to be reproduced from the PAT and PMT. PAT and PMT are tables that represent the program structure in the MPEG2 transport stream defined by the MPEG2 standard, and are embedded as an MPEG2 section in the payload of a TS packet included in the MPEG2 transport stream, along with audio and video. Is to be sent. For details, refer to the specifications. Here, only an outline will be described. PAT is an abbreviation of Program Association Table and is an MPEG2 section whose table_id is “0” that is stored in a TS packet with PID “0” and transmitted. The JMF 2205a designates the PID “0” and the CPU 1206 to the TS decoder 1202 through the library 2201b of the OS 2201 in order to obtain the PAT. The TS decoder 1202 performs filtering with PID “0” and table_id “0”, and passes them to the CPU 1206 through the primary storage unit 1208, whereby the JMF 2205a collects the PAT. FIG. 26 is a table schematically illustrating an example of collected PAT information. A column 2601 is a program number. Column 2602 is the PID. The PID in column 2602 is used to obtain the PMT. Rows 2611 to 2613 are a set of PIDs corresponding to channel program numbers. Here, three channels are defined. A row 2611 defines a set of a program number “101” and a PID “501”. Now, assuming that the identifier of the channel given to the JMF 2205a is “2”, the JMF 2205a refers to the row 2412 in FIG. 24 to obtain the corresponding program number “102”, and then the PAT row in FIG. Referring to 2612, PID “502” corresponding to program number “102” is acquired. PMT is an abbreviation of Program Map Table, and is an MPEG2 section whose table_id is “2” that is stored and transmitted in a TS packet with a PID defined by the PAT. In order to acquire the PMT, the JMF 2205a designates the PID acquired from the PAT and the table_id “2” to the TS decoder 1202 through the library 2201b of the OS 2201. Here, the designated PID is “502”. The TS decoder 1202 performs filtering with PID “502” and table_id “2”, and passes the result to the CPU 1206 through the primary storage unit 1208, whereby the JMF 2205a collects the PMT. FIG. 27 is a table schematically illustrating an example of collected PMT information. A column 2701 is a stream type. Column 2702 is the PID. In the TS packet of the PID specified by the column 2702, information specified by the stream type is stored in the payload and transmitted. A column 2703 is supplementary information. Rows 2711 to 2714 are a set of PID and the type of information being transmitted, called an elementary stream. A row 2711 is a set of the stream type “voice” and the PID “5011”, and represents that voice is stored in the payload of the TS packet with the PID “5011”. The JMF 2205a obtains video and audio PIDs to be reproduced from the PMT. Referring to FIG. 27, JMF 2205 a obtains audio PID “5011” from row 2711 and video PID “5012” from row 1712.

  Next, the JMF 2205a gives the AV decoder 1203 to the TS decoder 1202 as the acquired video / audio PID and output destination through the library 2201b of the OS 2201. The TS decoder 1202 performs filtering based on the given PID and output destination. Here, PID “5011” and “5012” TS packets are delivered to the AV decoder 1203. The AV decoder 1203 decodes the given PES packet and reproduces video / audio through the display 1205 and the speaker 1204.

  Finally, the service manager 2204 gives a channel identifier to the AM 2205b in the Java library 2205 and requests data broadcast reproduction. Here, the data broadcast reproduction means that a Java program included in the MPEG2 transport stream is extracted and executed by the JavaVM 2203. As a method for embedding a Java program in an MPEG2 transport stream, a method called DSMCC described in the MPEG standard document ISO / IEC13818-6 is used. Here, detailed description of DSMCC is omitted. The DSMCC method defines a method for encoding a file system composed of directories and files used in a computer in an MPEG2 transport stream TS packet using an MPEG2 section. The information of the Java program to be executed is embedded in the TS packet of the MPEG2 transport stream in a format called AIT, and transmitted as an MPEG2 section whose table_id is “0x74”. AIT is an abbreviation of Application Information Table defined in Chapter 10 of the DVB-MHP standard (formally, ETSI TS 101 812 DVB-MHP specification V1.0.2).

  First, the AM 2205b acquires the PAT and PMT in the same way as the JMF 2205a in order to acquire the AIT, and acquires the PID of the TS packet in which the AIT is stored. Now, if the given channel identifier is “2” and the PAT of FIG. 26 and the PMT of FIG. 27 are transmitted, the PMT of FIG. 27 is obtained in the same procedure as the JMF 2205a. The AM 2205b extracts the PID from the elementary stream having the stream type “data” and the supplementary information “AIT” from the PMT. Referring to FIG. 27, the elementary stream in row 2713 corresponds, and PID “5013” is acquired.

  The AM 2205b gives the AIT PID and table_id “0x74” to the TS decoder 1202 through the library 2201b of the OS 2201. The TS decoder 1202 performs filtering with the given PID and table_id, and passes the result to the CPU 1206 through the primary storage unit 1208. As a result, the AM 2205b can collect AIT. FIG. 28 is a table schematically showing an example of collected AIT information. A column 2801 is an identifier of the Java program. Column 2802 is Java program control information. The control information includes “autostart”, “present”, “kill”, etc., “autostart” means that the terminal device 1200 automatically executes this program immediately, and “present” means that it is not automatically executed. “Kill” means to stop the program. A column 2803 is a DSMCC identifier for extracting a PID including a Java program in the DSMCC format. A column 2804 is a program name of the Java program. Lines 2811 and 2812 are information sets of Java programs. The Java program defined in the row 2811 is a set of an identifier “301”, control information “autostart”, a DSMCC identifier “1”, and a program name “a / TopXlet”. The Java program defined in the row 2812 is a set of an identifier “302”, control information “present”, a DSMCC identifier “1”, and a program name “b / GameXlet”. Here, two Java programs have the same DSMCC identifier, which indicates that two Java programs are included in a file system encoded in one DSMCC format. Here, only four pieces of information are defined for the Java program, but more information is actually defined. For details, refer to the DVB-MHP standard.

  The AM 2205b finds the “autostart” Java program from the AIT, and extracts the corresponding DSMCC identifier and Java program name. Referring to FIG. 28, AM 2205b extracts the Java program on line 2811 and obtains the DSMCC identifier “1” and the Java program name “a / TopXlet”.

  Next, the AM 2205b uses the DSMCC identifier acquired from the AIT to acquire the PID of the TS packet storing the file system in the DSMCC format from the PMT. Specifically, the PID of the elementary stream in which the stream type is “data” in the PMT and the DSMCC identifier of the supplemental information matches is acquired.

Now, assuming that the DSMCC identifier is “1” and the PMT is FIG. 27, the elementary streams in the row 2714 match, and the PID “5014” is extracted.
The AM 2205b designates the PID and section filter condition of a TS packet that transmits an MPEG2 section in which data is embedded in the TS decoder 1202 in the DSMCC format through the library 2201b of the OS 2201. Here, PID “5014” is given. The TS decoder 1202 performs filtering of the DSMCC MPEG2 section using the given PID, and passes the filtered data to the CPU 1206 through the primary storage unit 1208. As a result, the AM 2205b can collect necessary DSMCC MPEG2 sections. The AM 2205b restores the file system from the collected MPEG2 section according to the DSMCC method, and stores it in the primary storage unit 1208. The extraction of data such as the file system from the TS packet in the MPEG2 transport stream and saving it in the storage means such as the primary storage unit 1208 and the secondary storage unit 1207 is hereinafter referred to as download.

  FIG. 29 is an example of a downloaded file system. In the drawing, a circle represents a directory, a square represents a file, 2901 is a root directory, 2902 is a directory “a”, 2903 is a directory “b”, 2904 is a file “TopXlet.class”, and 2905 is a file “GameXlet.class”. is there.

  Next, the AM 2205 b delivers the Java program to be executed from the file system downloaded to the primary storage unit 1208 to the Java VM 2203. If the name of the Java program to be executed is “a / TopXlet”, the file “a / TopXlet.class” with “.class” added to the end of the Java program name is the file to be executed. “/” Is a delimiter between directories and file names. With reference to FIG. 29, the file 2904 is a Java program to be executed. Next, the AM 2205b delivers the file 2904 to the Java VM 2203.

  The method of referring to the Java program to be executed by the AM 2205b is not limited to the AIT method. In OCAP that is expected to be used in the US cable system, XAIT that describes application reference information is used in the OOB described in FIG. In addition, the method of starting what was recorded beforehand in ROM1209, starting what was downloaded and memorize | stored in the secondary memory | storage part 1207, etc. can be considered.

The Java VM 2203 executes the delivered Java program.
When the service manager 2204 receives an identifier of another channel, the service manager 2204 stops the execution of the video / audio and the Java program being reproduced through each library included in the Java library 2205 through each library included in the Java library 2205, Based on the newly received channel identifier, video / audio playback and Java program execution are performed.

  The Java library 2205 is a set of a plurality of Java libraries stored in the ROM 1209. In this embodiment, here, the Java library 2205 includes a JMF 2205a, an AM 2205b, a Tuner 2205c, a CA 2205d, a Section Filter 2205e, a device manager 2205f which is a device management means, and the like.

Next, the device manager 2205f that is the basis of the present invention will be described.
The program described in the Java language that is activated as described above can realize various functions. The Java program realizes its function using the Java library 2205. The Java library 2205 includes a device manager 2205f that manages devices related to the digital broadcast receiving apparatus. The device manager 2205f has a function of logically connecting a plurality of devices and a function of providing information related thereto.

  The hardware configuration examples shown in FIGS. 11 to 16, the device configurations corresponding to the hardware configurations, and the input / output of each device as shown in FIGS. The hardware used in the process of extracting necessary information from the digital broadcast signal is limited to some extent. In the present embodiment, the “tuner”, “PID filter”, “section filter”, “descrambler”, and “AV decoder” are regarded as devices used for broadcast signal processing, and the control function is provided to the Java program. FIG. 11 is a hardware configuration diagram, and the number of devices in this embodiment conforms to FIG. The AV decoder 1203 has a function of simultaneously decoding video and audio, and can simultaneously accept a PES packet that transmits video and a PES packet that transmits audio. It is assumed that the number of PID filters existing in the TS decoder 1202 is X, the number of section filters is Y, and the number of descramblers is Z. If there are a plurality of devices of the same type, all of them can be logically connected to any device as long as they are physically connected according to the order represented in FIG. In other words, all PID filters can be logically connected to the tuner, all descramblers can be logically connected to all PID filters, and all section filters are logically connected to all PID filters and all descramblers. The AV decoder can be logically connected to all PID filters and all descramblers. FIG. 30 shows device logical connection paths that are possible under this situation. FIG. 30A shows a device logical connection path used when reproducing video and audio, and is used when reproducing video and audio transmitted by an unscrambled PES packet. FIG. 30B shows a device logical connection path used when reproducing video and audio, and is used when reproducing video and audio transmitted by a scrambled PES packet. FIG. 30 (c) shows a device logical connection path used when accessing data transmitted by the MPEG2 section, and is used when accessing data transmitted by an unscrambled MPEG2 section. FIG. 30 (d) shows a device logical connection path used when accessing data transmitted by the MPEG2 section, and is used when accessing data transmitted by the scrambled MPEG2 section. Using any of the four paths shown in FIG. 30, the Java program can access the broadcast signal. FIG. 31 shows an overall conceptual diagram of the logical connection in the present embodiment. In this embodiment, since the hardware configuration is the same as that in FIG. 11, there is one tuner 1801 and one AV decoder 1805, and there are a plurality of PID filters 1802, section filters 1803, and descramblers 1804, and the order is complied with. And logically connected to each other.

  The Java program can form a device logical connection path by accessing the device manager 2205f. In the present embodiment, the device manager 2205f is configured as shown in FIG. The device manager 2205f includes six modules: a device basic information management unit 3201, a device object management unit 3202, a device physical connection management unit 3203, a device logical connection management unit 3204, a device logical connection unit 3205, and a device logical connection release unit 3206.

  The device basic information management unit 3201 holds information on the type and number of devices handled by the device manager 2205f and the device alone. The device basic information management unit 3201 holds information in the primary storage unit 1208, the secondary storage unit 1207, or the ROM 1209, and is managed by the device manager 2205f. Further, it may be managed on dedicated hardware such as a register.

  A device object management unit 3202 manages a one-to-one correspondence between devices and objects representing the devices. The device object management unit 3202 holds information in the primary storage unit 1208 and is managed by the device manager 2205f. Further, it may be managed on dedicated hardware such as a register.

  A device physical connection management unit 3203 manages physical connection information of devices on the hardware configuration. For example, in FIG. 17, the tuner 1801 is physically connected to the PID filter 1802, and the PID filter 1802 is physically connected to the tuner 1801, the section filter 1803, the descrambler 1804, and the AV decoder 1805. To do. The device physical connection management unit 3203 basically stores information in the primary storage unit 1208, the secondary storage unit 1207, or the ROM 1209, and is managed by the device manager 2205f. Further, as an alternative implementation, an implementation may be adopted in which the state of the device itself is used as a device physical connection management unit, and when the physical connection state needs to be acquired, the physical connection configuration itself on the hardware of the device is checked. Further, it may be managed on dedicated hardware such as a register.

  A device logical connection management unit 3204 manages the logical connection state of devices. The device logical connection management unit 3204 basically holds information in the primary storage unit 1208 and is managed by the device manager 2205f. As an alternative implementation, the device logical connection management unit 3204 acquires the connection state by using the state of the device itself. It may be possible to check the device itself when it is necessary. Further, it may be managed on dedicated hardware such as a register.

  The device logical connection unit 3205 has a function of logically connecting devices. The device logical connection unit 3205 is realized as a library for connecting devices, stored in the ROM 1209, and executed by the CPU 1206.

  The device logical connection release unit 3206 has a function of releasing the logical connection of devices. The device logical connection release unit 3206 is realized as a library for releasing the connection of a device, stored in the ROM 1209, and executed by the CPU 1206.

Next, functions required for the device manager 2205f are listed, and the implementation procedure is shown while showing the relevance of each function to each of the units 3201 to 3206 in FIG.
As a first function of the device manager 2205f, a Java program is provided with a function for acquiring the type of device (hereinafter referred to as device type) managed by the device manager 2205f. In this embodiment, as described above, in order to handle “tuner”, “PID filter”, “section filter”, “descrambler”, and “AV decoder”, a function for acquiring the device type is provided to the Java program. By using this function, the Java program can acquire the device type of the device that can be logically connected by itself. The procedure for realizing this function is shown in the flowchart of FIG. First, when a device type acquisition request is received from the Java program (S3301), the device manager 2205f inquires the device basic information management unit 3201 to acquire all device types managed by the device basic information management unit 3201 (S3302). Return to the Java program (S3303).

  As a second function of the device manager 2205f, a function for returning the number of devices managed by the device manager 2205f is provided to the Java program. In the present embodiment, only one tuner 1801 exists on the hardware for the tuner, so 1 is returned, and X is returned because there are X PID filters. Using this function, the Java program can obtain the number of devices existing on the hardware configuration for each device type. The procedure for realizing this function is shown in the flowchart of FIG. When a device type acquisition request is received from the Java program by specifying a device type (S3401), the device manager 2205f inquires of the device basic information management unit 3201 and acquires the number of devices that match the specified device type (S3402). ), The number of acquired devices is returned (S3403). In step S3401, there may be an implementation that does not receive the device type designation and returns the number of all devices present in the broadcast receiving apparatus.

  As a third function of the device manager 2205f, a function of returning a Java object (hereinafter referred to as a device object (device identifier)) corresponding one-to-one with a device managed by the device manager 2205f is provided. Since there is only one tuner 1801 in FIG. 17 in the present embodiment, an object corresponding to the tuner 1801 is returned in a one-to-one correspondence to the “device object acquisition request” whose device type is “tuner”. Since there are Y section filters in the present embodiment as described above, a “device object acquisition request” whose device type is “section filter” corresponds to each section filter on a one-to-one basis. Returns Y objects. Since the object returned by this function corresponds to the device, the object can be used as the device identifier when executing the Java program. For example, when a logical connection between a tuner and a PID filter is performed, a logical connection operation for a device object that expresses one of the X objects of the PID filter 1802 and a device object that expresses the tuner 1801 is directly performed by the tuner. This is interpreted as logically connecting 1801 and “PID filters corresponding one-to-one with a device object among X PID filters 1802”. Using this function, the Java program can obtain an identifier for a device existing on the hardware configuration. A procedure example for realizing this function is shown in the flowchart of FIG. First, a device type is designated from the Java program, and an “all device object acquisition request” is received (S3501). Then, the device manager 2205f inquires of the device object management unit 3202 and acquires all device objects corresponding to the device having the designated device type (S3502). Thereafter, all the acquired device objects are returned to the Java program (S3503).

  As a fourth function of the device manager 2205f, the device manager 2205f has a device logical connection possibility acquisition function for acquiring a determination result (logical connection possibility) as to whether or not logical connection between devices managed by the device manager 2205f is possible. Provide to Java program. For example, in this embodiment, as can be seen from FIG. 17, the section filter and the AV decoder are not directly physically connected, and thus cannot be logically connected. In this way, a function for acquiring whether or not the connection itself is possible is realized by specifying a device. Using this function, the Java program can know the possibility of logical connection between devices. FIG. 36 shows a procedure for realizing this function. First, the device manager 2205f specifies a device object corresponding to two devices whose logical connection possibility is to be examined from the Java program and receives a “device logical connection possibility acquisition request” (S3601). To obtain devices corresponding to the two designated device objects (S3602). Next, the device physical connection management unit 3203 is inquired to obtain physical connection states related to the two devices (S3603). The acquired physical connection state is judged (S3604), and if it is directly physically connected, "Yes" is returned (S3605), and if it is not directly physically connected, "No" is returned (S3606). Does nothing if not physically connected.

  As a fifth function of the device manager 2205f, the Java program is provided with a function of acquiring the logical connection state of the device managed by the device manager 2205f. For example, when a section filter is logically connected to a PID filter, if that section filter is logically connected to another PID filter, the device configuration in the device logical connection path changes, which affects the operation result of the device. Is undesirable. Using this function, the Java program can acquire the device status and whether or not the device is logically connected. FIG. 37 shows a procedure for implementing this function. When the device manager 2205f receives a “device logical connection state acquisition request” from the Java program by designating device objects corresponding to two devices whose logical connection states are to be checked (S3701), the device object management unit 3202 To obtain devices corresponding to the two device objects (S3702). Next, the device logical connection management unit 3204 is inquired to obtain a logical connection state between the two devices (S3703), and the result is returned to the Java program (S3704).

  As a sixth function of the device manager 2205f, a function for logically connecting devices managed by the device manager 2205f is provided to the Java program. When a device that can be logically connected is designated, the devices are logically connected. Using this function, the Java program performs logical connection of devices. A procedure for implementing this function is shown in FIG. The device manager 2205f designates a device object corresponding to two devices to be logically connected and receives a “device logical connection request” from the Java program (S3801), and inquires the device object management unit 3202 to designate A device corresponding to two device objects is obtained (S3802). Next, the device physical connection management unit 3203 is inquired to obtain the physical connection state of the two devices (S3803), and the logical connection possibility is determined (S3804). If the logical connection is possible, the device logical connection management unit 3204 is inquired (S3805), the logical connection state of the two devices is acquired, and the determination is made (S3806). If the two devices are not logically connected and one device is not logically connected to another device of the same device type as the other, the device logical connection unit 3205 is used. The two devices are logically connected (S3807), and the fact that the two devices are connected is recorded in the device logical connection management unit 3204 (S3808). The determination in S3806 will be described in more detail. First, if “a logical connection already exists between two devices”, it is useless to connect again, so nothing is done. Furthermore, if one of the two devices is logically connected to another device of the same device type as the other, forcibly logically connecting will destroy the existing device logical connection path. End up. For example, when the PID filter A and the section filter A are designated, the logical connection state is checked, and if the PID filter A is already connected to the section filter B, nothing is done. However, if the PID filter A is in a logical connection state with the tuner A, but is not logically connected to other section filters, it is not “same device type”, so the device logical connection path is not destroyed. Make a connection.

  As a seventh function of the device manager 2205f, a Java program is provided with a function of releasing a logical connection between devices managed by the device manager 2205f. Using this function, the Java program releases the logical connection of the device. A procedure for implementing this function is shown in FIG. When the device manager 2205f receives a “device logical connection release request” from the Java program by designating a device object corresponding to two devices whose logical connection is desired to be released (S3901), the device manager 2205f makes an inquiry to the device object management unit 3202. A device corresponding to the two specified device objects is obtained (S3902). Next, the device logical connection management unit 3204 is inquired to obtain the logical connection states of the two devices (S3903) and determine (S3904). If they are logically connected, the device logical connection release unit 3206 is used to release the connection between the two devices (S3905), and the device logical connection management unit 3204 records that the two devices are disconnected ( S3906). If it is not logically connected, nothing is done.

  FIG. 40 shows a procedure example in which the Java program performs logical connection of devices. The flowchart shown in FIG. 40 illustrates the procedure used when extracting data from a broadcast signal using three section filters. In the present embodiment, the Java program has in advance knowledge about devices necessary for using the section filter and the connection order of the devices. First, the device type is acquired (S4001). Next, it is confirmed whether a tuner, PID filter, or section filter is handled for the obtained device type (S4002). If all necessary device types are handled by the device manager 2205f, the number of devices is obtained for each device type (S4003). It is determined whether or not the number of devices actually present exceeds the number of devices to be used (in this example, whether or not there are 1 or more tuners, 3 or more PID filters, and 3 or more section filters) (S4004). In this case, a device object is acquired for each device type (S4005). Next, the possibility of logical connection between device objects is acquired (S4006), and it is investigated whether or not logical connection is possible with each other (S4007). Specifically, the logical connection possibility between the tuner and each PID filter and the logical connection possibility between each PID filter and each section filter are investigated. If all the devices can be logically connected, the logical connection status of each device is acquired (S4008). If an unconnected device is found (S4009), each device is logically connected (S4010). By following this procedure, the Java program can logically connect the devices to each other, and thereafter, using the “operation library for each device” such as the tuner 2205a existing in the Java library 2205, the desired function can be obtained. Realization is possible. In the determination procedure S4002, the determination procedure S4004, the determination procedure S4007, and the determination procedure S4009, if the conditions are not satisfied, the logical connection of the devices is impossible as it is. If the conditions are not satisfied in the determination procedure S4007 and the determination procedure S4009, it is possible to try the device objects acquired in S4005 if there is room. If the condition is not satisfied in the determination procedure S4009, it is possible to try again after releasing the logical connection between the existing devices using the device logical connection release function which is the seventh function of the device manager 2205f. It is.

  In the present embodiment, it is possible to delete the ROM 1209 by storing the contents stored in the ROM 1209 in the secondary storage unit 1207. Further, the secondary storage unit 1207 includes a plurality of sub-secondary storage units, and can be implemented even when individual sub-secondary storage units store different information. For example, one sub-secondary storage unit stores only tuning information, another sub-secondary storage unit stores the library 2201b of the OS 2201, and yet another sub-secondary storage unit stores the downloaded Java program. It is possible to divide in detail, such as.

  In the present embodiment, the downloaded Java program is stored in the secondary storage unit 1207. However, it is also possible to store the downloaded Java program in the primary storage unit 1208. When storing in the primary storage unit 1208, all stored information is erased when the power is turned off.

  The present invention has been described by taking a broadcast receiving apparatus as an example of the information processing apparatus. However, the present invention can also be applied to an information processing apparatus such as a personal computer or a mobile phone. Also, information that performs data processing (for example, recording processing, reproduction processing, etc.) in a recording medium for recording information such as CD, DVD, BD (Blue-ray Disc), DVHS, memory, etc. even if broadcast reception is not possible. Of course, the present invention can also be applied to a processing apparatus.

(Embodiment 2)
The hardware configuration of the first embodiment is based on FIG. 11, and the descrambler 1804 is assumed to exist in the TS decoder 1202. However, the physical connection order of devices handled by the device manager 2205f is not always constant. The hardware configuration of this embodiment conforms to FIG. In the hardware configuration shown in FIG. 14, as shown in the corresponding FIG. 19, the descrambler 2004 does not exist in the TS decoder 1502 and the descrambler 2004 exists in the adapter 1511. In this configuration, the physical connection order is different from that of the first embodiment. Even in such a case, the device physical connection management unit 3203 manages information related to the physical connection order of devices. When acquiring the device connection possibility, the device manager 2205f can acquire the device connection order by making an inquiry to the device physical connection management unit 3203 as in FIG. 36, and can make a determination in consideration thereof. By implementing such an implementation, the present invention can be applied to any hardware configuration without depending on the physical connection order of devices.

(Embodiment 3)
The hardware configuration of the first embodiment conforms to FIG. 11, and the device manager 2205f treats “tuner”, “PID filter”, “section filter”, “descrambler”, and “AV decoder” as devices. However, in FIG. 11, there are other devices such as “display” and “speaker”. In addition, devices other than those shown in FIGS. 11 and 17 may exist. For example, the TS decoder 1202 existing in FIG. 11 includes a “switch” device that outputs the input MPEG2 transport stream to other devices physically connected to the TS decoder 1202 in addition to the devices existing in FIG. There is a case. In addition, there is a device that deletes unnecessary information from the input MPEG2 transport stream according to the designation of the CPU 1206 and sends a partial TS called “partial TS” to another device physically connected to the TS decoder 1202. There is also. In an HDD recorder having an HDD (Hard Disk Drive), “HDD” exists as a device that uses MPEG2 transport stream as input, and for DVD recorder, “DVD media control device” receives MPEG2 program stream as input. Exists as a device. As described above, there are various devices in the broadcast receiving apparatus in addition to the devices handled in the first embodiment.

  For example, a hardware configuration as shown in FIG. 41 is also possible. In this hardware configuration, in addition to the configuration of FIG. 11, an HDD 1221 to which an MPEG2 transport stream is input and an external output unit 1222 that outputs the MPEG2 transport stream to a network or the like are provided.

  The device manager 2205f of this embodiment can also handle these pieces of information. For this purpose, it is sufficient that each unit of the device manager 2205f manages information indicating that they are handled as devices. Specifically, the device basic information management unit 3201 increases the information of a single device, the device object management unit 3202 increases the set of devices and device objects, and the physical management of the device physical connection management unit 3203 manages. The connection information is increased, the device logical connection management unit 3204 manages logical connection information regarding the added device, and the device logical connection unit 3205 and the device logical connection release unit 3206 are changed to handle the added device. In another embodiment, when a module is further added in the device manager, the present invention can be applied by managing information on the added device.

  As described above, according to the present invention, it is possible to easily handle other devices without changing the basic configuration relationship of each unit in the device manager 2205f or the implementation sequence of each function of the device manager 2205f. is there.

(Embodiment 4)
In the first embodiment, “tuner”, “PID filter”, “section filter”, “descrambler”, and “AV decoder” are listed as devices managed by the device manager 2205f. However, there are cases in which there is no need to connect in particular, and there are those that need to be managed implicitly. In FIG. 30, since the PID filter is always used by being connected to either the section filter or the AV decoder, the flexibility is somewhat impaired. However, “PID filter is connected to either the section filter or the AV decoder in advance”. It is also possible to abstractly recognize that there are two types of devices, “PID filter and section filter” and “PID filter and AV decoder”. For example, in the case where a section filter is used, in the first embodiment, it is necessary to connect three types of devices called “tuner”, “PID filter”, and “section filter”. It is only necessary to connect two types of devices called “PID filter and section filter”, and the convenience of the Java program can be improved. Actually, in the OCAP / DVB-MHP specification, for example, regarding the section filter, it is assumed that the “section filter is connected to the PID filter in advance”, and the “PID filter and section filter” pair is abstracted as one type of device. It has become. As described above, the present invention is applicable even when a device logically connected in advance is abstracted as one device.

  In this embodiment, all the modules 3201 to 3206 existing in the device manager 2205f recognize the actual device pair as one device and perform recording, thereby realizing the above function. By implementing such an implementation, it is possible to improve the affinity between the concept of the device manager in the present invention and other existing libraries.

(Embodiment 5)
In the first embodiment, the device manager 2205f has a device number acquisition function as a second function. This function can know the number of devices that match each device type. However, the number of devices can also be acquired by counting the number of device objects obtained using the device object acquisition function which is the third function of the device manager 2205f. That is, the device number acquisition function is not an essential function.

  In the present embodiment, the device manager 2205f does not have a device number acquisition function which is the second function. The Java program can acquire the number of devices by counting the number of device objects acquired using the device object acquisition function which is the third function.

(Embodiment 6)
In the first embodiment, the device manager 2205f provides a device type acquisition function, which is a first function, to the Java program. However, particularly in the middleware specification in DVB-MHP / OCAP, the type of device handled by the middleware may be specified in the specification. In such a case, it is sufficient to use a device type determined by such specifications as a device type specified to the device manager 2205f.

  In the present embodiment, the device manager 2205f does not have a device type acquisition function that is the first function. In the present embodiment, the device manager 2205f does not have a device type acquisition function which is the first function, and the Java program instructs the device manager 2205f by using a predetermined device type.

(Embodiment 7)
In the sixth embodiment, the device manager 2205f does not provide the device type acquisition function which is the first function, and uses the device type defined by the middleware that can be used by the Java program as the device type specified to the device manager. Yes. Furthermore, in the DVB-MHP / OCAP specification, there is a library that can return a device object that represents a device in a one-to-one relationship. For example, a tuner control library existing in DVB-MHP / OCAP middleware has a function of providing a device object corresponding to a tuner existing on a broadcast receiving apparatus, and a Java program uses this function, It is possible to obtain a device object. This function is originally supposed to be specified to specify a tuner when using the function of the tuner control library. However, the device object described in the first embodiment is capable of specifying a device. Has the same function.

  The device manager 2205f in the present embodiment does not hold the device type acquisition function that is the first function and the device object acquisition function that is the third function. In the present embodiment, the Java program operating on the broadcast receiving apparatus can specify a device object acquired from the middleware as a device identifier when using each function of the device manager 2205f. In its internal implementation, the device manager 2205f cooperates with other libraries of middleware, and by sharing the device object management unit 3202 with other libraries, the device object returned by the other library can be implemented so that the device manager 2205f can be designated. is there.

(Embodiment 8)
In the first embodiment, the device manager 2205f has a device logical connection possibility acquisition function as a fourth function. This function is used by the Java program operating on the broadcast receiving apparatus to determine whether or not the device can be logically connected before performing the logical connection of the device, as used in step S4006 of FIG. . Whether or not the logical connection of the device is possible is acquired by inquiring of the device physical connection management unit 3203 as shown in the procedure S3603 of FIG. However, as shown in the procedure S3803 and the procedure S3804 in FIG. 38, the device logical connection possibility is determined in the implementation of the device logical connection function which is the sixth function of the device manager 2205f. If a device that is not possible is specified, the device is not logically connected. In other words, the determination of device logical connection possibility is an optional procedure. In the case of the device logical connection release function, in step S3903 in FIG. 39, the device logical connection management unit 3204 is inquired to check the device logical connection state, and the logical connection is released only when the device logical connection is established. In particular, it is not necessary to determine the possibility of device logical connection.

  The device manager 2205f in the present embodiment does not have a device logical connection possibility acquisition function which is a fourth function. Even in such a case, the Java program operating on the broadcast receiving apparatus automatically determines the possibility of logical connection of devices when using the device logical connection function. If the device logical connection function, which is the sixth function, is implemented so as to return a result, if the device logical connection is not possible, the Java program will notify the result notification when the device logical connection function is used. It is possible to know.

(Embodiment 9)
In the embodiment described so far, the device manager 2205f has a device logical connection state acquisition function as the fifth function. This function is used to determine whether or not the inter-device logical connection has already been established before the Java program operating on the broadcast receiving apparatus performs the logical connection or disconnection of the device, as used in step S4008 of FIG. Used to know. The logical connection state of the device is acquired by making an inquiry to the device logical connection management unit 3204 as shown in procedure S3703 of FIG. However, the device logical connection state check is not necessarily required before using the device logical connection function and the device logical connection release function. When the device logical connection function is implemented in the sequence shown in FIG. 38, the logical connection state is implicitly checked when the devices are logically connected. When the device logical connection release function is used, the determination of the device logical connection state is implicitly performed before the logical connection is released in step S3903 in FIG. That is, the acquisition of the device logical connection state is not an essential function for using the device logical connection function and the device logical connection release function, and the device logical connection and logical connection release using the device manager 2205f is possible even when the device logical connection state does not exist.

  The device manager 2205f in the present embodiment does not have a device logical connection state acquisition function which is a fifth function. When using the device logical connection function and the device logical connection release function, the Java program operating on the broadcast receiving apparatus can use each function without checking the device logical connection state. In this case, however, the device manager 2205f does not have a function for acquiring the logical connection state of the device. Therefore, the sixth function and the seventh function of the device manager 2205f are the device logical connection function and the device logical connection release function. It is necessary for the Java program itself to manage the information on the device logical connection path established by using.

(Embodiment 10)
In the first embodiment, there is a premise that all devices can be logically connected as long as they are physically connected. However, in an actual hardware configuration, due to hardware specifications, even a device that is often physically connected cannot be logically connected depending on the logical connection status of other devices on the broadcast receiver. May exist. FIG. 13 is used as the reference hardware configuration of the tenth embodiment. In the hardware configuration of FIG. 13, there are two tuners 1401a and 1401b, and AV decoder 1403a and AV decoder 1403b. Also in this case, the device logical connection path is as shown in FIGS. 30A to 30D, and the tuner and the AV decoder are connected with the PID filter and the descrambler interposed therebetween.

  Under such circumstances, in the present embodiment, the hardware specification of the TS decoder 1402 is that “PES packets obtained from the MPEG2 transport stream input from the same tuner cannot be output to a plurality of AV decoders simultaneously”. Suppose a default exists. Specifically, for example, while the PES packet selected using the PID filter from the MPEG2 transport stream input from the tuner 1401a to the TS decoder 1402 is output to the AV decoder 1403a, it is different from the same MPEG2 transport stream. PES packets selected using the PID filter cannot be output to the AV decoder 1403b. Under such an environment, the connection possibility between the PID filter and the AV decoder is dynamically changed depending on the logical connection state between the tuner and the PID filter. This is because the connection possibility between the PID filter and the AV decoder is also changed depending on the connection between the tuner and the PID filter.

  In such a case, information that the device manager must newly manage is “connection condition between PID filters and AV decoder”. For example, under the current environment, when a PID filter and an AV decoder are logically connected, the condition for enabling the logical connection is “specified PID filter is not logically connected to any of the tuners” or “specified PID. The filter is logically connected to the tuner, but the tuner is not logically connected to another PID filter "or" The designated PID filter is logically connected to the tuner, and the tuner is logically connected to another PID filter. However, the separate PID filter is not logically connected to the separate AV decoder.

  In this embodiment, a device logical connection condition management unit is introduced as a new component in the device manager 2205f. The device logical connection condition management unit manages the logical connection conditions of the devices as described above, and makes it possible to acquire the device logical connection conditions by accessing the device logical connection condition management unit when the device manager 2205f is necessary. The device logical connection condition management unit holds information in the primary storage unit 1208, the secondary storage unit 1207, and the ROM 1209, and is managed by the device manager 2205f.

  FIG. 42 shows a sequence when the device manager 2205f receives a “device logical connection possibility acquisition request” from the Java program. When the device manager 2205f receives the “device logical connectability acquisition request” issued by the Java program (S4101), it accesses the device object management unit 3202 to obtain devices corresponding to the two specified device objects (S4102). ). Next, the device physical connection management unit 3203 is inquired to obtain the physical connection state of the corresponding two devices (S4103). If the physical connection is established (S4104), the device logical connection condition introduced in this embodiment is used. The management unit is inquired to acquire device logical connection conditions related to the logical connection of the two devices (S4105). Next, according to the acquired device logical connection condition, the corresponding device logical connection state is acquired from the device logical connection management unit 3204 (S4106). It is determined whether or not the device logical connection state matches the device logical connection condition (S4107). If the device logical connection state matches, “Yes” is returned (S4108). If the conditions are not satisfied in the determination procedure S4104 and the determination procedure S4107, “impossible” is returned (S4109). In the example of the PID filter and the AV decoder, “designated PID filter is not logically connected to any tuner” or “designated PID filter and tuner are logically connected in procedure S4105. "Not connected" or "designated PID filter and tuner are logically connected, and the tuner is logically connected to another PID filter, but the PID filter is logically connected to an AV decoder different from the designated one. Get logical connection condition "not done". Accordingly, in step S4106, the logical connection state between the combinations of devices appearing in the logical connection condition is checked, and in the determination procedure S4107, it is determined whether the logical connection condition is satisfied.

  When the device manager 2205f receives a “device connection request” from the Java program, the condition acquisition using the device physical connection management unit 3203 in FIG. 38 is performed (S3803) as in the logical connection possibility acquisition sequence in FIG. In addition, according to the device connection condition acquired from the device connection condition management unit, the connection between other devices is investigated using the device logical connection management unit 3204, and the possibility of connection is determined after combining the results. In this case, if the connection is impossible due to the determination based on the connection condition, an error expressing that the connection is impossible due to the connection condition may be returned to the Java program.

By implementing such an implementation, the present invention can also be applied to a hardware configuration in which the connection possibility is dynamically changed according to the connection state of the device.
(Embodiment 11)
In the first embodiment, there is a restriction that each device (PID filter, section filter, descrambler) in the TS decoder 1202 allows only one-to-one logical connection. However, there are actually TS decoders that allow one-to-many logical connections for each device. There are also hardware configurations in which the maximum number of connections between devices is predetermined. In the present embodiment, it is assumed that there is a default such that a plurality of section filters can be logically connected per PID filter, but up to five.

  In such an environment, the device manager 2205f must manage the “maximum number of logical connections between devices”. In this environment, the condition is that “PID filter can be logically connected to 5 section filters simultaneously”.

  In this embodiment, a device logical connection maximum number management unit is introduced as a new component in the device manager 2205f. As described above, the device logical connection maximum number management unit manages the maximum number of inter-device logical connections such as how many logical connections a device can form with a device, and requires a device manager 2205f. Sometimes you can access and get the maximum number of device logical connections. The device logical connection maximum number management unit stores information in the primary storage unit 1208, the secondary storage unit 1207, and the ROM 1209, and is managed by the device manager 2205f. Moreover, it may be managed using dedicated hardware such as a register.

  FIG. 43 shows a sequence when the device manager 2205f receives a “device logical connection possibility acquisition request” from the Java program. When the device manager 2205f receives the “device logical connectability acquisition request” issued by the Java program (S4201), it accesses the device object management unit 3202 to obtain devices corresponding to the two specified device objects (S4202). ). Next, the device physical connection management unit 3203 is inquired to obtain the physical connection state of the corresponding two devices (S4203). If the physical connection is established (S4204), the maximum device logical connection introduced in this embodiment is used. The number management unit is inquired to obtain the maximum number of logical connections related to the logical connection of the two devices (S4205). Next, a device logical connection state is acquired from the device logical connection management unit 3204 in order to obtain the number of logical connections that already exist (S4206). It is determined whether or not the number of logical connections is less than the maximum number of logical connections (S4207). If the condition is satisfied, "Yes" is returned (S4208). If the conditions are not satisfied in the determination procedure S4204 and the determination procedure S4207, “impossible” is returned (S4209). In the example of the PID filter and the section filter, the maximum logical connection number “5” is obtained in procedure S4205. Next, the logical connection state of the designated PID filter and the other section filter is acquired from the device logical connection management unit 3204, and the number of existing logical connections is obtained (S4206). Using these, the maximum number of logical connections is compared with the number of existing logical connections in the determination procedure S4207, and if the number of existing logical connections is smaller, “Yes” is returned (S4208).

  When the device manager 2205f receives a “device connection request” from the Java program, the condition acquisition using the device physical connection management unit 3203 in FIG. 38 (similar to the logical connection possibility acquisition sequence shown in FIG. 43) ( In addition to S3803), whether or not the maximum number acquired from the device logical connection maximum number management unit has been reached is investigated using the device logical connection management unit 3204, and the possibility of connection is determined after combining the results. If “Yes”, logical connection between devices is performed. If it is determined that the logical connection is impossible because the maximum number of device logical connections has been reached, an implementation may be made to return an error expressing that fact to the Java program.

  In the state shown in the present embodiment, a device having a maximum connection number of 2 or more can be included in a plurality of device logical connection paths and can be said to be “sharable”. If the Java program can know whether a certain device is “sharable”, it is not necessary to logically connect more devices than necessary, and efficient logical connection is possible from the viewpoint of device management. In the present embodiment, a device connection shareability acquisition function is provided to the Java program as the eighth function of the device manager 2205f. The Java program can use this function to know whether the device represented by the device object can be shared. A sequence diagram of the simplest implementation of this function is shown in FIG. The device manager 2205f that has received a “device connection shareability acquisition request” together with one device type and one device object designation from the Java program (S4301) first queries the device object management unit 3202 to obtain the corresponding device ( S4302). Next, the device logical connection maximum number management unit is inquired regarding the target device, and the maximum number of logical connections related to the specified device type is acquired (S4303). If this is 2 or more (S4304), it can be determined that two or more logical connections between devices that match the specified device type of the specified device can exist simultaneously and can be shared (S4305). As a method of expressing “sharable”, there is also a method of returning the maximum number of logical connections per se instead of returning “permitted” or “not permitted” to the Java program as described above. Even with such an implementation, the Java program can determine whether the device is “sharable”.

By implementing in this way, the present invention can be applied even on a hardware configuration in which the maximum number is set for simultaneous connection.
Note that it is naturally assumed that the device logical connection management unit described in the tenth embodiment and the device logical connection maximum number management unit described in the present embodiment exist simultaneously. In that case, both the determination of the logical connection conditions in FIG. 42 (S4105 to S4107) and the determination of the maximum number of logical connections (S4205 to S4207) in FIG. .

(Embodiment 12)
In the first embodiment, when the Java program inquires about the logical connection state using the logical connection state acquisition function, which is the fifth function of the device manager 2205f, information indicating whether or not the logical connection between the two devices is performed. Can only be obtained. However, there may be situations where a Java program wants to know what other devices are logically connected to a device.

  The device manager 2205f in the present embodiment extends the device object acquisition function, which is the third function, and provides a Java program with a function for acquiring information as to which device is logically connected to a certain device at that time. In this function, when a Java program designates one device object and issues a “device object acquisition request”, the device manager 2205 f that receives the device object includes information on the logical connection state managed by the device logical connection management unit 3204. The device corresponding to the device object designated from the above and the devices logically connected at that time are searched, and all the device objects corresponding to the found devices are returned. Furthermore, when the device type is specified by the Java program, only the devices having the specified device type are further selected from the devices that are logically connected at that time. Returns all device objects corresponding to the device.

  In the present embodiment, the Java program can acquire a device logically connected to a certain device with a single operation.

(Embodiment 13)
In the first embodiment, when the Java program inquires about the logical connection possibility by using the logical connection possibility acquisition function which is the fourth function of the device manager 2205f, the logical connection possibility between the two devices designated by the Java program. Can only be obtained. However, there may be situations where a Java program wants to know what other devices can logically connect to a device.

  The device manager 2205f in the present embodiment extends the device object acquisition function, which is a third function, and provides a Java program with a function for acquiring information as to which device can be logically connected to a certain device at that time. In this function, when a Java program designates one device object and issues a “device object acquisition request”, the device manager 2205 f that receives the device object includes information on physical connections managed by the device physical connection management unit 3203. The device that can be logically connected to the device corresponding to the specified device object is searched, and all the device objects corresponding to the found device are returned. Furthermore, when the device type is designated by the Java program, only those having the designated device type are further sorted, and all device objects corresponding to the sorted devices are returned.

  In the present embodiment, the Java program can acquire a device that can be logically connected to a certain device in one operation.

(Embodiment 14)
In the first embodiment, when the Java program uses the logical connection possibility acquisition function that is the fourth function of the device manager 2205f and the logical connection state acquisition function that is the fifth function, the two devices specified by the Java program It is possible to acquire only the logical connection possibility and the logical connection state. However, a Java program may want to know what devices can be connected to a device and which devices are not connected. In such a case, in the first embodiment, it is necessary to investigate the logical connection possibility and the logical connection state for each of the device objects acquired by specifying the device type.

  In this embodiment, the device object acquisition function, which is the third function of the device manager 2205f, is expanded, and to which device a certain device can be logically connected at that time and logically unconnected. Provides a Java program with a function to acquire information. In this function, when a Java program designates one device object and issues a “device object acquisition request”, the device manager 2205 f that receives the device object first stores information on physical connections managed by the device physical connection management unit 3203. The device corresponding to the specified device object is searched for a device that can be logically connected. Next, among the found devices, a logically unconnected device is searched, and all device objects corresponding to the obtained devices are returned. Furthermore, when the device type is designated by the Java program, only those having the designated device type are further sorted, and all device objects corresponding to the sorted devices are returned.

  In the present embodiment, the Java program can acquire a device that can be logically connected to a certain device and logically unconnected with a single operation.

(Embodiment 15)
In the first embodiment, the device logical connection state is determined within the implementation of the device logical connection function, which is the sixth function of the device manager 2205f. In this case, determination of the logical connection state of the device is performed in step S3806 of FIG. In the first embodiment, at this time, “whether the two specified devices are already logically connected” and “one of the two specified devices is the same device type as the other device” Are two types of determinations made. The former is because the connection state is not wasted, and the latter is because the device logical connection path is not changed.

  In the present embodiment, within the implementation of the device logical connection function, which is the sixth function of the device manager 2205f, in the determination of the logical connection state of the device performed in step S3806 in FIG. It only determines whether the space is already logically connected, and if it is already done, nothing is done. Even if one of the two devices is connected to another device of the same device type as the other, the original device logical connection path is automatically released and the newly specified two devices are replaced. Logically connect and record the new device logical connection path in the device logical connection management unit 3204.

  When this implementation is adopted, the device logical connection release function which is the seventh function of the device manager 2205f is not necessary. This is because, when a logical connection of devices is performed, even if an existing logical connection exists, it is automatically released.

  According to this embodiment, the Java program can construct a new device logical connection path without being aware of the existing device logical connection path. However, even if the device logical connection path that the Java program wants to leave intentionally is likely to be automatically released at the time of logical connection of the device, the Java program itself makes the device logical connection path and its configuration. It is necessary to manage device objects as elements.

(Embodiment 16)
In the first embodiment and the fifteenth embodiment, when the Java program performs logical connection and logical connection release using the sixth and seventh functions of the device manager 2205f, the device manager 2205f does not return the result.

  For example, in the case shown in FIG. 38, when the logical connection possibility is determined using the result returned by the device physical connection management unit 3203 (S3804) and when the logical connection state is determined (S3806), In the first and fifteenth embodiments, whether or not the logical connection processing has been performed or not, or the Java program cannot know the result is determined. .

  For example, in the case shown in FIG. 39, when the logical connection state is determined using the result returned by the device logical connection management unit 3204 (S3904), whether or not the logical connection release processing (S3905) is actually performed is determined. However, in the first embodiment, the Java program cannot know whether the logical connection release processing has been performed or has not been performed.

  In this embodiment, when the logical connection function and the logical connection release function which are the sixth and seventh functions of the device manager 2205f are used, whether or not the logical connection and the logical connection release are actually performed is determined by the Java program. Return in sync with execution. As for the logical connection function, in the sequence of FIG. 38, two types of results are returned: “device connection success” and “device connection failure”. There are two types of logical connection release functions: “device connection release success” and “device connection release failure” in the sequence of FIG.

(Embodiment 17)
In the sixteenth embodiment, when the Java program uses the sixth and seventh functions of the device manager 2205f to perform logical connection and logical connection release, the device manager 2205f determines whether the logical connection and logical connection release have been performed. return. However, in the sequence of FIG. 38, for example, the reason why the device is not connected is “cannot connect” determined in step S3804 or “already connected” determined in step S3806 and “ There are three types of "existing another device logical connection path", but the Java program cannot know the reason why the device connection was not made as a result of whether or not the device was connected.

  In this embodiment, when the device logical connection function and the device logical connection release function, which are the sixth and seventh functions of the device manager 2205f, are used, whether or not the logical connection is actually performed, and why is it not performed further? Returns synchronously the reason why it was not done. For example, in the case of the sequence shown in FIG. 38, four types of results are returned: “device logical connection successful”, “device cannot logically connect”, “device is already logically connected”, and “another device logical connection path exists”. It is. For example, in the case of the sequence of FIG. 39, there are two types of results: “device logical connection release successful” and “device is not in logical connection state”.

(Embodiment 18)
In the seventeenth embodiment, when the Java program makes a logical connection using the sixth function of the device manager 2205f, the device manager 2205f returns four types of results. However, among these, the result that “the device is already in logical connection” is equivalent to “device logical connection successful” because the logical connection between devices has been made in the post-processing state. is there.

  In the present embodiment, when the device logical connection function, which is the sixth function of the device manager 2205f, is used, the reason why the logical connection is actually made and if not, why is not done Is returned synchronously. However, if “device is already in logical connection”, a result indicating “device logical connection successful” is returned. In other words, for example, in the case of the sequence of FIG. 38, three types of results are returned: “device logical connection successful”, “device cannot logically connect”, and “another device logical connection path exists”.

(Embodiment 19)
In the sixteenth to eighteenth embodiments, when the Java program uses the function of the device manager 2205f, each function is realized by synchronous processing, and the Java program proceeds with execution while the device manager 2205f is processing each function. It is impossible. For example, when the Java program issues a “device logical connection request”, the device manager 2205f performs the logical connection processing of the device, while the Java program must wait until the logical connection processing by the device manager 2205f is completed. However, depending on the device handled by the device manager 2205f, there is a device that takes time for logical connection of devices. When such device connection processing is realized as asynchronous processing, the Java program is convenient for the Java program because other processing can proceed while the device manager 2205f performs device logical connection processing.

  In the present embodiment, asynchronous notification of results is performed for the functions realized by the device manager 2205f. Therefore, the device manager 2205f holds a device processing result notification listener registration function as a ninth function. When the device processing result notification listener uses the first to eighth functions of the device manager 2205f, the Java program registers with the device manager 2205f in order to receive the processing results asynchronously. In order to receive asynchronous notification, the Java program registers a device processing result notification listener for receiving asynchronous notification in the device manager 2205f prior to or simultaneously with the use of the function of the device manager 2205f. Thereafter, the Java program uses the function of the device manager 2205f. The device manager 2205f notifies the processing result to the Java program through the device processing result notification listener.

  In this embodiment, the device manager 2205f newly has a device listener management unit in order to register a device processing result notification listener. The device listener management unit is accessed by the device manager 2205f and provides a registered device processing result notification listener. The device listener management unit holds information in the primary storage unit 1208, the secondary storage unit 1207, or the ROM 1209, and is managed by the device manager 2205f.

  As an example of the asynchronous operation by the Java program used in the present embodiment, FIG. 45 shows a device logical connection sequence as the sixth function. First, the Java program 1 issues a “device processing result notification listener registration request” to the device manager 2205 f (S 4401), and the device manager 2205 f receives the device processing result notification listener of the Java program 1 together with the Java program 1. Then, it is registered in the device listener manager (S4402). Next, the Java program 1 issues a “device logical connection request” regarding the PID filter A and the AV decoder B to the device manager 2205f (S4403), and the device manager 2205f logically connects the PID filter A and the AV decoder B (S4404). ). The Java program 1 can proceed with its execution while the device manager 2205f performs the logical connection process between the PID filter A and the AV decoder B after the end of the procedure S4403. When the logical connection processing is completed, the device manager 2205f acquires the device processing result notification listener of the Java program 1 from the device listener management unit (S4405), and notifies the logical connection result (S4406).

  In the present embodiment, it is not necessary to make all the functions provided by the device manager 2205f asynchronous. For example, even if an implementation is applied in which only the device logical connection function, which is the sixth function of the device manager 2205f, and the device logical connection release function, which is the seventh function, perform asynchronous notification and other functions perform synchronous notification. Good.

  By using this embodiment, the Java program can be executed even while the time-consuming function of the device manager 2205f is used, and an efficient operation can be realized.

(Embodiment 20)
In the nineteenth embodiment, since the device processing result notification listener registered by the Java program is registered in the device manager 2205f without specifying a device object, the processing results for all devices are notified to the same device processing result notification listener. . However, depending on the Java program, there is a case where it is desired to register a device processing result notification listener that is different for each device.

  In the present embodiment, when the device manager 2205f uses the device processing result notification listener registration function as the ninth function, the Java program designates one device object together with the device processing result notification listener. The device manager 2205f records the Java program, the device processing result notification listener, and the device represented by the device object as a set in the device listener management unit. When the device manager 2205f performs notification, the device manager 2205f acquires a device processing result notification listener related to a device related to processing performed in advance from the device listener management unit, and notifies only the acquired device processing result notification listener. Do.

(Embodiment 21)
In the first embodiment, the device object acquired using the device object acquisition function, which is the third function of the device manager 2205f, is only used as an identifier for the device existing in the broadcast receiving apparatus, and information about the device itself. Do not hold. Therefore, the Java program itself must manage the device object group acquired by the Java program issuing a “device object acquisition request” to the device manager 2205f. For example, in the first embodiment, Y device objects can be acquired by specifying “section filter” as the device type and acquiring device objects. When managing these, the Java program must use a “device type” and an “index indicating the number of device object”. This is very inconvenient from the viewpoint of device object management.

  In the present embodiment, the device object itself stores information related to the device corresponding to the device object. At least all device objects hold “the device type of their own device” and “ID uniquely assigned within the device of the same device type”. As a result, the Java program can facilitate management because the device object itself holds information. Further, the device object can manage auxiliary information about the device object itself to further facilitate device management. For example, the device object may manage “device name”. By handling the name, the Java program can handle device management more variously. For example, the names “tuner A” and “tuner B” are assigned to the tuners 1401a and 1401b in FIG. 13, respectively, and the Java program can use these names when managing devices.

  These functions are realized by the device basic information management unit 3201 managing the type, ID, and name of each device. When the Java program acquires a device object, the device manager 2205f accesses the device basic information management unit 3201, acquires the name of the device, and returns a device object that is set in the device object.

(Embodiment 22)
In the first embodiment, the device object acquired using the device object acquisition function, which is the third function of the device manager 2205f, is used when the function of the device manager 2205f is used as an identifier for the device existing in the broadcast receiving apparatus. It is specified. In the twenty-first embodiment, the device object holds information for specifying the device corresponding to itself, and the Java program can acquire such information from the device object. In the present embodiment, the function of the device object is further expanded to give a function of using the function of the device manager 2205f through the device object. Specifically, among the functions of the device object 2205f, the device object acquisition function that is the third function, the device logical connection possibility acquisition function that is the fourth function, and the device logical connection state that is the fifth function Requests regarding the acquisition function, the device logical connection function as the sixth function, and the device logical connection release function as the seventh function are received and relayed to the device manager 2205f. At that time, it notifies the device manager 2205f of the device that it corresponds to one to one as the designated device.

  When the device object acquisition function, which is the third function, is used, the Java program can realize the functions defined in the twelfth embodiment, the thirteenth embodiment, and the fourteenth embodiment regarding the device object acquisition function. In the twelfth embodiment, by specifying one device object to the device manager 2205f and issuing a “device object acquisition request”, a device object in a logical connection state with the specified device can be acquired. In this case, in the present embodiment, it is possible to issue a “device object acquisition request” to the device object. The sequence in that case is shown in FIG. When the Java program issues a “device object acquisition request” to the device object (S4501), the device object that has received it designates itself to the device manager 2205f and relays the “device object acquisition request”. (S4502). The device manager 2205f acquires the device object of the device logically connected to the device represented by the device object (S4503), returns it to the original device object (S4504), and the device object returns it to the Java program (S4505). ). Similarly, when the Java program designates a device type, the device object 2205f is relayed to the device manager 2205f by designating the device type with itself and the device object acquisition request, and the device object returned from the device manager 2205f. To the Java program. In the thirteenth embodiment, a device object representing a device that can be logically connected to the specified device can be acquired by designating one device object to the device manager 2205f and issuing a “device object acquisition request”. is there. Also, in the fourteenth embodiment, by specifying one device object to the device manager 2205f and issuing a “device object acquisition request”, the specified device can be logically connected and logically disconnected. A device object representing a certain device can be acquired. Regarding these, the device object can receive the request, and the Java program can acquire the device object to be obtained in the sequence of FIG.

  When using the device logical connection possibility acquisition function, which is the fourth function, in the first embodiment, the Java program designates two device objects and acquires the logical connection possibility between the devices represented by them. . When the device object relays this, the Java program designates one device object for the device object and issues a “device logical connectability acquisition request”. When the device object receives it, it designates itself and the device object designated by the Java program, and relays a “device logical connection possibility acquisition request” to the device manager 2205f. The device manager 2205f acquires the logical connection possibility in the same sequence as in FIG. 36 of the first embodiment, and returns it to the original device object. The original device object returns the logical connection possibility received from the device manager 2205f to the Java program. Note that the sequence when the device manager 2205f acquires the logical connection possibility follows the information in the device logical connection condition management unit and the device logical connection maximum number management unit according to FIGS. good.

  When the device logical connection state acquisition function, which is the fifth function, is used, in the first embodiment, the Java program designates two device objects and acquires the logical connection state between the devices represented by them. When this is relayed by the device object, the Java program designates one device object and issues a “device logical connection state acquisition request” to the device object. When the device object receives it, it designates the device object designated by itself and the Java program, and relays a “device logical connection state acquisition request” to the device manager 2205f. The device manager 2205f acquires the logical connection state in the same sequence as in FIG. 37 of the first embodiment, and returns it to the original device object. The original device object returns the logical connection state received from the device manager 2205f to the Java program.

  When using the device logical connection function, which is the sixth function, in the first embodiment, the Java program designates two device objects and logically connects the devices represented by them. When the device object relays this, the Java program designates one device object and issues a “device logical connection request” to the device object. When the device object receives it, it designates the device object designated by itself and the Java program, and relays a “device logical connection request” to the device manager 2205f. The device manager 2205f is logically connected in the same sequence as in FIG. 38 of the first embodiment. If the device manager 2205f is an implementation that returns a logical connection result, the device object returns the connection result obtained from the device manager 2205f to the Java program. When the device manager 2205f has a device logical connection condition management unit and a device logical connection maximum number management unit, information held by the device manager 2205f is also used for determination when determining the possibility of logical connection before logical connection.

  When the device logical connection release function, which is the seventh function, is used, in the first embodiment, the Java program designates two device objects and releases the logical connection between the devices represented by them. When this is relayed by the device object, the Java program designates one device object for the device object and issues a “device logical connection release request”. When the device object receives it, it designates the device object designated by itself and the Java program, and relays a “device logical connection release request” to the device manager 2205f. The device manager 2205f releases the logical connection in the same sequence as in FIG. 39 of the first embodiment. If the device manager 2205f is an implementation that returns a logical connection release result, the device object returns the connection release result obtained from the device manager 2205f to the Java program.

  When using the device connection shareability acquisition function as the eighth function, in the eleventh embodiment, the Java program designates one device object and one device type, and the device represented by the designated device object is the designated device type. A determination result indicating whether or not a plurality of device logical connection paths can be set with the device is acquired. When the device object relays this, the Java program designates one device type and issues a “device connection shareability acquisition request” to the device object. The device object designates itself as the device type and device object designated by the Java program and relays the “device connection shareability acquisition request”. Similar to the eleventh embodiment, the device manager 2205f acquires device connection sharability and returns it to the device object. The device object returns the result obtained from the device manager 2205f to the Java program.

  In using the device processing result notification listener registration function, which is the ninth function, in the twentieth embodiment, the Java program designates a device processing result notification listener and one device object. When this is relayed by the device object, the Java program designates a device processing result notification listener and issues a “device processing result notification listener registration request” to the device object. The device object relays the “device processing result notification listener registration request” specifying the device processing result notification listener specified by the Java program and the device object itself. Similarly to the twentieth embodiment, the device manager 2205f records the device processing result notification listener in the device listener management unit in combination with the device and the Java program. Thereafter, when the Java program performs processing on the device, the result is notified to the device processing result notification listener.

  It is not necessary for the device object to hold all of the above functions. According to the configuration in which the device object relays a request from the Java program for each function, it is impossible for the device object to have a function that does not exist in the device manager 2205f. Further, even if the function exists in the device manager 2205f, it may be determined depending on the implementation as to which of the functions the device object relays.

(Embodiment 23)
In the first embodiment, the number of devices having the specified device type is returned when the number of devices in FIG. 34 is acquired (S3402). In the present embodiment, it is possible to obtain the number of all devices existing in the broadcast receiving apparatus without specifying the device type. This can be implemented by eliminating the designation of the device type in the procedure S3401, obtaining the numbers of all devices in the procedure S3402, and providing them to the Java program.

(Embodiment 24)
In the first embodiment, device objects corresponding to all devices having the designated device type are returned when the device object is acquired (S3502) in FIG. In the present embodiment, it is possible to acquire device objects corresponding to all devices existing in the broadcast receiving apparatus without specifying a device. This can be implemented by eliminating the designation of the device type in the procedure S3501 and acquiring device objects corresponding to all device types in the procedure S3502 and providing them to the Java program. Further, in this case, in order to provide the Java program with information indicating what the acquired device object represents, each device object needs to hold information about itself as in the twenty-first embodiment. At a minimum, the device type is retained.

(Embodiment 25)
The broadcast receiving apparatus assumed in the present invention can simultaneously execute a plurality of Java programs. Therefore, there may be a plurality of Java programs that change the logical connection state of the device. In that case, the Java program may want to know a change in the logical connection state of a certain device. For example, if the device that the Java program 1 wants to use is already logically connected by the Java program 2, the Java program 1 can know the timing when the Java program 2 releases the logical connection related to the device. There is no need to periodically check the logical connection status of the device, which is convenient.

  In the present embodiment, a device state change notification listener registration function is introduced as a tenth function of the device manager 2205f. An example of using this function is shown in FIG. First, the Java program 2 issues a “device logical connection request” for the PID filter A and the AV decoder B to the device manager 2205f (S4601), and logical connection is performed (S4602). After that, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C. However, since the Java program 2 has already made a logical connection for the PID filter, the logical connection fails (S4603). Therefore, the Java program 1 designates the device state change notification listener and the PID filter A and issues a “device state change notification listener registration request” (S4604). When the “device state change notification listener registration request” is received, the device manager 2205f stores the specified device state change notification listener and the device represented by the specified device object in the device listener management unit. In this example, the PID filter A and the device state change notification listener are paired and stored in the device listener management unit (S4605). The Java program 2 issues a device logical connection release request for the PID filter A and the AV decoder B (S4606), the device manager 2205f releases the connection (S4607), and the device listener management unit notifies the device status change regarding the PID filter A. A listener is acquired and notified (S4608). In that state, since no PID filter A should be logically connected, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C (S4609), and the device manager 2205f is logically connected. Is performed (S4610).

(Embodiment 26)
The broadcast receiving apparatus assumed in the present invention can simultaneously execute a plurality of Java programs. Furthermore, it is assumed that each Java program holds a priority. In such a case, it is natural from the viewpoint of device management that a device logical connection path constructed by a low priority Java program can be reconfigured by a high priority Java program. When a “device logical connection request” is issued to the device manager 2205f, if it is a logically unconnected device, the device logical connection management unit 3204 performs logical connection of the Java program that logically connects the devices. Record the priority. If the device is already in the logical connection state, the device manager 2205f checks the priority of the currently connected Java program held by the device logical connection management unit 3204, and if this is the Java that issued this "device logical connection request" When the priority of the program is higher, the logical connection is changed according to the current instruction, and the priority of the new Java program is recorded in the device logical connection management unit 3204.

  A specific sequence is shown in FIG. The Java program 1 and the Java program 2 are Java programs that operate simultaneously on the broadcast receiving apparatus, and the Java program 2 has a higher priority than the Java program 1. First, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder B (S4701). The device manager 2205f that received it logically connects the PID filter A and the AV decoder B in accordance with the request (S4702). Thereafter, the Java program 2 having higher priority than the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C (S4703). The device manager 2205f that received it notices that the PID filter A is already connected to the AV decoder B, and the Java program 1 that has already established the logical connection and the Java program that has issued a new logical connection request. 2, since the Java program 2 has a higher priority, the device manager 2205 f logically connects the PID filter A and the AV decoder C (S 4704).

(Embodiment 27)
In the twenty-sixth embodiment, the device logical connection is implicitly changed. However, when the Java program issues a “device logical connection request” or before the “device logical connection request” is issued, a device state change notification listener is sent to the device. By registering, it is possible to receive a notification regarding that the device logical connection path has been changed by a Java program other than itself.

  In this embodiment, the device listener management unit holds the device state change notification listener registered by the Java program. When the device manager 2205f receives the “device logical connection request” from the Java program, the designated device is already logically connected, and the device logical connection path is changed based on the priority investigation similar to that in the twenty-sixth embodiment. When the device program is deprived of the device logical connection path, an event is excited if the device state change notification listener is registered in the device listener management unit.

  A specific sequence is shown in FIG. The Java program 1 and the Java program 2 are Java programs that operate simultaneously on the broadcast receiving apparatus, and the Java program 2 has a higher priority than the Java program 1. First, the Java program 1 issues a “device state change notification listener registration request” for registering a device state change notification listener to the device manager 2205f (S4801), and the device manager 2205f that has received the device manager 2205f receives the device manager 2205f. A state change notification listener is registered (S4802). Next, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder B (S4803). The device manager 2205f that received it logically connects the PID filter A and the AV decoder B according to the request (S4804). Thereafter, the Java program 2 having a higher priority than the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C (S4805). The device manager 2205f receiving it notices that the PID filter A is already logically connected to the AV decoder B, and the Java program 1 that has already established the logical connection and the Java that has issued a new logical connection request. The priority of the program 2 is compared. Since the Java program 2 has a higher priority, the device manager 2205f connects the PID filter A and the AV decoder C (S4806). Furthermore, since the Java program 1 has registered the device state change notification listener in procedure S4801, the device manager 2205f notifies that the logical connection between the PID filter A and the AV decoder B to which the Java program 1 is connected has been released (S4807). .

(Embodiment 28)
According to the embodiment 27, when a Java program whose device logical connection is deprived of another Java program having a higher priority is continued as it is, the deprived Java program is terminated or the logical connection is released. In addition, the device status change notification listener can be used to receive an availability notification. The device logical connection management unit 3204 is a device of the Java program whose logical connection has been deprived even after the device manager 2205f has reconfigured the device logical connection path and notified the deprived Java program. The state change notification listener is held, and when the deprived Java program releases the logical connection or the execution ends, the device manager 2205f newly notifies the deprived Java program.

  A specific sequence is shown in FIG. The Java program 1 and the Java program 2 are Java programs that operate simultaneously on the broadcast receiving apparatus, and the Java program 2 has a higher priority than the Java program 1. First, the Java program 1 issues a “device state change notification listener registration request” for registering a device state change notification listener for receiving a device state change notification to the device manager 2205f (S4901). The device manager 2205f registers a device state change notification listener of the Java program 1 (S4902). Next, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder B (S4903). The device manager 2205f that received it logically connects the PID filter A and the AV decoder B according to the request (S4904). Thereafter, the Java program 2 having a higher priority than the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C (S4905). The device manager receiving it notices that the PID filter A is already logically connected to the AV decoder B, and the Java program 1 that has already established the logical connection and the Java program that has issued a new logical connection request. 2, since the Java program 2 has a higher priority, the device manager 2205 f logically connects the PID filter A and the AV decoder C (S 4906). Furthermore, since the Java program 1 has registered the device state change notification listener in procedure S4901, the device manager 2205f notifies that the logical connection between the PID filter A and the AV decoder B to which the Java program 1 is logically connected is released (S4907). ). Thereafter, when the Java program 2 issues a “device logical connection release request” between the PID filter A and the AV decoder C (S4908), the device manager 2205f releases the logical connection between the PID filter A and the AV decoder C (S4909). The program 1 is notified that the logical connection related to the PID filter A is possible (S4910).

  In FIG. 50, after the PID filter A and the AV decoder C are logically connected in accordance with a request from the Java program 2, the Java program 2 may end execution for some reason before releasing the logical connection. In this case, the device manager 2205f can notify the end of the Java program 2 from the AM 5005b that performs application management. In this case, the logical connection established by the Java program 2 is released. At this time, if there is a conflict with the Java program 1, a status change notification is sent to the device status change notification listener of the Java program 1.

(Embodiment 29)
In the twenty-eighth embodiment, when a Java program that has deprived a logical connection of a device is released from the logical connection or when the execution is terminated, only the notification is given to the deprived Java program. At this time, the previous logical connection is restored. To do. Further, at this time, if the previous logical connection destination has already been logically connected by another Java program, the priority is also determined at this stage. If the logical connection can be restored, a notice to that effect is sent to the stolen Java program.

  A specific sequence is shown in FIG. The Java program 1 and the Java program 2 are Java programs that operate simultaneously on the broadcast receiving apparatus, and the Java program 2 has a higher priority than the Java program 1. First, the Java program 1 issues a “device state change notification listener registration request” for registering a device state change notification listener for receiving a device state change notification to the device manager 2205f (S5001). The manager 2205f registers the state change notification listener of the Java program 1 (S5002). Next, the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder B (S5003). The device manager 2205f that has received it logically connects the PID filter A and the AV decoder B in accordance with the request (S5004). Thereafter, the Java program 2 having a higher priority than the Java program 1 issues a “device logical connection request” for the PID filter A and the AV decoder C (S5005). The device manager 2205f receiving it notices that the PID filter A is already logically connected to the AV decoder B, and the Java program 1 that has already established the logical connection and the Java that has issued a new logical connection request. The priority of the program 2 is compared. Since the Java program 2 has a higher priority, the device manager 2205f logically connects the PID filter A and the AV decoder C (S5006). Further, since the Java program 1 registers the device state change notification listener in the procedure S5001, the device manager 2205f notifies that the logical connection between the PID filter A and the AV decoder B to which the Java program 1 is connected has been released (S5007). . Thereafter, when the Java program 2 issues a “device logical connection release request” between the PID filter A and the AV decoder C (S5008), the device manager 2205f releases the logical connection between the PID filter A and the AV decoder C (S5009). The PID filter A and AV decoder B are reconnected, and the Java program 1 is notified that the PID filter A and AV decoder B have been reconnected (S5010).

  In FIG. 51, after the PID filter A and the AV decoder C are logically connected in accordance with a request from the Java program 2, the Java program 2 may end execution for some reason before releasing the logical connection. In this case, the device manager 2205f can notify the end of the Java program 2 from the AM 5005b that performs application management. In this case, the logical connection established by the Java program 2 is released. If a conflict has occurred with the Java program 1, the logical connection requested by the Java program is established again, and a state change notification is sent to the device state change notification listener of the Java program 1.

Embodiment 30
In the first embodiment, the device logical connection management unit 3204 only manages the logical connection state of the device. However, the device to which the Java program is connected and the device logical connection path is constructed does not exhibit any effect unless it is used. In this embodiment, a device usage state management unit is introduced to manage the device usage state. When the Java program issues a “device logical connection request”, the device manager 2205f inquires of the device usage state management unit even if a low priority Java program has already established a connection. Do not rebuild.

(Embodiment 31)
In Embodiment 3, if a device exists in the broadcast receiving apparatus, each unit in the device manager 2205f handles information related to the device, so that the device manager 2205f can manage the logical connection. It was. However, like the device in the adapter 1511 in FIG. 14, there is a device that does not exist in advance in the broadcast receiving apparatus and is added later. In this regard, it is impossible for the device manager 2205f in the broadcast receiving apparatus to manage information on these devices in advance.

  In this embodiment, the device manager 2205f also manages these devices. For this purpose, a device description acquisition unit, a device description interpretation unit, and a device physical connection change acquisition unit are introduced into the device manager 2205f.

  The device description acquisition unit has a function of acquiring from the device a device description held by the newly added device. The device description acquisition unit is realized as a library for reading a device description from a device, is held in the ROM 1209, and is used by the CPU 1506.

  The device description interpreter interprets the device description acquired from the device, and corrects it to a form that can be understood by the device manager 2205f. The device description interpretation unit is realized as a library for interpreting the device description, is held in the ROM 1509, and is used by the CPU 1506.

  The device physical connection change acquisition unit is used to acquire a change in the physical connection relationship of devices existing in the broadcast receiving apparatus due to the addition of a device. The device manager 2205f implements two functions using the device physical connection change acquisition unit. One is detection of a change in the device configuration existing in the broadcast receiving apparatus. When a device configuration change (device addition or deletion) occurs, the device manager 2205f can be notified by receiving a notification from the device physical connection change acquisition unit. The other is acquisition of a change in the physical connection configuration of the device. The device manager 2205f can acquire a change in the physical connection of the device. The device physical connection change acquisition unit is realized as a library for acquiring a device physical connection change, is held in the ROM 1509, and is used by the CPU 1506.

  The device description is held by the added device. The device manager 2205f reads the device description of the connected device using the device description acquisition unit and interprets it using the device description interpretation unit when the broadcast receiving apparatus is activated. Thereafter, the information of other modules in the device manager 2205f is set as the interpreted information. The device description includes, in particular, “device type character string”, and further includes “device logical connection condition” and “maximum number of device logical connections” if necessary. The “device type” is managed by the device basic information management unit 3201. “Device logical connection condition” and “maximum number of device logical connections” express requirements defined in the hardware specifications of the added device, and are managed by the device logical connection maximum number management unit and the device connection condition management unit. Further, the device manager 2205 f acquires the physical connection changed by adding the device from the device physical connection change acquisition unit, and sets it in the device physical connection management unit 3203. Thereafter, the device manager 2205f can operate without changing the function realization sequence of the device manager 2205f defined in the first embodiment.

(Embodiment 32)
In the 31st embodiment, the form of reading the device description has been described. Furthermore, in this embodiment, the device description can be read while the broadcast receiving apparatus is activated. In this case, for example, when the adapter 1511 in FIG. 14 is dynamically added and a device that can be dynamically added is mounted, the device manager 2205f detects this by receiving a notification from the device physical connection change acquisition unit. Then, as in the case of Embodiment 31, a device is added. In the addition sequence, the device manager 2205f acquires and interprets the device description, and sets information in each part. Further, a change in physical connection is acquired and set in the device physical connection management unit 3203. By implementing in this way, the device manager 2205f can cope with addition of a dynamic connection.

(Embodiment 33)
In the thirty-second embodiment, the dynamic addition of devices has been described, but such a device that can be dynamically added is often dynamically deleted. In such a case, the device manager 2205f detects this by being notified from the device physical connection change acquisition unit, and changes the physical configuration of the device using the device physical connection change acquisition unit. Set to 3203. Further, among the logical connections established at that time, those that have used the deleted physical connection are automatically released. At this time, if the device state change notification listener is registered, the Java program is automatically notified through the device state change notification listener that the logical connection has been released.
Thereby, the device manager 2205f can cope with the dynamic deletion of the device.

(Embodiment 34)
In Embodiments 1 to 32, the device managed by the device manager 2205f is handled as a single device with the device object as a reference. For this reason, each device must be specified when the logical connection stage is reached, which makes the logical connection troublesome for Java programs.

  In the present embodiment, a concept of “device set” that can handle a set of devices collectively is introduced, and the device manager 2205f can receive an input of an object representing the device set. A device set is defined as a collection of device objects, and the device set holds the order in which the device objects are registered in the device set. In other words, the device set expresses “a device string constituting a device logical connection path”. In the embodiments so far, when each function of the device manager 2205f is used, the logical connection between the two devices can only be expressed using two device objects. In the present embodiment, when the function of the device manager 2205f is used, a device set representing a “device logical connection path” composed of a plurality of devices is designated, and the designated device logical connection path is targeted. Is possible. For example, if you want to acquire data transmitted by an MPEG2 section using a section filter, acquire device objects corresponding to the tuner, PID filter, and section filter devices from the device manager 2205f, and logically connect the device objects you want to logically connect It is possible to set the device set in order, and use the device set to determine the possibility of logical connection and to perform logical connection. At this time, the device manager 2205f uses each unit in the device manager 2205f to perform logical connection only when the device logical connection path can be established in the order in which the devices included in the device set are set. As a result, the Java program can easily perform the logical connection itself.

(Embodiment 35)
In the thirty-fourth embodiment, when the Java program designates a device set and issues a “device logical connection request”, the device manager 2205f connects only when logical connection is possible in the order in which the devices in the designated device set are set. I do. In this embodiment, in such a case, even if not all devices in the designated device set can be logically connected, only the logically connectable portion is logically connected.

Embodiment 36
In Embodiments 34 to 35, the concept of a device set was introduced, and an implementation was made so that a plurality of types of devices could be handled at one time. However, in Embodiment 36, as a more advanced function, an object representing a function The device manager 2205f provides a function for logically connecting devices according to designation. For example, when a section filter is used, in the thirty-fourth embodiment, it is necessary to set a device object corresponding to each device in a device set and perform a logical connection operation using the device object. The “function” can be designated to the device manager 2205f. For example, by designating the “function” “Want to select W MPEG2 sections” and using the device logical connection function which is the sixth function of the device manager 2205f, A necessary device is logically connected to the function ", and a device set holding a device object corresponding to the device in the actually established device logical connection path is returned. As a result, the Java program does not need to know which device should be logically connected and how a desired function can be realized, and a desired device logical connection path can be obtained by designating the desired “function” itself.

  In this embodiment, a function object for expressing “function” is defined. The Java program sets the “function” that it wants to use in the function object. The function object is designated to the device manager 2205f to use the function of the device manager 2205f.

  The device manager 2205f needs to derive a necessary device logical connection path from the “function” held by the function object. In this embodiment, a function interpretation unit is introduced into the device manager 2205f. When the device manager 2205f receives a function object, the function interpretation unit is realized as a library having a function for guiding a device included in a device logical connection path necessary for realizing the function, and exists in the ROM 1209. The CPU 1206 Used by.

  When a function object is specified when using each function, the device manager 2205f guides a necessary device using the function interpreter. For the obtained device, the device manager 2205f applies each function. For example, when the device logical connection function which is the sixth function is used, for example, when “select W MPEG2 sections” is designated, the device manager 2205 f first uses the function interpreter to read “W MPEG2 sections”. Acquire all devices necessary to establish the device logical connection path necessary for screening the section, and establish the device logical connection path.

  Using this function, a Java program can specify a “function” that it wants to use and establish a device logical connection path.

(Embodiment 37)
In the first to thirty-sixth embodiments, the device logical connection path established during the start of the broadcast receiving apparatus is canceled by powering off the broadcast receiving apparatus, and when restarting, the Java program on the broadcast receiving apparatus is newly connected to the device. It is necessary to make a logical connection. In the present embodiment, the device manager 2205f automatically re-establishes the device logical connection path that was established when the broadcast receiving apparatus was last terminated when the broadcast receiving apparatus was powered on. For this reason, the device logical connection management unit 3204 is placed in the secondary storage unit 1207 so that the information managed by the device logical connection management unit 3204 is not erased even if the power is turned off. The device manager 2205f checks the device logical connection management unit 3204 existing on the secondary storage unit 1207 when the broadcast receiving apparatus is turned on, and automatically re-establishes the device logical connection path that is powered off while being logically connected. Make a logical connection.

(Thirty-eighth embodiment)
In the thirty-seventh embodiment, when the broadcast receiver is turned on, the device logical connection path at the previous power-off is automatically restored. However, the Java program operating on the broadcast receiving apparatus has no means of knowing which device logical connection path has been restored. In this embodiment, when the broadcast receiver is turned on, the device logical connection path at the time of the previous power-off is automatically restored, and at the same time, the device logical connection request is automatically established. When the Java program that issued has been started, the device logical connection path automatically restored is notified. When the device logical connection management unit 3204 on the secondary storage unit 1207 stores the device logical connection path information, the identifier of the Java program that issued the request is held at the same time, so This can be realized by taking the procedure of acquiring the identifier of the Java program when restoring the device logical connection path and notifying if the matching Java program is operating.

  In each of the above embodiments, it is assumed that all broadcast receiving apparatuses execute a program described in the Java language. However, the present invention does not depend on a language, and therefore a program written in another language is executed. The present invention can be applied even in an environment in which it is performed as in the above embodiments.

  The broadcast receiving apparatus according to the present invention realizes more detailed device management by providing a device operating on the broadcast receiving apparatus with device connection / disconnection means on the broadcast receiving apparatus. It is possible to operate a higher-functional program on an information processing apparatus such as a broadcast receiving apparatus such as a television, a personal computer, a mobile phone, or an apparatus that performs data processing in a recording medium.

1 is a configuration diagram of a broadcasting system according to the present invention. It is an example of the usage of the frequency band used for communication between the broadcasting station side system and a terminal device in the cable television system which concerns on this invention. It is an example of the usage of the frequency band used for communication between the broadcasting station side system and a terminal device in the cable television system which concerns on this invention. It is an example of the usage of the frequency band used for communication between the broadcasting station side system and a terminal device in the cable television system which concerns on this invention. It is a block diagram of a TS packet defined in the MPEG2 specification. It is a schematic diagram of an MPEG2 transport stream. This is an example of division when a PES packet defined by the MPEG2 specification is transmitted using a TS packet. This is an example of division when an MPEG2 section defined by the MPEG2 specification is transmitted using TS packets. It is a block diagram of the MPEG2 section defined by the MPEG2 specification. This is an example of using the MPEG2 section defined in the MPEG2 specification. It is a structural example of the hardware constitutions of the broadcast receiving apparatus which concerns on this invention. It is an example of the front panel of the input part in the hardware constitutions of the terminal device concerning the present invention. It is a structural example of the hardware constitutions of the broadcast receiving apparatus which concerns on this invention. It is a structural example of the hardware constitutions of the broadcast receiving apparatus which concerns on this invention. It is a structural example of the hardware constitutions of the broadcast receiving apparatus which concerns on this invention. It is an example of the front panel which exists in the hardware structural example of the broadcast receiver which concerns on this invention. It is a device connection example of the broadcast receiving apparatus according to the present invention. It is a device connection example of the broadcast receiving apparatus according to the present invention. It is a device connection example of the broadcast receiving apparatus according to the present invention. It is a device connection example of the broadcast receiving apparatus according to the present invention. It is a conceptual diagram which shows the relationship between the hardware and software of the broadcast receiver which concerns on this invention. It is a block diagram of the program structure which the terminal device concerning this invention preserve | saves. (A), (b) is an example of EPG which the terminal device which concerns on this invention performs. It is an example of the information which the secondary storage part which concerns on this invention preserve | saves. (A), (b), (c) is an example of information stored in the primary storage unit according to the present invention. It is a schematic diagram showing the content of PAT prescribed | regulated by the MPEG2 specification which concerns on this invention. It is a schematic diagram showing the content of PMT prescribed | regulated by the MPEG2 specification which concerns on this invention. It is a schematic diagram showing the content of AIT prescribed | regulated by the DVB-MHP specification which concerns on this invention. It is a schematic diagram showing the file system transmitted by the DSMCC system based on this invention. (A), (b), (c), (d) is a configuration example of a device connection path according to the present invention. 1 is an example of the overall configuration of a device connection path according to the present invention. It is the structure in the device manager which concerns on Embodiment 1 of this invention. It is a device type acquisition sequence of the device manager which concerns on this invention. It is a device number acquisition sequence of the device manager which concerns on this invention. It is the sequence at the time of device object acquisition of the device manager concerning the present invention. It is a device connection possibility acquisition sequence of the device manager according to the present invention. It is a device connection state acquisition sequence of the device manager according to the present invention. It is a device connection sequence of the device manager according to the present invention. It is a device connection cancellation | release sequence of the device manager which concerns on this invention. It is a device connection sequence of a program using the device manager according to the present invention. It is a structural example of the hardware constitutions of the broadcast receiving apparatus which concerns on this invention. It is a device connection possibility acquisition sequence in Embodiment 10 of this invention. It is a device connection possibility acquisition sequence in Embodiment 11 of this invention. It is a device connection possibility acquisition sequence of the simplest mounting in Embodiment 11 of the present invention. It is a device connection sequence example of a program according to the nineteenth embodiment of the present invention. It is a sequence at the time of device object acquisition in Embodiment 22 of this invention. It is the sequence at the time of the multiple program operation | movement which concerns on Embodiment 25 of this invention. 27 is an operation sequence when a device connection conflict occurs between programs according to the twenty-sixth embodiment of the present invention. 27 is an operation sequence when a device connection conflict between programs according to the twenty-seventh embodiment of the present invention occurs. 29 is an operation sequence when a device connection conflict between programs according to the twenty-eighth embodiment of the present invention occurs. 29 is an operation sequence when a device connection conflict occurs between programs according to the twenty-ninth embodiment of the present invention. It is a hardware block diagram for demonstrating the subject which concerns on this invention.

Explanation of symbols

1800 terminal apparatus 1202 TS decoder 1801 tuner 1802 PID filter 1803 section filter 1804 descrambler 1805 AV decoder 1806 display / speaker 1807 primary storage unit 2205f device manager 3201 device basic information management unit 3202 device object management unit 3203 device physical connection management unit 3204 Device logical connection management unit 3205 Device logical connection unit 3206 Device logical connection release unit

Claims (44)

An information processing apparatus including a plurality of devices that are hardware having a predetermined function,
Program execution means for executing the program;
Device management means for managing the device,
The information processing apparatus according to claim 1, wherein the device management unit includes an information path setting unit that sets an information transfer path between the devices based on a request from a program executed by the program execution unit. The device management means further includes:
A device identifier notifying unit for notifying the program of a device identifier for identifying the device based on a request from the program executed by the program executing means;
The information processing apparatus according to claim 1, wherein the information path setting unit sets information transfer paths in a specified order between devices specified by the program using a plurality of the device identifiers. 3. The information according to claim 2, wherein the information path setting unit sets an information transfer path between the specified devices when two devices are specified using the two device identifiers by the program. Processing equipment. The information path setting unit sets an information passing path between specified devices in a specified order when two or more devices are specified by using the device identifier by two or more by the program. The information processing apparatus according to claim 2. The information processing apparatus according to claim 2, wherein the device identifier notification unit notifies the program of a device identifier corresponding to a device of a type specified by the program. The device identifier notifying unit notifies the program of device identifiers corresponding to all devices capable of setting an information transfer path with a device specified by the device identifier specified by the program. The information processing apparatus according to claim 2. The device identifier notifying unit notifies the program of device identifiers corresponding to all devices for which an information passing path is set with a device specified by the device identifier specified by the program. The information processing apparatus according to claim 2. The device identifier notifying unit can set an information transfer path with a device specified by the device identifier specified by the program, and corresponds to a device that is not yet part of the information transfer path The information processing apparatus according to claim 2, wherein the information is notified to the program. The device management means further includes:
The information according to claim 2, further comprising a device sharing possibility notification unit that notifies the program whether or not a device specified by a device identifier specified by the program can be included in a plurality of information transfer paths. Processing equipment. The information processing apparatus according to claim 9, wherein the device sharing availability notification unit notifies the program of the availability by notifying the maximum number of information transfer paths that can include the device. The device management means further includes:
Based on a function identifier specified by the program and indicating a large function realized by a plurality of the devices, a function interpreting unit that identifies a device necessary for realizing the large function,
The information processing apparatus according to claim 1, wherein the information path setting unit sets an information transfer path between the devices specified by the function interpretation unit. The information processing apparatus according to claim 1, wherein when the program makes a request to the device management unit, the program receives a response from the device management unit and resumes processing synchronously. . The information processing apparatus according to claim 1, wherein when the program makes a request to the device management unit, the program executes processing asynchronously regardless of a response from the device management unit. . The information path setting unit does not set a new information transfer path when any of a plurality of devices specified by the program has already been set as a part of another information transfer path. The information processing apparatus according to claim 1. The information path setting unit notifies the program of a processing result indicating whether the information passing path is successfully set or failed between a plurality of devices designated by the program. The information processing apparatus described. 16. The information according to claim 15, wherein, when the information path setting unit fails to set an information transfer path between a plurality of devices specified by the program, the information path setting unit notifies the program of the reason for the failure. Processing equipment. The device management means further includes:
The information processing apparatus according to claim 1, further comprising: an information path cancellation unit that cancels the setting of an information transfer path set between the devices based on a request from a program executed by the program execution unit. The device management means further includes:
A device identifier notifying unit for notifying the program of a device identifier for identifying the device based on a request from the program executed by the program executing means;
18. The information according to claim 17, wherein the information path cancellation unit cancels the setting of an information transfer path set in a specified order between devices specified by using the device identifier by a plurality of the programs. Processing equipment. The information path cancellation unit, when two devices are specified by using the two device identifiers by the program, cancels the setting of an information transfer path set between the specified devices. 18. An information processing apparatus according to 18. When two or more devices are designated by the program using two or more of the device identifiers, the information path release unit is configured to display information passing paths set in a designated order between the two or more devices. The information processing apparatus according to claim 18, wherein the setting is canceled. The device management means further includes:
Based on a function identifier specified by the program and indicating a large function realized by a plurality of the devices, a function interpreting unit that identifies a device necessary for realizing the large function,
The information processing apparatus according to claim 17, wherein the information path cancellation unit cancels the setting of an information transfer path set between the devices specified by the function interpretation unit. The information path cancellation unit notifies the program of a processing result indicating whether the information transfer path set between a plurality of devices designated by the program has been successfully or unsuccessfully set. The information processing apparatus according to claim 17. The information path cancellation unit, when failing to cancel the setting of an information transfer path set between a plurality of devices specified by the program, notifies the program of the reason for the failure. 22. The information processing apparatus according to 22. The device management means further includes:
The device number notifying unit according to claim 1, further comprising a device number notifying unit that notifies the program of the number of the devices existing on the information processing apparatus based on a request from a program executed by the program executing unit. Information processing device. The information processing apparatus according to claim 24, wherein the device number notifying unit notifies the program of the number of devices corresponding to the type of the device specified by the program. The device management means further includes:
A path setting availability notification unit that notifies the program whether or not an information transfer path can be set between the devices based on a request from a program executed by the program execution unit. The information processing apparatus according to claim 1. The device management means further includes:
A device identifier notifying unit for notifying the program of a device identifier for identifying the device based on a request from the program executed by the program executing means;
The path setting availability notification unit notifies the program whether or not an information transfer path can be set in a specified order between devices specified using a plurality of device identifiers by the program. 27. The information processing apparatus according to claim 26. The path setting availability notification unit determines whether or not it is possible to set an information transfer path between the specified devices when two devices are specified by using the two device identifiers by the program. The information processing apparatus according to claim 27, wherein the information is notified to a program. The path setting availability notification unit sets information passing paths between specified devices in a specified order when two or more devices are specified by using two or more device identifiers by the program. The information processing apparatus according to claim 27, wherein the program is notified whether or not it is possible. The device management means further includes:
Based on a function identifier specified by the program and indicating a large function realized by a plurality of the devices, a function interpreting unit that identifies a device necessary for realizing the large function,
27. The route setting availability notification unit notifies the program whether or not an information transfer route can be set between the devices specified by the function interpretation unit. Information processing device. The device management means further includes:
2. A path state notification unit that notifies the program whether or not an information transfer path is set between the devices based on a request from a program executed by the program execution unit. The information processing apparatus described. The device management means further includes:
A device identifier notifying unit for notifying the program of a device identifier for identifying the device based on a request from the program executed by the program executing means;
The path state notification unit notifies the program whether or not an information transfer path is set in a specified order between devices specified by using the device identifier by a plurality of the programs. 32. The information processing apparatus according to claim 31. The path state notification unit notifies the program whether or not an information transfer path is set between the specified devices when two devices are specified by using the device identifier by the program. The information processing apparatus according to claim 32. The route status notifying unit, when two or more devices are specified by using the device identifier by the program, whether an information passing route is set between the specified devices in the specified order. The information processing apparatus according to claim 32, wherein the program is notified of whether or not. The device management means further includes:
Based on a function identifier specified by the program and indicating a large function realized by a plurality of the devices, a function interpreting unit that identifies a device necessary for realizing the large function,
32. The information processing apparatus according to claim 31, wherein the route setting availability notification unit notifies the program whether or not an information transfer route is set between the devices specified by the function interpretation unit. The information path setting unit always prioritizes the information transfer path requested first when setting of an information transfer path including the same device is requested by a plurality of programs executed by the program execution unit. The information processing apparatus according to claim 1, wherein: The information processing apparatus according to claim 1, wherein the program execution unit manages priorities among a plurality of programs and compares the priorities of the programs using the priorities. The information path setting unit always gives priority to the information transfer path of a high priority program when the setting of an information transfer path including the same device is requested by a plurality of programs executed by the program execution means. The information processing apparatus according to claim 37, wherein the information processing apparatus is set. The information path setting unit, after setting the information passing path, when setting of an information passing path including a device set as the information passing path is requested by another program having a higher priority. 38. The information processing apparatus according to claim 37, wherein the information transfer path requested by the program is set, and the fact is notified to the program that has requested the first information transfer path. The information path setting unit is reused when a device included in the first information passing path and constituting the information passing path requested by the other program becomes available again. 40. The information processing apparatus according to claim 39, wherein the information processing apparatus notifies the program that requested the first information transfer path of the possibility. When the device included in the first information passing path and constituting the information passing path requested by the other program becomes available again, the information path setting unit is configured to receive the first information passing path. 40. The information processing apparatus according to claim 39, wherein a route is reset, and the reset is notified to a program that has requested the first information transfer route. The information processing apparatus according to claim 1, wherein the device management unit controls the device in response to a request from the program, and notifies the program of information related to the device in response to a request from the program. An information processing method in an information processing apparatus including a plurality of devices that are hardware having a predetermined function,
A program execution step for executing the program;
A device management step for managing the device,
The information processing method, wherein the device management step includes an information path setting step for setting an information transfer path between the devices based on a request from a program executed by the program execution step. A program for performing information processing in an information processing apparatus including a plurality of devices that are hardware having a predetermined function,
A program execution step for executing the program;
A program causing a computer to execute an information path setting step for setting an information transfer path between the devices based on a request from a program executed in the program execution step.

Images