Data processing method, apparatus and terminal device

Abstract

The present disclosure provides a data processing method, device and terminal equipment, the method comprising: obtaining a dependency relationship between a plurality of modules of an application program, the dependency relationship indicating a module of a dependent party and a module of a depended party in the plurality of modules; obtaining module information registered in a container of the module of the depended party; and determining a compilation result of the module of the dependent party based on the dependency relationship and the module information, the compilation result being used to indicate whether the module of the dependent party can obtain the module of the depended party.

Description

Technical Field

[0001] This disclosure relates to the field of software development technology, and in particular to a data processing method, apparatus, and terminal device. Background Technology

[0002] Inversion of Control (IoC) is a design methodology in software development that decouples two modules. In this method, the dependent module may or may not have access to the module it depends on.

[0003] Currently, during the compilation process, terminal devices need to compile modules that depend on others to obtain the logic processing of the modules they depend on, and modules that depend on others cannot obtain the logic processing of the modules they depend on. In this approach, the compilation complexity is high, leading to low development efficiency. Summary of the Invention

[0004] This disclosure provides a data processing method, apparatus, and terminal device to solve technical problems in the prior art.

[0005] In a first aspect, embodiments of this disclosure provide a data processing method, the data processing method comprising:

[0006] Obtain the dependencies between multiple modules of the application, wherein the dependencies indicate the dependent modules and the modules that are depended upon among the multiple modules;

[0007] Obtain the module information registered in the container of the module of the dependent party;

[0008] Based on the dependency relationship and the module information, the compilation result of the dependent module is determined, and the compilation result is used to indicate whether the dependent module can obtain the module of the dependent party.

[0009] In a second aspect, embodiments of this disclosure provide a data processing apparatus, which includes a first acquisition module, a second acquisition module, and a determination module, wherein:

[0010] The first acquisition module is used to acquire the dependency relationships between multiple modules of the application, wherein the dependency relationships indicate the dependent modules and the dependent modules among the multiple modules;

[0011] The second acquisition module is used to acquire module information registered in the container of the module of the dependent party;

[0012] The determining module is used to determine the compilation result of the dependent module based on the dependency relationship and the module information. The compilation result is used to indicate whether the dependent module can obtain the module of the dependent party.

[0013] Thirdly, this disclosure provides a terminal device including: a processor and a memory;

[0014] The memory stores computer-executed instructions;

[0015] The processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the data processing methods described in the first aspect above and various possible aspects of the first aspect.

[0016] Fourthly, this disclosure provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the data processing methods described in the first aspect above and various possible aspects of the first aspect.

[0017] Fifthly, this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the data processing methods described in the first aspect above and various possible aspects of the first aspect.

[0018] This disclosure provides a data processing method, apparatus, and terminal device. The terminal device can obtain the dependency relationships between multiple modules of an application. The dependency relationships indicate the dependent and dependent modules among the multiple modules. The terminal device can obtain module information registered in the container of the dependent module. Based on the dependency relationships and module information, the terminal device can determine the compilation result of the dependent module. In this method, since the compilation result can be used to indicate whether the dependent module can obtain the dependent module, the terminal device can accurately compile the dependent module without adding unnecessary processing logic, improving development efficiency. Furthermore, during the compilation process, the terminal device can pre-determine the dependencies between modules, thus improving the stability and reliability of the application. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of the architecture between modules provided in an embodiment of the present disclosure;

[0021] Figure 2 A flowchart illustrating a data processing method provided in an embodiment of this disclosure;

[0022] Figure 3 This is a schematic diagram illustrating a process for obtaining dependencies, provided in an embodiment of the present disclosure.

[0023] Figure 4 This is a schematic diagram illustrating a process for determining a compilation result, provided by an embodiment of the present disclosure.

[0024] Figure 5 This is a schematic diagram illustrating a method for determining compilation results provided in an embodiment of this disclosure;

[0025] Figure 6 This is a schematic diagram illustrating a process for determining a registration result, provided by an embodiment of the present disclosure.

[0026] Figure 7 A schematic diagram illustrating the process of determining the compilation result of a module that depends on another party, as provided in an embodiment of this disclosure;

[0027] Figure 8 This is a schematic diagram of a method for determining information about a container provided in an embodiment of the present disclosure;

[0028] Figure 9 This is a schematic diagram of the structure of a data processing apparatus provided in an embodiment of the present disclosure;

[0029] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this disclosure. Detailed Implementation

