CN116185441A

CN116185441A - Management method, device, equipment and medium of function module

Info

Publication number: CN116185441A
Application number: CN202111438339.6A
Authority: CN
Inventors: 陈燃
Original assignee: BYD Co Ltd
Current assignee: BYD Co Ltd
Priority date: 2021-11-29
Filing date: 2021-11-29
Publication date: 2023-05-30

Abstract

The application discloses a method, a device, equipment and a medium for managing a functional module, wherein the method comprises the following steps: acquiring a first function module corresponding to a new function to be added and at least one second function module stored in a current data linked list, wherein an API interface for executing the new function is packaged in the first function module; analyzing the connection pointers in the first functional module and each second functional module; by using the connection pointer to create a new function module linked list comprising the first function module and at least one second function module, when the system needs to add a new function, the system function can be updated through updating the module linked list without re-adapting the original system function and only by packaging the API interface with the new function into the function module.

Description

Management method, device, equipment and medium of function module

Technical Field

The present disclosure relates generally to the field of computers, and in particular, to the field of module invoking techniques, and more particularly, to a method, apparatus, device, and medium for managing a functional module.

Background

In the architecture strategy called by the existing singlechip module, the integration level of the system and the module is higher, namely, the system function and the module function are mixed together, so that the whole framework is poorer in modifiable, and when some functions need to be deleted, added or modified, the whole system needs to be modified, and the efficiency of developing and modifying the system is seriously influenced.

Disclosure of Invention

In view of the foregoing drawbacks or shortcomings in the prior art, it is desirable to provide a method, apparatus, device, and medium for managing a functional module, where the functional module is packaged into an independent node, so as to effectively improve development and maintenance efficiency.

In a first aspect, an embodiment of the present application provides a method for managing a functional module, including:

acquiring a first function module corresponding to a new function to be added and at least one second function module stored in a current data linked list, wherein an API interface for executing the new function is packaged in the first function module;

analyzing the connection pointers in the first functional module and each second functional module;

and creating a new function module linked list comprising the first function module and the at least one second function module by using the connection pointer.

In a second aspect, an embodiment of the present application provides a management apparatus for a functional module, including:

the system comprises an acquisition module, a first data link list and a second data link list, wherein the acquisition module is used for acquiring a first function module corresponding to a new function to be added and at least one second function module stored in the current data link list, and an API interface for executing the new function is packaged in the first function module;

the analysis module is used for analyzing the connection pointers in the first functional module and each second functional module;

and the creation module is used for creating a new function module linked list comprising the first function module and the at least one second function module by using the connection pointer.

In a third aspect, embodiments of the present application provide an electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a method as described in embodiments of the present application when the program is executed.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method as described in embodiments of the present application.

According to the method and the system, when a new function is required to be added to the system, the original system function is not required to be re-adapted, and the system function can be updated through updating of a module linked list only by packaging an API interface with the new function into a functional module.

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.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:

fig. 1 is a flowchart of a method for managing a functional module according to an embodiment of the present application;

fig. 2 is a schematic diagram of a management principle of a functional module according to an embodiment of the present application;

FIG. 3 is a flowchart of another method for managing a functional module according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of a method for managing a function module according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for managing a further function module according to an embodiment of the present application;

FIG. 6 is a flowchart of a method for managing a further function module according to an embodiment of the present application;

fig. 7 is a schematic block diagram of a management device of a functional module according to an embodiment of the present application;

FIG. 8 is a block diagram of a management device of another functional module according to an embodiment of the present application;

fig. 9 shows a schematic diagram of a computer system suitable for use in implementing an electronic device or server of an embodiment of the present application.

Detailed Description

The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the invention are shown in the drawings.

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

Fig. 1 is a flowchart of a method for managing a functional module according to an embodiment of the present application.

As shown in fig. 1, the method for managing a functional module in the embodiment of the present application includes the following steps:

step 101, a first function module corresponding to a new function to be added and at least one second function module stored in a current data link list are obtained, and an API interface for executing the new function is packaged in the first function module.

