JP5526621B2 - Optical disk playback device - Google Patents

Description

  The present invention relates to data protection of a removable medium attached to an optical disc playback device that plays back a virtual package such as a Blu-ray disc playback device.

  2. Description of the Related Art In recent years, optical disc playback apparatuses that play back large-capacity optical discs that record information with high image quality, high sound quality, and advanced interactive functions have become popular in general households.

  A Blu-ray Disc (BD), which is a typical optical disk playback device, includes video data recorded on a recording medium such as a BD-ROM and other recording media other than the recording medium. There is a technique for reproducing one package (hereinafter referred to as “virtual package”) that is dynamically combined with recorded video data.

  The BD playback device needs a binding unit data area (Binding Unit Data Area) to construct a virtual package, and moves data recorded in the BD-ROM and data recorded in the binding unit data area. By combining them together to construct a virtual package, the BD-ROM data is reproduced with additional information. In the BD playback device, writing data to the binding unit data area is an indispensable function according to the standard.

  The recording medium used for the binding unit data area may be integrated with an optical disk playback device such as a hard disk drive, but is used externally to an optical disk playback device such as an SD memory card or USB flash memory that is a removable medium. A configuration also exists.

  On the other hand, in addition to the data used for the virtual package, the data stored on the removable media can be stored as AV files created by the user on a personal computer or the like, and data taken with a digital camera or video camera. Data can also be played back by a BD playback device.

  When the unit integrated with the optical disk playback device such as a hard disk drive is used for the binding unit data area, data is restored using the journaling function of the file system after restoration even if the system stops during writing. Things are possible. However, considering the cost of the optical disk playback device, it is clear that when the recording medium integrated with the optical disk playback device is used in the binding unit data area, and when the removable media is prepared by the user, the latter It is possible to make it at a lower cost. For this reason, it is expected that an optical disk reproducing apparatus using a removable medium is generally used in the binding unit data area.

    As prior art regarding the virtual package, there are those described in Patent Documents 1 and 2 below.

JP 2006-109494 A Japanese Patent Laid-Open No. 2007-20221

  Generally, a file in a memory medium is managed by a file system, and when some data is recorded in the memory medium, a file management area in the memory medium is updated at the same time. However, removable media such as SD memory cards and USB flash memory do not have a journaling function in the file system, so if an abnormal system shutdown or power failure occurs while operating data in the memory media, There is a problem that system metadata is damaged and all files cannot be referenced.

  When the consistency in the memory medium is lost, it can be used again by initializing the memory. However, if data stored by other than the optical disk playback device that plays back the virtual package exists in the memory medium, There is a problem that the data of the same is erased at the same time.

  If it is a usage form of stationary playback equipment used mainly in ordinary households, it is unlikely that the power supply of the optical disk playback device will suddenly stop due to a power failure, etc. It may turn off suddenly. For example, it is assumed that the battery voltage is low or the ignition key is turned.

  The present invention has been made to solve the conventional problems, and an object of the present invention is to provide an optical disc reproducing apparatus that reproduces a virtual package capable of protecting user data written on a removable medium.

In order to solve the above-described problems, a first aspect of the present invention is an optical disc playback apparatus that plays back an application on a first recording medium and a second recording medium in conjunction with a digital stream. Either one of the recording medium and the second recording medium is a removable medium that is removable from the optical disc playback apparatus and does not have a journaling function in the file system, and a BD-J application section that controls the construction and playback of the virtual package; And a resident application unit for notifying the BD-J application unit that writing to the removable medium is not permitted when the user data is confirmed on the removable medium.

  According to this configuration, it is possible to provide an optical disc playback apparatus using a removable medium that can protect user data by providing a function for determining the presence or absence of user data on the removable medium.

In addition, the resident application unit notifies the BD-J application unit that writing to the removable medium is not permitted every time there is a write request to the removable medium from the BD-J application unit.

  According to this configuration, when a virtual package that has been built is played back, no write request is made, so even if user data exists on removable media, it is possible to play back a virtual package that was previously built. It becomes.

In addition, the resident application unit determines whether or not to permit writing to the removable medium according to the user's initial setting or the user's selection every time there is a write request to the removable medium from the BD-J application unit.

According to this configuration, the user can select data writing to the removable medium. Therefore, even if the user data exists on the removable medium, the virtual package can be constructed and reproduced by the user's selection.

