1. A method for managing component information, comprising:

searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

determining an obtaining mode for obtaining the dependent component based on the search result, and obtaining the dependent component;

and respectively storing the dependent component and the component to be managed into a repository matched with respective basic information, wherein the type of the component stored in the repository is different from that of the component stored in the component library.

2. The method of claim 1, wherein the base information further comprises location information; the determining, based on the search result, an obtaining manner of obtaining the dependent component and obtaining the dependent component includes:

when the search result is not searched, the obtaining mode is to obtain the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

3. The method of claim 1 or 2, wherein the repository comprises a first repository and a second repository; the storing the dependent component and the component to be managed into the repository matched with the respective basic information respectively includes:

storing the obtained dependent component to the second repository;

storing the component to be managed to the first repository; the first storage library and the second storage library are respectively used for storing different types of components.

4. The method of claim 1, further comprising:

taking the component to be managed as a current component, determining at least one dependent component related to the current component, and performing topological operation on the current component and the at least one dependent component to form a current topological relation;

taking each dependent component in the at least one dependent component as a current component respectively, and executing the topological operation to form a new current topological relation;

and forming a target topological relation of the component to be managed and a dependent component related to the component to be managed based on at least one topological relation.

5. The method of claim 4, wherein the base information further includes update information, and wherein the method further comprises:

determining a component to be updated from all components to be managed and dependent components of the components to be managed, which have topological relations, according to the updating information;

acquiring a target dependent component of the component to be updated from a third repository according to the update information of the component to be updated, wherein the type of the component stored in the third repository is different from that of the component stored in the component library;

and updating the component to be updated according to the target dependent component.

6. An apparatus for managing component information, comprising:

the searching unit is used for searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

the determining and obtaining unit is used for determining an obtaining mode for obtaining the dependent component based on a search result and obtaining the dependent component;

and the storage unit is used for respectively storing the dependent component and the component to be managed into a storage library matched with respective basic information, and the storage library and the component library are different in stored component type.

7. The apparatus of claim 6, wherein the base information further comprises location information;

the determination and acquisition unit is further configured to: when the search result is not searched, the obtaining mode is to obtain the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

8. The apparatus of claim 6 or 7, wherein the repository comprises a first repository and a second repository;

the storage unit is further configured to: storing the obtained dependent component to the second repository; storing the component to be managed to the first repository; the first storage library and the second storage library are respectively used for storing different types of components.

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method of any of the preceding claims 1 to 5 are implemented when the computer program is executed by the processor.

10. A computer readable medium having stored thereon machine executable instructions which, when invoked and executed by a processor, cause the processor to perform the method of any of claims 1 to 5.

Background

The existing enterprises pay attention to knowledge precipitation and achievement transformation, and under the guidance of the environment, componentization of a technical middle station, a business middle station, a large front end, a small front end and a data middle station is popular among enterprises and technical personnel. Thus, there are more components, versions, media, devices, SDKs, devices, runtime environment configurations to manage.

At present, the management mode of the component information still stays at the level of the verbal delivery or the document delivery (for example, the upgrading of the component A needs to depend on the component B, and the repository information of the component A and the component B is informed to the personnel who upgrade the component A in the form of the verbal delivery or the document), and the existing business system is complex, often containing many components, each requiring a different organization, department, team to maintain (e.g., components of a technical desk, requiring personnel of the technical desk to maintain in verbal delivery or documentation), labor intensive, time costly, and in addition, according to the requirements, research personnel can derive different component versions for the components, and the conventional component information management method cannot clearly and accurately determine the version information of the lower-end component on which the upper-end component is upgraded; in addition, when the business system is upgraded, oral handover or document transfer of information of different components needs to be performed across organizations and departments and across teams, the overall view cannot be snooped, the error rate is high, repeated adjustment and modification are needed, the business system is difficult to upgrade, and the research and development efficiency is low.

In conclusion, the existing component information management method has the problems of high cost, low efficiency and easy error.

Disclosure of Invention

In view of the above, an object of the present invention is to provide a method and an apparatus for managing component information, and an electronic device, so as to alleviate the technical problems of high cost, low efficiency, and error proneness of the existing component information management method.

In a first aspect, an embodiment of the present invention provides a method for managing component information, including:

searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

determining an obtaining mode for obtaining the dependent component based on the search result, and obtaining the dependent component;

and respectively storing the dependent component and the component to be managed into a repository matched with respective basic information, wherein the type of the component stored in the repository is different from that of the component stored in the component library.

Further, the basic information further includes location information; the determining, based on the search result, an obtaining manner of obtaining the dependent component and obtaining the dependent component includes:

when the search result is not searched, the obtaining mode is to obtain the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

Further, the repository comprises a first repository and a second repository; the storing the dependent component and the component to be managed into the repository matched with the respective basic information respectively includes:

storing the obtained dependent component to the second repository;

storing the component to be managed to the first repository; the first storage library and the second storage library are respectively used for storing different types of components.

Further, the method further comprises:

taking the component to be managed as a current component, determining at least one dependent component related to the current component, and performing topological operation on the current component and the at least one dependent component to form a current topological relation;

taking each dependent component in the at least one dependent component as a current component respectively, and executing the topological operation to form a new current topological relation;

and forming a target topological relation of the component to be managed and a dependent component related to the component to be managed based on at least one topological relation.

Further, the basic information further includes update information, and the method further includes:

determining a component to be updated from all components to be managed and dependent components of the components to be managed, which have topological relations, according to the updating information;

acquiring a target dependent component of the component to be updated from a third repository according to the update information of the component to be updated, wherein the type of the component stored in the third repository is different from that of the component stored in the component library;

and updating the component to be updated according to the target dependent component.

In a second aspect, an embodiment of the present invention further provides a device for managing component information, including:

the searching unit is used for searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

the determining and obtaining unit is used for determining an obtaining mode for obtaining the dependent component based on a search result and obtaining the dependent component;

and the storage unit is used for respectively storing the dependent component and the component to be managed into a storage library matched with respective basic information, and the storage library and the component library are different in stored component type.

Further, the basic information further includes location information;

the determination and acquisition unit is further configured to: when the search result is not searched, the obtaining mode is to obtain the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

Further, the repository comprises a first repository and a second repository;

the storage unit is further configured to: storing the obtained dependent component to the second repository; storing the component to be managed to the first repository; the first storage library and the second storage library are respectively used for storing different types of components.

In a third aspect, an embodiment of the present invention further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method according to any one of the above first aspects when executing the computer program.

In a fourth aspect, embodiments of the present invention also provide a computer readable medium having stored thereon machine executable instructions, which when invoked and executed by a processor, cause the processor to perform the method of any of the first aspect.

In an embodiment of the present invention, a method for managing component information is provided, including: searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components; determining an acquisition mode for acquiring the dependent component based on the search result, and acquiring the dependent component; and respectively storing the dependent component and the component to be managed into a storage library matched with the respective basic information, wherein the types of the components stored in the storage library and the component library are different. According to the above description, the management method of the component information can automatically determine the dependent component corresponding to the component to be managed, and store the component to be managed and the dependent component into the storage libraries matched with the respective basic information, so that the automatic management of the component information is realized, the intelligence degree is high, the cost is low, the efficiency is high, the accuracy is good, and the technical problems of high cost, low efficiency and high possibility of errors of the existing management method of the component information are solved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a flowchart of a method for managing component information according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating that dependent components and components to be managed are respectively stored in the repository matched with the respective basic information according to the embodiment of the present invention;

FIG. 3 is a flowchart of building a topological relationship of components according to an embodiment of the present invention;

FIG. 4 is a flow diagram of component update provided by an embodiment of the present invention;

fig. 5 is a schematic diagram of a device for managing component information according to an embodiment of the present invention;

fig. 6 is a schematic diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions of the present invention will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

At present, when component information is managed, the management is realized by means of oral delivery or document delivery, and the management mode has the technical problems of high cost, low efficiency and high possibility of errors.

Based on this, the embodiment provides a management method of component information, and this method can carry out automated management to the component information, and intelligent degree is high, and is with low costs, efficient, and the accuracy is good.

To facilitate understanding of the present embodiment, a detailed description will be given of a management method of component information disclosed in the present embodiment.

The first embodiment is as follows:

