Multi-level activity management method and device, equipment and storage medium

Abstract

The invention discloses a multi-level activity management method and device, equipment and a storage medium. The method comprises the steps that a main platform creates an activity and generates a first token about the activity; each primary platform obtains a first token of the main platform; the first-level platform analyzes the first token, extracts a version number, a token code and a domain name of the activity platform, splices an interface URL based on an agreed path of the domain name of the activity platform, and initiates an activity information request to a corresponding platform by carrying the version number and the token code; the target platform verifies the legality of the token code sent by the primary platform, inquires corresponding activity information based on the token code and returns activity information data according to a format specified by a version number; the first-level platform creates a first-level activity based on the returned activity information data, recycles and processes first-level activity data, and generates data of the first-level activity; the primary platform uploads the data to the main platform; and the main platform receives and stores the data. According to the method, the workload of a platform administrator can be greatly reduced, and the expansibility is better.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically, to a multi-level activity management method, apparatus, device, and storage medium. Background Technology

[0002] In daily operations, there are often needs to expand activities at multiple levels. Previously, the solutions were either to maintain a hierarchy of platform modules, with data from both levels residing in the same database (restricting access to only the current platform), and to create activities for a specific lower-level platform when configuring the main activity; or for lower-level platform administrators to manually create activities based on the main platform's activity information, select outstanding entries, and since neither the upper nor lower-level platforms supported directly pushing entry data to a specific activity, the selected entries had to be submitted to the main platform for final review. This entire process required significant manual work from platform administrators and lacked scalability. Summary of the Invention

[0003] To overcome the shortcomings of the prior art, which requires manual processing by platform administrators, resulting in a large workload and poor scalability, this invention provides a multi-level activity management method, device, equipment, and storage medium. The technical solution adopted by this invention is as follows.

[0004] In a first aspect, the present invention provides a multi-level activity management method, comprising:

[0005] The main platform creates an activity and generates a first token for the activity, which includes: the domain name of the platform conducting the activity, the version number, and the token code; the version number is used to manage the data return format.

[0006] Each primary platform obtains the first token from the main platform; wherein, the primary platform is the platform that needs to participate in the activity;

[0007] The first-level platform parses the first token, extracts the version number, token code, and domain name of the platform where the activity is being carried out, and concatenates the interface URL based on the agreed path of the domain name of the platform where the activity is being carried out. It then sends an activity information request to the corresponding platform carrying the version number and token code. This corresponding platform is the target platform.

[0008] The target platform verifies the validity of the token code sent by the primary platform, queries the corresponding activity information based on the token code, and returns the activity information data in the format specified by the version number.

[0009] The primary platform creates primary activities based on the returned activity information data, collects and processes primary activity data, and generates primary activity data.

[0010] The primary platform uploads the data of the primary activities to the main platform;

[0011] The main platform receives data uploaded from each primary activity, uses different parsing logic based on the version number, and then stores the received data into the database.

[0012] In one implementation, the process by which the primary platform creates a primary activity based on the returned activity information data includes:

[0013] The primary platform selects a data return format that can run on its own platform from the returned activity information data;

[0014] Create a first-level activity based on the selected data return format.

[0015] In one embodiment, the multi-level activity management method further includes:

[0016] The first-level platform generates a second token for the first-level activity. The second token includes: the domain name, version number, and token code of the platform conducting the first-level activity. The version number and token code contained in the second token are the same as those in the first token.

[0017] Each secondary platform obtains a second token from the primary platform;

[0018] The secondary platform parses the second token, extracts the version number, token code, and domain name of the platform conducting the primary activity, and constructs the interface URL based on the agreed path of the domain name of the platform conducting the primary activity. It then sends an activity information request to the corresponding platform, carrying the version number and token code. This corresponding platform is the target platform for the primary activity.

[0019] The primary activity target platform verifies the validity of the token code sent by the secondary platform, queries the corresponding activity information, and returns the activity information data in the format specified by the version number.

[0020] The secondary platform creates secondary activities based on the returned activity information data, collects and processes the secondary activity data, and generates secondary activity data.

[0021] The secondary platform uploads the data of the secondary activities to the primary platform, and the primary platform uploads the data received from each secondary activity to the main platform.

