PH12015000194A1 - Apparatus and method for managing user terminal - Google Patents

Abstract

A method of managing a user terminal is provided, and a method of operating a profiling server in the method of managing the user terminal includes determining whether a session builder server changes a mobile session database, fetching changed session information when it is determined that the session builder server changes the mobile session database, determining which of user terminal groups having separate profile attributes to include the fetched session information according to set profiling conditions, and updating a profiled user group database (DB) according to the determination.

Description

APPARATUS AND METHOD FOR MANAGING USER TERMINAL

BACKGROUND

1. Field of the Invention

[0001] The present invention relates to an apparatus and a method for managing a user terminal. 2. Discussion of Related Art

[0002] With the recent development of mobile communication technologies and the popularization of mobile terminals, a large number of users connect to the Internet and use services over a mobile communication network. Accordingly, mobile communication providers try to systematically manage information regarding users connecting to their networks and provide information, a notification or an advertisement suitable for subscribers.

However, recent mobile terminals support not only mobile communication networks, but also a wireless connection using Wi-Fi. Most of the mobile terminals preferentially support an Internet connection over the Wi-Fi.

Accordingly, when a subscriber of one mobile communication provider connects to only Wi-Fi of another mobile communication provider and uses the Internet, it is difficult to manage user connection information and Internet use information in an integrated manner, and thus, providing of information : suitable for the subscriber may be limited.

[0003] Conventionally, there are a method of transmitting a mobile notification or advertisement from a mobile communication provider using : only limited subscription information held in the mobile communication provider, and a method of transmitting a mobile notification or advertisement from an Internet service provider depending only on accumulated user profiles.

It is not easy to integrate the two services.

[0004] Accordingly, it is necessary to provide a new service of managing connections in an integrated manner when a user connecting to a mobile communication network simultaneously connects to another network, performing profiling, and providing information, a notification, or an advertisement suitable to the user.

SUMMARY OF THE INVENTION

[0005] The present invention is directed to provide an apparatus and a method of managing a user terminal, the method including monitoring status and session information of the terminal connecting to networks of a plurality of network providers in real time, performing grouping and profiling, and pushing a message to a profiled user among users who use Internet services using an application that uses a web browser or an Internet connection.

[0006] According to an aspect of the present invention, a method of operating a profiling server in a method of managing a user terminal includes determining whether a session builder server changes a mobile session database; fetching changed session information when it is determined that the session builder server changes the mobile session database; determining which : 2 A of user terminal groups having separate profile attributes to include the fetched session information according to set profiling conditions; and updating a profiled user group database (DB) according to the determination.

[0007] According to another aspect of the present invention, a method > of operating a notification policy server in a method of managing a user terminal includes fetching messaging requirements from a campaign database ; (DB) in which a messaging policy (campaign) is stored; selecting a user group to receive a message from a profiled user terminal group DB according to the messaging policy; and mapping the selected user group to the messaging policy and storing the user group and the messaging policy in a notification

DB.

[0008] According to still another aspect of the present invention, a method of operating a traffic mapping server in a method of managing a user ] terminal includes receiving a data request message of the user terminal; i extracting an in-browser messaging policy for the user terminal from an in- 1 browser messaging policy database (DB); determining whether to transmit a message according to the extracted in-browser messaging policy; and transmitting a message transmission request to an in-browser push server when it is determined to transmit a message according to an in-browser messaging policy.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features and advantages of the present invention will become more apparent to those of ordinary skill in the art by describing in detail exemplary embodiments thereof with reference to the attached drawings in which: . [0010] FIG. 1 is a diagram illustrating a network system according to an exemplary embodiment of the present invention;

[0011] FIG. 2 is a diagram illustrating session information according to an exemplary embodiment of the present invention;

[0012] FIG. 3 is a diagram illustrating a process of status-managing and profiling a user terminal over a mobile communication network according to an exemplary embodiment of the present invention;

[0013] FIG. 4 is a flowchart illustrating a method of operating a profiling server according to an exemplary embodiment of the present : invention;

[0014] FIG. 5 is a flowchart illustrating a method of operating a session builder server according to an exemplary embodiment of the present invention;

[0015] FIG. 6 is a diagram illustrating a process of updating connection information of a user terminal through a network system according to an exemplary embodiment of the present invention;

[0016] FIG. 7 is a diagram illustrating a process when the user terminal is disconnected through the network system according to an exemplary embodiment of the present invention;

[0017] FIG. 8 is a diagram illustrating a process of status-managing and profiling a user terminal over another network according to an exemplary embodiment of the present invention;

[0018] FIG. 9 is a diagram illustrating a process of changing session information over another network according to an exemplary embodiment of the present invention;

[0019] FIG. 10 is a diagram illustrating a process when a user terminal : is disconnected over another network according to an exemplary embodiment of the present invention;

