Method for providing an electronic device and push notifications thereof

Abstract

A method for providing push notifications in an electronic device according to one embodiment of the present disclosure may include the steps of: generating a plurality of push campaigns related to an application; assigning identification information to each of the plurality of push campaigns; verifying information of a user to whom push notifications will be provided; verifying, based on the user information, at least one push campaign from the plurality of push campaigns to be transmitted to the user; and determining, based on a push frequency control model and the identification information of the at least one push campaign, whether or not to transmit at least one push notification corresponding to the at least one push campaign to the user's terminal.

Description

Technical Field

[0001] This disclosure relates to a technology for providing an electronic device and its push notifications.

Background Art

[0002] With the development of electronic technology, e-commerce has become established as a field of shopping. Customers can order food and beverages online and have them delivered to their desired addresses. In the case of e-commerce, since providing detailed and accurate information about products has a considerable impact on service satisfaction, it is important to provide more detailed and accurate information.

[0003] A push notification can be a short message displayed as a pop-up on the screen of a terminal device. In particular, by appropriately providing application-related push notifications to a user's terminal periodically, the application-related user experience and the user's application usage time can be significantly improved.

[0004] However, if push notifications are transmitted to a user's terminal too frequently, the user may feel fatigue and may block the reception of push notifications. Therefore, it is important to provide push notifications effectively while reducing the user's fatigue.

Summary of the Invention

Problems to be Solved by the Invention

[0005] According to one embodiment of the present disclosure, a technical problem to be solved is to enable push notifications to be effectively transmitted to a user by adjusting the transmission frequency of the push notifications.

Means for Solving the Problems

[0006] A method for providing push notifications in an electronic device according to one embodiment of the present disclosure may include the steps of: generating a plurality of push campaigns related to an application; assigning identification information to each of the plurality of push campaigns; verifying information of a user to whom the push notifications will be provided; verifying, based on the user information, at least one push campaign from the plurality of push campaigns to be transmitted to the user; and determining, based on a push frequency control model and the identification information of the at least one push campaign, whether or not to transmit at least one push notification corresponding to the at least one push campaign to the user's terminal.

[0007] The identification information according to one embodiment includes information relating to a business type, and the information relating to a business type may include at least one of the following: a first type relating to a one-time push notification, a second type relating to a regular push notification, a third type relating to an emergency push notification, a fourth type relating to a test push notification, a fifth type relating to a system push notification, or a sixth type relating to a core push notification.

[0008] The push frequency control model according to one embodiment includes an effective time period model, and the step of determining whether or not to transmit the at least one push notification to the user's terminal may include a step of checking whether the transmission time set for the at least one push notification falls within a predetermined effective time range; and, if the transmission time set for the at least one push notification falls within the effective time range, a step of checking the identification information of the at least one push campaign.

[0009] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of transmitting the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the first type or the second type; and the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third type, the fourth type, the fifth type, or the sixth type.

[0010] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of deciding not to transmit the at least one push notification to the user's terminal if the transmission time set for the at least one push notification does not fall within the valid time range.

[0011] The push frequency control model according to one embodiment includes a maximum push control model, and the step of determining whether or not to transmit the at least one push notification to the user's terminal may include: checking the number of push notifications transmitted to the user's terminal during a predetermined period; comparing the checked number with a predetermined critical value; and, if the checked number is less than the critical value, checking the identification information of the at least one push campaign.

[0012] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of transmitting the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the first type or the second type; and the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third type, the fourth type, the fifth type, or the sixth type.

[0013] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of deciding not to transmit the at least one push notification to the user's terminal if the number of confirmed notifications is equal to or greater than the critical value.

[0014] The embodiment further includes a step of confirming the click-through rate of the user to the push notification, wherein the critical value may be a value determined based on the click-through rate.

[0015] The push frequency control model according to one embodiment includes a time interval control model, and the steps of determining whether or not to transmit the at least one push notification to the user's terminal may include: confirming the transmission time of the push notification most recently transmitted to the user's terminal; confirming whether or not a predetermined critical time has elapsed since the confirmed transmission time; and, if the predetermined critical time has elapsed since the confirmed transmission time, confirming the identification information of the at least one push campaign.

[0016] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of transmitting the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the first type or the second type; and the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third type, the fourth type, the fifth type, or the sixth type.

[0017] The step of determining whether or not to transmit the at least one push notification to the user's terminal according to one embodiment may further include the step of deciding not to transmit the at least one push notification to the user's terminal if a predetermined critical time has not elapsed from the confirmed transmission time.

[0018] A method for providing the push notification according to one embodiment further includes the step of checking the click-through rate of the user to the push notification, wherein the critical time may be a value determined based on the click-through rate.