[0022] In one implementation, the process by which the secondary platform creates a secondary activity based on the returned activity information data includes:

[0023] The secondary platform selects a data return format that can run on its own platform from the returned activity information data;

[0024] Create a secondary activity based on the selected data return format.

[0025] In one implementation, the version number includes: a first version number, a second version number, and / or a third version number;

[0026] The first version number corresponds to JSON format data;

[0027] The second version number corresponds to XML format data;

[0028] The third version number is a customized version number, which needs to be matched with a specific token code to return extended information.

[0029] In one implementation, the version number includes: a third version number, which is a customized version number that needs to be matched with a specific token code to return extended information;

[0030] The process by which the target platform verifies the validity of the token code sent by the primary platform includes:

[0031] When the version number is the third version number, verify whether the token conforms to a specific format;

[0032] If the request does not conform to the specific format, it is deemed an invalid request.

[0033] A request is considered valid if it conforms to a specific format.

[0034] In one implementation, the process by which the primary platform parses the first token and extracts the version number, token code, and domain name of the platform conducting the activity includes:

[0035] The first-level platform calls the agreed API interface 1 to obtain the activity credential, wherein the activity credential is an encrypted string;

[0036] The activity credentials are parsed to obtain information, and then the agreed API interface 2 is called to extract the version number, token code, and domain name of the platform where the activity is conducted.

[0037] Secondly, the present invention provides a multi-level activity management device, comprising: a main platform, a primary platform, and a target platform;

[0038] The main platform is used to create activities and generate a first token for the activity. The first token includes: the domain name of the platform where the activity is conducted, the version number, and the token code; the version number is used to manage the data return format.

[0039] The primary platform is used to obtain the first token from the main platform, parse the first token, extract the version number, token code, and domain name of the platform where the activity is being carried out, construct the interface URL based on the agreed path of the domain name of the platform where the activity is being carried out, and send an activity information request to the corresponding platform carrying the version number and token code. The corresponding platform is the target platform. The primary platform is the platform that needs to participate in the activity.

[0040] The target platform is used to verify the validity of the token code sent by the primary platform, query the corresponding activity information based on the token code, and return the activity information data in the format specified by the version number;

[0041] The primary platform is also used to create primary activities based on the returned activity information data, collect and process primary activity data, generate primary activity data, and upload primary activity data to the main platform.

[0042] The main platform is also used to receive data uploaded from various primary activities, and uses different parsing logic based on the version number to store the received data in the database.

[0043] Thirdly, the present invention provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method of any of the above embodiments.

[0044] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, characterized in that the program, when executed by a processor, implements the method of any of the above embodiments.

[0045] This invention, based on the concept of activity tokens, facilitates more convenient promotion of lower-level activities and supports scenarios where lower-level activities push their work to target platforms. The token contains information such as the platform address, version number, and token number. The version number and token number settings allow for multi-language support and customization. Furthermore, the token number is a unique identifier for the activity, enabling the retrieval of specific activities. Customized tokens (matching customized version numbers) are supported, and the version number manages the data return format and content. This invention significantly reduces the workload of platform administrators, offers better scalability (eliminating the need to maintain configurations for upper and lower-level platforms on the current platform), supports multi-scenario activity promotion, and can directly perform a series of tasks such as activity copying and activity work pushing through the program. While reducing the workload of platform administrators, it also ensures data integrity, achieves more efficient data flow, and better supports activity business promotion. Attached Figure Description

[0046] Figure 1 This is a flowchart illustrating one of the embodiments of the present invention.

[0047] Figure 2 This is a timing diagram of one of the embodiments of the present invention.

[0048] Figure 3 This is a timing diagram of another embodiment of the present invention. Detailed Implementation

[0049] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0050] It should be noted that the terms "first, second, ..." used in the embodiments of the present invention are merely used to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, ..." can be interchanged in a specific order or sequence where permissible. It should be understood that the objects distinguished by "first, second, ..." can be interchanged where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein.

[0051] Example 1

