KR102006458B1 - Method and apparatus of detecting fabricated game account - Google Patents

Abstract

Disclosed are a method and an apparatus of detecting a fabricated game account. According to an embodiment, at least one log relevant to a state change of a game account is received from a first entity, and at least one log relevant to a state change of the game account is received from a second entity. A first change history of the game account is grasped on the basis of the log received from the first entity, and a second change history of the game account is grasped on the basis of the log received from the second entity. Moreover, the game account is determined to be fabricated on the basis of the first change history and the second change history.

Description

[0001] METHOD AND APPARATUS OF DETECTING FABRICATED GAME ACCOUNT [0002]

The following embodiments are directed to techniques for detecting tampering with a game account.

The game account may be manipulated by the game developer or the game operator.

Korean Unexamined Patent Application Publication No. 10-2016-0134309 entitled " Method and System for Detecting Unusual Users of Online Games ", filed by NCsoft Corporation). The disclosed patent discloses a technique of expanding the range of suspicious users of the bots automatically through transaction information generated in an online game after selecting suspect users of the bots and analyzing program logs and / A method and system for detecting a bot user and a bot-related user are disclosed.

A method of operating a game account tamper detection device according to one aspect includes receiving one or more logs of a status change of a game account from a first entity; Receiving from the second entity one or more logs of status changes of the game account; Determining a first change history of the game account based on one or more logs received from the first entity and determining a second change history of the game account based on one or more logs received from the second entity ; And checking whether the game account has been operated based on the first change history and the second change history.

The step of checking whether the game account has been operated may include estimating that the game account has been operated if a specific log in the second change history is not in the first change history.

The method may further include receiving a log of status changes of the game account from the third entity when a status change of the game account occurs through a third entity.

The log received from the third entity may include an indicator indicating whether the state change through the third entity is due to normal processing.

The step of checking whether the game account has been operated may include checking whether the game account has been operated through the indicator.

The method may further include, when the game account is determined to be operated, granting a notation indicative of the operated game account to the game account.

If there is vocation information for the operation of the game account, the notation may be deleted.

The status change may include at least one of a level change of the game character of the game user and a change of the goods of the game character.

The first entity may represent a game server and the second entity may represent a game database.

The game account tamper detection device according to one side receives one or more logs about a status change of the game account from a first entity and receives one or more logs from the second entity regarding status change of the game account A log receiving unit for receiving the log; And a second change history of the game account based on one or more logs received from the first entity and a second change history of the game account based on the one or more logs received from the second entity, And a controller for checking whether the game account has been operated based on the first change history and the second change history.

The control unit may estimate that the game account has been operated when the specific log in the second change history is not in the first change history.

The log receiving unit may receive a log regarding the status change of the game account from the third entity when a status change of the game account occurs through the third entity.

The log received from the third entity may include an indicator indicating whether the state change through the third entity is due to normal processing.

The controller can estimate the game account through the indicator with the manipulated game account.

When the game account is confirmed to have been operated, the controller may assign a notation indicating the operated game account to the game account.

If there is vocation information for the operation of the game account, the notation may be deleted.

The status change may include at least one of a level change of the game character of the game user and a change of the goods of the game character.

The first entity may represent a game server and the second entity may represent a game database.

Embodiments can bypass the game operation tool to detect a corresponding operation when a game account is manipulated, and detect manipulations for actual game operation and manipulation for a negative purpose. In addition, the embodiments can prevent a negative viral situation by displaying a message informing the operator (or test) to the game account in which the operation occurred. Embodiments can also detect negative (or malicious) account manipulation of the internal worker, thus ensuring transparency in game operations.