in accordance with an embodiment of the present invention, there is provided an embodiment of a method for managing component information, it should be noted that the steps illustrated in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that herein.

Fig. 1 is a flowchart of a management method of component information according to an embodiment of the present invention, as shown in fig. 1, the method including the steps of:

step S102, searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

the basic information may specifically include: the management method comprises the following steps of version information of a component to be managed, class names (such as technical middleboxes, business middleboxes and the like), the size of the component, dependent component information corresponding to the component to be managed, position information of the component to be managed in a component library, a storage library corresponding to the component to be managed and the like, wherein the basic information is data capable of representing the uniqueness of the component to be managed.

Specifically, the component to be managed can be analyzed through the component identifier, so that the basic information of the component to be managed is obtained, and the dependent component corresponding to the component to be managed is searched from the component library.

It should be noted that, after the basic information is obtained, the dependent component information corresponding to the component to be managed is stored in the database.

Step S104, determining an acquisition mode for acquiring the dependent component based on the search result, and acquiring the dependent component;

specifically, when the search result is the search result, the dependent component is obtained from the component library in a manner of obtaining the dependent component, and the dependent component is directly obtained from the component library.

And S106, respectively storing the dependent component and the component to be managed into the storage libraries matched with the respective basic information, wherein the types of the components stored in the storage libraries are different from those stored in the component library.

Specifically, the information of the repositories respectively corresponding to the dependent component and the component to be managed can be saved in the database.

In an embodiment of the present invention, a method for managing component information is provided, including: searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components; determining an acquisition mode for acquiring the dependent component based on the search result, and acquiring the dependent component; and respectively storing the dependent component and the component to be managed into a storage library matched with the respective basic information, wherein the types of the components stored in the storage library and the component library are different. According to the above description, the management method of the component information can automatically determine the dependent component corresponding to the component to be managed, and store the component to be managed and the dependent component into the storage libraries matched with the respective basic information, so that the automatic management of the component information is realized, the intelligence degree is high, the cost is low, the efficiency is high, the accuracy is good, and the technical problems of high cost, low efficiency and high possibility of errors of the existing management method of the component information are solved.

The above description briefly describes the management method of component information according to the present invention, and the details thereof will be described in detail.

In an optional embodiment of the invention, the base information further comprises location information; determining an obtaining mode for obtaining the dependent component based on the search result, and obtaining the dependent component, specifically comprising:

when the search result is not searched, the acquisition mode is to acquire the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

In an alternative embodiment of the invention, the repository comprises a first repository and a second repository; referring to fig. 2, in step S106, storing the dependent component and the component to be managed into the repository respectively matched with the respective basic information includes:

step S201, storing the acquired dependent component in a second repository;

step S202, storing the component to be managed to a first storage library; the first storage library and the second storage library are respectively used for storing different types of components.

Specifically, the second repository is a repository matched with the basic information of the dependent component, and the first repository is a repository matched with the basic information of the component to be managed.

In an alternative embodiment of the invention, referring to fig. 3, the method further comprises the steps of:

step S301, taking the component to be managed as a current component, determining at least one dependent component related to the current component, and performing topology operation on the current component and the at least one dependent component to form a current topology relation;

the topology operation may specifically be to connect the current component and at least one dependent component in series to obtain a current topology relationship.

Step S302, taking each dependent component in at least one dependent component as a current component, and executing topological operation to form a new current topological relation;

step S303, forming target topological relations of the components to be managed and the dependent components related to the components to be managed based on at least one topological relation.

In an optional embodiment of the present invention, the basic information further includes update information, and referring to fig. 4, the method further includes:

step S401, according to the updating information, determining the components to be updated from all the components to be managed and the dependent components of which the components to be managed have the topological relation;

step S402, according to the updating information of the component to be updated, acquiring a target dependent component of the component to be updated from a third repository, wherein the types of the components stored in the third repository and the component library are different;

the update information may specifically include: and finally, determining a third repository corresponding to the target dependent component according to the basic information of the target dependent component (or according to information stored in a database).

And S403, updating the component to be updated according to the target dependent component.

The management method of the component information provides global management for the components, can reduce the component management cost and improve the management efficiency, and is simple and convenient, convenient to popularize and wide in application range.

Example two:

the embodiment of the present invention further provides a management apparatus for component information, where the management apparatus for component information is mainly used to execute the management method for component information provided in the first embodiment of the present invention, and the following describes the management apparatus for component information provided in the first embodiment of the present invention in detail.

Fig. 5 is a schematic diagram of a management apparatus of component information according to an embodiment of the present invention, as shown in fig. 5, the apparatus mainly includes: a search unit 10, a determination and acquisition unit 20 and a storage unit 30, wherein:

the searching unit is used for searching a dependent component corresponding to the component to be managed in the component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components;

the determining and acquiring unit is used for determining an acquiring mode for acquiring the dependent component based on the searching result and acquiring the dependent component;

and the storage unit is used for respectively storing the dependent component and the component to be managed into the storage libraries matched with the respective basic information, and the storage libraries and the component library are different in stored component type.

In an embodiment of the present invention, there is provided a device for managing component information, including: searching a dependent component corresponding to the component to be managed in a component library based on the acquired basic information of the component to be managed; the component library stores components and dependent components of the components; determining an acquisition mode for acquiring the dependent component based on the search result, and acquiring the dependent component; and respectively storing the dependent component and the component to be managed into a storage library matched with the respective basic information, wherein the types of the components stored in the storage library and the component library are different. According to the above description, the management device of the component information can automatically determine the dependent component corresponding to the component to be managed, and store the component to be managed and the dependent component into the storage libraries matched with the respective basic information, so that the automatic management of the component information is realized, the intelligence degree is high, the cost is low, the efficiency is high, the accuracy is good, and the technical problems of high cost, low efficiency and high possibility of errors of the existing component information management method are solved.

Optionally, the basic information further includes location information; the determination and acquisition unit is further configured to: when the search result is not searched, the acquisition mode is to acquire the dependent component corresponding to the component to be managed from the component comprehensive library according to the position information; the component comprehensive library comprises components which are not stored in the component library.

Optionally, the repository comprises a first repository and a second repository; the storage unit is further configured to: storing the acquired dependent component to a second repository; storing the component to be managed to a first storage library; the first storage library and the second storage library are respectively used for storing different types of components.

Optionally, the apparatus is further configured to: taking the component to be managed as a current component, determining at least one dependent component related to the current component, and performing topological operation on the current component and the at least one dependent component to form a current topological relation; taking each dependent component in at least one dependent component as a current component, and executing a topological operation to form a new current topological relation; and forming a target topological relation of the component to be managed and a dependent component related to the component to be managed based on the at least one topological relation.

Optionally, the basic information further includes update information, and the apparatus is further configured to: determining a component to be updated from all components to be managed and dependent components of the components to be managed, which have topological relations, according to the updating information; acquiring a target dependent component of the component to be updated from a third repository according to the updating information of the component to be updated, wherein the type of the component stored in the third repository is different from that of the component stored in the component library; and carrying out updating operation on the component to be updated according to the target dependent component.

The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the method embodiments without reference to the device embodiments.

As shown in fig. 6, an electronic device 600 provided in an embodiment of the present application includes: a processor 601, a memory 602 and a bus, wherein the memory 602 stores machine-readable instructions executable by the processor 601, when the electronic device runs, the processor 601 and the memory 602 communicate with each other through the bus, and the processor 601 executes the machine-readable instructions to execute the steps of the management method of the component information.

Specifically, the memory 602 and the processor 601 can be general-purpose memories and processors, which are not specifically limited herein, and the management method of the component information can be performed when the processor 601 runs a computer program stored in the memory 602.

The processor 601 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 601. The Processor 601 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the method in combination with the hardware thereof.

Corresponding to the management method of the component information, the embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores machine executable instructions, and when the computer executable instructions are called and executed by a processor, the computer executable instructions cause the processor to execute the steps of the management method of the component information.

The management device of the component information provided by the embodiment of the present application may be specific hardware on the device, or software or firmware installed on the device, and the like. The device provided by the embodiment of the present application has the same implementation principle and technical effect as the foregoing method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the foregoing method embodiments where no part of the device embodiments is mentioned. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the foregoing systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

For another example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, 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, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon 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 described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing an electronic device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the vehicle marking method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the scope of the embodiments of the present application. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.