[0052] Please see Figure 1 , Figure 1 This is a flowchart illustrating a multi-level activity management method according to Embodiment 1 of the present invention, including steps S110, S120, S130, S140, S150, S160, and S170. It should be noted that steps S110, S120, S130, S140, S150, S160, and S170 are merely reference numerals used to clearly explain the embodiment and the accompanying drawings. Figure 1 The correspondence is not intended to limit the order of steps in this embodiment.

[0053] Step S110: The main platform creates an activity and generates a first token for the activity. The first token includes: the domain name of the platform conducting the activity, the version number, and the token code; the version number is used to manage the data return format.

[0054] Step S120: Each primary platform obtains the first token from the main platform; wherein, the primary platform is the platform that needs to participate in the activity.

[0055] Step S130: The first-level platform parses the first token, extracts the version number, token code and the domain name of the platform where the activity is being carried out, and concatenates the interface URL based on the agreed path of the domain name of the platform where the activity is being carried out. The platform then sends an activity information request to the corresponding platform, which is the target platform.

[0056] Step S140: The target platform verifies the validity of the token code sent by the primary platform, queries the corresponding activity information based on the token code, and returns the activity information data in the format specified by the version number.

[0057] Step S150: The primary platform creates primary activities based on the returned activity information data, collects and processes the primary activity data, and generates primary activity data.

[0058] Step S160: The primary platform uploads the data of the primary activities to the main platform;

[0059] In step S170, the main platform receives data uploaded by each primary activity, follows different parsing logic based on the version number, and stores the received data in the database.

[0060] In daily operations, there are often needs to expand activities to multiple levels. In the past, this would involve maintaining a hierarchical relationship between the main platform and lower-level platforms, with each lower-level platform creating its own activity based on the main platform's information. Then, after selecting outstanding entries, these would be submitted to the main platform for final review.

[0061] In current multi-level activity management systems, a unique token is generated for each activity. The token contains information such as the platform domain name, version number, and token code. The version number is used to manage the data return format and also supports customized version numbers, that is, a specific version number uses a specific format token code. It can also return more information according to customized needs.

[0062] This method includes a main platform, a primary platform, and a target platform, and the interaction process between them is as follows: Figure 2 As shown.

[0063] Specifically, in step S110, the main platform creates activity A and generates a promotion token for the activity, namely the first token. The first token carries the domain name, version number, and token code of the platform conducting the activity. The version number is used to manage the data return format and supports customized version numbers, that is, a specific version number in the customized version number requires a specific token code.

[0064] In step S120, each primary platform administrator obtains a token from the main platform's activity page. It's important to note that a primary platform here refers to a platform that also deploys the review system and participates in Activity A; however, it can also be other third-party platforms, not necessarily subordinate to the main platform. The main platform's activity details page can directly provide a "copy token" button, allowing primary platforms to easily copy tokens with a single click.

[0065] In step S130, the primary platform parses the token to obtain the version number, token code, and the domain name of the platform to which the token belongs. Based on the agreed-upon path, it constructs the interface URL and sends a request to the interface along with the version number and token to retrieve activity information. The version number, token, and other parameters ensure that this request is legitimate and returns valid data.

[0066] In one implementation, the process of the first-level platform parsing the first token and extracting the version number, token code and domain name of the platform conducting the activity in step S130 includes steps S131 and S132.

[0067] Step S131: The first-level platform calls the agreed API interface 1 to obtain the activity credential, wherein the activity credential is an encrypted string;

[0068] Step S132: Parse the activity credentials to obtain information, and then call the agreed API interface 2 to extract the version number, token code, and domain name of the platform where the activity is conducted.

[0069] In this implementation, the primary platform receives the token and calls the agreed-upon API interface 1 to obtain the activity credential. The activity credential is a Base64 encrypted string containing the truly valid information: the domain name, version number, and token code of the platform conducting the activity. After parsing the activity credential to obtain the information, the platform then calls the agreed-upon API interface 2 to obtain the activity information.

[0070] In other words, even if outsiders obtain the token, they cannot steal the business data from it. Only platforms that know the agreed-upon API interface can obtain valid activity credentials by constructing the correct URL and including the token to call the API interface, thereby acquiring the business data.