In a second aspect of the present invention, the resident application unit notifies the BD-J application unit that writing to the removable medium is not permitted when a storage level confirmation request is made from the BD-J application unit. Features.

  According to this configuration, it is possible to replace the removable media before constructing the virtual package, and it is found that the user data exists on the removable media immediately before constructing the virtual package, and the virtual package cannot be reproduced. Can be avoided.

In addition, when the resident application unit confirms that user data exists on the removable medium, the resident application unit notifies the user to exchange the removable medium, and if there is no response from the user for a certain period of time, the resident application unit removes the removable data to the BD-J application unit. It is characterized by notifying that writing to the medium is not permitted .

  According to this configuration, in the in-vehicle environment, it is often prohibited for the driver to perform screen operations during driving. However, it is possible to cancel the state where nothing is reproduced at such time, and to reproduce normal content instead of the virtual package.

  The present invention provides an optical disc that reproduces a virtual package capable of protecting user data by providing a function of determining the presence or absence of user data on the removable medium when the removable medium is used as a binding unit data area. A playback device can be provided.

System diagram according to the first embodiment of the present invention 1 is a block diagram of an optical disc playback apparatus according to a first embodiment of the present invention. Software block diagram according to the first embodiment of the present invention The flowchart which shows the process of virtual package construction of the BD-J application which concerns on the 1st Embodiment of this invention The flowchart explaining the procedure when the removable media 12 of the resident application according to the first embodiment of the present invention is loaded. A flowchart when the removable media 12 of the resident application according to the first embodiment of the present invention is loaded. 6 is a flowchart showing write control of the BD-J module according to the first embodiment of the present invention. 6 is a flowchart showing write control of the resident application according to the first embodiment of the present invention. The figure which shows the example of notification of the write request which concerns on the 1st Embodiment of this invention The figure which shows the example of notification after the write control which concerns on the 1st Embodiment of this invention The figure which shows the example of notification of the write control which concerns on the 1st Embodiment of this invention 7 is a flowchart showing write control of a BD-J module according to the second embodiment of the present invention. The flowchart which shows the write-in control of the BD-J module which concerns on the 3rd Embodiment of this invention. The flowchart which shows the write control of the resident application which concerns on the 3rd Embodiment of this invention. The figure which shows the example of notification of the write request which concerns on the 3rd Embodiment of this invention The figure which shows the replacement notification example of the removable media 12 which concerns on the 3rd Embodiment of this invention. The figure which shows the example of notification of the write control which concerns on the 3rd Embodiment of this invention

(First embodiment)
A first embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating an example of a usage pattern of an optical disc playback apparatus 10 according to the first embodiment. For example, the optical disc playback apparatus 10 includes a BD-ROM 11, a removable medium 12, a television 13, and a WWW server 14.

  Next, the BD-ROM 11 that is an optical recording medium reproduced by the optical disc reproducing apparatus 10 according to the first embodiment will be described.

  The BD-ROM 11 is a recording medium on which AV content such as a movie work or live video is recorded.

  The removable medium 12 is a portable recording medium that can freely rewrite data represented by an SD memory card, a memory stick, a compact flash (registered trademark), a smart medium, a multimedia card, and the like. The removable medium 12 is attached to the optical disc playback apparatus 10 and stores data downloaded from the WWW server 14. In addition to these data, AV files saved by a user on a personal computer and data taken by a digital camera or a video camera can be saved, and these data can be played back by the optical disc playback device 10.

  The data downloaded from the WWW server 14 and the content recorded on the BD-ROM 11 can be reproduced in combination. Further, if data is stored from the BD-ROM 11 to the removable medium 12, the optical disk playback apparatus 10 can simultaneously play back the data on the BD-ROM 11 and the data on the removable medium 12 without frequently performing a seek operation on the BD-ROM 11. Is possible.

  The television 13 is a device that displays an image, and also has a function of displaying an operation menu to the user. Therefore, the user can visually operate the optical disc playback apparatus 10.

  The WWW server 14 is a device that provides auxiliary data of content recorded on the BD-ROM 11 to the user via the Internet or the like.

  Here, video data recorded on a recording medium such as the BD-ROM 11, data such as video recorded on a recording medium other than the recording medium (removable medium 12 in the first embodiment), and the like. A technique for reproducing one package (hereinafter referred to as “virtual package”) that is dynamically combined will be described.