[0030] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0031] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0032] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the terminal device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0033] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the terminal device.

[0034] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0035] For ease of understanding, the concepts involved in the embodiments of this disclosure will be explained below.

[0036] Terminal device: A device with wireless transceiver capabilities. Terminal devices can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted. These terminal devices can be mobile phones, tablet computers, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in self-driving vehicles, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, wearable terminal devices, etc. The terminal equipment involved in the embodiments of this disclosure may also be referred to as a terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, wireless communication equipment, UE agent, or UE device, etc. The terminal equipment may also be fixed or mobile.

[0037] In related technologies, Inversion of Control (IoC) is a design methodology in software development that decouples two modules. For example, normally a dependent module needs to load the module it depends on. However, IoC allows the dependent and dependent modules to avoid direct interaction, enabling the dependent module to access the module it depends on. Currently, because the dependent module may or may not access the module it depends on, during compilation, the terminal device needs to compile both the logic for the dependent module accessing the module's logic and the logic for the dependent module not accessing the module's logic. This increases compilation complexity and consequently reduces development efficiency.

[0038] To address the technical problems in related technologies, this disclosure provides a data processing method. A terminal device can obtain the identifier of a second module to be developed and determine the dependency relationship based on the identifier of the second module. The module of the dependent party in the dependency relationship is the second module. The terminal device can obtain the module information registered in the container of the module of the dependent party and determine the first module of the dependent party corresponding to the module of the dependent party based on the dependency relationship and the module of the dependent party. The terminal device can determine the compilation result of the module of the dependent party based on the first module and the module information.

[0039] In the above method, since the dependent module in the dependency relationship is the second module to be developed, the terminal device can accurately compile the second module. Furthermore, since the compilation result can be used to indicate whether the dependent module can obtain the module it depends on, the terminal device can accurately determine the processing logic of the second module, reduce the complexity of logic processing, and improve development efficiency. Moreover, during the compilation process, since the terminal device can predetermine the dependency issues between modules, the stability and reliability of the application can be improved.

[0040] Below, in conjunction with Figure 1 The architecture between modules in the embodiments of this disclosure will be described.

[0041] Figure 1 This is a schematic diagram illustrating the architecture between modules provided in an embodiment of this disclosure. Please refer to [link / reference]. Figure 1 This includes module A and a container. The container can register modules B and C. Module A can be a dependent module, while modules B and C can be dependent modules. Due to the terminal device ( Figure 1(Not shown) It can be determined that the container has registered modules B and C. Therefore, the logic processing of module A to obtain module B can include the logic processing of module A successfully obtaining module B, and the logic processing of module A to obtain module C can include the logic processing of module A successfully obtaining module C. In this way, there is no need to generate the logic processing of module A being unable to obtain modules B and C, which reduces the complexity of compilation and thus improves the efficiency of development.

[0042] The technical solutions of this disclosure and how they solve the aforementioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0043] Figure 2 This is a schematic flowchart illustrating a data processing method provided in an embodiment of this disclosure. Please refer to [link / reference]. Figure 2 The method may include:

[0044] S201. Obtain the dependencies between multiple modules of the application.

[0045] The execution entity of this disclosure can be a terminal device or a data processing device installed in the terminal device. The data processing device can be implemented in software, or it can be implemented using a combination of software and hardware; this disclosure does not limit this approach.

[0046] The dependency relationship includes the relationship of dependencies between modules. For example, a module can be used to implement the functions of an application. For example, a module can be a module that implements music functions, a module that implements video playback functions, and a module that implements shooting functions, etc., and this disclosure does not limit this.

[0047] In this context, dependencies can indicate which modules are dependent on and which are depended upon. For example, a dependent module is one that needs to call or use the functionality, data, or interfaces of other modules, while a dependent module is one that other modules depend on, providing the functionality, data, or interfaces required by the dependent module. For instance, a dependent module can actively seek dependencies. In a web application, the user interface module might depend on the business logic module to handle user requests; in this scenario, the user interface module can be the dependent module, and the business logic module can be the dependent module.

[0048] For example, if module A needs to use the functionality or data provided by module B, there is a dependency relationship between module A and module B. Module A depends on module B, and module B is depended upon by module A. That is, module A is the dependent module, and module B is the module that is depended upon. For instance, a module implementing video playback functionality needs to load a module implementing music functionality when performing video playback. Therefore, the module implementing video playback functionality depends on the module implementing music functionality; that is, the module implementing video playback functionality is the dependent module, and the module implementing music functionality is the module that is depended upon.