It should be noted that, the system function is implemented through the API interface in the function module, and multiple function modules for implementing the function are stored in the system in the form of a data link table, and when the function needs to be added to the system, the system function is added in the form of adding the function module to the current data link table.

Optionally, the number of the function modules in the current system may be detected in real time, or each function module in the system may be continuously polled, and when a function module belonging to a data link list outside the current system is identified, the function module is determined to be the first function module corresponding to the new function to be added.

Or receiving an operation instruction for adding the new function module, and inquiring the first function module corresponding to the new function to be added according to the operation instruction for adding the new module.

And 102, analyzing the connection pointers in the first functional module and each second functional module.

It should be noted that, the connection pointer is encapsulated in the functional module, and the connection pointer in the first functional module and the connection pointer in the second functional module are obtained by analyzing the functional module, so that the relative position between the first functional module and each second functional module, that is, the insertion position of the first functional module, is determined by using the connection pointer.

Step 103, creating a new function module linked list comprising the first function module and at least one second function module by using the connection pointer.

As shown in fig. 2, the function linked list ends with Null pointer Null, and the connection pointer connecting the function modules is a Next function.

Specifically, in the management method of the function module provided in the embodiment of the present application, when a first function module including a new function API interface is obtained, at least one second function module stored in a current data link table is obtained, then a connection pointer in the first function module and each second function module is parsed, and a new function module link table including the first function module and at least one second function module is created by using the connection pointer.

Therefore, when the system needs to add a new function, the system function can be updated through updating the module linked list without re-adapting the original system function and only packaging the API interface with the new function into the functional module.

And moreover, through independently packaging the functional modules comprising the API interface, a plurality of functional modules can be independently and parallelly developed, so that the overall development efficiency of the system is improved, meanwhile, the functional modules are stored in a mode of a module linked list, the independence among the functional modules is effectively improved, the mutual influence among the functional modules is reduced, and the convenience of independent maintenance of the functional modules is improved.

In one or more embodiments, as shown in fig. 3, step 101, obtaining a first function module corresponding to a new function to be added includes:

step 1011, obtaining at least one API corresponding to the new function and a first logic timing sequence of the at least one API.

Further, obtaining at least one API interface corresponding to the new function includes: splitting the functional requirement into at least one base function; and creating an API interface corresponding to the basic function according to each basic function.

Before the first functional module is created, the functions required to be implemented need to be developed according to the functional requirements of development, that is, API development of the basic functions. This process is the most important process in the development of system functions, and the implementation of some basic functions that the functional module should pay attention to when calling needs to be considered, so that the functions of the module have more dependence on such basic functions.

Step 1012, encapsulating the at least one API interface into a functional function according to the first logic timing.

The first logic sequence is a priority sequence of each API interface in the first functional module, for example, a step sequence priority in a step-by-step calling logic sequence, or a calling frequency priority in a calling frequency logic sequence, etc.

Specifically, each API interface for realizing the basic function is packaged into a function according to the function requirement and the logic time sequence called in steps. Wherein the function can realize a complex function through the step operation of the basic function.

Step 1013, a first pointer corresponding to the function and a connection pointer corresponding to the first function module are obtained.

The first pointer corresponding to the function is a pointer of an API interface storage address packaged in the first pointer.

Step 1014 encapsulates the function, the first pointer and the connection pointer into a first function module.

It should be appreciated that for a function module, a connection pointer is used to determine the location of the function module in a data link list, a function encapsulates an API interface to perform the called API interface function when called, and a first pointer function is used to indicate the storage location of the function.

Optionally, when the functional module is packaged, the first pointer corresponding to the core function of the functional module can be packaged in front, so that the calling efficiency of other functional modules to the functional module is conveniently improved. Or when the function cannot be used in the function module, the first pointer corresponding to the function needs to be assigned as Null, so that the error of the system caused by the pointer which cannot be executed is avoided. When the function is packaged in the function module, the function is only used for backup or non-called function, and can be regarded as a function which cannot be used.

