JPH11203226A - Hypertext storage device and medium storing hypertext storage device control program - Google Patents

Abstract

(57) [Summary] In a hypertext system such as the Internet, hypertext data and its additional information can be stored in one file and reproduced. An interface unit that communicates with a server connected to a network and receives hypertext data stored in the server; a parsing unit that parses the hypertext data received by the interface unit; A display processing unit that displays the hypertext data parsed by the unit on a display device, and a hypertext data that is being displayed on the display device, a plurality of data related thereto, and additional information associated with the hypertext data. It is composed of a file management unit that stores data in one file area, and a control device that controls each unit.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention is applied to a personal computer or a portable information terminal device capable of communicating with a server connected to a network, and stores and manages hypertext data by transmitting / receiving hypertext data between the devices. The present invention relates to a device and a medium storing a hypertext storage device control program.

[0002]

2. Description of the Related Art In recent years, with the spread of the WWW (World Wide Web), documents and data distributed on a network can be obtained at hand. A link mechanism can be set up between these documents and data, and a user interface tool called a browser can easily follow this link interactively and distribute multiple links over a network. Documents can be referenced. This has the advantage that the creator of the document has the advantage that it is not necessary to integrate all the document data and that the entire document can be constructed simply by following the link, which is rapidly expanding.

For example, in a hypertext system represented by WWW, all information sources on a network are connected to each other in a link relationship, and an associated information network is formed. To access such hypertext, specify the target information source and file name on the network by URL, and obtain the specified file and the file that will be the element for configuring the page with it as the main. It is usual to use a browser that can do this.

[0004] The browser provides an interactive operation environment with the user, and receives a URL (uniform resource resource) from the user.
cator) and instructions to follow a link from a document, connect to the corresponding information source, analyze the components of the page, lay it out, and display it on a graphic display device. ing. In order to display the target information on such a device, it is necessary to connect online and link to a related page (AN
CHOR) must be specified one by one by the user and displayed in order.

[0005] Therefore, there is a demand for a function of once taking necessary information into a device from a network and displaying the contents in an offline environment. Many software and information browsing devices satisfying the requirement have been developed. I have. Also,
As an automatic patrol function, there is provided software for automatically acquiring a page specified by a user and related pages in the apparatus in advance, and displaying the data acquired in the apparatus offline by the user.

[0006] For example, Free Loader, Inc (January 15, 1996)
According to the data described in (1), a specified page on the WWW is automatically acquired by software running on a personal computer and stored on a hard disk storage device. Further, there is known software that can be automatically started at a designated time or classified into a number of pages in advance, and a user can acquire data only by specifying a classification item.