[0071] In step S140, the target platform receives the request, verifies the token code, queries the activity information based on the token code, assembles the data into the corresponding format according to the version number, and returns it. The version number determines the returned data format. For example, the first version number returns JSON data format, the second version number returns XML format, and the third version number is a customized version number. For customized version numbers, the token is first checked to see if it conforms to a specific format. If it does not conform, it is judged as an invalid request and no data is returned. If it conforms, more information is returned according to the customized requirements corresponding to the customized version number.

[0072] In one implementation, the version number includes: a first version number, a second version number, and / or a third version number;

[0073] The first version number corresponds to JSON format data;

[0074] The second version number corresponds to XML format data;

[0075] The third version number is a customized version number, which needs to be matched with a specific token code to return extended information.

[0076] In one implementation, the version number includes: a third version number, which is a customized version number that needs to be matched with a specific token code to return extended information;

[0077] The process of the target platform verifying the legality of the token code sent by the primary platform in step S140 includes steps S141, S142 and S143.

[0078] Step S141: When the version number is the third version number, verify whether the token conforms to a specific format;

[0079] Step S142: If the request does not conform to the specific format, it is determined to be an invalid request;

[0080] Step S143: When the request conforms to a specific format, it is determined to be a valid request.

[0081] In step S150, after receiving the activity information, the primary platform directly creates an identical activity on its own platform, including activity information, registration form configuration information, etc., and begins activity operations. At this point, the primary platform is essentially a subordinate activity platform of the main platform, but the main platform does not need to maintain this hierarchical relationship. After creating the activity on its own platform, it receives activity materials uploaded from various sources. The primary platform organizes the collected materials; for example, if the platform conducts a judging activity to select outstanding works, it can then filter out the outstanding works and upload them to the main platform without the main platform needing to maintain the primary platform.

[0082] In one implementation, the process of the primary platform creating a primary activity based on the returned activity information data in step S150 includes:

[0083] Step S151: The primary platform selects a data return format that can run on its own platform from the returned activity information data;

[0084] Step S152: Create a first-level activity based on the selected data return format.

[0085] Since the platform is designed for multiple users, different user platforms may have different data format requirements. Therefore, this implementation returns different data formats for each platform to choose from.

[0086] It should be noted that the first token in step S110 of this method is not static, but will be updated as the platform iterates, so different data formats will be added to support gradually.

[0087] In step S160, the first-level platform uploads the data of the first-level activities to the main platform; in step S170, the main platform receives the data uploaded by each first-level activity, follows different parsing logic based on the version number, and stores the received data in the database. If it is a file, the main platform can also submit it to the asynchronous file download manager for download, repeating steps S160 and S170 until the outstanding works are collected on the main platform for final review, and the activity ends.

[0088] This method, based on the concept of activity tokens, facilitates easier promotion of lower-level activities and supports scenarios where lower-level activities push their work to target platforms. The token contains information such as the platform address, version number, and token number. The version number and token number settings allow for multi-language support and customization. Furthermore, the token number is a unique identifier for the activity, enabling the retrieval of specific activities. Customized tokens (matching customized version numbers) are supported, and the version number manages the data return format and content. This method significantly reduces the workload of platform administrators, offers better scalability (eliminating the need to maintain configurations for upper and lower-level platforms on the current platform), supports multi-scenario activity promotion, and can directly perform a series of tasks such as activity copying and activity work pushing programmatically. While reducing the workload of platform administrators, it also ensures data integrity, achieves more efficient data flow, and better supports activity business promotion.

[0089] In one embodiment, the method further includes steps S210, S220, S230, S240, S250, and S260.

[0090] Step S210: The first-level platform generates a second token for the first-level activity. The second token includes: the domain name, version number, and token code of the platform conducting the first-level activity. The version number and token code contained in the second token are the same as those in the first token.

[0091] Step S220: Each secondary platform obtains the second token from the primary platform;

[0092] Step S230: The secondary platform parses the second token, extracts the version number, token code, and domain name of the platform conducting the primary activity, and constructs the interface URL based on the agreed path of the domain name of the platform conducting the primary activity. It then sends an activity information request to the corresponding platform carrying the version number and token code. The corresponding platform is the target platform for the primary activity.

