JP2002251373A - Network system and network terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve a problem that it takes much time for displaying a screen when screen data which is frequently displayed does not exist in a screen display terminal since it waits for display data of the screen transmitted from a server. SOLUTION: The screen which is frequently used from the terminal or the server is previously registered in the cache of the terminal and the cache of display screen data is managed in a system where the registered screen is not deleted from the cache of the terminal. Thus, the screen which is frequently used is read from the cache of the terminal, the speed of the display of the screen is made fast and the traffic of a network is reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a screen display processing method at a terminal in a system including one or more terminals connected to a server via a network such as a local area network or a wide area network.

[0002]

2. Description of the Related Art Servers and terminals are connected via a network. The server responds to the request of the terminal by executing the application desired by the terminal and sending the result to each terminal. When each terminal receives an event from the keyboard or mouse, it sends the event to the server via the network. When the processing result for the event is received and the display of the screen changes, the display data is also received and displayed on its own screen. The server can transmit screen display data to each of a plurality of terminals.

Each terminal can display screen display data transmitted from a server on a display device connected to the terminal via a network. Also, each terminal has a cache in the main memory or auxiliary storage device of the terminal, and the display data of the screen can be stored in the cache in the main memory or auxiliary storage device of the terminal. The display data is managed by the server and the terminal. When the screen data to be displayed on the terminal stores the data to be displayed in the main memory or the auxiliary storage device of the terminal, the server does not transmit the display data of the screen to the terminal, and the terminal performs the main storage or the auxiliary storage of the terminal. The display data of the screen can be obtained from the cache in the device, and the screen can be displayed.

[0004]

In the above prior art, the terminal has no data in the terminal cache immediately after connecting to the server, and the terminal waits for display data of the screen transmitted from the server via the network. It takes time to display.

[0005] When the size of the cache in the main memory or the auxiliary storage device of the terminal is small, not only the problem immediately after the connection but also the frequently displayed screen may overflow from the cache. Once the data has overflowed from the cache, it takes time to display the screen because it waits for the screen display data transmitted from the server again.

When a predetermined screen is simultaneously displayed on a plurality of terminals by an application executed on a server, display data of the same screen is transmitted to the plurality of terminals only when the application is started. However, the processing on the server side is also redundant and wasteful.

[0007]

According to the present invention, by designating a screen to be stored in the terminal cache from the terminal, the designated screen data is stored in the cache in the main memory or the auxiliary storage device of the terminal. Immediately after the terminal has connected to the server, it is possible to obtain screen display data from the cache from the cache, shorten the display time of the terminal screen, and reduce the load on the local area network or wide area network. Can be.

[0008] Unlike screen data in which a screen specified by a terminal is stored in a normal cache, by always storing the screen in a cache, screen data frequently displayed for each terminal can be obtained regardless of the size of the terminal cache. It is possible to obtain from the cache, the display time of the terminal screen is reduced, and the load on the local area network or the wide area network can be reduced.

[0009] Also, by specifying a screen to be stored in the cache of the terminal from the server, even when the same screen is displayed on a plurality of terminals, the display time of the terminal screen is reduced, and the local area network or wide area is displayed. The load on the area network can be reduced.

In this specification, the cache on the terminal side is:
This is storage means for storing screen data, and is storage means including non-volatile storage means.

[0011]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a system configuration diagram of the present invention. Figure 1
, The server 101 and the terminal 108 are connected to the local area network or the wide area network 11.
3 is connected. The server 101 is an auxiliary storage device 10
6, the application 102 can be executed for each terminal by the operating system 103 executed on the server 101. Application 10
When Step 2 is executed, the screen data generation unit 104 generates screen data, and transfers the generated screen data to the screen data management unit 105. The screen data management unit 105 controls the terminal 10
It is determined whether or not the screen data acquired from the screen data generation unit 104 is present in the cache managed by the screen data management unit 111 of the eight terminals. The data is transmitted to the terminal 108 via the terminal 103. If the screen data is not in the cache, the screen data number and the screen data are transmitted to the terminal 108 via the operating system 103.

The terminal 108 does not necessarily need to have the auxiliary storage device 112. The terminal 108 receives a screen data number or screen data from the server 101 via the local area network or the wide area network 113 by the operating system 109 executed on the terminal 108. The screen data management unit 111 on the terminal 102 receives the screen data number or the screen data transmitted from the server 101 via the operating system 109, and when only the screen data number is received, the screen corresponding to the screen data number The data is acquired from the cache managed by the screen data management unit 111, passed to the screen data display unit 110, and
0 displays the screen data on the display device 107 connected to the terminal 108. When receiving the screen data number and the screen data, the screen data management unit 111 deletes the least recently used screen data from the cache managed by the screen data management unit 111, registers the received screen data in the cache, and displays the screen data display unit. The screen data display unit 110 displays the screen data on the display device 107 connected to the terminal 108. FIG. 2 is a configuration diagram of a cache used by the screen data management units 105 and 111 to manage screen data numbers, screen data, and screen registration settings to be described later.

FIG. 3, FIG. 4 and FIG. 5 show the processing flow of the present invention. The present invention will be described below with reference to FIG. 1 system configuration, FIG. 2 configuration diagram of cache, FIG. 3 processing flow of screen registration from terminal, FIG. 4 processing flow of screen registration from server, and FIG. 5 processing flow of screen data transmission. Processing of screen registration from a terminal, processing of screen registration from a server, and processing of screen data transmission will be described.

First, processing for registering a screen from a terminal will be described below.

