Resource change reminding method and device, electronic equipment and storage medium

Abstract

The application provides a resource change reminding method and device, electronic equipment and storage medium; wherein the method comprises: in response to a change submission instruction of a first resource, obtaining submission information of the first resource; based on the submission information and / or the historical version of the first resource, determining whether the submission information involves the change of a specified attribute resource in the first resource, and whether the trigger account of the change submission instruction matches the specified attribute resource, and sending a resource change reminder to the account matching the specified attribute resource. In this way, when the first resource submits a change, if the change of the first resource involves the change of the specified attribute resource, and the change of the first resource is not triggered by the account matching the specified attribute resource, a change reminder is sent to the account matching the specified attribute resource, so that the account can timely make a synchronous change of the resource, thereby improving the timeliness of resource synchronization.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and storage medium for notifying users of resource changes. Background Technology

[0002] With the development of internet technology, the specialization of job positions has led to an increase in professionalism and product quality. For the same resource file, it often requires the cooperation of professionals from upstream and downstream positions. For example, in games, animation resources need to be completed by motion effects artists upstream, and then by sound effects artists downstream.

[0003] However, in most cases, after upstream staff make modifications to resources, they may unknowingly affect the performance of downstream resources, or they may know that they have affected the performance of downstream resources but fail to notify downstream staff to make corresponding modifications in a timely manner, resulting in untimely resource synchronization changes. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method, apparatus, electronic device and storage medium for notifying resource changes, so as to improve the timeliness of resource synchronization changes.

[0005] In a first aspect, embodiments of the present invention provide a method for notifying users of resource changes. The method includes: responding to a change submission instruction for a first resource and obtaining submission information for the first resource; determining, based on the submission information and / or a historical version of the first resource, whether the submission information involves a change to a resource with a specified attribute in the first resource; if the submission information involves a change to a resource with a specified attribute in the first resource, determining whether the triggering account of the change submission instruction matches the resource with the specified attribute; if the triggering account of the change submission instruction does not match the resource with the specified attribute, sending a resource change notification to the account that matches the resource with the specified attribute.

[0006] Secondly, embodiments of the present invention provide a resource change notification device, the device comprising: an acquisition module, configured to acquire submission information of the first resource in response to a change submission instruction for a first resource; a determination module, configured to determine, based on the submission information and / or a historical version of the first resource, whether the submission information involves a change to a specified attribute resource in the first resource; a matching module, configured to determine, if the submission information involves a change to a specified attribute resource in the first resource, whether the triggering account of the change submission instruction matches the specified attribute resource; and a sending module, configured to send a resource change notification to the account that matches the specified attribute resource if the triggering account of the change submission instruction does not match the specified attribute resource.

[0007] Thirdly, embodiments of the present invention provide an electronic device, including a processor and a memory, wherein the memory stores machine-executable instructions that can be executed by the processor, and the processor executes the machine-executable instructions to implement the above-mentioned resource change notification method.

[0008] Fourthly, embodiments of the present invention provide a machine-readable storage medium storing machine-executable instructions. When the machine-executable instructions are invoked and executed by a processor, the machine-executable instructions cause the processor to implement the aforementioned resource change notification method.

[0009] The embodiments of the present invention bring the following beneficial effects:

[0010] The aforementioned resource change notification method, device, electronic device, and storage medium respond to a change submission instruction for a first resource and obtain the submission information of the first resource; based on the submission information and / or the historical version of the first resource, determine whether the submission information involves a change to a specified attribute resource in the first resource; if the submission information involves a change to a specified attribute resource in the first resource, determine whether the triggering account of the change submission instruction matches the specified attribute resource; if the triggering account of the change submission instruction does not match the specified attribute resource, send a resource change notification to the account that matches the specified attribute resource. In this method, when a change is submitted for the first resource, it is determined whether the change of the first resource involves a change to a specified attribute resource based on the submission information and the historical version. If the change of the first resource involves a change to a specified attribute resource, and the change of the first resource is not triggered by an account that matches the specified attribute resource, then a change notification is sent to the account that matches the specified attribute resource, so that the account can promptly synchronize the resource changes, thereby improving the timeliness of resource synchronization.

[0011] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0012] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0013] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0014] Figure 1 This is a flowchart of one embodiment of the resource change notification method in this invention.

[0015] Figure 2 A schematic diagram of a resource change notification device provided in an embodiment of the present invention;

[0016] Figure 3 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” or “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0019] It is understood that the executing entity of this invention can be a resource change notification device, a terminal, or a server; no specific limitation is made here. This embodiment of the invention will be described using a server as the executing entity as an example.

[0020] The application scenario of this invention is that the first resource is completed collaboratively by multiple people. The first resource includes performance attributes of a specified attribute resource. The performance attributes are used to indicate the appearance of the specified attribute resource in the first resource. The developers of the first resource can modify the attributes of the specified attribute resource in the first resource to change its appearance. For example, assuming the first resource is an art resource and the specified attribute resource is an audio file, then the performance attributes of the specified attribute resource can be: the attachment position of the audio file in the art resource, the delay duration, the trigger condition, the number of repetitions, etc. As another example, assuming the first resource is an animation scene resource and the specified attribute resource is a virtual animated character resource, then the performance attributes of the specified attribute resource can be: the attachment point attribute of the virtual animated character resource in the animation scene resource, the number of frames, the transparency, the curve, etc. The resource attributes of the specified attribute resource are the attributes of the specified attribute resource itself, such as the sampling rate, number of channels, bit depth, bit rate, etc. of the audio file, and the skeletal information, skinning information, animation curves, etc. of the virtual animated character resource.

[0021] It is understandable that, in addition to changes in the performance attributes of the specified attribute resources in the first resource potentially affecting their presentation within the first resource, modifications to the first resource itself may also influence the presentation of the specified attribute resources within it. For example, changes to the attachment points of art resources may affect the attachment positions of audio files within the art resources; changes to the animation duration of art resources may affect the delay duration, repetition count, and other presentation characteristics of audio files within the art resources; changes to the nodes of scene animation resources may affect the attachment points of virtual animated character resources within the scene animation resources, and so on. In summary, modifications to the first resource may affect the presentation of the specified attribute resources within the first resource, leading to anomalies in the first resource. Therefore, this invention aims to determine whether changes to the first resource involve changes to the specified attribute resources and to promptly send notifications of such changes to the relevant personnel accounts, enabling them to promptly update the specified attribute resources in accordance with the changes to the first resource.