[0049] Optionally, the dependencies and relationships between modules can change when implementing different functions of the application. For example, when implementing function A of the application, module 1 may depend on module 2, while when implementing function B of the application, module 2 may depend on module 1.

[0050] The terminal device can obtain dependencies using the following feasible implementation method: obtain the identifier of the second module to be developed, and determine the dependencies based on the identifier of the second module. This can accurately obtain dependencies and reduce their complexity.

[0051] The second module can be a module to be developed. For example, if the application includes module 1 and module 2, and module 1 is a module to be developed, the terminal device can determine that the second module is module 1; if module 2 is a module to be developed, the terminal device can determine that the second module is module 2. For example, when developing the music module of the application, the terminal device can determine that the module to be developed is the music module; when developing the video playback module of the application, the terminal device can determine that the module to be developed is the video playback module.

[0052] Optionally, the terminal device can determine the identifier of the second module based on business requirements. For example, the terminal device can receive business requirements sent by other devices or input business requirements into the terminal device. These business requirements can be associated with the second module, and the terminal device can determine the identifier of the second module based on these business requirements. For example, if a user develops new functions for the music module, and the business requirement is associated with the music module, the terminal device can identify the second module as the music module.

[0053] It should be noted that the terminal device may also obtain the identifier of the second module to be developed according to any feasible implementation method, and this disclosure embodiment does not limit this.

[0054] In this dependency relationship, the module that depends on the second module is the dependent module. This allows the terminal device to accurately determine the compilation result of the second module.

[0055] Optionally, the terminal device can obtain the dependency relationship of the dependent module as the second module based on the identifier of the second module. For example, the second module in dependency relationship 1 is the module of the dependent party, the second module in dependency relationship 2 is the module of the dependent party, and dependency relationship 3 does not include the dependency relationship of the second module. The dependency relationship obtained by the terminal device is dependency relationship 2.

[0056] Below, in conjunction with Figure 3 This section explains the process by which a terminal device obtains the dependencies between multiple modules of an application.

