JP2012099009A - Portable terminal device and display method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform information provision in a timely fashion according to the situation of a user.SOLUTION: A portable terminal device 103 includes a communication unit 201 for receiving ATOM feed and CSS, a display unit 204 for performing screen display based on the ATOM feed and the CSS received by the communication unit 201, and a position information acquisition unit 202 for acquiring current position information of the portable terminal device 103. The communication unit 201 receives the CSS according to the current position information acquired by the position information acquisition unit 202 and the display unit 204 updates the screen display according to the CSS acquired by the communication unit 201.

Description

  The present invention relates to a mobile terminal device and a display method of the mobile terminal device.

With the spread of network communications, services using communications have been created in various fields. In particular, an information providing service by transmitting data in a markup language such as XML (Extensible Markup Language) is widely performed.
Here, as an information providing method in the information providing service, a method in which information is stored in a server in a network and a user accesses the server using a terminal device to acquire information is generally used. In this method, in order for the user to know whether information has been updated, it is necessary to check whether the information has been updated by accessing the server using a terminal device and displaying the information on the browser. It was a hassle.

  In view of this, a mechanism that enables automatic acquisition of data update information by software called a feed reader is provided. The feed reader automatically acquires data update information stored in the server, for example, periodically, and notifies the user of the acquired data update information by browser display or the like. The data update information stored in this server is described in a document distribution format called a feed such as RSS (RDF Site Summery) 1.0, RSS 2.0, or ATOM.

  Further, as related to such an information providing service, Patent Document 1 discloses a method in which a plurality of users change a web application and web content through a network.

  Also, in Patent Document 2, when a network communication apparatus accepts an external request, it determines whether the request is RSS or HTML (Hyper Text markup Language). If it is determined to be RSS, XML response data is generated. A method of generating HTML response data when it is determined as HTML is shown.

  Also, in Patent Document 3, a network communication device that outputs communication history and job history as an XML document such as RSS uses a single Uniform Resource Locator (URL) of information output by RSS as one OPML (Outline Processor Markup Language). ) A method is shown in which URL data output by RSS can be centrally managed by outputting as a file.

  Further, in Patent Document 4, when there is a change in the state of data or the like held in an image processing apparatus such as a copying machine, the user is notified of the change and an image corresponding to the change item selected by the user. How to display is shown.

Special table 2009-531793 gazette JP 2008-21118 A JP 2006-246261 A JP 2006-324918 A

  The data update information obtained by the feed reader is information provided to an unspecified number of users. That is, the conventional feed reader cannot provide information in a timely manner according to the user's situation. Also, Patent Documents 1 to 4 do not disclose a technique for providing information in a timely manner according to the user's situation.

  The present invention has been made in view of such circumstances, and an object of the present invention is to provide a portable terminal device and a display method capable of providing information in a timely manner according to the user's situation.

  The present invention has been made to solve the above-described problems, and a mobile terminal device according to an aspect of the present invention is a mobile terminal device that performs wireless communication, and includes data including a plurality of display items, and the display items. A communication unit for acquiring data for selecting an item to be actually displayed from among the plurality of display items, a display unit for displaying the item to be actually displayed, and the portable terminal device A position information acquisition unit that acquires current position information of the communication unit, wherein the communication unit acquires data for selecting the item to be actually displayed according to the current position information, and the display unit Among the display items, an item indicated by data for selecting the item to be actually displayed according to the current position information acquired by the communication unit is displayed.

  The mobile terminal device according to an aspect of the present invention is the above-described mobile terminal device, wherein the communication unit includes an ATOM feed including the plurality of display items and an item to be actually displayed from the display items. The CSS to be selected is received.

  The mobile terminal device according to an aspect of the present invention is the above-described mobile terminal device, wherein the data including the plurality of display items is data indicating service information, and is displayed from the data including the plurality of display items. The communication unit further includes a management unit that reads an end time, and when the display end time arrives, the communication unit ends the display of the service information as data for selecting an item to be actually displayed from the display items. The data is acquired, and the display unit ends the display of the service information based on data for ending the display of the service information.

  Moreover, the portable terminal device by 1 aspect of this invention is the above-mentioned portable terminal device, Comprising: The said management part acquires the positional information on the shop which provides the said service from the data containing the said display item, The said portable terminal Based on the positional information between the apparatus and the store providing the service, a time for notifying that the display end time is approaching is set, and the communication unit notifies that the display end time is approaching. When the time arrives, data for notifying that the display end time is approaching is acquired as data for selecting an item to be actually displayed from among the display items, and the display unit is configured to display the plurality of display items. Among them, an item indicated by data for notifying that the display end time is approaching is displayed.

  In addition, a display method according to an aspect of the present invention is a display method of a mobile terminal device that performs wireless communication, and a communication unit displays data including a plurality of display items and items that are actually displayed from the display items. A first communication step for acquiring data for selecting the wireless communication, a first display step for displaying an item to be actually displayed among the plurality of display items, and a position information acquiring unit. A position information acquisition step of acquiring the current position information of the mobile terminal device; a second communication step of acquiring data for selecting the item to be actually displayed according to the current position information by the communication unit; A second display step of displaying an item indicated by data for selecting the item to be actually displayed according to the current position information acquired by the communication unit from among the plurality of display items. Characterized in that it.

  According to the present invention, information can be provided in a timely (timely) manner according to the user's situation.

1 is a system configuration diagram showing a schematic configuration of a service information providing system in an embodiment of the present invention. It is a block diagram which shows the outline of a function structure of the portable terminal device in the embodiment. It is a block diagram which shows the outline of a function structure of the process part at the time of feed reader execution of the portable terminal device of the embodiment. It is a data structure figure which shows the document structure of the feed prescribed | regulated by ATOM. It is a data structure figure which shows the document structure of the feed prescribed | regulated by ATOM. It is a table | surface explaining the content of each item shown by FIGS. It is a table | surface explaining the content of each item shown by FIGS. It is a table | surface explaining the content of each item shown by FIGS. In the same embodiment, it is a data structure figure which shows the data structure of the ATOM feed which a server apparatus transmits. In the same embodiment, it is a data structure figure which shows the data structure of the ATOM feed which a server apparatus transmits. It is a table | surface explaining the content of each item shown by FIGS. It is a table | surface explaining the content of each item shown by FIGS. It is a table | surface explaining the content of each item shown by FIGS. In the same embodiment, it is a figure which shows the example of the ATOM feed which a portable terminal device acquires. In the same embodiment, it is a figure which shows the example of id information and category information contained in the ATOM feed which a server apparatus transmits. In the embodiment, it is a figure which shows the example of CSS which a portable terminal device acquires. In the embodiment, it is a figure which shows the example of CSS which a portable terminal device acquires. In the embodiment, it is a figure which shows the example of CSS which a portable terminal device acquires. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. In the embodiment, it is a figure which shows the example of the screen which a portable terminal device displays on a display part. 4 is a flowchart illustrating a processing procedure in which the mobile terminal device acquires and displays service information in the embodiment. 4 is a flowchart illustrating a processing procedure in which the mobile terminal device acquires and displays service information in the embodiment. It is a sequence diagram which shows the process sequence of the service information regular update process in the embodiment. It is a flowchart which shows the process sequence of a visitor privilege information acquisition process in the embodiment. It is a flowchart which shows the process sequence of the additional service information acquisition process in the embodiment. It is a flowchart which shows the process sequence of the related service information acquisition process in the embodiment. It is a flowchart which shows the process sequence of the related service information acquisition process in the embodiment. It is a flowchart which shows the process sequence of id information comparison in the embodiment. 6 is a flowchart illustrating a processing procedure for setting a timer for service termination notification in the embodiment. FIG. 11 is a sequence diagram showing a flow of a file when the mobile terminal device displays the start of service and displays that when the service end time approaches in the embodiment. FIG. 6 is a sequence diagram showing a flow of a file when the mobile terminal device displays a service start and displays a service end after the service end time has elapsed in the embodiment.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a system configuration diagram showing a schematic configuration of a service information providing system according to an embodiment of the present invention. In FIG. 1, the service information providing system 1 includes a server device 101, one or more store side terminal devices 102, one or more portable terminal devices 103, and a network 104. The server device 101, the store side terminal device 102, and the mobile terminal device 103 are connected via a network 104 by wireless communication or wired communication. The mobile terminal device 103 is connected to the network 104 by wireless communication.