[0022] As an example, and not a limitation, this scenario describes a specific application where the first resource is an art resource, and the specified attribute resource within that first resource is an audio resource. The art resource can be of different types, such as effects resources, model resources, or scene resources. In existing workflows, audio production is typically at the end of the workflow. When upstream resources change, audio producers often cannot be informed of the change in time to synchronize the audio resource in the first resource. This leads to errors and degraded sound effects in the art resource, such as audio-visual asynchrony, audio interruptions, and unresponsive audio. Consequently, the art resource's presentation is flawed, resulting in a degraded user experience. For instance, if a large flame in an art resource is changed to a small flame during a modification process, the audio may not be synchronized in time, causing the sound of the small flame to still be that of a large fire, creating a jarring audio-visual asynchrony.

[0023] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 One embodiment of the resource change notification method in this invention includes:

[0024] Step S10: Respond to the change submission instruction of the first resource and obtain the submission information of the first resource;

[0025] In one implementation, to improve the development and management efficiency of resource collaboration, different versions of resources (including but not limited to the first resource and resources with specified attributes) are stored on servers, including local servers and cloud servers. The matching account for a resource has resource operation permissions on the server, and the matching account can share resources on the server, thereby enabling collaborative development of the resources on the server. Typically, the matching account for a resource is used to indicate the collaborative developer account for the resource. For example, the development of art resources requires collaboration from developers with different functions such as concept artists, special effects artists, and sound effects artists. Therefore, the matching account for the art resource can include accounts of concept artists, special effects artists, sound effects artists, and other relevant personnel accounts; the specifics are not limited here.

[0026] Based on the above, to further improve the development and management efficiency of resource collaboration, a version control system is used to version control the resources submitted to the server. This version control system can be SVN (a branch-based version control system), Git (a distributed version control system), etc. With a version control system, each change to a resource generates a new version, which becomes the current version, and the commit information is recorded on the server for version comparison and change tracking, thus improving resource management efficiency. It is understood that commit information includes, but is not limited to, the commit version number (i.e., the current version number), commit account information, commit time, commit file path, commit file list, change type of the committed files (e.g., added, modified, deleted), commit log, description information, and other commit operation attribute information. In one implementation, step S10 includes: responding to the change commit command of the first resource through the hook mechanism of the version control system, triggering a commit completion hook event, and collecting the commit information of the first resource through the commit completion hook event. The commit completion hook event refers to the hook that occurs after the resource commit is completed and the version is successfully created, such as the post-commit event in SVN. The format of the commit information can be JSON data exchange format, dictionary data structure format, etc., and is not specifically limited here. This implementation can collect commit information immediately after resource commit, making the acquisition of commit information more timely and accurate.

[0027] In one implementation, the resource is stored in a resource repository or resource pool of the version control system. Step S10 includes: responding to the triggering of a resource commit event in the resource repository, and obtaining the commit information of the first resource through the resource commit event. It is understood that for all change commit instructions in the resource repository or resource pool, a resource commit event in the resource repository is triggered, and resource commit information is obtained through the resource commit event, thereby obtaining the commit information of the first resource.

[0028] Step S20: Based on the submission information and / or the historical version of the first resource, determine whether the submission information involves changes to the specified attribute resource in the first resource;

[0029] In one implementation, the submission information of the first resource includes the current version number and the submission time. The current version number indicates the submission version number of the current version, the submission time indicates the submission time of the current version, and the historical version of the first resource indicates the historical submission version whose submission time is closest to the submission time of the current version, that is, the previous version of the current version. For example, the current version number is 2.0.0, and the commit time is 2022.08.01 12:00:00. Assume that the resource repository or resource pool contains three historical versions of the first resource: historical version A has a commit version number of 1.0.1 and a commit time of 2022.07.01 12:00:00; historical version B has a commit version number of 1.2.0 and a commit time of 2022.07.30 12:00:00; and historical version C has a commit version number of 1.2.10 and a commit time of 2022.07.30 18:00:00. Since the commit time of historical version C is closest to the commit time of the current version, historical version C is the historical version of the first resource. This implementation method can quickly determine whether the commit information of the current version involves changes to a specified attribute resource in the first resource without needing to go through all historical versions of the current version, making the determination of changes to specified attribute resources more efficient.

[0030] In one implementation, to improve the efficiency of change detection for specified attribute resources in the first resource and quickly determine whether the current version's commit information involves changes to the specified attribute resources in the first resource, a preliminary determination is made based on the commit information to obtain a preliminary determination result. This preliminary determination result can be used to determine whether the commit information involves related information files of the specified attribute resources in the first resource. If the preliminary determination indicates that the current version's commit information involves changes to the specified attribute resources in the first resource, further determination is made based on the preliminary determination result and historical versions of the first resource to obtain a target determination result. If the preliminary determination indicates that the current version's commit information does not involve changes to the specified attribute resources in the first resource, it means that the changes to the first resource in the current version will not affect the representation of the specified attribute resources in the first resource, and the current change commit is directly filtered without further processing. This change commit refers to the commit triggered by the change commit command. It is understood that the commit file path, commit file list, commit account information, commit log, etc., in the commit information can all be used to preliminarily determine whether the current version's commit information involves changes to the specified attribute resources in the first resource. As an example, and not a limitation, the submitted account information is compared with a preset whitelist of submitted accounts. Based on the comparison results, it is initially determined whether the current version of the submitted information involves changes to a specified attribute resource in the first resource. The whitelist of submitted accounts indicates the submitting accounts that match the specified attribute resource. For example, assuming the specified attribute resource is an audio file, the whitelist could include accounts belonging to audio production personnel. If the current version's change submission was triggered by an audio production personnel's account, it can be directly determined that the current version's change submission involves changes to a specified attribute resource in the first resource. Therefore, there is no need to further determine whether it involves changes to the specified attribute resource of the first resource, nor is it necessary to send resource change notifications to the audio production personnel's account. This change submission can be directly filtered without further processing. This implementation can quickly determine whether a change submission involves changes to a specified attribute resource through the submitted information, thereby quickly filtering submissions that do not involve changes to the specified attribute resource, improving the accuracy of resource synchronization change notifications.