[0057] Figure 3 This is a schematic diagram illustrating a process for obtaining dependencies according to an embodiment of this disclosure. Please refer to [link / reference]. Figure 3 This includes dependency A. Dependency A includes the dependencies between modules 1, 2, 3, 4, and 5. Modules 1 and 2 are dependent modules, and modules 3, 4, and 5 are dependent modules. Modules 3 and 4 are the dependent modules of module 1, and modules 4 and 5 are the dependent modules of module 2. In the terminal device ( Figure 3 (Not shown) If the second module is determined to be module 1, the terminal device can obtain dependency B, where dependency B includes the dependencies of module 1, module 3, and module 4, and module 3 and module 4 are the dependents of module 1. In this way, the terminal device can accurately obtain the dependencies associated with the second module to be developed, improving the accuracy of dependency acquisition and reducing the complexity of dependency relationships.

[0058] S202. Obtain the module information registered in the container of the dependent module.

[0059] Module information can be used to indicate modules registered in the container. For example, if the module information indicates that module 1 and module 2 are registered in the container, then dependent modules can obtain module 1 and module 2 from the container. After a module is registered in the container, the terminal device can manage the module based on the container (e.g., module creation, configuration, and dependency injection), reducing the complexity of logic processing and improving development efficiency.

[0060] Optionally, module information can be an explicit declaration of the container. For example, during the compilation phase, the container-related code can explicitly declare the modules that can be accessed in the container. In this way, the terminal device can accurately determine the registered modules in the container based on the explicit declaration of the container, thereby improving the accuracy of compilation.

[0061] Containers can be used to manage modules. For example, since modules of dependent parties can obtain modules from a container, the container can be a container of modules, and since the modules included in the container can be modules of the dependent parties, the container can be a container of modules of the dependent parties.

[0062] S203. Based on dependency relationships and module information, determine the compilation result of the dependent modules.

[0063] The compilation result indicates whether the dependent module can access the dependent module. For example, if the dependent module can access the dependent module, its compilation result will be "Successfully accessed the dependent module." If the dependent module cannot access the dependent module, its compilation result will be "Unable to access the dependent module." For instance, if module 1 is the dependent module, and modules 2 and 3 are the dependent modules, and the dependent module can successfully access module 2 but cannot access module 3, the compilation result for module 1 will be: "Module 2 successfully accessed, module 3 failed to compile."

[0064] For example, module 1 is a dependent module, and modules 2, 3, and 4 are dependent modules. The modules registered in the container include modules 2 and 3. The terminal device can determine that module 1 can obtain modules 2 and 3 in the container, but cannot obtain module 4. Therefore, the terminal device can determine that the compilation result of module 1 is: module 2 is successfully obtained, module 3 is successfully obtained, and module 4 fails to compile.

[0065] Optionally, since dependencies can include both dependencies between modules and modules that are depended upon, when there are many modules that are depended upon, the terminal device can also filter these modules based on business requirements. For example, if module 1 is a dependent module, and the modules that are depended upon by module 1 include modules 2, 3, and 4, and the function of module 1 to be developed is related to modules 2 and 3, then during the compilation process, the terminal device can handle the dependency issues between module 1 and modules 2 and 3, without needing to handle the dependency issues between module 1 and module 4. This reduces compilation complexity and improves development efficiency.

[0066] Below, in conjunction with Figure 4 This section explains the process of determining the compilation results of modules that depend on others.

[0067] Figure 4 This is a schematic diagram illustrating a process for determining a compilation result, provided as an embodiment of this disclosure. Please refer to... Figure 4This includes: the dependent module and the container. The container contains the dependent module 1 and dependent module 2, but does not contain dependent module 3. If the dependent module obtains modules 1, 2, and 3, it can successfully obtain modules 1 and 2 from the container. However, because the container does not contain dependent module 3, the dependent module cannot obtain dependent module 3 from the container. (Terminal device) Figure 4 (Not shown) It can be determined that the compilation results of the dependent modules are: Module 1 and Module 2 were successfully acquired, while Module 3 failed to compile.

[0068] Optionally, after determining the compilation results of the dependent modules, the terminal device can also display the compilation results of the dependent modules. For example, in Figure 4 In the illustrated embodiment, the terminal device can display information that module 1 and module 2 can be successfully acquired, while module 3 will fail to compile. In this way, during the development of dependent modules, logic processing is performed for modules 1 and 2 that can be successfully acquired, and logic processing is performed for modules 3 that cannot be acquired. This can improve the accuracy and efficiency of application development.

[0069] This disclosure provides a data processing method in which a terminal device can obtain the identifier of a second module to be developed, and determine the dependency relationship of the second module based on the identifier. The terminal device can also obtain module information and determine the compilation result of the dependent module based on the dependency relationship and module information. Since the dependent module in the dependency relationship is the second module to be developed, and the compilation result can be used to indicate whether the dependent module can obtain the module it depends on, the terminal device can accurately determine the processing logic of the dependent module, reducing the complexity of logic processing and improving development efficiency. Furthermore, during the compilation process, since the terminal device can pre-determine the dependencies between modules, the stability and reliability of the application can be improved.

[0070] exist Figure 2 Based on the embodiments shown, the following, in conjunction with Figure 5 The method described above for determining the compilation result of the dependent module based on dependency relationships and container information is explained in detail.

[0071] Figure 5 This diagram illustrates a method for determining compilation results according to an embodiment of this disclosure. Please refer to... Figure 5 The method process includes:

[0072] S501. Based on dependencies and the modules of the dependent parties, determine the first module.

[0073] In this context, the first module can be the module of the dependent party corresponding to the module of the dependent party. For example, the modules indicated by the dependency relationship are module 1, module 2, and module 3, where module 1 is the module of the dependent party, and the modules of the dependent party corresponding to module 1 can be module 2 and module 3. That is, the first module can be module 2 and module 3.

[0074] Since dependencies can include both dependencies and dependent relationships between modules, once the terminal device identifies the module that depends on the module, it can accurately determine the module that the module depends on based on these dependencies. For example, the dependencies may include those between modules 1, 2, 3, and 4. Modules 1 and 2 are the modules that depend on the module, module 3 is the module that depends on module 1, and module 4 is the module that depends on module 2. If the terminal device identifies the module that depends on the module (which could be the second module to be developed) as module 1, then the terminal device can identify the first module as module 3. If the terminal device identifies the module that depends on the module as module 2, then the terminal device can identify the first module as module 4.

[0075] S502. Based on the first module and module information, determine the compilation result of the dependent module.

[0076] The terminal device can determine the compilation result of the dependent module based on the following feasible implementation: based on the module information, determine the registration result of the first module in the container, and based on the registration result, determine the compilation result of the dependent module.

[0077] The registration result can be either that the first module is registered in the container, or that the first module is not registered in the container. For example, if the first module is registered in the container, it means that the dependent module can obtain the first module in that container; if the first module is not registered in the container, it means that the dependent module cannot obtain the first module in that container.

[0078] Optionally, the module information registered in the container may include the modules registered in the container. Therefore, the terminal device can determine the registration result of the first module in the container based on this module information. For example, if the module information registered in the container is: module 1, module 2, and module 3 are registered in the container, and the first module corresponding to the dependent module is module 2, then the registration result of the first module is that it is registered in the container. If the first module corresponding to the dependent module is module 4, then the registration result of the first module is that it is not registered in the container.

[0079] Below, in conjunction with Figure 6 The process of determining the registration result of the first module in the container is explained.

[0080] Figure 6This is a schematic diagram illustrating a process for determining a registration result, as provided in an embodiment of this disclosure. Please refer to [link / reference]. Figure 6 This includes: a container. The container contains registered modules 1, 2, and 3. If the terminal device ( Figure 6 If the terminal device determines that the first module corresponding to the dependent module is module 1, then the terminal device can determine that the registration result for this first module is that the first module is registered in the container. If the terminal device determines that the first module corresponding to the dependent module is module 4, then the terminal device can determine that the registration result for this first module is that the first module is not registered in the container. In this way, the terminal device can accurately determine whether the dependent module corresponding to the dependent module is registered in the container, thereby improving the accuracy of development.

[0081] Specifically, for any first module, the terminal device determines the compilation result of the dependent module based on the registration result. Specifically, if the registration result is that the first module is registered in the container, the terminal device determines that the dependent module can obtain the first module. If the registration result is that the first module is not registered in the container, the terminal device determines that the dependent module cannot obtain the first module.

[0082] Since terminal devices can manage modules based on containers, dependent modules can access registered modules within the container. However, dependent modules cannot access unregistered modules within the container. Thus, based on the compilation results of dependent modules, terminal devices can accurately determine the dependency issues involved in dependent modules. Therefore, users can resolve dependency issues during the compilation process, improving the stability and reliability of the application.

[0083] Below, in conjunction with Figure 7 This section explains the process of determining the compilation results of modules that depend on others.

[0084] Figure 7 This is a schematic diagram illustrating a process for determining the compilation result of a module that depends on another module, as provided in an embodiment of this disclosure. Please refer to [link to relevant documentation]. Figure 7 This includes dependencies and a container. Dependencies include those between module 1, module 4, and module 5. Module 4 is a dependent module, and the modules it depends on are module 1 and module 5. The registered modules in the container include module 1, module 2, and module 3.

[0085] Please see Figure 7 Terminal equipment ( Figure 7(Not shown) The registration result of the dependent module corresponding to module 4 in the container can be determined. Module 1 is registered, and module 5 is not registered. The terminal device can determine the compilation result of module 4 based on the registration result. The compilation result of module 4 includes: module 1 successfully acquired, and module 4 compilation failed. In this way, the user can accurately determine the processing logic of module 4 based on the compilation result, and can pre-determine dependencies between modules, improving the stability of the application.

[0086] This disclosure provides a method for determining compilation results. A terminal device can determine the first module of the dependent party associated with the module of the dependent party based on dependency relationships. Based on module information, it determines the registration result of the first module in the container. If the registration result shows that the first module is registered in the container, the terminal device determines that the compilation result of the dependent party's module indicates that the dependent party's module can obtain the first module. If the registration result shows that the first module is not registered in the container, the terminal device determines that the compilation result of the dependent party's module indicates that the dependent party's module has failed to obtain the first module. In this way, the terminal device can accurately determine whether a dependent party's module can obtain the module of the dependent party based on the modules already registered in the container. Therefore, users can optimize the logic processing of the dependent party's module, reduce the complexity of the logic processing, and improve development efficiency. Furthermore, the terminal device can accurately determine the dependency issues between modules based on the compilation results, thereby improving the reliability and stability of the application.

[0087] Based on any of the above embodiments, the above data processing method further includes a method for determining module information. Below, in conjunction with... Figure 8 The method for determining container information is explained in detail.

[0088] Figure 8 This diagram illustrates a method for determining container information according to an embodiment of this disclosure. Please refer to... Figure 8 ,include:

[0089] S801, Explicitly declare the third module that can be accessed in the container.

[0090] Optionally, the third module can be a module that is available in the container. For example, it can be specified in the code or configuration file that the third module can be loaded or imported into the container. This explicit declaration approach can improve the clarity and maintainability of the code or configuration file. For example, the terminal device can specify in the code that module 1, module 2, and module 3 can be loaded or imported into the container. In this way, the terminal device can determine that module 1, module 2, and module 3 are available in the container.

[0091] Optionally, the terminal device may explicitly declare the third module that can be obtained in the container based on any feasible implementation method, and this disclosure embodiment does not limit this.

[0092] S802. Register the third module in the container and determine the module information.

[0093] Optionally, after the terminal device obtains the third module that can be obtained from the explicitly declared container, it can implement the container. For example, if the terminal device explicitly declares that module 1 and module 2 can be obtained from the container, then the terminal device can implement the container, that is, the terminal device registers module 1 and module 2 in the container.

[0094] Optionally, after registering a third module in the container, the terminal device can determine the module information registered in the container based on the registered third module. For example, if the terminal device registers module 1 and module 2 in the container, the terminal device can determine that the module information is: the container includes module 1 and module 2.

[0095] Optionally, after explicitly declaring the third module that can be obtained in the container, the terminal device determines the module information registered in the container based on the content of the explicit declaration. For example, if the terminal device explicitly declares that module 1 and module 2 can be obtained in the container, the terminal device can determine the content of the explicit declaration as the module information, that is, the module information is that module 1 and module 2 can be obtained in the container.

[0096] This disclosure provides a method for determining container information. A terminal device can explicitly declare third modules that can be accessed within the container, register these third modules in the container, and determine the module information. In this way, the terminal device can accurately determine module information based on the explicitly declared content. Furthermore, during compilation, the terminal device can pre-determine the modules that can be accessed within the container based on the module information, thereby reducing the complexity of logical processing and accurately identifying dependencies between modules, thus improving the stability and reliability of the application.

[0097] Figure 9 This is a schematic diagram of a data processing apparatus provided in an embodiment of this disclosure. Please refer to [link / reference]. Figure 9 The data processing device 900 includes a first acquisition module 901, a second acquisition module 902, and a determination module 903, wherein:

[0098] The first acquisition module 901 is used to acquire the dependency relationships between multiple modules of the application, wherein the dependency relationships indicate the dependent modules and the dependent modules among the multiple modules;

[0099] The second acquisition module 902 is used to acquire module information registered in the container of the module of the dependent party;

[0100] The determining module 903 is used to determine the compilation result of the dependent module based on the dependency relationship and the module information. The compilation result is used to indicate whether the dependent module can obtain the module of the dependent party.

[0101] According to one or more embodiments of this disclosure, the determining module 903 is specifically used for:

[0102] Based on the dependency relationship and the module of the dependent party, a first module is determined, wherein the first module is the module of the dependent party corresponding to the module of the dependent party;

[0103] Based on the information of the first module and the module, the compilation result of the dependent module is determined.

[0104] According to one or more embodiments of this disclosure, the determining module 903 is specifically used for:

[0105] Based on the module information, the registration result of the first module in the container is determined, wherein the registration result is that the first module is registered in the container, or that the first module is not registered in the container;

[0106] Based on the registration results, the compilation results of the dependent module are determined.

[0107] According to one or more embodiments of this disclosure, the determining module 903 is specifically used for:

[0108] If the registration result is that the first module is registered in the container, it is determined that the compilation result of the dependent module is that the dependent module can obtain the first module;

[0109] If the registration result indicates that the first module is not registered in the container, it is determined that the compilation result of the dependent module is that the dependent module failed to obtain the first module.

[0110] According to one or more embodiments of this disclosure, the first acquisition module 901 is specifically used for:

[0111] Obtain the identifier of the second module to be developed;

[0112] Based on the identifier of the second module, the dependency relationship is determined, and the module that depends on the second module is the dependent module in the dependency relationship.

[0113] According to one or more embodiments of this disclosure, the second acquisition module 902 is further configured to:

[0114] Explicitly declare any third modules that can be accessed within the container;

[0115] Register the third module in the container and determine the module information.

[0116] According to one or more embodiments of this disclosure, the data processing apparatus 900 further includes a display module 904, the display module 904 being used for:

[0117] Displays the compilation results of the dependent module.

[0118] The data processing apparatus provided in this embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.

[0119] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this disclosure. Please refer to [link / reference]. Figure 10 The diagram illustrates a structural schematic suitable for implementing the terminal device 1000 of the embodiments of the present disclosure. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), tablet computers, portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 10 The terminal device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0120] like Figure 10 As shown, the terminal device 1000 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for the operation of the terminal device 1000. The processing unit 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0121] Typically, the following devices can be connected to the I / O interface 1005: input devices 1006 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1008 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows terminal device 1000 to exchange data via wireless or wired communication with other devices. Although Figure 10 A terminal device 1000 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0122] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure 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 flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 1009, or installed from storage device 1008, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of embodiments of this disclosure.