The virtual package generates package information that integrally shows the recording contents of a read-only recording medium such as the BD-ROM 11 and a readable / writable recording medium such as the removable medium 12, and is recorded on these recording media. This is a technique for playing and executing digital streams and application programs (hereinafter referred to as “applications”) as if they were recorded in one virtual package. In such a technique, by updating the data recorded in the rewritable removable medium 12, the BD-RO
Even after distributing M11, the contents of the work as the entire virtual package can be changed. For example, a provider of a movie work distributes a BD-ROM 11 that records the main part of the work, and provides a trailer digital stream of another work before the release via the network, so that the BD-ROM 11 is distributed. The latest work can always be advertised to users.

  Next, playback control will be described with reference to FIG. 2 which is a block diagram of the optical disk playback apparatus 10 according to the present invention.

  The optical disk reproducing apparatus 10 includes a pickup 21, a servo 22, a local storage 23, a network interface 24, a signal processing unit 25, and a reproducing unit 26.

  The pickup 21 is a means for acquiring data from the disk 20. The disk 20 is typically the BD-ROM 11 shown in FIG. 1, but may be a DVD-ROM or other recording medium.

  The servo 22 is a device that controls the pickup 21. Desired data is obtained from the disk 20 by seeking the pickup 21 or adjusting the focus. Data acquired from the disk 20 is sent to the signal processing means 25.

  The data processed by the signal processing unit 25 includes not only the data of the disk 20 but also data stored in the local storage 23 and data downloaded from the network via the network interface 24. The signal processing means 25 is a means for processing these data so that the reproduction means 26 can reproduce the data.

  Next, a detailed block diagram of software in the signal processing means 25 is shown in FIG.

  The BD-ROM player model layer 30 defines how AV streams provided from the disc 38, the binding unit data area 36, and the network 37 are decoded. The BD-ROM application environment layer 31 may access the disk 38, the binding unit data area 36, and the network 37. The BD-ROM player model layer 30 also provides means for this purpose.

  The BD-ROM application environment layer 31 executes an AV stream playback procedure and a stream control procedure. The BD-ROM application environment layer 31 includes an HDMV module 32 and a BD-J module 33, and each module realizes a reproduction procedure and a control procedure by different methods.

  The HDMV module 32 constitutes an HDMV title controlled by operating a scenario program in which a scenario for dynamically changing playback is described.

  The BD-J module 33 configures a BD-J title that is played back when the BD-J application 39 controls using a Java (registered trademark) virtual machine.

  The BD-ROM resident system software layer 34 receives the contents of the user operation from the resident application 35 and determines whether or not the operation can be accepted. If so, the HDMV module 32 or the BD-J depends on the type of the title being reproduced. It is determined which of the modules 33 is notified.

  The resident application 35 provides a graphic interface or the like to receive a user operation and notifies the BD-ROM resident system software layer 34.

  The binding unit data area 36 can be accessed by the BD-J application 39 using a Java (registered trademark) IO package. Therefore, data is written in the binding unit data area 36 in the BD-J title mode.

  Next, a general sequence when the BD-J application 39 constructs a virtual package will be described with reference to FIG.

  When a BD-ROM disc (disc 38 in FIG. 3) is inserted into the optical disc playback apparatus 10, the first play title is played back. After starting the playback of the first play title, the BD-J module 33 confirms the BD-ROM Profile of the optical disc playback apparatus 10 (step S10). If the profile is a virtual package construction target, the process proceeds to the next step S11. In the case of Profile 1 Version 1.0 that does not construct a virtual package, the title is reproduced with the disc package.

  In step S11, the type of the current package is determined, and if it is already a virtual package, it is not necessary to construct the virtual package again, so the title is reproduced as it is. If it is a disc package, the process proceeds to step S12.

  In step S <b> 12, the BD-J module 33 confirms the level of the binding unit data area 36. This level represents the reading speed of the binding unit data area, but there is also a level assuming that the removable medium 12 is not loaded in the optical disc playback apparatus 10, that is, the binding unit data area 36 does not exist. When the reading speed of the binding unit data area 36 is not sufficient or when the binding unit data area 36 does not exist, the BD-J application 39 displays an error to the user and plays the title with the disc package.

  If it is determined in step S12 that the level is appropriate, it is determined whether or not data necessary for reproduction with the virtual package already exists in the binding unit data area 36 (step S13). If the desired data is already in the binding unit data area 36, a virtual package is constructed and reproduced as a virtual package (step S18). When there is no desired data in the binding unit data area 36, the process proceeds to step S14.

  In step S14, the capacity of the binding unit data area 36 is confirmed, and the capacity of data to be written is compared with the free capacity to determine whether the capacity is sufficient. If it is determined that there is not enough free space, an error is displayed to the user and playback is performed as a disc package. If the free space is sufficient, data is written to the binding unit data area 36 in step S15.