[0031] Based on the above, if the preliminary judgment determines that the submitted information involves information files related to a specified attribute resource in the first resource, then based on the preliminary judgment result and the historical versions of the first resource, it is further determined whether the current version of the submitted information involves changes to the specified attribute resource in the first resource, thus obtaining the target judgment result. Specifically, relevant information files are extracted from the historical versions of the first resource to obtain historical relevant information files, and then relevant information files are extracted from the current version of the first resource to obtain current relevant information files. The current relevant information files are compared with the historical relevant information files to obtain resource difference information, and then the resource difference information is used to determine whether the submitted information involves changes to a specified attribute resource in the first resource. For example, assuming the specified attribute resource is an audio resource, if the resource difference information contains keywords unique to audio files, such as "sound" or ".bnk", then it can be determined that the submitted information involves changes to the audio resource in the first resource. This implementation method can determine whether the current version of the submitted information involves changes to a specified attribute resource based on the differences between the current submitted version and the historical versions, thereby improving the timeliness of synchronous changes to the specified attribute resource.

[0032] Step S30: If the submitted information involves changes to the specified attribute resource in the first resource, determine whether the account that triggered the change submission instruction matches the specified attribute resource.

[0033] Understandably, if the submitted information involves changes to a specified attribute resource in the first resource, it means that the submission triggered by the change submission instruction will affect the representation of the specified attribute resource in the first resource. Therefore, it is necessary to further determine whether the submission triggered by the change submission instruction was triggered by an account matching the specified attribute resource. If the submission triggered by the change submission instruction was triggered by an account matching the specified attribute resource, there is no need to send a resource change notification to the triggering account of the change submission instruction again, because the account matching the specified attribute resource already includes the triggering account of the change submission instruction. It should be noted that the account matching the specified attribute resource is used to indicate the whitelist account for changes to the specified attribute resource. In other words, the account matching the specified attribute resource is the designated change account for the specified attribute resource. It can be a functional account for the specified attribute resource, or a management account for the first resource or the specified attribute resource; the specifics are not limited here. For example, assuming the first resource is an art resource and the specified attribute resource is an audio resource, if the account that triggers the change submission instruction is the motion graphics staff account, then if it is determined that the change submitted by the motion graphics staff account involves changes to the audio resource, it is determined whether the account that triggers the change submission instruction does not match the specified attribute resource. However, if the account that triggers the change submission instruction is the audio staff account, it can be directly determined that the account that triggers the change submission instruction matches the specified attribute resource, without needing to send a resource change reminder to the audio staff account.

[0034] In one implementation, determining whether the triggering account of a change submission instruction matches a specified attribute resource includes: obtaining a list of specified submission accounts for the specified attribute resource, and determining whether the list of specified submission accounts contains the triggering account of the change submission instruction; if the list of specified submission accounts contains the triggering account of the change submission instruction, then the triggering account of the change submission instruction matches the specified attribute resource; if the list of specified submission accounts does not contain the triggering account of the change submission instruction, then the triggering account of the change submission instruction does not match the specified attribute resource. In this implementation, submission account information is obtained from the submission information, which includes the triggering account information of the change submission instruction. The submission account information is then compared with a preset list of specified submission accounts for the specified attribute resource to determine whether the triggering account of the change submission instruction is included in the list of specified submission accounts for the specified attribute resource. If the triggering account of the change submission instruction is included in the list of specified submission accounts for the specified attribute resource, then the triggering account of the change submission instruction matches the specified attribute resource; if the triggering account of the change submission instruction is not included in the list of specified submission accounts for the specified attribute resource, then the triggering account of the change submission instruction does not match the specified attribute resource. This implementation can filter change submission commands triggered by specified accounts for specified attribute resources, thereby providing more accurate resource synchronization change reminders.

[0035] Step S40: If the account that triggered the change submission instruction does not match the specified attribute resource, send a resource change notification to the account that matches the specified attribute resource.

[0036] In this step, if the account triggering the change submission command does not match the specified attribute resource, the change submission command is determined to affect the representation of the specified attribute resource in the first resource, and is therefore considered an abnormal submission command. The account matching the specified attribute resource needs to be notified so that the matching account can promptly synchronize the resource changes. Specifically, sending a resource change notification to the account matching the specified attribute resource includes: generating resource change information for the specified attribute resource and sending a resource change notification containing this information to the matching account. The submission information is encapsulated according to a preset notification format to obtain resource change information, and this resource change notification is sent to the account matching the specified attribute resource in the form of resource change information. Furthermore, to make the resource change notification more intuitive, changes to the specified attribute resource in the first resource are categorized by change type based on the submission information or historical versions of the first resource. The resource change type and submission information are then encapsulated in a preset notification format, and the resource change message is sent to the account matching the specified attribute resource.

[0037] In one implementation, resource change notifications can be sent to a single account or in batches to multiple accounts. To improve the timeliness of resource synchronization changes, resource change notifications can be sent in batches to multiple accounts that match the specified attribute resources. After each account that matches the specified attribute resources receives the resource change notification, it can determine whether it needs to perform synchronization changes to the specified attribute resources, thereby improving the timely coverage of resource synchronization changes.

[0038] The resource change notification method provided in the above implementation method determines whether the change of the first resource involves a change of a specified attribute resource based on the submission information and historical versions when the first resource is submitted for change. If the change of the first resource involves a change of a specified attribute resource, and the change of the first resource is not triggered by an account matching the specified attribute resource, then a change notification is sent to the account matching the specified attribute resource so that the account can promptly synchronize the resource change, thereby improving the timeliness of resource synchronization.

[0039] The following describes the method for determining changes to a specified attribute resource in the first resource. In one implementation, based on the submission information and / or the historical version of the first resource, determining whether the submission information involves changes to a specified attribute resource in the first resource includes the following steps:

[0040] (1) Determine whether the submitted information involves relevant information files of the resource with specified attributes in the first resource;

[0041] It should be noted that this step initially determines whether the submission triggered by the change command involves changes to the resource with the specified attribute in the first resource by submitting the information. Specifically, it determines whether the submission triggered by the change command contains relevant information files for the resource with the specified attribute in the first resource. For example, assuming the specified attribute resource is an audio resource, if the submission triggered by the change command contains an audio resource, it can be determined that the submission triggered by the change command contains relevant information files for the resource with the specified attribute in the first resource. For example, if the .sfxmusic file contains audio information indicating which audio .bnk file needs to be read and which event needs to be played in that .bnk file, then if the relevant information files contain a file with the .sfxmusic extension, it can be determined that the submission information involves relevant information files for the resource with the specified attribute in the first resource. This .sfxmusic file will then be used for subsequent resource difference information extraction files, thereby more efficiently identifying changes related to the specified attribute resource and thus more efficiently providing resource synchronization reminders.

