JP2006012369A - Information recording medium, and its reproducing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information recording medium which can suitably mediate conflict for resource usage among each of the programs when various programs are activated with progress in reproduction of image data. <P>SOLUTION: The image data and management information are recorded, and the management information indicates an effective block of the program in the image data in association with a required resource when the program is activated in the effective block. The reproducing device mediates the resource usage by multiple programs with reference to the effective block of this program. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information recording medium on which video data is recorded and a playback apparatus thereof, and more particularly to an improvement in starting a program or forcibly terminating a program in synchronization with the progress of playback in video data.

  In the movie business, there is a form in which a movie work and various applications related to the movie work are recorded on the same information recording medium and sold as package media. Because, if you record a game program, a quiz program, or a pet program that imitates a character appearing in a movie, on the same package media as the main movie, the product value of the package media will increase, and consumers willing to buy It is because it can be stimulated.

When the playback device tries to execute these various programs, the use of resources installed in the playback device competes among a plurality of programs. A technique for mediating when such a competition occurs is disclosed in Patent Document 1 below.
The resource contention arbitration described in Patent Document 1 mediates a resource use conflict occurring between a communication program operating on a mobile phone and an editing program for editing a telephone directory. When there is an incoming call while editing the phone book editing program and the communication program is started, the above-mentioned resource use conflict occurs. In this case, in Patent Document 1, the data used by the telephone directory editing program is saved in the memory and saved, and then the communication program is started. The idea of the technique described in Patent Document 1 is that when any event such as an incoming call occurs, the event is used as a trigger for resource arbitration.
JP 2000-224662 A

  By the way, with the progress of the reproduction of a movie work recorded on an information recording medium, a demand for executing various programs recorded on the information recording medium has recently arisen from producers of movie works. However, during playback of a movie work, the playback device uses various resources to play back video data. Therefore, when trying to start various applications in such a usage state, resource use conflicts between programs. . As described above, when a program is to be executed with the progress of reproduction of video data, there has been no idea of how to arbitrate resource competition between individual programs.

  The prior art described in Patent Document 1 saves information about a program that has been forcibly terminated. Since it is not known when the forcibly terminated program will return, it is necessary to save the saved information indefinitely. As a result, the more programs that are forcibly terminated, the greater the amount of saved information, and the greater the waste of memory resources.

  Further, the return of the forced termination program in the prior art is based on the premise that there is always a resource for editing. That is, in Patent Document 1, there are only two communication programs, that is, a communication program and an editing program. Therefore, when the processing of the communication program is completed, the resources used by the editing program can always be secured. In reality, however, resource contention often occurs between a plurality of application programs. When a program is returned from forced termination, the resources used by that program are not always fully recovered. Resuming the program without complete recovery can cause the program to hang.

A first object of the present invention is to provide an information recording medium that can suitably mediate resource use competition between individual programs when various programs are started as video data is played back.
A second object of the present invention is to provide a playback apparatus that can prevent memory resources from being wasted even when there are a large number of forcibly terminated programs.

  A third object of the present invention is to provide a playback apparatus that can safely return a program that has been forcibly terminated even when there are many programs that use resources.

  In order to achieve the first object, an information recording medium according to the present invention records video data, management information, and a program, and the program is executed in parallel with the reproduction of the video data. In addition, the management information is characterized in that an effective section of the program on the reproduction time axis of the video data is associated with a resource required when the program is started in the effective section.

  In order to achieve the first object, a playback apparatus according to the present invention includes a playback unit for playing back the video data, a program processing unit for processing the program, a valid section in the video data, and a program in the valid section. When starting up, execute a process to forcibly terminate the program and a process to restore the forcibly terminated program by referring to the management information, which holds management information indicating the required resources in association with each other And a program management unit.