[0007] According to the document of BUGInc (August 28, 1996) (Nawari Yashiro's homepage), software running on a personal computer automatically sets a specified page at a specified time (start, end time). To get. You can specify the number of links of the page that can be acquired. There is known software that can specify a server name (not a file name) to follow a link.

Further, according to NEC materials (Internet access manager), a specified page can be automatically acquired at a specified time by software that also operates on a personal computer. You can set usage time and charge restrictions. There is known software that can register a plurality of connection destinations (telephone numbers) with priorities.

According to NEC documents (homepage scrapbook), software that operates on a personal computer can save only the front or a part of the displayed page information, but can display it on a browser. Software that can save a current Internet page is known.

Further, according to Japanese Patent Application Laid-Open No. 8-95960, a document editing apparatus capable of adding additional information to a document being edited without making any changes is provided. The additional information is independent of the document being edited. There is proposed a document editing device having a supplementary information adding function capable of processing a document.

According to Japanese Patent Laid-Open Publication No. Hei 8-137843, when one document is edited and referred to from a plurality of terminals, additional information is stored in association with the document, and editing and reference can be performed by the additional information. A different document sharing system has been proposed, which is configured to integrally manage sentences in different formats using titles and keywords of the sentences.

As described above, in a conventional browser or an information device having an automatic patrol function, page information of a currently displayed page or a designated page can be saved. In addition, some of them can save a page related from a designated page.

[0013]

However, it has not been possible to save information including user operation history information, setting information at the time of saving, and input information. Therefore, when trying to display the saved hypertext data,
The situation displayed before saving could not be reproduced. In particular, since the information input by the user is not stored, it is necessary to make a separate memo for the information once input.

The present invention has been made in consideration of the above circumstances. For example, in a hypertext system such as the Internet, it is possible to store and reproduce hypertext data and its additional information in one file. Provided is a medium storing a hypertext storage device and a hypertext storage device control program.

[0015]

According to the present invention, there is provided an interface unit for communicating with a server connected to a network and receiving hypertext data stored in the server, and parsing the hypertext data received by the interface unit. A parsing unit that performs parsing, a display processing unit that displays hypertext data parsed by the parsing unit on a display device, hypertext data being displayed on the display device, a plurality of data related thereto, and the hypertext data. A hypertext storage device, comprising: a file management unit that associates additional information with the file information in one file area of a storage device; and a control device that controls each of the units.

In the present invention, the interface unit, the control device, the syntax analysis unit, the display processing unit, and the file management unit are constituted by a microcomputer including a CPU, a ROM, a RAM, and an I / O port. In particular, the ROM functions as a program memory, and the RAM functions as a work memory. The interface unit further includes a modem, RS232C, and the like.

The storage device can be constituted by a floppy disk, hard disk, MD, EEPROM, or the like. The display device can be configured by a CRT display, an LCD (liquid crystal display), a plasma display, or the like.

According to the present invention, hypertext data and its additional information are stored in one file, and the hypertext data that can be reproduced and the additional information related thereto can be managed as one file. .

[0019] The control device may include:
The hypertext data stored in the file area and the additional information thereof are read, and the display processing unit creates display information based on the additional information and displays the hypertext data on the display device. You may comprise. According to the configuration, the hypertext data stored in the file can be displayed based on the additional information.

When the interface unit receives the hypertext data and the additional information from the server connected to the network, the control unit associates the hypertext data with the additional information with the file management unit and associates the file with the file. The hypertext data may be stored in an area, the display processing unit may generate display information based on the additional information, and display the hypertext data on the display device.

According to the configuration, the hypertext data and the additional information received from the server connected to the network are stored in a file, and the hypertext data stored in the file is displayed based on the additional information. it can. Therefore, the hypertext data stored in a certain device (server) can be reproduced in the same state by another device via a network.

[0022] The control device may include:
The additional information including the operation history information of the user may be stored in the file area in association with the hypertext data.

[0023] The control device may include:
Causing the display processing unit to read out the hypertext data stored in the file area and the operation history information thereof, in which the additional information including the operation history information of the user is stored in the file area in association with the hypertext. The display device may be configured to create display information based on the operation history information and display the text data on the display device.

According to the above configuration, the hypertext data can be stored in the file in association with the operation history information of the user, and as a result, the hypertext can be reproduced based on the operation history information of the user.

[0025] The control device may include:
The additional information including the user input form information may be stored in the file area in association with the hypertext data.

[0026] The control device may include:
Additional information consisting of user input form information is stored in the file area in association with hypertext,
The display processing unit is configured to read out the hypertext data and the input form information stored in the file area, create display information based on the input form information, and display the hypertext data on the display device. May be.

According to the above configuration, the hypertext data can be stored in the file in association with the input form information of the user, and as a result, the hypertext can be reproduced based on the input form information of the user.

[0028] The control device may include:
A plurality of pieces of additional information including user input form information may be stored in the file area in association with one piece of hypertext data.

[0029] The control device includes:
A plurality of pieces of additional information composed of user input form information are stored in the file area in association with one piece of hypertext data, and the display processing unit converts one piece of hypertext data into display information based on the plurality of pieces of input form information. You may comprise so that it may be separately produced and displayed on the said display device.

According to the above configuration, hypertext data can be individually reproduced for one hypertext data based on a plurality of input form information.

When the interface unit receives a request for transmitting the data stored in the file area from the destination server connected to the network,
The file management unit may be configured to read out the hypertext data and the additional information stored in the file area and output the hypertext data to the interface unit.

According to the above configuration, a certain device (server)
Can be reproduced in the same state on another device via a network. For example, since the data can be transferred off-line to the server connected to the network, the network connection time can be reduced. Further, since the transmitted hypertext data is stored as it is, it is easy to confirm the content, and at the same time, the input information is less likely to be erroneous.

[0033] The control device includes:
Additional information including server connection condition information, data acquisition condition information, and display condition information may be stored in the file area in association with hypertext data.

[0034] The control device includes:
The server connection condition information, additional information consisting of data acquisition condition information and display condition information are stored in the file area in association with the hypertext data, and the display processing unit causes the hypertext data stored in the file area to be stored in the file area. Additional information may be read, display information may be created based on the display condition information, and the hypertext data may be displayed on the display device.

According to the above configuration, the hypertext data can be stored in the file in association with the server connection condition information, the data acquisition condition information and the display condition information, and as a result, the server connection condition information and the data can be stored. The hypertext can be reproduced based on the acquisition condition information and the display condition information.

According to another aspect of the present invention, there is provided an interface unit for communicating with a server connected to a network and receiving hypertext data stored in the server, a storage device, and a display device. A medium storing a program for controlling a hypertext storage device by a computer, the computer causing the computer to parse the hypertext data received by the interface unit, and displaying the parsed hypertext data on a display device. A medium storing a hypertext storage device control program characterized in that additional information is associated with hypertext data therein and a plurality of data related thereto and the hypertext data and stored in one file area of a storage device. .

[0037]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail based on an embodiment shown in the drawings. Note that the present invention is not limited by this.

FIG. 1 is a block diagram showing a hardware configuration of a hypertext storage device according to one embodiment of the present invention. In FIG. 1, reference numeral 1 denotes C for executing all processing instructions.
1 shows a PU (control device). Reference numeral 2 denotes a program memory including a ROM, an EEPROM, and the like for storing a program to be executed by the CPU 1. Reference numeral 3 denotes a work memory including a RAM, an EEPROM, and the like for temporarily storing data being executed by the CPU 1. 4 is stored data,
1 shows a multi-part file (external storage device) including a floppy disk, a hard disk, and the like for storing history data, setting data, and the like.

Reference numeral 5 denotes a display device including a CRT display, an LCD (liquid crystal display), and the like for displaying the acquired hypertext data and the like. Reference numeral 6 denotes an input device including a keyboard, a mouse, a pen, and the like for performing data input and various instructions by a user.

Reference numeral 8 denotes a modem for acquiring communication data (hypertext data) by connecting to a network;
1 shows a network device (interface unit) configured by RS232C or the like. The network device 8 can communicate with various devices connected on the network via a network such as a telephone line or a LAN.

Reference numeral 7 denotes a floppy disk for caching communication data obtained via the network device 8,
3 shows a cache file (external storage device) configured by a hard disk or the like. Reference numeral 9 denotes a server connected to a network such as the Internet or a LAN. Reference numeral 12 denotes a bus for transferring data and addresses.

Reference numeral 10 denotes an external storage medium such as a memory card, a CD-ROM, an MD, or a floppy disk which stores a program for controlling the hypertext storage device of the present invention by a computer. Reference numeral 11 denotes a medium reading device that reads a control program of the hypertext storage device from the external storage medium 10 and installs the control program in the program memory 2, for example.

In FIG. 1, according to the present invention, an interface unit (8) for communicating with a server connected to a network and receiving hypertext data stored in the server, a storage device (4), and a display device (5) a hypertext storage device comprising a computer (1)
Medium (10) storing a program controlled by the computer (1), causing the computer (1) to parse the hypertext data received by the interface unit (8), and display the parsed hypertext data on the display device (5). ), And the hypertext data being displayed, the plurality of data related thereto, and the hypertext data are associated with additional information and stored in one file area of the storage device (4). A medium storing a program is provided.

