KR20230169772A - Method and apparatus for providing user selected as event target user with event including reward for contents service - Google Patents

Abstract

Among users using the content service, an event target for providing an event is selected based on the users' viewing history of content items and/or the number of content items viewed by each user, and the event target's user terminal is selected. A method of providing an event is disclosed, providing an event push notification or event banner for participation in the event, and providing compensation to event recipients as the event push notification or event banner is selected.

Description

Method and apparatus for providing an event including compensation for content services to users selected as event targets {METHOD AND APPARATUS FOR PROVIDING USER SELECTED AS EVENT TARGET USER WITH EVENT INCLUDING REWARD FOR CONTENTS SERVICE}

This disclosure relates to a method and device for providing an event including compensation for content services to users selected as event recipients, and relates to a method and device for automating the processes of selecting event recipients and providing events to event recipients. do.

In order to use content such as webtoons and/or web novels through a user terminal, it is required to run a content provision service (hereinafter referred to as content service) that provides content such as webtoons and/or web novels on the user terminal. The content service provides requested content items to a user terminal in connection with a platform that manages and provides content (ie, a plurality of content items), and allows a user account associated with the user terminal to use the content items. Content services may be implemented in the form of dedicated applications installed on user terminals.

For users who use the content service, an event including the provision of a small reward is provided to encourage possession or viewing of content items provided through the content service. It is inefficient to provide events related to these content services to all users who use the content service. Additionally, it is very cumbersome for the operator to manually select event subjects that meet the conditions among users and manually reserve a user interface (UI) for event participation to the event subjects.

Therefore, in providing events to users who use the content service, in order to provide efficient events, event recipients can be appropriately selected to encourage users to revisit the content service and pay for the content service. It is required to automate the series of processes of selection and event provision.

Meanwhile, Korean Patent Publication No. 10-2011-0123393 (published on November 15, 2011) discloses a technology for providing comics in the form of mobile digital content through direct online transactions.

The information described above is for illustrative purposes only and may include content that does not form part of the prior art and may not include what the prior art would suggest to a person skilled in the art.

In one embodiment, among users using a content service, an event target for providing an event is selected based on the users' viewing history of content items and/or the number of content items viewed by each user, and the event target is selected. A method of providing an event can be provided to the target's user terminal, providing an event push notification or event banner for participation in the event, and providing compensation to the event target as the event push notification or event banner is selected. there is.

In one aspect, in a method of providing an event related to a content service, performed by a computer system, among users using the content service, the users' viewing of a plurality of content items provided by the content service Based on at least one of the history and the number of content items viewed by each of the users, selecting at least one event subject for providing the event, to a user terminal associated with the event subject, for the event Providing an event push notification or event banner requesting participation and, as the event push notification or event banner is selected in the user terminal, providing available rewards to the event target for viewing or holding the content items. A method for providing an event is provided, including steps.

Each of the content items includes at least one episode that can be viewed by the users, the reward is used for viewing or possession of a paid episode among the episodes by the event target, and the event banner is, When the application providing the content service is executed on the user terminal, it is displayed on the initial screen of the application, and the event push notification is displayed on the user terminal while the application is not running on the user terminal. , the event push notification and the event banner may not be displayed on the user terminals of users who are not selected as event recipients among the users.

The step of providing the reward includes providing an event page including information about the event to the user terminal as the event push notification or event banner is selected in the user terminal, and providing the event page including information about the event on the event page. Depending on the subject's interaction, it may include providing the reward to the event subject, and the event page may include a recommendation area that exposes at least one recommended content item selected from among the content items. .

The recommended content item may include at least one paid episode that the event recipient can view using the reward.

The event includes a first event provided on a one-day cycle in the content service, and the step of selecting the event target includes, based on the time of selection of the event target among the users, the content for a recent certain period of time. At least one user who does not have a viewing history for the items but has a viewing history for the content items on a date before the predetermined period of time may be selected as the event target for the first event.

The step of selecting the event target includes selecting a user whose number of viewed content items is within a predetermined range among at least one user who has a viewing history for the content items on a date before the predetermined period of time to the first event. You can be selected as a target for the above events.

The step of selecting the event target includes, among the users, based on the time of selection of the event target, if there is no viewing history for the content items during a recent first period and the content items are selected on a date before the first period. A first event target set including users who have a viewing history for items and the number of viewed content items falls within a predetermined first range, and, based on the time of selection of the event target among the users, the first event target set, A second event subject including a user who has a viewing history for the content items on a date before the second period but does not have a viewing history for the content items during a recent second period that is longer than 1 period A user included in the union of the sets may be selected as the event target for the first event.

The event further includes other events provided by the content service in a cycle different from the first event, and in the step of selecting the event target, the event target is an event target for the first event and the other event. When selected, the step of providing the event push notification or event banner includes providing the user terminal with an event push notification or event banner requesting participation in the first event, and providing the user terminal with an event push notification or event banner for the other event. Event push notifications or event banners requesting participation may not be provided.

The event includes a second event provided on a weekly basis in the content service, and the step of selecting the event target includes selecting the content item for the most recent week based on the time of selection of the event target among the users. At least one user who has a viewing history for the content items but does not have a viewing history for the content items during the recent third period may be selected as the event target for the second event.

The step of selecting the event target may include: Among the at least one user who has no viewing history for the content items during the recent third period, there is a viewing history for the content items on only one day out of a recent week; The method may include excluding a user who has viewed one content item from being an event target for the second event.

The event includes a third event provided on a one-month cycle in the content service, and the step of selecting the event target includes, among the users, based on the time of selection of the event target, the content item in the past month. At least one user who has a viewing history for the content items but does not have a viewing history for the content items this month may be selected as the event target for the third event.

The event includes a fourth event provided at a fourth period in the content service, and the step of selecting the event target includes the users' viewing history for the content items, the content items viewed by each user, Based on the number of and each user's payment history for the content items, at least one user among the users may be selected as the event target for the fourth event.

The step of selecting the event target includes, among the users, based on the time of selection of the event target, if there is a viewing history for the content items during the recent fifth period and there is a viewing history for the content items during the fifth period. At least one user without payment history may be selected as the event target for the fourth event.

The step of selecting the event target is a period shorter than the fifth period, based on the time of selection of the event target among the at least one user who has no payment history for the content items during the fifth period. A user whose number of content items viewed during the most recent sixth period falls within a predetermined second range may be selected as the event target for the fourth event.

The event push notification may be provided to the user terminal and displayed on the user terminal, regardless of the push limit setting indicating the number of push notifications that can be provided to the event target preset for the event target.

The event banner is a personalized event banner that is exposed only on user terminals associated with the event target and is not exposed on user terminals of users who are not selected as the event target among the users, and may include identification information of the event target. there is.

In another aspect, a computer system that provides an event related to a content service, comprising at least one processor implemented to execute instructions readable by the computer system, wherein the at least one processor provides the content service. Among the users, based on at least one of the viewing history of the users for a plurality of content items provided by the content service and the number of content items viewed by each of the users, at least one for providing the event Selecting an event target, providing an event push notification or event banner requesting participation in the event to a user terminal associated with the event target, and as the event push notification or event banner is selected on the user terminal , a computer system is provided that provides rewards available to the event recipients for viewing or owning the content items.