[0042] In one implementation, the submission information can be quickly determined by the submission file path and submission file type in the submission information to determine whether the submission information involves related information files of the specified attribute resource in the first resource. Specifically, the submission information includes the submission file path and submission file type. Step (1) includes: comparing the submission file path and submission file type with the preset file path list and file type list related to the specified attribute resource, respectively, to obtain the comparison result. The comparison result is used to indicate whether the file path list contains the submission file path and whether the file type list contains the submission file type. The comparison result determines whether the submission information involves related information files of the specified attribute resource in the first resource.

[0043] In this embodiment, for specified attribute resources of different file types, a file path list and a file type list related to the specified attribute resources are pre-defined. When determining the relevant information files of the specified attribute resources, the file path list and the file type list are compared and traversed to determine whether the file path list contains the submission file path and the file type list contains the submission file type. If the file path list contains the submission file path or the file type list contains the submission file type, it is determined that the submission information involves the relevant information files of the specified attribute resources in the first resource. If the file path list does not contain the submission file path and the file type list does not contain the submission file type, it is determined that the submission information does not involve the relevant information files of the specified attribute resources in the first resource, and the change submission instruction is directly filtered out without further operation. Using the above example as an illustration, the .sfxmusic file may only exist in certain file paths. For example, the .sfxmusic file may exist in the / test / fx / path, but not in the / test / gui / path. Therefore, the / test / fx / path can be preset in the file path list. In this way, all change commit commands under the / test / fx / path will be identified as related information files involving the resource with the specified attribute in the first resource, while all change commit commands under the / test / gui / path will be directly filtered out, thereby improving the efficiency of resource synchronization change identification and the timeliness of synchronization.

[0044] (2) If the submitted information involves related information files of the specified attribute resource in the first resource, then determine whether the submitted information involves changes to the specified attribute resource in the first resource by checking the historical versions of the first resource.

[0045] In this step, if the submitted information involves information files related to a specified attribute resource in the first resource, it indicates that the information files related to the specified attribute resource have been changed. The change submission instruction may affect the appearance of the specified attribute resource in the first resource. However, since a change in the information files related to the specified attribute resource does not necessarily mean that the specified attribute resource has been changed, the historical versions of the first resource are used to further determine whether the submitted information involves changes to the specified attribute resource in the first resource. Specifically, the method for determining changes to a specified attribute resource is divided into two parts: one part is the determination of changes directly related to the specified attribute resource, and the other part is the determination of changes indirectly related to the specified attribute resource. It can be understood that changes directly related to the specified attribute resource can be changes to the display attributes of the specified attribute resource, such as changing the attachment position of an audio file in an art resource, or changing the continuous frame rate of a virtual animated character resource in an animation scene resource. Changes directly related to the specified attribute resource will directly change the display form of the specified attribute resource in the first resource. Changes indirectly related to the specified attribute resource can be changes to the first resource or changes to the display attributes of the specified attribute resource. For example, changing a node of a scene animation resource may affect the display form of a virtual animated character resource attached to that node, or changing the attachment point of an art resource may affect the display form of an audio file attached to that attachment point.

[0046] Based on the above, step (2) includes: obtaining resource difference information by acquiring the differences between the current version submitted by the change submission command and the historical version through the historical versions of the first resource; determining whether the submission information involves direct or indirect changes to the specified attribute resources in the first resource through the resource difference information; it can be understood that responding to the change submission command of the first resource triggers the submission of the first resource and determines the current version of the first resource. Therefore, the current version refers to the version of the first resource submitted by the change submission command. By comparing the current version of the first resource with the historical version, resource difference information is obtained. In one embodiment, the differences between the current version submitted by the change submission command and the historical version are extracted through the version control system's difference extraction command (such as the SVN diff command) to obtain resource difference information, which can quickly and accurately extract difference information. After obtaining the resource difference information, it is determined whether the submitted information involves direct or indirect changes to the specified attribute resource in the first resource. This determines whether the submission of the first resource is a change directly or indirectly related to the specified attribute resource. If the submitted information involves direct or indirect changes to the specified attribute resource in the first resource, the triggering account of the change submission instruction is then determined to match the specified attribute resource. That is, if the submitted information involves changes to the specified attribute resource in the first resource, the triggering account of the change submission instruction is determined to match the specified attribute resource. This includes: if the submitted information involves direct or indirect changes to the specified attribute resource in the first resource, the triggering account of the change submission instruction is determined to match the specified attribute resource. If the submitted information does not involve direct or indirect changes to the specified attribute resource in the first resource, the change submission instruction is directly filtered out, and no further processing is performed.

[0047] Furthermore, the method for determining whether a specified attribute resource has been directly or indirectly altered is explained. It is understood that the methods for determining direct and indirect alterations can be performed simultaneously or sequentially. Specifically, the above method for determining whether the submitted information involves a direct or indirect alteration of the specified attribute resource in the first resource using resource difference information includes the following steps:

[0048] a. Use a pre-defined list of keywords related to specified attribute resources to perform keyword detection on resource difference information to determine whether the submitted information involves direct changes to the specified attribute resources in the first resource;

[0049] b. By using a pre-defined list of indirect change behaviors for specified attribute resources, detect indirect change behaviors of resource difference information to determine whether the submitted information involves indirect changes to specified attribute resources in the first resource.

[0050] Understandably, since direct changes to a specified attribute resource typically modify its attributes, comparing a pre-defined keyword list for the specified attribute resource with the resource difference information determines whether the resource difference information contains any keyword from the attribute keyword list. If the resource difference information contains any keyword from the attribute keyword list, then the submission information involves a direct change to the specified attribute resource in the first resource. Specifically, the keyword list must contain at least one attribute keyword of the specified attribute resource. These attribute keywords can be keywords related to the presentation attributes, without further limitation. For example, assuming the specified attribute resource is an audio file, the keyword list could contain audio-related keywords such as "sound," ".bnk," and "delay," without further limitation. Regarding indirect changes to a specified attribute resource, although these do not directly alter the presentation attributes, they still affect its presentation in the first resource. Therefore, for indirect changes to a specified attribute resource, a resource change notification should be sent promptly to remind relevant personnel to check whether the change submission command for the first resource requires a synchronized change to the specified attribute resource.