[0019] A method for providing the push notification according to one embodiment may further include the steps of: receiving user input from the user's terminal regarding whether or not to activate the push frequency control model; and determining whether or not to activate the push frequency control model based on the user input.

[0020] According to one embodiment, the user information includes at least one of the user's name, gender, age, or address information, the identification information includes optional information relating to the target to which the push notification is provided, and the step of confirming the at least one push campaign may include a step of confirming, based on the user information and the optional information, at least one push campaign from the plurality of push campaigns to be transmitted to the user.

[0021] A computer-readable non-temporary recording medium according to one embodiment of the present disclosure may be a non-temporary recording medium on which a program for causing a computer to perform the method of providing the push notification is recorded.

[0022] An electronic device according to an embodiment of the present disclosure includes a communication interface, a memory, and a processor. The processor generates a plurality of push campaigns related to an application, assigns identification information to each of the plurality of push campaigns, checks information of a user to whom a push notification is to be provided, and based on the user's information, checks at least one push campaign to be transmitted to the user among the plurality of push campaigns, and is configured to determine whether to transmit at least one push notification corresponding to the at least one push campaign to the user's terminal based on a push frequency control model and the identification information of the at least one push campaign.

Advantages of the Invention

[0023] According to an embodiment of the present disclosure, by adjusting the transmission frequency of push notifications, push notifications can be effectively transmitted to users.

Brief Description of the Drawings

[0024] [Figure 1] A drawing illustrating a system according to an embodiment of the present disclosure. [Figure 2] A configuration diagram of an electronic device according to an embodiment of the present disclosure. [Figure 3] A schematic diagram related to a method for controlling the frequency of push notifications according to an embodiment of the present disclosure. [Figure 4] A schematic diagram of a push frequency control model according to an embodiment of the present disclosure. [Figure 5] A processing flowchart of an electronic device according to an embodiment of the present disclosure. [Figure 6] A processing flowchart of an electronic device according to an embodiment of the present disclosure. [Figure 7] A processing flowchart of an electronic device according to an embodiment of the present disclosure. [Figure 8] A processing flowchart of an electronic device according to an embodiment of the present disclosure. [Modes for carrying out the invention]

[0025] The terminology used in the embodiments has been selected to the greatest extent possible from currently widely used and general terms, taking into account the function described herein, although this may change depending on the intent of the articulators or case law, the emergence of new technologies, etc. In certain cases, the applicant has arbitrarily selected some terms, in which case their meaning will be described in detail in the relevant descriptive section. Therefore, the terminology used in this disclosure must be defined not merely as names of terms, but based on the meaning of the term and the overall content of this disclosure.

[0026] Throughout the specification, when a part "includes" a component, this means, unless otherwise stated, that it may include other components rather than excluding them. Furthermore, terms such as "...part" and "...module" used in the specification mean a unit that performs at least one function or operation, which may be embodied in hardware or software, or in a combination of hardware and software.

[0027] The expression “at least one of a, b, and c” as described throughout the specification may encompass “a alone,” “b alone,” “c alone,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”

[0028] The term "terminal" as used below may be defined as a computer or portable terminal capable of connecting to a server or other terminals via a network. Here, a computer includes, for example, a laptop, desktop, or laptop computer equipped with a web browser, while a portable terminal may include, for example, any wireless communication device that ensures portability and mobility, such as terminals based on communication infrastructures like IIMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), as well as any type of handheld wireless communication device such as a smartphone or tablet PC.

[0029] The embodiments of this disclosure will be described below in detail, with reference to the attached drawings, so that they can be easily implemented by a person with ordinary skill in the art to which this disclosure pertains. However, this disclosure can be embodied in a variety of different forms and is not limited to the embodiments described herein.

[0030] Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0031] In describing the embodiments, we will omit explanations of technical content that is well known in the art to which the present invention belongs and is not directly related to the present invention. This is to ensure that the gist of the present invention is communicated more clearly without becoming ambiguous by omitting unnecessary explanations.

[0032] For similar reasons, some components in the attached drawings are exaggerated, omitted, or only schematically represented. Furthermore, the dimensions of each component do not fully reflect their actual size. In each drawing, identical or corresponding components are assigned the same reference number.

[0033] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and can be embodied in a variety of different forms, and these embodiments are provided merely to complete the disclosure of the present invention and to fully inform those ordinary skill in the art to which the invention pertains, and the present invention is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.

[0034] At this point, it can be understood that each block of the processing flowchart diagram and the combination of the flowchart diagram can be performed by computer program instructions. Since these computer program instructions can be implemented in the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions performed via the processor of the computer or other programmable data processing equipment will generate means to perform the functions described in the flowchart blocks(et). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed to the computer or other programmable data processing equipment in order to embody the functions in a particular manner, the instructions stored in that computer-available or computer-readable memory can also produce manufactured items that contain instruction means to perform the functions described in the flowchart blocks(et). Since computer program instructions can also be implemented on a computer or other programmable data processing equipment, a series of operational steps can be performed on the computer or other programmable data processing equipment to generate a process executed on the computer, and instructions for the computer or other programmable data processing equipment can also provide steps for performing the functions described in the flowchart blocks(e).

