JP2002244851A - Memory management device, memory management method, memory management program, and computer-readable recording medium recording the program - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To provide a memory management method capable of efficiently using a memory area while avoiding an overhead due to a copy process for generating a Java object. SOLUTION: A Java object executed by a Java application is stored, and a variable address memory area relocated by a Java virtual machine and data generated by a fixed address allocated to another program are stored. In a memory having a fixed address memory area, data generated in the fixed address memory area by another program is read as a Java object in response to a request from a Java application.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to the field of digital computer software, and more particularly, to a memory management device, a memory management method, and a memory for managing a memory storing an execution object executed by an object-oriented program. The present invention relates to a management program and a computer-readable recording medium on which the program is recorded.

[0002]

2. Description of the Related Art In recent years, with the development of computer technology, communication, and broadcasting technology, multimedia systems for providing various information media such as images, sounds, and moving images have become widespread. As such a multimedia system, an interactive digital television, a mobile terminal, a game device, and the like are provided on the market.

[0003] In a multimedia system, a large amount of data such as image, sound and moving image data transmitted through a communication medium such as the Internet is combined with an application in the multimedia system and is transmitted from a screen or a speaker. The video and audio are provided to the user. Therefore, a technology for efficiently processing a large amount of downloaded data is required for a multimedia system.

Recently, as a method of realizing efficient stream processing of a large amount of data such as image, audio and moving image data from a communication medium, a Java (registered trademark) which is an object-oriented language of Sun Microsystems, Inc. ) The environment is widespread.

[0005] Here, as an example of a general conventional technique related to an application constituted by a program described in Java (hereinafter referred to as a Java application), in response to a request from the Java application, a communication medium such as the Internet is used. The flow of processing from downloading image data to using it in a Java application will be described.

[0006] FIG. 10 shows that, in a multimedia environment, J
FIG. 11 is a functional block diagram of a general memory management device that downloads and executes image data in response to a request from an ava application.

[0007] The memory management device shown in FIG.
A Java application 11, a Java virtual machine program (hereinafter referred to as J)
avaVM) 12, a native program 13, an operating system (hereinafter, OS) 14, and an object storage unit 15.

[0008] The Java application 11 is a Java application.
It has the source code described in a, is compiled, and is converted into an intermediate code (hereinafter, byte code) which is a low-level pseudo code. By JavaVM12,
The bytecode is converted into a machine language that can be interpreted and executed by a computer (hereinafter referred to as native code) and executed. With this function of JavaVM12, a specific OS
An environment in which Java can be executed on any platform is realized without depending on the processor and the processor.

The Java VM 12 is an interpreter 12
a, object management unit 12b, JNI (JNI: Ja
va Native Interface) unit 12c. The interpreter unit 12a reads a bytecode representing one instruction from the Java application 11, converts the instruction into a native code, and executes it. The object management unit 12b generates data and source code (hereinafter, a Java object) used in the execution process of the Java application 11, and refers to the generated Java object.

Here, the Java object is a Java object.
a bytecode defined in the class of a
a Generated (instance) in the object storage unit 15 by the object management unit 12 b in response to a request from the application 11. The instantiated Java
a is the only execution object
It will be used in the execution process by the va application 11.

The JNI unit 12c includes an API (Application) composed of a set of instructions and functions for executing a native program 13 which is a native code described in C language or the like in response to a request from the Java application 11.
Program Interface). Also, the JNI unit 12
c is J in response to a request from the native program 13.
The ava application 11 can also be executed.

The object storage unit 15 is composed of a RAM or the like, and has a variable address memory area 15a serving as a work area for storing and generating Java objects.
And a fixed address memory area 15b serving as a work area for the native program 13 and the OS 14.

The variable address memory area 15a stores
Used in the function of collecting unnecessary Java objects by the aVM 12 (hereinafter, GC: Garbage Collection function), the address of stored data can be variably controlled. With this GC function, memory areas that are no longer used are aggregated to provide a continuous available memory area, and the memory can be used efficiently. On the other hand, the fixed address memory area 15b stores data used for execution processing of modules such as the native program 13 and the OS 14, and addresses are assigned to the respective programs under the control of the OS 14, and as in the variable address memory area 15a. No data relocation is performed.

As described above, the Java application 1
In the memory management in the execution environment of Java 1
In order to use the second GC function, the Java object is generally stored in a variable address memory area 15a on the memory, and is separated from an area in which data used by the native program 13 and the OS 14 are stored.

The native program 13 is a native code described in C language or the like. In response to a request from the Java application 11, the Internet,
The native program 13 is a module that enables real-time processing for downloading image data to the fixed address memory area 15b via a communication medium such as a satellite broadcast or a cable broadcast.

Next, the flow of processing when the downloaded image data is used in the execution processing of the Java application 11 will be described. Here, Java
The application 11 has a variable address memory area 15
a can only refer to the Java object stored in a.
It cannot be directly referenced as a va object.

In FIG. 10, the object storage unit 15
The Java objects OBA and OBB are stored in the variable address memory area 15a. Download data DA downloaded by the native program 13 is stored in the fixed address memory area 15b. In the example shown in FIG. 10, the Java object O
Only BA and OBB can be referred to by the Java application 11, and the download data DA cannot be referred to.