The server apparatus 101 provides information on a certain store. In particular, the server apparatus 101 provides information that is updated according to time, such as a time service. In addition, the server device 101 provides service information corresponding to the position of the mobile terminal device 103 so that the customer can receive a special service (customer privilege).
The mobile terminal device 103 acquires and displays information provided by the server device 101.
The store side terminal device 102 is installed in a store, and includes information transmission means such as an RF (Radio Frequency) device so that the mobile terminal device 103 can acquire store visitor privilege information. For example, when the mobile terminal device is brought close to the RF device, communication between the store-side terminal device 102 and the mobile terminal device 103 becomes possible, and the visitor privilege can be transmitted from the store-side terminal device 102 to the mobile terminal device 103. Become.

  Here, the server apparatus 101 uses a feed (an outline of the web content or the entire content for distribution in accordance with the document format of ATOM (XML document format for distributing content on the web and a communication protocol for editing content). Information is transmitted as a processed document). Hereinafter, a feed in accordance with the ATOM document format is referred to as an “ATOM feed”.

Then, the mobile terminal device 103 activates a feed reader (an application for acquiring and displaying a feed), requests the server device to transmit the feed, and displays the transmitted feed.
The mobile terminal device 103 also stores CSS (Cascading Style Sheets. Data files for designating HTML document decoration (character size, color, etc.)) used when displaying the feed received from the server device 101. 101.

  This system provides a special service when the user of the mobile terminal device 103 visits the store. In this way, the store that encourages the user to visit the store and provides the service is activated. Furthermore, this system also distributes information on service providing stores that exist adjacently as related information. Thereby, the effect of attracting customers can be expected even in the service providing stores that are adjacent to each other, and the number of customers can be increased synergistically.

  Further, in this system, a store that provides a service registers service information of the store in the server device 101 using an ATOM feed, and transmits an ATOM feed from the server device 101 in response to a request from the mobile terminal device 103. At that time, the server apparatus 101 transmits an ATOM feed based on the ATOM publication protocol. This ATOM publishing protocol is an HTTP-based communication protocol and conforms to the REST (Representational State Transfer) architecture.

  Specifically, the server apparatus 101 publishes ATOM feed document data described in XML on the website of a store that provides the service. Then, the feed reader executed on the mobile terminal device 103 automatically requests the server device 101 for an ATOM feed of the address of the website of the store that provides the service, at regular intervals. The server device 101 transmits an ATOM feed in response to a request from the mobile terminal device 103.

FIG. 2 is a configuration diagram illustrating an outline of a functional configuration of the mobile terminal device.
In the figure, a mobile terminal device 103 includes a communication unit 201, a position information acquisition unit 202, an operation input unit 203, a display unit 204, a processing unit 205, a storage unit 206, an imaging unit 207, and infrared communication. Unit 208, visible light communication unit 209, and RF unit 210.
The communication unit 201 transmits / receives data to / from the server apparatus 101 by wireless communication via the network 104 (FIG. 1). The position information acquisition unit 202 includes, for example, a GPS (Global Positioning System) and outputs information indicating the current position of the mobile terminal device 103.

The operation input unit 203 includes operation buttons such as a numeric keypad and accepts an operation input by a user.
The display unit 204 includes a display screen such as a liquid crystal display device or an organic EL display device, and displays an image including text, photos, and the like on the display screen based on the image data output from the processing unit 205.
The processing unit 205 is realized when a CPU (Central Processing Unit) included therein reads out a program from the storage unit 206, and controls each unit and processes data transmitted from the server device 101.
The storage unit 206 stores programs executed by the CPU and various data.

The imaging unit 207 includes a camera and performs imaging.
The infrared communication unit 208 includes an infrared transmitter and an infrared sensor and performs infrared communication.
The visible light communication unit 209 includes a light emitter that emits visible light and a visible light sensor, and performs data communication using visible light.
The RF unit 210 includes an antenna and performs data communication using high-frequency electromagnetic waves.
The imaging unit 207, the infrared communication unit 208, the visible light communication unit 209, and the RF unit 210 are used when acquiring a visitor benefit at a store. For example, the RF unit 210 becomes communicable by bringing it close to the RF device of the store-side terminal device 102 described above, and receives a visitor benefit from the store-side terminal device 102.

FIG. 3 is a configuration diagram illustrating an outline of a functional configuration of the processing unit 205 when the feed reader is executed.
In the figure, a processing unit 205 includes a communication processing unit 310, an application setting management unit 320, a feed document analysis unit 330, a memory data processing unit 340, a document data analysis unit 350, a system event processing unit 380, And a data drawing unit 390. The memory data processing unit 340 includes a data access unit 341 and a database function unit 342. The document data analysis unit 350 includes an XML document data analysis unit 360 and a script analysis unit 370. The XML document data analysis unit 360 includes an HTML document analysis unit 361, a CSS analysis unit 362, and an SVG analysis unit 363. The system event processing unit 380 includes a device / OS / timer event processing unit 381 and a UI component event processing unit 382. The data drawing unit 390 includes a font drawing unit 391, a document drawing unit 392, an image drawing unit 393, a moving image drawing unit 394, and a UI (User Interface) component drawing unit 395.

The communication processing unit 310 receives the output of reception data from the communication unit 201 (FIG. 2), and outputs transmission data to the communication unit 201.
The application setting management unit 320 manages the operation of each unit, manages data used in the application, and inputs / outputs data with other applications.

The feed document analysis unit 330 analyzes the feed document acquired by the communication processing unit 310. Then, the feed document analysis unit 330 reads the XML document data from the feed document and outputs it to the XML document data analysis unit 360. The feed document analysis unit 330 reads a script from the feed document and outputs the script to the script analysis unit 370.
The data access unit 341 reads / writes data by accessing the storage unit 206 (FIG. 2). The database function unit 342 provides database functions such as data search in the storage unit 206 and sorting and replacement of data read and written by the data access unit 341.

  The XML document data analysis unit 360 includes an HTML document analysis unit 361 that analyzes HTML documents, a CSS analysis unit 362 that analyzes CSS (Cascading Style Sheets), and SVG (Scalable Vector Graphics, a vector graphic language described in XML). SVG analysis unit 363 for analyzing the XML document is analyzed. Then, the XML document data analysis unit 360 reads the service information from the XML document and writes it into the storage unit 206 (FIG. 2) via the memory data processing unit 340. Also, the XML document data analysis unit 360 outputs the analysis result to the data drawing unit 390 so that the data drawing unit 390 performs drawing.