[0093] Step S240: The primary activity target platform verifies the validity of the token code sent by the secondary platform, queries the corresponding activity information, and returns the activity information data in the format specified by the version number.

[0094] Step S250: The secondary platform creates secondary activities based on the returned activity information data, collects and processes the secondary activity data, and generates secondary activity data.

[0095] In step S260, the secondary platform uploads the data of the secondary activities to the primary platform, and the primary platform uploads the data received from each secondary activity to the main platform.

[0096] This method offers high flexibility; the current platform can also generate tokens for activities, which can then be used by other platforms to launch further levels of activities. For example... Figure 3 As shown in the diagram, this implementation illustrates the scenario where the current platform instructs the next platform to carry out activities. In this case, the entire implementation process of the current platform is the same as that of the main platform, and the entire implementation process of the next platform (i.e., the second-level platform) is the same as that of the first-level platform. Finally, the information from all platforms is aggregated onto the main platform. Similarly, the second-level platform can generate tokens to instruct the third-level platform to implement activities, and so on.

[0097] In one implementation, the process of the secondary platform creating a secondary activity based on the returned activity information data in step S260 includes steps S261 and S262.

[0098] Step S261: The secondary platform selects a data return format that can run on its own platform from the returned activity information data;

[0099] Step S262: Create a secondary activity based on the selected data return format.

[0100] The entire implementation process of the secondary platform is the same as that of the primary platform, and the two steps mentioned above are also the same as those of the primary platform.

[0101] Example 2

[0102] Corresponding to the method in Embodiment 1, the present invention also provides a multi-level activity management device, including: a main platform, a primary platform, and a target platform;

[0103] The main platform is used to create activities and generate a first token for the activity. The first token includes: the domain name of the activity platform, the version number, and the token code; the version number is used to manage the data return format.

[0104] The primary platform is used to obtain the first token from the main platform, parse the first token, extract the version number, token code, and domain name of the activity platform, construct the interface URL based on the agreed path of the activity platform's domain name, and send an activity information request to the corresponding platform carrying the version number and token code. The corresponding platform is the target platform. The primary platform is the platform that needs to participate in the activity.

[0105] The target platform is used to verify the validity of the token code sent by the primary platform, query the corresponding activity information based on the token code, and return the activity information data in the format specified by the version number;

[0106] The primary platform is also used to create primary activities based on the returned activity information data, collect and process primary activity data, generate primary activity data, and upload primary activity data to the main platform.

[0107] The main platform is also used to receive data uploaded from various primary activities, and uses different parsing logic based on the version number to store the received data in the database.

[0108] In one implementation, the process of creating a primary activity based on the returned activity information data performed by the primary platform includes:

[0109] The primary platform selects a data return format that can run on its own platform from the returned activity information data;

[0110] Create a first-level activity based on the selected data return format.

[0111] In one embodiment, the multi-level activity management device further includes: a secondary platform and a primary target platform;

[0112] The primary platform is also used to generate a second token for the primary activity. The second token includes the domain name, version number, and token code of the platform conducting the primary activity. The version number and token code contained in the second token are the same as those in the first token.

[0113] The secondary platform is used to obtain the second token from the primary platform, parse the second token, extract the version number, token code, and domain name of the platform conducting the primary activity, and construct the interface URL based on the agreed path of the domain name of the platform conducting the primary activity. It then sends an activity information request to the corresponding platform carrying the version number and token code. This corresponding platform is the target platform for the primary activity.

[0114] The primary activity target platform is also used to verify the legality of the token codes sent by the secondary platform, query the corresponding activity information, and return the activity information data in the format specified by the version number;

[0115] The secondary platform is also used to create secondary activities based on the returned activity information data, collect and process secondary activity data, generate secondary activity data, and upload the secondary activity data to the primary platform.

[0116] The primary platform is also used to upload data received from various secondary activities to the main platform.

[0117] In one implementation, the process of creating a secondary activity based on the returned activity information data by the secondary platform includes:

[0118] The secondary platform selects a data return format that can run on its own platform from the returned activity information data;

[0119] Create a secondary activity based on the selected data return format.

[0120] In one implementation, the version number includes: a first version number, a second version number, and / or a third version number;

[0121] The first version number corresponds to JSON format data;