FIG. 11 shows that the download data DA is Ja.
FIG. 8 is a diagram illustrating a state of the object storage unit 15 when the object storage unit 15 can be referred to as a va object. First, Java
In response to a request from the application 11, the object management unit 12b secures a memory area corresponding to the download data DA in a free area of the variable address memory area 15a.

Next, the native program 13
The download data DA in the fixed address memory area 15b is transferred to the variable address memory area 15 via the I section 12c.
a as the download data DB. The download data DB copied to the variable memory address area 15a is finally converted into a Java object as a J object.
It will be used in the execution process of the ava application 11.

[0020]

As described above, when the data in the fixed address memory area 15b managed by the native program 13 is used in the execution processing of the Java application 11, the fixed address memory area 15b
It is necessary to copy the download data DA from the memory to the variable address memory area 15a. for that reason,
There is a possibility that the overhead due to the copy process occurs and the execution process is delayed. Also, during the execution of the copy process, it is necessary to secure the memory areas for the download data DA in each of the variable address memory area 15a as the copy destination and the fixed address memory area 15b as the copy source, and the memory area is efficiently used. In some cases it was not used.

Accordingly, an object of the present invention is to perform memory management that avoids the overhead due to copy processing for generating a Java object and that can use a memory area more efficiently.

[0022]

According to the present invention, a memory for storing an execution object executed by a virtual machine program for executing an object-oriented program composed of an object-oriented language is managed.

This memory is generated by a variable address memory area in which an execution object is stored and the execution object is rearranged by a virtual machine program, and another program constituted by a language other than the object-oriented language. A fixed address memory area in which data is stored.

When the present invention is embodied as a memory management device, the memory management device includes a generating unit and a reading unit. The generating means generates management information for the object-oriented program to read data in response to a request from the object-oriented program. The reading means reads the data generated in the fixed address memory area according to the management information generated by the generating means.

In some cases, the memory management device is provided with communication means for receiving data in a fixed address memory area of the memory. In this case, the data generated by another program is data received using the communication unit. Further, the generation unit generates management information for the object-oriented program to read data received using the communication unit.

Further, the memory management device may include a detection unit, a type determination unit, a deletion request storage unit, a deletion determination unit, and a deletion unit. After the execution of the object-oriented program, the detecting means detects the data requested to be deleted in response to the deletion request from the object-oriented program. The type determining means determines whether the data detected by the detecting means is stored in the variable address memory area or the fixed address memory area. The deletion request storage means, when the type determination means determines that the data detected by the detection means is stored in the fixed address memory area, sends a deletion request from the object-oriented program to the data detected by the detection means. Remember. The deletion determining means determines whether there is a deletion request from another program for the data in which the deletion request is stored in the deletion request storage means. And the deletion means,
When the deletion determination unit determines that there is a deletion request from another program for the data for which the deletion request is stored in the deletion request storage unit, the detected data and its management information are deleted.

Further, the memory management device may include a data determination unit that determines, in accordance with the data stored in the fixed address memory area, whether or not the execution object of the data is stored in the variable address memory area. Good. When the data determination unit determines that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area, the generation unit generates management information of the data.

The present invention may be implemented as a memory management method. In this memory management method, a generation step and a read step are performed. In the generation step,
Management information for the object-oriented program to read data is generated in response to a request from the object-oriented program. In the reading step, data generated in the fixed address memory area is read according to the management information generated in the generating step.

The memory management method may include a communication step of receiving data in a fixed address memory area of the memory. In this case, the data generated by the other program is the data received in the communication step. Further, in the generation step, management information for the object-oriented program to read the data received in the communication step is generated.

The memory management method may further comprise a detecting step,
A type determination step, a deletion request storage step, a deletion determination step, and a deletion step may be further included. In this case, in the detection step, after the execution processing of the object-oriented program, the data requested to be deleted is detected in response to a deletion request from the object-oriented program. Next, in the type determination step, it is determined whether the data detected in the detection step is stored in the variable address memory area or the fixed address memory area. In the deletion request storage step, when the type detection step determines that the data detected in the detection step is stored in the fixed address memory area, a deletion request from the object-oriented program for the data detected in the detection step is issued. It is memorized. Further, in the deletion request step, it is determined whether or not there is a deletion request from another program for the data in which the deletion request is stored in the deletion request storage step. And
In the deletion step, if the deletion determination step determines that there is a deletion request from another program for the data for which the deletion request has been stored in the deletion request storage step, the detected data and its management information are deleted. .

Further, the memory management method may include a data determining step of determining, in accordance with the data stored in the fixed address memory area, whether or not the execution object of the data is stored in the variable address memory area. is there. In the generation step, when the data determination unit determines that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area, management information of the data is generated.

The present invention may be embodied as a memory management program or a computer-readable recording medium on which the program is recorded.

This memory management program is a program for causing a computer to execute the above-described memory management method. When the memory management program is read by the computer, the software and the hardware resources cooperate to generate management information of data stored in the fixed address memory area and read data based on the management information. As a result, using a computer,
For example, a memory management device is constructed. Also, if the computer on which the memory management program is read operates,
A memory management method is established.

The memory management program may be distributed and sold by communication via a communication medium such as the Internet, or may be distributed and sold in a state recorded on a recording medium.

[0035]