In order to achieve the second object, the resource management unit in the playback apparatus according to the present invention, when an event indicating a transition of the valid section occurs, the current playback time of the video data is the valid section of the forced termination program It is characterized in that it is determined whether it is within or outside the valid section, and when it is outside the valid section, the information held by the forced termination program is deleted.
In order to achieve the third object, the resource management unit in the playback device according to the present invention updates the management information based on the program when the program is forcibly terminated, and the return of the forcible termination program It is characterized by being performed based on the updated management information.

  In the information recording medium that achieves the first object, the resource information indicating the resources necessary for starting the program is described for each reproduction unit of the video data. Arbitration can be performed for each reproduction unit of video data. That is, the process of forcibly terminating the program or restarting another program can be performed for each valid section of the video data.

  The playback device that achieves the second objective automatically deletes the data used by the program when the playback time of the video data has progressed and it has reached the outside of the valid section of the program that was forcibly terminated due to resource contention. Therefore, it is possible to reduce the amount of memory occupied. In addition, it is not necessary to execute useless processing such as program restoration processing.

Here, the playback device that achieves the third object updates the management information to indicate that the corresponding resource is unusable, and forcibly terminates it. The return is performed with reference to the management information, so that when the resource is insufficient, the program can be recovered according to the shortage.
Here, the return of the forcibly terminated program in the playback device that achieves the third object may be determined based on the acquired condition by acquiring predetermined condition information regarding the forced termination of the program. The predetermined condition information may be user preference information.

  When resource contention arbitration that does not match the user's intention is performed and the program is forcibly terminated, the user can specify how to restart the program by the pre-reference. Since it is possible to achieve recovery when an unintended behavior is performed, it is possible to construct a system in consideration of user needs.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
First, an embodiment of the present invention will be described. In the present embodiment, a richer interactivity is realized in a BD (Blu-ray Disc) application, and a programming environment such as Java (registered trademark) is introduced for the BD application, and the application from the resource contention mediation This is about the return.

Although Java (registered trademark) is assumed as a general-purpose programming environment, the same applies to C language and other programming languages.

(Logical data structure on disk)
FIG. 1 shows a configuration of a BD-ROM (hereinafter also referred to as “BD”), in particular, a configuration of a BD disc (104) that is a disc medium and data (101, 102, 103) recorded on the disc. FIG. Data recorded on the BD disc (104) is AV data (103), BD management information (102) such as management information related to AV data and an AV playback sequence, and a BD playback program (101) that realizes interactive processing. . In the present embodiment, a BD disc will be described focusing on an AV application for reproducing AV contents such as movies. The BD disc is used as an information recording medium for a computer, such as a CD-ROM or a DVD-ROM. Of course, it is possible to do this.

  FIG. 2 is a diagram showing logical data recorded on the BD disc described above. A BD disc has a spiral recording area from its inner periphery to its outer periphery, like other optical discs such as DVDs and CDs, and stores logical data between the inner lead-in and outer lead-out. It has a logical address space that can be recorded. Further, inside the lead-in, there is a special area that can be read only by a drive called BCA (Burst Cutting Area). Since this area cannot be read from an application, it is often used for copyright protection technology, for example.

  Application data such as video data is recorded in the logical address space with file system information (volume) at the head. The file system is UDF (Universal Disc Format), ISO9660, or the like, and can read logical data recorded in the same way as a normal PC using a directory and file structure.

In the present embodiment, the directory and file structure on the BD disc is a BDVIDEO directory placed directly under the root directory (ROOT). This directory is a directory in which data (301, 302, 303 described in FIG. 3) such as AV contents and management information handled by the BD-ROM is recorded.

The following seven types of files are recorded under the BDVIDEO directory.

BD. INFO (fixed file name)
This is one of “BD management information” and is a file in which information related to the entire BD disc is recorded. The BD player first reads this file.
BD. PROG (fixed file name)
It is one of “BD playback programs” and is a file in which programs related to the entire BD disc are recorded.

XXX. PL ("XXX" is variable, extension "PL" is fixed)
It is one of “BD management information”, and is a file in which play list information for recording a scenario is recorded. I have one file per playlist.
XXX. PROG ("XXX" is variable, extension "PROG" is fixed)
It is one of “BD playback programs” and is a file in which a program for each playlist described above is recorded. Correspondence with a playlist is identified by a file body name (“XXX” matches).

YYY. VOB ("YYY" is variable, extension "VOB" is fixed)
It is one of “AV data” and is a file in which VOB is recorded. There is one file for each VOB.
YYY. VOBI ("YYY" is variable, extension "VOBI" is fixed)
This is one of “BD management information” and is a file in which management information related to VOB as AV data is recorded. The correspondence with the VOB is identified by the file body name (“YYY” matches).

