Class activation method and device, electronic equipment and storage medium

By using the domain module injection function, the problem of repetitive development of category activation systems in the financial market was solved, enabling cross-market synchronous updates and low-cost maintenance, thereby improving user experience and market expansion efficiency.

CN121900781APending Publication Date: 2026-04-21FUTU NETWORK TECH (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
FUTU NETWORK TECH (SHENZHEN) CO LTD
Filing Date
2025-12-01
Publication Date
2026-04-21

Smart Images

  • Figure CN121900781A_ABST
    Figure CN121900781A_ABST
Patent Text Reader

Abstract

The invention relates to the field of data processing, and particularly discloses a category activation method and device, electronic equipment and a storage medium. In response to a category activation request submitted by a user, a user domain module is called to obtain user information; in response to a first selection instruction for selecting at least one candidate account, calling an account domain module to obtain a category list corresponding to the selected target account; in response to a second selection instruction for at least one target category in the non-activated category list, calling the application field submitting module to perform preposition check on the at least one target category corresponding to the second selection instruction, and performing preposition operation when the at least one target category needs preposition operation; in response to submission information fed back by the application domain submission module, calling the user application domain module to activate and check at least one target category corresponding to the second selection instruction; and when the target category is activated and audited successfully, the activation result of the target category is fed back, so that the maintenance cost of the category activation function is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to the field of data processing, and more specifically to a product category activation method, apparatus, electronic device, and storage medium. Background Technology

[0002] In financial market trading environments, users need to activate specific product categories to trade financial products within those categories. This activation grants them the ability and permissions to trade financial products within that category. Related technologies require category activation maintenance for the corresponding applications to meet user needs, including but not limited to interface design, code design, and database design. However, when applications are deployed in different market environments, such as different national markets, a separate category activation system needs to be developed and maintained for each market environment. This results in numerous systems, significant code duplication, high maintenance costs, and asynchronous feature updates. Summary of the Invention

[0003] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a category activation method, apparatus, electronic device and storage medium, in which the application injects relevant functions through the domain module to realize the category activation of financial products. This eliminates the need to develop and maintain a separate category activation system for each market application deployed in each market environment, reduces coupling and enables multi-market characteristic process application scheduling, and effectively reduces the maintenance cost of the category activation function.

[0004] In a first aspect, embodiments of this application provide a product category activation method, including: In response to a category activation request submitted by a user, the service interface of the user domain module is invoked to obtain user information through the user domain module; the user information includes at least one candidate account corresponding to the user; In response to a first selection instruction to select at least one of the candidate accounts, the service interface of the account domain module is invoked to obtain a category list corresponding to the selected target account through the account domain module, the category list including at least an inactive category list; In response to a second selection instruction for at least one target category in the list of inactive categories, the service interface of the application submission domain module is invoked to perform a preliminary check on at least one target category corresponding to the second selection instruction through the application submission domain module, and to perform a preliminary operation when at least one of the target categories requires a preliminary operation. In response to the submission information fed back by the application submission module, the service interface of the user application module is invoked to activate and review at least one of the target categories corresponding to the second selection instruction through the user application module; When the activation approval of the target category is passed, the activation result of the target category will be fed back.

[0005] Secondly, embodiments of this application provide a product category activation device, comprising: The first response module is used to respond to a category activation request submitted by a user by calling the service interface of the user domain module to obtain user information through the user domain module; the user information includes at least one candidate account corresponding to the user; The second response module is used to call the service interface of the account domain module in response to a first selection instruction to select at least one of the candidate accounts, so as to obtain the category list corresponding to the selected target account through the account domain module, wherein the category list includes at least an inactive category list. The third response module is used to respond to the second selection instruction for at least one target category in the list of inactive categories by calling the service interface of the application submission domain module, so as to perform a pre-check on at least one target category corresponding to the second selection instruction through the application submission domain module, and perform a pre-operation when at least one of the target categories requires a pre-operation. The fourth response module is used to respond to the submission information fed back by the application submission module, and call the service interface of the user application module to activate and review at least one of the target categories corresponding to the second selection instruction through the user application module. The feedback module is used to provide feedback on the activation result of the target category when the activation review of the target category is approved.

[0006] Thirdly, embodiments of this application provide an electronic 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 described in embodiments of this application.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in embodiments of this application.

[0008] Fifthly, embodiments of this application provide a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, it implements the method described in embodiments of this application.

[0009] The category activation method, apparatus, electronic device, and storage medium provided in this application embodiment allow the application to respond to user requests submitted through an interactive interface by calling the service interface of a domain module with corresponding functions. This allows the application to obtain the functional implementation of the domain module for the corresponding request, including but not limited to relevant information data, implementation process, implementation results, and other related content. The application injects the relevant functional implementation through the domain module and displays the functional implementation feedback from the domain module through the client's interactive interface, thereby activating the category of financial products. This eliminates the need to develop and maintain a separate category activation system for each market application deployed in each market environment, reducing coupling and enabling multi-market characteristic process application scheduling, effectively reducing the maintenance cost of the category activation function. Furthermore, when updating category activation, only the corresponding domain module needs to be updated to ensure synchronous updates of relevant functions across multiple markets, guaranteeing a consistent user experience in different market environments. Additionally, when a financial system enters a new market environment, category activation services can be obtained by building a market application with interfaces to call the relevant domain modules, improving the response speed to new markets and meeting the market expansion needs of financial institutions.

[0010] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0011] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 A flowchart illustrating a category activation method provided in an embodiment of this application is shown; Figure 2 An implementation architecture diagram of a category activation method provided in an embodiment of this application is shown; Figure 3 This application provides a schematic diagram of various domain modules and their common functions according to an embodiment of the present application; Figure 4 This illustration shows a schematic diagram of the implementation principle of calling a user domain module according to an embodiment of this application; Figure 5 A schematic diagram of a candidate account selection interface provided in an embodiment of this application is shown; Figure 6 This illustration shows a schematic diagram of the implementation principle of the account domain module provided in an embodiment of this application; Figure 7 A schematic diagram of a category list selection interface provided in an embodiment of this application is shown; Figure 8This illustration shows a schematic diagram of the implementation principle of calling the application submission field module according to an embodiment of this application; Figure 9 A schematic diagram of an interface for agreeing to derivatives trading according to an embodiment of this application is shown; Figure 10 A schematic diagram of an evaluation and testing interface provided in an embodiment of this application is shown; Figure 11 This illustration shows a schematic diagram of the implementation principle of calling the user application domain module according to an embodiment of this application; Figure 12 A schematic diagram of the structure of a computer system suitable for implementing an electronic device or server according to embodiments of this application is shown. Detailed Implementation

