KR100643704B1 - Mobile personalization service system and mobile personalization service method - Google Patents

Abstract

The present invention relates to a mobile personalization service system.

The mobile personalization service system of the present invention comprises a client module for receiving a user context and generating the received user context as ontology data; An agent module for receiving ontology data generated from the client module, interpreting a user context from ontology data received through a plurality of agents, and recommending service candidates suitable for the user context; And a server module receiving the user context from the agent module and transmitting service candidates satisfying the user context to the agent module, and transmitting the service candidate recommended by the agent module to the client module.

Wireless Internet, Personalization Service, Context-Based Processing

Description

Mobile personalization service system and mobile personalization service method {MOBILE PERSONALIZATION SERVICE SYSTEM AND MOBILE PERSONALIZATION SERVICE METHOD}

1 is a block diagram of a mobile personalization service system according to a first embodiment of the present invention.

2 is a relationship diagram of an agent and an ontology in the mobile personalization service system of the present invention.

3 is a block diagram of a personalization service engine according to a second embodiment of the present invention.

4 is a flowchart of a mobile personalization service method according to a third embodiment of the present invention.

The present invention relates to a mobile personalization service system and a mobile personalization service providing method.

In particular, the present invention relates to a service system and a service providing method for supporting differentiated services for each individual by reflecting personalization characteristic information of a mobile user in a wireless Internet service structure.

US Patent Publication No. 2004-218574 relates to a "service providing apparatus, a service providing program and a service providing method", and a service providing apparatus for providing a desired service only to a desired service terminal is disclosed.

Such a conventional wireless Internet service system and service method is not a mechanism for processing personalized feature information such as personal preferences, locations, preferences, and requests of mobile users. Therefore, in order to provide a personalized service to the user, the function must be improved systematically.

The present invention provides a mobile personalization service system that can receive a user's personalized information and provide a customized service to a user.

In addition, the present invention provides a mobile personalized service method that can receive a personalized information of the user and provide a customized service to the user.

The present invention provides an optimized personalization service for a user in a wireless Internet service environment by using an ontology, a semantic processing system, an agent system, and a web service processing system.

The mobile personalization service system of the present invention generates the user's service request as ontology data in the user terminal, and transmits the generated ontology data to the service agent at an optimal position at the current user's location, and the service agent is transmitted from the user terminal to the user. After receiving the requested ontology data, the user's requested ontology is analyzed by the ontology analyzer.

In addition, the mobile personalization service system of the present invention builds a knowledge model that reflects user request ontology using a plurality of intelligent agents that perform cooperative processing with a semantic web server and a web service server. The intelligent agent selects the services of the service providers using the knowledge model and provides the optimized service to the user.

According to an aspect of the present invention, there is provided a mobile personalization service system of the present invention, comprising: a client module configured to receive a user context and generate the received user context as ontology data; An agent module for receiving ontology data generated from the client module, interpreting a user context from the received ontology data, and recommending service candidates suitable for the user context; And a server module receiving the user context from the agent module and transmitting service candidates satisfying the user context to the agent module, and transmitting the service candidate recommended by the agent module to the client module.

According to another aspect of the present invention, there is provided a mobile personal management system of the present invention, comprising: a terminal agent unit configured to collect user contexts from a user's terminal and generate ontology data; An agent unit for receiving a user context ontology from the terminal agent unit, analyzing the received user context ontology, dividing the user context ontology according to the type of user context, and storing the ontology according to the type of user context; And an ontology unit for providing the agent unit with user information stored in the plurality of ontology in response to a request of the agent unit.

According to another aspect of the present invention, there is provided a method of mobile personalization service of the present invention comprising: collecting a user context from a user and ontology the collected user context; Recognizing user needs from an ontology user context and selecting an optimal service selection model for the user needs; Selecting service candidates suitable for user needs using the selected optimal service selection model; And further selecting recommended service candidates suitable for the user's needs using the user context from the selected service candidates.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention.

1 shows a configuration of a mobile personalization service system according to a first embodiment of the present invention.