In providing events to users who use content services, the process of selecting event subjects that meet the conditions, the process of reserving event push notifications and event banners for event subjects to participate in the event, and the process of providing rewards according to the event The process of configuring event pages for provision can be automated. Accordingly, computing and human resources used in providing content services can be reduced.

Appropriate event recipients can be automatically selected based on conditions that encourage users to revisit the content service and make paid payments. In other words, based on the users' viewing history of content items, the number of content items viewed by each user, and the payment history for content items, paid payment for the content service or users who will encourage return to the content service Users to be induced can be automatically selected.

1 illustrates an example of automatically selecting an event target for providing an event related to a content service and providing an event push notification or event banner related to the event to the selected event target, thereby providing information to the event target. Indicates a method of providing personalized events.
Figure 2 shows a computer system corresponding to a user terminal and a server that provides an event to an event target, according to an embodiment.
Figure 3 is a flowchart showing a method of automatically selecting event recipients for providing an event related to a content service and providing a personalized event to the event recipient, according to an embodiment.
Figure 4 illustrates a method of selecting event recipients according to the type of event and conditions for selecting event recipients associated with each event, according to an example.
Figure 5 shows a method of selecting event recipients to provide a first event (daily breakaway care event), according to an example.
Figure 6 shows a method of selecting event recipients to provide a second event (weekly escape care event), according to an example.
Figure 7 shows a method of selecting event recipients to provide a third event (monthly breakaway care event) according to an example.
Figure 8 shows a method of selecting event recipients to provide a fourth event (purchase conversion inducing event) according to an example.
Figure 9 shows an event banner provided to event recipients, according to an example.
Figure 10 shows an event push notification provided to an event recipient, according to an example.
11 and 12 show an event page provided to an event recipient according to selection of an event banner or event push notification, according to an example.
Figure 13 shows an event banner provided to event recipients in connection with a fourth event (purchase conversion inducing event), according to an example.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

The content service may be a service that provides requested content items to the user terminal 50 according to a request from the user terminal 50 . The content service may provide requested content items to the user terminal 50 in connection with a platform that manages and provides content, and may enable the user account associated with the user terminal 50 to use the content items. . The user account associated with the user terminal 50 may be an account (ID) of a user registered or subscribed to this content service. In the detailed description to be given later, “user” may be used to mean “user account” for convenience of explanation. Similarly, “event subject” may be used to mean “event subject’s account” for convenience of explanation.

Content services may be provided to the user terminal 50 (user) through the computer system 100, which is the server shown, and the computer system 100 includes a content platform that manages and provides content, or includes such a content platform and Can be configured to communicate.

“Content” provided through content services is digital goods and may include multimedia content and text content. For example, content or service may include video content, movie content, music content, webtoon content, broadcast program content, book content (web novel content), etc. A “content item” may represent individual content. For example, a “content item” may represent a webtoon or web novel containing at least one episode. Or, depending on the embodiment, the “content item” may represent only one episode of a webtoon or web novel.

Content items may be provided to a user through purchase by the user in a content service. “Purchase” of a content item may include rental for viewing, purchase (for permanent collection), and downloading of the content item.

Content services may be provided to the user terminal 50 through a dedicated application installed on the user terminal 50. This dedicated application may be an application installed on the user's user terminal 50 to provide content items to the user account through a content platform that includes a DB that stores content items or communicates with the DB. For example, such a dedicated application may be an application that provides webtoons or web novels. As described above, the content platform may be implemented by the computer system 100 shown. Computer system 100 may include at least one server.

1 illustrates an example of automatically selecting an event target for providing an event related to a content service and providing an event push notification or event banner related to the event to the selected event target, thereby providing information to the event target. Indicates a method of providing personalized events.

In the illustrated embodiment, the computer system 100 selects an event subject to provide an event related to a content service (①), and sends an event push notification associated with the event to the user terminal 50 of the selected event subject ( 30) Alternatively, an event banner (20) can be provided (②-1, ②-2).

The event push notification or event banner provided to the user terminal 50 may be exposed on the user terminal 50, and as selected by the user terminal 50, the event recipient may obtain compensation according to the event. As the event push notification or event banner is selected by the user terminal 50, the computer system 100 may provide the user terminal 50 with an event page containing information about the event, and the event target may be selected through the user terminal. Rewards can be obtained through interaction with the event page exposed at (50).

In an embodiment, the computer system 100 provides an event to users using a content service, including a process of selecting an event target that meets the conditions, an event push notification 30 for event participation, and The process of reserving the event banner 20 and configuring the event page for providing rewards according to the event can be automated.

Therefore, in the embodiment, the operator of the content service manually selects an event subject that meets the conditions among users and manually reserves a push notification 30 and an event banner 20 for event participation to the event subject. Without work, the computer system 100 may automatically select an event target among users and provide a push notification 30 or an event banner 20 to the event target.

First, the computer system 100 may select at least one event subject who is required to participate in the event from among users using the content service (①). Event recipients may be selected as users who meet certain conditions related to the event among users who use the content service. The method by which the computer system 100 selects event recipients from among users will be described in more detail with reference to FIGS. 3 to 8 , which will be described later.

The computer system 100 may provide an event banner 20 requesting participation in the event to the selected event target (②-1). Alternatively, the computer system 100 may provide an event push notification 30 requesting participation in the event to the selected event target (②-2).

As shown, the event banner 20 is a banner exposed at the top of the screen of the user terminal 50 and may be an 'app top banner'.

For example, when an application providing a content service is executed on the user terminal 40, the event banner 20 may be exposed on the application's initial screen or the application's home screen. The home screen may be a screen that is first or default displayed in the content service while the user is logged in to the content service.

As shown, the event banner 20 may include a button for landing the event page (eg, a “receive cookie gift” button). The user terminal 50 can land an event page when the corresponding button is selected.

As shown, the event push notification 30 may be a “push notification” displayed on the screen of the user terminal 50. The event push notification 30 may be exposed at the top or bottom of the screen of the user terminal 50. The event push notification 30 disappears after being exposed for a certain period of time on the screen of the user terminal 50, and the disappeared event push notification 30 can be viewed through the notification area of the user terminal 50.

The user terminal 50 may land an event page when the event push notification 30 exposed on the screen is selected or the event push notification 30 is selected through the notification area.

Meanwhile, the event push notification 30 may be exposed on the user terminal 50 even when an application providing a content service is not running on the user terminal 50. In other words, it may be displayed on the screen of the user terminal 50 at a certain point in time regardless of whether the application providing the content service is executed on the user terminal 50. As shown, the event push notification 30 may be displayed in the form of a pop-up on the home screen of the user terminal 50.

The illustrated event push notification 30 and event banner 20 may not be displayed on the user terminals of users who use the content service but are not selected as event recipients. In other words, the event push notification 30 and the event banner 20 are exposed only to the event target's user terminal 50 and may be personalized to the event target. Accordingly, event recipients can receive personalized events through the event push notification 30 and event banner 20.

