JP2009145982A - Service management server, service information provision method, and service information distribution program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable use of service connected to a position near a mobile device when moving to a location which recommends the most desirable service available at the present positions of the user of the mobile device. <P>SOLUTION: A service management server which extracts available services among a plurality of services which are provided to a terminal device via a network from one or a plurality of service providing servers, and provides the information about the extracted service to the terminal device includes: a service extraction means to extract a plurality of services which match the current position concerned responding to a request accompanied by a current position from the terminal device; a preference degree calculation means which calculates a preference degree for each extracted service based on the service use history of a user of the terminal device registered beforehand into a database; and an information transmission means to transmit information about service of all or a part of the extracted services and information which shows the preference degree for each service to the terminal device. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a system of software applications, and more particularly, to user preferences and mobile devices through a user interface that is composed of specific data received from a server that provides a specific service and is dynamically generated (created). Technical field of automatic location-based service discovery and service recommendation based on service usage in

  The global position finding function represented by GPS is becoming a standard feature of mobile devices such as mobile phones, PDAs (Personal Data Assistants), and laptops.

  Therefore, for handheld mobile devices, there is an increasing demand for new software that utilizes the location finding function, and many applications have already been developed by many companies around the world. One example is navigation software, which is accepted by the market.

  On the other hand, many of the technological innovations in the area of the location finding function described above are merely services that provide functions or information to users through mobile applications installed in devices that operate according to the location of mobile devices. . In other words, the development of services that only use location information is focused, and instead of creating an application that requires users to install in advance, it is possible to connect a specific location and the individual service to be provided without installing the application. A method for providing these services according to the location information of the terminal is not considered so much.

  For example, Patent Document 1 discloses an information guidance method for mobile users that can appropriately provide appropriate information according to user position information, preference information, and the like. A recommendation function that automatically provides the most favorable services in a location has not yet been developed in this technical area.

Therefore, it can be said that there is definitely a need to provide users with applications that provide various services by utilizing the graphic capabilities of hand-held mobile devices according to location information.
JP-A-11-055726

  Currently, the World Wide Web is widely used as a method for providing various services to users. However, because the World Wide Web is not designed with location information in mind, there is clearly a limit to the framework for providing various services with drawing layout information generated from HTML. The World Wide Web is a system consisting of linked hypertext documents that can be accessed from anywhere via the Internet. In other words, whatever is linked to individual Web services by the World Wide Web, it is data without location information. Therefore, individual services cannot be found or grouped based on the user location information. More importantly, they do not reflect user preferences.

  Therefore, users must know how to find the services they need by remembering the URLs needed to use the services or using a search engine. In other words, it is difficult for users to find services on the World Wide Web. In addition, it is difficult to automatically track how users use individual services and make recommendations based on this information without the need for actions such as voluntary declarations by the users themselves. It is.

  In order to implement a service by a system that overcomes the above-described restrictions, it is necessary to pay attention to the service associated with the location information and to take a method of tracking the service usage tendency of the user from the beginning. As a result, the user can shift from the service provided by the current World Wide Web to a service automatically linked to the position information by the position information and the preference information through his / her mobile terminal.

  The present invention solves two problems. One is location information that is useful in the vicinity of the mobile device in order to always recommend the most preferred service at the current location to the user who owns the mobile device when the mobile device moves from one location to another. To automatically discover services associated with. The other is to automatically generate a user interface tailored for a particular mobile device and use it to make individual services available.

  In order to solve the above problem, the invention according to claim 1 extracts an available service from a plurality of services that can be provided to a terminal device from one or a plurality of service providing servers via a network. A service management server for providing information related to the service to the terminal device, and a service extraction means for extracting a plurality of services matching the current location in response to a request accompanied by the current location from the terminal device; Preference degree calculating means for calculating a preference degree for each extracted service based on a service usage history of the user of the terminal device registered in advance in a database, and all or a part of the extracted services Information transmitting means for transmitting to the terminal device information related to the service and information indicating the degree of preference for each service. And butterflies.

  According to a second aspect of the present invention, in the service management server according to the first aspect, the preference level calculation means is based on the service usage history of the user, and the probability based on the usage time or the number of times of use of the extracted service. And the degree of preference is calculated based on the probability and the price of the extracted service.

  The invention according to claim 3 is the service management server according to claim 2, wherein the preference level calculation means calculates the preference level using a membership function based on the probability and the price. To do.

  According to a fourth aspect of the present invention, an available service is extracted from a plurality of services that can be provided to a terminal device from one or a plurality of service providing servers via a network, and information regarding the extracted service is stored in the terminal device. The service information providing method in the service management server provided to the server, in response to a request accompanied by the current position from the terminal device, extracting a plurality of services matching the current position, and pre-registered in the database Calculating the degree of preference for each extracted service based on the service usage history of the user of the terminal device, information on all or a part of the extracted services, and each service And a step of transmitting information indicating the degree of preference to the terminal device.

  The processing of the service information providing program according to claim 5 relates to the extracted service by extracting an available service from a plurality of services that can be provided to the terminal device from one or a plurality of service providing servers via the network. A computer that provides information to the terminal device, in response to a request with the current position from the terminal device, a service extracting means for extracting a plurality of services that match the current position, the database pre-registered in a database Based on the service usage history of the user of the terminal device, a preference level calculating means for calculating a preference level for each extracted service, information on all or a part of the extracted services, and each service And functioning as information transmitting means for transmitting information indicating the degree of preference to the terminal device, That.

  According to the present invention, when moving from one location to another location that always recommends the most desirable (optimum) service at the current location of the user of the mobile device, it is tied to the location near the mobile device. Can automatically discover available services, and further enable the use of these services through mobile applications by dynamically using a user interface tailored to specific mobile devices it can.

DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, the best mode for carrying out the invention will be described with reference to the drawings.
(1. Outline of system operation)
First, a schematic operation example of a system in an embodiment of the present invention will be described.

  In the system according to the present embodiment, in order to obtain a global position, a global application receives a radio wave from a GPS satellite by a mobile application executed on a mobile device (an example of a terminal device according to the present invention). Data is received in real time. When the location of the mobile device is changed, the application connects to a service server via the Internet (an example of a network) and requests an available service at the current location of the mobile device. In order to handle such requests, a service server (an example of a service management server in the present invention), a part of the server software running on it, retrieves information on all services available at the current location of the mobile device. (Extract) and determine which of the extracted services is more desirable to the user of the mobile device. This is done by calculating the “preference level” for each extracted service, and means that the extracted service is ranked (ranked) based on the service usage history of the user of the mobile device. Thereafter, the service server returns the extracted service information together with the degree of preference to the mobile device.

  When the response sent back from the service server is received, the application in the mobile device examines the list of received service information and updates any previously received list of service information. The service with the highest preference is recommended to the user using a pop-up notification through the mobile application. Thus, the user can select a service to use from a set of services recommended to the user, or select some other service available at the current location. Then, when the user selects a service, the mobile application was received in a previous service request to connect to a service provider server (an example of a service providing server in the present invention) that provides a specific service via the Internet. Use service information. After the application successfully connects to the service provider server providing the service, the application requests a desired service and transmits system information about the mobile device to the server. The service provider server then examines the system information and constructs and returns data specific to the user interface (having a display screen) that is uniquely adapted to the mobile device requesting the service.

  When the user interface data is received by the mobile device application, a user interface view is constructed based on the user interface view, and the user of the mobile device can create the newly created dynamic graphical user interface. You can use the service through. Whenever a user operates in this dynamically configured service user interface, the mobile application (mobile device application) collects all data from the user interface as set by the user, Send it to the service provider server. The service provider server then examines the transmitted data, performs some operations according to the service logic (processing), constructs a new user interface view, and returns it.