As shown in FIG. 1, the mobile personalization service system according to the first embodiment of the present invention receives a user context, generates a client ontology data, and analyzes a user context ontology to recommend a service candidate suitable for a user's request. It includes an agent module 300 and a server module 400 for providing service information to the agent module 300.

In the first embodiment of the present invention, a client means a mobile terminal, which may include a cellular phone, a PDA, and any kind of mobile terminal.

The client module 100 includes a personalization service engine 110, receives a user context including a user request and user information, generates the user context as ontology data, and transmits the ontology data to the agent module 300. The user context is a generic name that includes information about the user and the needs of the user. The user context is used to determine the location of the terminal, the specifications of the terminal device, the user's schedule, personal information that the user prefers, and the type of service that the user requires. Include. In addition to the information input by the user, the user context includes information about the user environment such as temperature and weather.

The personalization service engine 110 collects user contexts such as user information and user requests, and converts the collected user contexts into ontology data and transmits the collected user contexts to the agent module 300 through the network 200.

User information input to the personalization service engine 110 is not particularly limited as a context for the user. The user information may include current location information of the user, personal information preferred by the user, a schedule, a type of mobile terminal, and the like.

The network 200 between the client module 100 and the agent module 300 may be configured with a wireless network or an IP (Internet Protocol) based protocol.

The agent module 300 receives the user context ontology from the client module 100, interprets the user request from the user context ontology, selects a service candidate suitable for the user request, and selects the selected service candidate as the client module 100. send. The agent module 300 may include a server agent module 310, a mobile agent module 330, and a database 350 module.

The agent module 300 performs a server function on the client module 100, and when performing the server function on the client module 100, a unique IP of the server may be fixedly allocated. In addition, the agent module 300 may work integrally with the web service module 420 and the web service processing module 440 of the server module 400.

The mobile agent module 330 communicates with the server agent module 310 and the database module 350 to perform a decision algorithm to select recommendation service information, and to recommend the recommendation service information to the personalization service engine of the client module 100. 110).

The mobile agent module 330 may include an agent such as a decision engine 332, a user agent 334, a location agent 336, and a near field search agent 338. The decision engine 332 receives a context ontology from agents including a user agent 334, a location agent 336, a near field search agent 338, and performs a decision algorithm. The context ontology may be received from the ontology of the web service module 420 and may include user activity information, temperature, weather, and the like.

In detail, the mobile agent module 330 receives the user context ontology from the client module 100 and transmits the received user context ontology to the database module 350. The database module 350 selects a service selection model optimized for a user request and transmits it to the mobile agent module 330, and the mobile agent module 330 cooperates with the server agent module 310 to select a service selection model. Receive service candidates matching

The decision engine 332 receives service candidate information from the negotiation agent 312 of the server agent module 310, and checks ontology such as weather, temperature, distance, etc. from the web service module 420 of the server module 400. Then, the recommended service information most suitable for the user's needs in the current user environment is selected from the received service candidate information.

Specifically, receiving the location context from the location ontology 421, select the service candidates most suitable for the user's needs at the current user's location as the recommended service candidate, and receives the user schedule context from the personalization ontology 423, in the current user schedule The service candidates most suitable for the user are selected as recommended service candidates.

In this case, the decision engine 332 may consider the service ontology 427 of the web service using the recommendation information of the negotiation agent 312 and the web address of the service provider corresponding to the recommendation information.

The decision engine 332 determines the recommendation information (service candidate) suitable for the user information and then transmits the recommendation information to the personalization service engine 110 of the client module 100 to the current mobile terminal user. The transmitted recommendation information may be shown to the user through the display of the mobile terminal.

Meanwhile, the decision engine 332 may further include information for exporting information suitable for a user's situation. That is, depending on the performance of the mobile terminal used by the user, the context of the user's state as well as the context such as the optimal resolution that can be output (for example, the user is free or busy, or not free or busy) ), The recommendation information may be transmitted.

The database module 350 receives the user information from the mobile agent module 330, selects a suitable service selection model for the user's request, and transmits the selected model to the mobile agent module 330. The database module 350 may include a model database management system 352 and a database management system 355.