ZZZ. PNG ("ZZZ" is variable, extension "PNG" is fixed)
It is one of “AV data” and is a file in which image data PNG (an image format standardized by W3C and read as “ping”) for composing subtitles and menus is recorded. There is one file for each PNG image.

(Player configuration)
Next, the configuration of the player that plays the above-described BD disc will be described with reference to FIGS.

FIG. 3 is a block diagram showing a rough functional configuration of the player.
Data on the BD disc (301) is read through the optical pickup (302). The read data is recorded in a dedicated memory according to the type of each data. The BD playback program (the contents of the “BD.PROG” or “XXX.PROG” file) is stored in the program recording memory (303) in the BD management information (“BD.INFO”, “XXX.PL” or “YYY.VOBI”). Are recorded in the management information recording memory (304), and AV data ("YYY.VOB" or "ZZZ.PNG") is recorded in the AV recording memory (305).

The BD playback program recorded in the program recording memory (303) is recorded by the program processing unit (307), the BD management information recorded in the management information recording memory (304) is recorded by the management information processing unit (308), and the AV recording The AV data recorded in the memory (305) is processed by the presentation processing unit (309).
The resource management unit (306) has a function of grasping the usage status of resources such as a CPU, a memory, a decoder, and a network, and the program processing unit (307) notifies the lack of resources when starting a program. Upon receipt, it receives BD management information from the management information processing unit (308), determines a program to be activated, and notifies the program processing unit (307). Information regarding a program that could not be started or a program that was forcibly terminated at the time of resource arbitration is stored, and when a resource becomes available, the user is notified via the user interface. When the activation event is received from the user, it is notified to the program processing unit (307).

  The program processing unit (307) receives event information such as playlist information to be reproduced and program execution timing from the management information processing unit (308), and performs processing of the program. Also, the program can dynamically change the play list to be played back. In this case, the play list play command is sent to the management information processing unit (308). The program processing unit (307) receives an event from the user, that is, a request from the remote control key, and executes an execution process when there is a program corresponding to the user event.

Some programs give instructions to the management information processing unit and presentation processing unit, and if there are programs that play back AV streams via playlists, drawing instructions to the image plane (310) as with ordinary Java (registered trademark) applications Some do.
As an example of an application that instructs only reproduction of an AV stream, there is a simple reproduction application that performs reproduction of a main movie according to a user instruction. An example of an application that does not perform AV playback is a game-like application that draws a full screen by a program. It is also possible to draw as an application while playing back AV, and it is also possible to superimpose an image drawn by the program on the AV being played back or to perform animation by moving it.

  The management information processing unit (308) receives an instruction from the program processing unit (307), analyzes the corresponding playlist and VOB management information corresponding to the playlist, and receives the AV data targeted for the presentation processing unit (309). Instruct to play. The management information processing unit (308) receives the reference time information from the presentation processing unit (309), instructs the presentation processing unit (309) to stop AV data reproduction based on the time information, and the program processing unit. An event indicating the program execution timing is generated for (307).

  The presentation processing unit (309) has a decoder corresponding to each of video, audio, and subtitle / image, and decodes and outputs AV data in accordance with an instruction from the management information processing unit (308). In the case of video data and subtitles / images, after decoding, the video data and subtitles / images are drawn on the dedicated plane, video plane (311), and image plane (310), and the video is synthesized by the synthesis processing unit (312) and displayed on a TV or the like Output to the device.

