JP2013105459A - Information management system and terminal device, and terminal device program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information management system and a terminal device which acquire a part of data in a Web page.SOLUTION: An information management system 1 is composed of a terminal device 30 which requests data of a Web page from a server side as a client side, and a server device 20 which returns the data of the Web page requested by the terminal device 30 as the server side. The server device 20 comprises a storage part 22 which stores element data and layout data of Web pages, and a schedule management server 80 which returns at least one of the element data and the layout data stored in the storage part 22 in response to the request from the terminal device 30. The terminal device 30 comprising a storage part 32 which separately stores the element data and the layout data acquired from the server device 20 acquires and displays the data of the Web page on the basis of data stored in the storage part 32 and data to be displayed according to an input instruction of a user.

Description

  The present invention relates to an information management system and a terminal device, and in particular, a terminal device having a touch panel display caches screen data acquired from a server into layout data and element data in a memory, thereby storing data at the time of caching. The present invention relates to an information management system, a terminal device, and a terminal device program that improve the efficiency of acquisition.

  A conventional terminal device manages user data such as a schedule received from a server as an item, and grasps whether or not the item is cached in the terminal device (see, for example, Patent Document 1).

  Some conventional terminal devices selectively store web page data received from a server in response to a user command (see, for example, Patent Document 2).

JP 2009-123047 A (paragraph [0014]) JP 2009-163748 A (paragraph [0030])

  However, the smallest unit of data to be cached is user data such as a schedule. For this reason, layout data and element data constituting data such as a schedule are not separated and cached.

  Further, even if Web page data is selectively stored, the entire Web page data is stored. Therefore, the layout data and the element data are not separately stored by dividing the data structure of the Web page data.

  Therefore, the terminal device has already cached the web page data from the server, and even if only a part of the web page data needs to be obtained, the terminal device obtains the entire data of the same web page again. There was a point.

  Therefore, an information management system, a terminal device, and a terminal device program that can acquire only a part of the data of the Web page have been desired.

  An information management system according to the present invention comprises a terminal device that requests Web page data from the server side as the client side, and a server device that returns Web page data requested from the terminal device as the server side. In the above, the server device stores in the first storage means, first storage means for storing element data forming elements of the Web page and layout data for determining an arrangement of the element data forming the Web page. Data management means for returning at least one of the element data and the layout data as data of the Web page in response to a request from the terminal device, and managing the data of the Web page, and the terminal device includes: The data of the Web page returned from the server device is converted into the element data. Based on second storage means for storing the layout data separately, data on the Web page stored in the second storage means, and data on the Web page displayed in response to a user input command, the user An information processing unit that determines whether or not to request data of the Web page to be displayed in response to an input command, and when the data processing unit does not request data of the Web page, the data is stored in the second storage unit From the element data that has been stored and the layout data that has been stored in the second storage means, the data that forms the Web page to be displayed in response to the user's input command is selected and displayed. In the case of requesting data, the element data among the data of the Web page displayed by the user input command And when at least one of the layout data is not stored in the second storage means, the data not stored in the second storage means is acquired from the server device, the data acquired from the server device, The web page is displayed based on the data stored in the second storage means.

  The terminal device according to the present invention is a terminal device that requests web page data to the server side as a client side, and the web page data acquired after requesting the web page data to the server side is used as an element of the web page. Is stored separately into element data forming the web page and layout data defining the arrangement of the element data forming the web page, the web page data stored in the storage unit, and a user input command An information processing unit that determines whether to request the data of the Web page to be displayed based on the user input command based on the data of the Web page to be displayed, and the information processing unit includes the Web page If the data is not requested, the element data stored in the storage means and the storage means When the data for forming the web page to be displayed is selected and displayed from the stored layout data in response to an input command of the user and the data of the web page is requested, the user input When at least one of the element data and the layout data is not stored in the storage means among the data of the Web page displayed by the command, the data not stored in the storage means is acquired from the server side, The Web page is displayed based on the data acquired from the server side and the data stored in the storage means.

  The terminal device program of the present invention is a terminal device program that operates on a terminal device that requests web page data from the server side as a client side, and the web page data acquired after requesting the web page data from the server side Is stored in storage means separately into element data forming the elements of the Web page and layout data defining the arrangement of the element data forming the Web page, and the storage unit stored in the storage means An information processing unit for determining whether to request the data of the web page to be displayed by the user's input command based on the data of the web page and the data of the web page to be displayed by the user's input command; Provided that the information processing unit does not request the data of the Web page. From the element data stored in the means and the layout data stored in the storage means, the data for forming the Web page to be displayed by the user input command is selected and displayed, and the Web page The storage means when at least one of the element data and the layout data is not stored in the storage means among the data of the Web page displayed by the user input command. Data not stored in the server is acquired from the server side, and the Web page is displayed based on the data acquired from the server side and the data stored in the storage means.

  According to the present invention, only a part of the data of the Web page can be acquired, so that the efficiency of caching the data of the Web page can be improved.