[0020] FIG. 11 is a diagram illustrating a process of building a notification DB according to an exemplary embodiment of the present invention;

[0021] FIG. 12 is a flowchart illustrating a method of operating a notification policy server according to an exemplary embodiment of the present invention;

[0022] FIG. 13 is a diagram illustrating a process of building an in- browser message policy DB according to an exemplary embodiment of the present invention;

[0023] FIG. 14 is a diagram illustrating a process of transmitting a message to a Web browsing user according to an exemplary embodiment of the present invention;

[0024] FIG. 15 is a flowchart illustrating a process of transmitting a message to a Web browsing user according to an exemplary embodiment of the present invention;

[0025] FIG. 16 is a flowchart illustrating a method of operating a traffic mapping server according to an exemplary embodiment of the present invention;

[0026] FIG. 17 is a diagram illustrating a process of transmitting a message to an in-app module using an event generated in the user terminal according to an exemplary embodiment of the present invention; and

[0027] FIG. 18 is a diagram illustrating a process of transmitting a message to a user who performs browsing over a mobile communication network using an event generated in the user terminal according to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

[0028] Hereinafter, preferred exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this case, it should be noted that in the accompanying drawings, the same components are denoted with the same reference numerals. Further, detailed description of known functions and configurations, which may make the gist of the present invention ambiguous, will be omitted.

[0029] It will be understood that when an element is referred to as being “connected” to another element, it can be directly connected to the other element or intervening elements may be present. It will also be understood that when a unit “comprises or includes” a component, the unit may further comprise or include another component, unless otherwise defined.

[0030] FIG. 1 is a diagram illustrating a network system according to an exemplary embodiment of the present invention.

[0031] Referring to FIG. 1, a network system according to an : exemplary embodiment of the present invention may include a user terminal

101, a GGSN/PDSN or P-GW 103, probing devices 105 and 115, an Internet gateway 107, the Internet 109, another network provider 111, an AAA server 113, a PDP context probing server 117, a session builder server 119, a mobile session database 121, a mobile session server 123, a profiling policy server ; 125, a profiled user group database 127, a notification policy server 129, a notification database 131, a traffic mapping server 133, an app session server 135, an in-browser push server 137, an in-app push server 139, and an external server 141.

[0032] Some of the respective components may be components that are currently used in a communication network. For example, the GGSN/PDSN

P-GW 103, the Internet gateway 107, and the AAA server 113 may be general components that can be currently used in the communication network.

Further, some of the respective components may be unique components necessary for the present invention. For example, the profiling policy server 125 and the profiled user group database 127 are unique components necessary for the present invention. However, the respective components may be variously changed as necessary, and one component may perform a function of the other configuration. : [0033] Hereinafter, the respective components will be described together with exemplary embodiments.

[0034] FIG. 2 is a diagram illustrating session information according to an exemplary embodiment of the present invention.

[0035] In general, methods of monitoring status of an Internet user terminal in real time may be classified into two methods. First, the user ,

terminal may collect and manage user status in real time through a process of connecting to a data network, such as an authentication process, to use a data service of a communication provider. An application may be installed in a smart phone, a PC, or the like used by a user or an add-on module is provided to an application in use such that a connection status of the user can be collected and managed in real time. According to an exemplary embodiment of the present invention, session information may be configured in consideration of the two methods.

[0036] Referring to FIG. 2, the session information according to an exemplary embodiment includes a token ID 210, session information received from a network provider, and session information received from an in-app ; push server.

[0037] According to an exemplary embodiment of the present invention, it is possible to manage the session information in an integrated manner through the session information and the application through a communication provider, and build a more sophisticated complementary ; session information database in real time.

[0038] FIG. 3 is a diagram illustrating a process of status-managing and profiling a user terminal over a mobile communication network according to an exemplary embodiment of the present invention. :

[0039] The user terminal first performs an authentication process for connecting to a network of a communication provider to use a communication service. Referring to FIG. 3, in operation (a), the user terminal 101 transmits : international mobile station identity (IMSI) that is its own information to the :

network to connect to the packet data network. In operations (b) and (c), the

GGSN/PDSN or PDN GW 103 receives the IMSI and requests an AAA server 113 to start a session via a probing device 115. In operations (d) and (e), the ;

AAA server 113 receives the session start request and transmits a response to the request to the GGSN/PDSN or PDN GW 103 via the probing device 115.

Through this process, the GGSN/PDSN or PDN GW 103 exchanges the session information with the AAA server 113. Thereafter, the GGSN/PDSN or PDN GW 103 transfers a connection allowing or denying message to the user terminal 101 according to content of the response.

[0040] Hereinafter, a process of status-managing and profiling the user terminal 101 on the assumption that the user terminal 101 connects to a network of a communication provider will be described.

[0041] In operation (1), the probing device 115 transmits session information acquired between the GGSN/PDSN or PDN GW 103 and the