FIG. 2 is a block diagram showing the software configuration of the hypertext storage device according to one embodiment of the present invention. In FIG. 2, each component of the software configuration will be described. The software configuration includes a main processor (CPU) that performs processing from data analysis to display.
1) a resource interface unit (network device 5) 22 for controlling resources such as networks and files and data to the main processor unit 21; and a multi-unit capable of integrating / managing a plurality of data objects into one file. And a data management unit (multi-part file manager) 23.

For example, when displaying data or storing acquired data, the main processor 21 issues a data acquisition request to the resource interface 22 and sequentially processes the data sent from the resource interface 22. Then, processing such as displaying or issuing a storage request to the multi-data management unit 23 is performed.

The resource interface unit 22 receives a data acquisition request from the main processor unit 21 and determines whether the data acquisition source is at the end of the network or in a local file, or whether the data is acquired from the multi-data management unit 23. Classify whether the request is an acquisition request, and connect to the corresponding module. If the source of the data is the destination of the network, it is checked whether the same data has already been taken into the cache file 7, or if the data is not in the cache, the cache file 7 is written.

The main processor unit 21 and the resource interface unit 22 are configured as separate processes in this embodiment. Thus, data transfer between the two can be realized by performing inter-process communication (of course, it may be configured as one process). The multi-data management unit 23 and the main processor unit 21 and the resource interface unit 22 may be realized as a library call, or may be implemented as a separate process like the communication between the main processor unit 21 and the resource interface 22. You may communicate. In the present embodiment, an example is shown in which the respective processes of the main processor unit 21 and the resource interface 22 are connected as libraries.

In the present invention, the hardware configuration as shown in FIG. 1 and the software configuration as shown in FIG. 2 are not necessarily required. In particular, a program corresponding to a multi-part file module and its support are provided. It can also work with software modules.

Next, the sub-module (sub-function unit) will be described. The main processor unit 21 includes the following sub-modules. Browser control unit 21a: resource interface unit 22
And a function of determining the type of data transmitted from the resource interface unit 22 and distributing the data to the corresponding module. In addition, the sub-module is a sub-module that controls registration / update to history data, acquisition of data from history data, and the like in cooperation with the history management unit 21b as necessary.

History management unit 21b: memory of history data /
This is a submodule that provides an interface for file management and registration, update, and readout. Page save control unit 21c: performs control of passing data that is being displayed or acquired from a network or the like to the multi-data management unit 23 for saving. For example, HTML (Hyper-Te
xt Mark-up Langage) To save the file, use HT
After the ML data is stored, the sub-module is a control module that also performs control such as storing an image contained therein.

Layout unit 21d: a sub-module for laying out data to be displayed on the screen, such as HTML data and image data, in the screen. HTML parser unit 21e: a sub-module that, when the acquired data is HTML, analyzes the data in detail based on a grammar rule using this parser, and passes the analysis result to the layout unit 21d and the page storage control unit 21c. Form management unit 21f: a sub-module that manages user input information to an area defined on a page called an input form.

URL management unit 21g: U of the page being processed
This is a sub-module that collectively manages URL information indicating RL (uniform resource locator) information, including images contained in the page and links to other pages. Image processing unit 21h: When the acquired data is image data, this module analyzes the image data and performs a display control to a position on the screen based on a command from the layout unit 21d. is there. Display processing unit 21i: a sub-module that displays on an actual LCD (liquid crystal display) or CRT display based on instructions from the layout unit 21d and the image processing unit 21. Condition setting management unit 21j: a submodule that manages display conditions, network access conditions, storage conditions, and the like set by various users.

The resource interface section 22 is composed of the following sub-modules. Network interface unit 22a: Analyzes a request from the main processor unit 21 and, if it is a request to a network, converts it into an appropriate request to each network and makes a request. If the request is interpreted as a request for a local file or a request for the multi-data management unit 23, the sub-modules call the corresponding modules and transfer the data.

Cache data management unit 22b: When the network interface unit 22a makes a request to an external network, it checks whether it is in the cache file 7, and if so, transfers the cache data and if it is not in the cache file 7, If the acquired data can be written to the cache file 7, the sub-module performs writing to the cache file 7. The cache data management unit 22b also checks the total memory capacity of the cache file 7, deletes old cache data, and the like.

Further, the multi-data management unit 23 of this embodiment
Is linked as a library to the main processor unit 21 and the resource interface unit 22 to provide various interfaces.