This communication pattern continues until the mobile device has finished using the service and disconnected from the service provider server. When the mobile device disconnects from the service provider server, the mobile device reports the service usage to the service server (transmits report data). As described above, the report data transmitted to the service server includes information on which service has been used and for how long. Then, when the user's mobile device requests for the next service, the service server stores and stores this received information for future use so that more accurate ranking can be performed.
(2. System configuration and detailed operation example)
Next, a system configuration and a detailed operation example in the present embodiment will be described.

  FIG. 1 is a diagram illustrating a schematic configuration example in a system according to the present embodiment.

  As shown in FIG. 1, the system according to this embodiment includes five components 100 to 500.

  A GPS satellite 100 is used to obtain real-time position information of the mobile device 200 shown in FIG. A mobile device 200 having an Internet connection function can communicate with various servers such as a service server 300 and a number of service provider servers 500 connected to the Internet.

  In order for mobile device 200 to communicate with service server 300 and service provider server 500, a message-based interface is implemented. This consists of several binary messages, each of which is designed for a specific task in communication. The message interface is described in, for example, MIF (Message Interface Definition document). Four message pairs (request and response) in the MIF document are relevant to the system and will be described in detail here.

  The application executed on the mobile device 200 acquires a new position of the mobile device 200 from the GPS satellite 100 every time the position is changed.

  The application of the mobile device 200 requests a service that matches the current position from the service server 300 using a service search request message at intervals of several seconds that can be changed from the setting of the application.

  The service server 300 responds by transmitting a service search response message to the mobile device 200. The service search response message includes a list of services including all information stored in the service database 400, and a preference degree calculated for each service.

  The application of the mobile device 200 handles the response message from the service server 300, updates the current service list according to the content of the response, and recommends the service having the highest preference for the user through the user interface. Thereafter, the mobile device 200 can connect to the service extracted for use. In order to create (establish) the connection, the received service information (connection IP address and port number) is required.

  By the way, since the system is based on user profiling, the application of the mobile device 200 uses a user name (username) and a password (password) before requesting a service from the service server 300 by a service search request message. Thus, it is necessary to register with the service server 300. This is done by using the record (register) in the request message, and the application of the mobile device 200 receives the record in the response message as a reply from the service server 300. In this response message, there is a service server generation ID called a session ID, and this ID is used to confirm (identify) the user in the next service search request message. The session ID is always placed in the next request message sent by the mobile device 200.

  The purpose of the service server 300 is to work as a centralized knowledge base collected in the center, and the mobile device 200 is connected to the base and receives service information for service connection, service recommendation and use. Yes.

  There is a service application (executed by the CPU, which functions as a service extraction unit, a preference level calculation unit, and an information transmission unit in the present invention) that is executed on the service server 300. Confirmation is performed, and the mobile device 200 responds to the message transmitted by the connection. The service server 300 is connected to the service database 400. The service database 400 includes metadata of all services, user information, and service usage histories of all users that can be extracted (discovered) from the service database 400.

  FIG. 2 is a diagram illustrating an example of information registered in each table in the service database 400.

  As shown in FIG. 2, the service metadata on the “Service” table is composed of five fields (in other words, a registration area). The service ID (“service id”) is a unique (unique) identifier (identification information) of each service registered (stored) in the database. This is assigned by a service server application running on the service server 300. The name (name) is a character string representing the service name. The next two pieces of information (“address” and “port”) are the most important factors for the mobile device 300 to use a service that always requires data in these fields. In the “address” field, a name address or an IP address for connecting the mobile device 200 via the Internet when using a service, that is, an address of the service provider server 500 is described (registered). In the “port” field, a port (port number) to be used in connection to the service provider server 500 is described. The last “price” field describes the service attribute: price. This information shows how much money the user has to pay to use the service. The information described in all these fields in the “Service” table is embedded in the service search response message when the mobile device 200 requests a service that matches its location, and the service metadata of the service along with the preference. To the mobile device 200.

  This system is based on user-specific profiling that represents that all requests made by the mobile device 200 to the service server 300 are always tied to the user. Accordingly, all users of the mobile device 200 must have a unique user name and password for identity verification and authentication. This data enables the system to track user-specific service usage trends and create their favorite ranking.

  Next, the user data is stored in a “User” table in the service database 400. The “User” table contains all user information of the system and has four fields. The first one (username) is a unique identifier (identification information) of the user in the system. The second field contains the user password. The third field contains a string describing the user's full name, the last one being the user's email address.

  The “History” (history) table has information regarding the service history of each user. In order to calculate the preference of the extracted service, information on when the service was used (when and how long) can be obtained from this “History” table. The “History” table has a history ID that is a unique identifier assigned by the server application. The second and third fields contain keys (username, service id) that indicate which user's history registration and which service was used by the user. In the next field, the service use start time (start) is described in milliseconds from UTC (Coordinated Universal Time) 00: 00: 00: 00 in January 1970. In the last field, the end time (finish) of use of the service is described in milliseconds from UTC (Coordinated Universal Time) 00: 00: 00: 00 in January 1970.

  Two other tables are introduced into the service database 400 when a service is made available at more than one location and a location can have several services.

  The “Location” table holds all locations where each service is located. This “Location” table has a location ID as a primary key, which is assigned by the service server application. The “name” is a character string that describes a position such as a building name or street address. Longitude and latitude mean the geographical coordinates of a position on the earth.

  The “Linked” table is used to make an association between a service and a location, and holds a main key (Service id, location id) from the “Location” and “Service” tables.

  When the mobile device 200 connects to the service server 300 and the record in the request message is registered, the server application checks the user name and password in the request message against the user name and password read from the service database 400. . If the received password matches the password registered in the “User” table, the server application generates a session ID for the mobile device 200 and incorporates the session ID in the response message to create the mobile device 200. Reply to Thus, the session ID becomes a unique identifier for recording a session, and becomes a more important unique identifier for the user of the mobile device 200. Further, the session ID is used in the next request to the service server 300 in order to perform normal operation.

  When the service server 300 receives a service search request message from the mobile device 200, the service server 300 is on the service database 400 to find all services linked to coordinates close to the coordinates obtained from within the request message. Perform a search with. In order to determine which services are close, a rather simple calculation method is applied. The server application calculates the distance D between the two coordinate points (the current location of the device obtained from the request message and the location of the location in the “Location” table). If the distance D is within a predetermined range R (ie, D <R), all services linked to the location are selected and their service information from the “Service” table is the service search response. It is added to the message and returned to the mobile device 200. This applies to all locations in the database when a response message is received. The distance D (great circle distance) is calculated by using the following calculation formulas (1) and (2).