AAA server 113 to the PDP context probing server 117. In this case, the probing device 115 may clone a connection request transmitted to the AAA server 113 and the response thereto, and transmit the cloned request and response to the PDP context probing server 117. ’ [0042] In operation (2), the PDP context probing server 117 that receives the session information for use of the data network of the subscriber from the probing device 115 extracts data to be used for profiling from the received session information, and transmits the data to the session builder : server 119. The data to be used for profiling, which has been extracted in this : process, may include, for example, international mobile station identity (IMSI)

of the user terminal, a mobile station international ISDN number (MSISDN), position information, connected terminal information, and information regarding a network to which the user terminal is connected.

[0043] In operation (3), the session builder server 119 searches for the mobile session database 121 to check if there is information regarding a session established over another network or a current network. When there has already been the session information, the session builder server 119 updates the mobile session database 121 with the data to be used for profiling.

When there is no session information, the session builder server 119 adds new session information to the mobile session database 121. This process will be described with reference to FIG. 5.

[0044] FIG. 5 is a flowchart illustrating a method of operating the session builder server according to an exemplary embodiment of the present : invention.

[0045] Referring to FIG. 5, first, the data to be used for profiling is received from the PDP context probing server 117 in operation 510, and the : mobile session database 121 is searched for to determine whether there is information regarding a session established over another networks or a current network in operation 520. Since a process of status-managing and profiling the user terminal over a mobile communication network is described in FIG. 3, the data to be used for profiling is received from the PDP context probing server 117, but in the process of status-managing and profiling a user terminal over another network, the data to be used for profiling may be received from i the app session server 135. This will be separately described below.

[0046] When it is determined in operation 520 that there is information regarding a session established over another network or a current network, the session builder server 119 proceeds to operation 540 to update the mobile session database 121 with the data to be used for profiling. When it is determined in operation 520 that there is no information regarding a session established over another network or a current network, the session builder server 119 proceeds to operation 530 to add new session information to the mobile session database 121. : [0047] Further, although not illustrated in FIGS. 3 and 5, the session builder server 119 may transmit a message to request current status of the user terminal 101 so as to more positively recognize the status of the user terminal 101. :

[0048] Referring back to FIG. 3, the profiling policy server 125 stores profiling conditions set by a manager in advance. In operation (4), when the session builder server 119 changes the mobile session database 121, the profiling policy server 125 fetches changed session information and prepares for profiling. According to an exemplary embodiment of the present invention, which of user terminal groups having separate profile attributes to . include the fetched session information is determined :

[0049] In operation (5), the profiled user group database 127 is updated according to this determination. This process will be described with reference to FIG. 4.

[0050] FIG. 4 is a flowchart illustrating a method of operating the profiling server according to an exemplary embodiment of the present invention. ’ [0051] Referring to FIG. 4, it is first determined whether the session i builder server 119 changes the mobile session database 121 in operation 410.

When it is determined in operation 410 that the session builder server 119 : changes the mobile session database 121, the process proceeds to operation 420 to fetch the changed session information, and when it is determined that the session builder server 119 does not change the mobile session database 121, the process ends.

[0052] Then, the profiling policy server 125 proceeds to operation 430 to determine a user terminal group among user terminal groups having separate profile attributes to include the fetched session information according . to the set profiling conditions, and proceeds to operation 440 to update the 156 profiled user group database 127 according to this determination.

[0053] Through this profiling process, a communication provider can recognize status of the user who uses the Internet or connects to the Internet, and build a database for providing a service using the status of the user in future.

[0054] Hereinafter, a profiling process according to an occurring event will be described in greater detail with reference to FIGS. 6 and 7.

[0055] FIG. 6 is a diagram illustrating a process of updating connection information of the user terminal through a network system according to an : exemplary embodiment of the present invention. :

[0056] In FIG. 6, a process of performing updating with changed status when status of the user is changed and, for example, when position information is changed or a connected network is changed due to a movement of the user is assumed. Entire content is similar to the content shown in FIG. 3.

[0057] Referring to FIG. 6, in operation (a), a GGSN/PDSN or PDN

GW 103 is notified of an event indicating that the status of the user terminal 101 has been changed from another server in the same network when the status of the user terminal 101 is changed. In operations (b) and (c), the

GGSN/PDSN or PDN GW 103 receives the notification and requests a AAA server 113 to update the session via a probing device 115. In operations (d) and (e), the AAA server 113 receives the session update request, and transmits a response to the request to the GGSN/PDSN or PDN GW 103 via the probing device 115. Through this process, the GGSN/PDSN or PDN GW 103 exchanges session information with the AAA server 113.

[0058] Hereinafter, the process of status-managing and profiling a user terminal 101 on the assumption that the status of the user terminal 101 has been changed will be described.

[0059] In operation (1), the probing device 115 transmits the session : information acquired between the GGSN/PDSN or PDN GW 103 and the