The script analysis unit 370 has a function related to script processing. Specifically, the script is analyzed, and the system event processing unit 380 is requested to execute necessary event processing and monitor event occurrence. In addition, the script analysis unit 370 outputs a drawing request to the data drawing unit 390 as necessary.
In the data drawing unit 390, the document drawing unit 392 controls the configuration of the entire display screen (arrangement of characters and photos). The font drawing unit 391 performs a character string drawing process using font data. The image drawing unit 393 performs still image drawing processing based on still image data such as JPPG, BMP, and PNG. The moving image drawing unit 394 draws a moving image based on the moving image data. The UI component drawing unit 395 draws a UI using a library related to UI components stored in advance in the storage unit 206.

  In the system event processing unit 380, the device / OS / timer event processing unit 381 performs interaction with the user and event processing generated from the device and OS. In particular, the device / OS / timer event processing unit 381 receives information indicating the user's operation input output from the operation input unit 203 and information indicating the current position of the mobile terminal device 103 output from the position information acquisition unit 202. Accept. The UI component event processing unit 382 performs event processing related to the UI component, such as a UI component display request.

4 to 5 are data structure diagrams showing the document structure of the feed defined by ATOM.
Moreover, FIGS. 6-8 is a table | surface explaining the content of each item shown by FIGS. As shown in these figures, for example, in the item of “id element data” (medium element) of “Feed document” (major element) shown in FIG. 4, the feed document is uniquely identified as shown in FIG. The identifier to be stored is stored.
In the ATOM rules, as shown in FIGS. 4 to 8, the rough structure of the feed is defined, and more detailed rules, for example, what kind of data is stored in each item, or The details of how to use the data stored in the feed can be freely determined by the person who generates the feed. In addition, as a service currently provided using an ATOM feed, for example, there is a service that provides update information, new arrival information, and the like of a web page with an ATOM feed and notifies a user.

In this system, an ATOM feed in which the rules shown in FIGS. 9 to 13 are added to the structure specified by ATOM is used.
9 to 10 are data structure diagrams showing the data structure of the ATOM feed transmitted by the server apparatus 101. FIG.
Moreover, FIGS. 11-13 is a table | surface explaining the content of each item shown by FIGS.
The server apparatus 101 uses the ATOM feed shown in FIGS. 9 to 13 to transmit service information whose service contents change depending on time and user behavior. The terminal device that has received this ATOM feed displays the feed information, thereby providing a new form of service to the user.

  The ATOM feed transmitted by the server apparatus 101 includes a header indicating XML version information applied to the ATOM feed, and include CSS file information for screen display when the feed is acquired (line L401 in FIG. 9, FIG. 11 line L501), include CSS file information for screen display at the start of service provision (line L402, L502), include CSS file information for setting display of each service (lines L403, L503), Include CSS file information (lines L404 and L504) for screen display at the end of service provision.

  The ATOM feed transmitted by the server apparatus 101 includes a feed document having the same structure as the feed document shown in FIGS. 4 and 5, but some items include the feed document shown in FIGS. 4 and 5. Stores information with different contents. For example, id information that uniquely identifies the ATOM feed is stored in the item of the id element data (lines L405 and L505). In addition, in the uri element data item (rows L406 and L506) in the author element, the acquisition destination address of the CSS file for performing screen display at the time of feed data acquisition is stored. In addition, in the uri element data item (lines L407 and L507) of the contributor element, the acquisition destination address of the CSS file for displaying the screen at the start of service provision is stored. In addition, the item of link element data (lines L408 and L508) stores an acquisition destination address of a CSS file for performing screen display at the end of service provision.

FIG. 14 is a diagram illustrating an example of an ATOM feed acquired by the mobile terminal device 103. This ATOM feed is composed of the document blocks shown in FIGS.
Whether or not the acquired ATOM feed has been updated from the previously acquired ATOM feed is determined by comparing id information (line L605) that uniquely identifies the ATOM feed. This id information corresponds to the id element data (row L405) in FIG. 9 and the element id (row L505) in FIG.

  The line L601 stores include CSS file information for screen display when the feed is acquired (corresponding to the line L401 in FIG. 9 and the line L501 in FIG. 11). The row L602 stores include CSS file information (rows L402 and L502) for screen display at the start of service provision. The line L603 stores include CSS file information (lines L403 and L503) for setting the display of each service. Line L604 stores include CSS file information (lines L404 and L504) for displaying a screen at the end of service provision.

  In addition, a row L606 stores a CSS file acquisition destination address (rows L406 and L506) for displaying a screen when the feed data is acquired. Further, in a row L607, a CSS file acquisition destination address (rows L407 and L507) for displaying a screen at the start of service provision is stored. Further, in a row L608, an acquisition destination address (rows L408 and L508) of a CSS file for displaying a screen at the end of service provision is stored.

FIG. 15 is a diagram illustrating an example of id information and category information included in an ATOM feed transmitted by the server apparatus 101.
As shown in the figure, the id information includes URL information a201, distribution date information a202, service number a203, and service branch number a204, and is enclosed by <id> tags to constitute a document block. Further, the URL information a201, the delivery date information a202, the service number a203, and the service branch number a204 are combined by “/” (slash) to form a series of character strings. This ATOM feed information is stored at the position of row L605 in the example of FIG.

When determining whether or not the ATOM feed is updated, the mobile terminal device 103 determines whether the ATOM feed stored in the storage unit 206 is based on whether the URL information a201, the distribution date information a202, and the service number a203 are the same. A comparison-target ATOM feed is selected, and whether or not the content is updated is determined based on whether or not the service branch number a204 is the same.
Therefore, when the content of the ATOM feed is updated with the same service, the server apparatus 101 determines that the URL information a201, the delivery date information a202, and the service number a203 are the same id information as that of the ATOM feed before the update. The distribution date information a202 stores and distributes the ATOM feed with the id information indicating the date and time of the first distribution instead of the update date and time.
The service branch number a204 is serial number character information starting from, for example, “0”. When the ATOM feed is updated, the server apparatus 101 stores and distributes the ATOM feed including the id information in which the value of the service branch number a204 is a value obtained by adding “1” to the value before the update.

In addition, the category information includes an area a205 indicating a term (category information character string such as a category name) and an area a206 indicating an acquisition destination address of CSS data for publishing a cooperation service (service belonging to the same category) in the category. Including.
This category information is stored at the position of row L610 in the example of FIG.

  16 to 18 are diagrams illustrating examples of CSS acquired by the mobile terminal device 103. “Style_Delivery.css” in FIG. 16A, “style_StartService.css” in FIG. 16B, “style_entry1.css” in FIG. 17A, and “style_entry2.css” in FIG. “Style_entry3.css” in FIG. 17C and “style_EndService.css” in FIG. 18 are CSS files, and indicate conditions such as colors and data to be displayed when the ATOM feed is displayed. Yes.