Equation (1) describes the exact equation for calculating the center angle. Here, φ _s , λ _s ; φ _f , λ _f are the geographical longitude and latitude of the two points, Δλ is the longitude difference, and Δσ is the angle difference of the sphere. The great circle distance D is obtained from the equation (2). Where r is the radius of the sphere, and in this system is the radius of the earth.

  After the service server 300 searches for and extracts all available services close to the location of the mobile device 200, the service server 300 calculates user preferences for all the extracted services. These calculated preferences are then returned in a service search response message along with service metadata extracted from the “Service” table in the service database 400. This calculation method will be described later.

  The calculation of the service preference is performed based on a history of how the user has used the service in the past. This calculation is performed every time the mobile device 200 uses the service. Use of the service of the mobile device 200 is reported to the service server 300 by a service use request message.

  The information in this message includes an identifier (service ID) for the used service and a start time and an end time for using the service.

  When the service server 300 receives the service use request message, it creates a new column in the “history” table in the database 400 using information found in the service use request message.

  The service use response message is transmitted by the service server 300 as a response to the request.

  If the mobile device 200 wishes to connect to a service discovered from that location, the mobile device 200 connects to the service provider server 500 using the service address and port number. Then, the mobile device 200 transmits a service acquisition message. The service acquisition message includes XML data having a service identifier (received from among other service metadata) and information about the screen size of the mobile device 200. When the service provider server 500 recognizes the service ID, the service provider server 500 creates (generates) a user interface based on the screen size of the mobile device.

  Thereafter, this user interface is embedded in the service acquisition response message and returned to the mobile device 200 as an XML document. Mobile device 200 parses the document and then creates a graphical user interface.

  FIG. 3 is a diagram illustrating an example of an XML document transmitted by the mobile device 200 and the service provider server 500.

  On the left side of FIG. 3, two boxes describing XML data transmitted only by the mobile device 200 are shown. The number 1 box shows XML data that is transmitted only once when the mobile device 200 connects to the service provider server 500 for the first time. The screen size of the device can be found from within the screen components.

  The number 3 box on the right side of FIG. 3 shows XML data transmitted only by the service provider server 500. The XML code seen from within the box illustrates user interface components from which the mobile device 200 is supported to create a user interface for the service. In the case of the number 3 box, three different components are seen. They are a label, a button, and a combobox item.

  A label is a user interface component and contains only text to be displayed on the device screen. Like other components, it has an area element inside to indicate how much area is reserved for the text and where it is located. The actual content to be shown on the label is extracted from within the text tag element (<text>... </ Text>). The font of the text is set by using a font tag element (<font>... </ Font>).

  The button tag element has two identical internal tag elements like a label, and the text written on the button element on the screen is described in the text tag element. A combo box is a drop-down menu that contains several string elements inside. It has a selected attribute, which indicates which of the internal elements was selected by default.

  All these three components (level, button, and combo box) have a name attribute, and each name attribute is a unique identifier for each component.

  The item tag element in the combo box also has this name attribute to indicate which item the user selects from the drop-down menu.

  As can be seen from the number 3 box in FIG. 3, all components are extracted from within a root tag element called a form. This also has a name attribute as a unique identifier.

  Another attribute is the session required to store the state of service for the mobile device 200.

  The third attribute is a head line for the user interface view described by the XML document.

  When the user operates the mobile device 200 and presses a button on the generated user interface, the application on the mobile device 200 collects all information from the user interface component and based on the state of the component To construct an XML document.

  In the service provider server 500 to which the XML document is sent, the name and the values of the session attribute need to be copied accurately. This is because the service provider server 500 knows which device form the XML data is in, and which user interface view the data corresponds to.

  The value of this attribute is the name of the button pressed by the user in the view. This allows the service provider server 500 to know how the button was pressed and perform the required action accordingly. When the button is pressed, the mobile device 200 application generates an item tag element from each user interface component that can be set to value by the user.

  In the case of FIG. 3, such a component is a combo box as a place where the user can select a certain value.

  The key attribute in the item is the name of the component. Its value attribute is the actual value of the component set by the user.

  In the example of FIG. 3, since the label tag element has no user interaction, the label tag element is not changed and is therefore not needed on the service provider side.

  When the user presses the button, the XML data described in the two boxes shown in FIG. 3 is placed in the service acquisition request message and transmitted to the service provider server 500.

  When the service provider server 500 receives the message, it performs several actions according to the logic of the service to construct a new user interface view (similar to number 3 in FIG. 3). Then, the service provider server 500 puts the user interface view in the service acquisition response message and sends it back to the mobile device 200. And again, the user can react to the new user interface through the device.

  The communication pattern is repeated as many times as possible until the mobile device 200 finishes receiving the service and disconnects from the service provider server 500.

  An application running on the mobile device 200 maintains a history of service usage records when service usage starts and when it ends.

  When the mobile device 200 disconnects from the service provider server 500, a service usage request message is transmitted to the service server 300 in order to report how the service has been used by the user. This message includes the service identifier of the service used and the start and end times for its use.