As shown in FIG. 3, the BD player has a configuration based on the data configuration recorded on the BD disc shown in FIG.
FIG. 4 is a detailed block diagram of the player configuration described above. In FIG. 4, the AV recording memory (305) is in the image memory (408) and the track buffer (409), the program processing unit (307) is in the program processor (402) and the UOP manager (403), and the management information processing unit (308). ) Is a scenario processor (405) and a presentation controller (406), and a presentation processing unit (309) is a clock (407), a demultiplexer (410), an image processor (411), a video processor (412) and a sound processor (413). In addition, the resource management unit (306) corresponds to / expands the resource manager (418).

  The VOB data (MPEG stream) read from the BD disc (301) is recorded in the track buffer (409), and the image data (PNG) is recorded in the image memory (408). The demultiplexer (410) extracts the VOB data recorded in the track buffer (409) based on the time of the clock (407), and sends the video data to the video processor (412) and the audio data to the sound processor (413). The video processor (412) and the sound processor (413) are each composed of a decoder buffer and a decoder as defined by the MPEG system standard. That is, the video and audio data sent from the demultiplexer (410) are temporarily recorded in the respective decoder buffers and decoded by the individual decoders according to the clock (407).

  The PNG recorded in the image memory (408) has the following two processing methods. When the image data is for subtitles, the presentation controller (406) instructs the decoding timing. In order for the scenario processor (405) to receive the time information from the clock (407) once and display the appropriate subtitles, the subtitles are displayed to the presentation controller (406) at the subtitle display time (start and end). Give hidden instructions. Receiving the decode / display instruction from the presentation controller (406), the image processor (411) extracts the corresponding PNG data from the image memory (408), decodes it, and draws it on the image plane (414).

Next, when the image data is for a menu, the program processor (402) instructs the decoding timing. The time when the program processor (402) instructs to decode the image depends on the BD program being processed by the program processor (402), and is not generally determined.
As described with reference to FIG. 3, the image data and the video data are recorded on the image plane (414) and the video plane (415) after being decoded, and are synthesized and output by the synthesis processing unit (416).

  The management information (scenario, AV management information) read from the BD disc (301) is recorded in the management information recording memory (404), but the scenario information ("BD.INFO" and "XXX.PL") is stored in the management information recording memory (404). It is read and processed by the scenario processor (405). AV management information (“YYY.VOBI”) is read and processed by the presentation controller (406).

  The scenario processor (405) analyzes the information of the playlist and instructs the presentation controller (406) of the VOB referred to by the playlist and the playback position thereof. The presentation controller (406) manages the management information of the target VOB. ("YYY.VOBI") is analyzed, and an instruction is issued to the drive controller (417) to read out the target VOB.

The drive controller (417) reads the target AV data by moving the optical pickup according to the instruction of the presentation controller (406). The read AV data is recorded in the image memory (408) or the track buffer (409) as described above.
The scenario processor (405) monitors the time of the clock (407) and throws an event to the program processor (402) at the timing set in the management information.

  The BD program (“BD.PROG” or “XXX.PROG”) recorded in the program recording memory (401) is executed by the program processor (402). The program processor (402) processes the BD program when an event is sent from the scenario processor (405) or when an event is sent from the UOP manager (403). The UOP manager (403) generates an event in the program processor (402) when a request is sent from the user by a remote control key.

When the resource manager (418) receives a resource shortage notification from the program processor (402) when starting the program, the resource manager (418) acquires “BD.INFO” from the scenario information read from the scenario processor (405). The program to be started is determined and notified to the program processor (402). Information regarding a program that could not be started or a program that was forcibly terminated at the time of resource arbitration is stored, and when a resource becomes available, the user is notified via the user interface. When a request is sent from the user by a remote control key, when a startup event is received from the UOP manager (403), the program processor (402) is notified and the stored program is executed by the program processor (402). Is done.
(Navigation data structure)
The internal structure of information relating to the entire BD disc (“BD.INFO”) will be described with reference to FIG.