The functions supported by the multi-data management unit 23 include the following. Data writing function: Writes specified data to the multipart file 4. Data read function: Reads specified data from the multipart file 4. Data inquiry function: Respond to an inquiry as to whether or not there is specified data. Data index generation function: Generates list information of data included in the specified multipart file 4.

Next, an example of the format of data stored in the multi-data management section 23 will be described. The multi-data management unit 23 can store a number of data with its attributes and names in one physical file. FIG. 4 is a diagram showing an example of the format of the multipart file according to the present embodiment. As shown in FIG.
The multi-part file includes a file header section, a part section, and a file footer section, which are separated by data boundary symbols. In the file header section, a description of the file is described, and a data boundary symbol is also specified here (line (d) in the figure).

A single multi-part file can have a plurality of part parts. In the figure, the file is composed of two parts, part 1 and part 2. Each part is composed of a data header section and an actual data section. The data header section describes the data type, title, address (URL) of the original data, data size, and the like. The data itself is stored in the section.

According to the above-mentioned configuration, together with a plurality of data constituting one page and the data associated therewith, information relating to display on various display devices, various setting information such as history operation information, and the like, By saving input information etc. as one multipart file, management of the saved file can be facilitated, and at the same time, various information at the time of saving can be saved in association with the saved data. Therefore, when displaying the stored data, it is possible to set the display environment according to not only the data constituting the page but also the setting information at the time of storage.

FIG. 3 is a block diagram showing a software configuration having an automatic patrol function according to this embodiment. In FIG. 3, the basic software configuration is the same as the software configuration in FIG. In particular, the resource interface unit 22 and the multi-data management unit 23 have exactly the same configuration / operation. The automatic cruising main processor unit 24 performs data analysis and storage processing of the acquired data, and performs open control of data required next. In the automatic patrol function, the layout processing unit 21
d, the image processing unit 21h and the display processing unit 21i become unnecessary.

Hereinafter, only the sub-modules required for the automatic cruise function will be described. Automatic patrol control unit 24a: analyzes using an HTML parser 21e according to the type of acquired data, writes data to the multi-data management unit 23, and further controls opening of the next necessary data to the resource interface unit 22 Is a submodule that performs Tour list management unit 24b: manages a list of resources to be automatically visited, and in response to a request from the automatic tour control unit 24a,
This is a submodule that provides the next resource information to be acquired.

FIG. 5 is a flowchart showing the procedure of the data storage processing according to the present embodiment. In FIG. 5, step A1: a page to be stored is stored in page storage control unit 2
1c. URL is usually used to specify the page
Thus, the data as an information source can be specified even on a network such as the Internet or in a local information device.
For example, the following notation is performed as a URL.

(A) http: //server/dir/page.html (b) http: //server2/dir2/a.gif (c) file: //localhost/page2.html

In the above example, (a) indicates “server”
Means that page data (HTML data in this case) that can be specified by the path “/dir/page.html” of the host having the name “http” is acquired using the protocol “http”. Similarly, (b) indicates that data “/dir2/a.gif” (GIF image data in this case) of the host “server2” is acquired using the “http” protocol. In (c), the protocol "file" is specified, which indicates that this is a specification method for opening a normal file, and "localhos"
t ”, ie,“ / page ”in the user's own information device.
This means that HTML data that can be specified by the file name "2.html" is acquired.

There are various ways to specify the page to be saved depending on the environment of the information device.
If you want to save the page you are just displaying on the display device, the user specifies so (for example,
Menu selection operation, etc.), and the URL of the page to be stored is known on the display device.
L can be entered. In the software configuration having the automatic patrol function shown in FIG. 3, the patrol list management unit 24b
Is specified by the URL for saving the page.

Step A2: The page storage control section 21c once obtains additional information to be stored together with the stored page information from the corresponding module. Here, the additional information once stored is used for adding and storing the page information in step A12 after the storage of the page is completed.

According to the above-mentioned processing, additional information using the operation history information of the user leading to the storage can be obtained from the history management unit 21b. Further, the additional information using the input information to the input form on the user's page can be obtained by inquiring the form management unit 21f. The setting conditions to be stored when the automatic patrol function is executed can be obtained by inquiring of the condition setting management unit 21i.

Step A3: The URL information of the page to be stored is passed to the browser control unit 21a, and a request for data acquisition is made. Step A4: The browser control unit 21a makes such a U
In response to the RL Open process, a URL Open request is issued to the network interface unit 22. After issuing the request to the network interface unit 22, the browser control unit 21a waits for a notification from the network interface unit 22 until data is acquired.

Step A5: The network interface unit 22 performs a data acquisition process. The subroutine of this step will be described later with reference to the flowchart of FIG. Step A6: The browser control unit 21a receives a data acquisition notification from the network interface unit 22.

Step A7: The browser control unit 21a
The type of the acquired data is determined. Various data are obtained by the same processing in the steps up to this point. Among them, the HTML data includes URL information of related data constituting the page, and therefore, it is necessary to perform analysis. is there. Therefore, here, it is determined whether or not the data is HTML data. If the data is HTML data, the process proceeds to step A8; otherwise, the process proceeds to step A1.
Move to 0.

The determination as to whether or not the data is HTML data is because, as described above, the type of data including the page configuration information is determined to be HTML data. If the type of data to be described is specified, it is necessary to determine the type of the data. VRML data and the like are data types having the same meaning.