[0123] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. 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 disclosure, 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 disclosure, 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. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, 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: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0124] The aforementioned computer-readable medium may be included in the aforementioned terminal device; or it may exist independently and not assembled into the terminal device.

[0125] The aforementioned computer-readable medium carries one or more programs, which, when executed by the terminal device, cause the terminal device to perform the method shown in the above embodiments.

[0126] This disclosure provides a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements various methods that may be involved in the above embodiments.

[0127] This disclosure provides a computer program product, including a computer program that, when executed by a processor, implements various methods that may be involved in the above embodiments.

[0128] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0129] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. 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 consecutively indicated blocks may actually be executed substantially in parallel, and 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 function or operation, or using a combination of dedicated hardware and computer instructions.

[0130] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0131] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0132] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, 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 devices, magnetic storage devices, or any suitable combination of the foregoing.

[0133] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0134] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0135] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and provisions. The data may include information, parameters and messages, such as flow switching indication information.

[0136] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure 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 above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0137] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain environments. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely exemplary forms of implementing the claims.

Claims

1. A data processing method, characterized in that, include: Obtain the dependencies between multiple modules of the application, wherein the dependencies indicate the dependent modules and the modules that are depended upon among the multiple modules; Obtain the module information registered in the container of the module of the dependent party; Based on the dependency relationship and the module information, the compilation result of the dependent module is determined, and the compilation result is used to indicate whether the dependent module can obtain the module of the dependent party.