AAA server 113 to a PDP context probing server 117. In this case, the probing device 115 may clone a connection request transmitted to the AAA ] server 113 and the response thereto, and transmit the cloned request and response to the PDP context probing server 117.

[0060] In operation (2), the PDP context probing server 117 that receives the updated session information from the probing device 115 transmits a request to update a new session information to the session builder server 119.

[0061] In operation (3), the session builder server 119 updates the mobile session database 121.

[0062] In operation (4), the profiling policy server 125 detects that the : session builder server 119 has changed the mobile session database 121, fetches the changed session information, and prepares for profiling.

According to an exemplary embodiment of the present invention, which of user terminal groups having separate profile attributes to include the fetched session information is determined

[0063] In operation (5), the profiled user group database 127 is updated according to this determination.

[0064] FIG. 7 is a diagram illustrating a process when the user terminal is disconnected through a network system according to an exemplary embodiment of the present invention.

[0065] In FIG. 7, a case in which the user terminal is disconnected and entire content is similar to the content shown in FIG. 3.

[0066] Referring to FIG. 7, in operation (a), the GGSN/PDSN or PDN

GW 103 is notified of an event that the user terminal 101 has been : disconnected from another server in the same network when the user terminal 101 has been disconnected. in operations (b) and (c), the GGSN/PDSN or . PDN GW 103 receives the notification, requests the AAA server 113 to release the session via the probing device 115. In operations (d) and (e), the

AAA server 113 receives the session release request, and transmits a response to the request to the GGSN/PDSN or PDN GW 103 via the probing device 115.

[0067] Hereinafter, a process of status-managing and profiling the user terminal 101 on the assumption that the user terminal 101 is disconnected will be described.

[0068] In operation (1), the probing device 115 transmits session information acquired between the GGSN/PDSN or PDN GW 103 and the

AAA server 113 to the PDP context probing server 117. In this case, the probing device 115 may clone a connection request transmitted to the AAA server 113 and the response thereto, and transmit the cloned request and response to the PDP context probing server 117.

[0069] In operation (2), the PDP context probing server 117 that receives the session information from the probing device 115 extracts disconnection information from the session information, and transmits the disconnection information to the session builder server 119.

[0070] In operation (3), the session builder server 119 deletes the session information of the user terminal 101 from the mobile session database 121.

[0071] In operation (4), a profiling policy server 125 detects that the session builder server 119 has changed the mobile session database 121, fetches the changed session information, and prepares for profiling.

According to an exemplary embodiment of the present invention, the disconnected user terminal 101 may be deleted from a user terminal group to : which the user terminal 101 belongs.

[0072] In operation (5), the profiled user group database 127 is updated according to this determination.

[0073] FIGS. 8 to 10 illustrate a process of status-managing and profiling a user terminal over another network rather than the mobile communication network.

[0074] FIG. 8 is a diagram illustrating a process of status-managing and profiling a user terminal over another network according to an exemplary embodiment of the present invention.

[0075] According to the exemplary embodiment shown in FIG. 8, it is assumed that in a user terminal 101, an in-app push module have been installed as an independent module or as a module embedded in another application.

[0076] In operation (1), the in-app push module installed in the user terminal 101 connects to an app session server 135. When the in-app push module connects to the app session server 135 in this manner, the user terminal 101 may receive a push message.

[0077] In operation (2), the app session server 135 extracts data to be used for profiling from the session information of a session established between the in-app push module and the app session server 135, and transmits the data to the session builder server 119. The data to be used for profiling, which is extracted in this process, may include, for example, an App ID of the : user terminal 101, GPS position information, connected terminal information, ”

connected network information (for example, Wi-Fi, mobile communication network, or Bluetooth), an IP address, and a MAC address.

[0078] In operation (3), the session builder server 119 searches for the : mobile session database 121 to check if there is information regarding a session established over another network or a current network. When there has already been the session information, the session builder server 119 . updates the mobile session database 121 with the data to be used for profiling.

When there is no session information, the session builder server 119 adds new session information to the mobile session database 121. This process has been described with reference to FIG. 5.

[0079] Since FIG. 5 has been described above, repeated description is omitted. Here, the data to be used for profiling may be received from the app session server 135 in operation 510, unlike that described in FIG. 8.

[0080] Referring back to FIG. 3, the profiling policy server 125 stores profiling conditions set by a smnager in advance. In operation (4), when the session builder server 119 changes the mobile session database 121, the profiling policy server 125 fetches changed session information and prepares for profiling. According to an exemplary embodiment of the present invention, which of user terminal groups having separate profile attributes to include the fetched session information is determined

[0081] In operation (5), the profiled user group database 127 is updated according to this determination. This process has been described with reference to FIG. 4. Since FIG. 4 has been described above, repeated description is omitted.

[0082] Through this profiling process, it is possible to recognize status of the user connected to the network over another network rather than the mobile communication network, and to build a database for providing a service using the user status in future.