Step A8: For HTML data,
Analyze the data with an HTML parser. At step 9, the URL of other data constituting the page is registered in the URL management unit based on the analysis result of the HTML data. This is to obtain information from the URL management unit when the related data is further stored later.

Normally, image data and the like are considered as information included in the page, and when one page is stored, the data (HTML data or the like) which is the basis of the page is stored. However, if the acquired URL is related information to another page, there is no need to acquire it, except when saving it to the next page. In addition, even if image data or the like constituting a page can be set, for example, “do not save an image” by setting conditions at the time of saving, there is no need to save even an image. . These determinations are made in step A13.

Step A10: The acquired data is passed to the page storage control section 21c. Step A11: The page storage control section 21c passes the acquired data to the multi-data management section 23, and performs processing for storing the data in an external storage device such as the multi-part file 4.
The multi-data management unit 23 can store and manage a plurality of data passed for one physical file. A file storing a plurality of related data in the multi-data management unit 23 is a multi-part file.

Step A12: Page save control section 21c
Transfers the additional information secured in step A2 in the same module to the multi-data management unit 23 in association with the previously stored page information, and performs a storage process. The method of associating can be performed by notifying the fact that the information is additional information and the URL of the source data when the information is passed to the multi-data management unit 23. If the data to be stored is element data that constitutes a page such as image data, this additional information does not exist, and there is no need to perform the storage processing in this step.

Step A13: An inquiry is made to the URL management unit 21g to obtain the URL of the data to be obtained next. At this time, the URL of the image data is not acquired if the condition for not storing the image is set in consideration of the storage condition. When several pages including related pages are saved at a time, URLs that match conditions such as the number of pages and the related depth are acquired. UR to get
If there is L, repeat from step A3. If there is no URL to be acquired, the storage process ends.

FIG. 6 is a flowchart showing a procedure of a data acquisition process of the network interface unit according to the present embodiment. FIG. 6 is a subroutine of step A5 shown in FIG. 5, and from step A4 in FIG. 5 to step B1 in FIG.
Move to

Step B1: The network interface unit 22 receives a request for an open process specifying a URL. The network interface unit 22a usually includes
In a state where the series of processes has been completed, it is monitored whether or not a request for the open process has been received.

Step B2: Cache Data Management Unit 2
Inquire 2b of whether there is cache data corresponding to the specified URL. However, cache data may be ignored depending on a special URL, open request, or option specification. In this case, even if there is cache data, the processing is continued assuming that there is no cache data. If the cache data exists, the process proceeds to step B3; otherwise, the process proceeds to step B4.

Step B3: Cache data management unit 2
In step 2b, the cache data corresponding to the URL is read from the cache file. Step B4: Request data for the corresponding server on the network. Which server should make the request is determined by the cache data management unit 22b by interpreting the URL. If the URL is a request for data in the user's device (file:... In the above URL example), the file may be opened directly.

Step B5: If there is corresponding data on the server, the data is transmitted, so the data is received. Step B6: The cache file or data obtained from the network or the file is returned to the module that has transmitted the request to the network interface unit 22a, and the process proceeds to step A6 in FIG.

FIG. 7 is a flowchart showing the procedure of the processing for storing the additional information added to step A1 shown in FIG. In FIG. 7, C indicates a branch point, and D indicates a junction. The process moves from step A1 in FIG. 5 to step C1 in FIG. Step C1: Inquire of the multi-data management unit (multi-part file manager) 23 to check whether the URL of the page to be stored is already stored in the multi-part file (MPF) 4.

Step C2: As a result of the confirmation, if the data is not stored, the storage processing is continued as usual, and the process proceeds to step A2 in FIG. Step C3: If stored, the page itself does not need to be stored, so only the additional information is stored and the process proceeds to step A12 in FIG. By adding the processes C1 to C3 shown in the flowchart of FIG. 7, only a plurality of pieces of additional information (for example, user input information) can be saved by only saving one page data.

FIG. 8 is an explanatory diagram showing the process of storing the main body data in the multipart file according to the present embodiment. Via network data storage: [WWW] →
[Network interface unit] → [Prowser control unit] → [HTML parser] → [Page save control unit] →
[Multi-data management unit] → [Multi-part file] Via cache data storage processing: [Cache file] → [Cache data management unit] → [Network interface unit] → [Prowser control unit] → [HTML]
[Parser] → [Page Save Control Unit] → [Multi Data Management Unit] → [Multi Part File]

FIG. 9 is an explanatory diagram showing the process of storing the main body data and the history data in the multi-part file according to the present embodiment. The process of storing the network data and cache data in FIG. 9 is the same as in FIG. Via the history data saving process: [History management unit] → [Page storage control unit] → [Multi data management unit] → [Multipart file] is added to FIG.

FIG. 10 is a flowchart showing the procedure of the stored data display processing according to this embodiment. In FIG. 10, step E1: a page to be displayed is specified from the stored pages. Regarding the specification of the save page,
It is assumed that it can be specified by “URL” as in the page to be displayed on the network. For example, this can be achieved by providing the following URL specification rules.

The URL of the original page: http: //www/a/b.htm
l Saved multipart file name (Saved MPF name): / dir / f
ile Multi-part file server name (MPF server name): mpf-server → Designated URL of the saved page: x-mpf: // mpf-server / d
er / file / = URL = / http: //a/b.html

In the above example, the stored multi-part file is a file name managed by the multi-data management unit 23 and a plurality of data are stored in one file ('/ dir / file'). I have. In order to specify the data stored therein, the original URL may be specified after '/ = URL = /'.