1 is a view for explaining a game system according to an embodiment.
2 to 7 are views for explaining the operation of the game system according to an embodiment.
FIG. 8 is a diagram for explaining a state information change and log collection flow between a game account operation detection device, a game server, an operation device, and a game database according to an embodiment.
9 to 10 are views for explaining an account operation notification and calling according to an embodiment.
FIGS. 11 to 14 are diagrams for describing notation of a game account detected by the game account operation detection device according to an embodiment.
15 is a flowchart illustrating a game account operation detection method according to an embodiment.
16 is a block diagram illustrating a game account operation detection apparatus according to an embodiment.

In the following, embodiments will be described in detail with reference to the accompanying drawings. However, various modifications may be made in the embodiments, and the scope of the patent application is not limited or limited by these embodiments. It is to be understood that all changes, equivalents, and alternatives to the embodiments are included in the scope of the right.

The terms used in the examples are used for descriptive purposes only and are not to be construed as limiting. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises" or "having" and the like refer to the presence of stated features, integers, steps, operations, elements, components, or combinations thereof, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this embodiment belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

In the following description of the present invention with reference to the accompanying drawings, the same components are denoted by the same reference numerals regardless of the reference numerals, and redundant explanations thereof will be omitted. In the following description of the embodiments, a detailed description of related arts will be omitted if it is determined that the gist of the embodiments may be unnecessarily blurred.

1 is a view for explaining a game system according to an embodiment.

1, a game system 100 according to an embodiment includes a game account operation detection device 110, a game server 120, an operation device 130, a game database 140, and a game client 150, .

Although the game system 100 is shown as including one game client 150 in FIG. 1, the game system 100 may include a plurality of game clients.

