WO2005036555A1 - 記録媒体、再生装置、プログラム、再生方法 - Google Patents
記録媒体、再生装置、プログラム、再生方法 Download PDFInfo
- Publication number
- WO2005036555A1 WO2005036555A1 PCT/JP2004/015339 JP2004015339W WO2005036555A1 WO 2005036555 A1 WO2005036555 A1 WO 2005036555A1 JP 2004015339 W JP2004015339 W JP 2004015339W WO 2005036555 A1 WO2005036555 A1 WO 2005036555A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- title
- playback
- attribute
- branch
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/12—Formatting, e.g. arrangement of data block or words on the record carriers
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
- G11B27/102—Programmed access in sequence to addressed parts of tracks of operating record carriers
- G11B27/105—Programmed access in sequence to addressed parts of tracks of operating record carriers of operating discs
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
- G11B27/19—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier
- G11B27/28—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording
- G11B27/32—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording on separate auxiliary tracks of the same or an auxiliary record carrier
- G11B27/327—Table of contents
- G11B27/329—Table of contents on a disc [VTOC]
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/20—Disc-shaped record carriers
- G11B2220/21—Disc-shaped record carriers characterised in that the disc is of read-only, rewritable, or recordable type
- G11B2220/213—Read-only discs
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/20—Disc-shaped record carriers
- G11B2220/25—Disc-shaped record carriers characterised in that the disc is based on a specific recording technology
- G11B2220/2537—Optical discs
- G11B2220/2541—Blu-ray discs; Blue laser DVR discs
Definitions
- Control technologies for virtual machines such as Java programs have permeated various technology fields, including communications and broadcasting.
- technology for operating Java applications in accordance with digital video playback has already been established, and various services involving menu control by Java applications are attracting the interest of viewers.
- An object of the present invention is to provide a playback device that can avoid a long title boundary due to repeated application port-do application termination.
- the recording medium is characterized in that the branch destination title has an automatic start attribute for automatically starting the application.
- the auto-start attribute in this recording medium indicates that when the application is not running at the branch source, the application is automatically started. Only launch the application.
- Application startup is limited to the combination of the non-starting branch source and the automatic startup attribute of the branching destination, so the branching between the titles makes the playback complicated, and the application startup process is performed redundantly Not in Since redundant application startup can be avoided, title boundaries can be shortened. This makes it possible to realize smooth playback control without making the user aware of the title boundary. For this reason, it is particularly effective when providing long-form content that covers multiple titles or series content recorded on multiple BD-ROMs, such as a DVD-BOX.
- FIG. 1 is a diagram showing a mode of use of the playback device according to the present invention.
- FIG. 2 is a diagram showing a file 'directory structure on a BD-ROM.
- FIG. 3 is a diagram showing the relationship between the AVClip time axis and the PL time axis.
- FIG. 4 is a diagram showing a batch specification made by four Clips—Information_file—names.
- FIG. 5 is a diagram showing a chapter definition by PLraark.
- FIG. 6 is a diagram showing a playback section definition on the SubPlayltem time axis and synchronization designation.
- FIG. 7 (a) is a diagram showing the internal structure of the] Movie object.
- FIG. 7B shows the internal structure of the BD-J object.
- FIG. 9 (a) is a diagram showing a series of titles such as a top menu, title # l, and title # 2.
- FIG. 9B is a diagram showing a time axis obtained by adding the time axes of PlayList # 1 and PlayList # 2.
- Figure 10 is a diagram showing the disc contents including three titles: main title, online shopping title, and game title.
- FIG. 11 is a diagram showing an example of the reproduced images of the three titles shown in FIG.
- FIG. 12 (a) is a graph in which the life span of each application is graphed from the membership shown by the broken line in FIG.
- FIG. 12 (b) is a diagram showing an example of an application management table described in order to define the live range of FIG. 12 (a).
- FIG. 13A is a diagram showing an example of the activation attribute setting.
- FIG. 13 (b) is a diagram showing an application (application # 2) that is started for the first time when an application is called from another application.
- FIGS. 14 (a) and 14 (b) are diagrams showing an example of an application management table and a live range in which Suspend is significant.
- FIG. 15 is a diagram showing combinations of three modes (Persistent, AutoRun, and Suspend) that the startup attribute can take and three modes of the application state in the immediately preceding title (non-start, running, and Suspend).
- FIG. 16 is a diagram showing the internal configuration of the playback device according to the present invention.
- FIG. 17A is a diagram showing how the Java archive file existing on the BD-ROM is identified on the oral memory 29.
- FIG. 17 (b) is a diagram showing an application of FIG. 17 (a).
- FIG. 19 is a diagram schematically illustrating processing by the Presentation Engine 31 to the module manager 34. .
- FIG. 20 is a diagram schematically illustrating a process performed by the application manager 36.
- FIG. 21 is a diagram showing the work memory 37 to the Default Operation Manager 40.
- FIG. 22 is a diagram showing a control procedure at the time of branching by the application manager 36.
- FIG. 23 is a flowchart showing the processing procedure of the application termination processing.
- FIG. 24 is a diagram schematically showing a process of terminating the application.
- FIG. 25 (a) is a diagram showing an application management table in which a live range is defined on a PL time axis.
- FIG. 25 (b) is a diagram showing the life cycle of the application based on the application management table of FIG. 25 (a).
- Figure 26 (a) shows the title time axis determined from the PL time axis.
- Figure 2 (b) shows the title time axis determined from the life span of the main application.
- Figure 26 (c) is a diagram showing a title time axis determined from the life spans of multiple applications.
- FIG. 27 is a flowchart showing the processing procedure of the application manager 36 during title playback.
- FIG. 28A is a diagram showing a menu hierarchy realized by the BD-ROM.
- FIG. 28 (b) is a diagram showing a MOVIE object for implementing the menu hierarchy.
- FIG. 29 is a diagram schematically showing an Index Table and branching from the Index Table to each Movie object.
- FIG. 30 (a) shows a branch when the Index Table is described as shown in FIG. 29 (b).
- Figure 30 (b) shows the branch when the non-AV title is forcibly terminated.
- FIG. 31 is a flowchart showing a processing procedure of the module manager 34.
- FIG. 32 is a diagram showing an operation example of application termination by the application manager 36.
- Fig. 33 is a flowchart showing the PL playback procedure using Playback Control Engine 32.
- FIG. 34 is a flowchart showing a procedure for accepting angle switching, SkipBack, and SkipNext. .
- FIG. 35 is a flowchart showing the processing procedure when SkipBack and SkipNext API are called.
- FIG. 36 is a flowchart showing details of the processing procedure by the Presentation Engine 31.
- FIG. 37 is a flowchart showing the playback procedure of SubPlayltem.
- FIG. 38 is a flowchart showing a processing procedure of the application manager 36 according to the fifth embodiment.
- FIG. 41 (b) is a diagram showing a data management template described in order to define the Java archive file live range in FIG. 41 (a).
- Figure 42 is a diagram showing the embedding of a Java archive file by carouselization. .
- FIG. 43 (a) is a diagram showing AVClip embedding by interleaving.
- FIG. 43 (b) is a diagram showing three types of read attributes.
- FIG. 44A shows an example of the data management table.
- FIG. 44 (b) is a diagram showing the transition of the storage contents of the roll memory 29 due to the assignment of the data management table of FIG. 44 (a).
- FIG. 45 (a) is a diagram showing the memory size of the local memory 29 in the old and new playback devices in comparison.
- FIG. 45 (b) is a diagram showing an example of a data management table in which read priorities are set.
- FIG. 46 is a diagram showing a processing procedure of preload control by the application manager 36.
- FIG. 47 (a) is a diagram showing an example of a data management table defining a plurality of applications having the same applicationID but different read priorities.
- Fig. 47 (b) shows the low power due to the allocation of the data management table in Fig. 47 (a).
- 11 is a diagram showing changes in the contents stored in the memory 29.
- FIG. 48 (a) is a diagram showing an example of a data management table in which an application to be preloaded and an application to be loaded are described to be given the same applicationID.
- FIG. 48 (b) is a diagram showing the transition of the storage contents of the oral memory 29 in the playback device having a small memory scale.
- FIG. 49 is a diagram showing a processing procedure of the load processing by the application manager 36 based on the data management table.
- -FIG. 50 is a diagram showing a processing procedure by the application manager 36 when the current playback time reaches the live range of the application q.
- FIG. 52 (a) is a diagram showing the internal structure of a BD-J object according to the seventh embodiment.
- FIG. 52 (b) is a diagram showing an example of the playlist management table.
- FIG. 52 (c) is a diagram showing what processing is performed by the playback device when a PL whose playback attribute is set to AutoPlay exists in the playlist management table of the branch destination title.
- FIG. 53 (a) is a diagram showing a title time axis in a non-AV title when the playback attribute is set to indicate non-automatic playback.
- FIG. 53 (c) is a diagram illustrating a case where the playback attribute is set to indicate "AutoPlay” in the playlist management table and the application is forcibly terminated.
- FIG. 53 (d) is a diagram showing a case where the playback attribute is set to indicate “AutoPlay” in the playlist management table and the main application fails to start.
- FIG. 54 is a flowchart showing the processing procedure of the application manager 36 according to the seventh embodiment.
- Figure 56 (a) and (b) show the relationship between application handling and startup attributes.
- FIG. 57 is a diagram schematically illustrating how an application is read by the Java virtual machine 38 according to the eighth embodiment.
- FIGS. 58A and 58B are diagrams showing an example of the read priority according to the ninth embodiment.
- FIG. 59 (a) is a diagram showing a data management table to which a group attribute has been added.
- FIG. 59 (b) is a diagram showing access to the local memory 29 based on the application management table.
- -FIG. 60 is a diagram showing the parity of the allocation unit of the application management table.
- FIG. 1 is a diagram showing a mode of use of the playback device according to the present invention.
- a reproducing apparatus according to the present invention is a reproducing apparatus 200, and forms a home theater system together with a television 300 and a remote control 400.
- the disk content supplied to the home theater system by the BD-ROM is composed of multiple titles that can branch off from each other.
- Each title is composed of one or more playlists and a dynamic control procedure using the playlists.
- FIG. 2 is a diagram showing a file 'directory structure on a BD-ROM.
- the BD-ROM has a BDMV directory under the Root directory.
- the BDMV directory contains files with the extension bdmv (index.bdmv, MovieObject.bdmv) and files with the extension BD-J (00001.BD-J, 00002. BD-J, 00003.BD-J). Under this BDMV directory, there are four subdirectories called a PLAYLIST directory, a CLIPINF directory, a STREAM directory, and a BDAR directory.
- the PLAYLIST directory contains files (00001.mpls, 00002.mpls, 00003mpls) with the extension mpls.
- the CLIPINF directory contains files with the extension clpi (O0001.clpi, 00002.clpi, 00003.clpi).
- the STREAM directory contains files (00001.m2ts, 00002.m2ts, 0003.m2ts) with the extension m2ts.
- the BDAE directory contains files (00001.; jar, 00002.jar, 00003jar) with the extension jar. From the above directory structure, it can be seen that a plurality of files of different types are arranged on the BD-ROM.
- AVClip (00001.m2ts, 00002.m2ts, 00003.m2ts) stores an AVClip.
- AVClip has types such as MainCLip and SubClip.
- MainClip is a digital stream obtained by multiplexing multiple elementary streams such as a video stream, an audio stream, a presentation graphics stream, and an interactive graphics stream.
- the files with the extension “clpi” (00001.clpi, 00002.clpi, 00003.clpi) are management information corresponding to AVClips on a one-to-one basis. Because of the management information, the Clip information has information such as the encoding format of the stream in AVClip, the frame rate, the bit rate, the resolution, and the like, and the EP map indicating the cue position.
- a time axis different from the AVClip time axis is defined. This is the PL time axis shown in the second row.
- the definition of the Playltem information enables the definition of a time axis different from that of the AVClip.
- PLmark information is information that designates an arbitrary section on the PL time axis as a chapter.
- FIG. 5 is a diagram showing a chapter definition by PLmark.
- the first row shows the AVClip time axis
- the second row shows the PL time axis.
- the arrow pkl, 2 in the figure indicates the Playltem designation (ref-to-Playltem_ld) and the temporary point designation (mark_time_stamp) in PLmark.
- three chapters (Chaptei # 1, # 2, and # 3) are defined on the PL time axis.
- the Movie object is a component of the "Title" and is stored in the file MovieObject.bdmv.
- FIG. 7A shows the internal structure of a Movie object.
- the Movie object consists of attribute information and a command sequence consisting of multiple navigation commands.
- the attribute information is a clear report (resume-intention-flag) indicating whether or not playback is intended to be resumed after a MenuCall when a MenuCall is made on the PL time axis, and masks the MenuCall on the PL time axis (Menu call mask), title search W
- the navigation command sequence is a command sequence that implements conditional branching, setting of the status register in the playback device, acquisition of the setting value of the status register, and the like.
- the commands that can be described in the Movie object are shown below.
- PlayPL (1st argument, 2nd argument)-The 1st argument is the playlist number, which can specify the PL to be played.
- the second argument can specify the playback start position using the Playltem included in the PL, an arbitrary time in the PL, Chapter, and Mark.
- PlayPLatPlayltemO The PlayPL function that specifies the playback start position on the PL time axis by Playltem.
- the PlayPL function that specifies the playback start position on the PL time axis is defined by Chapter in PlayPLatChapterO,
- the JMP command is a branch that discards the current dynamic scenario on the way (discard) and executes the destination dynamic scenario as an argument.
- the description of the navigation command in the Movie object is very similar to the description method of the navigation command in the DVD, so that the task of porting the disc content on the DVD to the BD-ROM can be performed efficiently. it can.
- Movie objects there are prior arts described in the following International Publications. Exists. See this International Publication for details. International Publication WO 2004/074976 This concludes the description of the Movie object. Next, the BD-J object will be described.
- FIG. 7- (b) is a diagram showing the internal configuration of a BD-J object.
- the BD-J object is composed of the same attribute information and application management table as the Movie object.
- a BD-J object is almost the same as a Movie object in that it has attribute information.
- the difference from the Movie object is that the BD-J object does not directly describe commands. In other words, the control procedure in the Movie object was directly described by the navigation command.
- the control procedure is indirectly specified by defining a Java application whose life cycle is the title on the application management table.
- the control procedure can be efficiently shared, that is, the control procedure can be shared among a plurality of titles.
- FIG. 7 (c) is a diagram showing the internal configuration of the Java application.
- the application consists of one or more xlet programs loaded in the virtual machine's heap area (also called work memory).
- work memory also called work memory
- one or more threads are running, and the application is composed of xlet programs and threads that are loaded into the work memory.
- the above is the configuration of the application.
- the entity of this application is the Java archive files (00001.jar, 00002.jar) stored in the BDAR directory under the BDMV directory.
- the Java archive file will be described.
- FIG. 3 is a diagram showing programs and data stored in an archive file.
- the data in this figure is a collection of multiple files in which the directory structure shown in the frame is arranged by the java archiver.
- the directory structure shown in the box is composed of a root directory, a java directory, and an image directory.
- the root directory has com.mon.pk power
- the java directory has aaa.class, bbb.class
- the image directory has , Menujpg is arranged.
- a java archive file can be obtained by putting them together in a] 'ava archiver.
- Such data is expanded when it is read out from the BD-ROM to the cache, and is treated as multiple files placed in the directory on the cache.
- the five-digit number "xxxxx" in the file name of the Java archive file indicates the application ID (applicationlD).
- applicationlD application ID
- the program and data that make up any Java application can be extracted by referring to the numerical value in the file name.
- One file that is bundled together in a Java archive file is the xlet program.
- the xlet program is a Java program that can use the JMF (Java Media Frame Work) interface.
- the xlet program consists of a plurality of functions such as EventListner that receives key events, and performs processing based on the received key events according to a method such as JMF.
- FIG. 8B shows an example of the xlet program.
- JMFA "BD: //00001.mpls"; is a method that instructs the Java virtual machine to create a player instance that plays the PL.
- A.play is a method that instructs the JMF player instance to play.
- Such JMF player instance generation is performed based on the JMF library.
- the description of the xlet program is not limited to the PL of the BD-ROM, but is the description of the JMF applicable to all content with a time axis. Since such a description is possible, it is possible to encourage a software house that is skilled in Java programming to create a BD-J object.
- JumpTItleO in Fig. 8 (b) is a function API call.
- This function API instructs the playback device to branch to another title (title # l in the figure).
- the function API is an API (Appliation Interface) supplied by the BD-ROM playback device.
- the function API is an API (Appliation Interface) supplied by the BD-ROM playback device.
- the Anchor API By calling the Anchor API, the processing unique to the BD-ROM playback device can be described in the xlet program.
- PL playback is specified by the JMF interface. Since this JMF player instance defines the PL time axis, the title time axis is determined from the title having this JMF player instance. Also
- the timeline defined by the title is called the "title timeline”.
- the title time axis is composed of a Movie object or a PL whose playback is ordered by a BD-J object.
- One example here is the title shown in Fig. 9 (a).
- This title is a series of titles: top menu> title # l ⁇ title # 2 ⁇ top menu, top menu 2- ⁇ title # 3 top menu.
- PlayList # 2 title # 2 commands PlayList # 3 commands PlayList # 4
- PlayList # l as shown in Fig. 9 (b).
- Title # l has a time axis obtained by adding the time axes of PlayList # 2 and PlayList # 2.
- title # 2 has a time axis composed of PlayList # 3 time axis
- title # 3 has a time axis composed of PlayLis # 4 time axis.
- Seamless playback is guaranteed on the PL time axis in these title time axes, but seamless playback is not required between title time axes.
- service period the period during which the Java application can exist on the work memory of the virtual machine
- the service period of the Java application must be defined on the time axis that branches off from each other. The definition of this service period is a point to keep in mind when programming for BD-ROM.
- IndexTable is a table that associates title numbers with Movie objects and BD-J objects, and is an indirect reference table that is referenced when branching from a dynamic scenario to a dynamic scenario.
- IndexTable consists of Index for each of multiple labels. Each Index describes the identifier of the dynamic scenario corresponding to the label. By referring to such an IndexTable, branching can be realized without strictly discriminating between the Movie-object and the BD-J object. Details of IndexTable are described in the following International Publication. See this gazette for details. International Publication WO 2004/025651 A1 The above is an explanation of files recorded on a BD-ROM.
- JMF player instances and applications with JumpTitleAPI calls govern the title time axis, but other applications without JMF player instance ⁇ JumpTitleAPI calls operate on the title time axis.
- the period from the start of the service by the application to the end thereof is defined as “survival of the application”.
- Information for defining the survival of the application exists in the application management template of the BD-J object.
- the application management table will be described in more detail.
- the application management table is information indicating an application that can survive on the work memory of the virtual machine in the title time axis of each title. Survival in work memory is the Xlet program is read into the work memory and can be executed by the virtual machine.
- the broken arrow atl in FIG. 7 (b) shows a close-up of the internal configuration of the application management table. As shown in this internal configuration, the application management table includes “live range”, “applicationID” indicating an application whose title is the live range, and “activation attribute” of the application.
- the disc content used here is the main title of the main video (title # l), the online shopping title of online shopping (title # 2), and the title of the game application (title # 3) It includes three titles with different characteristics.
- FIG. 10 is a diagram showing disc content including three titles: a main title, an online shopping title, and a game title. In the figure, IndexTable is described on the right side, and three titles are described on the left side.
- FIG. 11 is a diagram showing an example of the reproduced images of the three titles shown in FIG.
- title # l consists of three applications, application # l, application # 2, and application # 3.
- title # 2 includes two applications, application # 3 and application # 4, and title # 3 includes application # 5.
- FIG. 11 is a diagram showing an example of the reproduced images of the three titles shown in FIG.
- the cart program application # 3 is started in both title # l and title # 2. .
- an application app that simulates a mascot appearing in a movie work, a menu that displays a menu in response to a menu call operation, etc. There is an app.
- Fig. 12 (a) When the life span of each application is graphed from the membership shown by the broken line in Fig. 10, the result is as shown in Fig. 12 (a).
- the horizontal axis is the title time axis.
- the live range of each application is arranged along the vertical axis.
- application # l and application # 2 belong only to title # l, so their survival sections remain within title # l. Since application # 4 belongs to title # 2 only, these live ranges remain within title # 2.
- application # 5 belongs to title # 3 only, so these live ranges remain in title # 3. Since application # 3 belongs to title # l and title # 2, their survival range extends from title # l to title # 2.
- the application management table for title # 1, # 2, and # 2 is as shown in Fig. 12 (b). If the application management table is described in this way, application # l, application # 2, and application # 3 are loaded into the work memory at the time of starting playback of title # l. At the start of title # 2, application # l and application? ⁇ Are deleted from the work memory and only application # 3 is controlled. Similarly, control can be performed such that application # 4 is loaded into a single memory at the start of playback of title # 2 and application # 3, # 4 is deleted from the work memory at the start of title # 3. .
- control can be performed such that application # 5 is loaded into the work memory during the playback of title # 3, and application # 5 is deleted from the work memory when the playback of title # 3 is completed.
- the surviving application at the branch source—branch destination is stored in the work memory, and the application that is not at the branch source but exists only at the branch destination is stored in the work memory.
- the number of times the application is read into the work memory is the minimum required. As described above, by reducing the number of times of reading, it is possible to realize an application that is not conscious of the title boundary, that is, an unready application.
- the startup attributes include "AutoRun”, which indicates automatic startup, "Persistent”, which indicates that it can be placed in the virtual machine's primary memory, which is not the target of automatic startup, and is placed in the virtual machine's work memory. However, there is a “Suspend” where CPU power cannot be allocated.
- the launch attribute “Persistent” is a continuation attribute, and indicates that the state of the application at the branch source title is to be continued. Also, it is a genus indicating that it can be loaded into work memory. If the launch attribute is “Persistent”, the application to which this launch attribute is assigned will be allowed to be called from other applications.
- the management entity application manager
- the management entity that manages the application checks whether the applicationlD of the application is described in the application management table and the startup attribute is "Persistent”. judge. If “Persistent”, load the application into work memory. On the other hand, if the applicationlD of the called application is not described in the application management table, the application will not be loaded into the work memory. Calls by applications are limited to applications to which this “Persistent” is assigned.
- Persistent is the default startup attribute that is assigned when the startup attribute is not explicitly specified, so if the startup attribute of a certain application is "-one", the startup attribute of that application is started.
- the attribute means this Persistent.
- FIG. 13 is an example of setting the startup attributes for the three applications in FIG.
- application # 2 is the application that is started only when an application is called from another application as shown in Figure 13 (b). I do.
- the remaining application # l and application # 3 are started automatically when title # l starts Suppose it is an application.
- the start attribute of each application in the application case management table is set to "AutoRun" for application # l and application # 3. Is set as I PersistentJ.
- application # l and application # 3 are automatically loaded into the work memory and executed when branching to title # l.
- application # 3 is an application that can be loaded on the work memory of the virtual machine. Therefore, application # 2 will be loaded into the virtual machine's work memory and executed only after a call from application # l.
- ⁇ survival interval '' startup attribute the number of applications that can run on the virtual machine can be limited to 4 or less, and the total number of threads can be limited to 64 or less. Can be guaranteed.
- FIGS. 14 (a) and 14 (b) are diagrams showing examples in which Suspend is significant.
- Fig. 14 (b) there are three titles (title # l, title # 2, title # 3), of which title # l and title # 3 execute the game T-pre Title # 2 is a side path, which realizes video playback.
- title # l title # 2
- title # 3 title # 3
- T-pre Title # 2 is a side path, which realizes video playback.
- the side path it is necessary to realize video playback, which interrupts game execution.
- scores in the middle are counted, so we want to keep the stored value of resources before and after title # 2.
- the application management table is described such that the game application is suspended at the start of title # 2 and application # 2 is resumed at the start of title # 3.
- the resource value is maintained for application # 2 in title # 2 because the resource is allocated.
- application # 2 is not executed by the virtual machine because the CPU is not allocated. As a result, a process of executing the side pass during the execution of the game title is realized.
- FIG. 15 shows three modes that the startup attribute can take (Persistent, AutoRun, Suspend), and three modes of the application status in the last title (non-start, running, Suspend)
- FIG. 7 is a diagram showing combinations that can be taken. If the last state is "not running”, and the startup attribute is "AutoRun", the application will be started in the branch destination title.
- the launch attribute is "Suspend”
- the state of the application will be suspended. If the previous state is "Suspend”, the start attribute of the branch title is Suspend, and if it is "Persistent” AutoRun ", the application is resumed at the branch title. Will be done.
- the live range and the start attribute in the application management table it becomes possible to perform synchronous control of operating a Java application along with the progress of the title time axis. Along with that, various applications can be launched. The above is the description of the recording medium. Next, the playback device according to the present invention will be described.
- FIG. 16 is a diagram showing the internal configuration of the playback device according to the present invention.
- the playback device according to the present invention is industrially produced based on the interior shown in the drawing.
- the playback device according to the present invention mainly includes two parts, a system LSI and a drive device, and can be industrially manufactured by mounting these parts on a cabinet and a board of the device.
- a system LSI is an integrated circuit that integrates various processing units that perform the functions of a playback device.
- the playback devices produced in this way include a BD-ROM drive 1, a lead buffer 2, a demultiplexer 3, a video decoder 4, a video plane 5, a P-Graphics decoder 9, a Presentation Graphics plane 10, a synthesizing unit 11, and a font generator.
- the BD-ROM drive 1 reads / ejects the BD-ROM and accesses the BD-ROM.
- the read buffer 2 is a FIFO memory in which TS packets read from the BD-ROM are stored in a first-in first-out manner.
- the demultiplexer (De-MUX) 3 extracts a TS packet from the lead buffer 2 and converts the TS bucket constituting this TS bucket into a PES bucket. Then, of the PES buckets obtained by the conversion, those having the PID set by the CPU 22 are output to one of the video decoder 4, the audio decoder 20, the P-Graphics decoder 9, and the I-Graphics decoder 13.
- Video plane 5 is a plane for storing uncompressed pictures.
- a plane is a memory area for storing pixel data for one screen in a playback device. If a plurality of planes are provided in the playback apparatus, and the stored contents of these planes are added for each pixel and video output is performed, the video output can be performed after combining the video content.
- the resolution in the video plane 5 is 1920 ⁇ 1080, and the picture data stored in the video plane 5 is composed of pixel data represented by a 16-bit YUV value.
- the P-Graphics decoder 9 decodes the presentation graphics stream read from the BD-ROM and HDD 17 and writes the uncompressed graphics to the Presentation Graphics plane 10. Subtitles will appear on the screen due to the decoding of the graphics stream.
- the Presentation Graphics plane 10 is a memory having an area for one screen, and can store uncompressed graphics for one screen.
- the resolution in this plane is 1920 x 1080, and each pixel of the non-compressed graphics in the Presentation Graphics plane 10 is represented by an 8-bit index color.
- CLUT Color Lookup Table
- the synthesizing unit 11 synthesizes the uncompressed picture data (i) with the contents stored in the Presentation Graphics plane 10.
- the font generator 12 expands the text code contained in the textST stream into a bitmap using character fonts.
- the I-Graphics decoder 13 decodes the interactive graphics stream read from the BD-ROM or the HDD 17 and writes uncompressed graphics to the Interactive Grannies plane 15.
- the switch 14 is a switch for selectively writing any one of the font sequence generated by the font generator 12 and the graphics obtained by the decoding of the P-Graphics decoder 9 to the Presentation Graphics plane 10.
- the synthesizing unit 16 combines the storage contents of the Interactive Graphics plane 10 with the synthesized image (uncompressed picture data and the storage contents of the Presentation Graphics plane 7) output from the synthesizing unit 8. Are synthesized.
- the HDD 17 is a built-in medium in which SubClip, Clip information, and playlist information downloaded via a network or the like are stored.
- the playlist information in the HDD 17 differs from the BD-ROM and the HDD 17 in that it can be specified as Clip information.
- the playlist information on the HDD 17 does not need to specify the file on the BD-ROM with a full path. This is because the HDD 17 is recognized by the playback device as a single virtual drive (called a virtual package) together with the BD-ROM.
- Clip_Information_file_name in Playltem information and Clip_Information_file_name in SubPlayltem information specify HDD 17 and BD-ROM by specifying a 5-digit numerical value corresponding to the file pod of the file storing the Clip information.
- the above AVClip can be specified.
- the read buffer 18 is a FIFO memory, in which TS buckets read from the HDD 17 are stored in a first-in first-out manner.
- the audio decoder 20 decodes the PES packet output from the demultiplexer 19 and outputs uncompressed ⁇ : audio data.
- the scenario memory 2.1 is a memory for storing current PL information and current clip information.
- the current PL information refers to the current PL to be processed among the multiple PL information recorded on the BD-ROM.
- the current Clip information refers to the information currently being processed from among the multiple Clip information recorded on the BD-ROM.
- the key processing unit 23 outputs a key event for performing an operation in response to a key operation on the remote control or the front panel of the playback device.
- the instruction ROM 24 stores software for controlling the playback device.
- Switch 25 is used for selectively reading each data read from BD-ROM and HDD I7 to read buffer 2, read buffer 18, scenario memory 21 or local memory 29. This is the switch to be put in.
- PSR4 when set to a value between 1 and 100, indicates the title to which the current playback point belongs, and when set to 0, indicates that the current playback point is the top menu.
- PSR7 when set to a value of 0 to 255, indicates the number of the PlayItem (current PlayItem) to which the current playback point belongs.
- PSR8 is set to a value from 0 to OxFFFFFF to indicate the current playback point (current PTM (Presentation TiMe)) using a time accuracy of 45 KHz.
- the current playback point is specified by the above PSR4 to PSR8.
- the oral memory 29 is a cache memory for temporarily storing the recorded contents of the BD-ROM because reading from the BD-ROM is slow.
- the presence of the local memory 29 improves the efficiency of application execution in the BD-J mode.
- FIG. 17 (a) is a diagram showing how a Java archive file existing on the BD-ROM is identified on the local memory 29.
- the left column shows the file names on the BD-ROM
- the right column shows the file names on the local memory 29.
- FIG. 17 (b) is a diagram showing an application of FIG. 17 (a).
- data stored in a file is stored in the format of header + data. What is used for the header is the file path in the local memory 29.
- Fig. 17 (b) in the oral memory 29, a part of the file path in the BD-ROM is omitted for the file path, and by storing the file path in the header, The location of the data on the BD-ROM can be clarified.
- FIG. 18 is a diagram in which a portion composed of software and hardware stored in the ROM 24 is replaced with a layer configuration.
- the layer configuration of the playback device consists of the following a), b), c), d-l), d-2), e), and £). That is,
- Playback Control Engine CJ 2 which performs playback control based on playlist information and Clip information There are two hierarchies,
- the HDMV module 33 which is the subject of decryption and execution of the Movie object, and d-2) the BD-J module 3, which decrypts and executes the BD-J object 5 is on the same level.
- the BD-J module 35 is a so-called Java platform, and has a configuration in which a Java virtual machine 38 including a work memory 37 is a core, an application manager 36, an event listener manager 39; It consists of Default Operation Manager 40.
- a Java virtual machine 38 including a work memory 37 is a core, an application manager 36, an event listener manager 39; It consists of Default Operation Manager 40.
- FIG. 19 is a diagram schematically illustrating the processing by the Presentation Engine 31 to the module manager 34.
- the Presentation Engine 31 performs the AV playback function.
- the AV playback function of the playback device is a group of traditional functions followed by DVD players and CD players, and starts playback (Play), stops playback (Stop), pauses (Pause On), and releases pause ( Pause Of £), Release of Still function (still of £), Fast forward with speed specification (Forward Play (speed)), Rewind with speed specification (Backward Play (speed)), Audio switching (Audio Change), This function is called Subtitle Change or Angle Change.
- the Presentation Engine 31 decodes the video decoder 4, P-Graphics decoder 9, and I-Video so as to decode the part corresponding to the desired time in the AVClip read on the read buffer 2.
- the playback control engine (PCE) 32 executes various functions such as a playlist playback function 0) and a state acquisition setting function (ii) in the playback device.
- the playback function of the PL means that, of the AV playback functions performed by the Presentation Engine 31, the playback start and playback stop are performed according to the current PL information and Clip information.
- These functions (i) to (ii) are based on the HDMV module 33 Execute in response to a call.
- the playback control engine 32 executes its own function in response to an instruction from a user operation or an instruction from a higher layer in the layer model.
- arrows marked with ⁇ 2 and ⁇ 3 schematically indicate the reference of Playback Control Engine 32 to Clip information and playlist information.
- the HDMV module 33 is the execution entity of the MOVIE mode, and when notified of a Movie object constituting a branch destination from the module manager 34, reads out a Movie object constituting a branch destination title into the local memory 29. Then, the navigation command described in the Movie object is decoded, and a function call to the Playback Control Engine 32 is executed based on the decoding result.
- arrows marked with V2, V3, and V4 indicate branch target Movie objects from the module manager 34 (2), navigation described in the Movie object; decoding of commands (3), A function call (4) to Playback Control Engine 32 is schematically shown.
- the module manager 34 holds the Index Table read from the BD-ROM and performs branch control.
- this branch control receives the title number of the jump destination, and This is to notify the HDMV module 33 or the BD-J module 35 of the Movie object or BD-J object constituting the title.
- Arrows marked with V0, V1, and V2 in the figure schematically show execution of the JumpTitle command (0), reference of the IndexTable by the module manager 34 (1), and notification of the branch destination Movie object (2). I have.
- FIG. 20 is a diagram showing the application manager 36.
- the application manager 36 controls the start of the application with reference to the application management table and the control when the title ends normally.
- Start control means that every time a BD-J object that is a branch destination is notified from the module manager 34, the BD-J object is read, and the local application is referred to by referring to the application management table in the BD-J object. Performs memory 29 access. And configure an application with the current playback point as the 'live range'
- the control is to read the xlet program into the work memory.
- ⁇ l, 2, and ir3 'in Fig. 20 represent the notification of the branch target BD-J object in the start control (1), refer to the application management table (2), and the start instruction to the Java virtual machine 38. Shown. In response to this start instruction, the Java virtual machine 38 reads the xlet program from the local memory 29 to the work memory 37 (5).
- Title end control includes control for normal termination and control for abnormal termination.
- the control at the time of normal termination includes a control in which a jump title API is called by an application constituting a title and a switch to a branch destination title is requested to a branch control main body (module manager 34). .
- Arrow 6 schematically shows the notification of the module manager 34 in this end control.
- the application composing the title may be left running. This is because whether to terminate the application is determined by the branch destination title.
- the application manager 36 performs a process of reading a Java archive file from the BD-ROM to the local memory 29 (8).
- Reference numeral 8 schematically illustrates the reading to the oral memory 29.
- the Java virtual machine 38 loads the xlet program constituting the application into the private memory 37, decrypts the xlet program, and executes a process according to the decryption result.
- the xlet program includes a method for instructing the generation of a JMF player instance and a method for instructing the execution of this JMF player instance, control for the lower layer is performed so as to realize the processing contents instructed by these methods. I do. If a JMF player instance creation is ordered, the Java virtual machine 38 will execute the JMF player associated with the YYYYMPLS file on the BD-ROM. Get key instance. Also, if execution of the JMF method in the JMF player instance is ordered, this JMF method is issued to the BD middleware,
- the Event Listner Manager 39 analyzes events (key events) generated by user operations and sorts the events.
- the solid arrows 01 and 02 in the figure indicate this Event
- the distribution by Listner Manager 39 is schematically shown. If a key event such as STAET, STOP, SPEED, etc. registered in the Event Listner in the xlet program, the event related to the xlet program indirectly referenced by the BD-J object can be sorted. START, STOP, and SPEED are events corresponding to JMF. Since these key events are registered in the Event Listner of the xlet program, the xlet program can be started by this key event. The key event
- this key event is distributed to Default Operation Manager 40.
- key events that occur in the BD-ROM playback device, such as audio switching and folder switching, which are not registered in the Event Listner. Even if these key events occur, perform processing without omission. That's why.
- Event Listner non-registered events were sorted by Event Listner Manager 39 and Default Operation Manager 40, but Playback Control Engine 32 directly received Event Listner non-registered events and performed playback control. (4 in the figure).
- FIG. 22 is a diagram showing a control procedure at the time of branching by the application manager 36.
- This flowchart is a process of starting or terminating an application (referred to as an application X) that satisfies the conditions of steps S2 to S5.
- step S2 it is determined whether or not the application is not activated in the branch source title but is alive in the branch destination title and the activation attribute in the branch destination title is an application X having the AutoRim attribute. For example, cache sense for the local memory 29 is performed. As a result of the cache sense, if the application X is on the oral memory 29 (Yes in step S7), the application X is read from the oral memory 29 to the work memory 37 (step S8). If it is not in the local memory 29, the application X is read from the BD-ROM to the local memory 29, and then the application X is read from the local memory 29 to the work memory 37 (step S9).
- step S3 it is determined whether or not there is an application X that is running in the branch source title and is non-existent in the branch destination title. If it exists, the application case X is deleted from the work memory 37 and the process is terminated (step S10).
- step S4 it is determined whether or not there is a branch source Suspend, a branch destination AutoRxm, or a Persistent application. If it exists, Resume Application X (Step S11).
- step S18 is for judging whether or not the application to be issued has been completed. If the application has been completed, the processing for this application is completed. In step S19, it is determined whether or not the timer has timed out. If timed out, in step S20, the application to be issued is deleted from the work memory 37, and the application is forcibly terminated.
- FIG. 24 is a diagram schematically showing a process of terminating the application.
- the first tier in this figure shows the application manager 36, and the second tier shows three applications.
- the left-hand application shows the application that received the terminate event and successfully completed the termination process.
- applications in the middle row indicate applications that received a terminate event but failed to terminate.
- the application on the right shows an application that could not receive a terminate event because EventListner was not implemented.
- the arrows epl and ep2 between the first stage and the second stage schematically show the issuance of the terminate event by the application manager, and the arrow ep3 schematically shows the start of the termination process.
- the third stage is the state after the state transition when the termination process is successful. This abridgement is terminated by its own termination process. If there are applications such as these xlet programs that do not end within a predetermined period, the abbreviation manager 36 forcibly removes them from the work memory 37.
- the fourth row shows the forced termination by the application manager 36. It is one of the missions of the Application Manager 36 to specify the forced termination in the fourth stage.
- an application that is started at the branch source title and is not alive at the branch destination title is automatically terminated. Even if it progresses, resources on the playback device No application launch beyond the limit is done. Since application operation before and after branching can be guaranteed, it is possible to distribute a lot of disc contents that execute an application while reproducing a digital stream.
- the application manager 36 In order to perform processing based on the application management table described in this way, the application manager 36 according to the present embodiment starts a live range from the chapter start point each time the chapter start point specified by PLmark is reached. It is determined whether or not the application exists, and if so, the application is loaded into the work memory 37.
- the life span of the application can be specified with finer precision.
- disc content can have a reverse time axis. Retrograde is a volume By returning, the time axis advances in the opposite direction. If this reversal and progress are repeated at the chapter boundary, loading and discarding of the private memory are repeated many times, resulting in extra read load. Therefore, in the present embodiment, the application is started at the moment when the normal playback by the Playback Control Engine 32 is started after entering the title.
- PL playback includes normal playback and trick playback.
- the trick playback includes fast forward, rewind, SkipNext, and SkipBack.
- the application is not started, and the application is started only after the normal reproduction is started. Normally, based on the moment of the start of reproduction, even if there is a crossing before and after the life cycle as described above, the application startup will not be repeated more than necessary. Note that the process of setting the instant of the normal playback as the reference for starting the application may be executed even when the survival area is title.
- the alive range of the ablation can be defined in units of chapters, which is smaller than the PL, so that it is possible to realize precise a-precision control.
- each application is assigned a priority. This priority takes a value from 0 to 255. If there is a conflict between resource usage among applications, which application is forcibly terminated, and from which application the resource is When the application manager 36 performs the process of stealing, it is used as a source of judgment.
- application # l has a priority of 255
- application # 2 and application # 3 have a priority of 128, so in the event of a conflict between application # l and application # 2, the application manager 36 has priority. Perform the process of forcibly terminating application # 2 with low degree.
- the disc content provided by the BD-ROM is composed of a plurality of titles that can be mutually branched.
- Each title includes one or more PLs and a control procedure using this PL, as well as a non-AV title that only includes control procedures for the playback device. In the present embodiment, this non-AV title will be described.
- Figure 26 (a) shows the title time axis determined from the PL time axis. Show. In this case, the PL time axis becomes the title time axis, and the live range of the application is determined on this title time axis. If there is no PL time axis as a reference, the title time axis should be defined as shown in Figure 26 (b) and (c).
- Figure 26 (b) shows the title time axis determined from the life span of the main application.
- the main application is the only application that has the start attribute set to AutoRun in the title and is automatically started when the title starts.
- this is a launcher application.
- a launcher application is an application program that launches another application.
- Figure 26 (b) is that the title time axis is assumed to be continuous as long as the main application is running, and the time axis is terminated when the main application ends.
- Figure 26 (c) is a diagram showing a tight time axis determined from the life span of multiple applications. One application is started at the beginning of the title, but this application calls another application, and this application repeatedly calls another application. There is a case that is. In this case, the idea is that the title time axis is continued as long as any application is running, and the title time axis ends when a state arrives in which no application is started. It is.
- the title time axis of a non-AV title is determined, the title will be set to the title at the same time as the end of the evening title axis, regardless of whether it is an AV title or a non-AV title.
- the process of branching can be performed uniformly.
- the title time axis for non-AV titles is merely an imaginary time axis for comparison with AV titles. Therefore, the playback device cannot go backward on the title time axis of a non-AV title or search for an arbitrary position.
- FIG. 27 is a flowchart showing the processing procedure of the application manager 36 during title playback. This flowchart has a loop structure in which steps S21 to S23 are repeated during title playback.
- Step S1 is for determining whether or not the title jump API has been called. If called, the module manager 34 is requested to branch to the jump destination title (step S27).
- Step S22 is a determination as to whether or not there is a main application that is responsible for calling the application in the title, and if so, confirms whether it has been started (step S25). ). If it has not been started, it is interpreted as "end of title", and the end is notified to module manager 34 (step S26).
- Step S23 is a step executed when there is no main application (No in step S22), and it is determined whether or not any application is running. If so, it also interprets it as "end of title" and notifies module manager 34 of the end (step S26). -As described above, according to the present embodiment, even if the title does not involve PL playback, it is possible to perform processing in which branching is performed only after application execution is completed, without branching during application execution.
- FIG. 28 (a) is a diagram showing a menu hierarchy realized by the BD-ROM.
- the menu hierarchy in this figure has a structure in which TopMenu is arranged at the top level, and lower TitleMenu, SubTitleMenu, and AudioMenu can be selected from this TopMenu.
- Arrows swl, 2, and 3 in the figure schematically show menu switching by button selection.
- TbpMerm is a menu in which buttons (buttons snl, sn2, sn3 in the figure) for selecting whether to perform audio selection, subtitle selection, or title selection are arranged.
- the TitleMenu is a menu with buttons to accept the selection of a movie, such as selecting the movie version of the movie (title), selecting the director's cut version, selecting the game version, etc. .
- AudioMenu is a menu with buttons to accept audio playback in Japanese or English.
- SubTitleMenu is a menu with buttons to accept subtitles in Japanese or English. It is.
- Figure 28 (b) shows a MOVIE object for operating a menu having such a hierarchy.
- MovieObject.bdmv stores FirstPlay OBJ, TpMenu OBJ, AudioMenu OBJ, and SubTitleMenu OBJ.
- the FirstPla object (FirstPlay OBJ) is used to load BD-ROMs to playback devices. This is a dynamic scenario that is automatically executed at the time of logging.
- the IpMenu object (TopMenu OBJ) is a dynamic scenario that controls the behavior of TbpMenu. It is this IbpMenu object that is invoked when the user requests a menu call.
- the IbpMenu object includes one that changes the state of a button in the TopMenu in response to a user operation, and a branch command that branches in response to a button operation. This branch command realizes menu switching from TopMenu to TitleMenu, TopMenu to SubTitleMentu TopMenu to AudioMenu.
- the AudioMenu object (AudioMenu OBJ) is a dynamic scenario that controls the behavior of AudioMenu. Commands that change the state of buttons in AudioMenu in response to user operations, and audio settings in response to button operations. Includes the command to update.
- the TitleMemi object (TitleMenu OBJ) is a dynamic scenario that controls the behavior of TitleMemi, and includes a command that changes the state of the button in itleMenu and a branch command that branches in response to a decision operation on the button.
- Arrows bcl, 2 in the figure schematically show the branch from Index Table to FirstPlayOBJ, and: Branch from FirstPlayOBJ to TpMenu, and arrows bc3,4,5 show the arrows from TpMenu to TitleMenu, SubTitleMenu, AudioMenu. Are schematically shown. Arrows bc6, 7, and 8 schematically show branches from the TitleMenu to each Movie object.
- FirstPLaylNDEX, TopMen INDEX, Audio Menu INDEX, Subtitle Menu INDEX, title Menu INDEX are indexes for FirstPLayOBJ, IbpMenu OBJ, Audio Menu OBJ, Subtitle Menu OBJ, title Menu OBJ, respectively, and these identifiers are described.
- title # l ⁇ # mINDEX is the index of the title entered from the 1st to the mth in the BD-ROM.
- the title of the MOVIE object to be branched to when selecting the title numbers from 1 to m is selected.
- An identifier (ID) is described.
- title # m + l ⁇ # nINDEX is the index of the title entered from the m + 1 to the nth entry on the BD-ROM, and becomes the branch destination when selecting these title numbers from m + 1 to n Describes the identifier (ID) of the BD-J object.
- the title # 0 INDEX is an INDEX that specifies a Movie object or a BD-J object to be a branch destination when the BD-J object is forcibly terminated.
- the identifier of TopMenuOBJ is stored in title # 0INDEX.
- FIG. 3 (a) shows a branch when the Index Table is described as shown in FIG. Since the Index Table is described in this way, when executing the branch command with the label title # l ⁇ title # m as the branch destination, the identifier of the Movie object # l ⁇ # m is obtained from title # llndex: ⁇ title # mlndex. Taken out.
- the identifier of the BD-J object # m + l to #n is extracted from title # m + llndex to title # nlndex.
- Step S31 is to determine whether or not the title jump API has been called. If the title jump API is called, the title number j which is the branch destination label is obtained (step S33), and the IDj is extracted from the index of the title number j in the Index Table (step S34). ), The HDMV module 33 or the BD-J module 35 executes the Movie object or the BD-J object of IDj (step S35).
- step S32 it is determined whether or not the title and the end are notified from the application manager 36. If notified (Yes in step S32), the top menu OBJ constituting the top menu title is set to the HDMV. The module 33 or the module manager 34 is executed (step S36).
- the titles to be played here are non-AV titles, including game apps that stack falling tile pieces.
- the lower part of Fig. 32 shows the title time axis consisting of the live range of the application, and the upper part shows the image displayed on the title time axis.
- the non-AV title is a game app
- one screen of the game app is displayed as shown in the upper left of Fig. 32 in the life span of this game app. If the game application has a bug and terminates abnormally, the application manager 36 forcibly terminates the game application according to the flowchart in FIG. 23 and notifies the module manager 34 of the end of the title.
- the Playback Control Engine 32 executes the processing procedure based on the PL information when the PL playback API is called. If the PL has a playback time of 2 hours, the above process will continue during these 2 hours. What matters here is a gap between the time when the Java virtual machine 38 returns a success response and the time when the Playback Control Engine 32 actually finishes processing. Since the Java virtual machine 38 is an event-driven processing entity, it returns a response indicating success or failure of playback immediately after the call.However, since the actual processing by Playback Control Engine 32 ends after two hours, If the time taken to return a success response to the application is used as a reference, it will not be possible to detect the end of processing after 2 hours. If fast forward, rewind, or skip is performed in PL playback, the playback period of 2 hours fluctuates around 2 hours, making it more difficult to detect the end of processing.
- PlayItem # x (PI # x).
- This Play tem #x is initialized by being set to the first Play tem of the current PL (step S42).
- the termination requirement of the loop processing described above is that this Playltem # x becomes the last Playltem of the current PL (step S49). If it is not the last Playltem, the next Playltem in the current PL is Playltem # x Is set to (Step S50).
- the presentation engine 31 is instructed to output from mark_time_stamp of the current PLMark to Out_time of Playltem # x (step S46).
- the presentation engine 31 is instructed to output from mark_time_stamp of the current PLMark to Out_time of Playltem # x (step S46).
- Playltem # x is the last PI of the current PL (scan Step S4 9).
- step S50 the next Playltem in the current PL is set to Playltem # x (step S50), and the process returns to step S43.
- the PIs constituting the PL are sequentially reproduced.
- FIG. 34 is a flowchart showing the angle switching procedure and the SkipBack and SkipNext procedures. This flowchart is performed in parallel with the processing procedure of FIG. 33, and repeats a loop process including steps S51 to S52. Step S51 in this loop is to determine whether or not the API for requesting angle switching has been called from the Java virtual machine 38. If there is a call for the angle switching API, the current Clip information is switched. Perform the operation.
- Step S55 in FIG. 34 is a determination step, which determines whether is-multi-angles of Playltem # x is on. is—nmlti-angles is a flag indicating whether Playltem # x supports multi-angle, and if step S55 is No, the process proceeds to step S53. If step S55 is Yes, execute steps S56 to S59. In steps S56 to S59, the angle number after the switching is substituted for the variable y (step S56), and the Clip information specified by the y-th Clip_information_file-name in Playltem # x is stored in the scenario memory.
- Step S57 Read out to 1 (Step S57), convert the current PTM to I picture address u using EP_map of current Clip information (Step S58), and convert Outjime of Playltem # to EP of current Clip information. — Convert to I-picture address V using map (step S59). After the I picture addresses u and v are changed in this way, the flow shifts to step S46. By shifting to step S46, a TS packet is read from another AVClip, so that the video content is switched.
- step S52 in the loop of FIG. 34 is a determination as to whether an API meaning SkipBack SkipNext is called from the Java virtual machine 38, and if it is called, the process of FIG.
- the processing procedure of the flowchart is executed.
- FIG. 35 is a flowchart showing a processing procedure when the SkipBack, SkipNext API is called.
- SkipBack SkipNext API
- step S61 the current Mark information is obtained by converting the current PI number indicated by the PSR and the current PTM.
- step S62 it is determined whether the pressed key is the SkipNext key or the SkipBack key. If the key is the SkipNext key, the direction flag is set to +1 in step S63, and the SkipBack key is set. If so, the direction flag is set to -1 in step S64.
- step S65 the number obtained by adding the value of the direction flag to the number of the current PLMark is set as the number of the current PLMark. If the key is a SkipNext key, the direction flag is set to +1 and the current PLMark is incremented. If the key is a SkipBack key, the direction flag is set to -1, so the current PLMark will be decremented.
- step S66 PI described in ref—to_PlayItem—Id of the current PLMark is set in Playltem # x, and in step S67, Clip information specified by Clip_information_file_name of Playltem # x is read.
- step S68 mark-time-stamp of the current PLMark is converted to I-picture address u using EP-map of the current Clip information.
- step S69 the Out-time of Playltem # x is converted to an I-picture address V using the EP-map of the current Clip information.
- step S70 the output to the Mark-time-stamp of the current PLMark and the Out-time of Playltem # x is instructed to the Presentation Engine 31, and then the flow proceeds to step S47 in Fig. 33. .
- the I-picture addresses u and v are changed, and the reproduction of another part is ordered.
- the process proceeds to step S47, so that the TS bucket is read from another AVClip, and the video content is switched. Is realized.
- FIG. 36 is a flowchart showing details of the processing procedure by the Presentation Engine 31.
- a loop process including steps S72 to S77 is executed.
- Step S76 in this loop processing defines the requirements for terminating the loop processing. In other words, step S76 is force. Rent The PTM makes Out # time of PI # x a termination requirement of the loop processing.
- Step S73 is whether the fast forward API or the fast reverse API is called from the Java virtual machine 38. Is determined. If a call is made, it is determined in step S78 whether fast forward or fast reverse. If fast forward, the PTS of the next I picture is set to the current PTM (step S79).
- Step S74 is a determination as to whether the menu call API has been called. If so, the current playback process is suspended (step S82), and the menu program for menu processing is executed. (Step S83). According to the above processing, when a menu menu call is made, the processing for menu display is executed after the reproduction processing is interrupted.
- step S75 it is determined whether or not SubPlayItem # y specifying Playltem # x exists according to sync-Playltem-id, and if so, the flow shifts to the flowchart of FIG. FIG. 37 is a flowchart showing the playback procedure of SubPlayltem.
- step S86 it is determined whether or not the current PTM is sync-start_PTS-of_j) layItem of SubPlayItem #. If so, in step S93, the playback control engine 32 is notified to perform the playback process based on SubPlayItem # y.
- Steps S87 to S92 of FIG. 37 are flowcharts showing a reproduction process based on SubPlayItem # y.
- step S87 the Clip information specified by Clip—information—file—name of SubPlayItem # y is read.
- EP map of the current Clip information Is used to convert the Injime of SubPlayItem # y to an address.
- step S89 Out_time of SubPlayItem # y is converted to address] 3 using the EP-map of the current Clip information.
- a step S90 instructs the decoder to output from In-time of SubPlayItem # y to Out-time of SubPlayItem # y.
- Step S53 is a determination as to whether or not the playback control by Presentation Engine 31 has been completed. As long as the processing of the flowchart of FIG. 36 is performed for the last Playltem # x, step S53 is No. become. Only after the processing of the flowchart in FIG. 36 is completed is step S53. YES and the process moves to step S54. Step S54 is the output of the reproduction end event to the Java virtual machine 38, and from this output, the Java virtual machine 38 can know the lapse of the reproduction time of 2 hours.
- step S24 is added between step S1 and step S22, and when step S24 becomes Yes, there is a step S101 to be executed.
- Step S24 is for determining whether or not the JMF player instance exists in the work memory 37. If not, the process proceeds to step S22. If there is, go to step S101.
- Step S101 is a determination as to whether or not a playback end event has been output from the Playback Control Engine 32.If the event has been output, the Java player instance in the work memory is deleted and then (Step S101). S 102), the end of the title is notified to the module manager 34 (step S 26). If not notified, a loop consisting of steps S21 to S24 is repeated. Return.
- steps S22 and S23 are skipped as long as a JMF player instance exists in the work memory 37 (Yes in step S24). Therefore, the title is interpreted as ongoing even if all applications are terminated.
- the application manager 36 can know the lapse of the playback time of 2 hours, so that the menu is displayed as the PL playback end condition, and this menu is displayed. It is possible to realize a control of branching to another title in response to an operation on.
- the sixth embodiment relates to an improvement of providing a data management template in a BD-J object.
- the data management table is a table indicating the Java archive file to be loaded on the local memory 29 in the title time axis in association with the read attribute and the read priority. "Surviving in local memory 29" means that the Java archive files that make up the application are read from local memory 29 and can be transferred to work memory 37 in Java virtual machine 38 State.
- FIG. 39 is a diagram showing an example of the data management table. As shown in this figure, the data management table contains the “live range” of the application, the “applicationID” that identifies the application that has the live range, the “read attribute” of the application, and the “read priority”. Is shown.
- the application management table has the concept of a live range
- the data management table has the same concept of a live range. At first glance, it seems wasteful to have the same concept as the application management table in the data management table, but this is intentional.
- FIG. 40 is a diagram illustrating an execution model assumed by a BD-J object.
- the execution model in this figure is composed of a BD-ROM, a local memory 29, and a Java virtual machine 38, and shows a relationship between the BD-ROM, the local memory 29, and the work memory 37.
- the arrow myl indicates reading between the BD-ROM and the local memory 29, and the arrow my2 indicates reading between the local memory 29 and the work memory 37.
- the annotations above the arrows indicate when these readings occur.
- reading between BD-ROM and oral memory 29 is a so-called "look-ahead" and must be done before the application is needed.
- the arrow my3 indicates the release of the application occupied area in the work memory 37
- the arrow my4 indicates the release of the application occupied area in the local memory 29.
- the annotations on the arrows indicate when these readings occur.
- the release on the work memory 37 is performed at the same time as the end of the application.
- the release on the oral memory 29 is made when it is no longer necessary for the Java virtual machine 38. The point where this is no longer needed is not the "end point". It means "when it is finished and there is no possibility of restarting", that is, when the corresponding title is finished.
- the release point in the work memory 37 is known from the live range in the application management table.
- the disc content to be produced here consists of three titles (title # l, title # 2, title # 3).
- Title # l Java that configures application # l and application # 2 at the start point of the time axis
- the archive file is read into the local memory 29, and application # l and application # 2 are resident in the local memory 29 while the title # l time axis is continuing.
- the Java archive files that make up application # l are released from oral memory 29, and the Java archive files that make up application # 3 are stored in local memory 29 instead.
- Fig. 41 (a) The description of the data management table in this case is as shown in Fig. 41 (a).
- the application ID of the application is described in association with its live range, thereby expressing the application that should reside in the local memory 29. .
- the applicationID of application # l is described in association with title # l
- the applicationID of application # 2 is associated with title # l and title # 2
- the applicationID of application # 3 It can be seen that is described in association with title # 3. In this way, the temporal transition of the local memory 29 occupation is specified by the authoring person.
- the live range specified in the application management table be a fine reproduction unit
- the live range specified in the data management table be a rough reproduction unit.
- Non-seamless playback units such as titles and PLs are desirable for rough playback units.
- a seamless playback unit such as a chapter in a PL is desirable. If the lifespan of the application is determined for each title and for each PL, the application exists in the local memory 29, so that the application can be taken out at any time during playback of the title. In that case, even if the life span of the application is finely defined, the application can be immediately read out to the work memory on the virtual machine, so even if the application is started and terminated frequently. Thus, it is possible to realize smooth application execution.
- the Java archive file was recorded in a separate recording area from the AVClip. But this is only an example.
- the Java archive file may be embedded in the recording area occupied by the AVClip on the BD-ROM.
- FIG. 42 is a diagram showing the embedding of a Java archive file by carouselization.
- the first row shows a Java archive file to be embedded in AVClip, and the second row shows sectioning.
- the third tier shows TS packetization, and the fourth tier shows a TS packet sequence constituting the AVClip.
- the sectioned and TS bucketed data (“D" in the figure) is embedded in the AVClip.
- FIG. 43 is a diagram showing embedding of Java archive files by interleaving.
- the first row is the AVClip to be embedded
- the second row is the Java archive file interleaved with the AVClip
- the third row is the AVClip arrangement in the recording area of the BD-ROM.
- the Java archive file to be embedded in the stream is interleaved and recorded between the divided parts (AVClip2 / 4, 3/4 in the figure) that constitute XXXXX.m2ts that constitute AVClip.
- the Java archive file multiplexed on the AVClip by interleaving will be read out at a higher bandwidth than the dynamic roux celling. Because of this high bandwidth reading, the playback device reads the Java archive file in a relatively short time.
- Java interleaved archive files are not preloaded.
- the current playback time reaches the portion of the AVClip recording area on the BD-ROM where the carousel / interleaved Java archive file is embedded, it is loaded into the local memory 29 of the playback device. .
- the recording format of the Java archive file there are those shown in Fig. 42 and Fig. 43 (a) in addition to those shown in Fig. 2, so the read attribute is set as shown in Fig. 43 (b). Can be done.
- the read attribute is “Preload” indicating that the read is to be read into the mouth-cal memory 29 prior to the title playback, and during the title playback, There are "Load.
- Carousel indicating that the data is read using the carousel method
- "LoadlnterLeave” indicating that the data is read using the interleaving method during title playback.
- the read attribute whether it is carouseled or interleaved is indicated by a subscript, but this may be omitted.
- FIG. 44 (a) shows an example of the data management table.
- FIG. 44 (b) is a diagram showing a change in the storage content of the local memory 29 due to the assignment of the data management table.
- the occupied area in the local memory 29 is shown on the vertical axis, and the horizontal axis is the PL time axis in one title.
- application # l is described so that the entire PL time axis in one title is set as a live range.Therefore, in this title, Chaptei # l to Chaptei # 5, the local memory 29 Will occupy the area.
- the read priority is a priority that determines the priority of reading to the local memory 29.
- the read priority has a plurality of values.
- FIG. 45 (a) is a diagram showing the memory size of the oral memory 29 in the old and new playback devices in comparison.
- Arrow mkl indicates the memory size of the old playback device
- arrow mk2 indicates the memory size of the new playback device. From the comparison of the arrows, it is assumed that the memory size of the local memory 29 in the new playback device is three times or more that of the old playback device. In this way, when memory size varies, applications are classified into two groups as shown in Figure 45. The first is an application (# 1, # 2) that should be read regardless of the memory size. The second is an application (# 3, # 4) that does not want to read on the old playback device but wants to read on the new playback device.
- FIG. 45 (b) is a diagram showing an example of a data management table in which read priorities are set.
- FIG. 46 is a diagram showing a processing procedure of preload control by the application manager 36.
- the data management table in the title to be played is read (steps S1, 1, 1), and the application having the lowest applicationlD while having the highest read priority in the data management table is designated as application i.
- Step S1 1 2 the judgment of Step S1 13 and Step S114, and preloading the application i to the local memory 29 (Step S115).
- the loop processing is repeated until step S116 is determined to be No and step S117 is determined to be No.
- Step S113 is a determination as to whether or not the read attribute of the application i is preload. -Mandatory or Optional. If the read priority is determined to be Mandatory in step S113 and the read priority is determined to be Mandatory in step S114, the application is preloaded in the local memory 29 (step S113). 1 5). If it is determined in step S113 that the read attribute is “speak”, steps S114 to S115 are skipped.
- Step S116 of the two steps that define the requirements for terminating the loop processing determines whether or not an application k with the next highest application ID and the same read priority as application i exists. It is. If such an application; k exists, the application k is made an application (step S119).
- Steps S120 to S123 are processing executed when it is determined in step S114 that the read priority is ⁇ Optional. '
- step S120 it is determined whether or not there is an application having the same application ID and a high read priority; j.
- Step S122 is a step of determining whether or not the remaining capacity of the oral memory 29 exceeds the size of the application i. If step S120 is No and step S122 is Yes, application i will be preloaded into local memory 29 in step S115. If step S120 is No and step S122 is No, the application i will proceed to step S116 without being preloaded into the oral memory 29.
- Step S122 is a step executed when it is determined to be Yes in step S122. If an application j having the same applicationlD and a high read priority exists in the local memory 29, whether the sum of the remaining capacity of the local memory 29 and the size of the application j exceeds the size of the application i It is determined whether or not it is not (Step S122), and if it exceeds, the application on the oral memory 29 is overwritten by using the application i; . If it is less, the application i is not preloaded into the oral memory 29, and the process directly proceeds to step S116. An example of the reading process in steps S115 and S123 will be described with reference to FIG. 47 (a).
- FIG. 47 (a) is a diagram showing an example of a data management table assumed in this specific example.
- an application with a read priority of Mandatory is read into the local memory 29 in step S115.
- an application whose read priority is Optional is read in step S123 after the determination in steps S120 to S122.
- preloading is performed so as to overwrite the application of the same applicationlD already in the local memory 29, so one of the multiple applications is exclusively It will be loaded into local memory 29.
- Java files of different sizes can be loaded into the local memory 29 according to the memory size.Thus, for playback devices with a small memory size, thumbnail images with the minimum necessary resolution A Java archive file with an SD image with a medium resolution is used for a playback device with a medium memory size, and a high resolution is used for a playback device with a large memory size. Java archive files with HD images can be imported to local memory 29.
- FIG. 48 is a diagram illustrating a specific example of the reading process with reference to the data management table.
- the two applications in this figure are two applications that have the same applicationID (application # 3). One of them is embedded in the AVClip, and the read priority is set to mandatory. The other is recorded in a file different from the AVClip, and the read priority is set to Optional. Since the former application is embedded in the AVClip, the live range corresponding to the embedded portion is described as a live range (title # l: chapter # 4 ⁇ # 5). Among these applications, application # 2 and application # 3 are provided with a read attribute indicating a mouth.
- Fig. 48 (b) is a diagram showing application # 2 and application # 3 stored exclusively at different time points on the title time axis. This is a consideration given to playback on a playback device that has only the minimum required memory size. If the data management table having such contents is to be processed, the application manager 36 performs different processing according to the memory scale according to the flowchart of FIG. 46 described above.
- the application manager can load data into the local memory 29 as long as the required memory size is sufficient.
- the problem here is when reading by a playback device with a large memory size. Despite having a large memory scale, the inability to read application # 3 until it reaches Chapter # 4 to Chapter # 5 is a waste of memory scale. Therefore, in the data management table in this figure, the same application # 3 is given a read attribute indicating preload and recorded on the BD-ROM, and these are given the same applicationID.
- step S121 Since the former application has a read priority of ⁇ Optional, it is preloaded only when step S121 becomes Yes (step S115). In this way, the playback device having a large memory size loads the same application embedded in the AVClip into the local memory 29 without waiting for the arrival of title # 1, Chapter # 4 to Chapter # 5. ( Figure 48 (c)).
- FIG. 49 is a diagram showing a processing procedure of the load processing based on the data management table.
- the loop processing consisting of step S131 to step S133 is repeated while the tile playback is continued.
- Step S1311 is for judging whether or not the live section of the application having the start attribute indicating AutoRun has arrived. If it arrives, the application having the startup attribute indicating AutoRun is set to the application q (step S134), and a motion instruction to start the application q is issued to the Java virtual machine 38, and the application q Is read from the local memory 29 to the work memory 37 (step S135).
- -Step S133 is a determination as to whether or not all PLs in the title have been reproduced. This determination is made based on whether or not a playback end event has been received from the Playback Control Engine 32, as described in the fifth embodiment. If completed, the process of this flowchart ends.
- step S132 it is determined whether or not a call has been made from the running application. If there is, the called application is set to the application q (step S136), and it is determined whether or not the current reproduction time point is a live range of the application q in the application management table (step S133). ). If it is not a live range, a start failure is displayed (step S148), and the process returns to the loop consisting of steps S131 to S133. If it is a live range, load processing is performed according to the flowchart in FIG.
- Step S138 in FIG. 50 is a judgment indicating whether or not the current reproduction time point is a live range of the application q in the data management table. If it is not a live range, application q cannot be loaded into local memory 29. In this case, a start instruction to start the application q is issued to the Java virtual machine 38, and the application q is directly read from the BD-ROM to the work memory 37 without passing through the local memory 29. In this case, since a head seek for reading the application occurs, the PL playback is interrupted (step S145).
- step S139 it is determined whether a read attribute is added to the application. Absence of read attribute means that The location q means that it is not carouseled or interleaved. However, even if the read attribute is not added, it is permissible to place the application q in the oral memory 29. Therefore, the application is read out, knowing that the playback has been interrupted. That is, the application is read from the BD-ROM to the oral memory 29, and then the application is read to the work memory 37 (step S140).
- Steps S141 to S146 are processing performed when step S139 is determined to be Yes.
- step S141 it is determined whether or not the application is preloaded by referring to the read attribute. If preloaded, the process moves to step S135. —
- Step S142 is a determination step executed when the read attribute is load, and determines whether application q is carouseled or interleaved. If interleaved, the cache sense is executed by the Java virtual machine 38 (step S144). If the application q exists in the local memory 29, the process proceeds to step S 135, and the application q is sent to the Java virtual machine 38.
- step S144 If there is no application in the local memory 29, exception processing such as branching to the top menu title is performed (step S144). If the carousel is used, a timer is set (step S148), and the cache sense is executed by the Java virtual machine 38 (step S148) until the timer times out (step S148). 4 6). If the application q appears in the local memory 29, the process proceeds to step S135 in FIG. 49, and the application q is loaded into the Java virtual machine 38. If a timeout occurs, exception processing such as branching to the top menu title is performed (step S144).
- FIG. 51 is a diagram schematically showing how an application is read by the Java virtual machine 38.
- Arrows ⁇ I, 2 indicate the reading of Java archive files that are alive in the application management table, are alive in the data management table, and have read attributes indicating force-rucelling and interleaving.
- the arrow ⁇ 1 indicates the local memory 29 sense performed in steps S65 and S67. This local memory 29 sense stores data embedded by carousel or interleaving In this case, the internal memory 29 is sensed because it may exist in the local memory 29.
- the arrow ⁇ 2 is a read corresponding to step S135, and indicates a load from the local memory 29 to the work memory 37 when the application exists in the local memory 29.
- the arrow with X indicates that there is no data in the local memory 29.
- the arrow Vl, 2 indicates that a Java archive file that is alive in the application management table but is not alive in the data management table and has no read attribute exists.
- An arrow VI corresponds to the reading in step S145, and indicates a request for direct reading from the BD-ROM by the Java virtual machine 38.
- the arrow V2 indicates that the Java archive file is read from the BD-ROM to the work memory 37 according to the request.
- Arrows 1, 2, and 3 indicate that a Java archive file that is alive in the application management table and alive in the data management table but has no read attribute is read.
- Arrow 1 corresponds to the reading in step S140, and indicates a request for direct reading from the BD-ROM by the Java virtual machine 38.
- Arrow 2 indicates the read of the Java archive file to the oral memory 29 according to the request.
- Arrow 3 indicates the reading of the Java file from the local memory 29 to the work memory 37.
- FIG. 52 (a) shows the internal structure of a BD-J object according to the seventh embodiment. What is different from FIG. 7 (b) is that a playlist management table has been added.
- FIG. 5.2 (b) is a diagram showing an example of the playlist management table. As shown in this figure, the playlist management table includes a PL specification and a playback attribute of the PL.
- FIG. 53 (a) shows the title time axis in a non-AV title when the playback attribute is set to indicate non-automatic playback.
- the title time axis is determined from the live range of the application, as in the non-AV title.
- FIG. 53 (d) shows a case in which the playback attribute is set to indicate “AutoPlay” in the playlist management table, and the activation of the main application has failed. Also in this case, the default PL playback by the Playback Control Engine 32 is performed irrespective of the failure to start the application, so the time axis of the default PL is the title time axis. '
- the playback attribute of the playlist management table is set to "AutoPlay", it takes 5 to 10 seconds to start the Java application. However, while it is being activated, it will be in a state where something is being shown for the time being. This "state in which something is in the picture" can supplement the startup delay at the start of title execution.
- FIG. 52 (c) is a diagram illustrating what processing is performed by the playback device when there is a PL whose playback attribute is set to AutoPlay in the playlist management table of the branch destination title.
- the application manager 36 in the BD-J module 35 Immediately thereafter, it instructs the Playback Control Engine 32 to start playback of this AutoPlayPL. In this way, the PL whose playback attribute is AutoPlay is instructed to start playback immediately after the title branch.
- the application manager 36 performs the processing according to the processing procedure shown in FIG.
- FIG. 54 is a flowchart showing the processing procedure of the application manager 36 according to the seventh embodiment. This flowchart is different from the flowchart of FIG. 38 in that steps S103 and S104 are added before step S21, so that steps S21 and S22 are interposed. Step S100 is added, and step S105 is added between step S23 and step S26.
- Step S103 is to determine whether or not the playback attribute of the playlist management table of the corresponding title is AutoPlay. If it is AutoPlay, the playback control for the default PL is started by the Playback Control Engine 32 (Step S.I0 Step S1000 determines whether or not the playback is being performed by the Presentation Engine 31. If, go to step S101.
- Step S105 is a determination step executed when Step S23 is Yes and Step S25 is No, and indicates whether or not the playback attribute is AutoPlay. If not, notify the module manager 34 of the end of the title. If it is AutoPlay, the process proceeds to step S1-1, and the process is continued.
- FIG. 7 is a diagram schematically illustrating what kind of reproduction is performed by the reproduction.
- the title to be played here is a non-AV title including a game application that stacks falling tile pieces.
- the playback attribute of the playlist management table is set to AutoPlay
- the default PL playback by the Playback Control Engine 32 is also started. Since the execution of the game application and the playback of the default PL are performed in parallel, a composite image with the foreground as the screen of the game application and the background as the playback image of the default PL is shown in the upper left part of Fig. 55. Will be displayed. It is assumed that this game application ends abnormally on the way.
- the game application is forcibly terminated by the application manager 36, but the title PL is in a state where something is reflected because the default PL is continuously played.
- the BD-J object has two tables, a data management table and an application management table.
- the present embodiment discloses a form in which these are integrated into one table. .
- the item of the read attribute in the data management table is abolished, and an attribute called the ready attribute is provided in the start attribute instead.
- the Ready attribute is a type of an activation attribute indicating that an application is pre-loaded into the oral memory 29 in preparation for a call from another application or a call from the application manager 36.
- Fig. 56 (b) is a diagram showing the relationship between application handling and startup attributes.
- the application is handled by whether it is preloaded (1), automatically started when the current playback point reaches the valid section, or responded to a call from another. It is either activated (2), loaded according to the progress of the title regeneration (3), or alive, and these differences lead to the five aspects shown in Fig. 56 (b). Appear.
- the startup attribute is set to AutoRun when preloading is performed and "automatic startup", and when loading is performed and "automatic startup”.
- the application manager 36 can load the application whose start attribute is set to AutoRun and the application whose start attribute is set to Ready before starting the title playback. Preloads the memory 29. By doing so, it becomes possible to preload the application into the local memory 29 without providing the read attribute.
- FIG. 57 is a diagram schematically illustrating how an application is read by the Java virtual machine 38 according to the eighth embodiment. The reading in this figure is based on Figure 51.
- Arrows ⁇ 1,2 indicate the reading of a Java archive file that is alive in the application's data management table and whose startup attribute is set to the Ready attribute. Arrows 1, 2, and 3 indicate that an application whose application attribute is “Persistent” is loaded in the application's overnight management table.
- the processing by the application manager 36 can be simplified. Can be. It should be noted that the application's data management table may be further simplified by eliminating the read priority.
- the ninth embodiment is an embodiment in which the read priority is represented by a combination of information meaning Optional and a numerical value from 0 to 255.
- FIG. 59 is a diagram showing a data management table to which group attributes have been assigned.
- the group attribute can be set in two ways, such as no exclusive group and exclusive group. If there is an exclusive group, the group number is described. In Fig. 59 (a), “#" in title # l indicates that there is no exclusive group. On the other hand, “group # l” in title # 2 and # 3 indicates that there is an exclusive group, and title # 2 and # 3 ′ indicate that the group belongs to the exclusive group called group # l.
- the playback device After reading each application into the local memory 29 based on the data management table, the playback device according to the present embodiment verifies the group attribute of the application in the local memory 29. If there are two or more applications belonging to the same exclusive group in the local memory 29, one of them is deleted from the oral memory 29.
- a specific example of an exclusive group is a group consisting of a launcher application and an application started by this application. Since the number of applications activated by this application is limited to one in principle, the local memory 29 is a chopstick that has only one launcher + 1 application. If there are three or more applications, the application manager 36 must perform the process of deleting them from the local memory 29. The application checks whether the existing application is a launcher + 1 application.
- FIG. 60 is a diagram showing variations of the allocation unit.
- the first row shows the three applications recorded on the BD-ROM.
- the management table is shown.
- the second row shows the title unit
- the third row shows the disk unit
- the fourth row shows the disk set unit composed of multiple BD-ROMs.
- the arrows in the figure schematically show the assignment of the application management table. Referring to this arrow, the application management tables # 1, # 2, and # 3 in the first row are assigned to titles # 1, # 2, and # 3, respectively, shown in the second row. You can see it.
- application management table # 4 is allocated for each disk, and application management table # 5 is allocated for the entire disk set. In this way, by setting the allocation unit of the application management table to a unit larger than the title, an application that survives while one BD-ROM is being loaded or one of the multiple BD-ROMs is loaded. An application can be defined that survives while it is being served.
- the optical disc according to the present invention is implemented as a BD-ROM.
- the optical disc of the present invention is characterized by a recorded dynamic scenario and an index table. -Does not depend on the physical properties of the ROM. Any recording medium that can record the dynamic scenario and the Index Table may be used. For example,
- Optical discs such as DVD-ROM, DVD-RAM, DVD-RW, DVD-R, DVD + RW, DVD + R, CD-R, and CD-RW; and magneto-optical discs such as PD and MO may be used.
- a semiconductor memory card such as a compact flash card, a smart media, a memory stick, a multimedia card, a PCM-CIA card, etc. may be used.
- a magnetic recording disk (i) such as a flexible disk, SuperDisk, Zip, Clik !, or a removable hard disk drive such as an ORB, Jaz, SparQ, SyJet, EZFley, or a micro drive may be used.
- a hard disk with a built-in device may be used.
- the playback device in all the embodiments decodes the AVClip recorded on the BD-ROM and outputs it to the TV, but the playback device is only a BD-ROM drive, and the other components are
- the TV may be provided.
- the playback device and the TV can be incorporated in a home network connected by IEEE1394.
- the playback device in the embodiment is of a type used by connecting to a television, but may be a playback device integrated with a display.
- only the portion that forms an essential part of the processing may be used as the playback device.
- the playback device is manufactured based on the internal configuration of the playback device described in each embodiment regardless of any of these aspects.
- the act is an act of practicing the invention described in the specification of the present application.
- the transfer of the playback device shown in each embodiment at no charge (free of charge, sales and free of charge is a gift), lending, and import are also implementations of the present invention.
- the act of inviting the general user to transfer or lend these items by displaying them at stores, soliciting logs, and distributing pamphlets is also an act of implementing the playback device.
- (E) Menu for displaying a list of chapters (Chapter Menu) and its behavior are controlled.
- the MOVIE object to be controlled may be recorded on a BD-ROM so that it can be branched from the Tbp Menu. It may be called by pressing the Chapter key of the remote control key.
- TP-extra-header When recording on a BD-ROM, it is desirable to add an extension header to each TS bucket constituting the AVClip.
- the extension header is called TP-extra-header, and has a data length of 4 bytes including U Arribval-Time-Stamp, u copy_j> ermission_indicator and 3 ⁇ 4 :.
- TP_extra — TS buckets with headers (hereinafter abbreviated as EX-attached TS packets) are grouped in groups of 32 and written to three sectors.
- the 32 TS packets with EX in 3 sectors are called "Aligned Unit".
- the playback device 200 When used in a home network connected via IEEE1394, the playback device 200 transmits Aligned Units by the following transmission processing.
- the sender device removes the TP-extra-header from each of the 32 EX-attached TS packets included in the Aligned Unit, encrypts the TS bucket body based on the DTCP standard, and outputs it.
- isochronous packets are inserted everywhere between TS buckets. This insertion point is based on the time indicated in the Arribval-ime-Stamp of the TP-extra-header.
- the playback device 200 outputs DTCP_Descriptor with the output of the TS bucket.
- DTCP_Descriptor indicates copy permission / prohibition setting in TP-extra-header. If the DTCP_Descriptor is described to indicate “copy prohibited” here, the TS bucket will not be recorded on other devices when used in a home network connected via IEEE1394.
- the digital stream recorded on the recording medium is the AVClip, but may be a DVD-Video standard or a DVD-Video Recordin standard VOB (Video Object).
- VOB is a program stream conforming to the ISO / IEC13818-1 standard, obtained by multiplexing video streams and audio streams.
- the video stream in AVClip may be in MPEG4 or WMV format.
- the audio stream may be a Linear-PCM system, a Dolby-AC3 system, an MP3 system, an MPEG-AAC system, Dts, or WMA (Windows media audio).
- the video work in each embodiment is an analog video signal broadcast on analog broadcast. It may be obtained by encoding a signal. It may be stream data composed of a transport stream broadcast by digital broadcasting. Also, the contents may be obtained by encoding analog / digital video signals recorded on a video tape. Furthermore, the content may be obtained by encoding an analog / digital video signal directly taken from a video camera. Alternatively, it may be a digital work distributed by a distribution server.
- the DBD-J module 35 may be a Java platform embedded in a device for receiving satellite broadcasting. If the BD-J module 35 is such a Java platform, the playback device according to the present invention is Also, it can be used as STB for MHP.- Further, it may be a Java platform embedded in a device for processing control of a mobile phone.This BD-J module 35 is a Java platform. If so, the playback device according to the present invention will also serve as a mobile phone.
- the MOVIE mode may be placed above the BD-J mode.
- the interpretation of the dynamic scenario in the MOVIE mode and the execution of control procedures based on the dynamic scenario place a light burden on the playback device, so that there is no problem if the MOVIE mode is executed in the BD-J mode. Because.
- only one mode of operation guarantee is required.
- the reproduction process may be executed only in the BD-J mode.
- the playback control synchronized with the PL playback can be performed, so that the MOVIE mode does not have to be provided.
- a navigation command may be provided in the interactive graphics stream to be multiplexed on the DAVClip, and a branch from one PL to another PL may be realized.
- the playback device according to the present invention may be used for personal use, such as in a home theater system.
- the internal configuration of the present invention is disclosed in the above embodiment, and since it is clear that mass production is performed based on this internal configuration, the present invention can be industrially used in terms of quality. From this, the reproducing apparatus according to the present invention has industrial applicability.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Management Or Editing Of Information On Record Carriers (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
- Indexing, Searching, Synchronizing, And The Amount Of Synchronization Travel Of Record Carriers (AREA)
- Television Signal Processing For Recording (AREA)
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2004800296950A CN1867998B (zh) | 2003-10-10 | 2004-10-12 | 记录方法、再现装置、再现方法 |
EP04773789A EP1677302A4 (en) | 2003-10-10 | 2004-10-12 | INFORMATION MEDIUM, REPRODUCTION DEVICE, PROGRAM, AND REPRODUCTION METHOD |
US10/573,173 US7515812B2 (en) | 2003-10-10 | 2004-10-12 | Recording medium, reproduction device, program, and reproduction method |
JP2005514682A JP3825463B2 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法。 |
KR1020067007232A KR101059343B1 (ko) | 2003-10-10 | 2004-10-12 | 기록매체, 재생장치, 기록방법, 재생방법 |
US12/393,001 US8107788B2 (en) | 2003-10-10 | 2009-02-25 | Recording medium, playback device, recording method and playback method |
US12/797,804 US8406604B2 (en) | 2003-10-10 | 2010-06-10 | Playback apparatus, recording method, and playback method |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003352913 | 2003-10-10 | ||
JP2003-352913 | 2003-10-10 | ||
JP2003379758 | 2003-11-10 | ||
JP2003-379758 | 2003-11-10 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/573,173 A-371-Of-International US20090107221A1 (en) | 2004-07-02 | 2004-07-02 | Hardness tester with indenter of hard metal or compound and oscillating crown for testing at high load and method of comparative assesment of the hardness/depth profile |
US12/393,001 Division US8107788B2 (en) | 2003-10-10 | 2009-02-25 | Recording medium, playback device, recording method and playback method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005036555A1 true WO2005036555A1 (ja) | 2005-04-21 |
Family
ID=34436929
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/015333 WO2005036545A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
PCT/JP2004/015330 WO2005036554A1 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法 |
PCT/JP2004/015335 WO2005036546A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
PCT/JP2004/015339 WO2005036555A1 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法 |
PCT/JP2004/015337 WO2005036547A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/015333 WO2005036545A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
PCT/JP2004/015330 WO2005036554A1 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法 |
PCT/JP2004/015335 WO2005036546A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/015337 WO2005036547A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
Country Status (7)
Country | Link |
---|---|
US (10) | US7715696B2 (ja) |
EP (9) | EP1944771A3 (ja) |
JP (6) | JP4117006B2 (ja) |
KR (7) | KR100937790B1 (ja) |
CN (2) | CN101840718B (ja) |
TW (1) | TW200518070A (ja) |
WO (5) | WO2005036545A1 (ja) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008532197A (ja) * | 2005-02-28 | 2008-08-14 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | データ再生のためのフォールバックメカニズム |
WO2006061743A3 (en) * | 2004-12-06 | 2008-10-16 | Koninkl Philips Electronics Nv | Method, device, and recording medium for extending interactivity to multiple storage media |
WO2009128246A1 (ja) | 2008-04-16 | 2009-10-22 | パナソニック株式会社 | 記録媒体、記録装置、記録方法、及び再生装置 |
US20090269030A1 (en) * | 2004-07-30 | 2009-10-29 | Samsung Electronics Co., | Storage medium including av data and application program, and apparatus and method using the same |
EP2180477A1 (en) | 2004-07-22 | 2010-04-28 | Panasonic Corporation | Playback apparatus and playback method |
WO2010052857A1 (ja) * | 2008-11-06 | 2010-05-14 | パナソニック株式会社 | 再生装置、再生方法、再生プログラム、及び集積回路 |
JP2011159314A (ja) | 2005-02-23 | 2011-08-18 | Thomson Licensing | ソフトウエア・アプリケーションを実行するための方法および装置 |
EP2387037A1 (en) | 2005-01-28 | 2011-11-16 | Panasonic Corporation | Reproduction device for mixing a primary audio stream with a secondary audio stream |
JP2020055054A (ja) * | 2018-09-28 | 2020-04-09 | ブラザー工業株式会社 | 工具寿命管理装置、工作機械、表示処理方法及びコンピュータプログラム |
Families Citing this family (79)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TW200518070A (en) * | 2003-10-10 | 2005-06-01 | Matsushita Electric Ind Co Ltd | Recording medium, reproduction device, program, and reproduction method |
US8218951B2 (en) * | 2003-10-30 | 2012-07-10 | Samsung Electronics Co., Ltd. | Storage medium storing program management information, and reproducing method and apparatus |
ATE389935T1 (de) * | 2003-11-10 | 2008-04-15 | Matsushita Electric Ind Co Ltd | Aufzeichnungsmedium, wiedergabeeinrichtung, programm, wiedergabeverfahren und systemintegrierte schaltung |
KR20050066265A (ko) * | 2003-12-26 | 2005-06-30 | 엘지전자 주식회사 | 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치 |
KR20050066264A (ko) | 2003-12-26 | 2005-06-30 | 엘지전자 주식회사 | 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치 |
JP4626799B2 (ja) * | 2004-07-12 | 2011-02-09 | ソニー株式会社 | 再生装置および方法、情報提供装置および方法、データ、記録媒体、並びにプログラム |
CN101916579A (zh) * | 2004-07-22 | 2010-12-15 | 松下电器产业株式会社 | 用于执行应用程序同步重放的重放装置 |
KR100677132B1 (ko) * | 2004-09-09 | 2007-02-02 | 삼성전자주식회사 | 동영상 재생 및 프로그래밍 기능을 위한 멀티미디어데이터를 기록한 저장 매체, 그 재생 장치 및 재생 방법 |
WO2006051037A1 (en) * | 2004-11-09 | 2006-05-18 | Thomson Licensing | Bonding contents on separate storage media |
KR20060059572A (ko) * | 2004-11-29 | 2006-06-02 | 삼성전자주식회사 | 플레이리스트를 자동 재생하기 위한 정보를 포함하는 저장매체, 그 재생 장치 및 재생 방법 |
KR20060081337A (ko) * | 2005-01-07 | 2006-07-12 | 엘지전자 주식회사 | 비밀키를 이용한 암호화 및 복호화 방법 |
KR20060085154A (ko) * | 2005-01-21 | 2006-07-26 | 엘지전자 주식회사 | 기록매체, 로컬 스토리지를 이용한 기록매체의 재생방법과재생장치 |
CN102081944B (zh) * | 2005-02-04 | 2012-12-26 | 松下电器产业株式会社 | 读取装置、记录方法及读取方法 |
EP1783769A4 (en) * | 2005-02-18 | 2011-11-30 | Panasonic Corp | CONTINUOUS REPRODUCTION DEVICE AND CONTINUOUS POWER SUPPLY DEVICE |
CN101133646B (zh) * | 2005-03-03 | 2010-05-19 | 皇家飞利浦电子股份有限公司 | 用于光盘应用的流文件系统 |
US20080022343A1 (en) * | 2006-07-24 | 2008-01-24 | Vvond, Inc. | Multiple audio streams |
US8904463B2 (en) * | 2005-03-09 | 2014-12-02 | Vudu, Inc. | Live video broadcasting on distributed networks |
US7698451B2 (en) * | 2005-03-09 | 2010-04-13 | Vudu, Inc. | Method and apparatus for instant playback of a movie title |
US20090025046A1 (en) * | 2005-03-09 | 2009-01-22 | Wond, Llc | Hybrid architecture for media services |
US7937379B2 (en) * | 2005-03-09 | 2011-05-03 | Vudu, Inc. | Fragmentation of a file for instant access |
US20090019468A1 (en) * | 2005-03-09 | 2009-01-15 | Vvond, Llc | Access control of media services over an open network |
US8219635B2 (en) * | 2005-03-09 | 2012-07-10 | Vudu, Inc. | Continuous data feeding in a distributed environment |
US9176955B2 (en) * | 2005-03-09 | 2015-11-03 | Vvond, Inc. | Method and apparatus for sharing media files among network nodes |
US7191215B2 (en) * | 2005-03-09 | 2007-03-13 | Marquee, Inc. | Method and system for providing instantaneous media-on-demand services by transmitting contents in pieces from client machines |
US8099511B1 (en) | 2005-06-11 | 2012-01-17 | Vudu, Inc. | Instantaneous media-on-demand |
US8799757B2 (en) * | 2005-07-01 | 2014-08-05 | Microsoft Corporation | Synchronization aspects of interactive multimedia presentation management |
US8020084B2 (en) * | 2005-07-01 | 2011-09-13 | Microsoft Corporation | Synchronization aspects of interactive multimedia presentation management |
US20080238938A1 (en) * | 2005-08-29 | 2008-10-02 | Eklund Don | Effects for interactive graphic data in disc authoring |
JP4972933B2 (ja) * | 2005-12-28 | 2012-07-11 | ソニー株式会社 | データ構造、記録装置、記録方法、記録プログラム、再生装置、再生方法および再生プログラム |
US20070223889A1 (en) * | 2006-03-16 | 2007-09-27 | Dandekar Shree A | Embedded high definition media management module for information handling systems |
JP2007328692A (ja) * | 2006-06-09 | 2007-12-20 | Canon Inc | 代数演算方法及びその装置、プログラム |
US8296812B1 (en) | 2006-09-01 | 2012-10-23 | Vudu, Inc. | Streaming video using erasure encoding |
EP1923781A1 (en) * | 2006-11-14 | 2008-05-21 | Thomson Holding Germany GmbH & Co. OHG | Method and device for sequentially processing a plurality of programs |
US8015548B2 (en) * | 2007-03-22 | 2011-09-06 | Arcsoft, Inc. | Method for obtaining context of corresponding Xlet while playing BD-J title |
JP5406044B2 (ja) * | 2007-12-17 | 2014-02-05 | パナソニック株式会社 | 個別販売に用いられる記録媒体、記録装置、再生装置、それらの方法 |
KR100943907B1 (ko) * | 2008-01-10 | 2010-02-24 | 엘지전자 주식회사 | 데이터 재생방법 및 기록재생장치 및 디지털 방송수신장치 |
EP2107567A1 (en) * | 2008-04-04 | 2009-10-07 | Deutsche Thomson OHG | Data carrier carrying a set of machine-interpretable instructions and media content which is presented upon execution of said machine-interpretable instructions |
US8380042B2 (en) * | 2008-04-16 | 2013-02-19 | Panasonic Corporation | Reproduction device, reproduction method, and program |
KR101486772B1 (ko) * | 2008-06-04 | 2015-02-04 | 삼성전자주식회사 | 재생 위치에 따라 디지털 컨텐츠를 관리하는 방법과 장치및 실행하는 방법 및 장치 |
JP2010009408A (ja) * | 2008-06-27 | 2010-01-14 | Sony Corp | 情報処理装置、およびデータ処理方法、並びにプログラム |
JP5395074B2 (ja) * | 2008-07-16 | 2014-01-22 | パナソニック株式会社 | 再生装置、再生方法、プログラム |
US8045429B2 (en) | 2008-07-29 | 2011-10-25 | Fujitsu Ten Limited | Control apparatus and method for content reproducing |
US8566869B2 (en) * | 2008-09-02 | 2013-10-22 | Microsoft Corporation | Pluggable interactive television |
US20100088602A1 (en) * | 2008-10-03 | 2010-04-08 | Microsoft Corporation | Multi-Application Control |
ES2536114T3 (es) * | 2008-11-06 | 2015-05-20 | Deluxe Media Inc. | Marcadores de posición en una tabla de índices para actualizar un medio de almacenamiento portátil |
KR101227289B1 (ko) * | 2008-12-04 | 2013-01-29 | 미쓰비시덴키 가부시키가이샤 | 영상 정보 재생 방법, 영상 정보 재생 장치, 기록 매체 및 영상 컨텐츠 |
JP5433239B2 (ja) * | 2009-01-15 | 2014-03-05 | 日本放送協会 | 放送型アプリケーションの起動システム |
KR101862351B1 (ko) * | 2009-01-21 | 2018-05-29 | 삼성전자주식회사 | 콘텐트 정보 제공 및 재생 방법 및 장치 |
KR20100111996A (ko) * | 2009-04-08 | 2010-10-18 | 삼성전자주식회사 | 가상 이미지 파일 처리 방법 및 장치 |
US9263085B2 (en) | 2009-05-20 | 2016-02-16 | Sony Dadc Austria Ag | Method for copy protection |
EP2254117B1 (en) | 2009-05-20 | 2018-10-31 | Sony DADC Austria AG | Method for copy protection |
EP2254120A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
EP2254119B1 (en) | 2009-05-20 | 2019-03-13 | Sony DADC Austria AG | Method for copy protection |
EP2254116A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
CN102422355A (zh) | 2009-05-20 | 2012-04-18 | 索尼达德克奥地利股份公司 | 用于拷贝保护的方法 |
EP2254118A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
EP2254121A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
JP5215255B2 (ja) * | 2009-07-10 | 2013-06-19 | シャープ株式会社 | プログラム実行装置、プログラム実行方法、コンテンツ再生装置、プログラムおよび記録媒体 |
WO2011007417A1 (ja) * | 2009-07-14 | 2011-01-20 | パイオニア株式会社 | 再生装置及び方法、並びにコンピュータプログラム |
US8401370B2 (en) * | 2010-03-09 | 2013-03-19 | Dolby Laboratories Licensing Corporation | Application tracks in audio/video containers |
JP2011216165A (ja) | 2010-04-01 | 2011-10-27 | Alpine Electronics Inc | ビデオ再生装置、コンピュータプログラム及びレジューム再生方法 |
US8909029B2 (en) * | 2010-10-13 | 2014-12-09 | Sony Corporation | Capturing playback key events in BD players |
US8648959B2 (en) | 2010-11-11 | 2014-02-11 | DigitalOptics Corporation Europe Limited | Rapid auto-focus using classifier chains, MEMS and/or multiple object focusing |
JP6018797B2 (ja) * | 2011-05-20 | 2016-11-02 | 日本放送協会 | 受信機 |
US8355305B1 (en) * | 2011-07-14 | 2013-01-15 | Disney Enterprises, Inc. | System and method for initialization of media asset modules for improved execution sequence on a playback environment |
JP5857636B2 (ja) * | 2011-11-02 | 2016-02-10 | ソニー株式会社 | 情報処理装置、情報処理方法及びプログラム |
JP6345424B2 (ja) * | 2012-04-19 | 2018-06-20 | サターン ライセンシング エルエルシーSaturn Licensing LLC | 受信装置、受信方法、送信装置、送信方法、プログラム、及びテレビジョン受像機 |
KR20140018743A (ko) * | 2012-08-03 | 2014-02-13 | 삼성전자주식회사 | 디스크리스 어플리케이션 재생 장치 및 기록 장치, 재생 방법 및 기록 방법과 디스크리스 어플리케이션을 기록한 정보저장매체 |
CN102917246B (zh) * | 2012-08-31 | 2015-01-14 | 北京视博云科技有限公司 | 一种基于虚拟机的应用数据提供方法、装置及系统 |
KR20140039504A (ko) * | 2012-09-24 | 2014-04-02 | 삼성전자주식회사 | 블루레이 디스크 재생 장치 및 블루레이 디스크 로딩 방법 |
EP2908539B1 (en) * | 2012-10-10 | 2019-12-18 | Saturn Licensing LLC | Reception device, reception method, transmission device, transmission method, and program |
CN105103232B (zh) | 2013-03-28 | 2017-09-22 | 三菱电机株式会社 | 再现装置、控制方法以及程序 |
CN104679578B (zh) * | 2015-03-12 | 2018-09-07 | 绚视软件科技(上海)有限公司 | BD-java平台上的最小内存自适应机制及使用方法 |
CN104951340B (zh) * | 2015-06-12 | 2018-07-06 | 联想(北京)有限公司 | 一种信息处理方法及装置 |
WO2017056194A1 (ja) * | 2015-09-29 | 2017-04-06 | 株式会社 東芝 | 情報機器または情報通信端末および、情報処理方法 |
KR102401772B1 (ko) * | 2015-10-02 | 2022-05-25 | 삼성전자주식회사 | 전자 장치에서 어플리케이션 실행 장치 및 방법 |
US10204059B2 (en) * | 2016-09-29 | 2019-02-12 | International Business Machines Corporation | Memory optimization by phase-dependent data residency |
CN106980579B (zh) | 2016-09-30 | 2020-08-14 | 阿里巴巴集团控股有限公司 | 一种图片加载方法及装置 |
US10506268B2 (en) * | 2016-10-14 | 2019-12-10 | Spotify Ab | Identifying media content for simultaneous playback |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH064166A (ja) * | 1992-06-24 | 1994-01-14 | Okayama Nippon Denki Software Kk | ジョブの有効期間設定装置 |
JPH06230946A (ja) * | 1993-02-07 | 1994-08-19 | Fuji Xerox Co Ltd | 自動プログラム開始装置 |
JPH1063362A (ja) * | 1996-08-16 | 1998-03-06 | Nec Corp | レジューム要因別に複数のプログラム状態を保持可能なサスペンドレジューム方法 |
JP2001238161A (ja) * | 2000-02-25 | 2001-08-31 | Sony Corp | 情報付加装置、情報付加方法および記録媒体 |
JP2002057990A (ja) * | 2000-08-09 | 2002-02-22 | Nec Corp | 映像再生システム及びそれに用いるデータ同期方式 |
JP2002369154A (ja) * | 2001-04-02 | 2002-12-20 | Matsushita Electric Ind Co Ltd | ディジタル映像コンテンツの映像再生装置、映像再生方法、映像再生プログラム、パッケージメディア |
JP2003249057A (ja) * | 2002-02-26 | 2003-09-05 | Toshiba Corp | デジタル情報媒体を用いるエンハンスド・ナビゲーション・システム |
JP2004206863A (ja) * | 2002-12-09 | 2004-07-22 | Toshiba Corp | 情報再生装置及び情報再生方法 |
Family Cites Families (63)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0491104A (ja) | 1990-08-06 | 1992-03-24 | Ootex Kk | 光重合反応開始剤 |
JPH0491078A (ja) | 1990-08-06 | 1992-03-24 | Kao Corp | イミダゾール誘導体 |
JPH0759608B2 (ja) | 1990-08-06 | 1995-06-28 | 株式会社クラレ | イミド化アクリル樹脂粒子体の処理方法 |
JP2609749B2 (ja) | 1990-08-31 | 1997-05-14 | 日本電気アイシーマイコンシステム株式会社 | 電流供給回路 |
JP2798490B2 (ja) | 1990-09-03 | 1998-09-17 | 日本電気アイシーマイコンシステム株式会社 | 発振回路 |
CN100351911C (zh) * | 1995-08-21 | 2007-11-28 | 松下电器产业株式会社 | 根据交互控制实现意外性场景展开的多媒体光盘再生装置 |
EP0788104B1 (en) * | 1995-08-21 | 1999-02-24 | Matsushita Electric Industrial Co., Ltd. | Multimedia optical disk capable of preserving freshness of image content for long time and its reproduction apparatus and method |
WO1997007511A1 (fr) * | 1995-08-21 | 1997-02-27 | Matsushita Electric Industrial Co., Ltd. | Disque optique multimedia pour lequel le producteur coordonne le mode vision/ecoute, notamment une reproduction speciale a la demande, dispositif reproducteur et procede de reproduction du disque |
US5915067A (en) * | 1995-08-21 | 1999-06-22 | Matsushita Electric Industiral Co., Ltd. | Multimedia optical disc facilitating branch reproduction to parental lock sections using reduced control information and a reproducing device for said disc |
EP0777230A1 (de) * | 1995-12-04 | 1997-06-04 | Markus Zwickl | CDs enthaltend zusätzliche Textinformation |
WO1997039451A1 (fr) * | 1996-04-12 | 1997-10-23 | Matsushita Electric Industrial Co., Ltd. | Disque optique multimedia contenant des titres d'images de sorte qu'il soit possible de determiner instantanement si des fonctions av sont necessaires pour leur reproduction, appareil et procede pour reproduire ceux-ci |
CN1260970C (zh) * | 1996-05-09 | 2006-06-21 | 松下电器产业株式会社 | 用于多媒体光盘的记录方法、再生装置及再生方法 |
JP3948051B2 (ja) | 1997-04-30 | 2007-07-25 | ソニー株式会社 | 編集装置及びデータ編集方法 |
JP3655433B2 (ja) * | 1997-06-20 | 2005-06-02 | パイオニア株式会社 | コンピュータ読み取り可能な記録媒体及び情報再生装置 |
JPH11219313A (ja) | 1998-02-02 | 1999-08-10 | Mitsubishi Electric Corp | コンテンツ先読み方法 |
WO1999050771A1 (en) | 1998-03-31 | 1999-10-07 | International Business Machines Corporation | A method and apparatus for creating an electronic commerce system |
JPH11296381A (ja) * | 1998-04-08 | 1999-10-29 | Matsushita Electric Ind Co Ltd | 仮想マシン及びコンパイラ |
JP3262539B2 (ja) | 1998-06-15 | 2002-03-04 | 株式会社ディジタル・ビジョン・ラボラトリーズ | データ放送方式及び同方式に適用されるデータ受信装置 |
EP0989743A1 (en) * | 1998-09-25 | 2000-03-29 | CANAL+ Société Anonyme | Application data table for a multiservice digital transmission system |
JP2000149514A (ja) * | 1998-11-10 | 2000-05-30 | Alpine Electronics Inc | ディスク再生装置 |
US7634787B1 (en) * | 1999-06-15 | 2009-12-15 | Wink Communications, Inc. | Automatic control of broadcast and execution of interactive applications to maintain synchronous operation with broadcast programs |
JP2001022625A (ja) | 1999-07-09 | 2001-01-26 | Sony Corp | データ記録装置、データ記録方法、データ取得装置、データ取得方法 |
US6874145B1 (en) | 1999-07-13 | 2005-03-29 | Sun Microsystems, Inc. | Methods and apparatus for implementing an application lifecycle design for applications |
JP2003504753A (ja) | 1999-07-13 | 2003-02-04 | サン・マイクロシステムズ・インコーポレイテッド | アプリケーションライフサイクルに従ってアプリケーションを管理するための方法および装置 |
JP3756708B2 (ja) * | 1999-09-30 | 2006-03-15 | 株式会社東芝 | 情報処理端末装置およびそのファイル管理方法 |
AU770163B2 (en) | 1999-10-29 | 2004-02-12 | Opentv, Corp. | System and method for recording pushed data |
AU770707B2 (en) | 1999-10-29 | 2004-02-26 | Opentv, Corp. | Playback of interactive programs |
JP2003514335A (ja) | 1999-11-10 | 2003-04-15 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | 記録担体、記録担体を再生する装置、記録担体を再生する方法、記録担体を記録する装置及び記録担体を記録する方法 |
US7200857B1 (en) * | 2000-06-09 | 2007-04-03 | Scientific-Atlanta, Inc. | Synchronized video-on-demand supplemental commentary |
EP2546833A3 (en) | 2000-04-21 | 2014-08-20 | Sony Corporation | Information processing apparatus, method and computer program |
GB0016062D0 (en) | 2000-06-30 | 2000-08-23 | Koninkl Philips Electronics Nv | Playback of applications with non-linear time |
GB2370658A (en) | 2000-12-29 | 2002-07-03 | Metadyne Ltd | A modular software framework |
JP2002238161A (ja) | 2001-02-14 | 2002-08-23 | Yanmar Diesel Engine Co Ltd | 分散電源用発電機の出力方法 |
JP2002269929A (ja) | 2001-03-08 | 2002-09-20 | Hitachi Ltd | ディスク装置 |
KR20030007706A (ko) * | 2001-04-02 | 2003-01-23 | 마츠시타 덴끼 산교 가부시키가이샤 | 디지털 영상 콘텐츠의 영상재생 장치, 영상재생 방법,영상재생 프로그램, 패키지 미디어 |
KR100771264B1 (ko) | 2001-05-12 | 2007-10-29 | 엘지전자 주식회사 | 스크립트 파일이 포함 기록된 기록매체와, 그 재생장치 및방법 |
JP2003032637A (ja) | 2001-07-16 | 2003-01-31 | Sharp Corp | データ放送受信装置 |
DE60223483T2 (de) | 2001-10-29 | 2008-09-18 | Humax Co. Ltd., Yougin | Verfahren zum aufzeichenen eines digitalen Rundfunkprogramms und zeitbasierter Wiedergabe eines aufgezeichneten Rundfunkprogramms und zugehörige Vorrichtung |
JP3921593B2 (ja) | 2001-11-30 | 2007-05-30 | ソニー株式会社 | 情報処理装置および方法、プログラム格納媒体、プログラム、並びに情報記録媒体 |
TW200300928A (en) * | 2001-11-30 | 2003-06-16 | Sony Corportion | Information processing method and apparatus, program storage medium, program and information recording medium |
US6968445B2 (en) | 2001-12-20 | 2005-11-22 | Sandbridge Technologies, Inc. | Multithreaded processor with efficient processing for convergence device applications |
GB0130534D0 (en) | 2001-12-20 | 2002-02-06 | Aspex Technology Ltd | Improvements relating to data transfer addressing |
AU2003206150A1 (en) * | 2002-02-07 | 2003-09-02 | Samsung Electronics Co., Ltd | Information storage medium containing display mode information, and reproducing apparatus and method therefor |
JP4532810B2 (ja) | 2002-02-22 | 2010-08-25 | キヤノン株式会社 | 画像処理装置、画像処理装置の制御方法、プログラム、及びコンピュータ読み取り可能な記憶媒体 |
JP3990928B2 (ja) | 2002-03-19 | 2007-10-17 | キヤノン株式会社 | テレビジョン放送受信装置、再生方法及びプログラム |
US7814025B2 (en) * | 2002-05-15 | 2010-10-12 | Navio Systems, Inc. | Methods and apparatus for title protocol, authentication, and sharing |
DE10228103A1 (de) | 2002-06-24 | 2004-01-15 | Bayer Cropscience Ag | Fungizide Wirkstoffkombinationen |
WO2004001751A1 (en) * | 2002-06-24 | 2003-12-31 | Lg Electronics Inc. | Recording medium having data structure including navigation control information for managing reproduction of video data recorded thereon and recording and reproducing methods and apparatuses |
BR0313688A (pt) * | 2002-08-26 | 2005-06-21 | Samsung Electronics Co Ltd | Mìdia de armazenamento de informações, método de processamento de uma entrada de usuário em um modo interativo em que dados de av são reproduzidos com um documento de marcação, aparelho para reprodução de dados de av em um modo interativo, dispositivo de reprodução, e método de processamento de uma entrada de usuário em um modo interativo |
CA2497697C (en) * | 2002-09-12 | 2013-07-09 | Matsushita Electric Industrial Co., Ltd. | Recording medium, playback device, program, playback method, and recording method |
US7715695B2 (en) * | 2002-11-26 | 2010-05-11 | Panasonic Corporation | Apparatus for managing removable storage media that can be connected thereto, and method, program, and system LSI for managing removable storage media |
KR101027200B1 (ko) | 2003-02-21 | 2011-04-06 | 파나소닉 주식회사 | 기록매체, 재생장치, 기록방법 및 재생방법 |
KR100957799B1 (ko) | 2003-03-06 | 2010-05-13 | 엘지전자 주식회사 | 대화형 디스크의 재생환경 설정방법 |
US7563748B2 (en) | 2003-06-23 | 2009-07-21 | Cognis Ip Management Gmbh | Alcohol alkoxylate carriers for pesticide active ingredients |
KR101014665B1 (ko) * | 2003-10-06 | 2011-02-16 | 삼성전자주식회사 | 프리로드 정보가 기록된 정보저장매체, 그 재생장치 및재생방법 |
TW200518070A (en) | 2003-10-10 | 2005-06-01 | Matsushita Electric Ind Co Ltd | Recording medium, reproduction device, program, and reproduction method |
JP4117019B2 (ja) | 2003-10-10 | 2008-07-09 | 松下電器産業株式会社 | 記録媒体、再生装置、記録方法、再生方法 |
JP4091105B2 (ja) | 2003-10-10 | 2008-05-28 | 松下電器産業株式会社 | 記録媒体、再生装置、記録方法、再生方法 |
JP4091104B2 (ja) | 2003-10-10 | 2008-05-28 | 松下電器産業株式会社 | 記録媒体、再生装置、記録方法、再生方法 |
US7467197B2 (en) * | 2005-01-20 | 2008-12-16 | International Business Machines Corporation | Workflow anywhere: invocation of workflows from a remote device |
JP2007265851A (ja) | 2006-03-29 | 2007-10-11 | Molex Inc | ケーブル用コネクタ |
JP2007265850A (ja) | 2006-03-29 | 2007-10-11 | Konica Minolta Holdings Inc | 有機エレクトロルミネッセンス素子の製造方法及び製造装置 |
JP2007265852A (ja) | 2006-03-29 | 2007-10-11 | Matsushita Electric Ind Co Ltd | 複合集電体およびその製造方法 |
-
2004
- 2004-10-08 TW TW093130684A patent/TW200518070A/zh unknown
- 2004-10-12 EP EP08155287A patent/EP1944771A3/en not_active Ceased
- 2004-10-12 US US10/572,980 patent/US7715696B2/en active Active
- 2004-10-12 EP EP04773786A patent/EP1675118A4/en not_active Withdrawn
- 2004-10-12 EP EP10183667.4A patent/EP2267711A3/en not_active Withdrawn
- 2004-10-12 JP JP2005514677A patent/JP4117006B2/ja active Active
- 2004-10-12 JP JP2005514681A patent/JP4182110B2/ja not_active Expired - Fee Related
- 2004-10-12 CN CN2010101438960A patent/CN101840718B/zh not_active Expired - Fee Related
- 2004-10-12 KR KR1020067007251A patent/KR100937790B1/ko not_active IP Right Cessation
- 2004-10-12 US US10/573,137 patent/US7702222B2/en active Active
- 2004-10-12 WO PCT/JP2004/015333 patent/WO2005036545A1/ja active Application Filing
- 2004-10-12 WO PCT/JP2004/015330 patent/WO2005036554A1/ja active Application Filing
- 2004-10-12 WO PCT/JP2004/015335 patent/WO2005036546A1/ja active Application Filing
- 2004-10-12 KR KR1020087009003A patent/KR100937791B1/ko active IP Right Grant
- 2004-10-12 WO PCT/JP2004/015339 patent/WO2005036555A1/ja active Application Filing
- 2004-10-12 KR KR1020067007234A patent/KR101051843B1/ko active IP Right Grant
- 2004-10-12 US US10/573,173 patent/US7515812B2/en active Active
- 2004-10-12 EP EP04773787A patent/EP1675119A4/en not_active Withdrawn
- 2004-10-12 KR KR1020067007239A patent/KR101051846B1/ko active IP Right Grant
- 2004-10-12 KR KR1020087009008A patent/KR100937792B1/ko active IP Right Grant
- 2004-10-12 JP JP2005514678A patent/JP4091078B2/ja not_active Expired - Fee Related
- 2004-10-12 JP JP2005514680A patent/JP4262250B2/ja active Active
- 2004-10-12 JP JP2005514682A patent/JP3825463B2/ja not_active Expired - Fee Related
- 2004-10-12 EP EP10170131A patent/EP2239737A3/en not_active Withdrawn
- 2004-10-12 KR KR1020097016043A patent/KR101059290B1/ko not_active IP Right Cessation
- 2004-10-12 CN CN2009102115066A patent/CN101702320B/zh not_active Expired - Fee Related
- 2004-10-12 EP EP04773784A patent/EP1675117A4/en not_active Withdrawn
- 2004-10-12 EP EP04773789A patent/EP1677302A4/en not_active Ceased
- 2004-10-12 US US10/572,873 patent/US8131130B2/en not_active Expired - Fee Related
- 2004-10-12 WO PCT/JP2004/015337 patent/WO2005036547A1/ja active Application Filing
- 2004-10-12 US US10/572,983 patent/US8437625B2/en not_active Expired - Fee Related
- 2004-10-12 EP EP04773781A patent/EP1672637A4/en not_active Ceased
- 2004-10-12 KR KR1020067007232A patent/KR101059343B1/ko not_active IP Right Cessation
- 2004-10-12 EP EP08155288A patent/EP1944772A3/en not_active Withdrawn
-
2008
- 2008-04-28 US US12/110,473 patent/US7623769B2/en active Active
- 2008-04-28 US US12/110,452 patent/US7630615B2/en not_active Expired - Fee Related
- 2008-05-29 JP JP2008140512A patent/JP4262296B2/ja not_active Expired - Fee Related
-
2009
- 2009-02-25 US US12/393,001 patent/US8107788B2/en active Active
-
2010
- 2010-04-09 US US12/757,136 patent/US8509596B2/en not_active Expired - Fee Related
- 2010-06-10 US US12/797,804 patent/US8406604B2/en not_active Expired - Fee Related
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH064166A (ja) * | 1992-06-24 | 1994-01-14 | Okayama Nippon Denki Software Kk | ジョブの有効期間設定装置 |
JPH06230946A (ja) * | 1993-02-07 | 1994-08-19 | Fuji Xerox Co Ltd | 自動プログラム開始装置 |
JPH1063362A (ja) * | 1996-08-16 | 1998-03-06 | Nec Corp | レジューム要因別に複数のプログラム状態を保持可能なサスペンドレジューム方法 |
JP2001238161A (ja) * | 2000-02-25 | 2001-08-31 | Sony Corp | 情報付加装置、情報付加方法および記録媒体 |
JP2002057990A (ja) * | 2000-08-09 | 2002-02-22 | Nec Corp | 映像再生システム及びそれに用いるデータ同期方式 |
JP2002369154A (ja) * | 2001-04-02 | 2002-12-20 | Matsushita Electric Ind Co Ltd | ディジタル映像コンテンツの映像再生装置、映像再生方法、映像再生プログラム、パッケージメディア |
JP2003249057A (ja) * | 2002-02-26 | 2003-09-05 | Toshiba Corp | デジタル情報媒体を用いるエンハンスド・ナビゲーション・システム |
JP2004206863A (ja) * | 2002-12-09 | 2004-07-22 | Toshiba Corp | 情報再生装置及び情報再生方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1677302A4 * |
Cited By (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8036513B2 (en) * | 2004-07-22 | 2011-10-11 | Panasonic Corporation | Playback apparatus and playback method |
EP2214171A1 (en) | 2004-07-22 | 2010-08-04 | Panasonic Corporation | Playback apparatus and playback method |
EP2216783A1 (en) | 2004-07-22 | 2010-08-11 | Panasonic Corporation | Playback apparatus and playback method |
US8347099B2 (en) | 2004-07-22 | 2013-01-01 | Panasonic Corporation | Playback apparatus and playback method |
EP2180477A1 (en) | 2004-07-22 | 2010-04-28 | Panasonic Corporation | Playback apparatus and playback method |
EP2216782A1 (en) | 2004-07-22 | 2010-08-11 | Panasonic Corporation | Playback apparatus and playback method |
EP2214169A1 (en) | 2004-07-22 | 2010-08-04 | Panasonic Corporation | Playback apparatus and playback method |
EP2216781A1 (en) | 2004-07-22 | 2010-08-11 | Panasonic Corporation | Playback apparatus |
EP2214170A1 (en) | 2004-07-22 | 2010-08-04 | Panasonic Corporation | Playback apparatus and playback method |
EP2214172A1 (en) | 2004-07-22 | 2010-08-04 | Panasonic Corporation | Playback apparatus and playback method |
US8805162B2 (en) * | 2004-07-30 | 2014-08-12 | Samsung Electronics Co., Ltd. | Storage medium including AV data and application program, and apparatus and method using the same |
US20090269030A1 (en) * | 2004-07-30 | 2009-10-29 | Samsung Electronics Co., | Storage medium including av data and application program, and apparatus and method using the same |
US8125859B2 (en) | 2004-12-06 | 2012-02-28 | Koninklijke Philips Electronics N.V. | Method and device for extending interactivity to multiple storage media |
WO2006061743A3 (en) * | 2004-12-06 | 2008-10-16 | Koninkl Philips Electronics Nv | Method, device, and recording medium for extending interactivity to multiple storage media |
EP2387037A1 (en) | 2005-01-28 | 2011-11-16 | Panasonic Corporation | Reproduction device for mixing a primary audio stream with a secondary audio stream |
US9137507B2 (en) | 2005-02-03 | 2015-09-15 | Thomson Licensing | Method and apparatus for executing software applications |
US9509969B2 (en) | 2005-02-23 | 2016-11-29 | Thomson Licensing | Method and apparatus for executing software applications |
US9204117B2 (en) | 2005-02-23 | 2015-12-01 | Thomson Licensing | Method and apparatus for executing software applications |
JP2011159314A (ja) | 2005-02-23 | 2011-08-18 | Thomson Licensing | ソフトウエア・アプリケーションを実行するための方法および装置 |
JP2008532197A (ja) * | 2005-02-28 | 2008-08-14 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | データ再生のためのフォールバックメカニズム |
JP2013175274A (ja) * | 2005-02-28 | 2013-09-05 | Koninklijke Philips Nv | データ再生のためのフォールバックメカニズム |
US8787131B2 (en) | 2005-02-28 | 2014-07-22 | Koninklijke Philips N.V. | Fallback mechanism for data reproduction |
WO2009128246A1 (ja) | 2008-04-16 | 2009-10-22 | パナソニック株式会社 | 記録媒体、記録装置、記録方法、及び再生装置 |
US8165458B2 (en) | 2008-11-06 | 2012-04-24 | Panasonic Corporation | Playback device, playback method, playback program, and integrated circuit |
JP5368470B2 (ja) * | 2008-11-06 | 2013-12-18 | パナソニック株式会社 | 再生装置、再生方法、再生プログラム、及び集積回路 |
WO2010052857A1 (ja) * | 2008-11-06 | 2010-05-14 | パナソニック株式会社 | 再生装置、再生方法、再生プログラム、及び集積回路 |
JP7119858B2 (ja) | 2018-09-28 | 2022-08-17 | ブラザー工業株式会社 | 工具寿命管理装置、工作機械、表示処理方法及びコンピュータプログラム |
JP2020055054A (ja) * | 2018-09-28 | 2020-04-09 | ブラザー工業株式会社 | 工具寿命管理装置、工作機械、表示処理方法及びコンピュータプログラム |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4182110B2 (ja) | 再生装置、プログラム、再生方法。 | |
KR101076198B1 (ko) | 기록매체, 재생장치, 기록방법, 재생방법 | |
JP4012563B2 (ja) | 記録媒体、再生装置、プログラム、再生方法。 | |
JP4117019B2 (ja) | 記録媒体、再生装置、記録方法、再生方法 | |
JP4091105B2 (ja) | 記録媒体、再生装置、記録方法、再生方法 | |
JP4091104B2 (ja) | 記録媒体、再生装置、記録方法、再生方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200480029695.0 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2005514682 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067007232 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004773789 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006282612 Country of ref document: US Ref document number: 10573173 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2004773789 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 10573173 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067007232 Country of ref document: KR |