The event push notification 30, event banner 20, and event page will be described in more detail with reference to FIGS. 9 to 13, which will be described later.

As described above, each content item of the plurality of content items provided by the content service may include at least one episode that users can view. A content item may include at least one paid session and/or at least one free session. Free episodes may be episodes that users can view for free, and paid episodes may be episodes that require payment from users to view. Paid episodes viewed through payment can be viewed free of charge for a certain period of time, for example, 3 days. Meanwhile, users can also keep paid episodes by paying for free episodes or paid episodes. For example, a user may retain a paid episode by paying for a larger amount of cash or currency than required for viewing. The collected episodes may be made available for viewing without any time limit. 'Viewable without time limit' means that the user can download or view the episode from the time the user purchases the episode for collection until the contract between the user and the content service ends. it means.

In an embodiment, an event may refer to a promotion of a content service that provides rewards to users who use the content service.

In an embodiment, the reward provided to the event subject according to the event may be cash used for viewing paid episodes of the content item by the event subject. Alternatively, this reward may be a cache used for retention of multiple rounds of content items by event recipients. Cash provided as a reward may directly represent the value of the corresponding real currency, or may have a unit of currency used only in the content service. For example, cash provided as a reward may be named 'cookie'.

Rewards provided according to an event may include the value of allowing event recipients to view one paid episode of a content item. For example, if two cookies are required to view one paid episode in the content system, the reward provided according to the event may be two cookies.

Meanwhile, an event may have a predetermined expiration date set, and this expiration date may be displayed on the event push notification 30 or the event banner 20. Additionally, rewards obtained according to events may also have an expiration date. For example, depending on the event, cookies acquired by event recipients may disappear if they are not used within 3 days.

A more specific method by which the computer system 100 selects event recipients and provides personalized events to the selected event recipients will be described in more detail with reference to FIGS. 2 to 13 to be described later.

Figure 2 shows a computer system corresponding to a user terminal and a server that provides an event to an event target, according to an embodiment.

The computer system 100 may be a server that provides the above-described content service. In other words, the computer system 100 provides the requested content item to the user terminal 50 associated with the user according to a request from the user, and if the user is an event target, a push notification 30 or an event is sent to the user terminal 50. The banner 20 is displayed, and according to the selection of the push notification 30 or the event banner 20 by the event target, an event page containing information about the event is provided to the user terminal 50, and the event It may be a device that provides compensation to event recipients.

Computer system 100 may be configured to include at least one computing device, and such computing device may be implemented as at least one server.

As shown, the computer system 100 may include a memory 130, a processor 120, a communication unit 110, and an input/output interface 140.

The memory 130 is a computer-readable recording medium and may include a non-permanent mass storage device such as random access memory (RAM), read only memory (ROM), and a disk drive. Here, the ROM and the non-perishable mass recording device may be separated from the memory 130 and included as a separate permanent storage device. Additionally, an operating system and at least one program code may be stored in the memory 130. These software components may be loaded from a computer-readable recording medium separate from the memory 130. Such separate computer-readable recording media may include computer-readable recording media such as floppy drives, disks, tapes, DVD/CD-ROM drives, and memory cards. In another embodiment, software components may be loaded into the memory 130 through the communication unit 110 rather than a computer-readable recording medium.

The processor 120 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations. Commands may be provided to the processor 120 by the memory 130 or the communication unit 110. For example, the processor 120 may be configured to execute instructions received according to program code loaded into the memory 130.

The communication unit 110 may be a component that allows the computer system 100 to communicate with other devices (such as user terminals or other servers). That is, the communication unit 110 is a hardware module or network, such as an antenna, a data bus, a network interface card, a network interface chip, and a networking interface port, of the computer system 100 that transmits/receives data and/or information to and from other devices. It may be a software module such as a device driver or networking program.

The input/output interface 140 may be a means for interfacing with an input device such as a keyboard or mouse and an output device such as a display or speaker.

The processor 120 can manage the components of the computer system 100, execute a program or application for providing the above-described content service, and perform operations necessary for executing the program or application and processing data. can be processed. The processor 120 may be at least one processor (CPU and/or GPU, etc.) of the computer system 100 or at least one core within the processor.

Additionally, in embodiments, computer system 100 and processor 120 may include more components than those shown.

The user terminal 50 is a terminal possessed and used by the user, which executes the content service provided by the computer system 100, or has a dedicated application for the content service installed and executes the content service through the dedicated application. It may be an electronic device. For convenience of explanation, the dedicated application may be referred to as an application in the detailed description that will be described later. The user terminal 50 may be implemented as a computer system. The user terminal 50 may transmit a request for a content item (e.g., a purchase request or a viewing request) to the computer system 100 through a user account registered for the content service, and is configured to output the requested content item. It can be.

The user terminal 50 can display a home screen when a content service is executed, and as a content item exposed in one area of the home screen is selected, detailed information about the content item can be output (displayed). In addition, the user terminal 50 may display a push notification 30 or an event banner 20, and as the push notification 30 or the event banner 20 is selected, an event page containing information about the event You can land.

The user terminal 50 is a computing device and may include, for example, a PC, a laptop, a smart phone, a tablet, an Internet of Things device, or a wearable computer.

As shown, the user terminal 50 may include a memory 135, a processor 125, a communication unit 115, and an input/output interface 145. Regarding the memory 135, processor 125, communication unit 115, and input/output interface 145, the memory 130, processor 120, communication unit 110, and input/output interface 140 of the computer system 100 are described above. Since the explanation for can be applied similarly, overlapping explanations will be omitted.

Processor 125 may manage the components of user terminal 50, execute the content services described above, forward requests for content items to computer system 100, and output the requested content or service. It can be configured. Additionally, the processor 125 can execute the above-described dedicated application (or program) and process operations necessary for executing the dedicated application and processing data. The processor 125 may be at least one processor (CPU and/or GPU, etc.) of the user terminal 50 or at least one core within the processor.

The user terminal 50 may also be referred to as the computer system 100, but for convenience of explanation, the user terminal 50 and the computer system 100 will be described separately in the detailed description below.

Depending on the operation of the user terminal 50 and the computer system 100, a push notification 30 or an event banner 20 is displayed on the screen of the user terminal 50, and rewards according to the event are provided to the event recipients. A more specific method of providing a personalized event will be described in more detail with reference to FIGS. 3 to 13, which will be described later.

The description of the technical features described above with reference to FIG. 1 can also be applied to FIG. 2 , so overlapping descriptions will be omitted.

In the detailed description to be described later, operations performed by the components of the computer system 100 or the processor 120 or the user terminal 50 or the processor 125 are referred to as the computer system 100 or the user for convenience of explanation. It can be described as an operation performed by the terminal 50.

Figure 3 is a flowchart showing a method of automatically selecting event recipients for providing an event related to a content service and providing a personalized event to the event recipient, according to an embodiment.

In an embodiment, a personalized event may be provided to a user selected as an event target among users using a content service. In other words, among users who use the content service, an event may be provided in a customized manner only to event recipients selected as users who will induce a return to the content service or users who will induce paid payment for the content service.