It is a figure which shows the whole structure of the information management system 1 in Embodiment 1 of this invention. It is a block diagram which shows the hardware constitutions of the terminal device 30 in Embodiment 1 of this invention. It is a block diagram which shows the hardware constitutions of the server apparatus 20 in Embodiment 1 of this invention. It is a block diagram which shows the structural example of the function of the information management system 1 in Embodiment 1 of this invention. It is a figure explaining the storage area of the memory 60 of FIG. 4 in Embodiment 1 of this invention. It is a figure explaining the storage area of the layout data area of FIG. 5 in Embodiment 1 of this invention. It is a figure explaining the storage area of the schedule data area 103 of FIG. 5 in Embodiment 1 of this invention. It is a figure which shows an example of the cache state management table stored in the cache state management area | region 101 of FIG. 5 in Embodiment 1 of this invention. It is a figure which shows an example of the data communication between the server and client in Embodiment 1 of this invention. It is a figure which shows an example which described the information stored in the layout data table 93 of FIG. 4 in Embodiment 1 of this invention in the XML format. It is a figure which shows an example which described the information stored in the schedule data table 92 of FIG. 4 in Embodiment 1 of this invention in the JSON format. It is a figure which shows the example of a display of the screen at the time of the schedule browsing in Embodiment 1 of this invention. It is a figure which shows the example of a display of the screen at the time of the schedule browsing different from FIG. 12 in Embodiment 1 of this invention. It is a figure which shows an example which described the information different from FIG. 10 stored in the layout data table 93 of FIG. 4 in Embodiment 1 of this invention in the XML format. It is a flowchart explaining operation | movement of the information management system 1 in Embodiment 1 of this invention. It is a flowchart explaining the detail of the cache data presence determination data creation process in Embodiment 1 of this invention. It is a flowchart explaining the detail of the cache data acquisition process in Embodiment 1 of this invention. It is a flowchart explaining the detail of the cache data preservation | save process in Embodiment 1 of this invention. It is a flowchart explaining the detail of the data acquisition process of the database in Embodiment 1 of this invention. It is a flowchart explaining the detail of the return data creation process in Embodiment 1 of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