Specifically, the model base management system 352 receives the user information from the mobile agent module 330, retrieves the service selection model optimized for the user information and transmits it to the mobile agent module 330. In this case, the service selection model refers to information that a user frequently uses, such as a service, extracted from a database file. The service selection models stored in the model base management system 352 are optimization service selection models generated by the context model miner 354 according to the user context. The service selection model optimized for user information is determined by the service requested by the user. That is, it includes an optimized service selection model for each service. These optimization service selection models are all stored in the model database management system 352 and are called and used whenever necessary.

The context model miner 354 receives the user information from the database management system 356 when the model base management system 352 does not include a suitable service selection model for the user's request, and receives the user information from the model base management system 352. A model is generated and stored in the model base management system 352.

The database management system 356 stores user information about the mobile terminal user, and provides the user information to the context model miner 354 at the request of the context model miner 354. The user information stored in the database may include a user ID, a type of service provided, and a user's preferred information result value.

The server agent module 310 connects the information in the service ontology with the agent of the service provider. Specifically, the server agent module 310 receives the service selection model optimized for the user information and the user request from the mobile agent module 330, and obtains the optimized service selection model. Communicate with agents of service providers to select appropriate service candidates and send the selected service candidates to mobile agent module 330. The server agent module 310 may include a negotiation agent 312, a coordination agent 314, and an arbitration agent 316.

When receiving the user information through the mobile agent 330, the decision engine 332 sends this information to the negotiation agent 312, the negotiation agent 312 sends this information back to the agent of the service provider, Send to Mediation Agent 314 or Mediation Agent 316. The mediation agent 314 or mediation agent 316 that has received the user information transmits this information to the service providers to which it mediates or mediates.

Service providers who have received user information transmit their intention to sell their services to negotiation agent 312, mediation agent 314, and / or mediation agent 316 when they want to sell their services for the received user information. do.

Here, the coordination agent 314 and / or the mediation agent 316 receive service intent from various service providers, and recommend only to the negotiation agent 312 the service provider with the most advantageous information about the corresponding user information. .

Finally, only a few of the service candidates collected by the negotiation agent 312 are recommended and transmitted to the decision engine 332 of the mobile agent 330 based on the preference information in the preference ontology 425. Here, the number of results recommended by the decision engine 332 may be set by the user.

Meanwhile, the mobile terminal user may not select the recommended information through the optimization process by the mobile personalization service system. These choices can be stored in the case base for future reference by the user for similar services. Therefore, it is possible to refer to the contents of the casebase and gradually recommend appropriate information to the user.

The agent module 300 and the server module may be configured with a SOAP (Single Object Access Protocol) based protocol.

The server module 400 includes a web service module 420 and a web service processing module 440.

The web service module 420 includes various ontology databases and manages the ontology database. There is no limitation to the ontology database that can be included in the present invention, but in the embodiment of the present invention, the location ontology 421, the personalization ontology 423, the preference ontology 425, the service ontology 427, and the like are included. Shall be. Ontologies can be divided into static ontologies that are not affected by user environment changes and dynamic ontology that is affected by changes in user environment. Static ontology corresponds to user information that is not affected by short-term user environment changes such as user profile information and user request service information, and dynamic ontology changes the current user's emotions such as the user's current location, temperature around the user, etc. This corresponds to user information sensitive to changes in the environment surrounding the user.

Here, the location ontology 421 includes a location context for the current user's location, the personalization ontology 423 includes a context about personalization information such as a user's schedule, and the preference ontology 425 is a service preference of the user. Service ontology 427 includes the context for the service of the service providers. It may also include a negotiation ontology 420 that includes negotiation rules preferred by the user.

Such ontology is initially provided with ontology data including default value for mobile user, and then creates personalized ontology through user context. These ontology is stored for each ontology by agents.

In detail, the location ontology 421 checks and stores the current location of the user every predetermined time using the location agent 336, and the personalization ontology 423 checks and stores the schedule of the user every predetermined time.

The web service module 420 may include an ontology management function module 429, and the ontology management function module 429 performs a management function of the ontology.