[0051] As an example, and not a limitation, when the first resource is an art resource and the specified attribute resource in the first resource is an audio resource, the list of indirect modification behaviors for the specified attribute resource includes, but is not limited to, changes to the audio resource attachment point, changes to the frame animation length of the art resource, significant deletions or modifications to the art resource causing line number offsets in the audio resource information of the art resource, and art resource replacement or overwriting. Although these operations do not directly modify the audio resource, they may indirectly affect the presentation and effect of the audio resource in the art resource. Therefore, based on the first resource and the specified attribute resource (such as art resource - audio resource) of different file types, a list of indirect modification behaviors for the specified attribute resource is pre-defined. During step b, the resource difference information is compared with the pre-defined list of indirect modification behaviors to detect whether the resource difference information contains any indirect modification behavior in the list of indirect modification behaviors. If the resource difference information contains any indirect modification behavior in the list of indirect modification behaviors, it is determined that the submitted information involves indirect modification of the specified attribute resource in the first resource. If the resource difference information does not contain any indirect modification behavior in the list of indirect modification behaviors, it is determined that the submitted information does not involve indirect modification of the specified attribute resource in the first resource. Specifically, step b above includes: determining whether the resource difference information contains any indirect change behavior in the indirect change behavior list by using a preset list of indirect change behaviors for specified attribute resources; if the resource difference information contains any indirect change behavior in the indirect change behavior list, then determining that the submitted information involves indirect changes to the specified attribute resources in the first resource.

[0052] In one implementation, to further improve the efficiency of determining changes to specified attribute resources, the direct change determination method for specified attribute resources is further limited. Specifically, the keyword list includes a first keyword list and a second keyword list; the relevance between the keywords in the first keyword list and the specified attribute resource is greater than the relevance between the keywords in the second keyword list and the specified attribute resource; step a above includes: detecting whether the resource difference information contains any first keyword from the first keyword list, and detecting whether the resource difference information contains any second keyword from the second keyword list; if the resource difference information contains any first keyword from the first keyword list, or if the resource difference information contains any second keyword from the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword from the first keyword list, then it is determined that the submitted information involves a direct change to the specified attribute resource in the first resource.

[0053] In this embodiment, certain file types have unique keywords for their specified attribute resources. For example, if the specified attribute resource is an audio file, then the unique keywords for audio resource files include "sound" and ".bnk". Therefore, the unique keywords for the specified attribute resource are set as the first keyword list. If the resource difference information contains any of the first keywords in the first keyword list, then it can be determined that the submission information involves a direct change to the specified attribute resource in the first resource. For keywords specific to file types that are not designated attribute resources, a second keyword list is set. These keywords can be keywords for designated attribute resources, keywords for the first resource, or keywords for other resources. For example, assuming the first resource is an art resource and the designated attribute resource is an audio resource, keywords such as "delay" and "event" can be keywords for both audio and art resources. If the resource difference information contains any second keyword from the second keyword list, it cannot be directly determined whether the submission information involves a direct change to the designated attribute resource in the first resource. It is also necessary to consider whether the module containing the second keyword contains any first keyword from the first keyword list. Only if the resource difference information contains any second keyword from the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword from the first keyword list, can it be determined that the submission information involves a direct change to the designated attribute resource in the first resource.

[0054] Based on the above, the module containing the second keyword is identified according to the preset module separator, such as curly braces {}, square brackets [], indentation symbols, etc. By performing context detection on the second keyword, the module containing the second keyword is determined, and the module containing the second keyword is subjected to first keyword detection to determine whether the module containing the second keyword in the resource difference information contains any first keyword in the first keyword list, thereby determining that the submitted information involves a direct change of the specified attribute resource in the first resource.

[0055] For the corresponding method embodiments described above, see [link to relevant documentation]. Figure 2 The diagram illustrates a resource change notification device, which includes: an acquisition module 20, configured to acquire submission information of the first resource in response to a change submission instruction for the first resource; a determination module 22, configured to determine, based on the submission information and / or historical versions of the first resource, whether the submission information involves a change to a specified attribute resource in the first resource; a matching module 24, configured to determine, if the submission information involves a change to a specified attribute resource in the first resource, whether the triggering account of the change submission instruction matches the specified attribute resource; and a sending module 26, configured to send a resource change notification to the account that matches the specified attribute resource if the triggering account of the change submission instruction does not match the specified attribute resource.

[0056] The aforementioned resource change notification device responds to a change submission command for a first resource and obtains the submission information of the first resource. Based on the submission information and / or the historical version of the first resource, it determines whether the submission information involves a change to a specified attribute resource within the first resource. If the submission information involves a change to a specified attribute resource within the first resource, it determines whether the triggering account of the change submission command matches the specified attribute resource. If the triggering account of the change submission command does not match the specified attribute resource, a resource change notification is sent to the account that matches the specified attribute resource. In this method, when a change is submitted for the first resource, it determines whether the change involves a change to a specified attribute resource based on the submission information and historical version. If the change involves a change to a specified attribute resource, and the change was not triggered by an account that matches the specified attribute resource, a change notification is sent to the account that matches the specified attribute resource, enabling that account to promptly synchronize resource changes, thereby improving the timeliness of resource synchronization.

[0057] The aforementioned determining module is also used to: determine whether the submitted information involves related information files of the specified attribute resource in the first resource; if the submitted information involves related information files of the specified attribute resource in the first resource, then determine whether the submitted information involves changes to the specified attribute resource in the first resource through the historical versions of the first resource.

[0058] The aforementioned submission information includes the submission file path and the submission file type; the aforementioned determination module is further configured to: compare the submission file path and the submission file type with a preset list of file paths and a list of file types related to the specified attribute resource, respectively, to obtain a comparison result; the comparison result is used to indicate whether the file path list contains the submission file path and whether the file type list contains the submission file type; and determine whether the submission information involves the relevant information file of the specified attribute resource in the first resource based on the comparison result.

[0059] The aforementioned determining module is further configured to: obtain the differences between the current version and the historical version submitted by the change submission instruction through the historical versions of the first resource, and obtain resource difference information; determine whether the submission information involves direct or indirect changes to the specified attribute resource in the first resource through the resource difference information; the aforementioned matching module is further configured to: if the submission information involves direct or indirect changes to the specified attribute resource in the first resource, determine whether the triggering account of the change submission instruction matches the specified attribute resource.

[0060] The aforementioned determining module is further configured to: perform keyword detection on resource difference information using a preset list of keywords related to specified attribute resources, and determine whether the submitted information involves direct changes to the specified attribute resources in the first resource; and perform indirect change behavior detection on resource difference information using a preset list of indirect change behaviors for specified attribute resources, and determine whether the submitted information involves indirect changes to the specified attribute resources in the first resource.

[0061] The aforementioned keyword list includes a first keyword list and a second keyword list; the relevance of keywords in the first keyword list to the specified attribute resource is greater than the relevance of keywords in the second keyword list to the specified attribute resource; the aforementioned determining module is further configured to: detect whether the resource difference information contains any first keyword from the first keyword list, and detect whether the resource difference information contains any second keyword from the second keyword list; if the resource difference information contains any first keyword from the first keyword list, or if the resource difference information contains any second keyword from the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword from the first keyword list, then it is determined that the submitted information involves a direct change to the specified attribute resource in the first resource.