19 to 27 are diagrams illustrating examples of screens displayed on the display unit 204 by the mobile terminal device 103. FIGS. 19 to 27 show examples in which various screens are displayed from the same ATOM feed according to CSS.
FIG. 19 is a diagram illustrating an example of a screen that is displayed only with an ATOM feed, that is, without using CSS. The example in the figure is a display example when the ATOM feed shown in FIG. 14 is displayed without using CSS. In addition to the display text such as “notification of service provision” and “XX outlet service”, In addition to the display text such as the id information included in the row L605, text sandwiched between tags is displayed.

  FIG. 20 is a diagram illustrating an example of a screen when a feed is acquired. The screen shown in FIG. 16 is displayed by applying “style_Delivery.css” shown in FIG. 16A to the ATOM feed shown in FIG. In FIG. 16A, for example, “title” is set to be displayed (“display: black”), and a title “service provision notification” sandwiched between title tags is displayed.

FIG. 21 is a diagram illustrating an example of a screen for notifying the start of service provision, and is a diagram illustrating an example of a screen for displaying a provided service for each service. The screen shown in FIG. 14 is displayed by applying “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16A and 16B to the ATOM feed shown in FIG. The entry “entry title... Display: block” for displaying the title of the entry in FIG. 16 (b), the titles “store 1 provided service information”, “store 2 provided service information”, and “store 3 provided” "Service information" is displayed, and the setting "p.CommonUpDateServiceTitle ... display: block" to display "CommonUpDateServiceTitle", "Service at visit" and "Common update service 2-0" corresponding to CommonUpDateServiceTitle in each service Is displayed. Further, “common update service 1-0” corresponding to CommonUpDateServiceTitle is displayed by the setting “p.CommonUpDateServiceContents... Display: block” for displaying “CommonUpDateServiceContents”.
In addition, when the setting with respect to the same item is performed in multiple times, such as when applying a plurality of CSS files, the setting performed later becomes effective. For example, after “style_Delivery.css” is read and “entry {display: none;}” is set, “style_StartService.css” is read and “entry {display; block; padding-left: 2em; } ”Is set,“ entry {display; block; padding-left: 2em; Thereby, in the display screen shown in FIG. 21, each service information enclosed by the entry tag in the ATOM feed of FIG. 14 is displayed.

  FIG. 22 is a diagram illustrating an example of a screen that displays the content of a service for each provided service. The screen shown in FIG. 14 includes an ATOM feed shown in FIG. 14, “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16 (a) and 16 (b), and “ It is displayed by applying “style_entry1.css”, “style_entry2.css”, and “style_entry3.css”. With “style_entry1.css” in FIG. 17A, “service 1-1” corresponding to PrivateService1-1 and “content 1” corresponding to PrivateServiceContents1-1 are displayed. Also, “style_entry2.css” in FIG. 17B displays “service 2-1” corresponding to PrivateService2-1, “content 2” corresponding to PrivateServiceContents2-1, and a link to the page. . Further, “style_entry3.css” in FIG. 17C is used to describe “service 3-1” corresponding to PrivateService3-1, “content” corresponding to PrivateServiceContents3-1, and “service 3-” corresponding to PrivateService3-2. “2” is displayed.

  FIG. 23 is a diagram illustrating an example of a screen for notifying a completed service. The screen shown in FIG. 14 is displayed by applying “style_Delivery.css” shown in FIG. 16A and “style_EndService.css” shown in FIG. 18 to the ATOM feed shown in FIG. In FIG. 18, “EndService” is set to be displayed (“EndService... Display: block”), and the text “○ month ○ day” corresponding to the “<p class =" EndService ”>” tag in FIG. ”Has been completed” is displayed in the screen example of FIG. On the other hand, in FIG. 18, “StartService” is not displayed (“StartService... Display: none”), and the text “○ month” corresponding to the “<p class =" StartService ”>” tag in FIG. “Come to the XX block” is not displayed in the screen example of FIG.

FIG. 24 is a diagram illustrating an example of a screen that displays the provided service for each service and displays the contents of the service provided by the store 1. The screen shown in FIG. 14 includes an ATOM feed shown in FIG. 14, “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16A and 16B, and “style_entry1.css” shown in FIG. And is displayed by applying.
FIG. 25 is a diagram illustrating an example of a screen that displays the provided service for each service and displays the contents of the service provided by the store 2. The screen shown in FIG. 16 applies “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16A and 16B and “style_entry2.css” shown in FIG. 17B to the ATOM feed. Is displayed.

FIG. 26 is a diagram illustrating an example of a screen that displays the provided service for each service and displays the contents of the service provided by the store 3. The screen shown in FIG. 16 applies “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16A and 16B and “style_entry3.css” shown in FIG. 17C to the ATOM feed. Is displayed.
FIG. 27 is a diagram illustrating an example of a screen that displays the provided service for each service, and displays the content of the service provided by the store 1 and the content of the service provided by the store 2. The screen shown in FIG. 16 includes an ATOM feed, “style_Delivery.css” and “style_StartService.css” shown in FIGS. 16A and 16B, and “style_entry1.css” shown in FIGS. 17A and 17B. And “style_entry2.css” are applied.

  As described above, the mobile terminal device 103 can acquire one ATOM feed and display the screen in various forms. As shown in FIGS. 14 and 16 to 18, the data amount (file size) is smaller in CSS than in ATOM feed. Therefore, the mobile terminal device 103 applies the newly received CSS to the previously received ATOM feed to update the screen display, so that the communication data is received rather than receiving the ATOM feed every time the screen display is updated. The amount can be reduced, and the load on the mobile terminal device 103, the server device 101, and the network 104 can be suppressed.

Next, the operation of the mobile terminal device 103 will be described with reference to FIGS.
FIG. 28 is a flowchart illustrating a processing procedure for the mobile terminal device 103 to acquire and display service information. When the feed reader (application) is automatically activated from the user or the system, the mobile terminal device 103 starts the processing in FIG.
First, the application setting management unit 320 outputs a signal instructing the UI component drawing unit 395 to draw a URL registration necessity inquiry screen via the UI component event processing unit 382. The UI component drawing unit 395 displays an inquiry screen on the display unit 204 in accordance with an instruction from the application setting management unit 320. Then, the application setting management unit 320 waits for a registration necessity instruction output from the operation input unit 203 via the device / OS / timer event processing unit 381 (step S101), and registers based on the instruction. Is determined (step S102).

When it is determined that the instruction from the user does not instruct the registration of the URL (step S102: NO), the application setting management unit 320 accesses the storage unit 206 via the data access unit 341, and acquires the service information acquisition target. It is determined whether or not the URL of the site is stored (step S111).
If it is determined that the URL is not stored (step S111: NO), since there is no service information acquisition target site, the mobile terminal device 103 ends the feed reader (application) and ends the processing in FIG. To do.
On the other hand, if it is determined in step S111 that the URL is stored, the process proceeds to step S121.
If it is determined in step S102 that the instruction from the user instructs registration of the URL (step S102: YES), the application setting management unit 320 registers the URL according to the user operation (step S102). S103), the process proceeds to step S121.

  Then, the application setting management unit 320 instructs the device / OS / timer event processing unit 381 to start a periodic update timer, and the device / OS / timer event processing unit 381 starts an internal periodic update timer. The count is started (step S121). Here, the periodic update timer is a timer indicating the timing for confirming whether or not there is service information update at the site where the service information is to be acquired. In other words, the mobile terminal device 103 periodically accesses the service information acquisition target site, and acquires the service information when the service information is updated. The periodic update timer is a timer for counting the periodic access cycle.