In the above example, the stored data is' mpf-s
Although the URL is assumed to be read from another host named "erver '", it can be omitted if it is in the user's device. Furthermore, although the leading “x-mpf:” is tentatively determined for simplicity, it may be a URL rule that specifies an existing protocol such as “http”.

Further, in the above example, '/ = URL = /'
And specify the URL of the original page,
Other designation methods can be provided. For example, ID
If it can be identified by, for example, '/ = ID = /', an ID may be specified after this character.

Step E2: The URL specifying the storage page in this way is sent to the browser control unit 21a by the U
Perform RL Open. Since the specification of the storage page can be specified by the URL in the step E1, this step can be shared with the process of the normal page data display method. Step E3: The browser control section 21a transmits an open request for obtaining page data for the saved page to the network interface section 22a.

Step E4: The network interface unit 22a receives the open request from the browser control unit 21a, and performs data acquisition processing from the multi-data management unit 23 (see the flowchart in FIG. 11). Step E5: The browser control section 21a receives the data returned from the network interface section 22a.

Step E6: The browser control section 21a analyzes the received data and checks whether or not additional information corresponding to the page data is stored.
The confirmation result as to whether or not the additional information is stored is transmitted to the network interface unit 22a in step E4.
At the time of data acquisition from the multi-data management unit 23 in the above, the data is attached to the header of the data by the multi-data management unit 23.

By interpreting the head of the data, the browser control unit 21a can easily identify whether or not additional information for the data is stored. If it can be confirmed that there is additional information, step E7
If there is no additional information, normal display processing may be performed, and the flow shifts to step E9.

Step E7: A request to acquire additional information is transmitted from the browser control unit 21a to the network interface unit 22a, and the network interface unit 22a receives the request and transmits the additional information of the corresponding data from the multi-data management unit 23. get. At this time, the browser control unit 21a sends the information to the network interface unit 22a.
Request for additional information can be performed by open processing using a URL that can identify the additional information.

The URL of the additional information is added to the header information when the data is obtained first, whereby
Network interface unit 22a in step E7
Can be performed in the same manner as the processing for a normal open request as in step E4. Step E7 will be described later using the detailed flowchart of FIG. The URL indicating the additional information can take the following form, for example.

Example of URL for obtaining additional information: x-mpf: // mpf-server / dir / file / = ID = / 100 In the above example, '/ dir / fil of the server named' mpf-server '
The ID included in the multi-file “e” indicates data “100”. If 'mpf-server' is omitted, it refers to data in the user's own device that does not go through the network. In this way, the URL can be reflected on the display even through the network.

Step E8: The acquired additional information is received by the browser control unit 21a and registered in the corresponding module.
Thus, the stored additional information can be reflected on the display for the data to be displayed. In this case, the module to which the additional information is passed is distinguished by the type of the additional information. If the additional information is user's history data, the operation history can be reproduced by setting the acquired additional information in the history management unit 21b.

If the additional information is user input information data, the input information can be reproduced by setting data in the form management section 21f which manages the input information. If the additional information is a connection condition, a data acquisition condition, or the like, the acquired information is set in the condition setting management unit 21i. As a result, the currently set conditions become valid for the page data to be displayed.

Also, a plurality of pieces of additional information may be set in the acquired page data. In such a case, all of the plurality of pieces of additional information are acquired in this step E8, and each is set in the corresponding module. This relates to a reproduction method in a case where a plurality of pieces of user input information are stored. In this case, the history management unit 21b is used to make it appear as a plurality of pages. That is, the history management unit 21b manages the reference history of the page together with the operation history of the user.

Therefore, as many times as the number of stored input information, the same page is first registered in the history management unit 21b as if the same page has been referred to a plurality of times. sign up. When pages are sequentially referred to by the history management unit 21b, input information registered in the form management unit 21f from there is the same page when displayed from the history management unit 21b, but the information is separately stored. It can be set and processed as if multiple pages had been saved.

Step E9: The data to be displayed is HTML
Determine whether it is data. If it is HTML data,
This is because it is necessary to interpret HTML. If H
If it is TML data, the process proceeds to step E10; otherwise, the process proceeds to step E12.

Step E10: acquired data HTML
Therefore, the HTML parser 21e performs an HTML analysis process. The analysis process analyzes the contents of description according to HTML grammar, and analyzes what characters are displayed in what layout, and whether images and link information to other pages are included. It is.

Step E11: If it is determined by the HTML analysis processing that an image or link information is included in the HTML, it is registered in the URL management unit 21g. Step E12: As processing when the data is not HTML data, it is determined whether or not the data is image data. This is because it is necessary to perform special processing on the image data in the image processing unit 21h.

Step E13: If the acquired data is image data, it is read out and
At h, the image data is analyzed. Here, various formats of the image data are interpreted and developed into a format that can be displayed. For example, there are various formats such as GIF and JPEG as formats, and it is necessary to perform expansion processing according to each format.

Step E14: HTML, image, or other data to be displayed is received, and a process for laying out (arranging) the data correctly in the display frame of one page is performed. Step E15: The layout result is displayed on the actual display device 5. Step E16: When one piece of data is displayed in this way, another object data constituting the same one page is obtained next, and there is no next data to perform the display processing together. To the URL management unit 21g.

The URL management unit 21g checks whether there are any other elements that make up the page, such as images, except for those that make up another page, such as link information. Repeat from step E2. If there is no more URL, the display is completed.