Embodiment 1 FIG.
FIG. 1 shows the overall configuration of an information management system 1 according to Embodiment 1 of the present invention. As shown in FIG. 1, the information management system 1 includes a communication line 10, a server device 20, and a plurality of terminal devices 30.

  In practice, there may be more terminal devices 30 than illustrated, and there may be fewer terminal devices 30 than illustrated. The terminal device 30 is connected to the server device 20 via the communication line 10.

  The communication line 10 is a network having a server, a router, etc. (none of which are shown). The communication line 10 connects the server device 20 and the terminal device 30. The communication line 10 transmits data according to a procedure compliant with TCP / IP (Transmission Control Protocol / Internet Protocol), HTTP (HyperText Transfer Protocol) realized on TCP / IP, and the like.

  Note that the communication protocols described above are merely examples, and the present invention is not limited to these.

  FIG. 2 shows a hardware configuration of the terminal device 30 according to Embodiment 1 of the present invention. As illustrated in FIG. 2, the terminal device 30 includes a control unit 31, a storage unit 32, a display unit 33, an operation unit 34, a communication unit 35, and a voice input / output unit 36. The terminal device 30 is a device that transmits and receives various data via the communication line 10 such as a mobile phone, a smartphone, a wireless terminal, a mobile tablet terminal, or a netbook, and is not particularly limited.

  The control unit 31 includes various processing devices such as a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory).

  The storage unit 32 is a nonvolatile storage unit that stores various data. The display unit 33 includes a display screen and displays an image based on a command from the control unit 31. The display screen is, for example, an LCD (Liquid Crystal Display). The LCD includes a touch panel (not shown). On the touch panel, various controls are displayed as various buttons. The operation unit 34 includes a plurality of operators, and supplies an operation signal to the controller 31 based on the operator selected by the user. The control unit 31 performs various processes based on the supplied operation signal. The communication unit 35 includes an antenna and a communication circuit, and transmits and receives data via the communication line 10. The sound input / output unit 36 includes sound collection means such as a microphone, sound emission means such as a speaker, and sound processing circuits such as a DSP (Digital Signal Processor).

  FIG. 3 shows a hardware configuration of the server device 20 according to the first embodiment of the present invention. As illustrated in FIG. 3, the server device 20 includes a control unit 21, a storage unit 22, a display unit 23, an operation unit 24, and a communication unit 25.

  Although the control unit 21 is different in that it processes a large amount of data, the control unit 21 has the same configuration as the control unit 31 and therefore will not be described here. The storage unit 22 includes a storage device such as an HDD (Hard Disk Drive) and stores various data to be supplied to the terminal device 30 as a client. Since the display unit 23 has the same configuration as that of the display unit 33, details thereof are omitted here, but the display unit 23 does not necessarily have a function such as a touch panel. The operation unit 24 includes input means such as a keyboard, for example. Although the communication unit 25 is different in that it processes a large amount of data, the communication unit 25 has the same configuration as the communication unit 35, and therefore the description thereof is omitted here.

  FIG. 4 shows a configuration example of functions of the information management system 1 according to Embodiment 1 of the present invention. As shown in FIG. 4, the information management system 1 includes a terminal device 30 and a schedule management system 40.

  The terminal device 30 is a so-called client side system. Specifically, the terminal device 30 includes a client application 50 and a memory 60. The client application 50 executes various processes based on a user command from the terminal device 30. For example, when a schedule display is requested by a user instruction, schedule screen data, which is web page data, is sent to the schedule management system 40 according to HTTP (HyperText Transfer Protocol) or HTTPS (HyperText Transfer Protocol Over Layer). The schedule screen data requested in the procedure and returned from the schedule management system 40 is cached in the memory 60 and displayed as a web page on the display unit 33 of the terminal device 30 based on a predetermined format. Here, the cached data is data that the client side system stores the data acquired from the server side system in the memory 60. Next, the client side system is designated by the same URL (Uniform Resource Locator). This is appropriately used when referring to a page on the Web. Here, the client application 50 is executed on the control unit 31 shown in FIG. The memory 60 is mounted on the storage unit 32 shown in FIG.

  In the above description, the communication protocol conforms to HTTP or HTTPS, but is not limited thereto.

  The client application 50 includes a message analysis unit 51 and a cache state management unit 52. The message analysis unit 51 reads the schedule screen data returned from the schedule management system 40, analyzes the structure thereof, and displays it on the display unit 33 according to the analysis result. For example, if the read document is data described in XML (Extensible Markup Language) format, the correspondence between the start tag (<title>) and the end tag (</ title>) is checked, and each element is nested. Check whether or not. At this time, if the format is not valid, an error is notified appropriately. That is, in this case, the message analysis unit 51 checks whether or not the read data is described grammatically in the XML format.

  Next, if the data described in the XML format is a grammatically valid format, the message analysis unit 51 causes the display unit 33 to display an XML format document using an API (Application Program Interface). In this case, the API is, for example, DOM (Document Object Model) or SAX (Simple API for XML).

  In addition, if the schedule screen data returned from the schedule management system 40 is data described in the JSON (JaveScript Object Notification) format, the message analysis unit 51 converts the data described in the JSON format into an object. A display object is generated using the processed data and displayed on the display unit 33.

  Moreover, when the schedule screen data returned from the schedule management system 40 includes data described in the XML format and data described in the JSON format, the message analysis unit 51 executes the processes described above. And displayed on the display unit 33.

  Here, the case where the schedule screen data returned from the schedule management system 40 is data described in the XML format or data described in the JSON format has been described. The data may be described in other formats.

  The cache status management unit 52 manages the status of cached data. For example, it manages whether or not the cached data includes layout data that defines the arrangement of element data, and also manages whether or not the cached data includes schedule data as element data. The cache state management unit 52 manages whether the cached data needs to be updated. Further, the cache state management unit 52 manages when the cached data is scheduled data. For example, if the cached data is schedule data of “September 2011”, the cache state management unit 52 determines whether to update “September 2011”, whether to include layout data, It manages whether to include schedule data as data.

  Note that the message analysis unit 51 may have a function corresponding to the cache state management unit 52.

  In addition, although the case where the data returned from the server side system is schedule screen data has been described here, the present invention is not limited to this.

  The schedule management system 40 is mounted on the server device 20 and is a so-called server-side system. Specifically, the schedule management system 40 includes an application server 70, a schedule management server 80, a database server 90, and the like. Here, the application server 70, the schedule management server 80, and the database server 90 are executed on the control unit 21 shown in FIG.

  The application server 70 includes a business processing unit 71. The business processing unit 71 executes various business-related processes, and appropriately updates and references schedule screen data held by the database server 90.

  The schedule management server 80 manages schedule screen data stored in the schedule management database 91 managed by the database server 90, and returns the schedule screen data to the client application 50 in response to a request for the schedule screen data from the client application 50. To do. For example, the schedule management server 80 appropriately converts the layout data and schedule data, which are the requested schedule screen data, into a predetermined format such as an XML format or a JSON format, Return to application 50.

  The database server 90 manages the schedule management database 91. The schedule management database 91 includes a schedule data table 92 as element data and a layout data table 93 that defines the arrangement of the element data. Here, the schedule management database 91 is implemented in the storage unit 22 shown in FIG.

  The format of data stored in the schedule data table 92 and the layout data table 93 is stored in, for example, a CSV (Comma-Separated Values) format. However, the data format to be stored is not limited to this. For example, it may be stored in a binary data format.

  Although the application server 70, the schedule management server 80, and the database server 90 are described as separate servers here, the present invention is not limited to these. For example, the application server 70 may also serve as the schedule management server 80. For example, the schedule management server 80 may also serve as the application server 70. The database server 90 may also serve as the application server 70 and the schedule management server 80.

  FIG. 5 shows a storage area of the memory 60 of FIG. 4 in Embodiment 1 of the present invention. As shown in FIG. 5, the memory 60 is basically composed of three areas. The first area is a cache state management area 101. In this cache state management area 101, for example, information relating to the state of cached data is stored as a cache state management table described later.

  The second area is a layout data area 102. In this layout data area 102, for example, layout data defining the arrangement of element data in the schedule screen data acquired from the schedule management system 40 is stored.

  The third area is a schedule data area 103. In this schedule data area 103, for example, schedule data that is element data among schedule screen data acquired from the schedule management system 40 is stored.

  FIG. 6 shows a storage area of the layout data area 102 of FIG. 5 in the first embodiment of the present invention. As shown in FIG. 6, the layout data area 102 is configured such that a plurality of unit areas are connected in an infinite loop. In this case, the layout data area 102 is divided into N unit areas, and when predetermined data is written in the area 1, the following information is written in the area 2. Further, information is written in order as in areas 3,... And information is written in area N, and then the next information is written in area 1. That is, the information already stored in the area 1 is erased, and new information is stored thereon. In this way, the latest N pieces of information are stored in the layout data area 102. For example, in FIG. 6, layout data of schedule screen data for September is stored in area 2, and layout data of schedule screen data for October is stored in area 3.

  FIG. 7 shows the storage area of the schedule data area 103 of FIG. 5 in Embodiment 1 of the present invention. As shown in FIG. 7, the schedule data area 103 is configured such that a plurality of unit areas are connected in an infinite loop. In this case, the schedule data area 103 is divided into N unit areas, and when predetermined data is written in the area 1, the next information is written in the area 2. Further, information is written in order as in areas 3,... And information is written in area N, and then the next information is written in area 1. That is, the information already stored in the area 1 is erased, and new information is stored thereon. In this way, the latest N pieces of information are stored in the schedule data area 103. For example, in FIG. 7, schedule data for schedule screen data for n−1 months is stored in area 1, schedule data for schedule screen data for n months is stored in area 2, and schedule data for n + 1 months is stored in area 3. Stores schedule data for schedule screen data.

  FIG. 8 shows an example of the cache status management table stored in the cache status management area 101 of FIG. 5 in the first embodiment of the present invention. As shown in FIG. 8, the cache state management table includes a cache target data variable, an update flag, a cache data display determination flag, a layout data determination flag, a schedule data determination flag, and a cache presence / absence determination flag. Information on determination. In the cache state management table, a cache state corresponding to one schedule screen data is defined for one row. That is, when a data variable to be cached is specified, update flag, cache data display determination flag, layout data determination flag, schedule data determination flag, and cache presence / absence as attribute information of schedule screen data for the specified cache target A judgment flag is specified.

  The data variable to be cached identifies schedule screen data to be cached. For example, as shown in FIG. 8, “201109”, “20111”, “20112”, “201103”, and “201104” are used. Is. “201109” means that the schedule for September 2011 is the schedule screen data to be cached, and “20111” is the schedule screen data for which the schedule for January 2011 is to be cached. "201102" means that the schedule for February 2011 is the schedule screen data to be cached, and "201103" means that the schedule for March 2011 is to be cached. "2011104" means that the schedule for April 2011 is schedule screen data to be cached.

  The update flag is changed when a schedule screen data update request is made by a user command. For example, when the schedule screen data is displayed on the display unit 33, when an update request for the schedule screen data is made according to a user command, the update flag is set to 1, and no update request for the schedule screen data is made. The update flag is set to 0.

  The cache data display determination flag is interlocked with the change of the update flag. For example, when the update flag is set to 1, the cache data display determination flag is set to 0, and when the update flag is set to 0, the cache data display determination flag is set to 1. When the cache data display determination flag is set to 0, both the layout data determination flag and the schedule data determination flag are set to 0 in conjunction therewith.

  Specifically, the information related to cache presence / absence determination includes a layout data determination flag, a schedule data determination flag, and a cache presence / absence determination flag.

  The layout data determination flag indicates whether or not layout data is included in the cached data. For example, when the layout data is included in the cached data, the layout data determination flag is set to 1, and when the layout data is not included in the cached data, the layout data determination flag is set to 0.

  The schedule data determination flag indicates whether or not schedule data is included in the cached data. For example, when the cached data includes schedule data, the schedule data determination flag is set to 1, and when the cached data does not include schedule data, the schedule data determination flag is set to 0.

  The cache presence / absence determination flag stores an AND operation result of the layout data determination flag and the schedule data determination flag. For example, when the cache presence / absence determination flag is 1, since both layout data and schedule data exist, the cached data defines the schedule data as the element data for displaying the schedule screen data and the arrangement of the element data Both the layout data and the layout data to be stored are present, and the state at this time is assumed to be cached data. In addition, when the cache presence / absence determination flag is 0, either or both of the layout data and the schedule data does not exist, so the data for displaying the schedule screen data is missing in the cached data. State that there is no cached data.

  For example, as shown in FIG. 8, when the data variable to be cached is September 2011, the update flag is 0, the cache data display determination flag is 1, the layout data determination flag is 1, the schedule data determination flag is Is 1, the cache presence / absence determination flag is set to 1, and the data variable to be cached is January 2011, the layout data determination flag is 1, the schedule data determination flag is 0, and the cache presence / absence determination flag is If the data variable to be cached is set to 0 and the data variable to be cached is February 2011, the layout data determination flag is set to 0, the schedule data determination flag is set to 1, the cache presence / absence determination flag is set to 0, and the data to be cached If the variable is March 2011, the layout data determination flag is set to 0 The schedule data determination flag is 0, is shown an example of cache existence determination flag is set to zero. In addition, in FIG. 8, about the location which is "-", the state in which nothing is set is shown.

  Note that the notation of the cache state management table described here is an example, and is not limited to these.

  FIG. 9 shows an example of data communication between the server and the client in the first embodiment of the present invention. As shown in FIG. 9, the client application 50 executes the screen request in the format “http://xxx.xxx/yyyy/xxxmonthly.do”. Based on the screen request from the client application 50, the schedule management server 80 divides and returns the schedule screen data into layout data and schedule data. Such a screen request may be made when a part of the schedule screen data (for example, element data or layout data) or all of the schedule screen data (for example, element data and layout data) is not cached in the memory 60 or when the schedule screen data is updated. It is executed when

  Note that the format of the screen request command described here is merely an example, and the present invention is not limited to this.

  FIG. 10 shows an example in which the information stored in the layout data table 93 of FIG. 4 in the first embodiment of the present invention is described in the XML format. As shown in FIG. 10, the description 151 defines the arrangement of schedule data that is element data. The description 152 defines a reference destination of schedule data that is element data. The description 153 defines a process corresponding to when the user operates the screen, for example, when the user flicks the screen when the display screen is scrolled.

  Since XML is a markup language based on a specific structure, if data is described in the XML format, it becomes easy for the user to add necessary elements.

  Needless to say, the operation is not limited to flicking. For example, as an operation when selecting an operation element, tap the operation element once, and as an operation when executing the selected operation element, double-tap the operation element twice, or move an operation element or an object. It may be an operation such as dragging when pinching or pinching when shrinking or enlarging an object or the like.

  The descriptions 151, 152, and 153 described here are merely examples, and the present invention is not limited to these.

  FIG. 11 shows an example in which the information stored in the schedule data table 92 of FIG. 4 in the first embodiment of the present invention is described in the JSON format. As illustrated in FIG. 11, the description 154 defines “CACHE_TAG” as a data variable to be cached, and defines “monthly_201109” as a variable in “CACHE_TAG”. The description 155 defines details of “monthly_201109”. In this case, “2011P” is defined as “DISP_MONTH”, “201110” is defined as “NEXT_MONTH”, and “201110” is defined as “PREV_MONTH”. Is defined. Here, “DISP_MONTH” is used as a variable that defines what is first displayed on the display unit 33 when the schedule screen data is acquired, and “NEXT_MONTH” is defined as a variable that defines what is displayed as the next month of “DISP_MONTH”. And “PREV_MONTH” is used as a variable that defines what is displayed as the month before “DISP_MONTH”.

  Note that JSON is a lightweight data exchange format that is easy for users to read and write, and can be easily parsed for machines equipped with a CPU, and is based on the object notation in JavaScript (registered trademark). Therefore, when data is described in the JSON format, the response time of Web page data can be shortened.

  The descriptions 154 and 155 described here are merely examples, and the present invention is not limited to these.

  FIG. 12 shows a display example of the screen at the time of viewing the schedule in the first embodiment of the present invention. As shown in FIG. 12, the terminal device 30 is formed of a display unit 33 and a housing 110 that houses the display unit 33 and the like. By flicking left and right with the finger 121, the terminal device 30 displays the schedule screen of the previous month or the next month. For example, when flicked in the direction of the right-pointing arrow 132, the schedule screen for July 2011, which is the previous month, is displayed on the display unit 33, and when flicked in the direction of the left-pointing arrow 131, the next month is September 2011. A schedule screen is displayed on the display unit 33. For example, when the update button 141 which is one of the operators is double-tapped with the finger 121, the schedule screen for August 2011 is updated. Further, as shown in FIG. 12, the schedule data is displayed as “all day” on August 5, 2011, for example, and this detail is displayed by further performing a predetermined operation. . Also, as shown in FIG. 12, the layout data defines where various operators, schedule data, and the like are arranged on the display unit 33. For example, the update button is a corner on the lower right side of the display unit 33. The schedule data is arranged in the approximate center of the display unit 33.

  FIG. 13 shows a display example of a screen at the time of viewing a schedule, which is different from FIG. 12 in the first embodiment of the present invention. As shown in FIG. 13, for example, a schedule screen for September 2011 is displayed on the display unit 33. In FIG. 12, since the schedule screen for August 2011 is displayed on the display unit 33, FIG. 13 shows a display example after flicking in the direction of the left arrow 131 in FIG.

  FIG. 14 shows an example in which information different from FIG. 10 stored in the layout data table 93 of FIG. 4 in the first embodiment of the present invention is described in the XML format. As illustrated in FIG. 14, the description 156 is an argument set in the operation at the time of the left flick. When the schedule screen data is cached in the memory 60, the cached schedule screen data is displayed on the display unit 33. When the schedule screen data is not cached in the memory 60, the schedule management server 80 requests the schedule screen data. Also, as shown in FIG. 14, the description 157 is an argument set in the right flick operation, and when the schedule screen data is cached in the memory 60, the cached schedule screen data is displayed. When the schedule screen data is not cached in the memory 60, the schedule management server 80 requests the schedule screen data. In the description 158, an argument is not set in the operation at the time of the left flick, and the schedule screen data is requested to the schedule management server 80 regardless of whether the schedule screen data is cached in the memory 60 or not.

  FIG. 15 is a flowchart for explaining the operation of the information management system 1 according to the first embodiment of the present invention.