[0035] Furthermore, each block may represent a module, segment, or portion of code containing one or more executable instructions for performing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in a block may occur out of order. For example, two blocks illustrated consecutively may effectively occur substantially simultaneously, or they may occasionally be performed in reverse order by the relevant functions.

[0036] Figure 1 is a diagram illustrating a system 10 according to one embodiment of the present disclosure. The system 10 disclosed herein may be a system 10 for controlling the frequency of push notifications for an application. The system 10 according to one embodiment may include an electronic device 100 and a terminal 200.

[0037] In one embodiment, the electronic device 100 may be a server for operating an application. The electronic device 100 may be a server-side server related to the application process and a back-end server that manages a database. The server can manage various programs (software) for operating the application. The electronic device 100 can communicate with a terminal 200 and send and receive various information. The electronic device 100 may acquire various information related to the application from the terminal 200 and provide it to other devices. The electronic device 100 can provide push notifications to the terminal 200.

[0038] In one embodiment, terminal 200 can be embodied as a portable terminal that can connect to electronic devices 100 or other terminals via a network. The portable terminal may include, for example, wireless communication devices that ensure portability and mobility, terminals based on communication infrastructures such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), as well as all kinds of handheld-based wireless communication devices such as smartphones and tablet PCs. Without being limited to this example, the terminal may be a variety of electronic devices equipped with computing capabilities. Users can run and use a variety of applications through the terminal. For convenience of explanation, the drawings show only one terminal 200, but there may be two or more terminals 200. Terminal 200 may be the terminal of a user (or customer) using an application.

[0039] According to one embodiment, the system 10 may further include an operator's terminal (not shown). The operator may be the entity that generates push campaigns related to the application. The operator may mean, for example, an operations or planning officer.

[0040] Figure 2 is a diagram illustrating a system 100 according to one embodiment of the present disclosure. The electronic device 100 according to one embodiment may include a processor 110, a memory 120, and a communication interface 130. At least one of the components included in the electronic device 100 may be omitted, or other components may be added to the electronic device 100. Additionally or alternatively, some components may be embodied as a combined entity or as one or more individuals. At least some components within the electronic device 100 may be embodied as a combined entity or as one or more individuals. At least some components within the electronic device 100 may be connected to each other via a bus, GPIO (general purpose input / output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface), etc., and may exchange data and / or signals.

[0041] In one embodiment, the processor 110 of the electronic device 100 may be operationally connected to the components of the electronic device 100 in a configuration that enables it to perform calculations or data processing related to the control and / or communication of each component of the electronic device 100. The processor 110 may load instructions or data received from other components of the electronic device 100 into the memory 120, process the instructions or data stored in the memory 120, and store the resulting data. Unless otherwise specified, in this disclosure, the processor 110 may mean a collection of one or more processors 110.

[0042] A memory 120 of an electronic device 100 according to one embodiment can store a variety of data used by at least one component (e.g., a processor 110). The memory 120 can store instructions for the operation of the processor 110 described above. Programs may be stored in the memory 120 as software and may include, for example, an operating system, middleware, or applications. Unless otherwise specified, in this disclosure, memory 120 may mean a collection of one or more memories 120.

[0043] In one embodiment, the communication interface 130 of the electronic device 100 can establish a wired or wireless communication channel with an external device (e.g., terminal 200) and send and receive various data with the external device. The communication interface 130 of the electronic device 100 may include at least one port for connecting to an external device by a wired cable in order to communicate with the external device via a wired connection. The communication interface 130 of the electronic device 100 may include a cellular communication module and be configured to connect to a cellular network (e.g., 3G, LTE, 5G, Wibro, or WiMAX). According to one embodiment, the communication interface 130 of the electronic device 100 may include a near-field communication module and be able to send and receive data with an external device using near-field communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), UWB).

[0044] According to one embodiment, the electronic device 100 may further include a database 140. The database 140 of the electronic device 100 can store a variety of data under the control of the processor 110. For example, the database 140 of the electronic device 100 can store multiple push campaigns related to an application.

[0045] Figure 3 is a schematic diagram of a method for controlling the frequency of push notifications according to one embodiment of the present disclosure.

[0046] Referring to Figure 3, an electronic device 100 according to one embodiment includes an IMP module 310, a push notification management module 320, a customer information management module 330, and a push notification relay module 340. The configuration shown in Figure 3 may be hardware modules or software modules. The configuration included in the electronic device 100 in Figure 3 can operate under the control of the processor 110 of the electronic device 100.