By the above processing, a page can be displayed based on the additional condition. However, the layout / display processing in step E14 or step E15 cannot be started until the image data included in the page is obtained. In some cases. In this case, the layout / display is not performed during the HTML acquisition, and the layout / display processing is performed at the time of acquiring the next image data.

Next, the network interface unit 22a in steps E4 and E7 during the above processing is executed.
The processing in is described below. FIG. 11 is a flowchart illustrating a procedure of a process of acquiring stored data in the network interface unit according to the present embodiment. FIG. 11 shows a subroutine of steps E4 and E7 shown in FIG.
The process moves to step F1 of FIG.

Step F1: The URL request is received by the network interface unit 22a. Step F2: It is determined whether or not the URL Open request requests stored data from the multi-data management unit 23. This can be determined by, for example, looking at the description such as 'x-mpf' at the head of the URL. If the storage data is requested from the multi-data management unit 23, the process proceeds to step F3. Otherwise, the process proceeds to step F6 to perform a normal open process.

Step F3: Determine whether the request is a request to the multipart file manager of another host. When displaying a saved page on another host, the request must be sent to another host. Step F6: Here, normal open request processing is performed once, and the multi-data management unit 2
3 is requested. The process proceeds to step A6 in FIG.

Step F4: The corresponding data is read from the multi-data management section 23. Reading can be performed by specifying a multi-file name and ID specified in the URL, a URL name before saving, and the like. Step F5: If the corresponding data can be read out by the multi-data management unit 23, the data is returned to the request destination. The process moves to step E5 or E8 in FIG.
The acquisition process in the network interface unit 22a can be performed without changing a request for normal page data or a request for additional information.

FIG. 12 is an explanatory diagram showing a process of displaying data stored in a multi-part file according to this embodiment. In FIG. 12, via the storage data display processing: [Multipart file] → [Multidata management unit] → [Network interface unit] → [Prowser control unit] → [HTML parser] → [Layout processing unit] → [Display Processing unit] → [Display device]

FIG. 13 is an explanatory diagram showing a process of displaying data stored in a multipart file and a process of reading history data according to the present embodiment. The process of displaying the stored data in FIG. 13 is the same as in FIG. Via reading history data: [Multipart file] → [Multidata management unit] → [Network interface unit] → [Prowser control unit] → [History management unit]
Is added to FIG.

FIG. 14 is an explanatory diagram showing the process of displaying the data stored in the server on the network and the history data according to the present embodiment. As shown in FIG. 14, display data and history data stored in a multi-part file on another information device (server) are read out via a network and displayed on a display device. Via the stored data display process: [Multipart file] → [Multidata management unit] → [Server] → [Network interface unit] → [Prowser control unit] →
[HTML parser] → [Layout processing unit] → [Display processing unit] → [Display device] Via display processing of history data:
[Multipart file] → [Multidata management unit] →
[Server] → [Network interface] →
[Prowser control unit] → [History management unit]

FIG. 15 is a flowchart showing the procedure of the batch transmission processing of the additional information stored in the multi-part file according to the present embodiment. User input information is stored as additional information in the saved page data, and the additional information is subjected to batch automatic transmission processing to the transmission destination. Step G1: After the display processing of the stored data in FIG. 10 is completed, it is determined whether or not to perform the batch automatic transmission processing of the stored additional information. This only requires, for example, determining whether or not such a mode has been set in advance. If the automatic transmission is not to be performed, the process ends.

Step G2: It is determined whether or not user input information has been set. If the user input information has not been set, there is no transmission information, and the process proceeds to the next page (step G5). Step G3: Further, it is determined whether or not the transmission destination is set. If the transmission destination has not been set, transmission is not possible, so the flow shifts to step G5.

Step G4: Since there is information to be automatically transmitted, it is necessary to arrange the information in a format that can be transmitted to the server. The user input information is formed into transmission information by the form management unit, and information specified to the page is added from the page information, and transmission processing is performed. The transmission process can be realized by opening the URL to the transmission destination with the formatted information, similarly to the normal data acquisition process. This is the same as the procedure of the display processing. When transmission is complete,
Next, the process proceeds to the next page.

Step G5: It is determined whether there is another saved page. If there is a stored page, the process proceeds to step G2 to perform the transmission process repeatedly. If there are no more pages to save, the process ends.

According to the above processing, the user's input information can be input to the stored data. Therefore, the information input in the offline state is stored, and the information is transferred to the connection destination on the network at a stretch online. Therefore, the network connection time can be shortened, the input information is less likely to be erroneous, and the transmitted data is stored as it is, so that the contents can be easily confirmed.

[0121]

According to the present invention, in a hypertext system such as the Internet, hypertext data and its additional information can be stored in one file and reproduced.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a hardware configuration of a hypertext storage device according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating a software configuration of a hypertext storage device according to an embodiment of the present invention.

FIG. 3 is a block diagram illustrating a software configuration having an automatic patrol function according to the embodiment;

FIG. 4 is a diagram illustrating an example of a format of a multipart file according to the embodiment.

FIG. 5 is a flowchart illustrating a procedure of a data saving process according to the embodiment;

FIG. 6 is a flowchart illustrating a procedure of a data acquisition process of the network interface unit according to the embodiment.

FIG. 7 is a flowchart illustrating a procedure of a storage process of additional information added to step A1 illustrated in FIG. 5;

FIG. 8 is an explanatory diagram showing a process of storing main body data in a multipart file according to the embodiment.