After that, the application setting management unit 320 determines whether or not the operation input unit 203 has received a user operation input that instructs to end the feed reader (step S122). If it is determined that a feed reader end instruction has been received (step S122: YES), the mobile terminal device 103 ends the feed reader (application) and ends the processing in FIG.
On the other hand, when it is determined that the feed reader termination instruction has not been received (step S122: NO), the application setting management unit 320 is preset with the value of the periodic update timer included in the device / OS / timer event processing unit 381. It is determined whether or not the confirmation interval time is over (step S131). When it determines with it being more than confirmation interval time (step S131: YES), the portable terminal device 103 performs regular update process step S132. This periodic update process is a process for periodically checking whether or not the service information has been updated for a site whose URL is registered as a service information acquisition target, and acquiring the updated service information. Thereafter, the process returns to step S122.

On the other hand, if it is determined in step S131 that the time is less than the confirmation interval time (step S131: NO), the application setting management unit 320 has received an operation input instructing to acquire the visitor privilege information. It is determined whether or not (step S141).
This store visitor privilege information is information indicating a special service (store visitor privilege) provided to the store visitor by the store side. The visitor benefit may be a privilege that can be used immediately, such as the distribution of prizes on the spot, product discounts or point grants, or a benefit that can be used at a later date, such as a discount at the next visit. .

When it is determined that there is an instruction to acquire the visitor privilege information (step S141: YES), the mobile terminal device 103 performs a process of acquiring the visitor privilege information (step S142). Thereafter, the process returns to step S122.
On the other hand, if it is determined in step S141 that there has been no instruction to acquire the visitor benefit information (step S141: NO), the application setting management unit 320 determines each service from the acquired service information stored in the storage unit 206. Is read out (step S151). This service end time is the end time of the service defined for the limited-time service.

Then, the application setting management unit 320 compares the read end time of each service with the current time, and determines whether there is a service whose service end time has arrived (step S152). As will be described later, the mobile terminal device 103 can detect a service whose service end time has arrived using a timer.
If it is determined that there is a service whose service end time has arrived (step S152: YES), the mobile terminal device 103 performs a process of terminating the service whose service end time has arrived. Specifically, the application setting management unit 320 transmits an HTTP request for requesting a CSS to the server apparatus 101 via the communication processing unit 310 and the communication unit 201, and acquires the CSS (step S153). Then, the document data analysis unit 350 analyzes the acquired CSS and the ATOM feed stored in the storage unit 206, and causes the display unit 204 to display a message indicating that the service has ended via the data drawing unit 390, In addition, the contents of the service are not displayed (hidden from the user. Step S154). Thereafter, the process returns to step S122.

On the other hand, when it is determined in step S152 that there is no service whose service end time has arrived (step S152: NO), the application setting management unit 320 determines whether there is a service whose service end notification time has not been set ( Step S161).
The service end notification time is a time set to notify the user that the service end time is approaching, and is set, for example, to a time before a certain time from the service end time. Alternatively, as described later, the time is set according to the distance between the mobile terminal device 103 and the service providing store.
If it is determined that there is a service for which the service end notification time has not been set (step S161: YES), the mobile terminal device 103 performs processing for setting the service end notification time (step S162). By notifying the user that the service end time is approaching, the user can be prevented from accepting the service. Also, the store side can expect users to visit the store. Thereafter, the process returns to step S122.

On the other hand, if it is determined in step S153 that the service end notification time is set for all services (step S161: NO), the process returns to step S122.
If it is determined in step S101 that the URL of the service information acquisition target site is stored (step S101: YES), the process proceeds to step S121.

FIG. 29 is a flowchart showing a URL registration process. The process shown in FIG. 28 is performed in step S103 of FIG.
First, the application setting management unit 320 instructs the UI component drawing unit 395 via the UI component event processing unit 382 to display a URL registration work start message indicating that the URL registration work is to be started. The unit 395 displays a URL registration work start message on the display unit 204 (step S201). Then, the application setting management unit 320 waits for the operation input unit 203 to accept an input operation for selecting a URL registration method (step S202). When the operation input unit 203 accepts the input operation, the application setting management unit 320 acquires information indicating the input operation via the device / OS / timer event processing unit 381 and corresponds to the selected registration method. A process is selected (step S203).

  When the movement to the URL registration site is selected (step S203: URL registration site), the application setting management unit 320 instructs the UI component event processing unit 382 to acquire the URL of the URL registration site. Upon receiving the instruction, the UI component event processing unit 382 instructs the data drawing unit 390 to start the browser, and the data drawing unit 390 displays the browser on the display unit 204 (step S211).

In this state, when the operation input unit 203 receives an operation input instructing movement to a URL registration target site, the mobile terminal device 103 moves to the instructed site (step S212).
Specifically, the document data analysis unit is configured so that the device / OS / timer event processing unit 381 acquires information indicating the operation input and transmits a signal requesting display data (HTTP data or the like) of the designated site. 350. The document data analysis unit 350 generates an HTTP request including the address of the designated site, and transmits the HTTP request to the server apparatus 101 via the communication processing unit 310 and the communication unit 201. When the designated site display data is transmitted from the server apparatus 101, the document data analysis unit 350 acquires the data via the communication unit 201 and the communication processing unit 310, and the screen information of the site is displayed as the data drawing unit. To 390. The data drawing unit 390 generates image data based on the screen information output from the document data analysis unit 350 and causes the display unit 204 to display the image of the site.

When the URL is moved to the URL registration target site, the feed document analysis unit 330 reads the URL of the site from the received data from the server apparatus 101 and outputs the URL to the application setting management unit 320 (step S213).
The application setting management unit 320 writes the URL of the site in the storage unit 206 via the memory data processing unit 340 (step S271). When the writing to the storage unit 206 is completed, the application setting management unit 320 instructs the UI component event processing unit 382 to display a registration completion message. In accordance with an instruction from the application setting management unit 320, the UI component event processing unit 382 displays a registration completion message on the display unit 204 via the data drawing unit 390 (step S272). Thereafter, the process of FIG.

  On the other hand, when reading of a code is selected as a registration method in step S203 (step S203: code reading), the application setting management unit 320 sends a code such as a barcode to the device / OS / timer event processing unit 381. Instruct reading. Receiving the instruction, the device / OS / timer event processing unit 381 activates the imaging unit 207, captures the code according to the user's operation input, and acquires the code data (step S222). Then, the device / OS / timer event processing unit 381 reads the URL to be registered from the acquired code data, and outputs the URL to the application setting management unit 320 (step S223). Thereafter, the process proceeds to step S271.

  On the other hand, when direct input of URL is selected as the registration method in step S203 (step S203: URL direct input), the application setting management unit 320 displays a character input screen on the UI component event processing unit 382. Instruct. Upon receiving the instruction, the UI component event processing unit 382 causes the display unit 204 to display a character input screen via the UI component drawing unit 395 (step S231). When the operation input unit 203 receives a URL character string input operation by the user, the application setting management unit 320 acquires the URL character string via the device / OS / timer event processing unit 381 (step S232). Thereafter, the process proceeds to step S271.

  On the other hand, when infrared communication is selected as the registration method in step S203 (step S203: infrared communication), the application setting management unit 320 acquires a character string by infrared communication with respect to the device / OS / timer event processing unit 381. Instruct. Receiving the instruction, the device / OS / timer event processing unit 381 activates the infrared communication unit 208 and waits for reception of data by infrared (step S241). When receiving the data, the infrared communication unit 208 outputs the data to the device / OS / timer event processing unit 381 (step S242). The device / OS / timer event processing unit 381 extracts the URL character string from the data output from the infrared communication unit 208 and outputs the URL character string to the application setting management unit 320 (step S243). Thereafter, the process proceeds to step S271.

  On the other hand, when visible light communication is selected as the registration method in step S203 (step S203: visible light communication), the application setting management unit 320 uses the visible light communication to the device / OS / timer event processing unit 381. Instructs acquisition of a character string. Upon receiving the instruction, the device / OS / timer event processing unit 381 activates the visible light communication unit 209 and waits for reception of data by visible light (step S251). When receiving the data, the visible light communication unit 209 outputs the data to the device / OS / timer event processing unit 381 (step S252). The device / OS / timer event processing unit 381 extracts a URL character string from the data output from the visible light communication unit 209, and outputs the URL character string to the application setting management unit 320 (step S253). Thereafter, the process proceeds to step S271.

  On the other hand, when RFID is selected as the registration method in step S203 (step S203: RFID), the application setting management unit 320 instructs the device / OS / timer event processing unit 381 to acquire a character string using RFID. . Receiving the instruction, the device / OS / timer event processing unit 381 activates the RF unit 210 and waits for reception of data using a radio frequency (RF) (step S261). When receiving the data, the RF unit 210 outputs the data to the device / OS / timer event processing unit 381 (step S262). The device / OS / timer event processing unit 381 extracts the URL character string from the data output from the RF unit 210 and outputs the URL character string to the application setting management unit 320 (step S263). Thereafter, the process proceeds to step S271.