In step 310, the computer system 100 selects among users using the content service, among the users' viewing history for a plurality of content items provided by the content service and the number of content items viewed by each user. Based on at least one, at least one event target for providing an event may be selected.

The event in the embodiment may be a CRM (customer relationship management)-related event for managing users who have not been active in the content service for a certain period of time, that is, have not viewed content items, and have dropped out of the content service. This event may select the abandoned user as the event target and provide compensation available in the content service to encourage the event target to return to the content service. Alternatively, the event selects users who have recently been active in the content service but have not made a paid payment (i.e., users who only use the content service for free) as event recipients, and provides rewards to the event recipients to encourage paid payments. It may be.

These events may be provided periodically by the content service, and according to the cycle, the computer system 100 may select event recipients from among users who use the content service.

The computer system 100 may select event recipients based on the users' viewing history of a plurality of content items and/or the number of content items viewed by each user using the content service. The viewing history may mean whether each user has viewed a content item. The number of content items viewed may represent the number of content items viewed by each user during a certain period of time (e.g., the most recent N days (N is a natural number) for which a viewing history exists) or the entire period of using the content service. In other words, the number of content items viewed may represent the number of works viewed by each user, rather than the number of times the work was viewed during a certain period or the entire period.

Additionally, when selecting event recipients, the computer system 100 may further consider payment history for content items during a certain period of time or the entire period of use of the content service by each user. Payment history may indicate whether each user has a history of making payments for a certain period or the entire period. Payments include paid payments, such as purchases of Cash or purchases of content items, where each user pays real currency, and purchases of content items, where each user uses rewards earned according to an event (i.e., free payments). can do.

The method by which the computer system 100 selects event subjects among users in consideration of conditions according to the type of event will be described in more detail with reference to FIGS. 4 to 8 , which will be described later.

In step 320, the computer system 100 may provide an event push notification 30 or an event banner 20 requesting participation in the event to the user terminal 50 associated with the event subject. The computer system 100 may encourage event recipients to participate in the event by providing an event push notification 30 or an event banner 20 to the user terminal 50 of the event recipient.

The event banner 20 may be exposed on the user terminal 50 when an application providing a content provision service is executed, and may be a banner at the top of the app that is exposed at the top of the screen of the user terminal 50.

In relation to this, Figure 9 shows an event banner provided to an event target, according to an example.

The event banner 20 shown in FIG. 9 may be a banner at the top of an app. The event banner 20 may include a button for landing the event page (eg, a “receive cookie gift” button). The user terminal 50 can land an event page when the corresponding button is selected. Alternatively, when an arbitrary area within the event banner 20 is selected, the user terminal 50 may land when the corresponding button is selected. Unlike what is shown, the event banner 20 is information about the event and may further include information about the expiration date of the event and/or information about the expiration date of the reward that can be obtained according to the event.

The event banner 20 may be configured to be exposed to the user terminal 50 only within the validity period of the event. At this time, the event banner 20 may be configured to be exposed at a specific time period. For example, the event banner 20 is displayed in the first time range (D-0 19:00 ~ D+2 00:00) on weekdays and in the second time range (D-0 11:30 ~ D+2 00: 00) may be configured (i.e., reserved) to be exposed on the user terminal 50. Here, D-0 may be the event start date and D+2 may be the event end date.

The event banner 20 may be a personalized event banner that is exposed only on the user terminal 50 associated with the event target and is not exposed on the user terminals of users who are not selected as the event target among users, and may contain identification information of the event target. It can be included. For example, the event banner 20 may include the name, ID, or nickname of the event subject. The event banner 20 may be configured to expose the name, ID, or nickname of the event subject on the event banner 20. For example, “you” in the event banner 20 of FIG. 9 may be replaced with “OO” corresponding to the name, ID, or nickname of the event subject.

The event banner 20 of the embodiment may be given higher priority than other promotional banners. In other words, the event banner 20 may be set to be displayed on the event target's user terminal 50 with greater priority than other promotional banners. For example, when a plurality of banners are provided in a switchable manner, the event banner 20 may be exposed first and may be exposed at the top of the screen compared to other banners.

For example, up to 20 banners can be displayed as the top banner of the app. When an application providing a content service is executed on the user terminal 50, from the first banner to the 20th banner may be sequentially displayed on the home screen. One banner may be exposed for a predetermined time (n seconds, n is a natural number), and after exposure, it may be configured to switch to the next banner and expose the next banner.

Banners may have priorities depending on the type to which they belong. For example, banners can be divided into four types, and banners with high priority can be exposed first. The types of banners are, for example, "Special type (1st ranked exposure banner type)", "New type (2nd ranked exposed banner type)", "Complete type (3rd ranked exposed banner type)", "Other type (4th ranked exposed banner type)" type)", etc. The order of exposure of banners may be determined according to the priority according to the type of banner. This can be the first standard for determining the banner exposure order.

Alternatively, as a second criterion for determining the order of banner exposure, the priority of banner exposure according to the 'target setting method' may be applied. For each banner type described above, the maximum number of slots may be set as the number of banners that can be assigned.

If the number of banners exceeding the maximum number of slots is registered for each banner type, the priority considering the 'target setting method' of each banner may be considered to determine the banner to be finally registered for that banner type. . That is, the second standard may be a standard for determining banners to be included in each banner type or determining the priority of exposure among banners belonging to the same banner type.

At this time, the narrower the scope of the target audience (for example, the aforementioned event target audience) for each banner, the higher the priority according to the second criterion may be. In other words, the narrower the range of people targeted by a banner, the more likely it is that the banner can be viewed as a banner targeted to event people in more detail, thereby increasing the likelihood of exposure. For example, the following priorities may be applied: 'Banner targeting people with an "interest" in a specific content or genre > Banner targeting people of a specific gender > Banner targeting all users'.

For example, in the case where the maximum number of slots in the 'Special Type' is 2, if more than 2 banners are registered in the 'Special Type', 2 according to the second standard according to the above-mentioned "Target Setting Method" Only banners can be determined as 'special type' banners to be exposed.

In exposing the banner 30 associated with the first to fourth events to be described later, the banner 30 may be exposed according to the priority of banner exposure according to the first criterion described above, and also targeting for each event Considering the 'target setting method' of the event target, the banner 30 may be exposed according to the priority of banner exposure according to the second standard described above. Determination of the priority of exposure of the banner may be performed by the computer system 100.

The event push notification 30 may be a push notification that can be displayed on the user terminal 50 even when an application providing a content service is not running on the user terminal 50, and may be displayed on the home screen of the user terminal 50. It may be exposed in the form of a pop-up.

In relation to this, Figure 10 shows an event push notification provided to an event recipient, according to an example.

As shown, the event push notification 30 may be a “push notification” displayed on the screen of the user terminal 50. The event push notification 30 may be exposed at the top or bottom of the screen of the user terminal 50. The event push notification 30 disappears after being exposed for a certain period of time on the screen of the user terminal 50, and the disappeared event push notification 30 can be viewed through the notification area of the user terminal 50. The event push notification 30 is information about an event and may further include information about the expiration date of the event and/or information about the expiration date of a reward that can be obtained according to the event. Information about the expiration date of the event included in the event push notification 30 may be output with the date changed according to the expiration date of the event.