In this way, the agent and the ontology can be built together as a user's personal management system. Such a personal management system has a user context such as user profile information and preference information. The personal management system can be built as a separate system or in an agent system.

In one embodiment, a personal management system includes a terminal agent unit for collecting a user context in a user's terminal, generating ontology data, and transmitting the generated ontology data to an agent unit; An agent unit 300 receiving a user context ontology from a terminal agent unit, analyzing the received user context ontology, dividing the received user context ontology into a plurality of ontology according to the type of user context, and storing the ontology unit for each user; And an ontology unit 420 for providing user information stored in the plurality of ontology at the request of the agent unit.

The web service processing module 440 is not limited as long as it can perform a web service processing function that is generally used.

In the above description, it has been described that the agents and the ontology are separately included in the server agent module 310, the mobile agent module 330, or the web service module 420, but the locations of the agents and the ontology are the present invention. It does not significantly affect the effect of the mobile personalized service system according to the first embodiment of the present invention. Thus, the location of agents and ontologies is not limited to the location disclosed in the above description.

Hereinafter, the relationship between agents and ontology in the operation of the mobile personalization service system according to the present invention will be described in detail with reference to FIG. 2.

2 illustrates an agent and an ontology relationship.

In FIG. 2, the user agent 334 receives the user's current location information and the user context. The user agent 334 may be located in the client module 100 or the agent module 300.

At the request of the user agent 334, the location agent 336 checks the location information of the user every predetermined time and stores the location information in the location ontology 421, or retrieves the location information stored in the location ontology 421 to retrieve the user agent. Can be passed to 334.

The near field search agent 338 performs a near field search using the user location information received from the user agent 334 and the context of the user. First, the distance is calculated by processing the user location information, and the user information and the preference are read from the personalization ontology 423 and the preference ontology 425. Thereafter, the service directory 500 is accessed to find a service to be searched, receives a uniform resource identifier (URI) of the service, and collects information on each service from the service ontology 427 based on the URI. The local search agent 338 then delivers the resulting service information and service ontology 427 of those services to the user agent 334.

Meanwhile, the negotiation ontology 428 may be used. Negotiation ontology 428 is necessary to obtain a result suitable for the user's needs, and includes information such as negotiation rules. The negotiation ontology 428 may be generated as an ontology by the user. In other words, the negotiation rule is changed according to the user's negotiation principle, and a new negotiation rule can be generated to configure a negotiation environment optimized for the user.

Agents that may be used in the personalization service system according to the first embodiment of the present invention may include, in addition to the agents, a request grasping agent, a job agent, a neighbor search agent, a service search and comparison agent.

The request grasping agent has the ability to read and write the ontology of the mobile user's needs, the user activity analysis to determine where the user is currently using the service, and the preference ontology to know which service the user is interested in. The user preference analysis function may be performed.

The job agent can manage automation services of agents, manage user delegation information that a user can edit from a database, and search and request using web services.

The Neighbor Search Agent calls a web service that supports location to determine your current location, the ability to identify nearby services, calculate the perceived distance, and process the Neighbor Search based on constraints when searching. Function can be performed.

Negotiation management agent manages personalized negotiation rule ontology which has the function of negotiating rule ontology that designates and manages class and properties of ontology using user-specific negotiation rule ontology, and reads and writes negotiation rule ontology created for each individual. And present a negotiation result.

The service discovery and comparison agent compares the user's needs with all the contexts for the user, and discovers the optimal service by querying the universal description, discovery, and integration (UDDI) for the user's needs, and compares it with the service provider of the found service. It can communicate to the user. That is, the service discovery and comparison agent performs a service discovery function that searches a web service to get a result, a function of sending a list and contents of found services to the user agent 334 to be sent to the client module 100, and the like. In addition, the user can perform a preference calculation function that the user prefers most.

The mobile personalization service system according to an exemplary embodiment of the present invention may include a personalization service engine 110 for personalization service in a mobile terminal, that is, a client.

3 shows a conceptual diagram of the personalization service engine 110 included in the client module 100 according to the second embodiment of the present invention.