[0047] Operator 305 can generate multiple push campaigns using the IMP (intelligent marketing platform) module 310. For example, Operator 305 can connect to the electronic device 100 using its own terminal and generate multiple push campaigns using the IMP module 310. Operator 305 may be, for example, an entity that operates and manages an application and provides various push notifications to the application's users (customers). Operator 305 may be, for example, a marketer. In this diagram, it is shown that there is one Operator 305 generating push campaigns, but the number of Operators 305 is not limited to this and may be two or more.

[0048] A push campaign can be a file containing the information necessary to generate and transmit (send) a push notification. One type of push campaign can correspond to one type of push notification. The push notification can be transmitted to at least one user's device 200 in the future. The IMP module 310 can store multiple generated push campaigns in the database 140. A push campaign may include, for example, information about the target product, the target user, and the conditions for transmitting the push notification.

[0049] The IMP module 310 can assign (assign) identification information (e.g., a push ID) to each of multiple push campaigns. Different push campaigns may be assigned (assigned) different identification information. The identification information for a push campaign may consist of a series of numbers. In the future, the push frequency control model 345 of the push notification relay module 340 can decide whether or not to transmit a push notification to the user's terminal based on the identification information of the push campaign.

[0050] Identification information may include, for example, information about the business type. Business type information may include at least one of the following: Type 1 for one-time push notifications (OP), Type 2 for regular push notifications (RP), Type 3 for urgent push notifications (UP), Type 4 for test push notifications (TP), Type 5 for system push notifications (SP), or Type 6 for core push notifications (CP).

[0051] Identification information may further include, for example, a campaign ID, option information, a scene ID, a content ID, and a template ID. Option information may be information for A / B testing. Option information may include information related to the target (i.e., target users) to whom the push notification is delivered. The scene ID, content ID, and template ID may be information for identifying the push notification transmission algorithm.

[0052] The push notification management module 320 can read multiple campaigns stored in the database 140 and generate batch jobs. A batch job can mean a batch of work generated based on information from multiple campaigns. The push notification management module 320 can receive information from at least one user from the customer information management module 330. Based on the information from multiple campaigns and at least one user, the push notification management module 320 can determine at least one campaign to provide to the queue 325 and generate a batch job based on this.

[0053] The customer information management module 330 can provide information on multiple users to the push notification management module 320. User information may include, for example, the user's name, gender, and address. Based on the user information, the push notification management module 320 can identify (or select) at least one push campaign from among multiple push campaigns to provide a push notification to the user.

[0054] Queue 325 can receive at least one push campaign from the push notification management module 320. Queue 325 can transmit at least one push campaign to the push notification relay module 340 in the order in which they were received.

[0055] The push notification relay module 340 can determine whether or not to transmit at least one push campaign received from queue 325 to the user's terminal 200. Based on the push frequency control model 345 and the identification information of at least one push campaign, the push notification relay module 340 can determine whether or not to transmit at least one push notification corresponding to at least one push campaign to the user's terminal 200. A specific explanation of the push frequency control model 345 will be given later in Figure 4. Information regarding at least one push notification controlled based on the push frequency control model 345 may be stored in cluster 370. Cluster 370 may be a system for managing unstructured data.

[0056] The push notification relay module 340 can skip transmission of push campaigns that it has decided not to transmit to the user's terminal. For push campaigns that it has decided to transmit to the user's terminal 200, the push notification relay module 340 can transmit the decided push campaign to the push notification providing module 360 ​​(e.g., counos). The push notification providing module 360 ​​may be a third-party server that transmits push notifications using GCM (Google Cloud Messaging) or APNS (APNs Apple Push Notification Service).

[0057] Through the process described above, the electronic device 100 can control the frequency of push notifications transmitted to the user's terminal 200.

[0058] Figure 4 is a schematic diagram of a push frequency control model 345 according to one embodiment of the present disclosure.

[0059] According to one embodiment, the push frequency control model 345 may include a valid time period model 351, a max push control model 353, and a time interval control model 355.

[0060] One embodiment of the validity period model 351 may be a model that provides push notifications to the user's terminal 200 only during a predetermined validity period range, and blocks push notifications from being provided to the user's terminal 200 outside of the validity period range. For example, the validity period model 351 may allow push notifications to be provided to the user's terminal 200 only during a validity period range such as from 10 a.m. to 8 p.m., and block push notifications from being provided to the user's terminal 200 during times such as from 8 p.m. to 10 a.m.

[0061] One embodiment of the maximum push control model 353 may be a model that limits the number of push notifications provided to the user's terminal 200 during a defined period. The maximum push control model 353 may be a model that limits the number of push notifications provided to the user's terminal 200 per day. For example, the maximum push control model 353 can be controlled to transmit up to three notifications per day to the user's terminal 200.