[0062] The aforementioned determining module is further configured to: determine whether the resource difference information contains any indirect change behavior in the indirect change behavior list by using a preset list of indirect change behaviors for specified attribute resources; if the resource difference information contains any indirect change behavior in the indirect change behavior list, then determine that the submitted information involves indirect changes to the specified attribute resources in the first resource.

[0063] The aforementioned acquisition module is also used to: respond to the triggering of a resource submission event in the resource repository, and obtain the submission information of the first resource through the resource submission event.

[0064] The matching module described above is further configured to: obtain a list of specified submission accounts for a specified attribute resource, and determine whether the list of specified submission accounts contains the triggering account for the change submission instruction; if the list of specified submission accounts contains the triggering account for the change submission instruction, then determine that the triggering account for the change submission instruction matches the specified attribute resource; if the list of specified submission accounts does not contain the triggering account for the change submission instruction, then determine that the triggering account for the change submission instruction does not match the specified attribute resource.

[0065] The aforementioned sending module is also used to: generate resource change information for a specified attribute resource, and send a resource change notification containing the resource change information to the account matching the specified attribute resource.

[0066] This embodiment also provides an electronic device, including a processor and a memory. The memory stores machine-executable instructions that can be executed by the processor. The processor executes the machine-executable instructions to implement the aforementioned resource change notification method. This electronic device can be a server or a terminal device.

[0067] See Figure 3 As shown, the electronic device includes a processor 100 and a memory 101. The memory 101 stores machine-executable instructions that can be executed by the processor 100. The processor 100 executes the machine-executable instructions to implement the above-mentioned resource change notification method.

[0068] Furthermore, Figure 3 The electronic device shown also includes a bus 102 and a communication interface 103, with the processor 100, the communication interface 103 and the memory 101 connected via the bus 102.

[0069] The memory 101 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 103 (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network. The bus 102 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0070] Processor 100 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 100 or by instructions in software form. Processor 100 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a readily available storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 101. The processor 100 reads information from memory 101 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments, for example:

[0071] In response to the change submission instruction for the first resource, obtain the submission information of the first resource; based on the submission information and / or the historical version of the first resource, determine whether the submission information involves changes to a specified attribute resource in the first resource; if the submission information involves changes to a specified attribute resource in the first resource, determine whether the triggering account of the change submission instruction matches the specified attribute resource; if the triggering account of the change submission instruction does not match the specified attribute resource, send a resource change reminder to the account that matches the specified attribute resource.

[0072] The resource change notification electronic device provided in the above embodiments determines whether the change of the first resource involves a change of a specified attribute resource based on the submission information and historical versions when the first resource is submitted for change. If the change of the first resource involves a change of a specified attribute resource, and the change of the first resource is not triggered by an account matching the specified attribute resource, a change notification is sent to the account matching the specified attribute resource so that the account can promptly synchronize the resource change, thereby improving the timeliness of resource synchronization.

[0073] The above determination of whether the submitted information involves changes to the specified attribute resource in the first resource based on the submitted information and / or the historical version of the first resource includes: determining whether the submitted information involves the relevant information file of the specified attribute resource in the first resource; if the submitted information involves the relevant information file of the specified attribute resource in the first resource, then determining whether the submitted information involves changes to the specified attribute resource in the first resource through the historical version of the first resource.

[0074] The aforementioned submission information includes the submission file path and the submission file type; determining whether the submission information involves relevant information files of the specified attribute resource in the first resource includes: comparing the submission file path and the submission file type with a preset list of file paths and a list of file types related to the specified attribute resource, respectively, to obtain a comparison result; the comparison result is used to indicate whether the file path list contains the submission file path and whether the file type list contains the submission file type; and determining whether the submission information involves relevant information files of the specified attribute resource in the first resource based on the comparison result.

[0075] The aforementioned determination of whether the submitted information involves changes to a specified attribute resource in the first resource through historical versions of the first resource includes: obtaining resource difference information by acquiring the differences between the current version submitted with the change submission instruction and historical versions through historical versions of the first resource; determining whether the submitted information involves direct or indirect changes to a specified attribute resource in the first resource through the resource difference information; and determining whether the triggering account of the change submission instruction matches the specified attribute resource if the submitted information involves changes to a specified attribute resource in the first resource, including: determining whether the triggering account of the change submission instruction matches the specified attribute resource if the submitted information involves direct or indirect changes to a specified attribute resource in the first resource.

[0076] The aforementioned method of determining whether submitted information involves direct or indirect changes to a specified attribute resource in the first resource through resource difference information includes: performing keyword detection on resource difference information using a preset keyword list related to the specified attribute resource to determine whether submitted information involves direct changes to a specified attribute resource in the first resource; and performing indirect change behavior detection on resource difference information using a preset list of indirect change behaviors for the specified attribute resource to determine whether submitted information involves indirect changes to a specified attribute resource in the first resource.

[0077] The aforementioned keyword list includes a first keyword list and a second keyword list; the relevance of keywords in the first keyword list to the specified attribute resource is greater than the relevance of keywords in the second keyword list to the specified attribute resource; the aforementioned keyword detection of resource difference information using a preset keyword list related to the specified attribute resource to determine whether the submitted information involves a direct change to the specified attribute resource in the first resource includes: detecting whether the resource difference information contains any first keyword in the first keyword list, and detecting whether the resource difference information contains any second keyword in the second keyword list; if the resource difference information contains any first keyword in the first keyword list, or, if the resource difference information contains any second keyword in the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword in the first keyword list, then it is determined that the submitted information involves a direct change to the specified attribute resource in the first resource.

[0078] The above-mentioned method uses a pre-defined list of indirect modification behaviors for specified attribute resources to detect indirect modification behaviors of resource difference information and determine whether the submitted information involves indirect modification of specified attribute resources in the first resource. This includes: determining whether the resource difference information contains any indirect modification behavior in the pre-defined list of indirect modification behaviors for specified attribute resources; if the resource difference information contains any indirect modification behavior in the pre-defined list of indirect modification behaviors, then it is determined that the submitted information involves indirect modification of specified attribute resources in the first resource.

[0079] The above-mentioned response to the change submission instruction of the first resource and the acquisition of the submission information of the first resource include: responding to the triggering of the resource submission event of the resource repository and acquiring the submission information of the first resource through the resource submission event.