The event push notification 30 may be a personalized event push notification that is exposed only on the user terminal 50 associated with the event target and is not exposed on the user terminals of users who are not selected as the event target among users, and identifies the event target. May contain information. For example, the event push notification 30 may include the name, ID, or nickname of the event recipient. The event push notification 30 may be configured to expose the name, ID, or nickname of the event recipient in the event push notification 30. For example, the event push notification 30 of FIG. 9 may display text such as “A cookie gift has arrived for OO” that corresponds to the name, ID, or nickname of the event recipient.

Meanwhile, the event push notification 30 may be provided to the user terminal 50 and exposed on the user terminal 50, regardless of the push limit settings preset for the event target. The push limit setting may be a preset value indicating the number of push notifications that can be provided to event recipients. For example, the push limit setting may be a push cap. These “push limit settings” are set in the content service and may be unrelated to the settings in the user terminal 50. In other words, “push limit settings” may cause the user to feel uncomfortable if too many push notifications are sent to the user terminal 50, and there is a risk that the notification setting itself will be turned off on the user terminal 50. In (50), this may be logic added to the content service to prevent certain types of push notifications (e.g., recommendations, event notifications, etc.) from being sent in excess of a certain number so as not to turn off the notification setting itself.

For example, even if it is set that more than a predetermined number of push notifications cannot be sent to the event target per day in relation to the content service according to these push limit settings, the event push notification 30 of the embodiment is sent to the event target. It may be provided and exposed to the user terminal 50. Or/Additionally, even if push notifications are set not to be transmitted for a certain period of time in relation to the content service, the event push notification 30 of the embodiment may be provided and exposed to the user terminal 50 of the event target. . Accordingly, the likelihood that the event target will check the event push notification 30 increases, and thus, the event target's participation in the event may be encouraged.

In other words, the event push notification 30 may be a push notification that is an exception to the push cap preset for the event target.

However, the event push notification 30 may be configured to be exposed to the user terminal 50 at a set time or time. For example, the event push notification 30 may be configured (i.e., scheduled) to be displayed on the user terminal 50 at a first time (19:00) on weekdays and at a second time (11:30) on weekends.

In step 325, the computer system 100 provides the event recipient with available rewards for viewing or possessing content items as the event push notification 30 or event banner 20 is selected on the user terminal 50. can be provided.

In step 330, the computer system 100 provides a reward to the event recipient, and as the event push notification 30 or event banner 20 is selected in the user terminal 50, the user terminal 50 An event page containing information about the event can be provided.

In step 340, the computer system 100 may provide a reward according to the event to the event subject according to the event subject's interaction with the event page.

The event subject's interaction may be the selection of a predetermined area or button on the event page, or the viewing of a content item exposed in connection with the event page, for example, a recommended content item. Subject to the event subject's interaction, the event subject can obtain rewards according to the event.

Depending on the event, the reward provided to the event target may be cash used for viewing or retaining paid episodes of the content item by the event target. Rewards provided according to an event may include the value of allowing event recipients to view one paid episode of a content item.

According to the provision of such compensation, event recipients who have left the content service can return to the content service by viewing paid episodes of the content item for free. Alternatively, according to the provision of compensation, event recipients who are users selected as needing to be encouraged to pay for content services are encouraged to view the paid episode of the content item for free and then view the next paid episode through paid payment. It can be.

In this way, the compensation provided to the event target can be an incentive to return to the content service or induce paid payment, and by having this predetermined expiration date (e.g., 3 days), quick use of the reward by the event target is possible. can be encouraged.

In relation to this, FIGS. 11 and 12 show an event page provided to an event recipient according to selection of an event banner or event push notification, according to an example.

The event page 1100 may be a page of an application that provides a content service that is exposed to the user terminal 100 when the above-described event banner 20 or event push notification 30 is selected.

The identifier of the event banner 20 (or the identifier of the event push notification 30) may be mapped to the event page 1100. Accordingly, the event subject who is provided with the event page 1100 and the event subject who is provided with the identifier of the event banner 20 (or the identifier of the event push notification 30) may be linked to each other.

The event page 1100 includes a first area 1110 including an interaction area 1115 for obtaining rewards, a second area 1120 providing information about the event, and at least one recommended content related to the event. It may be configured to include a third area 1130 containing items. The third area 1130 is a recommendation area and may be configured to expose at least one recommended content item selected from among content items provided by a content service.

The first area 1110 may be an image area for compensation payment.

For example, the interaction area 1115 may be a button (receiving a cookie gift button) as shown, and when the interaction area 1115 is selected, a reward according to the event may be provided to the event recipient. When the interaction area 1115 is selected, as shown in FIG. 12, a message 1210 notifying that compensation has been paid to the event recipient may be output. Rewards can only be provided to event recipients once during the event's validity period. If the event recipient has already been provided with a reward, the message 1210 may not be output even if the interaction area 1115 is selected, and instead, another message indicating that the reward has already been paid may be output.

The second area 1120 may include information about events. For example, the second area 1120 may include information about the event, such as the expiration date of the event, the expiration date of the reward according to the event, and other precautions related to obtaining the reward.

Recommended content items exposed in the third area 1130 may include at least one paid episode. That is, the recommended content item displayed in the third area 1130 may include at least one paid episode that can be viewed using rewards obtained by the event target. At this time, content items that include only free episodes may not be selected as recommended content items displayed in the third area 1130. Accordingly, if the event target is a user selected as needing to be induced to pay for a content service, the event target may be encouraged to view the paid episode of the recommended content item for free using the reward immediately obtained.

The third area 1130 may be provided at the bottom of the first area 1110 so that event recipients can search for recommended content items without leaving the event page 1100 after obtaining the reward.

Recommended content items may be selected based on the ranking of content items provided by the content service. The computer system 100 may expose a predetermined number of recommended content items in the third area 1130. The predetermined number of recommended content items includes at least one content item selected based on the ranking of the content item according to gender (male or female), and at least one content item selected based on the daily ranking, weekly ranking, monthly ranking, or rising ranking. Can contain one content item. Only one overlapping content item may be exposed in the third area 1130.

For example, when 10 recommended content items are exposed in the third area 1130, content items corresponding to the TOP 3 of the weekly new work ranking (female), content items corresponding to the TOP 3 of the weekly new work ranking (male), Content items ranked in the TOP 4 in the weekly rapid ranking (overall) can form 10 recommended content items.

When less than a predetermined number of recommended content items are selected, the computer system 100 may randomly select the insufficient number of recommended content items. For example, an insufficient number of recommended content items may be randomly selected from among the TOP 10 content items in the weekly new release ranking (total).

Below, how recommended content items to be exposed in the third area 1130 are determined will be described in more detail.

1) Recommended content items can be sorted in order of high content ranking. For example, i) recommended content items will be displayed in the following order: 1st place content item in female ranking, 2nd place content item, 3rd place content item, 1st place male ranking content item, 2nd place content item, 3rd place content item, etc. can be, or, ii) the female ranking 1st content item, the male ranking 1st content item, the female ranking 2nd content item, the male ranking 2nd content item, the female ranking 3rd content item, the male ranking 3rd content item, . Recommended content items may be exposed in the order of ..