[0083] Hereinafter, the profiling process according to an occurring event will be described in greater detail with reference to FIGS. 9 and 10.

[0084] FIG. 9 is a diagram illustrating a process of changing session information over another network according to an exemplary embodiment of the present invention.

[0085] In FIG. 9, a process of performing updating with changed status when status of the user is changed and, for example, when GPS position : information is changed or a cell ID is changed due to a movement of the user terminal 101 is assumed. Entire content is similar to the content shown in FIG. 8.

[0086] Referring to FIG. 9, in operation (1), when the GPS position information, the cell ID, or the like is changed, the in-app module installed in the user terminal 101 transmits such information to the app session server 135.

[0087] In operation (2), the app session server 135 extracts the data to be used for profiling, and transmits the data to the session builder server 119.

That is, the app session server 135 transmits a request for update for new session information to the session builder server 119. } [0088] In operation (3), the session builder server 119 updates the mobile session database 121.

[0089] In operation (4), a profiling policy server 125 detects that the session builder server 119 has changed the mobile session database 121, fetches the changed session information, and prepares for profiling.

According to an exemplary embodiment of the present invention, which of user terminal groups having separate profile attributes to include the fetched session information is determined

[0090] In operation (5), the profiled user group database 127 is updated according to this determination.

[0091] FIG. 10 is a diagram illustrating a process when a user terminal is disconnected over another network according to an exemplary embodiment of the present invention.

[0092] In FIG. 10, a case in which the user terminal is disconnected is illustrated. Entire content is similar to that shown in FIG. 8.

[0093] Referring to FIG. 10, when the user terminal 101 is disconnected, the app session server 135 detects this and ends the session in operation (1).

[0094] In operation (2), the app session server 135 extracts the session : information of the user terminal 101 from a session ending processing event, : and transmits the session information to the session builder server 119.

[0095] In operation (3), the session builder server 119 deletes the session information of the user terminal 101 from the mobile session database : 121.

[0096] In operation (4), the profiling policy server 125 detects that the session builder server 119 has changed the mobile session database 121, fetches the changed session information, and prepares for profiling.

According to an exemplary embodiment of the present invention, the disconnected user terminal 101 may be deleted from the user terminal group to which the user terminal 101 belongs.

[0097] In operation (5), the profiled user group database 127 is updated according to this determination.

[0098] The process of collecting status information of the user terminal 101 and performing profiling has been described above. Hereinafter, a process of transmitting a message to the user terminal 101 using the database collected in this way will be described.

[0099] FIG. 11 is a diagram illustrating a process of building a notification DB according to an exemplary embodiment of the present invention.

[00100] A service provider over a communication network, such as an advertising service provider, transmits advertisement to only a user terminal 101 satisfying desired conditions. Thus, it is possible to increase efficiency of the service. FIG. 11 illustrates a database building process for providing service from the service provider to only the user terminal 101 satisfying the desired condition.

[00101] Referring to FIG. 11, in operation (1), a campaign management server 149 stores a campaign for transmitting a message in a campaign database 147. According to an exemplary embodiment of the present . invention, a list of users that will receive a message according to profile conditions, a message to be transmitted to the user, and messaging conditions may be stored in the campaign database 147.

[00102] In operation (2), the notification policy server 129 fetches an active campaign from the campaign database 147.

[00103] In operation (3), the notification policy server 129 periodically : updates a user group that is a target receiving the message according to the fetched campaign. In this case, the notification policy server 129 may select a user group from the profiled user group database 127 and update the user : group that is a target receiving the message.

[00104] In operation (4), the notification policy server 129 maps the selected user group to the messaging_campaign and stores the user group and ; the campaign in the notification database 131.

[00105] This process is illustrated in FIG. 12.

[00106] FIG. 12 is a flowchart illustrating a method of operating a notification policy server according to an exemplary embodiment of the present invention.

[00107] First, the notification policy server 129 fetches messaging requirements from the campaign database (campaign DB) in which a i messaging policy (campaign) is stored in operation 1210.

[00108] Then, the notification policy server 129 selects a user group that will receive a message from the profiled user terminal group DB according to the messaging policy in operation 1220.

[00109] Finally, the notification policy server 129 maps the selected user group to the messaging policy, and stores the user group and the messaging policy in the notification database 131 in operation 1230.

[00110] Referring back to FIG. 11, when the user terminal group DB : profiled according to the messaging policy is changed, this may be reflected to update the notification database 131 built in this way.

[00111] Through the process illustrated in FIG. 11, it is possible to build a database in which the specific policy and the specific user group are mapped so that the service provider can transmit the message to only users satisfying desired conditions.

[00112] FIG. 13 is a diagram illustrating a process of building an in- browser message policy DB according to an exemplary embodiment of the present invention.

[00113] All data traffic transmitted between the user and the Internet is i transmitted from the probing device 105 to the traffic mapping server 133.