FIG. 30 is a sequence diagram illustrating a processing procedure for regular update processing of service information. The process shown in FIG. 28 is performed in step S132 in FIG. That is, in step S131, when the application setting management unit 320 determines that the value of the periodic update timer is equal to or greater than the preset confirmation interval time, the process of FIG. 30 is performed.
First, the application setting management unit 320 acquires the URL of the service information acquisition target site stored in the storage unit 206, and requests an ATOM feed including information on each site via the communication processing unit 310 and the communication unit 201. An HTTP request is transmitted to the server apparatus 101, and an ATOM feed is acquired. In addition, the application setting management unit 320 acquires the ATOM feed stored in the storage unit 206 (step S301). In addition, acquisition of the ATOM feed from the server apparatus 101 in step S301 is an example of acquisition of data including a plurality of display items in the first communication step of the present invention.

Next, the application setting management unit 320 compares the id information included in the ATOM feed acquired from the server device 101 with the id information included in the ATOM feed read from the storage unit 206, thereby updating the service information. The presence or absence is determined (step S302). If it is determined that the id information does not match (step S302: NO), the service information has been updated. Therefore, the application setting management unit 320 writes the ATOM feed acquired from the server device 101 into the storage unit 206 via the memory data processing unit 340 (step S311). Then, a screen for notifying data update is displayed on the display unit 204 via the UI component event processing unit 382 and the data drawing unit 390 (step S312). For example, the application setting management unit 320 causes the display unit 204 to display a screen for notification of feed acquisition as illustrated in FIG. In this screen, for example, in step S301, the application setting management unit 320 acquires the CSS shown in FIG. 16A together with the ATOM feed shown in FIG. 14 from the server apparatus 101, and applies the acquired CSS to the acquired ATOM feed. Obtained. In addition, acquisition of CSS shown to Fig.16 (a) from the server apparatus 101 in step S301 is an example of acquisition of the data which select the item actually displayed in the 1st communication step of this invention. Moreover, the display of the screen which notifies the service provision start by the display part 204 in step S312 is an example of the 1st display step of this invention.
The application setting management unit 320 instructs the device / OS / timer event processing unit 381 to reset the periodic update timer, and the device / OS / timer event processing unit 381 resets the periodic update timer to newly The count is started (step S313). Thereafter, the process of FIG.

  On the other hand, when it is determined in step S302 that the id information matches (step S302: YES), the service information is not updated. Therefore, the application setting management unit 320 discards the ATOM feed acquired from the server device 101 (step S321). Thereafter, the process proceeds to step S313.

FIG. 31 is a flowchart showing a processing procedure of store visitor privilege information acquisition processing. The process shown in FIG. 28 is performed in step S142 in FIG.
First, the application setting management unit 320 instructs the UI component drawing unit 395 through the UI component event processing unit 382 to display a store visitor registration information acquisition start message indicating that the store visitor registration information acquisition process is started. Then, the UI component drawing unit 395 displays a store visitor registration information acquisition start message on the display unit 204 (step S401).

Next, the application setting management unit 320 acquires information indicating the current position of the mobile terminal device 103 from the position information acquisition unit 202 via the device / OS / timer event processing unit 381 (step S402). The acquisition of information indicating the current position in step S402 is an example of a position information acquisition step in the present invention.
Then, the application setting management unit 320 determines whether or not the current position of the mobile terminal device 103 is within a range where the visitor benefit can be received, that is, whether the current position of the mobile terminal device 103 is in a store that provides the visitor benefit. It is determined whether or not (step S403). The information on the area where the store visitor benefit can be received is included in the ATOM feed as part of the service information, for example, and the application setting management unit 320 places the mobile terminal device 103 in the area indicated by the information read from the ATOM feed. It is determined whether or not the current position is included.

  When it is determined that the user is within the range where the customer benefit can be received (step S403: YES), the application setting management unit 320 waits for the operation input unit 203 to accept an input operation for selecting a method for registering the customer privilege information ( Step S411). When the operation input unit 203 accepts the input operation, the application setting management unit 320 acquires information indicating the input operation via the device / OS / timer event processing unit 381 and corresponds to the selected registration method. A process is selected (step S412). Here, the user selects one of code reading such as a bar code, infrared communication, visible light communication, or RFID as a registration method that can be performed only by the store visitor.

  In step S412, when code reading is selected as the registration method (step S412: code reading), the process proceeds to step S421. Steps S421 to S423 are the same as steps S221 to S223 in FIG. And the application setting management part 320 accesses the site of read URL, and acquires the CSS data for displaying visitor privilege information (step S424). The acquisition of CSS data in step S424 is an example of the second communication step of the present invention. The same applies to steps S433, S444, and S454 described below.

The application setting management unit 320 writes the acquired CSS data into the storage unit 206 via the memory data processing unit 340 (step S461).
Then, the document data analysis unit 350 analyzes the ATOM feed and CSS data stored in the storage unit 206, and outputs the analysis result to the data drawing unit 390. The data drawing unit 390 generates image data for displaying the visitor benefit information based on the analysis result output from the document data analysis unit 350 and outputs the image data to the display unit 204. The display unit 204 displays the visitor privilege information according to the image data output from the data drawing unit 390 (step S462). Note that the display of the visitor privilege information in step S462 is an example of a second display step of the present invention.