2) When selecting the above-described insufficient number of recommended items, content items with a higher ranking may be preferentially selected as recommended content items rather than in a random manner.

3) Alternatively, to prevent the above-described insufficient number of recommended items from occurring, recommended content items may be selected by additionally considering “supplemental ranking.” When there is an insufficient number of recommended content items, the number of recommended content items selected by additionally selecting the “supplemental ranking” may always be a certain number. “Supplementary ranking” is a secondary consideration in the selection of recommended content items and may indicate the ranking of all content items.

When a recommended content item exposed in the third area 1130 is selected, a detailed page for the recommended content item may be displayed on the user terminal 50. The detail page may include episodes of the selected recommended content item, and may be configured to allow the selected episode to be viewed.

The event page 1100 may be a personalized event page that is exposed only on the user terminal 50 associated with the event target and is not exposed on the user terminals of users who are not selected as the event target among users, and may contain identification information of the event target. It can be included. For example, the event page 1100 may include the name, ID, or nickname of the event subject.

The event page 1100 may be configured to expose the name, ID, or nickname of the event subject on the event banner 20. “You” in the first area 1110 may be replaced with “OO” corresponding to the name, ID, or nickname of the event subject.

Additionally, recommended content items exposed in the third area 1130 may be personalized to the event target. For example, recommended content items may consist of content items preferred or set as preferred by the event subject.

In this way, by constructing the event page 1100 personalized for the event target, the event can be personalized for the event target.

In an embodiment, the computer system 100 may automatically select an event target every event provision cycle according to preset conditions for selecting an event target, and display an event banner 20 and/or an event target for the event target. The push notification 30 can be automatically scheduled, and the event page 1100 can be configured and provided automatically according to the selection of the event banner 20 or the event push notification 30.

The description of the technical features described above with reference to FIGS. 1 and 2 can also be applied to FIGS. 3 and 9 to 12 , so overlapping descriptions will be omitted.

Figure 4 illustrates a method of selecting event recipients according to the type of event and conditions for selecting event recipients associated with each event, according to an example.

Referring to FIG. 4, various types of events and a method of selecting an event target among users using a content service according to event target selection conditions associated with each event will be described in more detail.

The event of the embodiment may be to periodically select event subjects and provide event banners 20 or event push notifications 30 to the event subjects.

First, a case where the event includes a daily breakaway care event will be described.

For example, such an event may include a first event provided on a daily cycle in a content service. When selecting an event subject in step 310, the computer system 100 may select an event subject for the first event (step 410).

The first event is an event that occurs (or is provided) every day and may be a daily breakaway care event. That is, according to the first event, the computer system 100 selects the user who leaves the content service every day as the event target and presents the event banner 20 or You can reserve and provide event push notifications (30).

Specifically, the computer system 100, among users who use the content service, based on the time of selection of the event target, has no history of viewing content items for a recent certain period of time and has no history of viewing content items on days before the certain period. At least one user who has a viewing history for the first event may be selected as the event target for the first event. In other words, the computer system 100 considers users who have a viewing history for content items N (N is a natural number) days ago, but have no viewing history for content items during the recent N-1 days as abandoned users. You can be selected as an event target.

At this time, when selecting an event subject for the first event, the computer system 100 has no viewing history for content items during a recent certain period of time and has no viewing history for content items on days before the certain period of time. Among the at least one existing user, a user whose number of viewed content items falls within a predetermined range may be selected as an event target for the first event. The range may be a range without an upper limit or a range with an upper limit. For example, the computer system 100 may select a user whose number of viewed content items is less than or equal to a predetermined value among the at least one user as an event target for the first event.

The “number of content items viewed” used to select event recipients may be the number of content items viewed by each user during a specific period. At this time, the specific period may be the entire period during which each user used the content service or the most recent N days (N is a natural number) for which each user has a viewing history. Additionally, the specific period may be the most recent week or month. That is, the “number of content items viewed” for each user can be calculated on a weekly or monthly basis. Additionally, the specific period may be the same as the period used to check the viewing history of each user.

In this way, the computer system 100 is configured to exclude users who are considered to be the above-mentioned dropout users who are likely to organically return to the content service without providing compensation according to the event from selection as event subjects, 'each user'. The number of content items viewed by users can be used to select event recipients. Users who leave after the number of viewed content items exceeds a predetermined value are expected to return to the content service even if compensation for the event is not provided, so they may not be selected as event recipients for the first event.

For example, the computer system 100 may, among users who use the content service, have no viewing history for content items during the most recent first period, based on the time of selection of the event subject, on a date before the first period. a first event target set including users who have a viewing history for content items and where the number of content items viewed falls within a predetermined first range; Among users who use the content service, based on the time of selection of the event target, there is no history of viewing content items during the most recent second period, which is longer than the first period, and content items are displayed on days before the second period. A user included in the union of the second event target set including users with a viewing history for the first event may be selected as the event target for the first event.

In relation to this, Figure 5 illustrates a method of selecting event recipients for providing a first event (daily breakaway care event) according to an example.

5 to 8 show the viewing history of each user's content items. If there is a viewing history for each user on the corresponding date, O is displayed, and if there is no viewing history, X is displayed.

As shown in Figure 5, in the case where D-0 is the event start date (or the time of selection of the event subject), the computer system 100: 1) There is no viewing history in D-6 to D-1 and 7 A set of users who have a viewing history a few days ago and the number of content items viewed is 1 to 8; 2) In D-10 to D-1, there is a set of users who have no viewing history but have a viewing history 11 days ago and the number of viewed content items is 1 to 8; 3) A set of users with no browsing history in D-15 to D-1 but with a browsing history 16 days ago; 4) A set of users with no browsing history in D-21 to D-1 but with a browsing history 22 days ago; 5) In D-28 to D-1, users who have no viewing history but are included in the union of the user sets with a viewing history 29 days ago can be selected as event targets for the first event.

As in 1) and 2) above, the number of viewed content items may be further considered when determining the user set corresponding to users who left relatively recently.

Meanwhile, the event of the embodiment may further include at least one other event provided by the content service at a different cycle from the above-described first event.

In selecting the event subject in step 310, the computer system 100 considers the priority of the event when the event subject is selected as the event subject for the first event and other events and selects the event subject as the high priority event. Only event push notifications or event banners related to can be provided to the user terminal 100 of the event target.

For example, in providing the event push notification 30 or the event banner 20 in step 320, the computer system 100 may request the user terminal 50 to participate in a first event that has a higher priority than other events. An event push notification 30 or an event banner 20 requesting may be provided. At this time, the user terminal 50 may not be provided with an event push notification or event banner requesting participation in another event with lower priority. In this way, the first event corresponding to the daily departure care event may have a higher priority than other events (eg, second to fourth events to be described later).

Next, a case where the event includes a weekly breakaway care event will be described.

For example, such an event may include a second event provided on a weekly basis by the content service. When selecting an event subject in step 310, the computer system 100 may select an event subject for the second event (step 420).