[0012] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0013] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0014] Figure 1 This illustration shows a flowchart of a category activation method provided in an embodiment of this application. The category activation method provided in this embodiment of the application, specifically the transaction order processing method, can be executed by a computer device, which can be a terminal or a server. The terminal can be a smartphone, tablet, laptop, desktop computer, smart TV, smart speaker, wearable smart device, smart vehicle terminal, etc. The terminal can also include an application client, which can be a financial client, browser client, or instant messaging client, etc. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network services, and big data and artificial intelligence platforms, but is not limited to these.

[0015] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation instruction steps as shown in the following embodiments or drawings, the method may include more or fewer operation instruction steps based on conventional or non-creative effort. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.

[0016] It should be noted that the acquisition or use of data in the embodiments of this application requires the user's consent. The relevant data can only be obtained after the user's authorization and permission, and the acquisition or use of the data complies with the laws and regulations of the relevant regions.

[0017] like Figure 1 As shown, the method includes: Step 101: In response to the category activation request submitted by the user, call the service interface of the user domain module to obtain user information through the user domain module; the user information includes at least one candidate account corresponding to the user.

[0018] It should be noted that this application embodiment applies to a financial transaction system that integrates an automated approval process for activating financial product categories. This ensures that users strictly adhere to the activation restrictions set by the institution and pass the corresponding approval process before activating any financial product category. The financial transaction system can run on a server and provide users with financial transaction application services through an application client. The established activation restrictions for financial product categories can be adjusted according to different market regulations.

[0019] Among them, at least one candidate account can be the sum of the user's operable accounts in multiple marketplaces, or it can be a candidate account that the user can operate in the current marketplace.