Accordingly, it should be selected whether the message is pushed to the user's browser when which of the traffic is generated. A policy for such a selection is stored in the in-browser messaging policy database 143, and the in-browser messaging policy management server 145 provides an interface to establish such a policy.

[00114] Referring to FIG. 13, in operation (1), the in-browser messaging policy management server 145 stores the traffic filtering conditions set automatically by the system or set by a manager in the in-browser messaging policy database 143.

[00115] In this case, policy information may include protocol, request/response, a messaging policy, messaging date and time zone, user terminal information, and destination website information.

[00116] Here, the user terminal information may include an IP address list or range, a list or range of MSISDNSs by which a message is to be received, ! a list or range of MSISDNs to which a message should not be transmitted, a list or range of IMSIs by which a message is to be received, a list or range of

IMSIs to which a message should not be transmitted, a list or range of MAC addresses by which a message is to be received, a list or range of MAC . addresses to which a message should not be transmitted, a specific terminal or terminal group by which a message is to be received, a specific terminal or terminal group to which a message should not be transmitted, a position of a user for receiving a message, and a position of a user to which a message should not be transmitted.

[00117] The destination website information may include a destination domain list to which message transmission is to be performed, a destination domain list to which message transmission should not be performed, a destination IP address list to which message transmission is to be performed, a destination IP address list to which message transmission should not be performed, a destination URL/URI list to which message transmission is to be performed, a destination URL/URI list to which message transmission should not be performed, and a content type list received from a destination to which message transmission is to be performed.

[00118] In operation (2), the traffic mapping server 133 reads the policy stored in the in-browser messaging policy database 143, filters user Internet traffic, and maps the traffic to an appropriate notification message.

[00119] FIG. 14 is a diagram illustrating a process of transmitting a } message to a Web browsing user according to an exemplary embodiment of the present invention, and FIG. 15 is a flowchart illustrating a process of transmitting a message to a Web browsing user according to an exemplary embodiment of the present invention.

[00120] A process of transmitting a message to a Web browsing user will : be described with reference to FIGS. 14 and 15. In FIGS. 14 and 15, the same processes are denoted with the same reference numerals. Further, in FIGS. 14 and 15, a situation in which the user is using a Web browser is assumed.

[00121] First, the user terminal 101 connecting to a network of a communication provider and registering a session for use of data requests a

Web server to provide the data. More specifically, the user terminal 101 transmits a data request for the destination Web server 151 to the probing device 105 in operation 1401. The probing device 105 receives this request, and transmits the request to the Internet gateway 107 in operation 1402. The

Internet gateway 107 transmits the request to the destination Web server 151.

In this process, the probing device 105 proceeds to operation 1403 to clone the ; data request received from the user terminal 101 and transmit the data request to the traffic mapping server 133, separately from operation 1402. According to an exemplary embodiment of the present invention, the probing device 105 may be a router or a tapping device.

[00122] In operation 1410, the traffic mapping server 133 analyzes the data request received from the probing device 105 and determines whether a message is to be transmitted according to the in-browser messaging policy.

Here, when the message is determined to be transmitted, the traffic mapping server 133 proceeds to operation 1411 and transmits a message transmission request to the in-browser push server 137. When the message is determined not to be transmitted, the request is ignored, and processing is not performed (discarded). FIG. 16 illustrates an operation of the traffic mapping server 133.

[00123] FIG. 16 is a flowchart illustrating a method of operating the traffic mapping server according to an exemplary embodiment of the present invention.

[00124] First, in operation 1610, the traffic mapping server 133 receives a data request message from the user terminal 101.

[00125] Then, in operation 1620, the traffic mapping server 133 extracts the in-browser messaging policy for the user terminal from the in-browser messaging policy database 143. This is intended to determine whether a message is pushed to the user's browser when any traffic is generated.

[00126] Then, the traffic mapping server 133 determines whether to transmit the message according to the extracted in-browser messaging policy in operation 1630.

[00127] When it is determined in operation 1630 that the message is transmitted according to the extracted in-browser messaging policy, the traffic mapping server 133 proceeds to operation 1640 to transmit the message, and otherwise, the traffic mapping server 133 proceeds to operation 1650 to discard the request.

[00128] Referring back to FIG. 14, the in-browser push server 137 receives the message transmission request, and searches for the notification database 131 to determine whether there is an active policy (campaign) in operation 1420. According to an exemplary embodiment of the present invention, it may be checked if there is currently an active policy based on data such as traffic generation conditions, a user that has generated the traffic, a traffic generation position, or a terminal in use by the user. When there is no active policy, the request is ignored, and processing is not performed (discarded).

[00129] When conditions that an in-browser push message should be transmitted to the user terminal that has generated the traffic are satisfied, the in-browser push server 137 proceeds to the next operation to push the message.