(Step S11)
The terminal device 30 displays a schedule screen (for n months).

(Step S12)
The terminal device 30 determines whether or not there is a command to display the schedule screen (for n + 1 month). If there is a command to display the schedule screen (n + 1 month), the terminal device 30 proceeds to step S13. On the other hand, if there is no instruction to display the schedule screen (for n + 1 month), the terminal device 30 returns to step S12.

  In addition, although the example based on the instruction | command which displays a schedule screen (for n + 1 month) was demonstrated above, it is not limited to this. For example, it may be based on a command for displaying a schedule screen (for n-1 month).

(Step S13)
The terminal device 30 determines whether to display cache data. Specifically, when the cache data display determination flag shown in FIG. 8 is 1, the terminal device 30 determines to display the cache data, and proceeds to step S14.

  On the other hand, when the cache data display determination flag shown in FIG. 8 is 0, the terminal device 30 determines that the cache data is not displayed, requests the schedule management system 40 for a schedule screen (for n + 1 month), and proceeds to step S19. move on. At this time, various flags of the cache state management table shown in FIG. 8 are changed. For example, when the cache data display determination flag is 0, the layout data determination flag and the schedule data determination flag are set to 0, whereby the cache presence / absence determination flag is set to 0. Then, the terminal device 30 transmits the contents of various flags in the cache state management table shown in FIG. 8 to the schedule management system 40.