As described above, the data written in the binding unit data area 36 can be data downloaded from the WWW server 14 or data in the disk 38. In step S16, it is confirmed whether or not the data has been successfully written to the binding unit data area 36. If successful, a virtual package is constructed (step S18) and reproduced as a virtual package. If it fails, an error message indicating that writing has failed is displayed to the user (step S17), and the disc package is played back. The above is the flow of processing for constructing a virtual package.

  Next, a conventional process when the removable medium 12 is loaded in the optical disc playback apparatus 10 will be described.

  The resident application 35 in FIG. 3 needs to notify the BD-J module 33 of the storage level to be confirmed by the BD-J application 39 in step S12 in FIG. FIG. 5 shows a normal sequence such as a BD playback device used in the home. In step S50, the BD-J module 33 is notified of the reading performance of the removable medium 12 loaded in the optical disc playback apparatus 10.

  In the first embodiment, it is determined whether there is data other than data necessary for constructing a virtual package on the removable medium 12 loaded in the optical disc reproducing apparatus 10, that is, whether there is data uniquely written by the user of the removable medium 12. Check. At that time, the sequence of FIG. 5 changes as shown in FIG.

  After the removable medium 12 is loaded into the optical disc playback apparatus 10, the resident application 35 checks the contents of the removable medium 12 in step S60. Since the data necessary for constructing the virtual package is written in a specific directory, when there is data other than this or a file other than this specific directory on the removable medium 12, there is data written by the user. judge. If it is determined that there is no data stored by the user on the removable medium 12, the process proceeds to step S61. This is the same process as step S50 of FIG.

  If there is data stored by the user on the removable medium 12, the process proceeds from step S60 to step S62, and the resident application 35 not only notifies the BD-J module 33 of the storage level but also by the BD-J application 39. A request is made to limit data writing to the binding unit data area 36. Note that the BD-J module 33 notifies the resident application 35 that writing to the binding unit data area 36 is performed when there is a write request from the BD-J application 39 in the sequence of FIG. You may make it do. This writing applies not only to actually writing a file but also to all operations related to creation, change, and update of file information such as file creation, directory creation, and file name change. By performing write control to the binding unit data area 36 for each write request in this way, when a virtual package once constructed is played back, no write request is made, so that user data exists in the removable medium 12. Even so, it is possible to replay a previously built virtual package.

  In the first embodiment, when the BD-ROM 11 is reproduced, the BD-J module 33 determines the request of the BD-J application 39, notifies the resident application 35 of the request, and responds by the response of the resident application 35. The BD-J application 39 is controlled. It is also epoch-making in that the operation of the BD-J application 39 is controlled using the user's determination result, which is convenient for the user.

  Next, in step S15 of FIG. 4, the BD-J application 39 writes data in the binding unit data area 36. This instruction is issued via the BD-J module 33. FIG. 7 shows an operation sequence of the BD-J module 33 at this time.

The BD-J module 33 receives the resident application 35 in step S62 of FIG.
When the restriction on writing to the binding unit data area 36 is received, it is determined whether or not the writing restriction is notified from the resident application 35 in step S70. When the resident application 35 has a write restriction, the BD-J application 39 notifies that there is a write request in step S71.

  In step S72, when a response is received from the resident application 35 and writing is permitted, data is written in the binding unit data area 36 in step S74. If the resident application 35 responds that the writing is not permitted, in step S73, the BD-J application 39 responds with a write request as an error.

  In step S71 in FIG. 7, the writing is notified from the BD-J module 33 to the resident application 35. The resident application 35 operates as shown in FIG.

  Upon receiving the notification of writing, in step S80, the user is notified that the data on the removable medium 12 may be erased by writing to the removable medium 12.

  An example of notification at this time is as shown in FIG. In the write request notification example of FIG. 9, the SD card is described, but this is applied to all removable media 12. The user selects whether to permit writing, and confirms this selection in step S81. When writing is permitted, the resident application 35 notifies the BD-J module 33 of writing permission. If writing is not permitted, writing suppression is notified to the BD-J module 33, and a display as shown in FIG. 10 is displayed to notify the user that writing to the removable medium 12 has not been performed in step S84.

  In the in-vehicle environment, since the driver is prohibited from operating the screen while driving, it is assumed that reproduction is not performed while the notification panel of the write request notification example in FIG. 9 is displayed. Therefore, it is also possible to skip the processing of step S80 and step S81 and notify the BD-J module 33 of the write suppression of step S83. In addition, since the reproduction by the virtual package cannot be performed if it is surely suppressed, the resident application 35 determines whether writing to the BD-J module 33 is suppressed or permitted depending on the initial setting performed by the user. This function is also possible.

  The notification of suppression of writing to the BD-J module 33 is when the writing has failed in step S16 in FIG. 4, and an error message indicating that writing has failed is displayed by the BD-J application 39 in step S17. If the display of the write request notification example of FIG. 9 is not performed, only the message notifying that the writing failed to be displayed by the BD-J application 39 may cause user confusion. In S83, since the user data exists in the removable medium 12 and there is a possibility that the data may be erased, a display is made to inform that the writing is restricted. An example is shown in FIG.