[0080] The process of determining whether the triggering account for the change submission instruction matches the specified attribute resource includes: obtaining a list of specified submission accounts for the specified attribute resource, and determining whether the list of specified submission accounts contains the triggering account for the change submission instruction; if the list of specified submission accounts contains the triggering account for the change submission instruction, then the triggering account for the change submission instruction matches the specified attribute resource; if the list of specified submission accounts does not contain the triggering account for the change submission instruction, then the triggering account for the change submission instruction does not match the specified attribute resource.

[0081] Sending resource change notifications to accounts matching the specified attribute resources includes: generating resource change information for the specified attribute resources and sending resource change notifications containing the resource change information to accounts matching the specified attribute resources.

[0082] This embodiment also provides a machine-readable storage medium storing machine-executable instructions. When these machine-executable instructions are invoked and executed by a processor, they cause the processor to implement the aforementioned resource change notification method, for example:

[0083] In response to the change submission instruction for the first resource, obtain the submission information of the first resource; based on the submission information and / or the historical version of the first resource, determine whether the submission information involves changes to a specified attribute resource in the first resource; if the submission information involves changes to a specified attribute resource in the first resource, determine whether the triggering account of the change submission instruction matches the specified attribute resource; if the triggering account of the change submission instruction does not match the specified attribute resource, send a resource change reminder to the account that matches the specified attribute resource.

[0084] The resource change notification storage medium provided in the above embodiments determines whether the change of the first resource involves a change of a specified attribute resource based on the submission information and historical versions when the first resource is submitted for change. If the change of the first resource involves a change of a specified attribute resource, and the change of the first resource is not triggered by an account matching the specified attribute resource, then a change notification is sent to the account matching the specified attribute resource so that the account can promptly synchronize the resource changes, thereby improving the timeliness of resource synchronization.

[0085] The above determination of whether the submitted information involves changes to the specified attribute resource in the first resource based on the submitted information and / or the historical version of the first resource includes: determining whether the submitted information involves the relevant information file of the specified attribute resource in the first resource; if the submitted information involves the relevant information file of the specified attribute resource in the first resource, then determining whether the submitted information involves changes to the specified attribute resource in the first resource through the historical version of the first resource.

[0086] The aforementioned submission information includes the submission file path and the submission file type; determining whether the submission information involves relevant information files of the specified attribute resource in the first resource includes: comparing the submission file path and the submission file type with a preset list of file paths and a list of file types related to the specified attribute resource, respectively, to obtain a comparison result; the comparison result is used to indicate whether the file path list contains the submission file path and whether the file type list contains the submission file type; and determining whether the submission information involves relevant information files of the specified attribute resource in the first resource based on the comparison result.

[0087] The aforementioned determination of whether the submitted information involves changes to a specified attribute resource in the first resource through historical versions of the first resource includes: obtaining resource difference information by acquiring the differences between the current version submitted with the change submission instruction and historical versions through historical versions of the first resource; determining whether the submitted information involves direct or indirect changes to a specified attribute resource in the first resource through the resource difference information; and determining whether the triggering account of the change submission instruction matches the specified attribute resource if the submitted information involves changes to a specified attribute resource in the first resource, including: determining whether the triggering account of the change submission instruction matches the specified attribute resource if the submitted information involves direct or indirect changes to a specified attribute resource in the first resource.

[0088] The aforementioned method of determining whether submitted information involves direct or indirect changes to a specified attribute resource in the first resource through resource difference information includes: performing keyword detection on resource difference information using a preset keyword list related to the specified attribute resource to determine whether submitted information involves direct changes to a specified attribute resource in the first resource; and performing indirect change behavior detection on resource difference information using a preset list of indirect change behaviors for the specified attribute resource to determine whether submitted information involves indirect changes to a specified attribute resource in the first resource.

[0089] The aforementioned keyword list includes a first keyword list and a second keyword list; the relevance of keywords in the first keyword list to the specified attribute resource is greater than the relevance of keywords in the second keyword list to the specified attribute resource; the aforementioned keyword detection of resource difference information using a preset keyword list related to the specified attribute resource to determine whether the submitted information involves a direct change to the specified attribute resource in the first resource includes: detecting whether the resource difference information contains any first keyword in the first keyword list, and detecting whether the resource difference information contains any second keyword in the second keyword list; if the resource difference information contains any first keyword in the first keyword list, or, if the resource difference information contains any second keyword in the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword in the first keyword list, then it is determined that the submitted information involves a direct change to the specified attribute resource in the first resource.

[0090] The above-mentioned method uses a pre-defined list of indirect modification behaviors for specified attribute resources to detect indirect modification behaviors of resource difference information and determine whether the submitted information involves indirect modification of specified attribute resources in the first resource. This includes: determining whether the resource difference information contains any indirect modification behavior in the pre-defined list of indirect modification behaviors for specified attribute resources; if the resource difference information contains any indirect modification behavior in the pre-defined list of indirect modification behaviors, then it is determined that the submitted information involves indirect modification of specified attribute resources in the first resource.

[0091] The above-mentioned response to the change submission instruction of the first resource and the acquisition of the submission information of the first resource include: responding to the triggering of the resource submission event of the resource repository and acquiring the submission information of the first resource through the resource submission event.

[0092] The process of determining whether the triggering account for the change submission instruction matches the specified attribute resource includes: obtaining a list of specified submission accounts for the specified attribute resource, and determining whether the list of specified submission accounts contains the triggering account for the change submission instruction; if the list of specified submission accounts contains the triggering account for the change submission instruction, then the triggering account for the change submission instruction matches the specified attribute resource; if the list of specified submission accounts does not contain the triggering account for the change submission instruction, then the triggering account for the change submission instruction does not match the specified attribute resource.

[0093] Sending resource change notifications to accounts matching the specified attribute resources includes: generating resource change information for the specified attribute resources and sending resource change notifications containing the resource change information to accounts matching the specified attribute resources.