(Step S14)
As will be described later in detail with reference to FIG. 16, the terminal device 30 executes cache data presence / absence determination data creation processing, and then proceeds to step S15.

(Step S15)
The terminal device 30 determines whether there is cache data. If the cache presence / absence determination flag shown in FIG. 8 is 1, the terminal device 30 determines that there is cache data, and proceeds to step S16.

  On the other hand, if the cache presence / absence determination flag shown in FIG. 8 is 0, the terminal device 30 determines that there is no cache data, requests the schedule screen (n + 1 month) from the schedule management system 40, and proceeds to step S19. At this time, the terminal device 30 transmits the contents of various flags in the cache state management table shown in FIG. 8 to the schedule management system 40.

(Step S16)
As will be described later in detail with reference to FIG. 17, the terminal device 30 executes a cache data acquisition process, and then proceeds to step S18.

(Step S17)
As will be described later, the terminal device 30 executes cache data storage processing, which is processing for storing layout data and schedule data returned from the schedule management system 40, as will be described later with reference to FIG. Thereafter, the process proceeds to step S18.

(Step S18)
The terminal device 30 displays the schedule screen (for n + 1 month), and the process ends.

(Step S19)
As will be described later in detail with reference to FIG. 19, the schedule management system 40 executes database data acquisition processing, returns layout data and schedule data to the terminal device 30, and then proceeds to step S20.

(Step S20)
As will be described later in detail with reference to FIG. 20, the schedule management system 40 executes return data creation processing, and then proceeds to step S17.

  FIG. 16 is a flowchart illustrating details of the cache data presence / absence determination data creation processing according to the first embodiment of the present invention.

(Step S31)
The terminal device 30 determines whether there is layout data corresponding to the cache target. If the layout data corresponding to the cache target exists in the layout data area 102 of the memory 60, the terminal device 30 proceeds to step S32. On the other hand, when the layout data corresponding to the cache target does not exist in the layout data area 102 of the memory 60, the terminal device 30 proceeds to step S33.