[0062] One embodiment of the time interval control model 355 may be a model that controls the number of push notifications transmitted to the user's terminal 200 within a predetermined time. The time interval control model 355 can control the transmission of a push notification to the user's terminal 200 if a predetermined critical time (e.g., 30 minutes) has not elapsed since the transmission time of the most recently transmitted push notification to the user's terminal 200.

[0063] The push frequency control model 345 may decide whether or not to control the transmission frequency of push notifications based on the identification information assigned to the push campaign. For example, the push frequency control model 345 can decide whether or not to control the transmission frequency of push notifications based on information about the business type included in the identification information of the push campaign.

[0064] Figure 5 is a processing flowchart of an electronic device 100 according to one embodiment of the present disclosure.

[0065] Referring to the processing flowchart 500, in one embodiment, the processor 110 of the electronic device 100 can generate multiple push campaigns related to the application in step 510. For example, based on operator input, the processor 110 can generate multiple push campaigns related to the application. A push campaign may be a file containing information necessary to generate and transmit push notifications.

[0066] In one embodiment, the processor 110 can, in step 520, assign identification information to each of a plurality of push campaigns. The identification information may be information used to control the transmission frequency of push notifications. The identification information may include at least one of the following: business type information, campaign ID, option information, scene ID, content ID, and template ID. The business type information may include at least one of the following: type 1 for one-time push (OP), type 2 for regular push (RP), type 3 for urgent push (UP), type 4 for test push (TP), type 5 for system push (SP), or type 6 for core push (CP).

[0067] In one embodiment, the processor 110 can confirm information about the user to whom the push notification will be provided in step 530. The processor 110 can confirm information about the target user to whom the push notification will be provided. The processor 110 can confirm information about the user who has agreed to receive the push notification. For example, based on the identification information of multiple push campaigns, the processor 110 can confirm information about the user to whom at least one of multiple push notifications corresponding to multiple push campaigns will be provided. In this drawing, for the sake of explanation, it is assumed that there is one user, but it goes without saying that there can be multiple users.

[0068] In one embodiment, the processor 110 can, in step 540, identify at least one push campaign from among multiple push campaigns to be transmitted to the user. Based on the user's information, the processor 110 can identify at least one push campaign to be transmitted to the user. For example, if the identified user is a man in his 20s living in Seoul, the processor 110 can identify (select) at least one push campaign from among multiple push campaigns whose target is a man in his 20s living in Seoul.

[0069] In one embodiment, the processor 110 can determine in step 550 whether or not to transmit at least one push notification corresponding to at least one push campaign to the user's terminal 200. Based on the push frequency control model 345 and the identification information of at least one push campaign, the processor 110 can determine whether or not to transmit at least one push notification corresponding to at least one push campaign to the user's terminal 200. The specific logic for determining whether or not to transmit at least one push notification to the user's terminal 200 will be specifically explained in Figures 6 to 8.

[0070] Figure 6 is a processing flowchart of an electronic device 100 according to one embodiment of the present disclosure. Specifically, Figure 6 relates to a method for controlling the transmission frequency of push notifications using the effective time period model 351 of the push frequency control model 345.

[0071] Referring to the processing flowchart 600, in step 610, the processor 110 of the electronic device 100 according to one embodiment can check whether the transmission time set for at least one push notification falls within a predetermined valid time range. The predetermined valid time range may be, for example, between 10 a.m. and 8 p.m.

[0072] If the transmission time set for at least one push notification does not fall within a predetermined valid time range, the process branches to step 650 (610 - No), and the processor 110 may decide not to transmit at least one push notification to the user's terminal 200.

[0073] If the transmission time set for at least one push notification falls within a predetermined valid time range, the process branches to stage 620 (610-Yes), and the processor 110 can verify the identification information of at least one push campaign. The processor 110 can then verify the business type information from the identification information of at least one push campaign.

[0074] In one embodiment, the processor 110 can determine in step 630 whether the verified identification information corresponds to a business type to which push frequency control is applied. For example, push frequency control may be applied to a push campaign having a first type related to one-time push notifications or a second type related to regular push notifications. For example, push frequency control may be applied to a push campaign having a third type related to emergency push notifications, a fourth type related to test push notifications, a fifth type related to system push notifications, or a sixth type related to core push notifications.

[0075] The business types to which the aforementioned push frequency control applies are illustrative and not limiting. Whether or not push frequency control applies can be changed by the settings of Operator 305. For example, push frequency control may be applied only to push campaigns that fall under Type 1, or it may be applied only to push campaigns that fall under Type 1 through Type 6.

[0076] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to stage 640 (630-Yes), and the processor 110 can transmit at least one push notification to the user's terminal 200.