2. The method according to claim 1, characterized in that, The process of determining the compilation result of the dependent module based on the dependency relationship and the container information includes: Based on the dependency relationship and the module of the dependent party, a first module is determined, wherein the first module is the module of the dependent party corresponding to the module of the dependent party; Based on the information of the first module and the module, the compilation result of the dependent module is determined.

3. The method according to claim 2, characterized in that, The step of determining the compilation result of the dependent module based on the first module and the module information includes: Based on the module information, the registration result of the first module in the container is determined, wherein the registration result is that the first module is registered in the container, or that the first module is not registered in the container; Based on the registration results, the compilation results of the dependent module are determined.

4. The method according to claim 3, characterized in that, For any first module; determining the compilation result of the dependent module based on the registration result includes: If the registration result is that the first module is registered in the container, it is determined that the compilation result of the dependent module is that the dependent module can obtain the first module; If the registration result indicates that the first module is not registered in the container, it is determined that the compilation result of the dependent module is that the dependent module failed to obtain the first module.

5. The method according to any one of claims 1-4, characterized in that, The acquisition of dependencies includes: Obtain the identifier of the second module to be developed; Based on the identifier of the second module, the dependency relationship is determined, and the module that depends on the second module is the dependent module in the dependency relationship.

6. The method according to any one of claims 1-4, characterized in that, Before obtaining the module information registered in the container of the dependent module, the method further includes: Explicitly declare any third modules that can be accessed within the container; Register the third module in the container and determine the module information.

7. The method according to any one of claims 1-4, characterized in that, After determining the compilation result of the module that depends on the other party, the method further includes: Displays the compilation results of the dependent module.

8. A data processing apparatus, characterized in that, It includes a first acquisition module, a second acquisition module, and a determination module, wherein: The first acquisition module is used to acquire the dependency relationships between multiple modules of the application, wherein the dependency relationships indicate the dependent modules and the dependent modules among the multiple modules; The second acquisition module is used to acquire module information registered in the container of the module of the dependent party; The determining module is used to determine the compilation result of the dependent module based on the dependency relationship and the module information. The compilation result is used to indicate whether the dependent module can obtain the module of the dependent party.

9. A terminal device, characterized in that, include: Processor and memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the data processing method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the data processing method as described in any one of claims 1-7.

11. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the data processing method as described in any one of claims 1-7.

Images