(Step S32)
The terminal device 30 is stored in the cache state management area of the memory 60, sets the layout data determination flag of the cache state management table shown in FIG. 8 to 1, and proceeds to step S34.

(Step S33)
The terminal device 30 is stored in the cache state management area of the memory 60, sets the layout data determination flag of the cache state management table shown in FIG. 8 to 0, and proceeds to step S34.

(Step S34)
The terminal device 30 determines whether there is schedule data corresponding to the cache target. If the schedule data corresponding to the cache target exists in the schedule data area 103 of the memory 60, the terminal device 30 proceeds to step S35. On the other hand, if the schedule data corresponding to the cache target does not exist in the schedule data area 103 of the memory 60, the terminal device 30 proceeds to step S36.

(Step S35)
The terminal device 30 is stored in the cache state management area of the memory 60, sets the schedule data determination flag of the cache state management table shown in FIG. 8 to 1, and proceeds to step S37.

(Step S36)
The terminal device 30 is stored in the cache state management area of the memory 60, sets the schedule data determination flag of the cache state management table shown in FIG. 8 to 0, and proceeds to step S37.

(Step S37)
The terminal device 30 performs an AND operation on the layout data determination flag and the schedule data determination flag, and proceeds to step S38.

(Step S38)
The terminal device 30 stores the AND operation result of the layout data determination flag and the schedule data determination flag in the cache presence / absence determination flag shown in FIG. 8, and the process ends and returns to step S14 in FIG.

  FIG. 17 is a flowchart illustrating details of the cache data acquisition process according to the first embodiment of the present invention.

(Step S51)
The terminal device 30 acquires layout data corresponding to the cache target from the cache data. Specifically, it is assumed that September is designated as the schedule screen (for n + 1 month). In this case, the data variable to be cached is “201109”. For the layout data at this time, the terminal device 30 searches for cache data corresponding to September from each unit area of the layout data area 102 shown in FIG. 6, and acquires the search result. For example, as shown in FIG. 6, layout data for September is stored in the area 2, and the terminal device 30 acquires this layout data. Thereafter, the process proceeds to step S52.

(Step S52)
The terminal device 30 acquires schedule data corresponding to the cache target from the cache data. Specifically, it is assumed that September is designated as the schedule screen (for n + 1 month). In this case, the data variable to be cached is “201109”. For the layout data at this time, the terminal device 30 searches for cache data corresponding to September from each unit area of the schedule data area 103 shown in FIG. 7, and acquires the search result. For example, as illustrated in FIG. 7, schedule data corresponding to September (n + 1 month) is stored in the area 3, and the terminal device 30 acquires the schedule data. Thereafter, the process ends, and the process returns to step S16 in FIG.

  FIG. 18 is a flowchart for explaining the details of the cache data storage process according to the first embodiment of the present invention.

(Step S61)
The terminal device 30 caches the acquired data in the memory area, and proceeds to step S62. Specifically, when the acquired data includes layout data, the acquired layout data is stored in the layout data area 102 shown in FIG. 5, and when the acquired data includes schedule data, the acquired schedule data is shown in FIG. It is stored in the schedule data area 103 shown.

(Step S62)
The terminal device 30 determines whether or not the layout data is cached in the memory area. If the terminal device 30 caches the layout data in the memory area, the terminal device 30 proceeds to step S63. On the other hand, if the terminal device 30 does not cache the layout data in the memory area, the terminal device 30 proceeds to step S64.

(Step S63)
The terminal device 30 sets the layout data determination flag shown in FIG. 8 to 1, and proceeds to step S64.

(Step S64)
The terminal device 30 determines whether the schedule data is cached in the memory area. When the schedule data is cached in the memory area, the terminal device 30 proceeds to step S65. On the other hand, if the terminal device 30 does not cache the schedule data in the memory area, the process ends and returns to step S17 in FIG.

(Step S65)
The terminal device 30 sets the schedule data determination flag shown in FIG. 8 to 1, the process ends, and the process returns to step S17 in FIG.

  FIG. 19 is a flowchart for explaining the details of the data acquisition processing of the database according to the first embodiment of the present invention.

(Step S81)
The schedule management system 40 determines whether or not the update flag shown in FIG. If the update flag shown in FIG. 8 is not 1, the schedule management system 40 proceeds to step S83. On the other hand, if the update flag shown in FIG. 8 is 1, the schedule management system 40 proceeds to step S82.

(Step S82)
The schedule management system 40 acquires layout data and schedule data corresponding to the cache target. Specifically, the schedule management system 40 assumes that September is designated as the requested schedule screen (for n + 1 month). In this case, the schedule management system 40 uses the schedule management database 91 as a search key to retrieve the schedule data and the layout data of schedule screen data corresponding to September from both the schedule data table 92 and the layout data table 93. After searching and acquiring the search result, the process ends, and the process returns to step S19 shown in FIG.

(Step S83)
The schedule management system 40 determines whether or not the layout data determination flag is 1. If the layout data determination flag is 1, the schedule management system 40 proceeds to step S84. On the other hand, if the layout data determination flag is not 1, the schedule management system 40 proceeds to step S85.

(Step S84)
The schedule management system 40 acquires layout data corresponding to the cache target. Specifically, the schedule management system 40 assumes that September is designated as the requested schedule screen (for n + 1 month). In this case, the schedule management system 40 searches the layout data of the schedule screen data corresponding to September from the layout data table 93 using September as a search key from the schedule management database 91, acquires the search result, Proceed to S85.

(Step S85)
The schedule management system 40 determines whether or not the schedule data determination flag is 1. If the schedule data determination flag is 1, the schedule management system 40 proceeds to step S86. On the other hand, if the schedule data determination flag is not 1, the schedule management system 40 ends the process and returns to step S19 shown in FIG.