The mobile device 200 obtains a service use response message as a response from the service server 300.
(3. Preference calculation example)
Next, details of the preference calculation will be described.

  FIG. 4 is a flowchart showing the preference calculation process in the service server 300.

  In order to calculate the preference, a record of the user history (how long and when the user has used the service) is described as a time zone. The server application of the service server 300 obtains all necessary information from the “History” table in the service database 400 in order to perform the above calculation. The total usage time of the service is divided into one day of the week and every hour. In other words, the total time is divided into 24 × 7 (168 time zones). The total time is not only divided into a plurality of time zones, but also the total number of times of use (meaning how many services are used).

  FIG. 5 is a diagram showing an example of a table describing time zone classifications.

  Each time the mobile device 200 reports service usage to the service server 300 using the service usage request message, the status in the table changes as usage time, and the number of usage times in the time zone increases.

  In FIG. 5, the user's history in the time zone (Time Zone) of three different services (Service A, Service B, and Service C) can be seen. From FIG. 5, it can be seen that the user uses Service A six times, and the total use time (TOTAL) of the user's service is 57 minutes 39 seconds. And this information consists of using services on three different time zones.

Now, if the user inputs the position again, two different probabilities can be calculated, for example on the time zone number 85 between 12:00 and 13:00 on Wednesday. That is, there is a probability P _t based on usage time and a probability P _n based on the number of times of usage. These probabilities are needed to indicate how likely the user wants to use the service. Also, from these probabilities, the highest probability for the final probability P (the probability P _t based on the usage time and the probability P _n based on the number of usages is P, hereinafter referred to as “Probability”) is always set. select. Therefore, the result in this case is 59.4%. If the user uses the service for the first time at some time, Probability will be zero. The reason for using the two probabilities is that the number of times the service is used within each time slot can vary. For example, when a user has used a service many times on a certain time zone, but it is only a few seconds, and uses the service for a long time, while using almost no service on other time zones. There is. Therefore, since the correct usage time does not always accurately indicate the service user's request, a probability based on the number of uses is introduced.

  Services in the system can have many different attributes such as price, payment method, security method, and privacy policy. All these attributes affect the user's decision to use the service and they must be taken into account when the preference is determined.

  Nevertheless, in the method described herein, it is assumed that a service has only one attribute as the price of the service. This attribute can be extracted from the “Service” table in the service database 400. It is also assumed that the user is more interested in an inexpensive service than an expensive service. Therefore, it is necessary to judge whether the service is cheap or expensive and perform the preference ranking accordingly. Here, the user's service usage history shows which service the user has used before and how much the user usually pays for the service.

  This information is used, for example, with fuzzy theory to be more effective.

  The following explains how the fuzzy methodology is applied to the preference Pr so that the service is actually determined from the probability and the price of the service (extracted from the “Service” table for each service) To do.

  To determine the degree of preference, fuzzy logic is used to generate its final value.

  First, it is necessary to define a fuzzy membership function so that the values of the input variables (price and probability) can be put into the fuzzy values.

  FIG. 6 is a diagram illustrating a graph example of the membership function of Probability.

  Generating a service price membership function is more complicated because the membership function is not static but changes on a case-by-case basis according to the user and the service usage history of the user. In order to generate the membership function, it is necessary to extract the following four values (a) to (d) from the “History” table and the “Service” table in the service database 400.