Embodiments of the present invention will be described below in detail with reference to the drawings. (Embodiment 1) FIG. 1 is a functional block diagram showing a schematic configuration of a memory management device 100 according to Embodiment 1 of the present invention. In FIG. 1, the memory management device 100 includes, for example, a Java application storage unit 101 and a Java application storage unit 101.
VM 102, Java object table 103, J
An ava object management information storage unit 104, an object storage unit 105, a download management unit 106, a network control unit 107, a network device 108, and a fixed address memory providing unit 109 are provided.

The Java application storage unit 101 stores a Java application 111 and a class library 112. The Java application 111 is configured by a program described in Java which is an object-oriented language. The source code of the Java application 111 is converted into bytecode by being compiled. JavaVM1
02, this bytecode is transmitted. Further, the class library 112 is a library in which classes that collectively define the data structure inside the Java object are collected. Although the Java application storage unit 101 of the present embodiment is configured by a RAM (Random Access Memory), it may be realized by a ROM (Read Only Memory), a hard disk, or the like.

The Java VM 102 is, for example, Java
Interpreter unit 102a, Java object reference unit 102b, Java object generation unit for variable address memory (hereinafter, GOBV unit) 102c, Java object generation unit 102d for fixed address memory (GOBF)
Part).

[0038] The Java interpreter unit 102a
It reads and interprets one instruction at a time from the va application 111. Although the memory management device 100 employs an execution mechanism of an interpreter, the execution mechanism such as a compiler can be appropriately changed. Further, in response to a request from the Java application 111, the Java object reference unit 102b
Implements object read processing. GOBV part 1
02c, the GOBF unit 102d generates a Java object in the object storage unit 105 in response to a request from the Java application 111.

The Java object table 103 stores a pointer indicating the address of the Java object management information. Further, the Java object management information storage unit 104 stores Java object management information. The Java object management information includes a Java object in the object storage unit 105 and its J
This is information for managing data related to the class of the ava object. Information on the Java object is stored in, for example, Java in the object storage unit 105.
Pointer indicating address of object, data size. In addition, the information about the class
Information necessary for execution and reference by the application 111, such as a class name indicating the type of the ava object and an execution code.

The object storage unit 105 is constituted by a RAM or the like. The object storage unit 105 stores
a variable address memory area 105a serving as a work area for generating an ava object, and an OS (not shown)
And a fixed address memory 105b in which data managed by another application is stored.

In the variable address memory area 105a, J
Java is executed by the GOBV unit 102c of the avaVM 102.
a object is created. In addition, JavaVM10
The address of the Java object used and stored in the second GC function can be variably controlled.

On the other hand, fixed address memory area 105b
Stores data generated by each program under the control of an OS (not shown) and stores the data in the variable address memory area 1
Data relocation is not executed by the GC function of the Java VM 102 as in 05a.

The download management unit 106 is implemented by a program written in both a native language such as the C language that generates a platform-dependent native code and the Java language, and fixes data received via the Internet 300. Address memory area 10
Execute the memory management in 5b.

The network control unit 107 includes a modem and T
A (TA: Terminal Adapter) and the like to control the network device 108 and the Internet 30
Data is received from 0. Network control unit 1
07 is a program that requires real-time processing and is implemented in a native language such as the C language.

The fixed address memory provision unit 109
When data is received in response to a request from the va application 111, a memory area for storing data received from a free area of the fixed address memory area 105b is provided to the download management unit 106.

A central processing unit (CP not shown)
The control unit including U) implements a control operation executed by the memory management device 100 in cooperation with each circuit other than the CPU according to the program of the present invention. However, in the following, for convenience of explanation, the control operation related to the CPU is described as Ja.
It is assumed that a program such as a va application directly controls the program.

Next, Ja in the memory management device 100
The data configuration of the va object management will be specifically described with reference to the drawings. FIG. 2 shows an object table 103, a Java object management information storage unit 104,
FIG. 3 is a diagram illustrating a data configuration stored in an object storage unit 105.

In FIG. 2, OB1 is a GOBV unit 102.
c is a Java object generated in the variable address memory area 105a by c. OM1 is Ja
This is Java object management information of the va object OB1. The Java object information includes a pointer indicating the address of the Java object OB1 in the variable address memory area 105a and class information.
P1 is the Java of the Java object management information OM1.
a Pointer indicating an address in the object management information storage unit 104. By referring to the pointer P1 and the Java object management information OM1, the Java
The a application 111 can read the Java object OB1 via the Java object reference unit 102b and use it for execution processing.

Similarly, OB2 is generated by the GOBV unit 102c in the variable address memory area 105a.
va object. OM2 is Java object management information of the Java object OB2. The Java object management information includes a pointer indicating the address of the Java object OB2 in the variable address memory area 105a and class information. P2 is
It is a pointer indicating the address of the Java object management information OM2 in the Java object management information storage unit 104. By referring to the pointer P2 and the Java object management information OM2, the Java application 111 allows the Java object reference unit 102
b, the Java object OB2 can be read and used for execution processing.

D1 is the download management unit 106
Indicates data downloaded from the Internet 300 to the fixed address memory area 105b. Here, in the memory management apparatus 100, the fixed address memory area 105
b generated by the Java application 1
It can be read as a Java object in response to the request of No. 11. In the example shown in FIG. 2, Java object management information for reading the download data D1 is generated by the GOBF unit 102d. Thus, the download data D1 received in the fixed address memory area 105b from the Internet 300 is
The data can be read out as a Java object without going through the copy process to the variable address memory area 105a.