[0020] Step 102: In response to a first selection instruction to select at least one candidate account, the service interface of the account domain module is invoked to obtain the category list corresponding to the selected target account through the account domain module. The category list includes at least the list of inactive categories.

[0021] In other words, users select the account for which category activation is required through the first selection command, and then obtain the corresponding category list for the selected target account through the account domain module.

[0022] Step 103: In response to the second selection instruction for at least one target category in the list of inactive categories, call the service interface of the application submission domain module to perform a preliminary check on at least one target category corresponding to the second selection instruction through the application submission domain module, and perform a preliminary operation when at least one target category requires a preliminary operation.

[0023] It should be noted that, in addition to approval, some product category activation restrictions also require the configuration of corresponding pre-approval procedures under specific market conditions. These pre-approval operations must be completed before activation can be submitted. For example, users need to agree to derivatives trading before activating futures or forex.

[0024] Step 104: In response to the submission information provided by the application field module, call the service interface of the user application field module to activate and review at least one target category corresponding to the second selection instruction through the user application field module.

[0025] Optionally, in this embodiment of the application, the user application domain module can automatically review the activation application, and then the reviewer can review it based on the records in the management system. Alternatively, the reviewer can review the application and record it in the management system.

[0026] In an optional embodiment, parameter information during the target category activation process is obtained to generate an activation record for the target category activation, for example, by generating the activation record for the target category activation in a management system.

[0027] Step 105: When the activation approval for the target category is approved, provide feedback on the activation result of the target category.

[0028] Furthermore, when the target category activation approval is granted, the user application domain module calls the service interface of the account domain module to activate the target category in the target account through the account domain module.

[0029] In other words, once the target category has completed the preliminary operations and review, the target account's trading permissions for that target category will be activated through the account domain module, enabling the target account to conduct trading operations on financial products within that target category.

[0030] Preferably, the account domain module can also provide a feedback interface after the target category is activated, to notify the user that the target category in the target account has been successfully activated.

[0031] Specifically, in this embodiment, the application responds to user requests submitted through the interactive interface by calling the service interface of the corresponding domain module. This allows the application to obtain the domain module's functional implementation for the request, including but not limited to relevant information, implementation process, results, and other related content. The application injects the relevant functional implementation through the domain module and displays the feedback from the domain module through the client's interactive interface, thus activating the category of financial products. This eliminates the need to develop and maintain a separate category activation system for each market application deployed in each market environment, reducing coupling and enabling multi-market characteristic process application scheduling, effectively reducing the maintenance cost of the category activation function. Furthermore, when updating category activation, only the corresponding domain module needs to be updated to ensure synchronous updates of related functions across multiple markets, guaranteeing a consistent user experience across different market environments. Additionally, when a financial system enters a new market environment, category activation services can be obtained by building a market application with interfaces to call the relevant domain modules, improving the response speed to new markets and meeting the market expansion needs of financial institutions.

[0032] Figure 2 This diagram illustrates the implementation architecture of a category activation method according to an embodiment of this application. The category activation system includes an application layer and a domain layer. The application layer provides users with an application client to offer interactive interfaces and feedback information for category activation. The application layer executes the category activation method provided in this embodiment, obtaining functional implementations from multiple domain modules by calling their service interfaces in multiple steps, thereby achieving category activation. The domain layer provides multiple domain modules, each offering a specific domain function. These functions include common functions across multiple markets and unique functions specific to different markets. The common functions provide consistent command response for multiple market applications, while the unique functions provide execution methods corresponding to each market application. The market applications are financial systems deployed in various market environments.

[0033] like Figure 2 and Figure 3 As shown in this embodiment, the domain module includes a user domain module, an account domain module, an application submission domain module, and a user application domain module. The user domain module is used for user verification. For example, common capabilities of the user domain module across multiple app stores include verifying whether a user can enter the category activation process and obtaining basic user parameters. Specific capabilities across multiple app stores include obtaining all of the user's accounts across multiple app stores, performing specific verifications for users who cannot enter the category activation process in each app store, and obtaining extended basic user information.

