WO2005036545A1 - 再生装置、プログラム、再生方法 - Google Patents
再生装置、プログラム、再生方法 Download PDFInfo
- Publication number
- WO2005036545A1 WO2005036545A1 PCT/JP2004/015333 JP2004015333W WO2005036545A1 WO 2005036545 A1 WO2005036545 A1 WO 2005036545A1 JP 2004015333 W JP2004015333 W JP 2004015333W WO 2005036545 A1 WO2005036545 A1 WO 2005036545A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- title
- read
- playback
- cache
- 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
- the present invention is an invention belonging to the technical field of reproduction control technology that simultaneously executes reproduction of a digitized movie work and execution of an application. It is deeply concerned with applied technology when applied to consumer playback devices and programs. Background art
- the life cycle of an application is the period from the start of the application service to the end of the service. If such a period is set in a small unit like a chapter, services by various applications can be executed alternately. However, if the live range of the application is defined in detail, the number of times the application is read from the recording medium increases. On the other hand, optical disc media for distributing movie works, such as BD-ROM and DVD, generally have a low reading speed. If the number of readings at such a slow speed increases, the reading of the video stream that constitutes the main part of the movie work is affected, and the movie playback tends to be interrupted. Although various services will be realized, simultaneous execution that hinders video playback will greatly discourage users and will be shunned by movie producers. Disclosure of the invention
- An object of the present invention is to provide a playback apparatus that can determine a live range of an application in small units.
- the above object has a module for executing an application, a playback control engine unit for playing back a digital stream belonging to one title, and a module manager for controlling branching between a plurality of titles, wherein the title is a tape.
- the table includes, for each title, an application whose life cycle is the title, and the module includes a virtual machine unit, a cache, and an application manager that loads the application into the cache.
- the section manager is achieved by a reproducing apparatus characterized in that, if there is a branch between titles, an application having the title as a live section is read into a cache.
- the application Since the application is loaded into the cache in units of titles and the process of deleting the application from the cache is performed, the application can be read out to the virtual machine at any time in the title. Since the application can be read to the virtual machine at any time, the number of times that the application is read from the recording medium can be reduced even if the life span of the application is determined in small units such as chapters. In addition, reading from the optical disk to the cache is performed at the time of a title branch, which does not require seamless playback guarantee. I can put it.
- the application manager reads the application whose read priority is set to Mandatory into the cache and stores the key after reading. It is desirable that the playback device be configured to read into the cache an application for which the read priority is optionally set according to the cache free space. Either the application corresponding to the memory size, which is the minimum standard, or the application corresponding to the operating environment with a larger memory size, It can be loaded into the memory of the playback device according to the memory size of the device and the read priority of each application. With such a road, it is possible to provide the soil that can guarantee the operation of the minimum standard while at the same time exerting the authoring staff's willingness to produce.
- the plurality of applications are given different read priorities and the same identifier, and the application manager assigns the same identifier based on the size of the cache and the read priority assigned to each application.
- One of the multiple applications may be exclusively loaded into the cache. ⁇
- 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 Clip_Information-file-names.
- FIG. 5 is a diagram showing a chapter definition by PLmark.
- FIG. 6 is a diagram showing a playback section definition on the SubPlayltem time axis and synchronization designation.
- FIG. 7A shows the internal structure of a Movie object.
- FIG. 7B shows the internal structure of the BD-J object.
- FIG. 7 (c) is a diagram showing the internal configuration of the Java application.
- FIG. 8 (a) is a diagram showing programs and data stored in a Java archive file.
- FIG. 8B shows an example of an xlet program.
- Figure 9 (a) shows a series of titles, including the top menu, title # l, and title # 2.
- FIG. 9 (a) shows a series of titles, including the top menu, title # l, and title # 2.
- FIG. 9 (b) is a diagram showing a time axis obtained by adding the time axes of PlayList # 1 and PlayList # 2.
- FIG. 10 is a diagram showing a disc content including three titles, a main title, an online shopping title, and a 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 ablation 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 illustrating 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 possible modes (Persistent, AutoRun, Suspend) of the startup attribute and three modes of the application state in the immediately preceding title (non-starting, running, Suspend).
- FIG. 16 is a diagram showing the internal configuration of the playback device according to the present invention.
- FIG. 17 (a) 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. 18 is a diagram in which a portion composed of software and hardware stored in the ROM 24 is replaced with a layer configuration.
- FIG. 19 is a diagram schematically illustrating the processing performed 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. is there.
- 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 that defines a live range on the 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 26 (b) shows the title time axis determined from the life span of the main application.
- Figure 26 (c) is a diagram showing the title time axis determined from the life span 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 realizing a menu hierarchy.
- FIG. 29 is a diagram schematically illustrating an Index Table and a branch from the Index Table to each Movie object.
- FIG. 30 (a) shows the branches when the Index Table is described as shown in FIG. 29 (b).
- FIG. 30 (b) is a diagram showing a branch when a non-AV title is forcibly terminated.
- FIG. 31 is a flowchart showing the processing procedure of the module manager 34.
- Figure 32 shows the application manager 36 killing the application. It is a figure showing an example of operation of end.
- FIG. 33 is a flowchart showing a PL playback procedure by the 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 a processing procedure when the SkipBack, SkipNext API is 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. 39 is a diagram illustrating an example of the data management table.
- FIG. 40 is a diagram showing an execution model assumed by the BD-J object.
- FIG. 41 (a) is a diagram showing a live range indicating the existence of a Java archive file in the local memory 29.
- FIG. 41 (b) is a diagram showing a data management table described for specifying the Java archive file live range in FIG. 41 (a).
- Figure 42 is a diagram showing embedding of a Java archive file by carouseling.
- FIG. 43 (a) is a diagram showing AVClip embedding by in-leaving.
- 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 local memory 29 due to the allocation of the data management template 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 pre-control by the application manager 36.
- FIG. 47 (a) is a diagram showing an example of a data processing table defining a plurality of applications having the same applicationID but different read priorities.
- FIG. 47 (b) is a diagram showing the transition of the storage content of the oral memory 29 due to the assignment of the data management table of FIG.
- 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 local memory 29 in a playback device having a small memory scale.
- FIG. 48 (c) is a diagram showing the transition of the storage contents of the local memory 29 in a playback device having a large 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. 51 is a diagram schematically showing how an application is read by the Java virtual machine 38.
- FIG. 52A shows 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 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.
- 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. 6 is a diagram illustrating an ittle time axis.
- 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 activation of the main application has failed.
- FIG. 54 is a flowchart showing a processing procedure of the application manager 36 according to the seventh embodiment.
- Figures 56 (a) and 56 (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. 58 (a) and 58 (b) 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 assigned.
- 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 a partition of the allocation unit of the application management table. BEST MODE FOR CARRYING OUT THE INVENTION
- 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 controller 400.
- the BD-ROM 100 contains a playback device 200, a remote control 300, and a TV 400 It is used for supplying movie works to the home theater system formed by.
- the disc content supplied to the home theater system by the BD-ROM is composed of multiple titles that can branch off from each other. Each evening consists of one or more playlists and a dynamic control procedure using these playlists. .
- a playlist is an access unit on a BD-ROM that includes one or more digital streams and a playback path in the digital streams, and has a concept of "time axis".
- the title combines the concept of a timeline specific to digital streams with the characteristics of a computer program, because it includes the above play list and dynamic control procedures.
- FIG. 2 is a diagram showing a file 'directory structure in a BD-ROM.
- the BD-ROM has a BDMV directory below the Root directory.
- the BDMV directory contains files with the extension bdmv.
- STREAM directory There are four subdirectories called the STREAM directory and the BDAR directory.
- the PLAYLIST directory contains files with the extension mpls.
- the STREAM directory contains files with the extension m2ts.
- AVClip (O0001.m2ts, 00002.m2ts, 00003.m2ts) stores an AVClip.
- AVClip has types such as MainCLip and SubClip.
- MainClip is a digital stream obtained by multiplexing a plurality of elementary streams such as a video stream, an audio stream, a presentation graphics stream, and an interactive graphics stream.
- SubClip is a digital stream that corresponds to only one elementary stream, such as an audio stream, a graphics stream, and a text subtitle 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 the AVClip, the frame rate, the bit rate, the resolution, and the like, and the EP-map indicating the start position.
- the playlist information is information that defines a playlist with reference to the AVClip.
- the playlist is composed of MainPath information, PLMark information, and SubPath information.
- MainPath information is composed of multiple Playltem information.
- Playltem is a playback section defined by specifying In-Time and Out-Time on one or more AVClip time axes.
- a playlist (PL) consisting of multiple playback sections is defined.
- FIG. 3 is a diagram showing the relationship between AVClip and PL. The first level shows the time axis of AVClip, and the second level shows the time axis of PL.
- the PL information includes three pieces of Playltem information, Playltem #l, # 2, and # 3, and three playback sections are defined by the In_time and Out_time of these Playltems # 1, # 2, and # 3. .
- a time axis different from the AVClip time axis is defined. This is the PL shown in the second row It is a time axis.
- the definition of the Playltem information enables the definition of a time axis different from that of the AVClip.
- AVClip is basically one, but it is also possible to specify multiple AVClips at once. This batch, designation,
- FIG. 11 is a diagram illustrating batch designation performed by Clip_Information_file_name.
- the first to fourth rows show four AVClip time axes (time axes of AVClips # 1, # 2, # 3, and # 4), and the fifth row shows PL time. Show the axis.
- These four time axes are specified by four Clip-Information-file-names in Playltem information.
- four playback sections that can be played back alternatively are defined by the In-time and Out_time of the Playltem.
- a section composed of switchable multiple andal videos is defined on the PL time axis.
- 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.
- Arrows pkl, 2 in the figure indicate the Playltem designation (ref_to—Playltem—Id) in PLmark and the one-time designation (mark_time—stamp).
- three chapters (Chapter #l, # 2, # 3) are defined on the PL time axis.
- SubPath information is composed of a plurality of SubPlayltem information.
- the SubPlayltem information defines a playback section by specifying In_Time and Out_Time on the time axis of the SubClip.
- the SubPlayltem information can be specified to synchronize the playback section on the SubClip time axis with the PL time axis.
- the PL time axis and the SubPlayltem information time axis can proceed in synchronization. become.
- FIG. 6 is a diagram showing the definition of a playback section on the SubPlayltem time axis and the designation of synchronization. In the figure, the first row shows the PL time axis, and the second row shows the SubPlayltem time axis.
- SubPlayltem.IN-time indicates the start point of the playback section
- SubPlayltem.Out-time indicates the end point of the playback section. This shows that the playback section is also defined on the SubClip time axis.
- Sync—Playltem—Id is Indicates the synchronization designation for Playltem, indicated by arrow Sn2
- sync—start—PTS—of—Playltem indicates a point in time on Playltem on the PL time axis.
- a dynamic scenario is scenario data that dynamically defines AVClip playback control.
- “Dynamic” means that the contents of playback control change due to a state change in the playback device or a key event from the user.
- the BD-ROM assumes two modes as the operating environment for this playback control. The first is an operating environment that is very similar to the operating environment of DVD playback devices, and is a command-based execution environment. The second is the operating environment of the Java virtual machine. The first of these two operating environments is called HDMV mode. The second is called BD-J mode. Since there are these two operating environments, the dynamic scenario is described assuming one of these operating environments.
- a dynamic scenario assuming the HDMV mode is called a Movie object and is defined by management information.
- a dynamic scenario that assumes the BD-J mode is called a BD-J object.
- the Movie object is a component of the "Title"
- 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 information (resume—intention_flag) that indicates whether or not playback is intended to be resumed after MenuCall when a MenuCall is made on the PL time axis.
- the axis consists of information indicating whether MenuCall is masked (menu_call-mask) and information indicating whether title search is masked (title-search-flag).
- a Movie object can have both properties of "time axis" + "programmatic control", and various types of titles, such as those that execute the main part playback, can be described by this Movie object. become.
- 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 Movie objects are shown below. PlayPL command
- the first argument is the playlist number, which can specify the PL to be played.
- the second argument can specify the playback start position using 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 by the time information is called PlayPLatSpecified TimeO.
- the JMP command is a branch that discards the current dynamic scenario on the way (discard) and executes the branch destination dynamic scenario as an argument.
- the navigation command description for the Movie object is described on the DVD. It is very similar to the description method of navigation commands that can be used, so that the task of porting disc contents on a DVD to BD- ⁇ ⁇ can be performed efficiently.
- the Movie object there is a prior art described in the following International Publication. See this International Publication for details. International Publication WO 2004/074976 This concludes the description of the Movie object.
- the BD-J object will be described. - ⁇ BD-J object>
- FIG. 7B 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 Movie objects is that BD-J objects do not directly describe commands.
- the control procedure in the Movie object was directly described by the navigation command.
- the Java application whose lifetime is the title is defined in the application management table.
- the control procedure is indirectly defined by the control procedure, and the control procedure can be efficiently shared by 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 that are spoken in the virtual machine 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 loaded in the work memory.
- the above is the configuration of the application.
- the real thing of this application is the Java archive file stored in the BDAR directory under the BDMV directory.
- Java archive files (00001.jar, 00002.jar) are archive files that store programs and data that make up Java applications.
- FIG. 8 (a) 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;
- the directory structure shown in the frame consists of a root directory, a java directory, and an image directory. menu.jpg is placed.
- a java archive file can be obtained by putting them together in a java archiver.
- Such data is expanded when it is read from the BD-ROM into 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 file indicates the application ID (applicationlD).
- 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. 8 (b) is a diagram showing an example of an xlet program.
- JMF A "BD7 / 00001.mpls"; is a Java temporary It is a method for commanding a virtual machine.
- A.play is a method for instructing a JMF player instance to play. Such JMF player instance generation is 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 contents with 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 and the APK Appliation Interface supplied by the BD-ROM playback device In addition to the JumpTitle command, processing specific to the BD-ROM playback device can be described in the xlet program by calling the function API.
- 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 branch from the title to the title in BD-J mode is specified by the JumpTitleAPI call. Since the Jump itleAPI call determines the end point of the title, so to speak, such a JMF player instance and an application having the JumpTitleAPI call will govern the start and end of the title in BD-J mode. Such an application is referred to as a main playback application.
- the above is the description of the dynamic scenario in the BD-J mode.
- the dynamic scenario in the BD-J mode defines a title that combines PL playback and programmatic control.
- the programs and data constituting the application are collected in a Java archive file, but may be an LZH file or a zip file.
- the timeline defined by the title is called the "title timeline”.
- the title time axis is composed of a PL whose playback is ordered by a Movie object or BD-J object.
- An example here is the title shown in Fig. 9 (a).
- This title is a series of titles such as “Top menu 1” title # l ⁇ title # 2 ⁇ Top menu, Top menu 1 ”title # 3 ⁇ Top menu.
- title # l is for PlayList # 1
- title # 2 is for PlayList # 3
- title # 4 is for PlayList # 4 as shown in Fig.
- PlayList Add the time axis of #l and PlayList # 2, and title # l will have a time axis.
- title # 2 has a time axis consisting of PlayList # 3 time axis
- title # 3 has a time axis consisting of PlavList # 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.
- the period (service period) during which the Java application can exist in the work memory of the virtual machine must be defined on such a title time axis.
- the service period of the Java application must be defined on a 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 evening 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.
- 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 ⁇ ⁇ ⁇ When operating on the axis, it is important to clearly define the "service start point 'end point'" where the application service starts from the time axis and where the application service ends on the time axis. become. In the present embodiment, the period from the start of the service by the application to the end of the service is defined as "survival of the application". Information for defining the survival of the application exists in the application management table in the BD-J object. The following describes the application management table in more detail.
- the application management table is information indicating applications that can survive on the work memory of the virtual machine in the title time axis of each title. Survival in the work memory refers to the state in which the xlet program that constitutes the application 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 “start attribute” of the application.
- FIG. 10 is a diagram showing disc contents including three titles: a main title, an online shopping title, and a game title. In the figure, the right side describes the IndexTable, and the left side describes three titles.
- FIG. 11 is a diagram showing an example of the reproduced images of the three titles shown in FIG. In the playback images of these three titles, the main title in Fig. 11 (a) and (b) and the online shopping title have images (cart crl) imitating a shopping cart. There is no cart video in the game title of (c).
- the application # 3 which is a cart program, is started in both title # l and title # 2.
- Such applications that start with multiple titles include the cart app described above, an agent app that imitates a mascot appearing in a movie, and a menu app that displays a menu in response to a menu call operation. is there.
- Fig. 12 (a) When the life span of each application is transformed 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, and the live range of each application is arranged in the vertical axis direction.
- application # l and application # 2 belong only to title # l, so their live range remains within title # l. Since application # 4 belongs to title # 2 only, these live ranges remain within title # 2. Since application # 5 belongs to title # 3 only, these live ranges remain in title # 3. Since application # 3 belongs to title # l and title # 2, their life span extends from title # l to title # 2.
- 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 startup attributes include "AutoRun”, which indicates automatic startup, "Persistent”, which indicates that it is not the target of automatic startup, but may be placed in the virtual machine's private memory, and is placed in the virtual machine's work memory. There is “Suspend” where CPU power cannot be allocated.
- AutoRun is a live range indicating that the application is read into the work memory and executed at the same time as the corresponding title branch.
- the management entity application manager
- the management entity determines the application that is alive in that branch destination title and whose startup attribute is set to AutoRun. Read into the work memory of the virtual machine and execute. This will automatically launch the application along with the title branch.
- Applications that set the startup attribute to AutoRun include applications that have a JMF player instance and a JumpTitle API call. Because, Such an application is an application that governs the title time axis, and unless such an application is automatically started, the concept of the title time axis becomes ambiguous.
- the start attribute “Persistent” is a continuation attribute, and indicates that the application state at the branch source title is to be continued. It is an attribute indicating that it can be loaded into the work memory. If the launch attribute is “Persistent”, the application to which this launch attribute is assigned is allowed to be called from other applications.
- the management entity application manager
- the management entity that performs application management determines whether or not a call is made from a running application, the application ID of the application is described in the application management table, and the startup attribute is “Persistent”. Is determined. If "Persistent”, load the application into work memory. On the other hand, if the applicationID 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 with this “Persistent”.
- “Persistent” is the default startup attribute given when the startup attribute is not explicitly specified, so if the startup attribute of a certain application is "11", the startup attribute of the application is activated. The attribute means that it is persistent.
- FIG. 13 is an example of setting the startup attributes for the three applications in FIG. Of the three applications shown in FIG. 12, application # 2 is assumed to be an application that is started only when an application is called from another application, as shown in FIG. 13 (b). The remaining application # l and application # 3 are assumed to be applications that are automatically started when title # l starts.
- the start attribute of each application in the application management table is "Application Auto" for application # l and applicauon # 3, and "Persistent" for application # 2. And set it.
- application # l and application # 3 are automatically loaded into the work memory and executed when branching to title # l.
- application # 2 is a persistent attribute, so the negative meaning is that application # 3 is an application that can be loaded on the work memory of the virtual machine. Therefore, application # 2 is loaded into the virtual machine's work memory and executed only after a call from application # l.
- 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.
- Suspend means that an application is placed in a state where resources are allocated but CPU power is not allocated. Such Suspend is useful for realizing a process of passing through a side path during the execution of a game title, for example.
- Figures 14 (a) and 14 (b) show examples where Suspend is significant. As shown in Figure 14 (b), there are three titles (titie # l, title # 2, title # 3), of which title # l and title # 3 execute the game app, but title # 2 is a side bus that implements video playback. In a side bus, it is necessary to realize video playback, which interrupts game execution. In the game application, scores in the middle are counted, so we want to keep the stored value of the resource 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.
- application # 2 in title # 2 has its resources allocated, so the stored values of the resources are maintained.
- application # 2 is not executed by the virtual machine. As a result, a process of executing a side path during the execution of the game title is realized.
- FIG. 15 is a diagram showing combinations that can be taken by three modes (Persistent, AutoRun, Suspend) that the startup attribute can take, and three modes of the application state in the immediately preceding title (non-started, running, Suspend). If the previous state is "not running” In this case, if the launch attribute is "AutoRun", the application will be launched at the branch target title.
- the application state will be Suspend. If the immediately preceding state is "Suspend”, Suspend will be maintained if the activation attribute of the branch destination title is "Suspend”. If "Persistent” / AutoRun ", the application will resume at the branch target title.
- the title time axis As the application progresses, it becomes possible to perform synchronous control by operating the Java application, and to send out various applications with video playback and program execution to the world. 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 reproducing apparatus 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 produced by mounting these parts on a cabinet and a board of the device.
- the system LSr 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, read buffer 2, demultiplexer 3, video decoder 4, video plane 5, P-Graphics decoder 9, Presentation Graphics plane 10, synthesizing unit 11, and font generator.
- I-Graphics decoder 13 Switch 14
- Interactive Graphics plane 15 Synthesizer 16 HDD 17, Lead buffer 18, Demultiplexer 19, Audio decoder 20, Scenario memory It consists of 21, CPU 22, key event processing section 23, instruction ROM 24, switch 25, CLUT section 26, GLUT section 27, PSR set 28, and local memory 29.
- the BD-ROM drive 1 performs loading / ejection of the BD-ROM and executes access to the BD-ROM.
- the read buffer 2 is a FIFO memory in which TS buckets read from the BD-ROM are stored in a first-in first-out manner.
- the demultiplexer (De-MUX) 3 extracts a TS bucket from the red buffer 2 and converts a TS packet constituting the TS packet into an ES packet.
- the PES packet with the PID set by the CPU 22 is transferred to one of the video decoder 4, audio decoder 20, P-Graphics decoder 9, and I-Graphics decoder 13. Output.
- the video decoder 4 decodes the plurality of PES buckets output from the demultiplexer 3 to obtain an uncompressed picture and writes the picture in the video plane 5. .
- 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 device, 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. By decoding the graphics stream, subtitles will appear on the screen.
- 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 1080, and each pixel of uncompressed graphics in the Presentation Graphics plane 10 is represented by an 8-bit index color.
- CLUT Color Lookup Table
- the combining unit 11 combines the uncompressed picture data (i) with the contents stored in the Presentation Graphics plane 10.
- the font generator 12 expands the text code included in the textST stream into a bitmap using the character font.
- 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 Graphics plane 1o.
- the switch 14 selectively writes a font sequence generated by the font generator 12 or graphics obtained by decoding by the P-Graphics decoder 9 to the Presentation Graphics plane 10. It is a switch.
- the synthesizing unit 16 synthesizes the contents stored in the Interactive Graphics plane 10 with the synthesized image (composite of the uncompressed picture data and the contents stored in the Presentation Graphics plane 7) output from the synthesizing unit 8. I do.
- the HDD 17 is a built-in medium for storing SubClip, Clip information, and playlist information downloaded via a network or the like.
- the playlist information in the HDD 17 is different in that it can be specified regardless of whether the clip information exists in the BD-ROM or the HDD 17.
- the playlist information on the HDD 17 does not need to specify the file on the BD-ROM with the full path. This is because the HDD 17 is integrated with the BD-ROM and recognized by the playback device as one virtual drive (called a virtual package). Therefore, the Clip_Information_file_name in the Playltem information and the Clip_Information_file_name in the SubPlayltem information specify the five-digit numerical value corresponding to the file body of the file storing the Clip information.
- AVClip on BD-ROM can be specified. Read the recorded contents of this HDD, and read the BD-ROM By dynamically combining this with the recorded contents of, various playback variations can be created.
- the read buffer 18 is a FIFO memory, and stores TS packets read from the HDD 17 in a first-in first-out manner.
- the demultiplexer (De-MUX) 19 takes out the TS packet from the read buffer 18 and converts the TS packet into a PES bucket. Then, of the PES packets obtained by the conversion, those having the desired streamPID are output to the font generator 12.
- the audio decoder 20 decodes the PES packet output from the demultiplexer 19 and outputs uncompressed audio data.
- the scenario memory 21 is a memory for storing the current PL information and the current Clip information.
- the current PL information is the information currently being processed from the multiple PL information recorded on the BD-ROM.
- the current Clip information refers to information currently being processed, such as multiple Clip information recorded on the BD-ROM.
- the CPU 22 executes software stored in the instruction ROM 24 to control the entire playback device.
- the key event processing section 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 command ROM 24 stores software for controlling the playback device.
- Switch 25 selectively inputs various data read from BD-ROM and HDD 17 to any of read buffer 2, read buffer 18, scenario memory 21 and local memory 29. It is a switch to do.
- the CLUT unit 26 converts the index colors in the uncompressed graphics stored in the video plane 5 into Y, Cr, Cb values.
- the CLUT unit 27 converts the index colors in the uncompressed graphics stored in the Interactive Graphics plane 15 into Y, Cr, Cb values.
- the ken 811 set 28 is a register built into the playback device, consisting of 64: Player Status Register (PSE) and 4096 General Purpose Register (GPE). Become. Of the Player Status Register settings (PSR), PSR4 to PSR8 are used to represent the current playback point.
- PSR Player Status Register settings
- PSR4 indicates the title to which the current playback point belongs by being set to a value from 1 to L00, and indicates that the current playback point is the top menu by being set to 0.
- PSR5 indicates the chapter number to which the current playback point belongs by being set to a value of 1 to 999, and indicates that the chapter number is invalid in the playback device by being set to OxFFFF.
- PSR6 when set to a value from 0 to 999, indicates the number of the PL (current PL) to which the current S raw point belongs.
- PSR7 when set to a value from 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 time point (power Rent. PTM (Presentation TiMe)) using a time accuracy of 45 KHz.
- the current playback point is specified.
- FIG. 17 is a diagram showing how the 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.
- a part of the file path in the BD-ROM is omitted and used as the file path. Therefore, by storing the file path in the header,
- the location 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), and e).
- Playback Control Engine ⁇ 2 which performs playback control based on playlist information and Clip information.
- the decryption of the Movie object 'HDMV module 33 which is the execution subject' and the d-2) the decryption of the BD-J object 'BD-J module 3 and 5 are on the same level.
- the BD-J module 35 is a so-called Java platform, which has a core configuration of a Java virtual machine 38 including a work memory 37, and has an application manager 36, an event listener manager 39, and a default operation manager. It consists of 40.
- the Presentation Engine 31 to Module Manager 34 will be described.
- FIG. 19 is a diagram schematically illustrating the processing by the Presentation Engine 31 to the module manager 34.
- 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). Off), Canceling Still function (still of £>, Fast forward with speed specification (Forward Play (speed)), Rewind with speed specification (Backward Play (speed)), Audio switching (Audio Change), These are functions such as subtitle change and angle change.
- the Presentation Engine 31 has a video decoder 4, a P-Graphics decoder 9, and a P-Graphics decoder 9, which decode the portion of the AVClip read on the read buffer 2 at the desired time. Controls I-Graphics decoder 13 and audio decoder 20. By decoding the part indicated by PSR8 (Power PTM) as a desired time, it is possible to reproduce an arbitrary point in the AVClip.
- PSR8 Power PTM
- the playback control engine (PCE) 32 executes various functions such as a playlist playback function (i) and a status 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, playback start and playback are performed according to the current PL information and Clip information.
- These functions (i) to (ii) are executed in response to a function call from the HDMV module 33 to the BD-J module 35. That is, the reproduction 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 show the Playback Control Engine 32 referring to the Clip information and the playlist information.
- the HDMV module 33 is the execution entity of the MOVIE mode, and when the module manager 34 notifies the movie object constituting the branch destination, the Movie object constituting the branch destination title is read out to the oral memory 29.
- 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 in Fig. 19 indicate the branch target Movie object from the module manager 34 (2), decode navigation commands described in the Movie object (3), and playback. Function call (4) to 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 uses the JumpTitle command in the HDMV mode.
- the module 33 is executed, or when the title jump API is called from the BD-J module 35, the title number of the jump destination is received, and the Movie object or the Movie object constituting the title is received.
- the BD-J object is notified to the HDMV module 33 or the BD-J module 35.
- Arrows marked with V0, V1, and V2 in the figure schematically show execution of the JimipTitle command (0), reference of IndexTable by module manager 3.4 (1), and notification of branch destination Movie object (2). I have.
- FIG. 20 is a diagram showing the application manager 36.
- the application manager 36 controls the startup of the application with reference to the application management table and controls when the title ends normally.
- Start control means that every time a BD-J object to be branched to is notified from the module manager 34, the BD-J object is read and the application management table in the BD-J object is referred to. Perform local memory 29 access. Then, the control is to read the xlet program, which constitutes the application whose live period is the current playback point, into the work memory.
- Reference numerals 1, 2, and 3 in FIG. 20 schematically show the notification of the branch destination BD-J object in the start control (1), the application management table reference (2), and the start instruction to the Java virtual machine 38. 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 at the time of normal end and control at the time of abnormal end.
- 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 entity (module manager 34).
- An arrow 6 schematically shows the notification of the module manager 34 in this end control.
- the applications that make up the title may remain running. Because quit the application This is because whether or not to do so is determined at the branch destination title.
- the application manager 36 reads the Java archive file from the BD-ROM to the local memory 29 (8).
- Reference numeral 8 schematically illustrates the reading from the oral memory 29.
- the work memory 37 is a heap area in which xlet programs constituting the application are arranged.
- the work memory 37 originally exists in the Java virtual machine 38, but in FIG. 21, the work memory 37 is described in the upper layer of the Java virtual machine 38 for convenience of drawing.
- the xlet program on the work memory 37 includes EventListner and a JMF player instance.
- the Java virtual machine 38 loads the xlet program constituting the application into the work memory 37, decodes the xlet program, and executes processing according to the decoding result.
- the xlet program includes a method for instructing the creation of a JMF player instance, and a method for instructing the execution of this JMF player instance, so the 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 is ordered, the Java virtual machine 38 obtains a JMF player instance associated with the YYYY.MPLS file on the BD-ROM.
- this JMF method is issued to the BD middle player, and replaced with a function call supported by the BD playback device. Then, the function call after the replacement is issued to the Playback Control Engine 32.
- Event Listner Manager 39 analyzes events (key events) generated by user operations and sorts the events. Solid arrows 1 and ⁇ > 2 in the figure schematically show the distribution by the Event Listner Manager 39.
- Key events such as START, STOP, SPEED, etc. registered in the Event Listner in the xlet program are related to the xlet program indirectly referenced by the BD-J object. Distribute vents. 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. If the key event is a key event that is not registered in Event Listner, this key event is allocated to Default Operation Manager 40. There are various key events that occur in the BD-ROM playback device, such as audio switching and angle switching, that are not registered in the Event Listner, and even if these key events occur, perform processing without omission. That's why.
- Event Listner unregistered events were sorted by Event Listner Manager 39 and Default Operation Manager 40, but Playback Control Engine 32 directly received Event Listner unregistered events and performed playback control. (04 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 application X) that satisfies the conditions of steps S2 to S5.
- Step S.2 is not activated at the branch source title, but survives at the branch destination title. Then, it is determined whether or not the application X whose startup attribute in the branch destination title is the AutoRxm attribute exists. If there is, the cache sense for the local memory 29 is performed. As a result of the cache sense, if the application X is on the local memory 29 (Yes in step S7), the application X is read from the local memory 29 to the park memory 37 (step S8). If it is not in the local memory 29, the application x is read from the BD-ROM into 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 not alive in the branch destination title. If there is, the application X is deleted from the work memory 37 and the process is terminated (step S10).
- -Step S4 is to determine whether or not there is an application of branch source SuspencU branch destination AutoRun or Persistent. If it exists, Resume Application X (step S11).
- step S5 it is determined whether or not the application of the branch destination Suspend is running at the branch source title. If it exists, the application X is suspended (step S12).
- FIG. 23 is a flowchart illustrating a processing procedure of the application termination processing.
- This figure shows a loop process in which the processes from step S16 to step S20 are repeated for each of a plurality of applications to be completed (step S15).
- the application manager 36 issues a terminate event for terminating the running application (step S16), sets a timer (step S17), and executes steps S18 to S18. Move to a loop process consisting of 20.
- the Event Listner receives this terminate event, the corresponding xlet program starts the termination process.
- the xlet program is released from the work memory 37, and ends.
- step S18 is for judging whether or not the issuance application has been completed. If it has been completed, the processing for this application ends.
- 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 the process of terminating the application.
- the first tier in this figure shows the application manager 36, and the second tier shows three applications.
- the application on the left 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 the termination process.
- the application on the right indicates 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 row shows the state after the state transition when the termination process is successful. This application is terminated by its own termination process. If there are applications such as these xlet programs which do not end within a predetermined period, the application 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 in the branch source title and that is not alive in the branch destination title is automatically terminated. Even if progressing, resources in the playback device No application is launched beyond the limits of the application. Since the application operation before and after branching can be guaranteed, it is possible to distribute a lot of disk contents that execute the application while playing the digital stream. ,
- Fig. 25 (a) is a diagram showing an application management table that defines the live sections on the PL time axis.
- application ⁇ is specified as the live range from Chapter # 2 to Chapter # 3 of title # l, and the startup attribute AutoRxm is specified. Therefore, application # 2 is started at the start of Chapter # 2 and ends at the end of Chapter # 3, as shown in Figure 25 (b).
- application # 3 the title # l from Chaptei # 4 to Chapter # 6 are specified as live areas. Therefore, application # 3 is started at the starting point of Chapter # 4 and ends at the ending point of Chapter # 6, as shown in Fig.25 (b), as shown in Fig.25 (b).
- the application manager 36 Since the application manager 36 according to the present embodiment performs processing based on the application management table described in this way, every time it reaches the chapter start point specified by PLmark, the live range starts from the chapter start point. It is determined whether or not the application exists, and if so, the application is loaded into the work memory 37.
- the application is started at the moment when normal playback by the Playback Control Engine 32 is started after entering the title.
- the PL playback includes normal playback and trick playback.
- Trick playback includes fast forward, rewind, SkipNext, and SkipBack.
- the application is not started but the application is started only after the normal playback is started.
- the moment of the normal playback start as a reference, the application startup will not be unnecessarily repeated even if there is a crossing before and after the live range as described above. It should be noted that the process of setting the instant of the normal reproduction to be the starting reference of the application may be executed even when the live range is the title.
- the live range of the application can be defined in units of chapters, which is smaller than the PL, so that precise application control can be realized.
- each application is assigned a priority. This priority takes a value from 0 to 255. If there is contention among resources between applications, which application is forcibly terminated, and which application deprives resources When the application manager 36 performs such a process, it becomes a judgment material.
- the priority of application # l is 255
- the priority of application # 2 is 128, so in the event of a conflict between application # l and application # 2, the application manager 36 Process to forcibly terminate application # 2 with low
- the disc content provided by the BD-ROM is composed of multiple It consists of titles.
- 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.
- this non-AV title will be described.
- Figure 26 (a) shows the title time axis determined from the PL time axis.
- 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 that serves as this criterion, the title time axis should be defined as shown in Figures 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 whose startup attribute is set to AutoRun in the title and is automatically started at the start of the title.
- this is a launcher application.
- a launcher application is an application program that launches another application.
- the idea in Fig. 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 title time axis determined from the life span of multiple applications. One application is started at the beginning of the title, but there are cases where this application calls another application, and this application calls another application.
- FIG. 27 is a flowchart showing a processing procedure of the application manager 36 during title playback. In this flowchart, during title playback, step s 2 1
- Step S23 is repeated to form a loop structure.
- Step S21 is a determination as to whether or not the title jump API has been called. If called, a branch to the jump destination title is requested to the module manager 34 (step S27).
- Step S22 is to determine whether or not there is a main application that is responsible for calling the application in the title, and if so, confirms whether or not it has been started (step S22). Five). If not started, it is interpreted as "end of title" and module manager 34 is notified of the end (step S26).
- Step S23 is a step executed when there is no main application ( ⁇ in step S22), and it is determined whether or not any application has not been started. If so, it also interprets it as "end of title” and notifies module manager 34 of the end (step S26).
- FIG. 28 (a) is a diagram showing a menu hierarchy realized by a BD-ROM.
- the menu hierarchy in this figure has a structure in which TpMenu is placed at the top level, and from this TopMenu, lower-level TitleMenu, SubTitleMenu, and AudioMenu can be selected. Arrows swl, 2, and 3 in the figure schematically show menu switching by button selection.
- TopMenu is for audio selection, subtitle selection, title selection It is a menu with buttons (buttons snl, sn2, sn3 in the figure) to accept which one to perform.
- the TitleMenu is a menu with buttons that accept the selection of a movie, such as selecting the movie version of the movie (title), the director's cut version, or the game version.
- 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 the MOVIE object for operating a menu having such a hierarchy.
- MovieObject.bdmv stores FirstPlay OBJ, TopMenu OBJ, AudioMenu OBJ, and SubTitleMenu OBJ.
- the FirstPlay object (FirstPlay OBJ) is a dynamic scenario that is automatically executed when a BD-ROM is dictated to a playback device.
- TopMenu object (TopMenu OBJ) is a dynamic scenario that controls the behavior of TopMenu. It is this TopMenu object that is invoked when the user requests a menu call. TopMenu objects include those that change the state of buttons in the TopMenu in response to user operations, and branch commands that branch in response to button operations. This branching command realizes a user switching from TopMenu to TitleMenu, TopMenu to SubTitleMenu, TopMenu to AudioMenu.
- the AudioMenu object (AudioMenu OBJ) is a dynamic scenario that controls the behavior of the AudioMenu.
- the SubTitleMenu object (SubTitleMenu OBJ) is a dynamic scenario that controls the behavior of the SubTitleMenu.
- a command that changes the state of the button in the SubTitleMenu in response to an operation from the user, and a subtitle setting in response to a finalization operation on the button Contains the command to update the PSR for
- the TitleMenu object (TitleMemi OBJ) is a dynamic scenario that controls the behavior of the TitleMenu, and includes a command that changes the state of a button in the TitleMenu and a branch command that branches in response to a decision operation on the button.
- Figure 29 is a diagram schematically showing the Index Table and the branch from the Index Table to each Movie object.
- the left side shows the internal structure of the Index Table.
- the Index Table in the present embodiment includes-FirstPLaylNDEX, IpMenuINDEX, Audio MenuINDEX, Subtitle Me dish INDEX, title MenuINDEX, title # l to #mINDEX, title # m + l to #nINDEX, and title # 0INDEX.
- Arrows bcl, 2 in the figure schematically show the branch from Index Table to FirstPlayOBJ and the branch from FirstPlayOBJ to TopMenu
- arrows bc3, 4, and 5 show the branches from TopMenu to TitleMenu, SubTitleMenu, and AudioMenu. This is schematically shown.
- Arrows bc6, 7, and 8 schematically show branches from TitleMenu to Movie objects.
- FirstPLaylNDEX, TopMenuINDEX, Audio MenuINDEX, Subtitle MenuINDEX, title MenuINDEX are indexes for FirstPLayOBJ, TopMenuOBJ, Audio MenuOBJ, Subtitle MenuOBJ, title MenuOBJ, respectively, and these identifiers are described.
- title # l to #mINDEX are the indexes of the titles entered from the 1st to the mth in the BD-ROM, and the identifiers of the MOVIE objects to be branched to when the title numbers from 1 to m are selected. ID) is described.
- title # m + l ⁇ # nINDEX is an index for the titie that is the nth entry from the m + 1 on the BD-ROM.When the title number from m + 1 to n is selected, The identifier (ID) of the new BD-J object is described.
- title # 0INDEX is an INDEX that specifies the Movie object or BD-J object to be branched to when the BD-J object is forcibly terminated. Book In the embodiment, the identifier for TopMemiOBJ is stored in title # 0INDEX.
- FIG. 30 (a) shows the 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 to title # m as the branch destination, the identifiers of the Movie objects #l to #m are obtained from title # llndex to title # mlndex. Taken out. When executing the branch command with the label title # m + l to title # n as a branch, the identifier of the BD-J object # m + l to #n is extracted from title # m + llndex to title # nlndex.
- BD-J objects # m + l to #n are five-digit numbers that represent file names, "00001.BD-J, 00002.BD-J, 00003.BD-J" It will be fetched and the dynamic scenario with that file name will be read into memory and executed. This is the branching process using the Index Table.
- FIG. 30 (b) is a diagram showing a branch at the time of forced termination when executing a BD-J object.
- the identifier is extracted from title # 01ndex, and the playback device executes the dynamic scenario with that identifier. If this identifier is the identifier of the top menu title, the top menu OBJ will be automatically selected when the application is forcibly terminated.
- the above is an improvement on the recording medium in the present embodiment.
- improvements to the playback device according to the present embodiment will be described.
- the module manager 34 in the playback device performs processing according to the processing procedure shown in FIG.
- FIG. 31 is a flowchart showing the processing procedure of the module manager 34. This flowchart constitutes a loop process consisting of step S31 and step S32, and when either step S31 or step S32 becomes Yes, the corresponding process is executed. is there.
- Step S31 is to determine whether or not the title jump API has been called. If there is a call to the title jump API, a title number] ′ that is a branch destination label is obtained (step S33), and IDj is extracted from the index of the title number j in the Index Table (step S3). 4), IDj Movie Objek Or the BD-J object is executed by the HDMV module 33 or the BD-J module 35 (step S35).
- Step S32 is for determining whether or not the end of the title is notified from the application manager 36. If notified (Yes in step S32), the top menu constituting the top menu title The OBJ is executed by the HDMV module 33 or the module manager 34 (step S36).
- the title to be played here is a non-AV title that includes a game application that stacks 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 in the life cycle of this game app, as shown in the upper left of Fig. 32.
- 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 module manager 34 branches to the top menu title. Then, an image as shown on the upper right side of FIG. 32 is displayed, and the operation waits for the user.
- it is possible to control to branch to the top menu title even at the end of a non-AV title that includes a program but does not include a digital stream. As a result, even if the application program terminates with an error, it is possible to avoid occurrence of blackout / hangup.
- BD-J mode it relates to the improvement of how to achieve synchronization with PL playback.
- the Java virtual machine 38 decodes the JMF player instance (A.play;) that instructs playback of the JMF player instance, the Java virtual machine 38 calls the PL playback API. And right after the call Access to the application.
- 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 process described above will continue during those 2 hours. The problem here is how long the Java virtual machine 38 returns a success response and how long the Playback Control Engine
- 3 2 is the gap with the time to actually finish 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, but since the actual processing by the Playback Control Engine 32 ends after 2 hours, However, if the time to return a success response to the application is used as a reference, the end of the process after 2 hours cannot be detected. When fast forward, rewind, and skip are performed in PL playback, the playback time of 2 hours fluctuates around 2 hours, and it becomes more difficult to detect the end of processing.
- Playback Control Engine 3 2 operate with the Abu 1] Ke one Chillon and stand-alone, the termination judgment as in the third embodiment, it is impossible to interpret the end of PL playback tie bets Le ends. Therefore, in this embodiment, whether or not the application is terminated, as long as the JMF player instance exists in the private memory 37, that is, the control right of the Presentation Engine 31 is controlled by the BD_J module 35. While waiting for a playback end event from Playback Control Engine 32. If there is a playback end event, it interprets that the title has ended, and notifies the module manager 34 to branch to the next title. By doing so, the point at which Playback Control Engine 32 ends PL playback can be used as the end of the title.
- FIG. 33 is a flowchart showing a PL playback procedure by the Playback Control Engine 32.
- This playback procedure includes control of the Presentation Engine 31 (step S46) and control of the BD-ROM drive 1 or HDD 17 (step S46).
- the Playltem to be processed in this flowchart is Playltem # x.
- This flowchart reads the current PL information (.mpls) (Step S41), and thereafter, the processing of steps S42 to S50 is executed.
- Steps S42 to S50 repeat the processing of Steps S43 to S50 for each PI information constituting the current PL information until Step S49 becomes Yes.
- the Playltem to be processed in this loop processing is called PlayItem # x (PI # x). This Playltenrffx is initialized by being set to the first Playltem of the current PL (step S42).
- this Playltem # x becomes the last Playltem of the current PL (step S49), and if it is not the last Playltem, the next Playltem in the current PL is It is set to Playltem # x (step S50).
- Steps S43 to S50 which are repeatedly executed in the loop processing, read the Clip information specified by the Clip_information_file__name of Playltem # x into the scenario memory 21 (step S43), and the In-time of Playltem # x Is converted to I-picture address u using the EPmap of the current Clip information (step S44), and Out-time of Playltem # x is converted to I-picture address V using the EP_map of the current Clip information. (Step S45), find the next I-picture of the address V obtained by these conversions, set the address immediately before that address to the address w (Step S47), and calculate in this way. Using the address w, the reading of the TS packet from the I picture address u to the address w is instructed to the BD-ROM drive 1 or the HDD 17 (step S48).
- the presentation engine 31 is instructed to output from mark_time_stamp of the current PLMark to Out-time of Playltem # x (step S46).
- 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 (step S49).
- Playltem # x is current: If not the last PI of the PL, the next Playltem in the current PL is set to Playltem # (step S50), and the process returns to step S43. By repeating the above steps S43 to S50, PL Are reproduced sequentially.
- FIG. 34 is a flowchart showing an angle switching procedure and SkipBack, SkipNext procedures. This flowchart is performed in parallel with the processing procedure of FIG. 33, and repeats the loop processing consisting of 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—multi_angles is a flag indicating whether Playltem # x supports multi-angles. 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 into a variable y (step S56), and the y-th Clip—information—file—name in Playitem # x is specified.
- the Clip information is read out to the scenario memory 21 (step S57), the current PTM is converted to an I picture address u using the EP_map of the current Clip information (step S58), and the Out_time of Playltem # x is set to the current It is converted to an I picture address v using the EP-map of the Clip information (step S59).
- the flow shifts 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 or not an API meaning SkipBack / SkipNext has been called from the Java virtual machine 38.
- the processing procedure of the flowchart is executed.
- FIG. 35 is a flowchart showing a processing procedure when the SkipBack, SkipNext API is called.
- the processing procedures for executing SkipBack and SkipNext are various. It is to be noted that the description here is only an example.
- Step S.61 1 is to determine the power PI number indicated by the PSR and the current PTM To obtain the current Mark information.
- 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 pressed.
- step S64 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 it is the SkipNext key, the direction flag is set to +1 and the power mark PLMark will be incremented. If it is a SkipBack key, the direction flag is set to -1, so the current PLMark will be decremented.
- step S66 the PI described in the ref—to—Playltem_ld of the current PLMark is set to Hayltem # x.
- step S67 the Clip—information of Playltem # x; Read information.
- step S68 the mark-time-stamp of the current PLMark is converted to an I-picture address u using the EP-map of the current Clip information.
- step S69 Out-time of Playltem # x is converted to I-picture address V using EP_map of current Clip information.
- step S70 the output up to the mark-time-stamp of the current PLMark or the Out-time of Playltem # x 3 ⁇ 4: After instructing the Presentation Engine 31, the process proceeds to step S47 in FIG.
- the I-picture addresses u and v are changed, and the reproduction of another part is ordered, and then the process proceeds to step S47.Therefore, the TS bucket is read from another AVClip, and the video contents are read. Switching 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 termination requirements of the loop processing. That is, step S76 makes the loop processing end requirement that the current PTM is the Out_time of PI # x.
- step S73 it is determined whether or not the fast forward API or the fast reverse API has been called from the Java virtual machine 38. If called, 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). By setting the current PTM to the PTS of the next I picture in this way, the AVClip can be played every second. As a result, the AVClip is reproduced in the forward direction at a double speed or the like. If it is a quick reverse, it is determined whether the current ⁇ has reached the Out-time of Playltem # x (step S80). If not reached, the PTS of the immediately preceding I picture is set to the current PTM (step S81).
- the AVClip By setting the read destination address A to the previous I picture in this way, the AVClip can be played back one second at a time in the backward direction. As a result, the AVClip is reproduced in the reverse direction at a double speed or the like.
- the processing procedures for executing fast-forward and rewind are various. Please note that this is only an example.
- 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). With 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 Hayltem # x exists according to sync-Playltem_id. If so, the flow shifts to the flowchart of FIG. FIG. 37 is a flowchart showing the playback procedure of SubPlayltein.
- 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 a playback process based on SubPlayItem # y.
- Steps S87 to S92 in Fig. 37 are performed based on SubPlayItem # y. It is a flowchart which shows a process.
- step S87 the Clip information specified by Clip—information—file—name of SubPlayItem # y is read.
- step S88 the In_time of SubPlayItem # is converted to an address ⁇ using the EP-map of the current Clip information.
- step S89 the Out-time of SubPlayItem # y is converted to an 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.
- the I-picture next to address 0 obtained by these conversions is obtained, and one before that address is set to address y (step S91), and the SubClip is calculated using the address y calculated in this way. This is to instruct the BD-ROM drive 1 or the HDD 17 to read the TS packet from the address ⁇ to the address in #z (step S92).
- 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 in FIG. become. Only after the processing of the flowchart in FIG. 36 is completed, step S53 becomes Yes and the process proceeds to step S54.
- Step S54 is the output of the reproduction end event to the Java virtual machine 38, which allows the Java virtual machine 38 to know the lapse of the reproduction time of 2 hours.
- FIG. 38 is a flowchart showing a processing procedure of the application manager 36 according to the fifth embodiment.
- the flowchart of FIG. 38 is an improvement of the flowchart of FIG. The improvement is that step S 24 is added between step S 21 1 and step S 22, and when step S 24 becomes Yes, there is a step S 101 executed. It is.
- step S24 the JMF player instance is stored in the work memory 37. This is a determination as to whether or not there is any data. 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 so, the Java player instance in the work memory is deleted, and then (Step In step S102, the end of the title is notified to the module manager 34 (step S26). If not notified, the loop processing consisting of steps S21 to S24 is repeated.
- the ablation manager 36 can know the point of time when the playback time of 2 hours has elapsed, a menu is displayed in the end condition of the PL playback, and the menu is displayed. Control to branch to another title in accordance with the operation can be realized.
- the sixth embodiment relates to an improvement of providing a data management table 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.
- "Survival in oral memory 29" means that the Java archive file that constitutes the application is read from local memory 29 and can be transferred to work memory 37 in Java virtual machine 38.
- 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, and the data management table has the same concept of a live range.
- Application At first glance, it seems wasteful to have the same concept as the Yon 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 consists of a BD-ROM, a local memory 29, and a Java virtual machine 38, and shows the relationship between the BD-ROM, the oral memory 29, and the work memory 37.
- Arrow myl indicates reading between BD-ROM and local memory 29, and arrow my2 indicates reading between oral memory 29 and work memory 37.
- the annotations on the arrows indicate when these readings occur. According to the annotation, reading between the BD-ROM and the local memory 29 is so-called "look-ahead" and must be performed before the application is needed.
- reading from the local memory 29 to the work memory 37 is performed when the application becomes necessary.
- “When needed” means the point in time when the life span of the application has arrived (1), and the point in time when an application call is instructed by another application or the application manager 36 (2).
- Arrow my3 indicates release of the application occupied area in work memory 37
- arrow my4 indicates release of the application occupied area in local memory 29.
- the annotations on the arrows indicate when these readings are made.
- 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 needed for the Java virtual machine 38. This point when it is no longer needed is not an "end point.” It means “at the end when there is no possibility of restart", that is, when the corresponding title ends.
- the release point in the work memory 37 is determined 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 title # 2
- the time axis of these titles at the timing shown in Fig. 41 (b), You want to use local memory 29.
- the Java archive files that make up the application # l and application # 2 are read into the local memory 29, and the title # l time axis continues, application # l and application # 2 In the oral memory 29.
- the Java archive files that make up application # l are released from local memory 29, and the Java archive files that make up application ⁇ are read into oral memory 29 instead.
- a rough playback unit is preferably a non-seamless playback unit such as a title or PL.
- a seamless playback unit such as a chapter in a PL is desirable.
- Java archive file was recorded in a separate recording area from AVCIip. But this is only an example. Java archive files may be embedded in the recording area occupied by AVCIip on BD-ROM. There are two types of embedding modes: carouseling and interleaving unitization.
- 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 AVCIip, and the second row shows sectioning.
- the third row shows the TS bucketing, and the fourth row shows the TS bucket sequence forming the AVCIip.
- the sectioned and TS bucketed data ("D" in the figure) is embedded in AVCIip.
- Java archive files multiplexed on AVCIip by the carousel will be read at low bandwidth when read. Since reading at this low bandwidth takes a long period of time, typically 2-3 minutes, the playback device will read the Java archive file in 2-3 minutes.
- FIG. 43 shows the Java archive file embedding by interleaving.
- FIG. The first row shows the AVClip to be embedded
- the second row shows the Java archive file interleaved with the AVClip
- the third row shows the AVClip arrangement in the recording area of the BD-ROM.
- the Java archive file to be embedded in the stream is interleaved, and between the divided parts (AVClip 2/4, 3/4 in the figure) constituting XXXXX.m2ts constituting AVClip It is recorded.
- Java archive files multiplexed on AVClip by interleaving will be read at a higher bandwidth than carouseling. Because of this high bandwidth reading, the playback device reads the Java archive file in a relatively short time.
- Carouseled Java archive files are not pre-seen.
- the current playback time reaches the portion where the carouselized and interleaved Java archive file is embedded in the recording area of the AVClip on the BD-ROM, 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 it is read into the local memory 29 prior to the title playback, and that the read attribute is read in the carousel format during the title playback.
- FIG. 44 (a) is a diagram showing an example of the data management table.
- FIG. 44 (b) is a diagram showing the transition of the contents stored in the roll memory 29 due to the allocation of the data management table.
- the vertical axis indicates the occupied area in the local memory 29
- the horizontal axis indicates the PL time axis in one title.
- application # l is described so that the entire PL time axis within one title is set as a live range.
- Cliapter # 1 to Cliapter # 5 occupy the area in the local memory 29.
- the read priority is a priority that determines the priority of reading to the local memory 29. There are multiple values for read priority. To set two levels of priority, set the value indicating Mandatory and the value indicating optional as the read priority. In this case, Mandatory means higher read priority and optional means lower read priority.
- FIG. 45 (a) is a diagram showing the memory size of the local memory 29 in the old and new playback devices in comparison.
- the arrow mkl indicates the memory size in the old playback device, and the arrow mk2 indicates the memory size in the new playback device.
- FIG. 45 (b) is a diagram showing an example of a data management table in which read priorities are set.
- the application manager 36 performs the processing according to the processing procedure shown in FIG.
- FIG. 46 is a diagram showing a processing procedure of preload control by the application manager 36.
- This flowchart reads the data management table in the title to be played back (step S111), and sets the application with the lowest applicationID to the application i while having the highest read priority in the data management table (step S111).
- step S1 13 and step S114 After performing the determinations in step S1 1 2), step S1 13 and step S114, the application i is preloaded into the local memory 29 (step S1 15).
- 1 16 is No and Step SI 17 is looped until it is determined as No.
- Step S116 of the two steps defining the end requirement of the loop processing is to determine whether or not there is an application k having the next highest applicationID and the same read priority as the application i. . If such an application k exists, the application k is made an application i (step S119).
- step S117 is a determination as to whether or not there is an application having the next lowest read priority in the data management table. Then, among the applications having the second lowest read priority, the application k with the smallest applicationID is selected (step S118), and the application k is set as the application i (step S119). As long as these steps S116 and S117 are set to Yes, the above-described processing of steps S113 to S115 is repeated. In steps S116 and S117, if there is no corresponding application, the process of this flowchart ends.
- Step S120 is a judgment as to whether or not there is an application having the same applicationID and a high read priority; j.
- Step S1221 is a step of determining whether or not the remaining capacity of the local 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 proceeds to Step S116 without being preloaded in the local memory 29.
- step S120-step S12.1 the data of the read priority -Optional will be pre-loaded to the oral memory 29 unless the judgment in step S120-step S12.1 becomes "Yes". Is not done.
- the old playback device with a small memory scale reads only two or three applications, and the judgment in step S121 is No. However, the new playback device with a large memory scale loads more applications. Even so, the judgment in step S1221 is not No. As described above, only the Mandatory application is read into the local memory 29 in the old playback device, and the Mandatory application and the Optional application are read into the new playback device.
- Step S122 is a step executed when it is determined to be Yes in step S122.
- an application j having the same applicationlD and having a high read priority exists in the local memory 29
- 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 this is the case (step S122). If it exceeds, the application j is preloaded by overwriting the application j on the local memory 29 using the application i (step S122). If it is less, the application i is not preloaded into the local memory 29, and the process directly proceeds to step S116.
- FIG. 47 (a) is a diagram showing an example of a data management table assumed in this specific example.
- Java archive files of different sizes can be loaded into the local memory 29 according to the memory size, so for playback devices with a small memory size, Java archive files with thumbnail images with the minimum necessary resolution
- a Java file containing SD images with a medium resolution is used.
- a high resolution is used.
- a Java archive file having an HD image with the image can be imported to the local memory 29.
- FIG. 48 is a diagram showing a specific example of the reading process with reference to the data management table.
- the two applications in this figure are two applications with 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 separate file 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). Of these applications, application # 2 and application # 3 have a read attribute indicating load.
- 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 in consideration of reproduction with a reproduction device having a minimum necessary 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 size 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 is performed by a playback device having a large memory size. Despite the large memory size, the inability to read application # 3 until it reaches Chapter 4 to Chapter # 5 is a waste of memory size. Therefore, in the data management table in this figure, preload the same application # 3.
- the read attribute indicating the ID is added and recorded on the BD-ROM, and the same applicationID 3 ⁇ 4: is assigned to these.
- FIG. 49 is a diagram showing a processing procedure of the load processing based on the data management table.
- the loop processing consisting of steps S131 to S133 is repeated while title reproduction is continued.
- Step S1311 is for determining whether or not the life span of the application having the startup attribute indicating AutoRun has arrived. If the application arrives, the application having the startup attribute indicating AutoRmi is set to the application q (step SI34), a start instruction to start the application q is issued to the Java virtual machine 38, and the application q is executed. The data is read from the oral memory 29 to the work memory 37 (step S135).
- Step S133 is a determination as to whether or not the reproduction of all PLs in the title has been completed. 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 processing of this flowchart ends.
- Step S132 is a determination as to whether or not a call from the running application has been received. If there is, the called application is set to application q (step S1336), and it is determined whether or not the current playback point is a live range of application q in the application management table (step S1337). ). If it is not a live range, the start failure is displayed (step S148), and the process returns to the loop consisting of steps S13.1 to S133. Live range Then, the load processing is performed according to the flowchart of 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 read directly from the BD-ROM to the work memory 37 without passing through the local memory 29. . In this case, PL playback is interrupted because a head seek for reading the application occurs (step S145).
- step S139 it is determined whether a read attribute is added to the application.
- the absence of the read attribute means that the application q is not carouseled or interleaved. However, even if the read attribute is not added, the local memory
- 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 it has been preloaded, the process proceeds to step S135.
- Step S142 is a determination step performed when the read attribute is "load”, and determines whether the application q is carouseled or interleaved. If interleaved, the Java virtual machine 38 executes the cache sense (step S144). If the application q exists in the local memory 29, the process proceeds to step S135 to load the application q into 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). Carouseled If so, the timer is set (step S148), and the cache sense is executed by the Java virtual machine 38 (step S146) until the timer times out (step S147). If the application q appears in the local memory 29, the process proceeds to step S135 in FIG. 49 to load the application q 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 illustrating how an application is read by the Java virtual machine 38.
- Arrows ⁇ 1,2 indicate the reading of a Java archive file that is alive in the application management template, alive in the data management table, and has a read attribute indicating force-rucelling and interleaving.
- the arrow ⁇ 1 indicates the local memory 29 sense performed in steps S65 and S67.
- the local memory 29 sense means that the data embedded by the carousel or the interleaving may be present in the local memory 29 because the data 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.
- Arrow Vl, 2 indicates that a Java archive file that is alive in the application management table but not 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.
- Arrow # 2 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 exists.
- Arrow 1 corresponds to the reading in step S140, and Indicates a request for direct read from the BD-ROM by the virtual machine 38.
- the arrow ⁇ 2 indicates the reading of the Java archive file to the local memory 29 according to the request.
- Arrow 3 indicates reading of the Java archive file from the local memory 29 to the work memory 37.
- the number of applications resident simultaneously on the local memory 29 can be specified so as to be equal to or less than a predetermined number.
- a cache miss can be avoided as much as possible. Since application reading without cache miss can be guaranteed, the application is not read from the BD-ROM until the AVClip playback is stopped when the application is called. Since AVClip playback is not interrupted, seamless playback of AVClip can be guaranteed.
- the time axis of the non-AV system title is determined based on the survival area of the application.
- the behavior of the application is unstable, and there may be startup failure or abnormal termination.
- the present embodiment proposes a Fail Safe mechanism in a case where a startup failure or abnormal termination has occurred.
- FIG. 52 (a) shows the internal structure of a BD-J object according to the seventh embodiment. What is new in this figure compared to Fig. 7 (b) is that a playlist management template has been added.
- FIG. 52 (b) is a diagram showing an example of the playlist management table.
- the playlist management table includes a PL specification and a playback attribute of the PL.
- the designation of PL indicates the PL that can be played back on the title time axis of the corresponding title.
- the PL playback attribute indicates whether the specified PL is automatically played at the same time as the start of title playback (the PL automatically played in this manner is called the default PL).
- FIG. 53 (a) shows the title time axis for non-AV titles when the playback attribute is set to indicate non-automatic playback.
- FIG. 53 (a) shows the title time axis for non-AV titles when the playback attribute is set to indicate non-automatic playback.
- the title time axis is determined from the live range of the application, like the non-AV title.
- FIG. 53 (b) is a diagram showing the title time axis of a non-AV title in which the playback attribute is set to AutoPlay. If the playback attribute is set to indicate AutoPlay, the Playback Control Engine 32 starts playback of the default PL at the same time as playback of the non-AV title starts. However, even if the application operates normally and terminates normally, the title time axis is determined based on the PL time axis.
- FIG. 53 (c) shows a case where the playback attribute is set to indicate “AutoPlay” in the playlist management table and the application ends abnormally. As a result of this abnormal termination, no application is running, but the playback of the default PL continues. Also in this case, the PL time axis of the default PL becomes the title time axis.
- 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, since the default PL playback by the Playback Control Engine 32 is performed irrespective of the failure to start the application, the time axis of the default PL becomes the title time axis.
- FIG. 52 (c) is a diagram showing 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 The Title branch Immediately thereafter, it instructs the Playback Control Engine 32 to start playback of this AutoHayPL. In this way, a 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 S 103 and S 104 are added before step S 1, and step S 100 is added between steps S 21 and S 22. , 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 template 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 S104).
- step S100 it is determined whether or not reproduction is being performed by Presentation Engine 31. If the data is being reproduced, the process proceeds 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 module manager 34 of the end of the title. If it is AutoPlay, the flow shifts to step S101 to continue the processing.
- the titles to be replayed here are non-AV titles that include a game abuse of stacking falling tile pieces.
- the playback attribute in the playlist management table is set to AutoPlay
- the default PL playback by the Playback Control Engine 32 also starts. Since the execution of the game app and the playback of the default PL are performed in parallel, the foreground is the screen of the game app and the background is the playback screen of the default PL, as shown in the upper left of Figure 55. A composite image as an image is 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 is in a state where something is reflected because the default PL is continuously played.
- By specifying the playback attribute in such a playlist management table even if the game application in the non-AV title ends abnormally, it is possible to maintain the operation without hangup / blackout.
- the BD-J object has two tables, a data management table and an application management table.
- This embodiment discloses a form in which these are integrated into one table.
- the item of read attribute in the data management table is abolished, and an attribute of ready attribute is provided in the start attribute instead.
- the Ready attribute is a type of an activation attribute indicating that an application 3 is loaded in the local memory 29 in advance in preparation for a call from another application or a call from the application manager 36.
- Figure 56 (b) is a diagram showing the relationship between application handling and startup attributes.
- the application is handled by whether it is pre-speaked (1), automatically started when the current playback point reaches the valid section, or It is activated on call (2), loaded according to the progress of title playback (3), or alive. These differences cause the difference as shown in Fig. 56 (b). Five modes emerge. Of these, the start attribute is set to AutoRun when preloading is performed and “automatic start”, and when loading is performed and "automatic start”.
- the activation attribute is set to the; Ready attribute when preloading or loading is performed and the activation item indicates "call activation".
- the work memory 37 is alive, but the memory is not loaded into the oral memory 29. "This is because there is no work memory 37 in the application's data management table. This is because the section and the live range of the local memory 29 are integrated. Since the Ready attribute has been added as a start attribute, the application manager 36 can execute an application whose start attribute is set to AutoRun and an application whose start attribute is set to Ready before the title playback. Processing for preloading to the local memory 29 is performed. By doing so, it is possible to perform processing in which the application is pre-stored in the local memory 29 without providing a 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 and 2 indicate 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 the reading of an application that is alive in the application's data management table and whose startup attribute is Persistent.
- the data management table and the application management table can be combined into one table (application ⁇ ⁇ ⁇ data management table), the processing by the application manager 36 is simplified. can do. Note that the application's data management table may be further simplified by eliminating the read priority.
- the read priority when the application is read into the local memory 29, the read priority is referred to, and the read processing is given priority according to the read priority.
- the ninth embodiment information meaning Optional and 0 to 255 This is an embodiment in which the read priority is represented by a combination with numerical values up to.
- FIGS. 58 (a) and (b) are diagrams showing an example of the read priority according to the ninth embodiment.
- 255 and 128 are examples of the read priority from 0 to 255.
- application # 2 means that the read priority is higher than application # 3.
- the application manager 36 first reads the application to which the read priority indicating Mandatory is assigned to the local memory 29.
- FIG. 59 is a diagram showing a data management table to which a group attribute has been added.
- 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" of title # 2, # 3 indicates that there is an exclusive group, and that title # 2, # 3 belong to the exclusive group of roup # l.
- the above is the recording according to the present embodiment. It is a medium improvement.
- the playback device After reading each application into the local memory 29 based on the data management template, 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 local 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 started by this application is limited to one in principle, only one launcher + 1 application exists in the local memory 29. If there are three or more applications, the application manager 36 must delete them from the local memory 29. It checks whether the existing application is a launcher + 1 application.
- FIG. 59 (a) is a diagram showing access to the local memory 29 based on the application management table.
- group attribute of application # 2 and application # 3 set as read priority -Optional is group # l, these applications belong to the same exclusive group.
- application # l is the launcher application described above, and application # 2 and application # 3 are the applications started by this, so only one of them is on the oral memory 29.
- Group attributes have been assigned to exist.
- the application manager 36 refers to the group attributes of application # 2 and application # 3, and performs processing to delete one of them from the local memory 29. Such a deletion creates a margin in the local memory 29.
- FIG. 60 is a diagram showing variations of the allocation unit.
- the first row shows three application management tables recorded on the BD-ROM
- the second row shows title units
- the third row shows disk units
- the fourth row shows.
- the arrows in the figure schematically show the assignment of the application management table. Referring to this arrow, application management tables # 1, # 2, and # 3 in the first row are assigned to titles # 1, # 2, and # 3 shown in the second row. You can see that it is.
- application management table # 4 is allocated for each disk, and application management table # 5 is allocated for the entire disk set.
- the optical disk according to the present invention is implemented as a BD-ROM.
- the optical disk of the present invention has a feature in 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 disks, and magneto-optical disks such as PDs and MOs.
- a semiconductor memory card such as a compact flash card, a smart media, a memory stick, a multimedia card, a PCM-CIA card, or the like may be used.
- Magnetic recording disk such as flexible disk, SuperDisk, Zip, Clik !, etc., and removable hard disk drive (ii) such as ORB, Jaz, SparQ, SyJet, EZFley, micro drive, etc. Good.
- a hard disk with a built-in device may be used.
- the playback device in all embodiments decodes the AVClip recorded on the BD-ROM and outputs it to the TV.
- the playback device is only a BD-ROM drive, and the other components are the TV.
- the playback device and the TV can be incorporated in a home network connected by IEEE 1394.
- 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 devices are manufactured based on the internal configuration of the playback device described in each embodiment.
- the act is an act of practicing the invention described in the specification of the present application.
- the transfer of the playback device described in each embodiment at no charge (free for sale, sale for free, and gift for free), lending, and importing are also implementations of the present invention.
- the act of offering the transfer or lending to general users through in-store display, solicitation of catalogs, and pamphlet distribution is also the practice of the playback device.
- a Menu (Chapter Menu) for displaying a list of Chapters and a MOVIE object that controls its behavior may be recorded on the BD-ROM so that branching from the Top Menu is possible. It may be called up by pressing the Chapter key of the remote control key.
- TP_extra — TS buckets with headers (hereinafter abbreviated as TS packets with EXs) are grouped into 32 packets and written to three sectors.
- the 32 EX-attached TS packets contained 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. In other words, the sender's device removes the TP-extra-header from each of the 32 EX-attached TS packets included in the Aligned Unit, encrypts the TS packet itself based on the DTCP standard, and outputs it. When outputting TS buckets, isochronous packets are inserted anywhere between TS buckets. This insertion point is based on the time indicated in Arribval—Time—Stamp of TP_extra_header. is there. The playback device 200 outputs a DTCP_Descriptor with the output of the TS packet.
- DTCP_Descriptor indicates the copy permission setting in TP_extm_header. If the DTCP-Descriptor is described to indicate “copy prohibited” here, the TS packet 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.
- the digital stream may be a DVD-Video standard or a DVD-Video Recording standard VOB (Video Object).
- VOB is a program stream conforming to the ISO / IEC13818-1 standard obtained by multiplexing a video stream and an audio stream.
- the video stream in AVClip may be in the 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 may be obtained by encoding an analog video signal broadcasted by analog broadcasting. It may be stream data composed of a transport stream broadcast by digital broadcasting.
- the content may be obtained by encoding an analog / digital video signal 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 BD-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 also performs processing as an MHP STB.
- the playback device may be a Java platform embedded in a device for processing control of a mobile phone. If the BD-J module 35 is such a Java platform, 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 no problems occur even if the MOVIE mode is executed in the BD-J mode. Because there is no.
- operation can be guaranteed in only one mode.
- the reproduction process may be executed only in the BD-J mode. As described in the fifth embodiment, even in the BD-J mode, playback control synchronized with PL playback can be performed. Therefore, it is not necessary to provide the MOVIE mode strongly.
- a navigation command may be provided in the interactive graphics stream to be multiplexed in the AVClip, 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 present invention discloses the internal configuration in the above-described embodiment, and it is clear that mass production is performed based on this internal configuration. From this, the playback device according to the present invention has industrial applicability.
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2005514678A JP4091078B2 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、記録方法、再生方法 |
US10/572,873 US8131130B2 (en) | 2003-10-10 | 2004-10-12 | Recording medium, playback apparatus, recording method, and playback method |
KR1020067007251A KR100937790B1 (ko) | 2003-10-10 | 2004-10-12 | 기록매체, 재생장치, 기록방법, 재생방법 |
EP04773784A EP1675117A4 (en) | 2003-10-10 | 2004-10-12 | PLAYBACK DEVICE, PROGRAM AND METHOD |
US12/110,452 US7630615B2 (en) | 2003-10-10 | 2008-04-28 | Recording medium, playback apparatus, recording method, and playback method |
US12/110,473 US7623769B2 (en) | 2003-10-10 | 2008-04-28 | Recording medium, playback apparatus, recording method, and playback method |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003-352913 | 2003-10-10 | ||
JP2003352913 | 2003-10-10 | ||
JP2003-379758 | 2003-10-11 | ||
JP2003379758 | 2003-11-10 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/110,452 Division US7630615B2 (en) | 2003-10-10 | 2008-04-28 | Recording medium, playback apparatus, recording method, and playback method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005036545A1 true WO2005036545A1 (ja) | 2005-04-21 |
Family
ID=34436929
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/015339 WO2005036555A1 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法 |
PCT/JP2004/015337 WO2005036547A1 (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/015333 WO2005036545A1 (ja) | 2003-10-10 | 2004-10-12 | 再生装置、プログラム、再生方法 |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/015339 WO2005036555A1 (ja) | 2003-10-10 | 2004-10-12 | 記録媒体、再生装置、プログラム、再生方法 |
PCT/JP2004/015337 WO2005036547A1 (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 | 再生装置、プログラム、再生方法 |
Country Status (7)
Country | Link |
---|---|
US (10) | US7515812B2 (ja) |
EP (9) | EP1675118A4 (ja) |
JP (6) | JP4182110B2 (ja) |
KR (7) | KR101059343B1 (ja) |
CN (2) | CN101840718B (ja) |
TW (1) | TW200518070A (ja) |
WO (5) | WO2005036555A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008537273A (ja) * | 2005-03-03 | 2008-09-11 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | 光ディスクアプリケーション用のストリームファイルシステム |
US7515812B2 (en) | 2003-10-10 | 2009-04-07 | Panasonic Corporation | Recording medium, reproduction device, program, and reproduction method |
JP2011018277A (ja) * | 2009-07-10 | 2011-01-27 | Sharp Corp | プログラム実行装置、プログラム実行方法、コンテンツ再生装置、プログラムおよび記録媒体 |
CN102917246A (zh) * | 2012-08-31 | 2013-02-06 | 北京视博云科技有限公司 | 一种基于虚拟机的应用数据提供方法、装置及系统 |
US9661259B2 (en) | 2013-03-28 | 2017-05-23 | Mitsubishi Electric Corporation | Playback device, control method, and program |
Families Citing this family (83)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8218951B2 (en) | 2003-10-30 | 2012-07-10 | Samsung Electronics Co., Ltd. | Storage medium storing program management information, and reproducing method and apparatus |
CA2761989C (en) * | 2003-11-10 | 2013-11-26 | Panasonic Corporation | Recording medium, playback apparatus, program, playback method, system integrated circuit |
KR20050066265A (ko) * | 2003-12-26 | 2005-06-30 | 엘지전자 주식회사 | 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치 |
KR20050066264A (ko) | 2003-12-26 | 2005-06-30 | 엘지전자 주식회사 | 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치 |
JP4626799B2 (ja) * | 2004-07-12 | 2011-02-09 | ソニー株式会社 | 再生装置および方法、情報提供装置および方法、データ、記録媒体、並びにプログラム |
CN101814310B (zh) * | 2004-07-22 | 2012-11-28 | 松下电器产业株式会社 | 重放装置和重放方法 |
TWI451406B (zh) * | 2004-07-22 | 2014-09-01 | Panasonic Corp | 用以實施應用程式同步化播放之播放裝置、播放方法及播放程式 |
KR100694123B1 (ko) * | 2004-07-30 | 2007-03-12 | 삼성전자주식회사 | 동영상 데이터와 어플리케이션 프로그램이 기록된 저장매체 및 그 재생 장치 및 방법 |
KR100677132B1 (ko) | 2004-09-09 | 2007-02-02 | 삼성전자주식회사 | 동영상 재생 및 프로그래밍 기능을 위한 멀티미디어데이터를 기록한 저장 매체, 그 재생 장치 및 재생 방법 |
EP1810294B1 (en) | 2004-11-09 | 2018-11-28 | Thomson Licensing | Bonding contents on separate storage media |
KR20060059572A (ko) * | 2004-11-29 | 2006-06-02 | 삼성전자주식회사 | 플레이리스트를 자동 재생하기 위한 정보를 포함하는 저장매체, 그 재생 장치 및 재생 방법 |
JP5265920B2 (ja) | 2004-12-06 | 2013-08-14 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | 複数の記憶媒体にインターラクティブ性を拡張する方法と装置 |
KR20060081336A (ko) * | 2005-01-07 | 2006-07-12 | 엘지전자 주식회사 | 기록매체에서의 디지털 인증방법 |
KR20060085154A (ko) * | 2005-01-21 | 2006-07-26 | 엘지전자 주식회사 | 기록매체, 로컬 스토리지를 이용한 기록매체의 재생방법과재생장치 |
US8249416B2 (en) | 2005-01-28 | 2012-08-21 | Panasonic Corporation | Recording medium, program, and reproduction method |
EP1696321A1 (en) | 2005-02-23 | 2006-08-30 | Deutsche Thomson-Brandt Gmbh | Method and apparatus for executing software applications |
EP2317516B1 (en) * | 2005-02-04 | 2013-04-17 | Panasonic Corporation | Readout apparatus, recording method and readout method |
US7844355B2 (en) * | 2005-02-18 | 2010-11-30 | Panasonic Corporation | Stream reproduction device and stream supply device |
WO2006090300A1 (en) | 2005-02-28 | 2006-08-31 | Koninklijke Philips Electronics N.V. | Fallback mechanism for data reproduction |
US20090019468A1 (en) * | 2005-03-09 | 2009-01-15 | Vvond, Llc | Access control of media services over an open network |
US20080022343A1 (en) | 2006-07-24 | 2008-01-24 | Vvond, Inc. | Multiple audio streams |
US9176955B2 (en) * | 2005-03-09 | 2015-11-03 | Vvond, Inc. | Method and apparatus for sharing media files among network nodes |
US7698451B2 (en) * | 2005-03-09 | 2010-04-13 | Vudu, Inc. | Method and apparatus for instant playback of a movie title |
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 |
US8904463B2 (en) * | 2005-03-09 | 2014-12-02 | Vudu, Inc. | Live video broadcasting on distributed networks |
US8219635B2 (en) * | 2005-03-09 | 2012-07-10 | Vudu, Inc. | Continuous data feeding in a distributed environment |
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 |
US8099511B1 (en) | 2005-06-11 | 2012-01-17 | Vudu, Inc. | Instantaneous media-on-demand |
US8020084B2 (en) * | 2005-07-01 | 2011-09-13 | Microsoft Corporation | Synchronization aspects of interactive multimedia presentation management |
US8799757B2 (en) * | 2005-07-01 | 2014-08-05 | 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 |
JP5373772B2 (ja) | 2008-04-16 | 2013-12-18 | パナソニック株式会社 | 記録媒体、記録装置、記録方法、及び再生装置 |
KR101486772B1 (ko) * | 2008-06-04 | 2015-02-04 | 삼성전자주식회사 | 재생 위치에 따라 디지털 컨텐츠를 관리하는 방법과 장치및 실행하는 방법 및 장치 |
JP2010009408A (ja) * | 2008-06-27 | 2010-01-14 | Sony Corp | 情報処理装置、およびデータ処理方法、並びにプログラム |
CN102027544B (zh) * | 2008-07-16 | 2013-11-06 | 松下电器产业株式会社 | 再生装置、再生方法及程序 |
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 |
WO2010052857A1 (ja) * | 2008-11-06 | 2010-05-14 | パナソニック株式会社 | 再生装置、再生方法、再生プログラム、及び集積回路 |
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 | 삼성전자주식회사 | 가상 이미지 파일 처리 방법 및 장치 |
EP2254119B1 (en) | 2009-05-20 | 2019-03-13 | Sony DADC Austria AG | Method for copy protection |
EP2254118A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
EP2254120A1 (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 |
US9263085B2 (en) | 2009-05-20 | 2016-02-16 | Sony Dadc Austria Ag | Method for copy protection |
EP2254116A1 (en) | 2009-05-20 | 2010-11-24 | Sony DADC Austria AG | Method for copy protection |
EP2254117B1 (en) | 2009-05-20 | 2018-10-31 | Sony DADC Austria AG | Method for copy protection |
JP2012527712A (ja) | 2009-05-20 | 2012-11-08 | ソニー デーアーデーツェー オーストリア アクチェンゲゼルシャフト | コピープロテクションのための方法 |
US20120109871A1 (en) * | 2009-07-14 | 2012-05-03 | Pioneer Corporation | Reproducing apparatus and method, and computer program |
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 | 삼성전자주식회사 | 디스크리스 어플리케이션 재생 장치 및 기록 장치, 재생 방법 및 기록 방법과 디스크리스 어플리케이션을 기록한 정보저장매체 |
KR20140039504A (ko) * | 2012-09-24 | 2014-04-02 | 삼성전자주식회사 | 블루레이 디스크 재생 장치 및 블루레이 디스크 로딩 방법 |
WO2014057833A1 (ja) * | 2012-10-10 | 2014-04-17 | ソニー株式会社 | 受信装置、受信方法、送信装置、送信方法、及び、プログラム |
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 | 阿里巴巴集团控股有限公司 | 一种图片加载方法及装置 |
EP3310066A1 (en) * | 2016-10-14 | 2018-04-18 | Spotify AB | Identifying media content for simultaneous playback |
JP7119858B2 (ja) * | 2018-09-28 | 2022-08-17 | ブラザー工業株式会社 | 工具寿命管理装置、工作機械、表示処理方法及びコンピュータプログラム |
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 | 自動プログラム開始装置 |
JPH11219313A (ja) * | 1998-02-02 | 1999-08-10 | Mitsubishi Electric Corp | コンテンツ先読み方法 |
JP2001022625A (ja) * | 1999-07-09 | 2001-01-26 | Sony Corp | データ記録装置、データ記録方法、データ取得装置、データ取得方法 |
WO2001035416A2 (en) * | 1999-11-10 | 2001-05-17 | Koninklijke Philips Electronics N.V. | Record carrier, device and method for playing back a record carrier, device for recording a record carrier |
JP2002269929A (ja) * | 2001-03-08 | 2002-09-20 | Hitachi Ltd | ディスク装置 |
JP2002369154A (ja) * | 2001-04-02 | 2002-12-20 | Matsushita Electric Ind Co Ltd | ディジタル映像コンテンツの映像再生装置、映像再生方法、映像再生プログラム、パッケージメディア |
JP2003032637A (ja) * | 2001-07-16 | 2003-01-31 | Sharp Corp | データ放送受信装置 |
Family Cites Families (63)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0491104A (ja) | 1990-08-06 | 1992-03-24 | Ootex Kk | 光重合反応開始剤 |
JPH0759608B2 (ja) | 1990-08-06 | 1995-06-28 | 株式会社クラレ | イミド化アクリル樹脂粒子体の処理方法 |
JPH0491078A (ja) | 1990-08-06 | 1992-03-24 | Kao Corp | イミダゾール誘導体 |
JP2609749B2 (ja) | 1990-08-31 | 1997-05-14 | 日本電気アイシーマイコンシステム株式会社 | 電流供給回路 |
JP2798490B2 (ja) | 1990-09-03 | 1998-09-17 | 日本電気アイシーマイコンシステム株式会社 | 発振回路 |
EP0788105B1 (en) * | 1995-08-21 | 1999-10-20 | Matsushita Electric Industrial Co., Ltd. | Multimedia optical disk for easily realizing branch reproduction to parental lock section with a little amount of control information and reproducing device therefor |
CN100351911C (zh) | 1995-08-21 | 2007-11-28 | 松下电器产业株式会社 | 根据交互控制实现意外性场景展开的多媒体光盘再生装置 |
CN1103486C (zh) * | 1995-08-21 | 2003-03-19 | 松下电器产业株式会社 | 能永久保持图象内容新鲜感的光盘的再生装置及再生方法 |
MX9702848A (es) * | 1995-08-21 | 1997-07-31 | Matsushita Electric Ind Co Ltd | Disco optico de multimedia que permite a un desarrollador de titulos coordinar el uso de funciones especiales de reproduccion y un dispositivo de reproduccion para este disco. |
EP0777230A1 (de) * | 1995-12-04 | 1997-06-04 | Markus Zwickl | CDs enthaltend zusätzliche Textinformation |
EP0935249B1 (en) * | 1996-04-12 | 2006-05-24 | Matsushita Electric Industrial Co., Ltd. | Multimedia optical disc storing both video titles provided with AV functions and video titles with no such functions which can instantly distinguish between such kinds of titles, and a reproduction apparatus and reproduction method for such disc |
CN1260970C (zh) * | 1996-05-09 | 2006-06-21 | 松下电器产业株式会社 | 用于多媒体光盘的记录方法、再生装置及再生方法 |
JPH1063362A (ja) | 1996-08-16 | 1998-03-06 | Nec Corp | レジューム要因別に複数のプログラム状態を保持可能なサスペンドレジューム方法 |
JP3948051B2 (ja) | 1997-04-30 | 2007-07-25 | ソニー株式会社 | 編集装置及びデータ編集方法 |
JP3655433B2 (ja) | 1997-06-20 | 2005-06-02 | パイオニア株式会社 | コンピュータ読み取り可能な記録媒体及び情報再生装置 |
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 |
KR20020022085A (ko) | 1999-07-13 | 2002-03-23 | 썬 마이크로시스템즈, 인코포레이티드 | 응용프로그램 라이프사이클에 따른 응용프로그램 관리방법 및 장치 |
US6874145B1 (en) * | 1999-07-13 | 2005-03-29 | Sun Microsystems, Inc. | Methods and apparatus for implementing an application lifecycle design for applications |
JP3756708B2 (ja) * | 1999-09-30 | 2006-03-15 | 株式会社東芝 | 情報処理端末装置およびそのファイル管理方法 |
CN1225905C (zh) | 1999-10-29 | 2005-11-02 | 公共电视公司 | 交互式节目回放 |
DK1224806T3 (da) | 1999-10-29 | 2004-02-16 | Opentv Corp | System og en metode til optagelse af "pushed" dataindhold |
JP2001238161A (ja) | 2000-02-25 | 2001-08-31 | Sony Corp | 情報付加装置、情報付加方法および記録媒体 |
US7200857B1 (en) * | 2000-06-09 | 2007-04-03 | Scientific-Atlanta, Inc. | Synchronized video-on-demand supplemental commentary |
CN1383678A (zh) | 2000-04-21 | 2002-12-04 | 索尼公司 | 编码设备和方法、记录介质和程序 |
GB0016062D0 (en) * | 2000-06-30 | 2000-08-23 | Koninkl Philips Electronics Nv | Playback of applications with non-linear time |
JP2002057990A (ja) * | 2000-08-09 | 2002-02-22 | Nec Corp | 映像再生システム及びそれに用いるデータ同期方式 |
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 | 分散電源用発電機の出力方法 |
CN1229990C (zh) * | 2001-04-02 | 2005-11-30 | 松下电器产业株式会社 | 数字影像内容的影像再生装置、影像再生方法 |
KR100771264B1 (ko) | 2001-05-12 | 2007-10-29 | 엘지전자 주식회사 | 스크립트 파일이 포함 기록된 기록매체와, 그 재생장치 및방법 |
EP1309195B1 (en) | 2001-10-29 | 2007-11-14 | Humax Co., Ltd. | Method for recording a digital broadcast program and time-based playback of a recorded broadcast program and apparatus therefor |
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 |
CN100414537C (zh) * | 2002-02-07 | 2008-08-27 | 三星电子株式会社 | 包含显示模式信息的信息存储介质、再现装置及其方法 |
JP4532810B2 (ja) | 2002-02-22 | 2010-08-25 | キヤノン株式会社 | 画像処理装置、画像処理装置の制御方法、プログラム、及びコンピュータ読み取り可能な記憶媒体 |
JP2003249057A (ja) | 2002-02-26 | 2003-09-05 | Toshiba Corp | デジタル情報媒体を用いるエンハンスド・ナビゲーション・システム |
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 |
RU2320030C2 (ru) * | 2002-06-24 | 2008-03-20 | Эл Джи Электроникс Инк. | Носитель записи со структурой данных для управления воспроизведением записанных на нем видеоданных нескольких каналов воспроизведения и способы и устройства записи и воспроизведения |
DE10228103A1 (de) | 2002-06-24 | 2004-01-15 | Bayer Cropscience Ag | Fungizide Wirkstoffkombinationen |
TWI234392B (en) * | 2002-08-26 | 2005-06-11 | Samsung Electronics Co Ltd | Apparatus for reproducing AV data in interactive mode, method of handling user input, and information storage medium |
EP2246857A3 (en) * | 2002-09-12 | 2010-12-01 | Panasonic Corporation | Recording medium, playback device, program, playback method, and recording method |
EP1576460B1 (en) * | 2002-11-26 | 2012-01-11 | Panasonic Corporation | Apparatus for managing removable storage media that can be connected thereto, and method and program for managing removable storage media |
JP3908724B2 (ja) * | 2002-12-09 | 2007-04-25 | 株式会社東芝 | 情報再生装置及び情報再生方法 |
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 |
JP4091104B2 (ja) | 2003-10-10 | 2008-05-28 | 松下電器産業株式会社 | 記録媒体、再生装置、記録方法、再生方法 |
JP4117019B2 (ja) | 2003-10-10 | 2008-07-09 | 松下電器産業株式会社 | 記録媒体、再生装置、記録方法、再生方法 |
JP4091105B2 (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 |
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 | 複合集電体およびその製造方法 |
JP2007265851A (ja) | 2006-03-29 | 2007-10-11 | Molex Inc | ケーブル用コネクタ |
-
2004
- 2004-10-08 TW TW093130684A patent/TW200518070A/zh unknown
- 2004-10-12 EP EP04773786A patent/EP1675118A4/en not_active Withdrawn
- 2004-10-12 WO PCT/JP2004/015339 patent/WO2005036555A1/ja active Application Filing
- 2004-10-12 US US10/573,173 patent/US7515812B2/en active Active
- 2004-10-12 CN CN2010101438960A patent/CN101840718B/zh not_active Expired - Fee Related
- 2004-10-12 EP EP04773789A patent/EP1677302A4/en not_active Ceased
- 2004-10-12 JP JP2005514681A patent/JP4182110B2/ja active Active
- 2004-10-12 US US10/573,137 patent/US7702222B2/en active Active
- 2004-10-12 WO PCT/JP2004/015337 patent/WO2005036547A1/ja active Application Filing
- 2004-10-12 KR KR1020067007232A patent/KR101059343B1/ko not_active IP Right Cessation
- 2004-10-12 KR KR1020087009003A patent/KR100937791B1/ko active IP Right Grant
- 2004-10-12 JP JP2005514677A patent/JP4117006B2/ja active Active
- 2004-10-12 KR KR1020097016043A patent/KR101059290B1/ko not_active IP Right Cessation
- 2004-10-12 EP EP10183667.4A patent/EP2267711A3/en not_active Withdrawn
- 2004-10-12 EP EP04773784A patent/EP1675117A4/en not_active Withdrawn
- 2004-10-12 EP EP04773787A patent/EP1675119A4/en not_active Withdrawn
- 2004-10-12 WO PCT/JP2004/015330 patent/WO2005036554A1/ja active Application Filing
- 2004-10-12 KR KR1020087009008A patent/KR100937792B1/ko active IP Right Grant
- 2004-10-12 WO PCT/JP2004/015335 patent/WO2005036546A1/ja active Application Filing
- 2004-10-12 EP EP08155287A patent/EP1944771A3/en not_active Ceased
- 2004-10-12 KR KR1020067007234A patent/KR101051843B1/ko active IP Right Grant
- 2004-10-12 WO PCT/JP2004/015333 patent/WO2005036545A1/ja active Application Filing
- 2004-10-12 JP JP2005514680A patent/JP4262250B2/ja active Active
- 2004-10-12 KR KR1020067007251A patent/KR100937790B1/ko not_active IP Right Cessation
- 2004-10-12 EP EP08155288A patent/EP1944772A3/en not_active Withdrawn
- 2004-10-12 EP EP04773781A patent/EP1672637A4/en not_active Ceased
- 2004-10-12 JP JP2005514678A patent/JP4091078B2/ja not_active Expired - Fee Related
- 2004-10-12 US US10/572,983 patent/US8437625B2/en not_active Expired - Fee Related
- 2004-10-12 JP JP2005514682A patent/JP3825463B2/ja not_active Expired - Fee Related
- 2004-10-12 US US10/572,980 patent/US7715696B2/en active Active
- 2004-10-12 EP EP10170131A patent/EP2239737A3/en not_active Withdrawn
- 2004-10-12 CN CN2009102115066A patent/CN101702320B/zh not_active Expired - Fee Related
- 2004-10-12 US US10/572,873 patent/US8131130B2/en not_active Expired - Fee Related
- 2004-10-12 KR KR1020067007239A patent/KR101051846B1/ko active IP Right Grant
-
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 | 自動プログラム開始装置 |
JPH11219313A (ja) * | 1998-02-02 | 1999-08-10 | Mitsubishi Electric Corp | コンテンツ先読み方法 |
JP2001022625A (ja) * | 1999-07-09 | 2001-01-26 | Sony Corp | データ記録装置、データ記録方法、データ取得装置、データ取得方法 |
WO2001035416A2 (en) * | 1999-11-10 | 2001-05-17 | Koninklijke Philips Electronics N.V. | Record carrier, device and method for playing back a record carrier, device for recording a record carrier |
JP2002269929A (ja) * | 2001-03-08 | 2002-09-20 | Hitachi Ltd | ディスク装置 |
JP2002369154A (ja) * | 2001-04-02 | 2002-12-20 | Matsushita Electric Ind Co Ltd | ディジタル映像コンテンツの映像再生装置、映像再生方法、映像再生プログラム、パッケージメディア |
JP2003032637A (ja) * | 2001-07-16 | 2003-01-31 | Sharp Corp | データ放送受信装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1675117A4 * |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8437625B2 (en) | 2003-10-10 | 2013-05-07 | Panasonic Corporation | Playback apparatus program and playback method |
US7515812B2 (en) | 2003-10-10 | 2009-04-07 | Panasonic Corporation | Recording medium, reproduction device, program, and reproduction method |
US7623769B2 (en) | 2003-10-10 | 2009-11-24 | Panasonic Corporation | Recording medium, playback apparatus, recording method, and playback method |
US7630615B2 (en) | 2003-10-10 | 2009-12-08 | Panasonic Corporation | Recording medium, playback apparatus, recording method, and playback method |
US7702222B2 (en) | 2003-10-10 | 2010-04-20 | Panasonic Corporation | Playback apparatus program and playback method |
US7715696B2 (en) | 2003-10-10 | 2010-05-11 | Panasonic Corporation | Recording medium, playback apparatus, program, and playback method |
US8107788B2 (en) | 2003-10-10 | 2012-01-31 | Panasonic Corporation | Recording medium, playback device, recording method and playback method |
US8131130B2 (en) | 2003-10-10 | 2012-03-06 | Panasonic Corporation | Recording medium, playback apparatus, recording method, and playback method |
US8509596B2 (en) | 2003-10-10 | 2013-08-13 | Panasonic Corporation | Recording medium, playback apparatus, program, and playback method |
US8406604B2 (en) | 2003-10-10 | 2013-03-26 | Panasonic Corporation | Playback apparatus, recording method, and playback method |
JP2008537273A (ja) * | 2005-03-03 | 2008-09-11 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | 光ディスクアプリケーション用のストリームファイルシステム |
JP2011018277A (ja) * | 2009-07-10 | 2011-01-27 | Sharp Corp | プログラム実行装置、プログラム実行方法、コンテンツ再生装置、プログラムおよび記録媒体 |
CN102917246A (zh) * | 2012-08-31 | 2013-02-06 | 北京视博云科技有限公司 | 一种基于虚拟机的应用数据提供方法、装置及系统 |
CN102917246B (zh) * | 2012-08-31 | 2015-01-14 | 北京视博云科技有限公司 | 一种基于虚拟机的应用数据提供方法、装置及系统 |
US9661259B2 (en) | 2013-03-28 | 2017-05-23 | Mitsubishi Electric Corporation | Playback device, control method, and program |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4117006B2 (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: 200480029696.5 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): BW GH 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: 2005514678 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067007251 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004773784 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2004773784 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007089146 Country of ref document: US Ref document number: 10572873 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067007251 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 10572873 Country of ref document: US |