FIG. 3 is a diagram showing a state in which the Java object management information of the download data D1 shown in FIG. 2 is generated by the GOBF unit 102d. OMD
Indicates a pointer J indicating the address of the download data D1 in the fixed address memory area and J including the class information.
This is ava object management information. PD is Ja
This is a pointer indicating the address of the va object management information OMD in the Java object management information storage unit 104. By referring to the pointer PD and the Java object management information OMD, the Java application 111 can read out the download data D1 as a Java object via the Java object reference unit 102b and use it for execution processing.

Hereinafter, the flow of processing in the memory management device 100 according to the present embodiment from when the download data D1 is downloaded to when it is read as a Java object will be described. FIG. 4 is a diagram showing the flow of processing from receiving the download data D1 to reading the download data D1 as a Java object.

When the Java application 111 executes Java
The reception request is executed by specifying the identification information of the data to be downloaded to the download management unit 106 via the vaVM 102 (step S1). As identification information of data to be downloaded, an identification number of the data and a storage location (for example, URL: Uniform Resource Locater) are specified.

Next, the download management unit 106 issues a download request to the network control unit 107 by designating the identification number of the data to be downloaded and the address stored in the fixed address memory area 105b (step S2). ). The network control unit 107 connects to the data storage location on the Internet 300 specified in step S1 via the network device 108, and downloads the specified data. The downloaded data is download data D1 (FIG. 2).
Is stored in the fixed address memory area 105b at the address specified in step S2 (see step S2).
3).

After the download of the download data D1 is completed, the network control unit 107 notifies the download management unit 106 that the download has been completed (step S4). After the download is completed, a Java object generation process described later is executed by the Java VM 102 based on the download data D1 (step S5). After the Java object management information OMD is generated by the Java object generation processing of step S5, the download data D1 is
Java application 1 as a va object
11 and used for execution processing (step S6).

Next, the flow of the Java object generation process (step S5) will be described. FIG.
It is a flowchart which shows the flow of a object generation processing (step S5).

The download management unit 106 specifies the download data D1 in the fixed address memory area 105b and requests the GOBF unit 102d to generate a Java object based on the download data D1 (step S11). Next, download data D
1 is determined whether an address stored in the fixed address memory area 105b is designated (step S
12). If no address is specified (step S
12; No), the fixed address memory providing unit 109 provides a memory area of a predetermined capacity in the fixed address memory area 105b (step S13). FIG.
In the case of, since the address of the download data D1 has already been specified by the download management unit 106 in step S2, the process proceeds to step S14 without executing the process in step S13.

If the address of the download data D1 to be converted into a Java object is specified (step S12; Yes), the class information corresponding to the generated Java object is read from the class library 112 via the Java VM 102, It is stored as Java object management information OMD in the Java object management information storage unit 104 (step S1).
4).

Next, the pointer indicating the address of the download data D1 is set in the Java object management information OMD.
Is secured in the Java object management information storage unit 104 (step S15).
The pointer indicating the address of the download data D1 in the fixed address memory area 105b is stored as the Java object management information OMD in the secured memory area (Step S16).

Subsequently, the Java object management information O
The pointer PD indicating the address of the MD is stored in the Java object table 103 (step S17). Thereafter, the download data D1 is stored in the download management unit 1.
06 is passed to the Java application 111. Further, the download data D1 is read by the Java object reference unit 102b according to the Java object management information OMD, and is used in the execution processing of the Java application 111 (step S6 in FIG. 4).

As described above, the fixed address memory area 10
5b can be directly read as a Java object, so that the downloaded data can be stored in the variable address memory area 105a.
This eliminates the need for a copy process, and eliminates processing overhead and reduces the processing load on the memory management device.

During the execution of the copy process, the variable address memory area 105a and the fixed address memory area 105b
To create a Java object,
There is no need to secure one memory area, and the memory area can be used efficiently. This is particularly effective when a large amount of data such as audio and image data is downloaded and referred to by the Java application 111. When receiving large amounts of data, during the copy process,
This is because it is not necessary to secure a large capacity memory area in both the variable address memory area 105a and the fixed address memory area 105b. Needless to say, the present invention can be applied when downloading source code.

In FIG. 4, after the download is completed (step S3), the Ja of the download data is
va object management information is generated (step S
5) Although the download data is directly referenced from the Java application 111, the processing procedure can be changed to further improve the efficiency of the real-time processing. Specifically, even if the download of the download data is not completed, the data being downloaded can be referred to from the Java application 111.

For example, in FIG. 4, after the identification information of the data to be downloaded is designated by the Java application 111 (step S1), the process proceeds to step S1.
5 by the Java object generation process
What is necessary is just to make it generate object management information beforehand. As a result, the Java application 1
11 requests data in the fixed address memory area 105
The data being downloaded can be directly read out as a Java object even while downloading to b. As a result, the efficiency of real-time processing can be further improved as compared with the related art in which copying is performed from the fixed address memory area 105b to the variable address memory area 105a. In this case, in the Java object generation processing of FIG.
Since the address 05b is not designated (Step S12 in FIG. 5; No), the fixed address memory providing unit 109
As a result, a memory area in the fixed address memory area 105b is provided (step S1 in FIG. 5).
3). (Embodiment 2) Hereinafter, Embodiment 2 of the present invention will be described in detail with reference to the drawings.