[0077] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to stage 650 (630-No), and the processor 110 may decide not to transmit at least one push notification to the user's terminal 200.

[0078] Through this, the electronic device 100 can control that push notifications are transmitted to the user's terminal 200 only within a predetermined valid time range on the user's terminal 200. In other words, the electronic device 100 can control the frequency of transmission of push notifications to the user's terminal 200 based on the identification information of the push campaign and the valid time cycle model 351.

[0079] Figure 7 is a processing flowchart of an electronic device 100 according to one embodiment of the present disclosure. Specifically, Figure 7 relates to a method for controlling the transmission frequency of push notifications using the maximum push control model 353 among the push frequency control models 345.

[0080] Referring to the processing flowchart 700, in step 710, the processor 110 of the electronic device 100 according to one embodiment can confirm the number of push notifications transmitted to the user's terminal 200 during a predetermined period (e.g., one day). For example, the processor 110 can confirm the total number of push notifications transmitted to the user's terminal 200 in one day.

[0081] In one embodiment, the processor 110 can, in step 720, check whether the number confirmed is less than a predetermined critical value. The critical value can mean, for example, the maximum number of push notifications that can be transmitted to a user in one day. The critical value may be, for example, three.

[0082] The critical value may be set by the operator 305, set to a default value, or set based on user information. For example, the processor 110 can check the user's click-through rate for push notifications. The user's click-through rate for push notifications may be stored in the database 140 based on log information related to the push notifications. The critical value may be determined based on the click-through rate. For example, the critical value may be set higher for users with a relatively high click-through rate, and the number of push notifications transmitted per day may be set relatively higher, while the critical value may be set lower for users with a relatively low click-through rate, and the number of push notifications transmitted per day may be set relatively lower.

[0083] If the number of confirmed notifications exceeds the critical value, the process branches to step 760 (720 - no), and the processor 110 may decide not to transmit at least one push notification to the user's terminal 200.

[0084] If the number confirmed is less than the critical value, the process branches to stage 730 (720 - yes), and the processor 110 can confirm the identification information of at least one push campaign. The processor 110 can then confirm the information regarding the business type from the identification information of at least one push campaign.

[0085] In one embodiment, the processor 110 can, in step 740, determine whether the verified identification information corresponds to a business type to which push frequency control is applied. For example, in the case of a push campaign having a first type related to one-time push notifications or a second type related to regular push notifications, push frequency control may be applied. For example, in the case of a push campaign having a third type related to emergency push notifications, a fourth type related to test push notifications, a fifth type related to system push notifications, or a sixth type related to core push notifications, push frequency control may be applied.

[0086] The business types to which the aforementioned push frequency control applies are illustrative and not limiting. Whether or not push frequency control applies can be changed by the settings of Operator 305. For example, push frequency control may be applied only to push campaigns that fall under Type 1, or it may be applied only to push campaigns that fall under Type 1 through Type 6.

[0087] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to step 750 (740-Yes), and the processor 110 can transmit at least one push notification to the user's terminal 200.

[0088] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to step 760 (740 - No), and the processor 110 can decide not to send at least one push notification to the user's terminal 200.

[0089] Through this, the electronic device 100 can control the transmission frequency of push notifications by determining the maximum number of push notifications that can be transmitted to the user's terminal 200 within a predetermined period. In other words, the electronic device 100 can control the transmission frequency of push notifications to the user's terminal 200 based on the identification information of the push campaign and the maximum push control model 353.

[0090] Figure 8 is a processing flowchart of an electronic device 100 according to one embodiment of the present disclosure. Specifically, Figure 8 relates to a method for controlling the transmission frequency of push notifications using a time interval control model 355 among the push frequency control models 345.

[0091] Referring to the processing flowchart 800, in one embodiment, the processor 110 of the electronic device 100 can, in step 810, confirm the transmission time of the push notification most recently transmitted to the user's terminal 200. For example, the processor 110 can confirm the transmission time of the push notification immediately preceding the one transmitted to the user's terminal 200.

[0092] In one embodiment, the processor 110 can, in step 820, check whether a predetermined critical time (e.g., 30 minutes) has elapsed since the confirmed transmission time. Specifically, the processor 110 can check whether the transmission time set for at least one push notification has elapsed since the confirmed transmission time. For example, if the transmission time of a push notification recently transmitted to the user's terminal 200 is 1:10 p.m. and the predetermined critical time is 30 minutes, the processor 110 can check whether the transmission time set for at least one push notification is 1:40 p.m. or later.

[0093] The critical time may be set by the operator 305, set to a default value, or set based on user information. For example, the processor 110 can check the user's click-through rate for push notifications. The user's click-through rate for push notifications may be stored in the database 140 based on log information related to the push notifications. The critical time may be determined based on the click-through rate. For example, for users with a relatively high click-through rate, the critical time may be set shorter to shorten the push notification transmission waiting time, and for users with a relatively low click-through rate, the critical time may be set longer to lengthen the push notification transmission waiting time.