[0034] The common capabilities of the account domain module across multiple app stores include obtaining information on all current integrated accounts and categories of a user, obtaining categories that can be added to an integrated account, activating a specific category for a specified integrated account, and activating a specific category for all integrated accounts. Specific capabilities across multiple app stores include initializing dependency data, obtaining a list of categories that can be activated, obtaining a list of categories that can be added to an integrated account, obtaining a list of account types corresponding to a category, obtaining the category display order, obtaining the prerequisite dependent categories for each category, and the reasons why a single category cannot be selected.

[0035] The common capabilities of the application submission module across multiple marketplace applications include submitting activation applications. Its unique capabilities across different marketplace applications include initializing dependency data, performing pre-activation checks in each marketplace, and performing pre-activation operations in each marketplace.

[0036] The common capabilities of the user application module across multiple app stores include approval and completion of the application task (activation process) after approval. Its unique capabilities across multiple app stores include post-approval operations for each app store's application and post-activation operations for each app store's application.

[0037] Furthermore, such as Figure 2 As shown in Figure 3, multiple domain modules in the domain layer can also have dependencies. Specifically, the account domain module depends on the user domain module, the submit activation domain module depends on the account domain module, and the user application domain module depends on the account domain module.

[0038] In one feasible embodiment, obtaining the category list corresponding to the selected target account through the account domain module includes: the account domain module responding to the first selection instruction to obtain the target account; the account domain module calling the service interface of the user domain module to obtain the first target account that the user can operate in the current market application through the user domain module; and the account domain module determining the target category list corresponding to the first target account in the current market application based on the first target account.

[0039] In other words, in this embodiment of the application, the candidate account is the sum of the accounts that the user can operate in multiple market applications. The first selection instruction may include accounts that are not operable in the current market application. That is, the target account includes a first target account that is operable in the current market application and a second target account that is not operable in the current market application. The account domain module can determine the first target account that is operable in the current market application from the target account by calling the user domain module, and then obtain the target category list for the first target account.

[0040] In another feasible embodiment, the candidate account is an account that the user can operate in the current market application, obtained by the user domain module, and the target account is the first target account that the user can operate in the current market application. The category list corresponding to the selected target account is obtained through the account domain module, including: sending the first target account to the account domain module through the service interface of the account domain module; the account domain module determines the target category list corresponding to the first target account in the current market application based on the first target account.

[0041] In other words, in this embodiment of the application, the user domain module on which the account domain module depends has provided the currently operable accounts of the market application before calling the account domain module. At this time, the target account corresponding to the first selection instruction is the first target account operable by the current market application. The account domain module can directly obtain the first target account through the service interface and obtain the target category list for the first target account.

[0042] The target category list includes at least one of the following: categories that can be activated by the first target account, categories that can be activated by additional accounts, account types corresponding to the categories, category display order, prerequisites for category activation, and reasons why a category cannot be selected.

[0043] Therefore, this application provides two ways to provide dependency information for domain modules. Taking the account domain's dependency on the user domain as an example, the account domain module can call its dependent user domain module during the execution of the response function to ensure that the account domain module can perform its function. Alternatively, the application layer can obtain the information required by the account domain module when it first obtains user-related information and account information, and send it to the account domain module when calling the account domain module. This reduces coupling, reduces the number of network requests, and improves performance by injecting the dependency domain of a single domain.

[0044] It should also be noted that, in the embodiments of this application, the dependency of the later domain module on the earlier domain module can be a common capability or a specific capability, which is determined according to the earlier domain content on which the later domain module depends, and this application does not make specific limitations.

[0045] For example, the account domain module relies on the features and capabilities of the user domain module to obtain the user's account information that can be operated in the current application market, while the user application domain module relies on the common capabilities of the account domain module to activate a specified category with a specified comprehensive account or activate a specified category with all comprehensive accounts to complete the approval process.

[0046] In one specific embodiment, after logging into the application client, the user enters the category activation interface through the corresponding functional controls. At this time, such as Figure 4As shown, the application layer calls the service interface of the user domain module to verify whether the user can enter the category activation process based on the common capabilities of the user domain module. If the user can enter the category activation process, it retrieves at least one candidate account that the user can operate in the current market application based on the characteristic capabilities of the user domain module. For example, if the user can enter the category activation process, the following will be displayed: Figure 5 The interface shown displays at least one candidate account that the user can operate in the current market application, such as a margin account (XXXX), for the user to choose from.