In the memory management device according to the present embodiment, similarly to the memory management device 100 according to the first embodiment, the data in the fixed address
It is read in accordance with the va object management information. In addition, the execution process of the Java application ends, and the fixed address memory area 105b
When the data is no longer needed, the unnecessary data is deleted from the fixed address memory area. By deleting unnecessary data in the fixed address memory area 105b, it is possible to effectively secure a free memory area as a work area of the native program and the OS.

FIG. 6 is a functional block diagram showing a schematic configuration of a memory management device 200 according to the second embodiment of the present invention. The memory management device 200 according to the present embodiment includes, for example, a Java application storage unit 101 and a Java application storage unit 101.
VM 202, Java object table 103, J
An ava object management information storage unit 104, an object storage unit 105, a download management unit 106, a network control unit 107, a network device 108, and a fixed address memory providing unit 109 are provided. Java application storage unit 101, Java object table 103, Java object management information storage unit 1
04, the object storage unit 105, the download management unit 106, the network control unit 107, the network device 108, and the fixed address memory providing unit 109 have the same basic configuration and functions as those of the first embodiment. Detailed description is omitted.

Memory management device 200 according to the present embodiment
The difference between the configuration and the memory management device 100 according to the first embodiment is that the garbage processing unit 202
a.

The garbage processing unit 202a includes, for example, a non-reference object detecting unit 203, an object type determining unit 204, a variable address memory deleting unit 205, a fixed address memory deleting determining unit 206, and a fixed address memory deleting unit 207. ing. Garbage processing unit 202a
Implements a function of deleting unnecessary Java objects stored in the variable address memory area 105a or the fixed address memory area 105b in response to a request from the Java application 111 or the download management unit 106.

The non-reference object detection unit 203 detects an unnecessary object which is not referred to by the Java application 111 from the Java objects stored in the object storage unit 105.

The Java object type determination unit 204
Determines whether the unnecessary Java object detected by the non-reference object detection unit 203 is stored in the variable address memory area 105a or the fixed address memory area 105b.

The variable address memory deletion unit 205 deletes unnecessary Java objects stored in the variable address memory area 105a.

Fixed address memory deletion determination unit 206
Is an unnecessary Ja by the object type determination unit 204.
It is determined whether data corresponding to the va object is present in the fixed memory address area 105b, and whether there is a request from the download management unit 106 to delete unnecessary data corresponding to the Java object.

The fixed address memory deletion unit 207 deletes data corresponding to unnecessary Java objects stored in the fixed address memory area 105b according to the determination result of the fixed address memory deletion determination unit 206.

Hereinafter, the flow of processing for deleting unnecessary Java objects in the object storage unit 105 will be described. FIG. 7 shows unnecessary Java in the object storage unit 105.
13 is a flowchart illustrating a flow of processing for deleting an a object.

First, after the execution process of the Java application 111 ends, the reference to the Java object in the object storage unit 105 is removed (step S).
21). Subsequently, a request to delete an unnecessary Java object whose reference has been removed is sent to the Java application 1.
11 is executed by the Java VM 202 (step S
22).

Next, the non-reference object detection unit 203 of the Java VM 202 requests the J to be deleted.
An ava object is detected. Java detected
Whether the object belongs to the variable address memory area 105a or the fixed memory address area 105b is determined by the Java object type determination unit 204 (step S23). If the detected Java object belongs to the variable address memory area 105a,
The Java object detected by the variable address memory deletion unit 205 is deleted.

If it is determined in step S23 that the Java object requested to be deleted is based on the data stored in the fixed address memory area 105b,
The request to delete the data corresponding to the Java object is stored by the fixed address memory deletion determination unit 206 (step S24).

After that, the download management unit 106 executes a deletion request on the data in which the deletion request from the object type determination unit 204 is stored in step S24 (step S25). When the deletion request from the download management unit 106 is executed, the fixed address memory deletion determination unit 206 executes a deletion request of the data in which the deletion request is stored in step S24 to the fixed address deletion unit 207. If there is no deletion request from the download management unit 106, the fixed address memory deletion determination unit 206
, The deletion request to the fixed address deletion unit 207 is not executed.

That is, the Java application 111
Only when both the deletion request from the download management unit 106 and the deletion request from the download management unit 106 are executed, the deletion unit 207 for the fixed address memory
Unnecessary data 5b is deleted. As a result, unnecessary data is deleted only when all applications in the memory management device 200 are no longer referred to, so that data loss during application execution can be avoided, and memory sharing can be safely realized. . In addition,
The order of the deletion request from the Java application 111 and the deletion request from the download management unit 106 may be reversed.

Next, the fixed address memory deletion unit 207
Deletes the pointer of the Java object table 103 corresponding to the data to be deleted and the Java object management information stored in the Java object management information storage unit 104 (step S26).

Further, the fixed address memory deletion unit 207
Executes a request to the fixed address memory providing unit 109 to release the memory area in the fixed address memory area 105b in which the data to be deleted is stored (step S27). After receiving the deletion request, the fixed address memory providing unit 109 deletes the data to be deleted and releases the memory (step S28).