[0094] If a predetermined critical time has elapsed since the confirmed transmission time, the process branches to stage 860 (820 - No), and the processor 110 may decide not to transmit at least one push notification to the user's terminal 200.

[0095] If the number confirmed is less than the critical value, the process branches to stage 830 (820 - yes), and the processor 110 can confirm the identification information of at least one push campaign. The processor 110 can then confirm the information regarding the business type from the identification information of at least one push campaign.

[0096] In one embodiment, the processor 110 can determine in step 840 whether the verified identification information corresponds to a business type to which push frequency control is applied. For example, push frequency control may be applied to a push campaign having a first type related to one-time push notifications or a second type related to regular push notifications. For example, push frequency control may be applied to a push campaign having a third type related to emergency push notifications, a fourth type related to test push notifications, a fifth type related to system push notifications, or a sixth type related to core push notifications.

[0097] The business types to which the aforementioned push frequency control applies are illustrative and not limiting. Whether or not push frequency control applies can be changed by the settings of Operator 305. For example, push frequency control may be applied only to push campaigns that fall under Type 1, or it may be applied only to push campaigns that fall under Type 1 through Type 6.

[0098] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to stage 850 (840-Yes), and the processor 110 can transmit at least one push notification to the user's terminal 200.

[0099] If the verified identification information corresponds to a business type to which push frequency control applies, the process branches to stage 860 (840 - No), and the processor 110 can decide not to send at least one push notification to the user's terminal 200.

[0100] Through this, the electronic device 100 can be configured to transmit only a predetermined number of push notifications to the user's terminal 200 within a predetermined critical time, thereby preventing the transmission of a large number of push notifications in a short period of time. In other words, the electronic device 100 can control the frequency of transmission of push notifications to the user's terminal 200 based on the identification information of the push campaign and the time interval control model 355.

[0101] In another embodiment, the push frequency control model 345 may be activated and deactivated by the user. For example, the user can decide whether or not to activate the push frequency control model 345 via the user's terminal 200. The processor 110 of the electronic device 100 can receive user input from the user's terminal 200 regarding whether or not to activate the push frequency control model 345 and can decide whether or not to activate the push frequency control model 345 based on the user input. The user can deactivate the push frequency control model 345 via the user's terminal 200 if they want to receive push notifications regardless of the current time, the maximum number of push notifications, and the transmission waiting time for push notifications. In one embodiment, the user can set whether or not to activate each of the effective time period model 351, the maximum push control model 353, and the time interval control model 355 included in the push frequency control model 345 via the user's terminal 200.

[0102] In another embodiment, the processor 110 of the electronic device 100 may set different types of push frequency control models 345 to be applied based on the identification information of the push campaign. For example, the processor 110 may be set to apply only the effective time period model 351 to push campaigns corresponding to the first type, to apply only the maximum push control model 353 to push campaigns corresponding to the second type, and to apply only the time interval control model 355 to push campaigns corresponding to the third type.

[0103] On the other hand, while preferred embodiments of the present invention are disclosed in this specification and drawings, and specific terms are used, these are merely general terms used to facilitate the explanation of the technical content of the invention and to aid in its understanding, and are not intended to limit the scope of the invention. It will be obvious to those ordinary skill in the art to which the present invention pertains that other modifications based on the technical idea of ​​the present invention are also possible, in addition to the embodiments disclosed herein.

[0104] The apparatus or terminal according to the above-described embodiment may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with external devices, and user interface devices such as a touch panel, keys, and buttons. A method embodied in a software module or algorithm may be stored on a computer-readable recording medium as computer-readable code or program instructions executable on the processor. Here, computer-readable recording media include magnetic recording media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD (Digital Versatile Disc)). Computer-readable recording media may be distributed across a network of computer systems, and computer-readable code may be stored and executed in a distributed manner. The medium is computer-readable, can be stored in memory, and can be executed by the processor.

[0105] This embodiment may be represented by functional block configurations and diverse processing stages. Such functional blocks may be embodied by a diverse number of hardware and / or software configurations that perform specific functions. For example, the embodiment may employ integrated circuit configurations such as memory, processing, logic, and look-up tables, which can perform diverse functions under the control of one or more microprocessors or other control devices. Just as the components may be executed as software programming or software elements, this embodiment includes diverse algorithms embodied by combinations of data structures, processes, routines, or other programming configurations, and may be embodied in programming or scripting languages ​​such as C, C++, Java, assembler, and Python. Functional aspects may be embodied by algorithms executed by one or more processors. Furthermore, this embodiment may employ prior art for electronic environment configuration, signal processing, and / or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The terms may also include the meaning of a series of software processes (routines) in conjunction with a processor, etc.