[0047] User from Figure 5 In the interface shown, select at least one candidate account to form at least one first target account, and trigger the trigger control at the bottom of the interface (e.g., Figure 5 The "Next" option in the code generates the first selection instruction. At this point, the application layer calls the service interface of the account domain module, such as... Figure 6 As shown, based on the common capabilities of the account domain module, all user account and category information is obtained. Then, based on the specific capabilities, the activatable categories, additional categories, account types corresponding to the categories, category display order, prerequisites for each category, and reasons why categories cannot be selected are obtained for the first target account. The application layer assembles the information returned by the account domain module and processes it according to the following... Figure 7 The display shows the trading instruments for the Margin Integrated Account (XXXX), including a list of inactive categories, a list of activated categories, and a list of categories that can be added, displayed in the order of inactive, activated, and then addable categories. Among the inactive categories, Japanese stocks, Singapore stocks, funds, bonds, and institutional notes are all selectable for activation. Figure 7 The example shown selects Japanese stocks, Singapore stocks, and structured notes to generate the second option instruction. Additionally, the "Leveraged Forex" category in the inactive category list is an inactive category. In some embodiments, this indicates that the product category is not active when the user selects the cursor to move to it. In such cases, a floating window will display the reason why the category cannot be activated to the user. It should also be noted that several categories in the activated list, such as Hong Kong stocks, US stocks, A-shares through the Stock Connect, and futures, are also in an inactive state. Figure 7 The interactive interface also displays a list of available trading categories to the user with the prompt, "Does not the trading instrument you want to activate above? Open a cash account to activate."

[0048] After obtaining the second selection instruction, the application calls the service interface of the application submission domain module, such as... Figure 8As shown, the application submission module verifies whether the target category in the target account can submit an activation application and then initiates the application submission. After verifying that the target category in the target account can submit an activation application, the application submission module further performs pre-submission verification on the target category based on its feature capabilities. If the user has not completed the pre-activation operation, the module provides the user with the corresponding pre-operation. For example, as... Figure 9 As shown, a confirmation interface is provided to users to agree to derivatives trading, prompting them that activating this target product category requires unified derivatives trading. Alternatively, if the current market is the Hong Kong market and the target product is cryptocurrency, a series of assessments and tests are required, in which case the user is provided with... Figure 10 The interface shown here is for activating a cryptocurrency account and assessing its eligibility to assist users in completing relevant assessments and tests, such as virtual asset risk assessment, virtual asset holding limit assessment, virtual asset knowledge assessment, and virtual asset knowledge test. It should be understood that these preliminary steps are set according to the rules of the prevailing market environment, and this application does not impose specific limitations on them.

[0049] If the user completes the above preliminary operations, and the application layer responds to the submission information from the application submission module, such as an activation application, then... Figure 11 As shown, the service interface of the user application domain module is called. The application domain module reviews the activation application based on common capabilities, and after the review is approved, it calls the account domain module to activate the target category in the target account through the common capabilities of the account domain module, thus completing the activation. The user application domain module also further utilizes its special capabilities to perform post-approval operations and activation completion operations when the corresponding category has post-operations, and saves a snapshot for information retention.

[0050] It should be noted that although the operation of the method of the present invention is described in a specific order in the accompanying drawings, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed in order to achieve the desired result.

[0051] The division of modules or units mentioned in the detailed description above is not mandatory. In fact, according to the embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0052] The following is for reference. Figure 12 , Figure 12 A schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application is shown. like Figure 12As shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1202 or programs loaded from storage section 1208 into random access memory (RAM) 1203. The RAM 1203 also stores various programs and data required for the system's operating instructions. The CPU 1201, ROM 1202, and RAM 1203 are interconnected via a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0053] The following components are connected to I / O interface 1205: an input section 1206 including a keyboard, mouse, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to I / O interface 1205 as needed. Removable media 1211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1210 as needed so that computer programs read from them can be installed into storage section 1208 as needed.

[0054] Specifically, according to embodiments of this application, the flowchart above refers to... Figure 2 The described process can be implemented as a computer software program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program contains program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 1209, and / or installed from removable medium 1211. When the computer program is executed by central processing unit (CPU) 1201, it performs the functions defined in the system of this application.