(Second Embodiment)
The method of suppressing writing from the BD-J application 39 to the binding unit data area 36 in step S15 of FIG. 4 is the first embodiment. The second embodiment is a method of suppressing writing in step S14.

The resident application 35 confirms whether there is data written by the user on the removable medium 12 when the removable medium 12 is loaded. This is the same as in the first embodiment and is represented by the sequence of FIG.

  The sequence of the BD-J module 33 for suppressing writing when the capacity of the binding unit data area 36 is confirmed in order to write data from the BD-J application 39 to the binding unit data area 36 is shown in FIG. When the BD-J application 39 confirms the free capacity of the binding unit data area 36 in step S14 of FIG. 4, the BD-J module 33 confirms in step S120 whether the resident application 35 has a write restriction.

  If it is restricted, the BD-J application 39 notifies the resident application 35 that the capacity of the binding unit data area 36 has been confirmed in step S121.

  When the resident application 35 receives this notification, it goes through the same sequence of FIG. 8 as in the first embodiment and inquires of the user whether or not to permit writing. If the user suppresses writing, in step S123, the BD-J module 33 notifies the BD-J application 39 that the binding unit data area 36 has no capacity. On the contrary, if the user permits writing, the BD-J application 39 is notified of the free capacity of the binding unit data area 36. This is the sequence in FIG. 4 which is the same as the normal operation when constructing and playing back a virtual package. Similarly, when the write restriction is not performed, the process proceeds from step S120 to step S124, and the BD-J application 39 is notified of the free capacity of the removable medium 12. This also has the same function as a normal operation when a virtual package is constructed and played back.

  As described above, even when the free capacity of the binding unit data area 36 is confirmed from the BD-J application 39 in step S14 of FIG. 4, a method of avoiding data writing to the removable medium 12 can be realized. However, the BD-J application 39 does not necessarily write data immediately after confirming the capacity of the binding unit data area 36. Therefore, the first embodiment is more desirable in terms of preventing only writing, but also in the second embodiment, it is possible to prevent user data from being lost.

(Third embodiment)
In the third embodiment, writing to the binding unit data area 36 is controlled in step S12 in which the BD-J application 39 confirms the storage level in FIG.

  As in the first embodiment, when the removable medium 12 is loaded, the resident application 35 checks whether there is data recorded by the user on the removable medium 12 and notifies the BD-J module 33 of the data. This is the sequence of FIG.