Modules included in the personalization service engine 110 shown in FIG. 3 are not limited to the modules shown in FIG. 3 as examples of modules that may be included in the present invention.

As shown in FIG. 3, the personalization service engine 110 may include a user interface 120, a communication module 122, a user context input module 124, a terminal agent 125, an ontology generation module 126, and a web service module. (128). Such modules can be configured to operate on Java, which is used in existing commercial applications.

The user interface 120 displays a list of recommended service candidates to the user, and provides a service selection function and an event type service selection function by the user. The service list providing function is a function of presenting a recommendation service list suitable for the current user context, and the service selection function is a function of processing to select a preferred service among the suggested recommendation service candidates.

The communication module 122 supports the location of the mobile terminal using various types of location tracking modules. Technology such as GPS, WIFI, Bluetooth, etc. may be used.

The user context input module 124 automatically or manually receives a context from a user through the user interface 120. The mobile user always leaves information about the user on his mobile terminal. The personalization service engine according to the embodiment of the present invention intelligently accepts the information left by the user as a context for the user and provides a service.

The terminal agent 125 performs some of the personalization processing functions in the client module 100. As a specific function, the user request for a predetermined schedule is confirmed from user schedule information input by the user, and the user request is ontologyed through the ontology generation module 126, and an agent of a service area supporting the user request. Can be sent to.

The ontology generation module 126 stores the context for the user in the ontology based on the personal information URI based on the information input by the user.

The web service module 128 configures a web service passively or autonomously, and supports a web service function for a distance calculation recognized according to a user's request service. You can also introduce optimization algorithms to discover web services.

4 is a conceptual diagram of a mobile personalization service method according to a third embodiment of the present invention.

Hereinafter, a mobile personalization service method according to a third embodiment of the present invention will be described with reference to FIG. 4.

First, a user context is collected from a user and ontology is collected (s100). The user terminal 100 recognizes and collects user information input through the user interface 120, and generates the collected user context as ontology data. The ontology data for the user context generated from the user terminal is then sent to the agent module 300 of the service base station most appropriate for the current location of the user.

Next, the user request is recognized from the ontology-based user context, and an optimal service selection model for the user request is selected (S200).

Specifically, the agent module 300 recognizes a user request from the received ontology data, and retrieves a model most suitable for the recognized user request from the model base management system 352.

At this time, when the model suitable for the user's request is not stored in the model base management system 352, the user information stored in the database unit is transmitted to the context model miner 354. The context model miner 354 generates a model suitable for the user context by using the received user request and the user context stored in the database unit, and stores the model in the model base management system 352, and the model base management system 352. Transmits the optimal service selection model received from the context model miner 354 to the user agent 334.

Next, service candidates suitable for user needs are selected using the selected optimal service selection model (S300).

The user agent 334 searches for a negotiation ontology 428 that includes negotiation rules appropriate for the user context based on the received user context and / or the optimal service selection model. The user agent 334 receives a negotiation rule from the negotiation ontology 428 and receives service candidates using the service ontology 427 including service information of the service provider through the negotiation rule. Here, the received service candidates may be selected through the negotiation agent 312, the mediation agent 314, and the mediation agent 316.

Next, the recommended service candidates are further selected from the selected service candidates by using the user context (S400).

The user agent 334 checks the ontology reflecting the user environment such as location ontology, personalization ontology, and selects the recommended service candidates most suitable for the current user.

Next, the selected recommendation service candidates are transmitted to the user terminal (S500).

The mobile terminal user selects a desired service from the recommended service candidates displayed on the terminal, and the unselected service is stored in the case base for use in selecting a service candidate later.

The mobile personalization service system of the present invention may provide a personalized service that is more intelligent than an existing mobile service and considers personal preferences by using personalized information of a mobile user, that is, context information. In other words. The mobile personalization service system of the present invention can provide a differentiated service for each individual by collecting a context for a user and then calling and applying an optimized service selection model suitable for the context.

On the other hand, in the mobile personalization service system of the present invention, the mobile terminal can perform the processing function for the personalization-related information, can have flexibility in the configuration of the mobile personalization service system, expandability and adaptability to the change of the new service structure Have