Optionally, the functional module may further include an initialization pointer, a feature parameter variable, etc. for initializing the functional module, so as to meet all the functional requirements of the functional module.

It should be further understood that, in the embodiment of the present application, in the creation process of the first functional module corresponding to the new function, the working state of the second functional module in the previous system does not need to be concerned, and only the creation needs to be performed according to the new function to be added.

In one or more embodiments, as shown in FIG. 4, step 103, creating a new function module linked list comprising the first function module and at least one second function module using the connection pointer, comprises:

step 1031, obtaining a second logic time sequence corresponding to the first functional module.

The second logic time sequence corresponding to the first functional module is a logic relationship between the first functional module and the second functional module, for example, when the first functional module is a linkage module or a lower layer module of a certain second functional module, the logic time sequence of the first functional module is the next of the second functional module.

Step 1032, inserting the first connection pointer corresponding to the first functional module into the connection pointer chain according to the second logic sequence to form a new connection pointer chain.

Step 1033, connecting the first functional module and at least the second functional module into a new linked list of functional modules according to the new connection pointer.

That is, as shown in fig. 2, the logic sequence corresponding to the first functional module is next to the nth functional module, and therefore, the first functional module is inserted to the right of the nth functional module to become the n+1th functional module.

It should be understood that the logic sequence corresponding to the first functional module may be the preceding or the following, and may be determined according to the corresponding function implemented by the first functional module.

In one or more embodiments, each function module in the new function module linked list has a first identifier, each API interface in the function module has a second identifier, the method further comprising: when a call instruction for a target API interface is received, inquiring a target identifier corresponding to the target API interface, wherein the target identifier comprises a first target identifier corresponding to a target functional module comprising the target API interface and a second target identifier corresponding to the target API interface; and calling a target API interface in the target function module according to the target identifier.

The first identifier may be a handle or an ID number preset by the system for the functional module, and the second identifier may be a handle or an ID number preset by the system for an API interface in the functional module.

That is, when the system calls the API interface in the functional module, the system queries, according to the call instruction, a first target identifier corresponding to the functional module to which the target API interface to be called belongs and a second target identifier corresponding to the target API interface to be called, and then sequentially determines, according to the first target identifier and the second target identifier, the functional module to which the target API interface belongs and the target API interface, so as to call the target API interface.

Therefore, the API interface is called through the identification information of the API interface, so that the error rate of calling the API interface can be effectively reduced, and the calling efficiency of the API interface is improved.

Further, the call instruction is a linkage call instruction, and the method further includes: receiving a first calling instruction for calling a first target API interface; identifying a second target API interface linked with the first target API interface according to a pre-stored association relation; respectively inquiring a second target identifier corresponding to the first target API interface and a second target identifier corresponding to the second target API interface; and calling a second target API interface according to a second target identifier corresponding to the second target API interface after calling the first target API interface according to the first target identifier corresponding to the first target API interface.

It should be noted that, the linkage call instruction is to perform a call to another API interface when a call to a certain API interface is performed, for example, in the intelligent home system, the door opening may be linked with the lamp opening, that is, when the intelligent home system performs the door opening function, the lamp opening function is performed at the same time.

Specifically, after a first call instruction for calling the first target API interface is received, identifying a second target API interface linked with the first target API interface according to a pre-stored association relation, namely, although only the first call instruction for calling the first target API interface is received, actually receiving the first call instruction for calling the first target API interface and the second call instruction for calling the second target API interface at the same time, then querying a second target identifier corresponding to the first target API interface and a second target identifier corresponding to the second target API interface according to the first call instruction and the second call instruction respectively, and calling the second target API interface according to the second target identifier corresponding to the second target API interface after calling the first target API interface according to the second target identifier corresponding to the first target API interface, so that the association call between linked API interfaces is effectively realized.

In one or more embodiments, identifying the presence of an abnormal function module in the new function module linked list; and (5) independently maintaining the abnormal function module.