[0122] The second version number corresponds to XML format data;

[0123] The third version number is a customized version number, which needs to be matched with a specific token code to return extended information.

[0124] In one implementation, the version number includes: a third version number, which is a customized version number that needs to be matched with a specific token code to return extended information;

[0125] The process by which the target platform verifies the validity of the token code sent by the primary platform includes:

[0126] When the version number is the third version number, verify whether the token conforms to a specific format;

[0127] If the request does not conform to the specific format, it is deemed an invalid request.

[0128] A request is considered valid if it conforms to a specific format.

[0129] In one implementation, the process of resolving the first token and extracting the version number, token code, and domain name of the active platform by the primary platform includes:

[0130] The first-level platform calls the agreed API interface 1 to obtain the activity credential, wherein the activity credential is an encrypted string;

[0131] The activity credentials are parsed to obtain information, and then the agreed API interface 2 is called to extract the version number, token code, and domain name of the activity platform.

[0132] This device, based on the concept of activity tokens, facilitates easier promotion of lower-level activities and supports scenarios where lower-level activities push their work to target platforms. The token contains information such as the platform address, version number, and token number. The version number and token number settings allow for multi-language support and customization. Furthermore, the token number is a unique identifier for the activity, enabling the retrieval of specific activities. Customized tokens (matching customized version numbers) are supported, and the version number manages the data return format and content. This device significantly reduces the workload of platform administrators, offers better scalability (eliminating the need to maintain configurations for upper and lower-level platforms on the current platform), supports multi-scenario activity promotion, and can directly perform a series of tasks such as activity copying and activity work pushing through the program. While reducing the workload of platform administrators, it also ensures data integrity, achieves more efficient data flow, and better supports activity business promotion.

[0133] Example 3

[0134] This invention also provides a storage medium storing computer instructions that, when executed by a processor, implement the multi-level activity management method of any of the above embodiments.

[0135] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, random access memory (RAM), read-only memory (ROM), magnetic disks, or optical disks.

[0136] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to related technologies, 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, terminal, or network device, etc.) to execute all or part of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, RAM, ROM, magnetic disks, or optical disks.

[0137] Corresponding to the computer storage medium described above, one embodiment also provides a computer device, which includes a memory, an encoder, and a computer program stored in the memory and executable on the encoder, wherein the encoder executes the program to implement any of the multi-level activity management methods described in the above embodiments.

[0138] The aforementioned computer equipment, based on the concept of activity tokens, facilitates easier promotion of lower-level activities and supports scenarios where lower-level activities push their work to target platforms. The token contains information such as the platform address, version number, and token number. The version number and token number settings allow for multi-language support and customization. Furthermore, the token number is a unique identifier for the activity, enabling the retrieval of specific activities. Customized tokens (matching customized version numbers) are supported, and the version number manages the data return format and content. This computer equipment significantly reduces the workload of platform administrators, offers better scalability (eliminating the need to maintain configurations for upper and lower-level platforms on the current platform), supports multi-scenario activity promotion, and can directly perform a series of tasks such as activity copying and activity work pushing through the program. While reducing the workload of platform administrators, it also ensures data integrity, achieves more efficient data flow, and better supports activity business promotion.

[0139] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0140] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the implementation of the present invention. Those skilled in the art can make other variations or modifications based on the above description. It is neither necessary nor possible to exhaustively describe all embodiments here. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the claims of the present invention.

Claims

1. A multi-level activity management method, characterized by, The method comprises the following steps: A main platform creates an activity and generates a first token about the activity, the first token comprising: a domain name of a platform that carries out the activity, a version number and a token code; the version number is used for managing data return format; Each first-level platform acquires the first token of the main platform; wherein the first-level platform is a platform that needs to participate in the activity; The first-level platform parses the first token, extracts the version number, the token code and the domain name of the platform that carries out the activity, splices an interface URL based on the agreed path of the domain name of the platform that carries out the activity, carries the version number and the token code and initiates an activity information request to a corresponding platform, i.e. a target platform; The target platform checks the legality of the token code sent by the first-level platform, queries corresponding activity information based on the token code and returns activity information data in a format specified by the version number; The first-level platform creates a first-level activity based on the returned activity information data, recycles first-level activity materials and processes, and generates data of the first-level activity; The first-level platform uploads the data of the first-level activity to the main platform; The main platform receives the data uploaded by each first-level activity, and based on the version number, different analysis logics are used to store the received data in a database.