As described above, the memory management device 2
Unnecessary data in the fixed address memory area 105b is deleted only when the application is no longer referred to by all the applications in 00, so that data loss during application execution can be avoided and memory can be safely shared. You. (Embodiment 3) In the above-described Embodiment 1, in order for the Java application 111 to read data generated in the fixed address memory area 105b by the native program, the management information of the data is generated by the GOBF unit 102d. Was.

However, it is not necessary for the GOBF unit 102d to generate management information for all data generated in the fixed address memory area 105b by the native program. Depending on the specifications and functions of the OS and the device that manage the fixed address memory area 105b, it is preferable not to treat the data in the fixed address memory area 105b as a Java object.

For example, if the size of the data generated in the fixed address memory area 105b by the native program is small, even if the Java object of the data is generated in the variable address memory area 105a, the relocation of the Java object by the GC function is performed. The frequency is low, the processing overhead and the memory efficiency do not decrease, and the disadvantages of the processing are relatively small.
However, when the OS that manages the fixed address memory area 105b does not have the GC function, the small-sized data in the fixed address
When treated as a va object, small-sized data causes fragmentation in the fixed address memory area 105b.

For large-capacity data such as audio and image data, as described above, the Java
When the “a” object is generated in the variable address memory area 105a, overhead and memory efficiency are greatly reduced. Further, when the variable address memory area 105a is squeezed by a large amount of data, J
Relocation of ava objects frequently occurs, and the load on the system increases. Fixed address memory area 105b
Even if the size of the is small, if the expiration date of the data is short,
These disadvantages are more problematic than the compression of the fixed address memory area 105b. However,
If the size of the fixed address memory area 105b is small, and if the expiration date of the large-capacity data is long, the J
The ava object is stored in the variable address memory area 105a.
Is preferably generated.

Therefore, as shown in FIG. 8, a memory management device 400 according to the third embodiment includes a judgment unit 40 in addition to the configuration of the memory management device 100 according to the first embodiment.
1 is provided.

The determining unit 401 determines the J of the data according to the data stored in the fixed address memory area 105b.
The ava object is stored in the variable address memory area 105a.
It is determined whether or not the information is stored.

The criteria for the determination are the size, type, and expiration date of the data. These criteria are the size of the entire memory, the details thereof (each size of the variable address memory area 105a and the fixed address memory area 105b), the size of data to be downloaded, how to handle the data, and the OS that manages the fixed address memory area. It is determined by the function of

For example, when the data size is equal to or larger than a predetermined size, when the data expiration date is equal to or longer than a predetermined period, or when the data type represents AV data such as audio and video data, the Java object is a variable It is determined that the data is not stored in the memory area 105a. In this case, as described in the first embodiment, the management information of the data stored in the fixed address memory area 105b is generated by the GOBF unit 102d. Java
The object reference unit 102b reads out the data stored in the fixed address memory area 105b as a Java object according to the management information.

On the other hand, if the data size is smaller than a predetermined size, if the data expiration date is shorter than the predetermined period, or if the data type represents normal data other than AV data, the Java object is a variable address. It is determined that the data is stored in the memory area 105a. In this case, the Java object stored in the fixed address memory area 105b may be generated in the variable address memory area 105a as in the related art.

Memory management device 4 in the third embodiment
At 00, the flow of processing from when the download data D1 is downloaded to when it is read as a Java object is basically the same as that in the first embodiment described with reference to FIG.

However, in the memory management device 400 according to the third embodiment, the Java object generation processing in step S5 is partially different from that in the first embodiment. FIG. 9 is a flowchart illustrating a flow of a Java object generation process according to the third embodiment.

As shown in FIG. 9, the flow of the Java object generation processing in the third embodiment is the same as that in the first embodiment.
The difference from the case is that steps S40 and S41 are provided.

When a request to generate a Java object is made in step S11, the size, type, expiration date, and the like of the download data D1 stored in the fixed address memory area 105b are obtained.

In step S40, the determining unit 401 stores the data D1 in the variable address memory area 105a as a Java object based on the size, type, expiration date, etc. of the download data D1 stored in the fixed address memory area 105b. It is determined whether it is performed.

Only when it is determined that the download data D1 is not stored in the variable address memory area 105a as a Java object, the processes after step S12 are performed as in the first embodiment.

On the other hand, when it is determined in step S40 that the download data D1 is stored as a Java object in the variable address memory area 105a, a Java object of the download data D1 is generated in the variable address memory area 105a ( Step S41). Note that the processing in step S41 is the same as that in the related art, and a detailed description of this processing will be omitted.

As described above, in the third embodiment, the management information is stored only when it is determined that the data is not stored in the variable address memory area in accordance with the size of the data stored in the fixed address memory area. Is generated.
If the criterion is changed according to the specification of the OS or the device that manages the fixed address memory area, even if the data handled is various, the O that manages the fixed address memory area is changed
An optimal memory area for storing such data is selected according to the S and the specifications of the apparatus. As a result, memory management is optimized.

Although the present invention has been specifically described in each of the embodiments, the present invention is not limited to these embodiments, and may be appropriately modified without departing from the gist thereof. Of course.

Note that the memory management device according to the present invention generates Java objects based on data downloaded via the Internet 300. However, when a digital TV, a set-top box, a mobile phone, or the like is moved, It is also applicable to body terminals. For example, in a digital TV, the memory management device according to the present invention can also be applied to a digital TV receiver that can receive data superimposed on a carrier wave transmitted via a digital broadcast network. When the present invention is applied to a digital TV, a network device (see FIG. 1) may be configured with a digital broadcast receiving tuner to receive data.