The second event is, for example, an event that occurs (or is provided) every Thursday and may be a weekly breakaway care event. That is, according to the second event, the computer system 100 selects the user who is leaving the content service every week as the event target, and sends the event banner 20 or You can reserve and provide event push notifications (30).

Specifically, the computer system 100, among users using the content service, has a viewing history of content items for the most recent week based on the time of selection of the event target, and content items for the most recent third period. At least one user who has no viewing history for may be selected as an event target for the second event. For example, the computer system 100 considers users who have a history of viewing content items from the past week ago, but have no history of viewing content items during the past three days, as dropout users and select them as event targets. You can select.

At this time, the computer system 100 determines that among the at least one user who has no history of viewing content items during the most recent third period of time and who is considered an abandoned user, content items were viewed on only one day in the most recent week. A user who has a history and has viewed one content item (during the relevant day) may be excluded from being an event target for the second event. In other words, the computer system 100 may regard a user who views only one content item a week as a user who views only one content item that is updated every week, and such a user is naturally likely to return next week. can be predicted to be excluded from the event target for the second event.

In relation to this, Figure 6 shows a method of selecting event recipients for providing a second event (weekly breakaway care event) according to an example.

As shown in FIG. 6, when D-0 is Thursday as the event start date (or the time of selection of the event subject), the computer system 100 can select the event subject for the second event every Thursday. there is. The computer system 100 may select a user who has no browsing history during the three days from Monday to Wednesday of this week as an event target for the second event among users who have a browsing history during the seven days from Monday to Sunday of last week as of Thursday. there is. However, the computer system 100 may exclude users whose number of days with a one-week viewing history is 1 and the number of content items viewed is 1 from being event recipients.

Meanwhile, in selecting event subjects for the second event of the embodiment, similarly to the method of selecting event subjects for the first event described above, "whether the number of content items viewed by each user falls within a predetermined range " may be further considered, and users whose number of viewed content items is less than or equal to a predetermined value may be selected as event recipients for the second event.

By providing compensation according to the above-described second event, the computer system 100 may select users who leave every week and encourage the users to return to the content service.

Next, a case where the event includes a monthly breakaway care event will be described.

For example, such an event may include a third event provided every month by the content service. When selecting an event subject in step 310, the computer system 100 may select an event subject for the third event (step 430).

The third event is, for example, an event that occurs (or is provided) every day before the last day of each month and may be a monthly breakaway care event. That is, according to the third event, the computer system 100 selects the user who is leaving the content service every month as the event target, and sends the event banner 20 or You can reserve and provide event push notifications (30).

Specifically, the computer system 100 determines that among users who use the content service, based on the time of selection of the event target, there is a viewing history for content items last month and a viewing history for content items this month. At least one user who does not have one may be selected as an event target for the third event.

In relation to this, Figure 7 shows a method of selecting event recipients for providing a third event (monthly breakaway care event) according to an example.

As shown, in the case where D-0 is the event start date (or the time of selection of the event subject) and is the day before the last day of the month, the computer system 100 is the 1st to the last day of the last month (M-1) Users who have a viewing history for content items up to, but do not have a viewing history for content items from the 1st to D-1 of this month (M-0) can be selected as event recipients for the third event.

For example, if an event is held in December, D-0 is December 30th, and there is a viewing history for content items from 11/1 to 11/30, but from 12/1 to 12/29 A user who has no history of viewing content items until this day may be selected as an event target for the third event.

Meanwhile, in selecting event subjects for the third event of the embodiment, similarly to the method of selecting event subjects for the first event described above, "whether the number of content items viewed by each user falls within a predetermined range" " may be further considered, and users whose number of viewed content items is less than or equal to a predetermined value may be selected as event recipients for the third event.

By providing compensation according to the third event described above, the computer system 100 may select users who leave every month and encourage the users to return to the content service.

Next, a case where the event includes a purchase conversion inducing event will be described.

For example, this event may include a fourth event provided in a fourth period in the content service. When selecting an event subject in step 310, the computer system 100 may select an event subject for the fourth event (step 440). The fourth period may be, for example, one week. For example, the fourth event is an event that occurs (or is provided) every Friday and may be a purchase conversion inducing event. That is, according to the fourth event, the computer system 100 selects users who are not making paid payments in the weekly content service as event recipients, and provides rewards to the selected event recipients, so that the selected event recipients receive an event banner ( 20) Alternatively, you can reserve and provide event push notifications (30). Event recipients will use paid rounds of content items using the provided rewards, so event recipients may be encouraged to make additional paid payments.

The computer system 100 selects at least one user from among the users based on the users' viewing history for content items, the number of content items viewed by each user, and each user's payment history for the content items. You can be selected as an event target for the fourth event.

Specifically, when selecting an event target, the computer system 100 selects among users who use the content service, based on the time of selection of the event target, if there is a viewing history for content items during the most recent fifth period and the fifth period. At least one user who has no payment history for content items may be selected as an event target for the fourth event. Accordingly, event subjects requiring induction of paid payments may be selected.

At this time, the computer system 100, based on the time of selection of the event target among the at least one user who has no payment history for the content items during the fifth period, is a period shorter than the fifth period. A user whose number of content items viewed during the most recent sixth period falls within a predetermined second range may be selected as the event target for the fourth event. As an example, the second range may indicate that the number of viewed content items is 6 to 25.

In relation to this, Figure 8 shows a method of selecting event recipients to provide a fourth event (purchase conversion inducing event) according to an example.

As shown, when D-0 is Friday as the event start date (or the time of selection of the event subject), the computer system 100 stores content items in the past month (D-30 to D-1). Among users who have a viewing history, but no payment history during the period, users with 6 to 25 content items viewed can be selected as event recipients for the fourth event. Here, the existence of 'payment history' means that there is a history of purchasing cash or content items by paying actual currency, and/or there is a history of purchasing content items using rewards obtained according to the event. can indicate that

According to the fourth event, compensation is provided to selected event recipients and allows them to experience paid rounds of content items for free, thereby encouraging event recipients to make future paid payments.

Meanwhile, when the event page 1100 related to the fourth event is provided, the recommended content item exposed in the third area 1130 may include at least one paid episode. That is, the recommended content item displayed in the third area 1130 includes at least one paid episode that can be viewed using rewards obtained by the event target, and the content item containing only the free episode is displayed in the third area 1130. It may not be selected as a recommended content item displayed in .

The event banner provided to the user terminal 50 in connection with the fourth event may have a different form from the event banner 20 provided in connection with the first to third events.

In relation to this, Figure 13 shows an event banner provided to event recipients in connection with a fourth event (purchase conversion inducing event) according to an example.

As shown, the event banner 1300 may be configured to include images and/or text that are different from the event banner 20 described above. In other words, the fourth event may be configured differently from the event banner 20 in that it is not intended to return users who have left the content service.

Like the event banner 20, the event banner 1300 can also be personalized for the event target.

As technical features similar to those described above for the event banner 20 or the event push notification 30 may be applied to other event banners 1300, overlapping descriptions will be omitted.