The entire BD disc information includes a title list (TitleList) and an event table for global events (EventTable).
The title list (TitleList) is composed of the number of titles (Number) in the disc and the following pieces of title information (Title # 1 to Title # n). Each piece of title information (Title) includes a playlist table (PLTable) included in the title and a chapter list (ChapterList) in the title. The playlist table (PLTable) has the number of playlists in the title (Number) and the playlist name (Name), that is, the playlist file name.

The title is a unit of AV stream playback and application execution recognized by the user, but at the same time, the player also manages AV stream playback and application execution.
The chapter list (ChapterList) is composed of the number of chapters (Number) included in the title and individual chapter information (Chapter # 1 to Chapter # n), and the chapter information (Chapter #) is a table of cells included in the chapter (Chapter #). The cell table (CellTable) includes the number of cells (Number) and individual cell entry information (CellEntry # 1 to CellEntry # k). Cell entry information (CellEntry #) is described by the name of the playlist including the cell and the cell number in the playlist.

The event list (EventList) includes the number of global events (Number) and information on individual global events. It should be noted that the global event defined first is called a first event (FirstEvent), and is the first event called when a BD disc is inserted into a player. The event information for global events has only an event type (Type) and an event ID (ID).

(Application management)
FIG. 6 shows a state in which the title list (601) indicates a title as an application management unit.

Title # 1 is the title of the top menu that is played when the disc is inserted. When the disc is inserted, the top menu playback application (602) is started, and playback of the top menu is started. An application (603) for causing a pet to appear is activated together with an application for reproducing the top menu.
If you want to move from the top menu playback to another title, switch the title. For example, if it is desired to activate the playback application for the main part of the movie, it moves to the title # 2 where the main part is played back.

  When moving from title # 1 to title # 2, as in title # 1, applications (604, 605) related to title # 2 are started, and applications (802) not related to title # 2 are stopped. The application (803) related to both title # 1 and title # 2 can continue to be activated for both titles, and stop and restart occur during the title transition between title # 1 and title # 2. is not.

  Title # 2 is a title from which the main movie is reproduced. When title # 1 is selected, the main video playback application (604) is activated and playback of the main video starts. In response to an event such as fast-forwarding or skipping by a remote control key, the main-part playback application issues an instruction to the playback control unit to control the operation of the player. When title # 2 is activated, an application (605) for causing a pop-up menu to appear is activated together with the main part reproduction application.

Title # 3 is a title that is independent of title # 1 and title # 2. When title # 3 is selected, the app that was started with title # 1 and title # 2 stops and is associated with title # 3. The activated application (606) is started.
FIG. 7 shows management information for realizing application management in units of titles as described above.

  The application management information (701) has a valid period (702) indicating a section in which the application can operate, an application ID (703), an activation state at the start of the title (704), and which application is activated preferentially at the time of resource conflict The priority (705) for determining whether to start and the resource information (706) necessary for starting the application are managed, and which application is started in the specified title. I manage.

  The resource information described in the application management information may be used as a judgment material when starting an application. Alternatively, information on an application that has been forcibly terminated may be retained at the time of resource contention and used as a confirmation of necessary resources when automatically restarting according to the release of resources. Examples of the resource include an amount of memory necessary for starting the application, a screen (screen area) used by the application, a video decoder, an audio decoder, a network, a remote control resource, and the like.

  When resource contention occurs when starting an application, the resource management unit (306) not only determines which application should be started preferentially, but also stores the forcibly terminated application to recover resources. It is necessary to respect the user's intention as much as possible by notifying the user at that time. Details regarding the processing flow of the resource management unit (306) will be described in FIG. 9, and are omitted here.

Application # 1 is an application whose priority (705) is “200”, resource information (706) is “memory, screen, video decoder, audio decoder”, and is automatically started when title # 1 starts.
The application may be terminated by another application or event. In such a case, even if the activation attribute is AutoRun (automatic activation), it is not automatically activated in the title. When the title is switched and title # 1 is started again, it is automatically activated.

The application ID may be a class file name having a startup interface such as Applet or xlet.
In addition, by registering the same application for a plurality of titles, it is possible to continue to start the application across titles. In the application management information, the application # 2 has “120” as the priority (705) and “memory, screen, audio decoder” as the resource information (706), but is not automatically activated when the title starts. Application # 2 is activated by another application or by an event such as a user operation. Since the application # 2 is registered in both the title # 1 and the title # 2, when transitioning from the title # 1 to the title # 2, the application # 2 transitions to the title # 2 without ending at the end of the title # 1. If the same application is registered for a plurality of titles in this way, the application will not be restarted after completion when transitioning between registered titles.

Even if the application straddles multiple titles, it is terminated when transitioning to an unregistered title. In the example of application # 2, application # 2 is terminated when transitioning from title # 2 to title # 3 (not shown).
Application # 3 has a priority (705) of “200” and resource information (706) of “memory, full screen, video decoder, audio decoder”, and is activated in the same manner as application # 2.

FIG. 8 shows the state of an application that starts and ends according to the title transition and the application management information (701) shown in FIG. Here, a case where resource contention occurs between application # 2 and application # 3 will be described as an example.
First, simultaneously with the disc insertion, title # 1 is started and application # 1 is automatically started (801). After a while, the application # 1 starts the application # 2 (802). When title # 1 ends, application # 1 ends according to application management information (701) (803).

  Next, when title # 2 is selected, resource competition occurs between application # 2 and application # 3, and resource competition arbitration is performed by the resource management unit (306). In response to the result of the resource contention arbitration, the application # 2 is forcibly terminated (804), and the application # 3 is activated (805). When the application # 3 is terminated (806) and the resource management unit (306) receives the resource release notification, the application # 2 is started again (807). When the title # 2 is terminated, the resource management unit (306) stores the application management information (701). Therefore, application # 2 is terminated.

FIG. 9 is an example of a processing flow of the resource management unit (306) according to the present invention. When the BD disc is inserted, the resource management unit waits for an event from the program processing unit (307).
When a resource shortage event is received from the program processing unit (307) (S101), the resource management unit selects an application to be preferentially started and performs an application forced termination process (S102) for forcibly terminating other applications. Do. This step is omitted here as it will be described in detail in FIG. When the application is forcibly terminated, it is determined whether to restore the forcibly terminated application (S103). When restoring the forcibly terminated application, the insufficient resources are confirmed (S104), and the application management information is updated (S105). The updated application management information is omitted here as will be described in detail with reference to FIG. When the application management information is updated, a process for restoring the forcibly terminated application is performed (S106). This step is omitted here as it will be described in detail in FIG. If the forcibly terminated application is not restored, it is terminated without doing anything.

  Note that the determination process for determining whether to restore the forcibly terminated application in S103 can be confirmed with the user each time or set in advance in the user preferences. The user preference is information that allows the user to input preferences and features in advance and use the information to allow the system to perform various processes. It is assumed that the user preference information is stored in a readable / writable nonvolatile memory that stores and holds data even when the power is turned off.

FIG. 10 is an example of a processing flow related to the forced application termination of the resource management unit (306) according to the present invention.
First, user preference information is acquired (S201). In the acquired user preference information, in the case of resource contention mediation, it is confirmed whether pop-up display setting has been made in order to confirm with the user which application is preferentially activated (S202). If the pop-up display setting has been made, a pop-up display is performed to ask the user's intention (S204). If there is a selection from the user, a resource loss notification is sent to the application to be forcibly terminated (S205). If no pop-up display setting is made and no selection is made by the user, the application management information is read (S206), and the application to be forcibly terminated is determined based on the priority (S207). A resource loss notification is sent to the server (S205). If the application does not perform termination processing even after a certain period of time has elapsed since the resource loss notification has been sent (S208), the application is forcibly terminated (S209).

FIG. 11 shows management information for realizing application management in units of titles, taking into account information necessary for resource contention arbitration. FIG. 9 shows an example after the application management information is updated.
In the application management information, a use item (1101) indicating whether a resource is newly available and a forced end flag item (1102) indicating whether the application is forcibly terminated are added. The use item is valid (possible, not allowed) only when the forced termination flag is “Yes”, and invalid (−) otherwise. Further, the use item corresponds to the resource item, and is “possible” if the resource is available, and “impossible” if the resource is not available.

The forced termination flag is “Yes” for an application that is forcibly terminated by resource competition arbitration, and “No” for an application that is not.
Note that the state of the application at the time of forced termination may be saved. As an example of the state of the application, when considering a game application, score information, a state of an appearing character, or the like can be given.

FIG. 12 is an example of a processing flow relating to the forced termination application return of the resource management unit (306) according to the present invention.

First, user preference information is acquired (S301). In the acquired user preference information, at the time of resource contention arbitration, it is determined whether or not launcher display setting is made when returning the forcibly terminated application (S302). Here, the launcher display means that applications whose “forced termination” item in the application management information is displayed as a list with icons and can be easily started by selecting with a cursor or the like. is doing. If the launcher display setting is made, the launcher is displayed (S303), and if not, nothing is done. Among them, an event is received (S304). It is determined whether or not the received event is an event related to scenario transition (S305). If the event is related to a scenario transition, compare the contents of the “validity period” item of the application whose “forced termination” item in the application management information is “Yes” and the currently played scenario number. Then, it is determined whether it is within the valid period (S306). If it is determined that it is not within the valid period, it is updated by changing the “forced termination” item of the application management information to “No” (S316), and the process ends. If it is determined in S305 that the event is not related to scenario transition, it is determined whether the event is related to resource release (S307). If it is determined that it is within the valid period, or if it is not an event related to resource release, it waits until an event is received. If the event is related to a resource, it is determined whether or not the application having the forced termination flag “Yes” in the application management information has all the resources necessary to start up again (S308). This step will be described in detail with reference to FIG. 13 and will not be described here. It is determined whether or not the resource necessary for starting the application is complete recovery (S309). If so, it is determined whether or not the automatic return setting of the forced termination application is set (S310). If automatic return is not set, it is determined whether or not the launcher is currently displayed (S311). If the launcher is being displayed, the launcher display is updated (for example, the color or size is changed according to the state) (S312). If not, the user is notified by a pop-up display (S313). If the resource has not been recovered, it waits for an event. If the automatic return setting has been made, or if the user selects activation from the launcher or popup (S314), the forcibly terminated application is activated again (S315), and the forced termination flag in the application management information is set to “No”. It is updated (S316).

If the automatic return setting is set and there are a plurality of forcibly terminated applications, the user is inquired to select an application to be returned.
FIG. 13 is an example of a processing flow related to resource recovery determination during restoration of a forced termination application by the resource management unit (306) according to the present invention.
First, application management information is read (S401). Regarding the application whose forcible termination item of the application management information is “Yes”, the released resource is confirmed (S402), and the usage item is updated (S403). It is determined whether all use items of the application whose forced termination item of the application management information is “Yes” is displayed (S404). If so, the resource is completely recovered (S405). It is determined that the resource is not recovered (S406).

  As described above, in this embodiment, for the user who uses the BD service, the information on the application that is forcibly terminated through the resource contention arbitration is retained, and the user is automatically notified when the resource is recovered. , Users can check the availability of resources, save the trouble of searching and executing the application again, and easily restore the application that was forcibly terminated, as well as the application range forcibly terminated due to resource contention Since the stored information can be automatically deleted when it goes outside, it is possible not only to reduce the memory consumption but also to eliminate unnecessary processing such as application restoration processing.

  In addition, by describing the resource information necessary for activation in the application management information, it is possible to guarantee the operation of the application and clarify the section in which the application can operate.

  According to the present invention, since a programming environment is introduced for the development of content including video data and programs, the present invention has a possibility of being used particularly in the movie industry and consumer equipment industry engaged in the production of video content.

Data hierarchy diagram of BD-ROM Configuration diagram of logical space on BD-ROM Outline block diagram of BD-ROM player Configuration block diagram of BD-ROM player BD disk overall management information file configuration diagram Illustration of application management unit Illustration of application management information Explanatory drawing of application state transition according to title transition Processing flow in the resource management department Process flow for forced termination of applications in the Resource Management Department Explanatory drawing of application management information including information necessary for resource conflict mediation Process flow for returning to the forced termination application of the resource manager Processing flow for resource recovery judgment during return to forced termination application of resource manager

Explanation of symbols

101 BD Playback Program 102 BD Management Data 103 AV Data 104 BD Disc 301 BD Disc 302 Optical Pickup 303 Program Recording Memory 304 Management Information Recording Memory 305 AV Recording Memory 306 Resource Management Unit 307 Program Processing Unit 308 Management Information Processing Unit 309 Presentation Processing Unit 310 image plane 311 video plane 312 synthesis processing unit 401 program recording memory 402 program processor 403 UOP manager 404 management information recording memory 405 scenario processor 406 presentation controller 407 clock 408 image memory 409 track buffer 410 demultiplexer 411 image processor 412 video processor 413 414 Image plane 415 Video plane 416 Compositing processing unit 417 Drive controller 418 Resource manager 601 Title list 602 Application that reproduces top menu 603 Application that displays pet 604 Application that reproduces main video data 605 Application that displays pop-up menu 606 Game Application 701 Application management information 702 Valid period 703 Application ID
704 Activation attribute 705 Application priority 706 Resource required for application 707 Registration information of application # 2 in title # 1 708 Registration information of application # 2 in title # 2 801 Activation of application # 1 802 Application # 2 by application # 1 803 Application termination at the end of the title 804 Application termination by resource contention arbitration 805 Application # 3 activation 806 Application # 3 termination 807 Application # 2 activation by resource recovery 1101 Resource availability 1102 Resource competition arbitration Flag indicating whether or not forced termination

S101 Resource shortage event reception step S102 Forced application termination processing step S103 Forced termination application return determination step S104 Shortage resource confirmation step S105 Application management information update step S106 Forced termination application return processing step S201 Preferences acquisition step S202 Pop-up display setting determination step S203 Popup Display step S204 User selection determination step S205 Resource loss notification step S206 Application management information reading step S207 Forced termination application determination step S208 Fixed time elapsed determination step S209 Application forced termination step S301 Preferences acquisition step S302 Launcher display setting determination step S303 Launcher display step S304 Event reception Step S305 Scenario transition event determination step S306 Effective range determination step S307 Resource release event determination step S308 Resource recovery determination step S309 Resource complete recovery determination step S310 Automatic recovery setting determination step S311 Launcher display in progress determination step S312 Launcher display update step S313 Pop-up display Step S314 User selection step S315 Forced termination application return step S316 Application management information update step S401 Application management information reading step S402 Recovery resource confirmation step S403 Application management information update step S404 Insufficient resource presence determination step S405 Resource complete recovery notification step S406 Resource unrecovered step Notification step

Claims (17)

Video data, management information, and programs are recorded.
The program is executed in parallel with the playback of video data.
Management information
An information recording medium characterized in that an effective section of a program on a reproduction time axis of video data and a resource required when the program is started in the effective section are associated with each other. The information recording medium according to claim 1, wherein the management information includes priority information indicating a priority of a program at the time of resource use competition. The information recording medium according to claim 1, wherein the management information includes a start attribute indicating whether or not to automatically execute a program at the start of the valid section. In the information recording medium, playlist information defining a playlist is recorded,
The information recording medium according to claim 1, wherein the valid section is expressed using a title section composed of one or more playlists. A playback device for playing back an information recording medium on which video data and a program are recorded,
A playback unit for playing back the video data;
A program processing unit for processing the program;
A holding unit that holds management information indicating the valid section in the video data and the resources required when the program is started in the valid section;
A playback apparatus comprising: a program management unit that executes a process for forcibly terminating a program and a process for restoring the forcibly terminated program with reference to management information. The resource management unit
When an event indicating a transition of the valid section occurs, it is determined whether the current playback time of the video data is within the valid section of the forced termination program or outside the valid section. 6. The playback apparatus according to claim 5, wherein the information held by the forced termination program is deleted. The resource management unit
If the program is forcibly terminated, the management information is updated based on the program,
The playback apparatus according to claim 5, wherein the return of the forced termination program is performed based on the updated management information. A program that was forcibly terminated
8. The playback apparatus according to claim 7, wherein predetermined condition information relating to forced termination of the program is acquired and determined based on the acquired condition.   The playback apparatus according to claim 8, wherein the predetermined condition information is user preference information.   10. The playback apparatus according to claim 9, wherein the user preference information indicates whether to automatically restart the forcibly terminated program.   The playback apparatus according to claim 7, wherein the return of the forced termination program is notified to the user by a launcher display.   12. The playback apparatus according to claim 11, wherein the launcher display changes a display state when the resource is recovered.   The playback device according to claim 7, wherein the return of the forced termination program is notified to the user by a pop-up display during resource recovery. When an event indicating a resource shortage occurs, it acquires predetermined condition information related to the forced termination of the program, determines a program to be forcibly terminated based on the acquired condition, and forcibly terminates the program. The reproducing apparatus according to claim 5.   The playback apparatus according to claim 14, wherein the predetermined condition information is user preference information.   16. The playback apparatus according to claim 15, wherein the user preference information includes information on whether to perform pop-up display to the user. The reproducing apparatus according to claim 14, wherein the predetermined condition information is priority information of the management information.

Images