[0106] The embodiments described above are merely examples, and other embodiments may be realized within the scope of the claims described later.

Claims

1. A method for providing push notifications in an electronic device, The stage of generating multiple push campaigns related to the application, The step of assigning identification information to each of the aforementioned push campaigns, The step of verifying the information of the user to whom push notifications are provided, Based on the user information, the step of confirming at least one push campaign from the plurality of push campaigns to be transmitted to the user, A method to provide, which includes the step of determining whether or not to transmit at least one push notification corresponding to the at least one push campaign to the user's terminal, based on a push frequency control model and identification information of the at least one push campaign.

2. The aforementioned identification information includes information regarding the type of business, The method of providing according to claim 1, wherein the information relating to the business type includes at least one of the following: a first type relating to one-time push notifications, a second type relating to regular push notifications, a third type relating to emergency push notifications, a fourth type relating to test push notifications, a fifth type relating to system push notifications, or a sixth type relating to core push notifications.

3. The push frequency control model includes an effective time period model. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The steps include: confirming whether the transmission time set for at least one push notification falls within a predetermined valid time range; The method provided according to claim 2, further comprising the step of confirming the identification information of the at least one push campaign if the transmission time set for the at least one push notification falls within the valid time range.

4. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: If the identification information of the at least one push campaign falls under the first type or the second type, the step of transmitting the at least one push notification to the user's terminal, The method provided according to claim 3, further comprising the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third, fourth, fifth, or sixth category.

5. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The method provided according to claim 3, further comprising the step of deciding not to transmit the at least one push notification to the user's terminal if the transmission time set for the at least one push notification does not fall within the valid time range.

6. The push frequency control model includes a maximum push control model. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The steps include: confirming the number of push notifications transmitted to the user's device during a predetermined period; The step involves comparing the number confirmed above with a predetermined critical value, The method provided according to claim 2, further comprising the step of verifying the identification information of at least one push campaign if the number verified is less than the critical value.

7. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: If the identification information of the at least one push campaign falls under the first type or the second type, the step of transmitting the at least one push notification to the user's terminal, The method provided according to claim 6, further comprising the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third, fourth, fifth, or sixth category.

8. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The method provided according to claim 6, further comprising the step of deciding not to transmit at least one push notification to the user's terminal if the number confirmed is greater than or equal to the critical value.

9. The process further includes a step of checking the click-through rate of the user's push notification, The method provided according to claim 6, wherein the critical value is a value determined based on the click rate.

10. The push frequency control model includes a time interval control model. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The steps include: confirming the transmission time of a push notification recently transmitted to the user's device; The step of confirming whether a predetermined critical time has elapsed from the transmission time confirmed above, The method provided according to claim 2, further comprising the step of confirming the identification information of at least one push campaign when a predetermined critical time has elapsed from the confirmed transmission time.

11. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: If the identification information of the at least one push campaign falls under the first type or the second type, the step of transmitting the at least one push notification to the user's terminal, The method provided according to claim 10, further comprising the step of deciding not to transmit the at least one push notification to the user's terminal if the identification information of the at least one push campaign falls under the third, fourth, fifth, or sixth category.

12. The step of deciding whether or not to transmit at least one push notification to the user's terminal is: The method provided according to claim 10, further comprising the step of deciding not to transmit the at least one push notification to the user's terminal if a predetermined critical time has not elapsed since the confirmed transmission time.

13. The process further includes a step of checking the click-through rate of the user's push notification, The method provided according to claim 10, wherein the critical time is a value determined based on the click rate.

14. The steps include receiving user input from the user's terminal regarding whether or not to activate the push frequency control model, The method provided according to claim 2, further comprising the step of determining whether or not to activate the push frequency control model based on the user input.

15. The user information includes at least one of the user's name, gender, age, or address information. The aforementioned identification information includes optional information related to the target to whom the push notification is provided. The step of confirming at least one push campaign is: The method provided according to claim 1, further comprising the step of confirming, based on the user information and the option information, at least one push campaign from the plurality of push campaigns to be transmitted to the user.

16. A computer-readable non-temporary recording medium that stores a program for causing a computer to execute the method according to claim 1.

17. An electronic device, Communication interface, Memory and Includes a processor, The aforementioned processor, Generate multiple push campaigns related to the application, Identification information is assigned to each of the aforementioned push campaigns. Check the information of the users who will be receiving push notifications. Based on the user information, identify at least one push campaign from the plurality of push campaigns to be transmitted to the user. An electronic device configured to determine whether or not to transmit at least one push notification corresponding to the at least one push campaign to the user's terminal, based on a push frequency control model and identification information of the at least one push campaign.

Images