In particular, in the actual maintenance process, a special group can be established according to each functional module to be responsible for research and development and maintenance, the research and development cost is low, and the code quantity is relatively small. In addition, as for maintaining each functional module by independent small-component workers, the maintenance difficulty is low, if the problem is found, the abnormal functional module can be quickly positioned, and the problem checking efficiency is higher.

As a specific embodiment, as shown in fig. 5, the method for managing a functional module includes the following steps:

step 201, splitting the functional requirement into a plurality of basic functions.

Step 202, creating an API interface corresponding to the basic function according to each basic function.

Step 203, packaging the API interface into a functional function according to the first logic time sequence.

Step 204, creating a function module according to the function, the first pointer corresponding to the function and the connection pointer.

Step 205, it is determined whether a new function needs to be added.

If so, then step 206 is performed; if not, step 207 is performed.

Step 206, determining whether the new function depends on the existing basic function.

If yes, go to step 203; if not, step 202 is performed.

Step 207, performing independent maintenance on the functional modules.

As a possible embodiment, as shown in fig. 6, at the time of the initial start-up of the system, the management method of the functional module includes the following steps:

step 301, the system is guided to start working through Boot program.

Step 302, traversing all functional modules in the data segment.

Traversing from the initial position of the data segment, and determining the next traversed functional module according to the connection pointer in each functional module until the connection pointer of the current functional module is Null.

And 303, creating a current module linked list of the functional modules obtained through traversing according to the sequence of the connection pointers.

Thus, the initialization of the module linked list in the system is realized, namely, the first current module linked list is generated.

Step 304, initializing each function module in the current module linked list.

Step 305, when receiving a call instruction to the target API interface, querying a target identifier corresponding to the target API interface.

And step 306, calling a target API interface in the target function module according to the target identification.

In summary, when the system needs to add a new function, the application can update the system function through updating the module linked list without re-adapting the original system function and only packaging the API interface with the new function into the functional module.

It should be noted that although the operations of the method of the present invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in that particular order or that all of the illustrated operations be performed in order to achieve desirable results.

Fig. 7 is a schematic block diagram of a management apparatus for a functional module according to an embodiment of the present application. As shown in fig. 7, the management apparatus 10 of the functional module according to the embodiment of the present application includes:

the obtaining module 11 is configured to obtain a first function module corresponding to a new function to be added and at least one second function module stored in a current data link table, where an API interface for executing the new function is encapsulated in the first function module;

a parsing module 12, configured to parse the connection pointers in the first functional module and each of the second functional modules;

a creating module 13, configured to create a new function module linked list including the first function module and the at least one second function module using the connection pointer.

In some embodiments, the obtaining module 11 is further configured to:

acquiring at least one API interface corresponding to the new function and a first logic time sequence of the at least one API interface;

encapsulating at least one API interface into a function according to the first logic time sequence;

acquiring a first pointer corresponding to the function and the connection pointer corresponding to the first function module;

and packaging the function, the first pointer and the connection pointer into the first function module.

In some embodiments, the obtaining module 11 is further configured to:

splitting the functional requirement into at least one base function;

and creating the API interface corresponding to the basic function according to each basic function.

In some embodiments, the creation module 13 is further configured to:

acquiring a second logic time sequence corresponding to the first functional module;

inserting a first connection pointer corresponding to the first functional module into the connection pointer chain according to the second logic time sequence to form a new connection pointer chain;

and connecting the first functional module and at least one second functional module into a new functional module linked list according to a new connection pointer chain.

In some embodiments, as shown in fig. 8, the management apparatus 10 of a function module further includes a calling module 14, each of the function modules in the new function module linked list has a first identifier, each of the API interfaces in the function module has a second identifier, and the calling module 14 is further configured to:

when a call instruction for a target API interface is received, inquiring a target identifier corresponding to the target API interface, wherein the target identifier comprises a first target identifier corresponding to a target functional module comprising the target API interface and a second target identifier corresponding to the target API interface;