Next, the application setting management unit 320 determines whether there is an additional service (step S481). Here, the additional service is a service that can be further received by a user who has received a visitor benefit. For example, the visitor benefit is a point grant that can be obtained immediately upon visiting the store, and the additional service is a discount privilege that can be used at the next visit. The presence / absence of the additional service is described in the ATOM feed, and the application setting management unit 320 determines the presence / absence of the additional service based on the presence / absence of the description.
If it is determined that there is an additional service (step S481: YES), the mobile terminal device 103 performs processing for acquiring additional service information (step S482).
Thereafter, the process of FIG.

On the other hand, when it is determined in step S403 that the current position of the mobile terminal device 103 is not within the range where the customer benefit can be received (step S403: NO), the application setting management unit 320 performs the UI component event processing unit 382 and the data drawing. Via the unit 390, the display unit 204 is informed that the customer benefit cannot be received and a message prompting the user to move to the store is displayed.
Thereafter, the process of FIG.

  On the other hand, if infrared communication is selected as the registration method in step S412, the process proceeds to step S431. Steps S431 to S432 are the same as steps S241 to S242 in FIG. The device / OS / timer event processing unit 381 extracts CSS data from the data output from the infrared communication unit 208 and outputs the CSS data to the application setting management unit 320 (step S433). Thereafter, the process proceeds to step S461.

  On the other hand, in step S412, when visible light communication is selected as the registration method (step S412: visible light communication), the process proceeds to step S441. Steps S441 to S443 are the same as steps S251 to S253 in FIG. Then, the application setting management unit 320 accesses the site of the read URL and acquires CSS data for displaying the visitor benefit information (step S444). Thereafter, the process proceeds to step S461.

  On the other hand, in step S412, when RFID is selected as the registration method (step S412: RFID), the process proceeds to step S451. Steps S451 to S453 are the same as steps S261 to S263 in FIG. Then, the application setting management unit 320 accesses the site of the read URL and acquires CSS data for displaying the visitor privilege information (step S454). Thereafter, the process proceeds to step S461.

  On the other hand, if it is determined in step S481 that there is no additional service (step S481: NO), the processing in FIG.

FIG. 32 is a flowchart illustrating a processing procedure of additional service information acquisition processing. The process shown in FIG. 31 is performed in step S482 in FIG.
Steps S501 to S554 are the same as steps S401 to S454 in FIG.
In step S561, the application setting management unit 320 determines whether CSS data is already stored in the storage unit 206. When it determines with having memorize | stored (step S561: YES), the application setting management part 320 overwrites the acquired CSS data on the memory | storage part 206 via the memory data processing part 340 (step S571).

  Then, the document data analysis unit 350 analyzes the ATOM feed and CSS data stored in the storage unit 206, and outputs the analysis result to the data drawing unit 390. The data drawing unit 390 generates image data for displaying additional service information based on the analysis result output from the document data analysis unit 350 and outputs the image data to the display unit 204. The display unit 204 displays the additional service information according to the image data output from the data drawing unit 390 (step S582). Thereafter, the process of FIG.

On the other hand, when it is determined in step S561 that CSS data is not stored in the storage unit 206 (step S561: NO), the application setting management unit 320 stores the acquired CSS data via the memory data processing unit 340. The data is written in the unit 206 (step S581). Thereafter, the process proceeds to step S582.
On the other hand, when it is determined in step S503 that the current position of the mobile terminal device 103 is not within the range where the customer benefit can be received (step S503: NO), the application setting management unit 320 performs the UI component event processing unit 382 and the data drawing. Via the unit 390, a message (error display) is displayed on the display unit 204 that informs that the additional service cannot be received and prompts the user to move to the store.
Thereafter, the process of FIG.

In addition to the additional service, a related service may be provided to the user who has received the visitor benefit. Here, the related service is service information of a nearby store. For example, the related service is a discount privilege at a nearby store. By providing a service to a user who has visited the store, that is, a user in the vicinity of a nearby store, it can be expected that the user will visit the nearby store.
33 to 34 are flowcharts showing the processing procedure of the related service information acquisition processing. The process shown in FIG. 31 is performed in step S482 in FIG. 31 instead of the process described in FIG.

  Steps S601 to S612 are the same as steps S501 to S512 in FIG. Steps S621 to S623 are the same as steps S521 to S523 in FIG. Steps S631 to S632 are the same as steps S531 to S532 in FIG. Steps S641 to S643 are the same as steps S541 to S543 in FIG. Steps S651 to S653 are the same as steps S551 to S553 in FIG.

  In steps S624, S633, S644, and S654, the application setting management unit 320 acquires category information in addition to the CSS data. The category information is information indicating the range of related services provided to the user. As category information, for example, store type information can be used. For example, service information on an exercise facility such as a tennis court is provided to a user using a sports equipment store.

Steps S661 to S682 are the same as steps S561 to S582 in FIG.
In step S701 in FIG. 34, the application setting management unit 320 determines whether or not the acquired category information matches the category information included in the ATOM feed.
In the ATOM feed, category information is included as category element data (row L414 in FIG. 9, row L610 in FIG. 14). Therefore, the application setting management unit 320 reads out the category information from the ATOM feed data stored in the storage unit 206 via the memory data processing unit 340, and determines whether or not it matches the category information acquired together with the CSS data.
Here, the URL of the storage destination of CSS data is stored in the ATOM feed along with the category information. If it is determined in step S701 that the category information matches (step S701: YES), the application setting management unit 320 acquires CSS data based on the URL (step S711). Steps S712 to S732 are the same as steps S661 to 682 in FIG.

On the other hand, when it is determined in step S603 that the current position of the mobile terminal device 103 is not within the range where the additional service can be received (step S403: NO), the application setting management unit 320 displays the UI component event processing unit 382 and the data drawing unit. Through 390, a message (error display) that informs the display unit 204 that the customer benefit cannot be received and prompts the user to move to the store is displayed (step S691).
Thereafter, the process of FIG.

FIG. 35 is a flowchart showing the id information comparison process. The process shown in FIG. 30 is performed in step S302 in FIG.
The application setting management unit 320 first determines whether or not an ATOM feed has already been written in the storage unit 206 (step S801). If it is determined that data has not been written (step S801: NO), the process proceeds to step S311.

  On the other hand, if it is determined in step S801 that the ATOM feed has already been written in the storage unit 206 (step S801: YES), the URL information of the acquired ATOM feed and the URL of the ATOM feed written in the storage unit 206 are determined. It is determined whether or not the information matches (step S802). If it is determined that they do not match (step S802: NO), the process proceeds to step S311.

  On the other hand, if it is determined in step S802 that the URL information matches (step S802: YES), whether the acquired date and time information of the ATOM feed matches the date and time information of the ATOM feed written in the storage unit 206 or not. Is determined (step S803). If it is determined that they do not match (step S803: NO), the process proceeds to step S311.

  On the other hand, if it is determined in step S803 that the date and time information matches (step S803: YES), whether or not the acquired service number of the ATOM feed matches the service number of the ATOM feed written in the storage unit 206 or not. Is determined (step S804). If it is determined that they do not match (step S804: NO), the process proceeds to step S311.

On the other hand, if it is determined in step S804 that the service numbers match (step S804: YES), does the acquired service branch number of the ATOM feed match the service branch number of the ATOM feed written in the storage unit 206? It is determined whether or not (step S805). If it is determined that they do not match (step S805: NO), the process proceeds to step S311.
On the other hand, if it is determined in step S805 that the service branch numbers match (step S805: YES), the process proceeds to step S321.