FIG. 9 is an explanatory diagram showing a process of storing main data and history data in a multipart file according to the embodiment;

FIG. 10 is a flowchart illustrating a procedure of a stored data display process according to the embodiment;

FIG. 11 is a flowchart illustrating a procedure of a process of acquiring stored data in a network interface unit according to the embodiment;

FIG. 12 is an explanatory diagram illustrating a process of displaying data stored in a multipart file according to the embodiment;

FIG. 13 is an explanatory diagram illustrating a process of displaying data stored in a multipart file and a process of reading history data according to the present embodiment.

FIG. 14 shows a server on a network according to the present embodiment.
FIG. 8 is an explanatory diagram showing the process of displaying data stored in the storage device and history data.

FIG. 15 is a flowchart illustrating a procedure of batch transmission processing of additional information stored in a multi-part file according to the embodiment.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 CPU 2 Program memory 3 Work memory 4 Multi-part file 5 Display device 6 Input device 7 Cache file 8 Network device 9 Server 10 External storage medium 11 Medium reading device 12 Bus 21 Main processor unit 21a Browser control unit 21b History management unit 21c Page Save control unit 21d Layout processing unit 21e HTML parser 21f Form management unit 21g URL management unit 21h Image processing unit 21i Display processing unit 21j Condition setting management unit 22 Resource interface unit 22a Network interface unit 22b Cache data management unit 23 Multi-data management unit 24 Automatic tour main processor 24a Automatic tour controller 24b Tour list manager

Claims (15)

[Claims] An interface unit for communicating with a server connected to a network and receiving hypertext data stored in the server; a parsing unit for parsing the hypertext data received by the interface unit; A display processing unit for displaying the hypertext data parsed by the analysis unit on a display device, a storage device for associating the hypertext data being displayed on the display device with a plurality of data related thereto and additional information to the hypertext data A hypertext storage device, comprising: a file management unit that stores the data in one file area; and a control device that controls each unit. 2. The control device causes the file management unit to read hypertext data stored in the file area and its additional information, and causes the display processing unit to read the hypertext data into the additional information. 2. The hypertext storage device according to claim 1, wherein display information is created based on the information and displayed on the display device. 3. The control device, when the interface unit receives the hypertext data and the additional information from a server connected to a network, associates the hypertext data with the additional information with the file management unit. 2. The hypertext storage device according to claim 1, wherein the hypertext data is stored in the file area, and the display processing unit creates display information based on the additional information and displays the hypertext data on the display device. . 4. The hypertext according to claim 1, wherein the control device causes the file management unit to store additional information including user operation history information in the file area in association with hypertext data. Storage device. 5. The control device causes the file management unit to store additional information including user operation history information in the file area in association with hypertext.
The display processing unit, read the hypertext data and its operation history information stored in the file area,
2. The hypertext storage device according to claim 1, wherein display information is created based on the operation history information, and the hypertext data is displayed on the display device. 6. The hypertext according to claim 1, wherein the control device causes the file management unit to store additional information including user input form information in the file area in association with hypertext data. Storage device. 7. The control device causes the file management unit to store additional information including user input form information in the file area in association with hypertext, and the display processing unit stores the additional information in the file area. 2. The hypertext storage device according to claim 1, wherein the hypertext data and the input form information thereof are read, and the hypertext data is displayed on the display device by creating display information based on the input form information. . 8. The file management device according to claim 1, wherein the control unit causes the file management unit to store a plurality of pieces of additional information including user input form information in the file area in association with one piece of hypertext data. A hypertext storage device as described. 9. The control device causes the file management unit to store a plurality of pieces of additional information including user input form information in the file area in association with one piece of hypertext data. 2. The hypertext storage device according to claim 1, wherein display information is individually created for one hypertext data based on a plurality of input form information and displayed on the display device. 10. The control device, when the interface unit receives a request for transmitting data stored in the file area from a destination server connected to a network, the file management unit transmits the request to the file area. 2. The hypertext storage device according to claim 1, wherein the stored hypertext data and the additional information are read out and output to the interface unit. 11. The control device may cause the file management unit to store additional information including connection condition information of a server, acquisition condition information of data, and display condition information in the file area in association with hypertext data. The hypertext storage device according to claim 1, wherein 12. The control device causes the file management unit to store additional information including server connection condition information, data acquisition condition information, and display condition information in the file area in association with hypertext data. The display processing unit reads the hypertext data stored in the file area and the additional information, creates display information based on the display condition information, and displays the hypertext data on the display device. The hypertext storage device according to claim 1, wherein 13. A program for controlling, by a computer, a hypertext storage device including an interface unit for communicating with a server connected to a network and receiving hypertext data stored in the server, a storage device, and a display device. Is a medium storing
The computer causes the computer to parse the hypertext data received by the interface unit, display the parsed hypertext data on a display device, and add additional information to the hypertext data being displayed and the multiple data and hypertext data related thereto. And storing the hypertext storage device control program in a file area of the storage device. 14. The computer reads the hypertext data and the additional information stored in the file area, creates display information in which the additional information is associated with the hypertext data, and sends the display information to the display device. 14. A medium storing the hypertext storage device control program according to claim 13, which is displayed. 15. When the interface unit receives hypertext data and its additional information from a server connected to a network, the computer stores the hypertext data and the additional information in the file area in association with each other, 14. The medium storing the hypertext storage device control program according to claim 13, wherein display information in which the additional information is associated with hypertext data is created and displayed on the display device.