That is, the in-browser push server 137 transmits a request cancellation message to the destination Web server 151 via the Internet gateway 107 on behalf of the user terminal 101, to thereby drop the request transmitted by the user terminal in operations 1421 and 1422.

[00130] Then, the in-browser push server 137 transmits a response to the user terminal 101 via the Internet gateway 107 on behalf of the destination

Web server 151 in operations 1423 and 1424. This response includes a message to make a request for transmission of the push message to the in- browser push server 137, and a message to make a request for retransmission of the data request message to the destination Web server 151.

[00131] In operation 1424, the user terminal 101 that has received the response from the in-browser push server 137 retransmits the data request message to the destination Web server 151 via the probing device 105 and the

Internet gateway 107 in operations 1431, 1432, and 1433. In this case, the data request message is the same as the message transmitted in operation 1401.

The traffic mapping server 133 may recognize the request transmitted in such a process, but the traffic mapping server 133 does not additionally perform a separate operation since the request has already been processed.

[00132] The destination Web server 151 that has received the data request message transmits a response to the user terminal 101 via the probing device 105 and the Internet gateway 107 in operations 1434, 1435, and 1436.

[00133] Operations 1441 to 1447 are performed in parallel with : operations 1431 to 1436.

[00134] In operation 1424, the user terminal 101 receiving the response from the in-browser push server 137 requests the in-browser push server 137 to transmit the push message via the probing device 105 and the Internet gateway 107 in operations 1441, 1442, and 1434. In this process, the probing device 105 may clone the request and transmit the request to the traffic mapping server 133 in operation 1443, but the traffic mapping server 133) does not perform a separate operation.

[00135] The in-browser push server 137 receiving the data request message transmits a notification message to the user terminal 101 via the probing device 105 and the Internet gateway 107 in operations 1445, 1446, and 1447.

[00136] According to an exemplary embodiment of the present invention, through this process, the service provider provides a service to only the user terminal 101 satisfying the desired conditions, and thus, it is possible to increase efficiency of the service.

[00137] FIG. 17 is a diagram illustrating a process of transmitting a message to an in-application module using an event generated in the user ! terminal according to an exemplary embodiment of the present invention.

[00138] A process of sensing any event and transmitting a message to the in-app module when the event is generated in the user terminal 101 will be described with reference to FIG. 17.

[00139] A process in operations (1) to (3) is a process in which user status information is updated between the GGSN/PDSN or P-GW 103 and the

AAA server 113 when a specific event is generated in the user terminal 101 that receives a data service over a mobile communication network.

[00140] In operation (4), the probing device 105 transmits updated user status information acquired between the GGSN/PDSN or PDN GW 103 and the AAA server 113 to the PDP context probing server 117. In operation (5), the PDP context probing server 117 transmits the updated user status information to the session builder server 119. In operation (6), the session builder server updates the mobile session database 121.

[00141] The profiling policy server 125 detects session information : including the user status information updated in the mobile session database 121 in operation (7), and accordingly, updates the profiled user group database in operation (8).

[00142] The notification policy server 129) fetches the changed profiled user group database 127 in operation (9), and generates a new notification message to be transmitted to the user of which the information has been ”

changed, and stores the new notification message in the notification database 131 in operation (10).

[00143] The in-app push server 139 fetches the new notification message to be transmitted to the user of which the information has been changed from : the notification database 131 in operation (11), and transmits the new notification message to the in-app module installed in the user terminal 101 in operation (12).

[00144] FIG. 18 is a diagram illustrating a process of transmitting a message to a user who performs browsing over a mobile communication network using an event generated in the user terminal according to an exemplary embodiment of the present invention.

[00145] In operation (1), a session connection is made over other networks 111 and 109 rather than the mobile communication network between : the in-app push module installed in the user terminal 101 and the app session server 135. :

[00146] In operation (2), the app session server 135 extracts the data to be used for profiling from session information of the session established between the in-app push module and the app session server 135, and transmits the data to the session builder server 119. In operation (3), the session builder server 119 updates the mobile session database 121.

[00147] The profiling policy server 125 detects the session information including user status information updated in the mobile session database 121 . in operation (4), and updates the profiled user group database 127 with the session information in operation (5).

[00148] The notification policy server 129 fetches the changed profiled user group database 127 in operation (6), and generates a new notification message to be transmitted to the user of which the information has been changed and stores the message in the notification database 131 in operation

[00149] This process is a process in which the notification database 131 is updated through a session connection made over another network rather ) than the mobile communication network. Hereinafter, a process in which a notification message is transmitted using such an updated notification database 131 when the user terminal 101 performs web browsing over the mobile communication network will be described.

[00150] In operation (a), when the user terminal 101 requests the Web server to provide data, the traffic mapping server 133 detects this and proceeds to operation (b) to transmit a notification request to the in-browser push server 137. The in-browser push server 137 receives the request, fetches the notification database 131 in operation (c), and transmits a notification message to the user terminal 101 based on the notification database 131 in operation (d). . [00151] Through such a process, an event generated in the user terminal 101 can be received over the other network, and a notification message can be transmitted over the mobile communication network.