[0094] The resource change notification method, apparatus, electronic device, and storage medium computer program product provided in the embodiments of the present invention include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0095] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0096] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0097] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0098] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0099] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for notifying users of resource changes, characterized in that, The method includes: Responding to the change submission command of the first resource, obtain the submission information of the first resource; Based on the submission information and / or the historical version of the first resource, determine whether the submission information involves a change to a specified attribute resource in the first resource; the change includes a change to the presentation attribute of the specified attribute resource, the presentation attribute being used to indicate the presentation form of the specified attribute resource in the first resource; If the submitted information involves a change to a resource with a specified attribute in the first resource, determine whether the account that triggered the change submission instruction matches the resource with the specified attribute. If the account that triggers the change submission instruction does not match the specified attribute resource, a resource change reminder is sent to the account that matches the specified attribute resource; The step of determining whether the submission information involves changes to a specified attribute resource in the first resource based on the submission information and / or the historical version of the first resource includes: Determine whether the submitted information involves information files related to the specified attribute resource in the first resource; If the submission information involves information files related to a specified attribute resource in the first resource, then the historical versions of the first resource are used to determine whether the submission information involves changes to the specified attribute resource in the first resource; The step of determining whether the submission information involves changes to a specified attribute resource in the first resource by using historical versions of the first resource includes: By using the historical versions of the first resource, the differences between the current version submitted by the change submission instruction and the historical version are obtained, and resource difference information is obtained. The resource difference information is used to determine whether the submitted information involves direct or indirect changes to the specified attribute resource in the first resource; wherein, the direct change is determined by keyword detection, and the indirect change is determined by indirect change behavior detection. If the submitted information involves a change to a specified attribute resource in the first resource, determining whether the account that triggered the change submission instruction matches the specified attribute resource includes: If the submitted information involves a direct or indirect change to a specified attribute resource in the first resource, determine whether the account that triggered the change submission instruction matches the specified attribute resource.

2. The method according to claim 1, characterized in that, The submission information includes the submission file path and the submission file type; determining whether the submission information involves information files related to the specified attribute resource in the first resource includes: The submitted file path and the submitted file type are compared with a preset list of file paths and a list of file types related to the specified attribute resource, respectively, to obtain a comparison result; the comparison result is used to indicate whether the list of file paths contains the submitted file path and whether the list of file types contains the submitted file type. The comparison results are used to determine whether the submitted information involves information files related to the specified attribute resource in the first resource.

3. The method according to claim 1, characterized in that, The step of determining whether the submitted information involves a direct or indirect change to a specified attribute resource in the first resource through the resource difference information includes: By using a pre-defined list of keywords related to the specified attribute resources, keyword detection is performed on the resource difference information to determine whether the submitted information involves a direct change to the specified attribute resources in the first resource. By using a pre-defined list of indirect change behaviors for the specified attribute resources, indirect change behavior detection is performed on the resource difference information to determine whether the submitted information involves indirect changes to the specified attribute resources in the first resource.

4. The method according to claim 3, characterized in that, The keyword list includes a first keyword list and a second keyword list; the keywords in the first keyword list are more relevant to the specified attribute resource than the keywords in the second keyword list are. The step of performing keyword detection on the resource difference information using a preset keyword list related to the specified attribute resource to determine whether the submitted information involves a direct change to the specified attribute resource in the first resource includes: Detect whether the resource difference information contains any first keyword from the first keyword list, and detect whether the resource difference information contains any second keyword from the second keyword list; If the resource difference information contains any first keyword from the first keyword list, or if the resource difference information contains any second keyword from the second keyword list, and the module containing the second keyword in the resource difference information contains any first keyword from the first keyword list, then it is determined that the submission information involves a direct change to a specified attribute resource in the first resource.

5. The method according to claim 3, characterized in that, The step of detecting indirect change behaviors of resource difference information by using a preset list of indirect change behaviors for the specified attribute resources, and determining whether the submitted information involves indirect changes to the specified attribute resources in the first resource, includes: By using a pre-defined list of indirect change behaviors for the specified attribute resource, determine whether the resource difference information contains any indirect change behavior from the list of indirect change behaviors. If the resource difference information contains any indirect change behavior from the list of indirect change behaviors, then the submission information is determined to involve an indirect change to a specified attribute resource in the first resource.

6. The method according to claim 1, characterized in that, The step of responding to the change submission instruction for the first resource and obtaining the submission information of the first resource includes: In response to the triggering of a resource commit event in the resource repository, the commit information of the first resource is obtained through the resource commit event.

7. The method according to claim 1, characterized in that, Determining whether the account that triggered the change submission instruction matches the specified attribute resource includes: Obtain a list of specified submitting accounts for the specified attribute resource, and determine whether the list of specified submitting accounts contains the account that triggered the change submission instruction; If the list of specified submitting accounts contains the triggering account of the change submitting instruction, then it is determined that the triggering account of the change submitting instruction matches the specified attribute resource; If the list of specified submission accounts does not contain the triggering account for the change submission instruction, then it is determined that the triggering account for the change submission instruction does not match the specified attribute resource.

8. The method according to claim 1, characterized in that, Sending resource change notifications to accounts matching the specified attribute resources includes: Generate resource change information for the specified attribute resource and send a resource change notification containing the resource change information to the account matching the specified attribute resource.

9. A resource change notification device, characterized in that, The device includes: The acquisition module is used to respond to the change submission command of the first resource and acquire the submission information of the first resource; The determination module is configured to determine, based on the submission information and / or the historical version of the first resource, whether the submission information involves a change to a specified attribute resource in the first resource; the change includes a change to the performance attribute of the specified attribute resource, the performance attribute being used to indicate the performance form of the specified attribute resource in the first resource; The matching module is used to determine whether the account that triggered the change submission instruction matches the specified attribute resource if the submission information involves a change to the specified attribute resource in the first resource. The sending module is used to send a resource change reminder to the account that matches the specified attribute resource if the account that triggered the change submission instruction does not match the specified attribute resource. The determining module is further configured to: determine whether the submitted information involves related information files of a specified attribute resource in the first resource; if the submitted information involves related information files of a specified attribute resource in the first resource, determine whether the submitted information involves changes to the specified attribute resource in the first resource through historical versions of the first resource; The determining module is further configured to: obtain the difference between the current version submitted by the change submission instruction and the historical version through the historical version of the first resource, and obtain resource difference information; The resource difference information is used to determine whether the submitted information involves direct or indirect changes to the specified attribute resource in the first resource; wherein, the direct change is determined by keyword detection, and the indirect change is determined by indirect change behavior detection. The matching module is further configured to: if the submitted information involves a direct or indirect change to a specified attribute resource in the first resource, determine whether the account that triggered the change submission instruction matches the specified attribute resource.

10. An electronic device, characterized in that, The system includes a processor and a memory, the memory storing machine-executable instructions that can be executed by the processor, the processor executing the machine-executable instructions to implement the resource change notification method according to any one of claims 1-8.

11. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores machine-executable instructions, which, when invoked and executed by a processor, cause the processor to implement the resource change notification method according to any one of claims 1-8.

Images