In the third embodiment, when a storage level confirmation request is sent from the BD-J application 39 to the BD-J module 33, the BD-J module 33 performs the sequence process of FIG. In step S130, it is determined whether or not the resident application 35 suppresses writing in steps S61 and S62 of FIG. If the write restriction has been requested, the resident application 35 is notified in step S131 that a storage level confirmation request has been issued from the BD-J application 39. The operation of the resident application 35 at this time is shown in FIG. When the resident application 35 suppresses writing, the process proceeds from step S132 to step S133. Although the binding unit data area 36 exists on the removable medium 12, the BD-J application 39 is notified that there is no storage, which is an epoch-making content. By doing so, it is handled as an inappropriate level in step S12 of the sequence of FIG. 4, and writing to the binding unit data area 36 can be suppressed.

  If write suppression is not requested from the resident application 35 in step S130, or if the resident application 35 permits writing in step S132, the BD-J module 33 notifies the normal storage level in step S134, and FIG. Continue the write sequence.

  FIG. 14 is a diagram showing a sequence when the resident application 35 receives a notification that the storage level has been confirmed from the BD-J module 33. In step S140, the user is notified that data is to be written to the removable medium 12. A display example at this time is as shown in FIG. FIG. 15 is almost the same as FIG. 9 which is a display example of step S80 of FIG. 8 of the first embodiment, but FIG. 15 provides a user interface capable of exchanging the removable medium 12. If the removable medium 12 is replaced in the third embodiment, and the process returns to the sequence of FIG. 4, then the BD-J application 39 performs a confirmation process such as the free space. In the embodiment, even if the replacement of the removable medium 12 is permitted immediately before writing, the BD-J application 39 cannot check the free space and the like, and thus an unexpected error may occur when the capacity is insufficient. Therefore, in the first embodiment, the removable medium 12 is not replaced. Even in the first embodiment, if there is a function for notifying the BD-J module 33 of the configuration of the binding unit data area 36 necessary and sufficient to construct a virtual package such as a free capacity from the BD-J application 39, It is also possible to replace the removable medium 12.

  When the user selects writing in step S141, writing permission is notified to the BD-J module 33 in step S142. When the user selects write suppression in step S141, the BD-J module 33 is notified of write suppression, and the user is notified of the fact that writing has been suppressed. The display example for the user at this time is the same as FIG. 10 shown in the first embodiment.

  When the user selects replacement of the removable medium 12 in step S141, a display prompting the user to replace the removable medium 12 is performed in step S145. A display example at this time is shown in FIG. If the resident application 35 detects the removal / removal of the removable medium 12 in step S146, the notification displayed to the user is deleted in step S145, and the process proceeds to step S147, where the data originally written by the user in the removable medium 12 is stored. Check whether it exists. If it does not exist, the write permission is notified to the BD-J module 33 in step S142. If the user data exists in the exchangeable removable medium 12, the process returns to step S140 and asks the user whether or not writing can be performed again.

  Consider a case where the replacement of the removable medium 12 is not detected in step S146. There are cases where the user cancels the exchange or the exchange is not detected for a certain period of time. In these cases, it is determined that the writing is suppressed, and the process proceeds to step S143 to suppress the writing to the BD-J module 33. Notify you. Thereafter, in step S144, a display as shown in FIG. 17 indicating that the exchange has not been performed is displayed to the user to notify that the removable medium 12 is not written.

  As in the first embodiment, in the in-vehicle environment, the driver is prohibited from performing screen operations during driving. Therefore, when there is data uniquely written by the user on the removable medium 12, it is possible to easily create an initial setting item for whether or not to perform writing and operate according to the setting.

  As described above, the optical disc playback apparatus according to the present invention has an effect of suppressing writing on a removable medium, and is useful as a Blu-ray disc playback apparatus.

10 Optical disk playback device 11 BD-ROM
DESCRIPTION OF SYMBOLS 12 Removable media 13 Television 14 WWW server 20 Disk 21 Pickup 22 Servo 23 Local storage 24 Network interface 25 Signal processing means 26 Playback means 30 BD-ROM player model layer 31 BD-ROM application environment layer 32 HDMV module 33 BD-J module 34 BD-ROM resident system software layer 35 resident application 36 binding unit data area 37 network 38 disk

Claims (5)

An optical disc playback apparatus for playing back an application on a first recording medium and a second recording medium in conjunction with a digital stream,
Either one of the first recording medium and the second recording medium is a removable medium that is removable from the optical disk playback device and does not have a journaling function in the file system ,
A BD-J application section that controls the construction and playback of a virtual package;
When the user data is confirmed on the removable medium, a resident application unit that notifies the BD-J application unit not to allow writing to the removable medium;
An optical disc playback apparatus having The resident application unit notifies the BD-J application unit that writing to the removable medium is not permitted whenever there is a write request to the removable medium from the BD-J application unit. 2. An optical disk reproducing apparatus according to 1. The resident application unit determines whether or not to permit writing to the removable medium according to user's initial setting or a user's selection every time there is a write request to the removable medium from the BD-J application unit. The optical disk reproducing apparatus according to claim 1. The resident application unit notifies the BD-J application unit of permission to write to the removable medium when a storage level confirmation request is received from the BD-J application unit. Item 4. The optical disk reproducing device according to Item 1. The resident application unit, the when the user data in the removable media to confirm that there was a notification for prompting the replacement of the removable media to the user, if there is no response from the subsequent predetermined time user, the BD-J application unit The optical disk reproducing apparatus according to claim 1, wherein a notification is made not to permit writing to the removable medium.

Images