The game client 150 can access the game server 120. [ Accordingly, the game user can play the game through the game client 150.

The game client 150 may transmit the status information of the game account to the game server 120. [ The status information of the game account may include, for example, at least one of the goods, items, and status (e.g., level, proficiency, or race) of the game characters of the game account, But is not limited thereto. The game server 120 may store the status information received by the game client 150 in its own memory. In addition, the game server 120 may store or record the corresponding status information in the game database 140. [

The state of the game account may change due to the game play of the game user. For example, the level of the game character may increase or the amount of goods may increase. The game client 150 may transmit the changed status information of the game account to the game server 120 and the game server 120 may change the status information of the corresponding game account stored in the memory thereof.

The operating device 130 may inquire or change information of one or more game users for game operation. Such information may, for example, include, but is not limited to, the status information of the game account described above. The operating device 130 may be implemented as an operating tool for game operation or may include an operating tool.

The game account tamper detection device 110 detects account tampering. Account manipulation means that a game account is modified or changed in a manner other than normal game play. For example, the account manipulation may mean that at least one of the goods of the game account, the item, the status of the item, and the state of the game character is modified or changed in a manner not normal game play.

In an embodiment, the game account tamper detection device 110 may detect account tampering based on a status change log and an internal change log regarding the game account. Here, the status change log relating to the game account may be generated in the game server 120 among a plurality of entities in the game system 100, and the internal change log may be generated by various entities in the game system 100. [ May be generated in the operating device 130 or in the game database 140.

The account operation described above can be performed by an internal worker. Herein, the internal worker may not be a user who updates the status of the game account through normal game play, but rather an object which can arbitrarily change or manipulate one or more game accounts by accessing the operation device 130 and / or the game database 140 It can mean. An internal worker may, for example, include, but is not limited to, a game operator or a developer.

In an embodiment, the game account tamper detection device 110 may handle an account operation exception for a particular case. For example, when the state of a game account is changed by a customer service (CS), the game account operation detection device 110 collectively processes a plurality of game accounts for game operation, In the case where the status is changed, a game rollback situation occurs due to an issue in the game, and / or the status of each of the test accounts for the game test is changed, an account operation exception can be handled.

The game system 100 described above can detect the operation even when the game account is manipulated (for example, a log in the game database 140 is manipulated) by bypassing the manipulation tool, And manipulation of fraudulent purposes. In addition, the game system 100 can prevent an unauthorized viral situation by displaying a notice indicating that the game account has an arbitrary operation as an operator account (or a test account). In addition, the game system 100 can detect malicious intentional account manipulation of the internal worker, thereby ensuring transparency of the game operation. Malicious purpose account manipulation can be performed, for example, by manipulating an individual account by manipulation of an internal worker, manipulating an account using an operating tool by asking a person who has an acquaintance with an internal worker, But are not limited to, manipulation.

2 to 7 are views for explaining the operation of the game system according to an embodiment.

Referring to FIG. 2, the game client 150 transmits status information of the game account to the game server 120 (210). For example, when the level of the game character of the game account P0001 is changed from 5 to 6 and the goods are changed from 1000 to 1100 at 11:00 am on May 1, 2018 due to the game play of the game user of the game account P0001, The game server 150 may transmit the status information of the game account P0001 including the level 6 of the game character and the goods 1100 to the game server 120. [

The game server 120 changes state information of the game account based on the state information received from the game client 150 (230). For example, when the game server 120 receives status information including the changed level 6 and the changed goods 1100 from the game client 150, the game server 120 may change the level of the game character of the game account P0001 from 5 to 6 , And the goods can be managed by changing from 1000 to 1100.

When the status information of the game account is changed, the game server 120 transmits the status change log to the game account operation detection device 110 (250). For example, when the level of the game character of the game account P0001 is changed from 5 to 6 and the goods are changed from 1000 to 1100, the game server 120 transmits a status change log corresponding to the change to the game account operation detection device 110, Lt; / RTI > Here, the state change log may include, for example, a state before the change (level 5, item 1000), a state after change (level 6, goods 1100), and a change time of the game account P0001.

The game server 120 transmits the status information received from the game client 150 to the game database 140 (220). Since the state information before the change of the game account is recorded in the game database 140, the game server 120 may transmit the state information received from the game client 150 to the game database 140 so that the corresponding state information is changed . The game database 140 changes state information of the game account based on the state information received from the game server 120 (240). The game database 140 transmits the change information of the game account as a log to the game account operation detection device 110 (260). In other words, the game database 140 may send a status change log to the game account tamper detection device 110. In one example, the game database 140 may receive status information from the game server 120, including changed level 6 of the game account P0001 and the changed goods 1100. [ In this case, the game database 140 can manage the game character of the game account P0001 by changing the level of the game character from 5 to 6, and change the goods from 1000 to 1100 and manage it. Also, the game database 140 may transmit the change information of the game account P0001 to the game account operation detection device 110 in a log form. Here, the change information may include a state before change (level 5, goods 1000), a state after change (level 6, goods 1100), and a change time.

3, a status change log for each game account of the game server 120 is shown.

3, a status change log including the status change log of the game account P0001, that is, the status before change (level 5, goods 1000), the status after change (level 6, goods 1100) have.

In the example shown in FIG. 3, the level of the game character of the game account P0001 may be changed from 6 to 7 once again at 12:00 on May 1, 2018, and the goods may be changed once again from 1500 to 1800 . In this case, the game server 120 transmits a status change log including the state before the change (level 6, goods 1500), the state after change (level 7, goods 1800), and the change time of the game account P0001 to the game account operation detection device (110). In addition, the game server 120 may transmit the changed state (level 7, goods 1800) and the change time to the game database 140 so that the state information of the game account P0001 is once again changed on the game database 140, The game database 140 may transmit the change information to the game account operation detection device 110 after changing the status information of the game account P0001. Here, the change information may include, for example, a state before change (level 6, goods 1500), a state after change (level 7, goods 1800), and a change time.

3, the status information of each of the game accounts P0003, P0004, and P0005 may be changed on the game server 120, and the game server 120 may update the status information of each game account 120 The status change log of the game account may be transmitted to the game account operation detection device 110. [ Similarly, status information of each of the game accounts P0003, P0004, and P0005 may be changed in the game database 140, and the game database 140 may store change information of each game account each time the status information of each game account is changed To the game account operation detection device 110 in the form of a log.

If there is no account operation in the game database 140, the game change log for each game account received from the game server 120 by the game account operation detection device 110 is transmitted to the game account operation detection device 110 from the game database 140 It will be the same as the change information for each received game account. However, this is not the case when an account operation occurs on the game database 140 by the above-mentioned internal worker. This will be described later.

Referring to FIG. 4, the operating device 130 changes the status information of the game account (410). For example, the operating device 130 may change status information of a game account of a corresponding customer through an operation tool according to a customer service. Such a change may correspond to normal processing. In another example, the operating device 130 may change status information of one or more game accounts for game operations. Such changes are due to systematic decisions such as "electronic approval", which may correspond to normal processing. As another example, the operating device 130 may change the status information of the game account due to a trusted third party's consent, and such a change may also correspond to normal processing.

However, the internal worker can change the status information of the specific game account through the operation device 130 or the operation tool. This change is not due to the above-described customer response, not for game operation, and is not due to the consent of a reliable third party, and thus does not correspond to normal processing.

The operating device 130 transmits the change information of the game account as a log to the game account operation detection device 110 (440). In other words, the operating device 130 may transmit a status change log corresponding to the change information of the game account to the game account operation detection device 110. The change information may include, but is not limited to, an indicator indicating, for example, a pre-change state, a post-change state, a change time, and whether or not the change is due to normal processing.

When the operating device 130 changes the status information of the game account, the operating device 130 transmits the changed status information to the game database 140 (420). The game database 140 changes the status information of the game account in accordance with the changed status information (430). The game database 140 transmits the change information of the game account as a log to the game account operation detection device 110 (450). In other words, the game database 140 may transmit a status change log corresponding to change information of the game account to the game account operation detection device 110. [ The change information may include, for example, a pre-change state, a post-change state, and a change time, but is not limited thereto.

5, the level of the game character of the status information of the game account P0003 on the operating device 130 may be changed from 15 to 25. [ There is an indicator that this change is not due to normal processing on the operating device 130. For example, there may be an indicator that the level of the game character of the game account P0003 has been changed from 15 to 25 not due to the customer's response, but not due to the normal operation if not the result of the game operation. In other words, the change may correspond to an account operation by an internal worker.

When the status information of the game account P0003 is changed, the operating device 130 may transmit the change information of the game account P0003 to the game account operation detection device 110 in a log form. The change information may include, for example, a state before change (level 15, goods 1000), a state after change (level 25, goods 1000), a change time, and an indicator that the change is not due to normal processing.

The operating device 130 may transmit the changed status information of P0003 to the game database 140. [ Accordingly, the level of the game character of the game account P0003 may be changed from 15 to 25 on the game database 140, and the game database 140 may transmit the change information of the game account P0003 to the game account operation detection device 110, The change information may include a state before the change (level 15, 1000) of the game account P0003, a state after the change (level 25, 1000), and a change time.

The goods of account P0004 may be changed from 1500 to 11500 on the operating device 130. [ There is an indicator that this change is due to normal processing on the operating device 130. For example, there may be an indicator that the goods of the game account P0004 have been changed from 1500 to 11500 due to customer correspondence, or that the game account P0004 is due to normal operation.

The operating device 130 may transmit the change information of the game account P0004 to the game account operation detection device 110 in a log form. The change information may include, for example, a state before change (level 5, goods 1500), a state after change (level 5, goods 11500), a change time, and an indicator that the change is due to normal processing.

In addition, the operating device 130 may transmit the changed status information of P0004 to the game database 140. [ Accordingly, the goods of the game account P0004 may be changed from 1500 to 11500 in the game database 140, and the game database 140 may transmit the change information of the game account P0004 to the game account operation detection device 110 have. At this time, the change information may include a state before the change (level 5, item 1500), a state after change (level 5, goods 11500), and a change time of the game account P0004.

FIG. 6 shows change information of each of the game accounts of the game database 140. As shown in FIG.

The change information shown in FIG. 6 may coincide with the change information except the indicator of the operating device 130 described with reference to FIG. 5 and the status change log for each game account described with reference to FIG.

Referring to FIG. 7, an internal worker performs an account operation on the game account P0005 in the game database 140. [ In other words, the internal worker changes the level of the game character of the game account P0005 from 5 to 100 and the goods from 1200 to 99999. Accordingly, the change information 710 may be written to the game database 140 and the game database 140 may transmit the change information 710 to the game account operation detection device 110 in a log form.

The game account tamper detection device 110 may detect game account tampering based on logs received from various entities within the gaming system 100. For example, the game account operation detection apparatus 110 can grasp the first change history of each game account through the status change log for each game account received from the game server 120, The second change history for each game account can be grasped through the star change information. If there is no account manipulation in the game database 140 by the internal worker as in the example shown in Fig. 6, the first change history and the second change history will be the same. However, if there is an account operation by the internal worker as in the example shown in Fig. 7, the first change history will be different from the second change history. In other words, a state change that is not present on the game server 120 exists on the game database 140. The game account operation detection apparatus 110 can confirm that the game account P0005 has been operated since the status change log corresponding to the change information 710 existing only in the game database 140 does not exist in the game server 120. [ In other words, the history that the level of the game character of the game account P0005 of FIG. 7 is changed from 5 to 100 does not exist as the status change log on the game server 120 described with reference to FIG. 3. Therefore, the game account operation detection device 110 It can be confirmed that the game account P0005 has been operated.

In addition, the game account operation detection device 110 can detect the game account operation using the indicator described above. 3, when the level of the game character of the game account P0003 is changed from 15 to 25 and the value of the game account P004 is changed from 1500 to 115000 by the operating device 130, the indicator for the game account P0003 is Indicating that the state change is not due to normal processing, the game account operation detection device 110 can confirm that the game account P0003 has been operated. However, since the indicator for the game account P004 indicates that the state change is due to normal processing, the game account operation detection device 110 can confirm that the game account P0004 has not been manipulated.

FIG. 8 is a diagram for explaining a state information change and log collection flow between a game account operation detection device, a game server, an operation device, and a game database according to an embodiment.

In FIG. 8, a solid line indicates a flow of status information change, and a dotted line indicates a log collection flow.

8, the game server 120 can change the status information of the game account (810-1) and change the status information of the corresponding game account recorded on the game database 140 (810-2) . Also, the game server 120 may transmit the status change log to the game account operation detection device 110 (810-3). The game server 120 may transmit a status change log to the game account operation detection device 110 whenever the status information of one or more game accounts is changed. The game database 140 may transmit the change information of the game account to the game account operation detection device 110 as a log (830).

The operating device 130 may change the status information of the game account 820-1 and change the status information of the corresponding game account recorded on the game database 140 at operation 820-2. In addition, the operating device 130 may transmit information on the changed game account to the game account operation detection device 110 as a log (820-3). The operating device 130 may log information on the changed game account to the game account operation detection device 110 whenever the status information of one or more game accounts is changed. The game database 140 may transmit the change information of the game account to the game account operation detection device 110 as a log (830).

The game database 140 may transmit the change information for each game account to the game account operation detection device 110 as the log information is changed (830).

The game account operation detection device 110 can estimate that the account operation has been performed by the internal worker by the operating device 130 in a game account that has been changed in a non-normal manner. In the example described above, the game account operation detection device 110 can estimate that the game account P0003 has been accounted for by the internal worker. In addition, the game account operation detection device 110 can estimate that the account operation has been performed by the internal worker in a game account that is not in the game server 120 and has a history of change recorded only in the game database 140. [ In the example described above, the game account operation detection device 110 can estimate that the game account P0005 has been accounted for by the internal worker.

1 through 7 can be applied to the matters described with reference to FIG. 8, detailed description thereof will be omitted.

9 to 10 are views for explaining an account operation notification and calling according to an embodiment.

According to one embodiment, the game account operation detection device 110 or the operation device 130 can continuously track (or monitor) the activities of the internal test account and the arbitrarily operated account. In addition, the game account operation detection device 110 or the operation device 130 may track (or monitor) the number of days of activity and the recent activity status so that the operator can confirm the operation. In addition, the game account operation detection device 110 or the operation device 130 may perform account sanctioning based on the tracking result. Here, the game account operation detection device 110 or the operation device 130 may proceed with the sanitization process through the notification by period or the notification by the order. In addition, the game account operation detection device 110, the operation device 130, or a call requesting device, which will be described later, can designate a notification target or a call target. If there is no call according to the notification, Not possible). If the account operation has occurred, the game account may be a test account for testing. In this case, if the corresponding game account is excluded from the request for calling, it can be excluded from the above-mentioned sanctioning process.

In the example shown in FIG. 9, the game account operation detection device 110 can notify the game client 150 of an account operation when it is confirmed that an account operation has occurred in the game account of the game user of the game client 150. [ In other words, the game account operation detection device 110 may transmit an account operation notification to the game client 150. [

The game client 150 may indicate that the game account of the game user is in an account operation state. For example, the game client 150 may indicate on the game play screen that the corresponding game account is in an account operation state. Although not shown in FIG. 9, the game account operation detection device 110 may notify each of the other game clients that the game account of the game user of the game client 150 has been operated. Each of the other game clients may indicate that the game account of the game user of the game client 150 is in an account operation state on his or her game screen. These notations will be described later with reference to FIG. 11 through FIG.

The game client 150 or a separate device may transfer the calling information of the game user to the operating device 130. Here, the calling information may correspond to information indicating that the operation is not an account operation. Accordingly, the game user can call the game operator not an account operation.

The operating device 130 can confirm the calling information. The operating device 130 can write the history of being called to the state information of the game account of the corresponding game user and handle it as an exception of the account operation when the account operation state is not claimed through the corresponding calling information .

The operating device 130 can inform the game account operation detection device 110 of the calling result. The game account operation detection apparatus 110 can know that the corresponding game account has been treated as an exception of account operation.

The game system 100 shown in FIG. 10 may further include a requestor 1010 as compared to the example shown in FIG.

The game account operation detection device 110 may notify the game client 150 of an account operation when it is confirmed that an account operation has occurred in the game account of the game user of the game client 150. [ At this time, the game account operation detection device 110 can notify the request name requestor 1010 that the corresponding account has been operated through the operation device 130. If the game account of the game client 150 corresponds to the game test account, the game account operation detection device 110 may transmit a notification to the game client 150 to indicate that the corresponding game account is a test account. The description of the test account will be described later with reference to FIG. 13 through FIG.

The operating device 130 may grant a calling opportunity to the game user before the account sanction through the calling requestor 1010, and if the calling is not made, the accountant can proceed to the game account of the corresponding game user, If so, the game account can be processed for exceptional processing. In one example, the operating device 130 may determine that an account manipulation is detected in game account A of the game user of game client 150 to apply an account sanction to game account A. If there is such a determination, the operating device 130 may provide the game client 150 with target information requiring calling through the calling requestor 1010. For example, the operating device 130 may send the target information including the name of the game character A of the game account A suddenly changed from 5 to 100 to the game client 150 through the call requestor 1010 Lt; / RTI > The game client 150 receiving the target information can activate the calling function and send the calling information including the calling request inputted from the game user to the operating device 130. [ The operating device 130 can determine whether the calling of the game user has been made based on the calling information. The operating device 130 can proceed with the account reallocation to the game account A if the call is not made. If the operating device 130 is called, the game account A can proceed to an exception process from the object of account settlement. For example, if the game account A corresponds to a game test game account and there is a call to change the level from 5 to 100 for game test, the operating device 130 determines that the call is appropriate, You can proceed with exception handling from the account sanction

FIGS. 11 to 14 are diagrams for describing notation of a game account detected by the game account operation detection device according to an embodiment.

9, the game account operation detection device 110 may notify the game client 150 of the account operation of the game account of the game user, and the game client 150 may notify the game account 150 of the account of the game account in the game Can be given. Such notation may be sufficient for the game user or other game users to recognize.

11, when the game client 150 receives a notification from the game account operation detection device 110 that the game account of its game user "Ares" is account operated, the game client 150 displays the object 1110 on the game screen, Can be exposed. At this time, an object indicating that the game account of the game user "Ares" is account-operated may be displayed on the game screen of the game client of another game player playing the game together with the game user "Ares. &Quot; Accordingly, another game user playing the game together with the game user "Ares " can recognize that the game account of the game user" Ares "

Referring to FIG. 12, the game client 150 may expose an object 1210 indicating that the game account of its own game user "Ares " is account operated, to the ranking screen. At this time, the object 1201 may be exposed to the ranking screen of game clients of other game users. Accordingly, another game user can recognize that the game account of the game user "Ares" is account operated.

Referring to FIG. 13, the game client 150 may expose the object 1310 to the game character detail screen of the game user "Lana ". Other game clients may expose the object 1310 to the detailed screen of the game character of the game user "Ares. &Quot; Accordingly, another game user can recognize that the game account of the game user "Ares" is an operator account.

Referring to FIG. 14, the game client 150 may expose an object 1410 around the game character 1420 of the game screen. The object 1410 can be exposed around the game character of "Lanna" on the game screen of the game client of another game user corresponding to the game character 1420. [ Accordingly, other game users can recognize that the game account of "Lona" is a test account.

15 is a flowchart illustrating a game account operation detection method according to an embodiment.

The game account manipulation detection method may be performed by the game account manipulation detection device 110.

Referring to FIG. 15, the game account operation detection apparatus 110 receives 1510 a log of at least one log regarding a status change of a game account from a first entity in the game system 100. Here, the first entity may correspond to the game server 120.

The game account operation detection device 110 receives 1520 the one or more logs regarding the status change of the game account from the second entity. Here, the second entity may correspond to the game database 140.

The game account operation detection device 110 may be configured to determine a first change history of the game account based on the one or more logs received from the first entity and to determine a second change of the game account based on the one or more logs received from the second entity The history is grasped (1530).

The game account operation detection device 110 determines whether the game account has been operated based on the first change history and the second change history (1540). In step 1540, the game account operation detection device 110 may estimate that the game account has been tampered with when the particular log in the second change log is not in the first change log.

In an embodiment, the game account tamper detection device 110 may receive a log of status changes of the game account from the third entity when a status change of the game account occurs via the third entity. Here, the third entity may correspond to the operation device 130, and the log received from the third entity may include an indicator indicating whether the state change through the third entity is due to normal processing. The game account operation detection device 110 can confirm whether or not the game account has been operated through the indicator.

In an embodiment, when the game account operation detection device 110 determines that the game account has been operated, the game account operation detection device 110 may assign a notation indicating the operated game account to the game account. Accordingly, as described with reference to FIGS. 11 to 14, an object indicating that the game account is an operated game account or an operator account (or a test account) on the game play screen may be displayed on the game screen. If there is vocabulary information for an operation of the game system, the notation described above may be deleted. Such notation may be deleted by the game account operation detection device 110 or the operation device 130. [

Since the matters described with reference to Figs. 1 to 14 can be applied to the matters described with reference to Fig. 15, detailed description will be omitted.

16 is a block diagram illustrating a game account operation detection apparatus according to an embodiment.

16, the game account operation detection device 110 includes a log reception unit 1610 and a control unit 1620. [ The log receiving unit 1610 and the control unit 1620 may be implemented by one or more processors.

The log receiver 1610 receives one or more logs relating to the status change of the game account from the first entity in the game system 100 and receives one or more logs regarding the status change of the game account from the second entity.

The control unit 1620 grasps the first change history of the game account based on the one or more logs received from the first entity and grasps the second change history of the game account based on the one or more logs received from the second entity . The control unit 1620 checks whether the game account has been operated based on the first change history and the second change history.

Since the matters described with reference to Figs. 1 to 15 can be applied to the matters described with reference to Fig. 16, detailed description will be omitted.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) , A programmable logic unit (PLU), a 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. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (16)

A method of operating a game account tamper detection device,
The method comprising: receiving one or more logs of status changes of a game account from a first entity;
Receiving from the second entity one or more logs of status changes of the game account;
Determining a first change history of the game account based on one or more logs received from the first entity and determining a second change history of the game account based on one or more logs received from the second entity ; And
Determining whether the game account has been operated based on the first change history and the second change history
Lt; / RTI >
Wherein the game account operation detection apparatus further comprises a log information receiving unit operable to log the log received from the third entity when a status change of a specific game account occurs through a third entity and a log relating to a status change of the specific game account is received from the third entity, Based on whether or not the specific game account has been operated,
Wherein the log received from the third entity includes an indicator indicating whether the status change through the third entity is due to normal processing,
A method of operating a game account tamper detection device.
The method according to claim 1,
Wherein the step of verifying whether the game account has been operated comprises:
Estimating that the game account has been tampered when a specific log in the second change history is not in the first change history
/ RTI >
A method of operating a game account tamper detection device.
delete The method according to claim 1,
Wherein the game account operation detection device comprises:
And determining whether the specific game account has been operated through the indicator,
A method of operating a game account tamper detection device.
The method according to claim 1,
If it is determined that the game account has been operated, assigning a notation indicating that the game account is a manipulated game account to the game account
≪ / RTI >
A method of operating a game account tamper detection device.
6. The method of claim 5,
If there is vocation information for the operation of the game account,
A method of operating a game account tamper detection device.
The method according to claim 1,
Wherein the state change of the game account includes at least one of a level change of the game character of the game account and a change of the goods of the game character,
Wherein the state change of the specific game account includes at least one of a level change of a game character of the specific game account and a change of a game character of the specific game account.
A method of operating a game account tamper detection device.
The method according to claim 1,
The first entity representing a game server and the second entity representing a game database,
A method of operating a game account tamper detection device.
A log receiver for receiving one or more logs of status changes of a game account from a first entity and receiving one or more logs of status changes of the game accounts from a second entity; And
A first change history of the game account based on one or more logs received from the first entity and a second change history of the game account based on one or more logs received from the second entity, A controller for checking whether the game account has been operated based on the first change history and the second change history,
Lt; / RTI >
When the status of the specific game account is changed through the third entity and the log of the status change of the specific game account is received from the third entity, the control unit determines, based on the log received from the third entity, Check to see if the game account has been tampered with,
Wherein the log received from the third entity includes an indicator indicating whether the status change through the third entity is due to normal processing,
Game account tamper detection device.
10. The method of claim 9,
Wherein the control unit estimates that the game account has been tampered when the specific log in the second change log is not in the first change log,
Game account tamper detection device.
delete 10. The method of claim 9,
Wherein the controller checks whether the specific game account has been operated through the indicator,
Game account tamper detection device.
10. The method of claim 9,
Wherein the control unit provides the game account with a notation indicating that the game account is a manipulated game account when it is determined that the game account has been operated,
Game account tamper detection device.
14. The method of claim 13,
If there is vocation information for the operation of the game account,
Game account tamper detection device.
10. The method of claim 9,
Wherein the state change of the game account includes at least one of a level change of the game character of the game account and a change of the goods of the game character,
Wherein the state change of the specific game account includes at least one of a level change of a game character of the specific game account and a change of a game character of the specific game account.
Game account tamper detection device.
10. The method of claim 9,
The first entity representing a game server and the second entity representing a game database,
Game account tamper detection device.

Images