From the terminal 108 to the screen data management unit 1 of the terminal
A screen registration process is issued 301 to 301. The screen data management unit 110 that has received the registration process transmits the screen data registration process to the cache to the server screen data management unit 105 via the operating system 109 of the terminal and the operating system 103 of the server 30.
2. Screen data management unit 10 of the server that has received the registration process
No. 5 sets 303 a “fixed” flag in the registration column of the cache storing the screen data to be registered.
The screen data management unit 105 of the server transmits to the screen data management unit 111 of the terminal a screen data number for setting a “fixed” flag in the registration column of the terminal cache 304. The screen data management unit 1 of the terminal that has received the screen data number for setting the “fixed” flag in the registration column of the terminal cache
11 sets 305 a "fixed" flag in the cache corresponding to the screen data number transmitted from the server.

Next, processing for registering a screen from the server will be described below.

The server 101 issues 401 a screen registration process to the screen data management unit 105 of the server. The screen data management unit 105 of the server that has received the registration processing sets a “fixed” flag 402 in the registration column of the cache storing the screen data to be registered. The screen data management unit 105 of the server transmits to the screen data management unit 111 of the terminal the screen data number and the screen data for setting the “fixed” flag in the registration column of the terminal cache 403. The screen data number that sets the “fixed” flag in the registration field of the terminal cache and the screen data management unit 111 of the terminal that has received the screen data register the screen data transmitted from the server in the cache and register the cache in the cache registration field. “Fixed”
404 is set.

Finally, a process for transmitting screen data from the server 101 to the terminal 108 will be described below. Terminal 10
8, when the application 102 is executed on the server 101 or the application 102 being operated on the server 101 is operated, the screen displayed on the terminal 108 changes 501. The screen data generation unit 104 of the server generates screen data t according to the change of the screen. 5
02. The screen data management unit 105 controls the screen data generation unit 1
Check whether the screen data generated by the server 04 is in a cache managed by the screen data management unit 105 of the server.
3. If there is screen data in the cache, the screen data number corresponding to the screen data generated by the screen data generation unit 104 is transmitted 504 to the terminal 108. The screen data management unit 111 of the terminal 108 includes the local area network or the wide area network 113 and the terminal 10
The screen data number is acquired via the operating system 109 of FIG. 8 and the screen data corresponding to the screen data number is acquired from the cache managed by the screen data management unit 111 506. On the other hand, if there is no screen data in the cache managed by the screen data management unit 105 of the server 101, the “registration” flag is not set in the registration column of the cache managed by the management unit 105 and the most recently used The screen data that does not exist is deleted from the cache, and the screen data newly generated by the screen data generation unit 104 is registered 505 in the cache. Screen data management unit 105 of server
Transmits the screen data and the screen data number to the screen data management module 111 of the terminal via the local area network or wide area network 113 and the operating system 109 of the terminal 108 (507). The screen data management unit 111 of the terminal deletes the least recently used screen data from the cache, and registers the screen data and the screen data number transmitted from the server in the cache 508. The screen data management unit 111 transfers 509 the screen data acquired from the cache or the server 101 to the screen data display unit. The screen display unit 110 of the terminal 108 displays the display device 1 connected to the terminal 108.
At 07, screen data is displayed.

[0020]

As described above, according to the present invention, when operating an application executed on a server from a terminal, screen data frequently displayed from the terminal or the server is registered in a cache of the terminal. By loading frequently displayed screen data from the device cache,
The screen can be displayed at a high speed, and the data transfer amount of the local area network or the wide area network can be suppressed.

Further, by registering screen data frequently displayed from the terminal or the server in the cache of the terminal and preventing the registered screen data from being lost from the cache, the screen can be displayed at a high speed when the terminal connects to the server for the first time. Can be displayed to prevent frequently used screens from being deleted from the cache.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is a configuration diagram of a screen data cache.

FIG. 3 is a processing flowchart of screen registration from a terminal.

FIG. 4 is a processing flowchart of screen registration from a server.

FIG. 5 is a processing flowchart of screen data transmission.

[Explanation of symbols]

Reference Signs List 101 server 102 application 103 server operating system 104 server screen data generation module 105 server screen data management module 106 auxiliary storage device 107 display device 108 terminal 109 terminal operating system 110 terminal screen data generation module 111 terminal screen data management module 112 auxiliary storage device 113 Local area network or wide area network

Claims (6)

[Claims] 1. A network terminal that executes application software on a server connected via a network to generate screen data, and receives and displays the generated screen data via a network. A network terminal, wherein predetermined screen data among generated screen data is stored in a storage unit of the terminal in advance, and the screen data is read out from the storage unit and displayed. 2. The network terminal according to claim 1, wherein, when said storage means is full of screen data received from said server by said storage means, screen data other than said predetermined screen data is erased and stored in a storage area. A network terminal characterized by securing the following. 3. A system comprising a server that executes application software to generate screen data, and a network terminal that receives and displays the generated screen data via a network, wherein a screen generated by the application software is provided. A network system, wherein predetermined screen data of data is stored in a storage unit of a terminal in advance, and the screen data is read out from the storage unit and displayed. 4. The network system according to claim 3, wherein said screen data other than said predetermined screen data is erased when said storage means is full with screen data received from said server by said storage means. Network system characterized by ensuring. 5. The network system according to claim 3, wherein the server holds information for specifying screen data held by the network terminal in advance, and transfers the screen data to the network terminal prior to transfer of the screen data. A network system that checks whether the image data is already stored, and sends the screen data to the network terminal if the screen data is not stored. 6. The network system according to claim 5, wherein when said network terminal already holds said screen data, an ID for specifying said screen data is sent to said network terminal. Network system.