[0055] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0056] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operational instructions of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two connected blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified functions or operational instructions, or using a combination of dedicated hardware and computer instructions.

[0057] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments, or may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the category activation method described in this application.

[0058] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the foregoing disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A product category activation method, characterized in that, include: In response to a user's category activation request, the service interface of the user domain module is invoked to obtain user information through the user domain module; The user information includes at least one candidate account corresponding to the user; In response to a first selection instruction to select at least one of the candidate accounts, the service interface of the account domain module is invoked to obtain a category list corresponding to the selected target account through the account domain module, the category list including at least an inactive category list; In response to a second selection instruction for at least one target category in the list of inactive categories, the service interface of the application submission domain module is invoked to perform a preliminary check on at least one target category corresponding to the second selection instruction through the application submission domain module, and to perform a preliminary operation when at least one of the target categories requires a preliminary operation. In response to the submission information fed back by the application submission module, the service interface of the user application module is invoked to activate and review at least one of the target categories corresponding to the second selection instruction through the user application module; When the activation approval of the target category is passed, the activation result of the target category will be fed back.

2. The product category activation method according to claim 1, characterized in that, The account domain module depends on the user domain module. Obtaining the category list corresponding to the selected target account through the account domain module includes: The account domain module responds to the first selection instruction and obtains the target account; The account domain module calls the service interface of the user domain module to obtain the first target account that the user can operate in the current market application through the user domain module; The account domain module determines a list of target product categories corresponding to the first target account in the current market application based on the first target account; The target category list includes at least one of the following: categories that can be activated by the first target account, categories that can be activated by additional accounts, account types corresponding to categories, category display order, prerequisites for category activation, and reasons why categories cannot be selected.

3. The product category activation method according to claim 1, characterized in that, The account domain module depends on the user domain module. The candidate account is the user's operable account in the current market application obtained by the user domain module. The target account is the first target account that the user can operate in the current market application. Obtaining the category list corresponding to the selected target account through the account domain module includes: The first target account is sent to the account domain module through the service interface of the account domain module; The account domain module determines a list of target product categories corresponding to the first target account in the current market application based on the first target account; The target category list includes at least one of the following: categories that can be activated by the first target account, categories that can be activated by additional accounts, account types corresponding to categories, category display order, prerequisites for category activation, and reasons why categories cannot be selected.

4. The product category activation method according to claim 1, characterized in that, When the target category activation approval is granted, the following is also included: The user application domain module calls the service interface of the account domain module to activate the target category in the target account through the account domain module.

5. The product category activation method according to claim 1, characterized in that, After completing the activation operation for the target product category, the process further includes: Obtain parameter information during the activation process of the target product category to generate an activation record for the target product category.

6. The product category activation method according to claim 1, characterized in that, The user domain module, the account domain module, the application submission domain module, and the user application domain module include common capabilities across multiple marketplace applications and unique capabilities corresponding to each marketplace application. The common capabilities are used to provide consistent command response functionality for multi-market applications; The aforementioned features are used to provide an execution plan corresponding to each of the market applications.

7. A category activation system, characterized in that, It includes an application layer and a domain layer, the domain layer comprising multiple domain modules, and the application is used for: In response to a category activation request submitted by a user, the service interface of the user domain module is invoked to obtain user information through the user domain module; the user information includes at least one candidate account corresponding to the user; In response to a first selection instruction to select at least one of the candidate accounts, the service interface of the account domain module is invoked to obtain a category list corresponding to the selected target account through the account domain module, the category list including at least an inactive category list; In response to a second selection instruction for at least one target category in the list of inactive categories, the service interface of the application submission domain module is invoked to perform a preliminary check on at least one target category corresponding to the second selection instruction through the application submission domain module, and to perform a preliminary operation when at least one of the target categories requires a preliminary operation. In response to the submission information fed back by the application submission module, the service interface of the user application module is invoked to activate and review at least one of the target categories corresponding to the second selection instruction through the user application module; When the activation approval of the target category is passed, the activation result of the target category will be fed back.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the category activation method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the category activation method as described in any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the category activation method according to any one of claims 1-6.