2. The multi-level activity management method of claim 1, wherein, The process of creating a first-level activity by the first-level platform based on the returned activity information data comprises: The first-level platform selects a data return format that can run on the platform itself in the returned activity information data; The first-level platform creates a first-level activity based on the selected data return format.

3. The multi-level activity management method of claim 2, wherein, Further comprising: The first-level platform generates a second token about the first-level activity, the second token comprising: a domain name of a platform that carries out the first-level activity, a version number and a token code, the version number and the token code contained in the second token being the same as those in the first token; Each second-level platform acquires the second token of the first-level platform; The second-level platform parses the second token, extracts the version number, the token code and the domain name of the platform that carries out the first-level activity, splices an interface URL based on the agreed path of the domain name of the platform that carries out the first-level activity, carries the version number and the token code and initiates an activity information request to a corresponding platform, i.e. a target platform of the first-level activity; The target platform of the first-level activity checks the legality of the token code sent by the second-level platform, queries corresponding activity information and returns activity information data in a format specified by the version number; The second-level platform creates a second-level activity based on the returned activity information data, recycles second-level activity materials and processes, and generates data of the second-level activity; The second-level platform uploads the data of the second-level activity to the first-level platform, and the first-level platform uploads the data of each second-level activity received to the main platform.

4. The multi-level activity management method of claim 3, wherein, The process of creating a second-level activity by the second-level platform based on the returned activity information data comprises: The second-level platform selects a data return format that can run on the platform itself in the returned activity information data; The second-level platform creates a second-level activity based on the selected data return format.

5. The multi-level activity management method according to any one of claims 1 to 4, characterized in that, The version number comprises: a first version number, a second version number and / or a third version number; The first version number corresponds to JSON format data; The second version number corresponds to XML format data; The third version number is a customized version number, which needs to be matched with a specific token code to return extended information.

6. The multi-level activity management method according to any one of claims 1 to 4, characterized in that, The version number comprises a third version number, which is a customized version number, and needs to be matched with a specific token code to return extended information. The process of verifying the legality of the token code sent by the target platform comprises: When the version number is the third version number, verifying whether the token conforms to a specific format; When not conforming to the specific format, judging as an illegal request; When conforming to the specific format, judging as a legal request.

7. The multi-level activity management method according to any one of claims 1 to 4, characterized by, The process of the first-level platform analyzing the first token to extract the version number, the token code and the domain name of the platform where the activity is carried out comprises: The first-level platform calls an agreed API interface 1 to obtain an activity credential, wherein the activity credential is an encrypted string; The information is obtained by analyzing the activity credential, and an agreed API interface 2 is called to extract the version number, the token code and the domain name of the platform where the activity is carried out.

8. A multi-level activity management apparatus, characterized by, Comprise: A main platform, a first-level platform and a target platform; The main platform is used to create an activity and generate a first token about the activity, wherein the first token comprises a domain name of a platform where the activity is carried out, a version number and a token code; the version number is used to manage the data return format; The first-level platform is used to obtain the first token of the main platform, analyze the first token, extract the version number, the token code and the domain name of the platform where the activity is carried out, splice an interface URL based on the agreed path of the domain name of the platform where the activity is carried out, carry the version number and the token code, and initiate an activity information request to a corresponding platform, i.e. the target platform; wherein the first-level platform is a platform that needs to participate in the activity; The target platform is used to verify the legality of the token code sent by the first-level platform, query corresponding activity information based on the token code, and return activity information data in the format specified by the version number; The first-level platform is also used to create a first-level activity based on the returned activity information data, recycle the first-level activity data and process, generate data of the first-level activity, and upload the data of the first-level activity to the main platform; The main platform is also used to receive the data uploaded by each first-level activity, based on the version number, to take different analysis logic, and store the received data in a database.

9. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to realize the method of any one of claims 1-7.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to realize the method of any one of claims 1-7.

Images