As described above, the first event corresponding to the daily breakaway care event may have a higher priority than other events (eg, second to fourth events to be described later). Accordingly, when a user is selected as an event target for a plurality of events, only the event banner 20 or event push notification 30 corresponding to the first event may be preferentially provided to the user terminal 50. Meanwhile, the second event and the fourth event may be configured to occur weekly but on different days of the week, so that no duplicate event recipients are selected. If the second event and the fourth event are configured to occur on the same day of the week, the second event and the fourth event may have different priorities. For example, the second event may be set to have a higher priority than the third event. Meanwhile, the third event may be set to have a higher priority than the fourth event. Priorities between events may be configured differently than illustrated.

The device described above may be implemented with hardware components, software components, and/or a combination of hardware components and software components. For example, the devices and components described in the embodiments include a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), and a programmable logic unit (PLU). It may be implemented using one or more general-purpose or special-purpose computers, such as a logic unit, microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. Additionally, a processing device may access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, a single processing device may be described as being used; however, those skilled in the art will understand that a processing device includes multiple processing elements and/or multiple types of processing elements. It can be seen that it may include. For example, a processing device may include a plurality of processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are possible.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software and/or data may be used on any type of machine, component, physical device, virtual equipment, computer storage medium or device to be interpreted by or to provide instructions or data to a processing device. It can be embodied in . Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. At this time, the medium may continuously store a computer-executable program, or temporarily store it for execution or download. In addition, the medium may be a variety of recording or storage means in the form of a single or several pieces of hardware combined. It is not limited to a medium directly connected to a computer system and may be distributed over a network. Examples of media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, And there may be something configured to store program instructions, including ROM, RAM, flash memory, etc. Additionally, examples of other media include recording or storage media managed by app stores that distribute applications, sites or servers that supply or distribute various other software, etc.

As described above, although the embodiments have been described with limited examples and drawings, various modifications and variations can be made by those skilled in the art from the above description. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent.

Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the claims described below.

Claims (18)

In a method of providing an event related to a content service, performed by a computer system,
Among users using the content service, the event is generated based on at least one of the users' viewing history of a plurality of content items provided by the content service and the number of content items viewed by each of the users. Selecting at least one event subject to provide;
Providing an event push notification or event banner requesting participation in the event to a user terminal associated with the event target; and
As the event push notification or event banner is selected on the user terminal, providing available rewards to the event target for viewing or holding the content items.
A method of providing an event, including. According to paragraph 1,
Each of the content items includes at least one episode that can be viewed by the users,
The compensation is used for viewing paid episodes of the episodes or for possession of the episodes by the event recipients,
The event banner is displayed on the initial screen of the application when the application providing the content service is executed on the user terminal,
The event push notification is exposed on the user terminal while the application is not running on the user terminal,
The event push notification and the event banner are not exposed to user terminals of users who are not selected as event recipients among the users. According to paragraph 1,
The step of providing the compensation is,
When the event push notification or event banner is selected on the user terminal, providing an event page including information about the event to the user terminal; and
Providing the reward to the event subject according to the event subject's interaction with the event page
Including,
The event page includes a recommendation area that exposes at least one recommended content item selected from among the content items. According to paragraph 3,
The recommended content item includes at least one paid episode that the event target can view using the reward. According to paragraph 1,
The event includes a first event provided on a daily cycle by the content service,
The step of selecting event recipients is,
Among the users, based on the time of selection of the event target, at least one who has no viewing history for the content items during a recent certain period of time but has a viewing history for the content items on a date before the certain period of time A method of providing an event, selecting a user as an event target for the first event. According to clause 5,
The step of selecting event recipients is,
An event that selects a user whose number of viewed content items falls within a predetermined range among at least one user who has a viewing history for the content items on a date before the certain period of time as the event target for the first event. How to provide . According to clause 6,
The step of selecting event recipients is,
Among the users, based on the time of selection of the event target, there is no viewing history for the content items during the recent first period, but there is a viewing history for the content items on a date before the first period, and , a first event target set including users whose number of viewed content items falls within a predetermined first range;
Among the users, based on the time of selection of the event target, there is no viewing history of the content items during a recent second period that is longer than the first period, and the content is displayed on a date before the second period. A method of providing an event, wherein a user included in a union of a second event target set including users with a viewing history for items is selected as the event target for the first event. According to clause 5,
The event further includes other events provided by the content service at a different cycle from the first event,
In the step of selecting the event subject, when the event subject is selected as an event subject for the first event and the other event,
The step of providing the event push notification or event banner includes providing the user terminal with an event push notification or event banner requesting participation in the first event,
A method of providing an event, wherein an event push notification or event banner requesting participation in the other event is not provided to the user terminal. According to paragraph 1,
The event includes a second event provided on a weekly basis by the content service,
The step of selecting event recipients is,
Among the users, based on the time of selection of the event target, at least one user who has a viewing history for the content items in the recent one week, but does not have a viewing history for the content items in the recent third period A method of providing an event, selecting an event target for the second event. According to clause 9,
The step of selecting event recipients is,
Among the at least one user who has no viewing history for the content items during the recent third period, a user who has a viewing history for the content items on only one day in the most recent week and the number of content items viewed is one. is excluding from the event target for the second event
A method of providing an event, including. According to paragraph 1,
The event includes a third event provided every month by the content service,
The step of selecting event recipients is,
Among the users, based on the time of selection of the event target, at least one user who has a viewing history for the content items last month but does not have a viewing history for the content items this month is selected by the third user. A method of providing an event, selecting the event target for the event. According to paragraph 1,
The event includes a fourth event provided periodically in the fourth period in the content service,
The step of selecting event recipients is,
Based on the users' viewing history for the content items, the number of content items viewed by each user, and each user's payment history for the content items, at least one user among the users is selected as the second user. 4 A method of providing an event, selecting the event target for the event. According to clause 12,
The step of selecting event recipients is,
Among the users, based on the time of selection of the event target, at least one user who has a viewing history for the content items during the recent fifth period but does not have a payment history for the content items during the fifth period A method of providing an event, selecting the event target for the fourth event. According to clause 13,
The step of selecting event recipients is,
Among the at least one user who has no payment history for the content items during the fifth period, content items viewed during the most recent sixth period, which is a shorter period than the fifth period, based on the time of selection of the event target A method of providing an event, selecting users whose number falls within a predetermined second range as the event target for the fourth event. According to paragraph 1,
The event push notification is provided to the user terminal and exposed on the user terminal, regardless of the push limit setting indicating the number of push notifications that can be provided to the event target preset for the event target. A method of providing an event . According to paragraph 1,
The event banner is a personalized event banner that is exposed only on user terminals associated with the event target and is not exposed on user terminals of users who are not selected as the event target among the users, and includes identification information of the event target, How to present an event. A program recorded on a computer-readable recording medium for executing the method of claim 1 on the computer system. In a computer system that provides events related to content services,
At least one processor implemented to execute instructions readable by the computer system
Including,
The at least one processor,
Among users using the content service, the event is generated based on at least one of the users' viewing history of a plurality of content items provided by the content service and the number of content items viewed by each of the users. Select at least one event target to provide,
Providing an event push notification or event banner requesting participation in the event to a user terminal associated with the event target,
As the event push notification or event banner is selected at the user terminal, a computer system providing available rewards to the event target for viewing or possessing the content items.

Images