(Step S86)
The schedule management system 40 acquires schedule data corresponding to the cache target. Specifically, the schedule management system 40 assumes that September is designated as the requested schedule screen (for n + 1 month). In this case, the schedule management system 40 searches the schedule data of the schedule screen data corresponding to September from the schedule data table 92 using September as a search key from the schedule management database 91, acquires the search result, Is completed, and the process returns to step S19 shown in FIG.

  FIG. 20 is a flowchart for explaining the details of the return data creation processing in Embodiment 1 of the present invention.

(Step S101)
The schedule management system 40 determines whether there is layout data in the acquired data. If there is layout data in the acquired data, the schedule management system 40 proceeds to step S102. On the other hand, if there is no layout data in the acquired data, the schedule management system 40 proceeds to step S103.

(Step S102)
The schedule management system 40 converts the layout data into XML format data, and proceeds to step S103.

(Step S103)
The schedule management system 40 determines whether there is schedule data in the acquired data. If there is schedule data in the acquired data, the schedule management system 40 proceeds to step S104. On the other hand, if there is no schedule data in the acquired data, the schedule management system 40 ends the process and returns to step S20 shown in FIG.

(Step S104)
The schedule management system 40 converts the schedule data into JSON format data, the process ends, and the process returns to step S20 shown in FIG.

  As described above, the processes of Step S11 to Step S20, Step S31 to Step S38, Step S51, Step S52, Step S61 to Step S65, Step S81 to Step S86, and Step S101 to Step S104 are performed by the terminal device 30 and the server device 20. As a result, the client-side system does not need to request the entire Web page from the server-side system each time, and can request only necessary data. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved.

  Further, by executing the processing of steps S11 to S18 by the terminal device 30, it is not necessary to request the entire web page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved. Moreover, since the caching efficiency can be improved, the power consumption of the terminal device 30 can be reduced. Further, since only necessary data can be requested, communication data traffic of the terminal device 30 can be improved.

  In the first embodiment, the steps for describing the program are executed in parallel or individually even if they are not necessarily processed in time series, as well as the processes performed in time series in the described order. It also includes the processing.

  In the first embodiment, the system represents the entire apparatus composed of a plurality of apparatuses.

  As described above, in the first embodiment, the terminal device 30 that requests the Web page data from the server side as the client side, and the server device 20 that returns the Web page data requested from the terminal device as the server side. In the information management system 1 including the server device 20, the storage unit 22 stores element data that forms elements of a Web page and layout data that defines the arrangement of element data that forms a Web page. The terminal device 30 includes a schedule management server 80 that returns at least one of the stored element data and layout data as Web page data in response to a request from the terminal device 30 and manages the Web page data. Web page data returned from the Web page to be displayed in response to a user input command based on the storage unit 32 stored separately and the Web page data stored in the storage unit 32 and the Web page data to be displayed in response to the user input command A control unit 31 that determines whether or not to request the data, and the control unit 31 stores the element data stored in the storage unit 32 and the storage unit 32 when the Web page data is not requested. Web page data to be displayed in response to a user input command when data for forming a Web page to be displayed in response to a user input command is selected from display layout data and displayed. Of these, when at least one of the element data and the layout data is not stored in the storage unit 32, it is stored in the storage unit 32. Data is acquired from the server device 20, and only a part of the data of the Web page is acquired by displaying the Web page based on the data acquired from the server device 20 and the data stored in the storage unit 32. Therefore, the efficiency of caching the Web page data can be improved.

  Further, in the first embodiment, the control unit 31 is configured such that when the web page element data to be displayed in response to a user input command is not stored in the storage unit 32 and the web page layout data is stored in the storage unit. When the data is stored in 32, by requesting the element data of the Web page from the server device 20, it is not necessary to request the entire Web page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved.

  Further, in the first embodiment, the control unit 31 displays the Web page element data when the layout data of the Web page to be displayed by the user input command is not stored in the storage unit 32 and the storage unit 32 stores the element data of the Web page. By storing the web page layout data from the server device 20, it is not necessary to request the entire web page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved.

  Further, in the first embodiment, the control unit 31 sends the Web page to the server device 20 when both the element data and the layout data of the Web page displayed by the user input command are not stored in the storage unit 32. By requesting the element data and layout data, it is not necessary to request the entire Web page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved.

  Further, in the first embodiment, when the user input command updates the web page data, the control unit 31 requests both the element data and the layout data of the web page from the server device 20, thereby It is not necessary to request the entire page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved.

  In the first embodiment, the layout data is data described in the XML format. Since XML is a markup language based on a specific structure, the data is described in the XML format. It becomes easy for the user to add necessary elements.

  In the first embodiment, since the element data is data described in the JSON format, the JSON is a lightweight data exchange format, which is easy for a user to read and write, and is installed in a machine equipped with a CPU. Since it is a data description language based on the object notation in JavaScript (registered trademark), it can be easily parsed, so when data is described in the JSON format, the response time of the data on the Web page Can be shortened.

  Further, in the first embodiment, in the terminal device 30 that requests the web page data to the server side as the client side, the web page data acquired after requesting the web page data to the server side is used as the element of the web page. Is stored in accordance with the element data forming the web page and the layout data for determining the arrangement of the element data forming the web page, the web page data stored in the memory unit 32, and a user input command. A control unit 31 that determines whether or not to request web page data to be displayed based on a user input command based on the web page data. When the control unit 31 does not request web page data, From the element data stored in the storage unit 32 and the layout data stored in the storage unit 32 When data for forming a Web page to be displayed is selected and displayed in response to a user input command and is requested, and data of the Web page to be displayed in response to a user input command is displayed. When at least one of the data is not stored in the storage unit 32, the data not stored in the storage unit 32 is acquired from the server side, and the data acquired from the server side and the data stored in the storage unit 32 are By displaying the web page based on this, it is not necessary to request the entire web page from the server side system each time, and only necessary data can be requested. Thereby, only the screen layout can be updated. Further, when the screen layout is the same and only the element data is updated, only the element data can be updated by acquiring only the element data without requesting the entire Web page. Therefore, since only a part of the data of the web page can be acquired, the efficiency of caching the data of the web page can be improved. Moreover, since the caching efficiency can be improved, the power consumption of the terminal device 30 can be reduced. Further, since only necessary data can be requested, communication data traffic of the terminal device 30 can be improved.

  In the first embodiment, in the terminal device program that operates on the terminal device that requests the Web page data from the server side as the client side, the Web page acquired after requesting the Web page data from the server side Is stored in the storage means, and is stored in the storage means, divided into element data forming the elements of the Web page and layout data defining the arrangement of the element data forming the Web page, An information processing unit that determines whether to request the data of the Web page to be displayed by the user's input command based on the data of the Web page and the data of the Web page to be displayed by the user's input command And when the information processing unit does not request the data of the Web page, From the element data stored in the storage unit and the layout data stored in the storage unit, the data for forming the Web page to be displayed is selected and displayed by the user input command, and the Web In the case of requesting page data, when at least one of the element data and the layout data is not stored in the storage means among the data of the Web page displayed by the user input command, the storage By acquiring data not stored in the means from the server side and displaying the Web page based on the data acquired from the server side and the data stored in the storage means, Since only a part of the data can be obtained, the web page data is cached. It is possible to improve the efficiency.

  1 Information management system, 10 communication line, 20 server device, 30 terminal device, 21, 31 control unit, 22, 32 storage unit, 23, 33 display unit, 24, 34 operation unit, 25, 35 communication unit, 36 voice input Output unit, 40 schedule management system, 50 client application, 51 message analysis unit, 52 cache state management unit, 60 memory area, 70 application server, 71 business processing unit, 80 schedule management server, 90 database server, 91 schedule management database, 92 Schedule Data Table, 93 Layout Data Table, 101 Cache State Management Area, 102 Layout Data Area, 103 Schedule Data Area, 110 Case, 121 Finger, 131 Left Arrow, 132 Right Arrow Mark, 141 update button, 151, 152, 153, 154, 155, 156, 157, 158 description.