The program of the present invention may be distributed and sold in a form such as being downloaded from a server connected via a communication medium such as the Internet to a memory or a hard disk drive of a client computer. In this case, when the program of the present invention is read by the client computer, the memory management device and the memory management method of the present invention are constructed using the computer. Furthermore, a mode in which a program or data stored in a memory or the like of another device is used via a communication medium may be adopted.

Further, the program of the present invention is a CD-RO
It may be stored in a recording medium such as M, FD, DVD or the like, and may be provided in a removable form with respect to a general-purpose computer. This makes it possible to easily distribute and sell the software product storing the program of the present invention independently of the device as a software product. By using this software using hardware such as a general-purpose computer and a general-purpose game device, the present invention can be easily implemented with these hardware.

[0103]

According to the present invention, in response to a request from an object-oriented program, management information for the object-oriented program to read data generated in a fixed address memory area by another program is generated. This eliminates the need to copy downloaded data to a memory area managed by an object-oriented language program as in the related art. Further, the processing overhead is eliminated, the processing load is reduced, and the memory area can be used efficiently.

When the execution of the Java application is completed and the data in the fixed address memory area becomes unnecessary, unnecessary data is deleted from the fixed address memory area. Effective free memory area can be secured.

Further, according to the data stored in the fixed address memory area, the management information is generated only when it is determined that the data is not stored in the variable address memory area. Optimal memory management is performed according to the situation.

[Brief description of the drawings]

FIG. 1 is a functional block diagram illustrating a schematic configuration of a memory management device according to a first embodiment of the present invention;

FIG. 2 is an object table according to the embodiment;
FIG. 3 is a diagram showing a data configuration stored in an object management information storage unit and an object storage unit;

FIG. 3 shows J of download data according to the embodiment.
Diagram showing a state in which ava object management information is generated

FIG. 4 is a diagram showing a flow of processing from reception of download data to reading of the download data as a Java object according to the embodiment;

FIG. 5 is a flowchart illustrating a flow of a Java object generation process according to the first embodiment.

FIG. 6 is a functional block diagram illustrating a schematic configuration of a memory management device according to a second embodiment of the present invention;

FIG. 7 is a flowchart of a processing flow for deleting unnecessary Java objects in the object storage unit according to the embodiment;

FIG. 8 is a functional block diagram illustrating a schematic configuration of a memory management device according to a third embodiment of the present invention;

FIG. 9 is a flowchart illustrating a flow of a Java object generation process according to the third embodiment.

FIG. 10 is a functional block diagram of a general memory management device that downloads and executes image data according to the related art.

FIG. 11 is a diagram showing a state of an object storage unit when download data can be referred to as a Java object.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 Memory management device 101 Java application storage unit 102 JavaVM 103 Java object table 104 Java object management information storage unit 105 Object storage unit 105a Variable address memory area 105b Fixed address memory area 106 Download management unit 107 Network control unit 108 Network device 109 Fixed address Memory providing unit 401 judgment unit

Claims (20)