[00152] The exemplary embodiment of the invention described above may be implemented as instructions executed by a processor and stored in a computer-readable storage medium. When the instructions are executed by the processor, means for implementing the functions/operations specified in the flowcharts and/or block diagrams described above can be made. In the ; flow charts/block diagrams, respective blocks may also indicate hardware : and/or software modules or logics that implement the exemplary embodiments of the present invention. Further, the functions noted in the block diagrams may also be performed in order different from an order shown in the drawings, or may be performed simultaneously.

[00153] The computer-readable storage medium may include, for example, a floppy disk, a ROM, a flash memory, a disc drive memory, a CD-

ROM, or a non-volatile memory such as a permanent storage unit, but is not limited thereto and various media can be used.

[00154] According to the present invention, the communication provider can transmit a message such as an advertisement, an information service, or : disaster warning according to status of a user who uses the Internet or connects to the Internet. ;

[00155] The exemplary embodiments of the present invention disclosed herein and the drawings are intended to easily describe the technical content of the invention and present specific examples in order to assist in understanding of the invention, and are not intended to limit the scope of the invention. It is obvious to a person skilled in the art that besides the exemplary embodiments disclosed herein, other modification examples based on the technical idea of the invention are possible.

Claims (15)

WHAT IS CLAIMED IS:

1. A user terminal managing method of a profiling server, the method comprising: determining whether a mobile session database is changed by a session builder server; fetching changed session information if the mobile session database is changed by the session builder server ; determining a user terminal groups to include the fetched session information from a plurality of user terminal groups with separate profile attributes based on set profiling conditions; and updating a profiled user group database (DB) according to the determination. 156

2. The method according to claim 1, wherein the session builder server performs receiving data to be used for profiling from a packet data protocol (PDP) context proving server or an app session server; searching for the mobile session DB and determining whether there is information regarding a session established over another network or a current network; and updating the mobile session DB with the data to be used for profiling when it is determined that there is the information regarding a session established over another network or a current network.

3. The method according to claim 2, } wherein the session builder server further performs adding the data to be used for profiling to the mobile session DB as new session information when it is determined that there is no information regarding a session established over another network or a current network.

4. The method according to claim 2, wherein the session builder server further performs transmitting a message to request current status of the user terminal.

5. The method according to claim 2, wherein the data to be used for profiling includes at least one of international mobile station identity (IMSI) of the user : terminal, mobile station international ISDN number (MSISDN), position information, connected terminal information, and information regarding a network to which the user terminal connects.

6. The method according to claim 2, wherein the data to be used for profiling includes at least one of an app ID of the user terminal, GPS position information, connected terminal information, connected network information, an IP address, and a MAC address. :

7. A user terminal managing method of a notification policy server, the method comprising: fetching messaging requirements from a campaign DB includes a messaging policy (campaign); selecting a user group to receive a message from a profiled user terminal group DB according to the messaging policy; mapping the selected user group to the messaging policy; and storing the user group and the messaging policy in a notification DB.

8. The method according to claim 7, wherein the messaging policy includes at least one of a user terminal to receive a message, a message to be transmitted to the user terminal, and messaging conditions based on profile conditions.

9. The method according to claim 7, further comprising: after the storing in the notification DB, updating the notification DB when the profiled user terminal group DB is changed according to the messaging policy.

10. The method according to claim 9, further comprising: after the updating of the notification DB, transmitting a message to the user terminal through an in-app push server or an in-browser push server.

11. A user terminal managing method of a traffic mapping server, the . method comprising: receiving a data request message of the user terminal; extracting an in-browser messaging policy for the user terminal from an in-browser messaging policy database (DB); determining whether to transmit a message according to the extracted in-browser messaging policy; and transmitting a message transmission request to an in-browser push server when it is determined to transmit a message according to the in-browser messaging policy. }

12. The method according to claim 11, wherein the in-browser messaging policy DB stores policy conditions set by an in-browser messaging policy management server.

13. The method according to claim 12, wherein the policy conditions include at least one of a protocol, a request/response, a messaging policy, a messaging date and time zone, user terminal information, and Web browsing destination website information.

14. The method according to claim 11, wherein the in-browser push server performs determining whether there is an active campaign for the user terminal through a notification DB; transmitting a request cancellation message to a Web server on behalf of the user terminal when it is determined that there is the active campaign for the user terminal; and transmitting a response message to the user terminal on behalf of the Web server, the response message including a message to make a request for transmission of a push message to the in-browser push server, and a message to make a request for retransmission of the data request message to the Web server.

15. The method according to claim 14, wherein the in-browser push server performs receiving a request for transmission of the push message from the user terminal, and transmitting the message according to the request for transmission of the push message.