Claims (9)

In an information management system comprising a terminal device that requests Web page data from the server side as a client side and a server device that returns Web page data requested from the terminal device as a server side.
The server device
First storage means for storing element data forming elements of the Web page and layout data defining an arrangement of the element data forming the Web page;
Data management means for returning at least one of the element data and the layout data stored in the first storage means as data of the Web page in response to a request from the terminal device, and managing the data of the Web page; ,
The terminal device
Second storage means for storing the data of the Web page returned from the server device separately into the element data and the layout data;
Whether to request the Web page data to be displayed by the user input command based on the Web page data stored in the second storage means and the Web page data to be displayed by the user input command An information processing unit for determining whether or not
The information processing unit
When the web page data is not requested, the element data stored in the second storage means and the layout data stored in the second storage means are displayed by the user input command. Select and display the data that forms the web page,
When requesting data of the web page,
Data not stored in the second storage means when at least one of the element data and the layout data is not stored in the second storage means among the data of the Web page displayed by the user input command Is acquired from the server device, and the Web page is displayed based on the data acquired from the server device and the data stored in the second storage unit. The information processing unit
When the element data of the web page to be displayed by the user input command is not stored in the second storage unit, and the layout data of the web page is stored in the second storage unit The information management system according to claim 1, wherein the server device requests the element data of the Web page from the server device. The information processing unit
When the layout data of the Web page to be displayed by the user input command is not stored in the second storage means, and the element data of the Web page is stored in the second storage means The information management system according to claim 1 or 2, wherein the server device requests the layout data of the Web page from the server device. The information processing unit
When both the element data and the layout data of the Web page displayed by the user input command are not stored in the second storage unit, the element data and the layout data of the Web page are stored in the server device. The information management system according to any one of claims 1 to 3, wherein the information management system is requested. The information processing unit
5. When the user input command updates the data of the Web page, the server device is requested for both the element data and the layout data of the Web page. The information management system according to claim 1. The information management system according to claim 1, wherein the element data is data described in a JSON format. The information management system according to claim 1, wherein the layout data is data described in an XML format. In a terminal device that requests web page data from the server side as the client side,
The Web page data acquired after requesting the Web page data to the server side is divided into element data forming the elements of the Web page and layout data defining the arrangement of the element data forming the Web page. Storage means for storing
Whether to request data of the web page to be displayed by the user input command based on the data of the web page stored in the storage unit and the data of the web page to be displayed by the user command. And an information processing unit for determining
The information processing unit
When the web page data is not requested, the web page to be displayed is formed by the user input command from the element data stored in the storage unit and the layout data stored in the storage unit. Select the data to be displayed,
When requesting data of the web page,
When at least one of the element data and the layout data is not stored in the storage means, the data not stored in the storage means is stored on the server side. And the Web page is displayed based on the data acquired from the server side and the data stored in the storage means. In a terminal device program that operates on a terminal device that requests web page data from the server side as a client side,
The Web page data acquired after requesting the Web page data to the server side is divided into element data forming the elements of the Web page and layout data defining the arrangement of the element data forming the Web page. A storage processing unit for storing in the storage means,
Whether to request data of the web page to be displayed by the user input command based on the data of the web page stored in the storage unit and the data of the web page to be displayed by the user command. And an information processing unit for determining
The information processing unit
When the web page data is not requested, the web page to be displayed is formed by the user input command from the element data stored in the storage unit and the layout data stored in the storage unit. Select the data to be displayed,
When requesting data of the web page,
When at least one of the element data and the layout data is not stored in the storage means, the data not stored in the storage means is stored on the server side. A terminal device program that displays the Web page based on the data acquired from the server side and the data stored in the storage means.

Images