(A) The lowest price Pci paid for the service used by the user (obtained from the “History” table)
(B) The highest price Pei paid for the service used by the user (obtained from the “History” table)
(C) Lowest price Pc among all services in the “Service” table
(D) The highest price Pe among all services in the “Service” table
Using these four values, a service price membership function is constructed, as shown in FIG.

  FIG. 7 is a diagram illustrating a graph example of the service price membership function, and FIG. 8 is an example of an equation for calculating the price membership function. FIG. 9 is a diagram illustrating a graph example of the membership function of preference.

  The final preference calculation is done by using fuzzy rules, and then the result is obtained by calculating the center of weight.

  The fuzzy rules are defined as follows:

Rule 1: When the price is high and Probability is low, the degree of preference is low. Rule 2: When the price is intermediate, the degree of preference is average. Rule 3: When the price is low or Probability is high, the degree of preference is high. An example of calculating the degree of preference will be described below. In the following description, calculation is performed assuming that currency unit = 6 as an example.

First, as shown in FIG. 4, the probability P _t based on the usage time in the current time zone is calculated (step S1), and the probability P _n based on the number of usages in the current time zone is calculated (step S2).

Next, it is determined whether or not the probability P _t is larger than the probability P _n (step S3). If the probability P _t is larger than the probability P _n (step S3: YES), the probability P _t is set as Probability (P). It is set (step S4). On the other hand, when the probability P _t is not larger than the probability P _n (step S3: NO), the probability P _n is set as Probability (step S5).

  Next, a determination process of the degree of membership (membership value) of Probability is performed (step S6). For example, when the membership function of Probability shown in FIG. 6 is used, for example, assuming that Probability = 0.67 (X axis), in the low curve, the degree of affiliation (Y axis) is “0”, and high In the (high) curve, the degree of affiliation is “0.45”.

  Next, a determination process of the degree of membership (membership value) of the service price (Price) is performed (step S7). For example, when the membership function of the service price shown in FIG. 7 is used and it is assumed that the currency unit = 6 (X axis), the degree of affiliation (Y axis) is “0” in the cheap curve, and medium ( In the middle curve, the degree of affiliation is “1.0”, and in the expensive curve, the degree of affiliation is “0”.

  Next, a preference function creation process is performed (step S8). For example, the determined affiliation value, the membership function of preference shown in FIG. 9, and the fuzzy rule are used.

  Since rule 1 is not satisfied from step S6 and step S7, the low curve of preference shown in FIG. 9 is not used.

  Since rule 2 is established from step S7, the average curve of the preference shown in FIG. 9 is used. At this time, the medium curve of the service price has a degree of affiliation of “1.0”, so the entire average curve is used.

  Further, since rule 3 is established from step S6, the high curve of preference shown in FIG. 9 is used. At this time, in the high curve of Probability, since the degree of affiliation is “0.45”, the degree of affiliation of 0.45 or higher of the high curve is cut.

  FIG. 10 shows a graph example of the membership function of the degree of preference obtained in this way. That is, in the above processing, the curve and the degree of membership are determined from the two input values and the respective functions, and which curve is used and how much is determined by the fuzzy rule. The degree of affiliation determines how much is used.

  Then, the “weight center” is obtained from the membership function graph shown in FIG. 10 by a known calculation method, and the final preference is calculated. In the example of FIG. 10, the preference level is about 19.02. The membership function graph described above is determined based on empirical rules.

  As another example, assuming that currency unit = 3 and Probability = 0.1, in the process of step S6, the affiliation degree is “0.65” in the low curve, and the affiliation degree is “ 0 ". Next, in the process of step S7, the degree of belonging is “0.35” for the cheap curve, the degree of belonging is “0.65” for the medium curve, and the degree of belonging is “0” for the expensive curve. Next, in the process of step S8, rule 1 is not satisfied (the low curve is not used), and rule 2 is satisfied, so the average curve of preference is used, and at this time, the medium curve of the service price is the affiliation degree Is “0.65”, so 0.65 or more of the average curve is cut. Also, since rule 3 is satisfied, a high curve of preference is used. At this time, in the high curve of Probability, the degree of affiliation is “0.35”, so the degree of affiliation of 0.35 or higher of the high curve is cut. . Therefore, the final preference curve of preference is none of the low curve, the average curve is a trapezoid with a cut of 0.65 or more, the high curve is a trapezoid with a cut of 0.35 or more, Calculated as the degree of preference.

  As described above, according to the above embodiment, when moving from one location to another location that always recommends the most desirable (optimum) service at the current location of the user of the mobile device, It is possible to automatically discover available services tied to a location nearby, and to dynamically use these user services through mobile applications by dynamically using a user interface tailored to a specific mobile device. Can be used.

  Further, the probability based on the usage time and the number of times of use of the extracted service is calculated based on the service usage history of the user, and the degree of preference for each service is calculated based on either one of the probabilities and the price of the extracted service. In particular, since the preference degree is calculated using the membership function based on the probability and the price, it is possible to effectively apply a service that more accurately reflects the user's preference.

  Further, in the above embodiment, all services available at the current location of the user are always automatically extracted, and the service that is most preferred is automatically provided to the user's mobile device. The user only needs to have a mobile device, and the services available will change as the user moves. That is, all users need only concentrate on selecting services to use at different locations. In addition, since the service used by the user is ranked, the user does not need to perform an extra operation. That is, according to the above-described embodiment, it is possible to provide a new type of effect for providing a user with a favorite service.

  Moreover, according to the said embodiment, a user's service usage pattern can be grasped | ascertained correctly and the optimal service recommendation of the specific time of a specific day of a week can be performed.

  In the above embodiment, the mobile device application itself does not provide any service. However, in the above system, the mobile device may be configured to provide a service to another mobile device. For example, when mobile devices are close to each other, the service provided to one may be configured to be used by the other mobile device.

It is a figure which shows the schematic structural example in the system in this embodiment. It is a figure which shows the example of information registered into each table in the service database. 6 is a diagram illustrating an example of an XML document transmitted by the mobile device 200 and the service provider server 500. FIG. 5 is a flowchart illustrating a preference level calculation process in a service server 300. It is a figure which shows the example of a table which describes a time zone (Time Zone) division. It is a figure which shows the example of a graph of the membership function of Probability. It is a figure which shows the example of a graph of the membership function of a service price. It is an example of the formula for calculating the membership function of a price. It is a figure which shows the example of a graph of the membership function of a preference. It is a figure which shows the example of a graph of the membership function of a preference.

Explanation of symbols

100 GPS Satellite 200 Mobile Device 300 Service Server 400 Service Database 500 Service Provider Server

Claims (5)

A service management server that extracts available services from a plurality of services that can be provided to a terminal device from one or a plurality of service providing servers via a network, and provides information related to the extracted services to the terminal device. ,
In response to a request with the current position from the terminal device, a service extracting unit that extracts a plurality of services that match the current position;
A preference degree calculating means for calculating a preference degree for each extracted service based on a service usage history of the user of the terminal device registered in advance in a database;
Information transmitting means for transmitting information on all or a part of the extracted services and information indicating the degree of preference for each service to the terminal device;
A service management server comprising: The service management server according to claim 1,
The preference degree calculating means calculates a probability based on the usage time or the number of times of use of the extracted service based on the service usage history of the user, and based on the probability and the price of the extracted service, the preference Service management server characterized by calculating degrees. In the service management server according to claim 2,
The service level management server, wherein the preference level calculation means calculates the preference level using a membership function based on the probability and the price. Service information in a service management server that extracts available services from a plurality of services that can be provided to a terminal device via a network from one or a plurality of service providing servers and provides the terminal device with information related to the extracted services Providing method,
In response to a request with the current location from the terminal device, extracting a plurality of services that match the current location;
Calculating the degree of preference for each of the extracted services based on the service usage history of the user of the terminal device registered in advance in a database;
Transmitting information related to all or a part of the extracted services and information indicating the degree of preference for each service to the terminal device;
A service information providing method comprising: A computer that extracts available services from a plurality of services that can be provided to a terminal device from one or a plurality of service providing servers via a network, and that provides information about the extracted services to the terminal device;
Service extraction means for extracting a plurality of services that match the current position in response to a request with the current position from the terminal device;
A preference degree calculating means for calculating a preference degree for each of the extracted services based on a service usage history of a user of the terminal device registered in advance in a database; and
A service information providing program for causing information relating to all or a part of the extracted services and information indicating the degree of preference for each of the services to function as information transmission means for transmitting to the terminal device.

Images