FIG. 36 is a flowchart showing a processing procedure for timer setting for service end notification (service end notification time setting). The process shown in FIG. 28 is performed in step S162 in FIG.
First, the application setting management unit 320 acquires the current position information of the mobile terminal device 103 output from the position information acquisition unit 202 via the device / OS / timer event processing unit 381 (step S821).
Next, the application setting management unit 320 acquires the location information of the service providing store. The location information of the service providing store is stored in the rights element (row L412 in FIG. 9, row L612 in FIG. 14) of the ATOM feed (step S822).

Then, the application setting management unit 320 calculates the distance between the mobile terminal device 103 and the service providing store from the current position of the mobile terminal device 103 and the position of the service providing store (step S823).
In addition, the application setting management unit 320 acquires the service end time. This service end time is stored in the Update element of the ATOM feed (row L413 in FIG. 9 and row L613 in FIG. 14). Then, the application setting management unit 320 calculates the remaining time until the service end from the difference between the service end time and the current time (step S824).

Then, the application setting management unit 320 sets the timer value by determining the time until the service end notification is started from the distance between the mobile terminal device 103 and the service providing store and the remaining time until the service ends. The timer starts counting (step S825). For example, as the distance between the mobile terminal device 103 and the service providing store increases, the start of the service end notification is advanced so that the user can reach the service providing store with a margin.
Thereafter, the process of FIG.

  When the set time elapses, the application setting management unit 320 acquires the CSS from the server apparatus 101, and the service end time is approaching based on the acquired CSS and the ATOM feed stored in the storage unit 206. A message prompting the customer to notify the store is displayed on the display unit 204 via the system event processing unit 380, the document data analysis unit 350, and the data drawing unit 390.

Next, a data flow in the service information providing system 1 will be described with reference to FIGS.
FIG. 37 is a sequence diagram illustrating the flow of a file when the mobile terminal device 103 displays the start of service and displays when the service end time approaches. First, the mobile terminal device 103 reads the URL of the service information acquisition target site stored in the storage unit 206, and transmits an HTTP request for requesting transmission of an ATOM feed to the site of the server device 101 (sequence S841). ). The server apparatus 101 that acquired this request returns an ATOM feed (sequence S842).
The mobile terminal device 103 that has received the ATOM feed saves the received ATOM feed in the storage unit 206 (sequence S843), and analyzes the received ATOM feed to read out the CSS request destination address for service start display (sequence). S844).

Then, the mobile terminal device 103 transmits an HTTP request for requesting the service start display CSS to the service start display CSS request destination of the server device 101 (sequence S845). The server apparatus 101 that acquired this request returns a CSS (sequence S846).
The mobile terminal device 103 that has received the CSS stores the received CSS (sequence S847), and displays a screen indicating service start based on the ATOM feed and the CSS (sequence S848).

In addition, the mobile terminal device 103 sets a timer for notifying the timing for notifying that the service end time is approaching, and starts counting. At this time, as described with reference to FIG. 36, a timer value is set according to the distance between the user and the service providing store (sequence S849).
When the time set in the timer elapses (sequence S850), the mobile terminal device 103 reads out the CSS request destination address for notifying that the service end time is approaching from the ATOM feed, and the request destination of the server device 101 An HTTP request for requesting CSS for notifying that the service end time is approaching is transmitted (sequence S851). The server apparatus 101 that has acquired this request returns the CSS (sequence S852). The mobile terminal device 103 displays a screen for notifying that the service end time is approaching, based on the CSS and the ATOM feed.

  FIG. 38 is a sequence diagram showing the flow of a file when the mobile terminal device 103 displays the start of service and displays that the service has ended after the service end time has elapsed. Sequences S861 to S868 in the figure are the same as sequences S841 to S848 in FIG.

In addition, the mobile terminal device 103 sets a timer for informing the service end timing, and starts counting (sequence S869).
When the time set in the timer elapses (sequence S870), the mobile terminal device 103 reads out the CSS request destination address for the service end processing from the ATOM feed, and sends the service end processing address to the request destination of the server device 101. For this purpose, an HTTP request for requesting CSS is transmitted (sequence S871). The server apparatus 101 that acquired this request returns the CSS (sequence S872). Based on the CSS and the ATOM feed, the mobile terminal device 103 displays a screen for notifying the end of the service.

As described above, since the mobile terminal device 103 updates the display contents according to the distance between the mobile terminal device 103 and the service providing store, it is possible to provide information in a timely manner according to the user's situation.
Further, when changing the display, the mobile terminal device 103 acquires a CSS, and selects a display item from the acquired items of the ATOM feed based on the CSS. Thereby, the portable terminal device 103 does not need to receive an ATOM feed for each display update. As shown in FIG. 14 and FIGS. 16 to 18, the amount of data can be reduced by communicating the display change information by CSS rather than by ATOM feed, and the load on the mobile terminal device 103 and the server device 101 can be suppressed. Can do.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like without departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 Service information provision system 101 Server apparatus 102 Shop side terminal device 103 Portable terminal device 201 Communication part 202 Position information acquisition part 203 Operation input part 204 Display part 205 Processing part 206 Storage part 207 Imaging part 208 Infrared communication part 209 Visible light communication part 210 RF unit 104 network

Claims (5)

A mobile terminal device that performs wireless communication,
A communication unit that acquires data including a plurality of display items and data for selecting an item to be actually displayed from the display items by the wireless communication;
Of the plurality of display items, a display unit that displays the items that are actually displayed;
A position information acquisition unit for acquiring current position information of the mobile terminal device;
Comprising
The communication unit obtains data for selecting an item to be actually displayed according to the current position information,
The display unit displays an item indicated by data for selecting the item to be actually displayed according to the current position information acquired by the communication unit from among the plurality of display items.
The portable terminal device characterized by the above-mentioned.   The mobile terminal apparatus according to claim 1, wherein the communication unit receives an ATOM feed including the plurality of display items and a CSS for selecting an item to be actually displayed from the display items. The data including the plurality of display items is data indicating service information,
Further comprising a processing unit for reading a display end time from the data including the plurality of display items,
When the display end time arrives, the communication unit acquires data for ending display of the service information as data for selecting an item to be actually displayed from the display items,
The portable terminal device according to claim 1, wherein the display unit ends the display of the service information based on data for ending the display of the service information. The management unit acquires location information of a store that provides the service from data including the display item, and the display end time approaches based on location information between the mobile terminal device and the store that provides the service. Set the time to notify
When the time for notifying that the display end time is approaching comes, the communication unit notifies that the display end time is approaching as data for selecting an item to be actually displayed from the display items. To get data
The display unit displays an item indicated by data notifying that the display end time is approaching among the plurality of display items.
The mobile terminal device according to claim 3. A display method for a mobile terminal device that performs wireless communication,
A first communication step in which the communication unit acquires data including a plurality of display items and data for selecting an item to be actually displayed from the display items by the wireless communication;
A first display step in which the display unit displays the item to be actually displayed among the plurality of display items;
A position information acquisition unit that acquires current position information of the mobile terminal device; and
A second communication step in which the communication unit acquires data for selecting an item to be actually displayed according to the current position information;
A second display step for displaying an item indicated by data for selecting the item to be actually displayed according to the current position information acquired by the communication unit from among the plurality of display items;
A display method comprising:

Images