and calling the target API interface in the target functional module according to the target identifier.

In some embodiments, the calling module 14 is further configured to:

receiving a first calling instruction for calling a first target API interface;

identifying a second target API interface linked with the first target API interface according to a pre-stored association relation;

respectively inquiring a second target identifier corresponding to the first target API interface and a second target identifier corresponding to the second target API interface;

and calling the second target API interface according to a second target identifier corresponding to the second target API interface after calling the first target API interface according to the second target identifier corresponding to the first target API interface.

In some embodiments, the management device 10 of the functional module further includes a maintenance module 15, where the maintenance module 15 is configured to:

identifying abnormal function modules in the new function module linked list;

and carrying out independent maintenance on the abnormal function modules.

It should be understood that the elements or modules depicted in the apparatus 10 correspond to the various steps in the method described with reference to fig. 1. Thus, the operations and features described above with respect to the method are equally applicable to the apparatus 10 and the units contained therein and are not described in detail herein. The apparatus 10 may be implemented in advance in a browser or other security application of the electronic device, or may be loaded into the browser or security application of the electronic device by means of downloading or the like. The corresponding units in the apparatus 10 may cooperate with units in an electronic device to implement aspects of embodiments of the present application.

The division of the modules or units mentioned in the above detailed description is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

It should be noted that, for details not disclosed in the management device of the functional module in the embodiment of the present application, please refer to details disclosed in the foregoing embodiments of the present application, and details are not repeated herein.

Referring now to fig. 9, fig. 9 shows a schematic diagram of a computer system suitable for use in implementing an electronic device or server of an embodiment of the present application,

as shown in fig. 9, the computer system includes a Central Processing Unit (CPU) 901, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM903, various programs and data required for operation instructions of the system are also stored. The CPU901, ROM902, and RAM903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

The following components are connected to the I/O interface 905; an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

In particular, according to embodiments of the present application, the process described above with reference to flowchart fig. 2 may be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program contains program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. When the computer program is executed by a Central Processing Unit (CPU) 901, the above-described functions defined in the system of the present application are performed.

It should be noted that the computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation instructions of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, blocks shown in two separate connections may in fact be performed substantially in parallel, or they may sometimes be performed in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units or modules described in the embodiments of the present application may be implemented by software, or may be implemented by hardware. The described units or modules may also be provided in a processor, for example, as: a processor includes an acquisition module, an parsing module, and a creation module. The names of these units or modules do not in some cases limit the unit or module itself, for example, the acquisition module may also be described as "acquiring a first function module corresponding to a new function to be added and at least one second function module stored in the current data link table, where the first function module encapsulates an API interface for executing the new function".

As another aspect, the present application also provides a computer-readable storage medium that may be included in the electronic device described in the above embodiment or may exist alone without being incorporated into the electronic device. The computer-readable storage medium stores one or more programs that when executed by one or more processors perform the methods of managing the functional modules described herein.

The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the disclosure. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.

Claims

1. A method for managing a functional module, comprising:

2. The method of claim 1, wherein the obtaining a first function module corresponding to a new function to be added further comprises:

3. The method according to claim 2, wherein said obtaining at least one of said API interfaces corresponding to said new function comprises:

splitting the functional requirement into at least one base function;

4. The method of claim 1, wherein creating a new function module linked list comprising the first function module and the at least one second function module using the connection pointer comprises:

5. The method of claim 1, wherein each function module in the new function module linked list has a first identifier and each API interface in the function module has a second identifier, the method further comprising:

6. The method of claim 5, wherein the call instruction is a ganged call instruction, the method further comprising:

receiving a first calling instruction for calling a first target API interface;

7. The method according to claim 1, wherein the method further comprises:

identifying abnormal function modules in the new function module linked list;

and carrying out independent maintenance on the abnormal function modules.

8. A management device for a functional module, comprising:

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements a method for managing functional modules according to any of claims 1-7 when executing the program.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a method of managing functional modules according to any of claims 1-7.