[Claims] 1. A variable address memory in which an execution object executed by a virtual machine program executing an object-oriented program constituted by an object-oriented language is stored, and the execution object is rearranged by the virtual machine program. A memory management device that manages a memory having an area and a fixed address memory area in which data generated by another program configured in a language other than the object-oriented language is stored. Generating means for generating management information for the object-oriented program to read the generated data in response to a request from the server; generating the management information in the fixed address memory area in accordance with the management information generated by the generating means Read the saved data Memory management device characterized by comprising a means out. 2. The communication device according to claim 1, further comprising a communication unit configured to receive data in a fixed address memory area of the memory, wherein the data generated by the other program is data received using the communication unit. 2. The memory management device according to claim 1, wherein the memory management device generates management information for the object-oriented program to read data received using the communication unit. 3. A detecting means for detecting, in response to a deletion request from the object-oriented program, the data requested to be deleted after execution processing of the object-oriented program; and data detected by the detecting means. A type determining unit that determines whether the data is stored in the variable address memory area or the fixed address memory area; and a type determining unit that the data detected by the detecting unit is stored in the fixed address memory area. When the determination is made by the determination unit, a deletion request storage unit that stores a deletion request from the object-oriented program for the data detected by the detection unit; and a deletion request storage unit that stores the deletion request in the deletion request storage unit. Deletion determination means for determining whether there is a deletion request from another program; When the deletion determination unit determines that there is a deletion request from the other program for the data for which the deletion request is stored in the deletion request storage unit, the detected data and the management information of the data are deleted. 2. The memory management device according to claim 1, further comprising a deletion unit that performs the deletion. 4. A data determining means for determining whether an execution object of the data is stored in the variable address memory area in accordance with the data stored in the fixed address memory area, Wherein the data management information is generated when the data determination means determines that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area. 2. The memory management device according to 1. 5. The object-oriented program according to claim 1, wherein
The memory management device according to any one of claims 1 to 4, wherein the memory management device is configured by ava. 6. A variable address memory in which an execution object executed by a virtual machine program that executes an object-oriented program constituted by an object-oriented language is stored, and the execution object is rearranged by the virtual machine program. A memory management method for managing a memory having an area and a fixed address memory area in which data generated by another program configured in a language other than the object-oriented language is stored. Generating a management information for the object-oriented program to read the generated data in response to a request from the server, and according to the management information generated in the generating step,
A reading step of reading data generated in the fixed address memory area. 7. The method according to claim 1, further comprising: a communication step of receiving data in a fixed address memory area of the memory, wherein the data generated by the other program is data received in the communication step; 7. The memory management method according to claim 6, wherein management information for causing the object-oriented program to read the data received by the communication step is generated. 8. A detecting step for detecting, in response to a deletion request from the object-oriented program, the data requested to be deleted after the execution processing of the object-oriented program; and a data detected in the detecting step. Determining whether the data is stored in the variable address memory area or the fixed address memory area; and determining that the data detected in the detection step is stored in the fixed address memory area. When determined by the determination step, a deletion request storage step of storing a deletion request from the object-oriented program for the data detected in the detection step; and Is there a deletion request from another program? A deletion determination step of determining whether or not the deletion request is stored in the deletion request storage step; and if the deletion determination step determines that there is a deletion request from the other program, the detection is performed. 7. The memory management method according to claim 6, further comprising a deleting step of deleting the data and management information of the data. 9. A data determining step of determining whether an execution object of the data is stored in the variable address memory area in accordance with the data stored in the fixed address memory area, The data management information is generated when the data determination step determines that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area. The memory management method according to claim 6. 10. The memory management method according to claim 6, wherein the object-oriented program is configured by Java. 11. A variable address memory in which an execution object executed by a virtual machine program executing an object-oriented program constituted by an object-oriented language is stored, and the execution object is rearranged by the virtual machine program. A memory management program for managing a memory having an area and a fixed address memory area in which data generated by another program configured in a language other than the object-oriented language is stored. A generation step of generating management information for reading the generated data from the object-oriented program in response to a request from the directional program, and according to the management information generated in the generation step,
A memory management program for executing a memory management method including a reading step of reading data generated in the fixed address memory area. 12. The memory management method further includes a communication step of receiving data in a fixed address memory area of the memory, wherein the data generated by the other program is the data received in the communication step. 12. The memory management program according to claim 11, wherein in the generation step, management information for the object-oriented program to read data received in the communication step is generated. 13. The memory management method according to claim 1, wherein after the execution processing of the object-oriented program, in response to a deletion request from the object-oriented program, a detection step of detecting the data requested to be deleted, A type determining step of determining whether the data detected in the step is stored in the variable address memory area or the fixed address memory area; and storing the data detected in the detecting step in the fixed address memory area. When it is determined by the type determination step that the deletion has been performed, a deletion request storing step of storing a deletion request from the object-oriented program for the data detected in the detection step; The other program for stored data A deletion determination step of determining whether there is a deletion request from the program; and 12. The memory management program according to claim 11, further comprising: a deletion step of deleting the detected data and management information of the data when the determination is made. 14. The memory management method according to claim 1, further comprising, in accordance with the data stored in the fixed address memory area, a data determining step of determining whether an execution object of the data is stored in the variable address memory area. In the generating step, when the data determining step determines that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area, the management information of the data is generated. The memory management program according to claim 11, wherein 15. The object-oriented program according to claim 11, wherein the object-oriented program is composed of Java.
15. The memory management program according to any one of items 1 to 14. 16. A variable address memory in which an execution object executed by a virtual machine program that executes an object-oriented program constituted by an object-oriented language is stored, and the execution object is rearranged by the virtual machine program. A memory management program for managing a memory having an area and a fixed address memory area in which data generated by another program configured in a language other than the object-oriented language is stored. A generation step of generating management information for reading the generated data from the object-oriented program in response to a request from the directional program, and according to the management information generated in the generation step,
A computer-readable recording medium recording a memory management program for executing a memory management method including a reading step of reading data generated in the fixed address memory area. 17. The memory management method further includes a communication step of receiving data in a fixed address memory area of the memory, wherein the data generated by the other program is the data received in the communication step. 17. The computer readable recording medium according to claim 16, wherein the generation step generates management information for the object-oriented program to read data received by the communication step. recoding media. 18. The memory management method according to claim 1, further comprising: after the execution processing of the object-oriented program, detecting a deletion-requested data in response to a deletion request from the object-oriented program; A type determining step of determining whether the data detected in the step is stored in the variable address memory area or the fixed address memory area; and storing the data detected in the detecting step in the fixed address memory area. When it is determined by the type determination step that the deletion has been performed, a deletion request storing step of storing a deletion request from the object-oriented program for the data detected in the detection step; The other program for stored data A deletion determination step of determining whether there is a deletion request from the program; and 17. The computer-readable recording medium recording a memory management program according to claim 16, further comprising: a deletion step of deleting the detected data and management information of the data when the determination is made. 19. The memory management method according to claim 1, further comprising, in accordance with the data stored in the fixed address memory area, a data determining step of determining whether an execution object of the data is stored in the variable address memory area. In the generating step, when it is determined in the data determining step that the execution object of the data stored in the fixed address memory area is not stored in the variable address memory area, the management information of the data is generated. A computer-readable recording medium recording the memory management program according to claim 16. 20. The object-oriented program according to claim 16, wherein the object-oriented program is composed of Java.
20. A computer-readable recording medium on which the memory management program according to any one of claims to 19 is recorded.