Claims (17)

A mobile personalization service system that receives ontology data representing a user context from a client module, An agent module receiving ontology data generated from the client module, interpreting a user context from the ontology data, and requesting service candidates suitable for the user context; And A server module for providing service candidates suitable for the user context to the agent module, And the agent module selects a recommended service candidate from service candidates provided from the server module and transmits the recommended service candidate to a client module. The method of claim 1, The agent module A database unit for storing a service selection model and providing a service selection model corresponding to a user context; And And an agent unit for requesting and receiving a service selection model corresponding to a user context from the database unit, and selecting an appropriate service candidate for a user's request by using the service selection model. The method of claim 2, Add the database And a context model miner for generating a service selection model suitable for a user's request using a user context received from the client module and a user context stored in the database unit. The method of claim 2, The mobile personalization service system further includes an ontology section including a plurality of ontology including individual user information, The agent blowing And a decision engine that checks user information from the ontology unit and determines a service candidate that satisfies user information stored in the ontology as a recommended service candidate when determining the service candidate. The method of claim 4, wherein When the location ontology is included in the ontology portion, Check the current location of the user every predetermined time, and transmit a user location ontology to the agent unit, And the decision engine interprets the user location ontology to select service candidates most suitable for the user's needs at the current user's location as recommended service candidates. The method of claim 4, wherein When the ontology portion includes a personalized ontology, Check the schedule of the user every predetermined time, and transmit the user schedule ontology to the agent unit, And the decision engine interprets the user schedule ontology to select service candidates most suitable for the user in the current schedule as recommended service candidates. The method of claim 1, The client module A communication module configured to detect a current location of a mobile terminal; A user context input module configured to receive a user context; A terminal agent unit performing a personalization processing function; And Mobile personalization service system comprising an ontology generation module for storing the input user context in the form of an ontology. The method according to any one of claims 2 to 7, A mobile personalization service system in which the database portion and / or the ontology addition is continuously modified through a user context and gradually optimized for a user. The method according to any one of claims 1 to 7, A case base storing the selection by the user for the recommended service candidate determined in the agent module, And when determining next recommendation service candidate, referring to the case base to determine a recommendation service candidate. In the mobile personal management system, A terminal agent unit for collecting a user context in a terminal of the user and generating the ontology data; An agent unit for receiving a user context ontology from the terminal agent unit, analyzing the received user context ontology, dividing the user context ontology according to the type of user context, and storing the ontology according to the type of user context; And A mobile personal management system including an ontology unit for providing user information stored in a plurality of ontology to the agent unit in response to a request of the agent unit. The method of claim 10, The ontology part Location ontology for the current user's location, Personalization ontology of your personalized information, A preference ontology of the user's service preferences, Service ontology for service providers, or A mobile personal management system that includes one or more of the negotiation ontology that includes the user's preferred negotiation rules. In the mobile personalization service method, Ontotizing a user context; Recognizing user needs from an ontology user context and selecting an optimal service selection model for the user needs; Selecting service candidates suitable for user needs using the selected optimal service selection model; And further selecting recommendation service candidates suitable for the user's needs using the user context from the selected service candidates. The method of claim 12, Checking the user information at a predetermined time, the mobile personalization service method comprising the step of ontology the user information. The method of claim 12, A method of mobile personalization service further comprising the step of continuously checking a user schedule and recognizing user needs from the user schedule. The method according to any one of claims 12 to 14, And if there is no model suitable for the user's needs, using the received user request and the pre-stored user context to create a service selection model suitable for the user's needs. The method according to any one of claims 12 to 14, When choosing the right service for your needs, A service ontology that stores the service provider's services, and A mobile personalization service method for selecting a service candidate suitable for a user's needs by using a negotiation ontology including negotiation rules optimized for a user. The method according to any one of claims 12 to 14, When selecting a recommended service candidate from the selected service candidates, Check the ontology that reflects your environment, A mobile personalization service method that selects service candidates that are optimized for user needs in the current user environment.

Images