Component integration method and device, equipment, storage medium and program product

Abstract

The invention discloses a component integration method and device, equipment, a storage medium and a program product, and relates to the field of computers. And the computing device integrates the multiple components according to the target integration version and the product requirements corresponding to the multiple components to obtain a target integration component. The target integrated component comprises an entrance, and the entrance supports the provision of product requirements corresponding to each component in the plurality of components. Therefore, the user equipment does not need to access a plurality of entrances, the product requirement corresponding to each component in the plurality of components can be obtained through one entrance, and the operation is simple. And product requirements corresponding to the components can be compared conveniently, so that the product requirements corresponding to the components can be optimized according to a comparison result.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a component integration method, apparatus, device, storage medium, and program product. Background Technology

[0002] Product integration refers to the process of combining multiple products or services to obtain an integrated system that can integrate multiple products or services. Typically, this can be achieved using a collaborative R&D platform (such as Huawei Cloud CodeArts). TM Based on the R&D needs of each product or service, an integrated system is formed by integrating multiple products or services. Specifically, the R&D collaboration platform provides different entry points for different products or services to access their corresponding R&D needs, based on the R&D requirements of each product or service. Users utilize the entry points corresponding to each product or service to obtain R&D needs, and based on the obtained R&D needs, obtain an integrated system containing multiple entry points corresponding to multiple products.

[0003] In the above process, the single entry point of the R&D collaboration platform supports the R&D needs of one product or service, but does not support the R&D needs of other products or services. When it is necessary to obtain the R&D needs of multiple products or services, it is necessary to obtain them one by one through the entry point corresponding to each product or service, which is cumbersome. Summary of the Invention

[0004] This application provides a component integration method, apparatus, device, storage medium, and program product to solve the problem of cumbersome operation when there is a need to obtain multiple products or services.

[0005] Firstly, this application provides a component integration method. This method can be executed by a computing device, a computing device cluster comprising multiple computing devices, a component of the computing device (such as a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the computing device. Taking execution by a computing device as an example, the component integration method provided in the first aspect includes: the computing device responding to a component integration request and acquiring multiple components; the computing device acquiring the product requirements corresponding to each of the multiple components according to a set integration specification; the product requirements corresponding to each component indicating the integration requirements for the component; and the computing device integrating the multiple components according to a target integration version and the product requirements corresponding to the multiple components to obtain a target integrated component. The target integration version indicates the implementation method of the product requirements. The target integrated component includes an entry point that supports providing the product requirements corresponding to each of the multiple components.

[0006] In the first aspect of this application, a computing device integrates multiple components to obtain a target integrated component based on a target integrated version and the product requirements corresponding to multiple components. This target integrated component includes an entry point, and this single entry point supports providing the product requirements corresponding to each of the multiple components. Thus, user devices do not need to access multiple entry points; they can obtain the product requirements corresponding to each of the multiple components through a single entry point, simplifying the operation. This also facilitates comparison of the product requirements corresponding to each component, allowing for optimization (e.g., adding or removing) of the product requirements corresponding to components based on the comparison results.

[0007] In one possible implementation, the computing device integrates multiple components to obtain a target integrated component based on a target integrated version and the product requirements corresponding to the multiple components. This includes: the computing device generating multiple transactions under the target integrated version. Each transaction indicates a code file for a product requirement of a component. The computing device integrates the multiple components based on the multiple transactions to obtain the target integrated component. Thus, the computing device determines the code files for each product requirement corresponding to multiple components based on the target integrated version, and integrates the multiple components based on the determined code files to obtain the target integrated component. The target integrated component is obtained by the computing device integrating multiple components based on the same target integrated version, improving the consistency of the product requirements corresponding to each component. Furthermore, when updating or modifying the product requirements corresponding to each component, only the target integrated version needs to be modified, improving efficiency.

[0008] In another possible implementation, multiple transactions include a first transaction and a second transaction. The first transaction is determined based on a first component and a first product requirement of the first component in the target integration version. The second transaction is determined based on a second component and the first product requirement of the second component in the target integration version. Both the first and second transactions support the implementation of the first product requirement. Thus, the computing device determines the transaction that supports the implementation of a product requirement based on a product requirement in the target integration version. When at least one component among multiple components corresponds to a product requirement, each of those at least one component has the same implementation method for that product requirement. If the implementation method of that product requirement needs to be modified, only the target integration version needs to be modified, thus improving efficiency.

[0009] In another possible implementation, the first transaction and the second transaction instruct the first code file.

[0010] In another possible implementation, the multiple transactions also include a third transaction. The third transaction is determined based on the first component and the second product requirements of the first component in the target integration version. The third transaction supports the implementation of the second product requirements. The third transaction is used to instruct the first code file. In this way, the computing device implements at least two product requirements corresponding to a component using the same code file, reducing the time required to develop the code file and improving development efficiency.

[0011] In another possible implementation, the method further includes: a computing device displaying a first interface in response to an access request for the target integrated component. The first interface includes one or more of the following: multiple components, multiple transactions, status information of each transaction within the multiple transactions, multiple product requirements, a first correspondence, and a second correspondence. The transaction status information includes one or more of the following: processed, processing, and unprocessed. The multiple product requirements include the product requirements corresponding to each component among the multiple components. The first correspondence indicates the correspondence between each component among the multiple components and each transaction among the multiple transactions. The second correspondence indicates the correspondence between each product requirement among the multiple product requirements and each transaction among the multiple transactions. Thus, using the information displayed on the first interface, the transactions of each component among the multiple components can be obtained. This facilitates comparison of the transactions of each component, allowing for optimization (e.g., adding or removing) of the transactions corresponding to the components based on the comparison results. Furthermore, the status information of each transaction among the multiple transactions allows for the acquisition of the integration progress of the multiple components, enabling timely adjustments to the integration schedule according to the integration plan and reducing the risk of delays.

[0012] In another possible implementation, the first interface includes an integration matrix. The integration matrix is ​​an M-row × N-column matrix. Here, M represents the number of various product requirements, N represents the number of components, and the elements of the integration matrix represent multiple transactions. Thus, the integration matrix allows for a quick and intuitive understanding of the correspondence between components and transactions (e.g., the first correspondence) and between product requirements and transactions (e.g., the second correspondence), improving the user-friendliness of the interaction.

[0013] Secondly, this application provides a component integration apparatus. The apparatus includes various modules for performing the methods described in the first aspect or any possible design of the first aspect.

[0014] Thirdly, this application provides a processor. The processor includes an interface circuit and a control circuit. The interface circuit is used to acquire a component integration request and, in conjunction with the control circuit, implement the method in the first aspect or any of the optional implementations of the first aspect.

[0015] Fourthly, this application provides a computing device cluster. The computing device cluster includes at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, causing the computing device cluster to perform operational steps of the component integration method in the first aspect or any possible implementation of the first aspect.

[0016] Fifthly, this application provides a computer-readable storage medium, comprising: computer software instructions; which, when executed in a computing device, cause the computing device to perform operational steps of the method as described in the first aspect or any possible implementation thereof.

[0017] Sixthly, this application provides a computer program product. When the computer program product is run on a computer, it causes a computing device to perform the operational steps of the method as described in the first aspect or any possible implementation thereof.

[0018] The beneficial effects of aspects two through six above can be described with reference to the first aspect or any implementation thereof, and will not be repeated here. Based on the implementations provided in the above aspects, this application can be further combined to provide more implementations. Attached Figure Description

[0019] Figure 1 A process architecture diagram for product integration;

[0020] Figure 2 This is an example diagram of a collaborative R&D platform;

[0021] Figure 3 A schematic diagram of the structure of a component integration system provided in this application;

[0022] Figure 4 This application provides a schematic diagram of the structure of a chip;

[0023] Figure 5 A flowchart illustrating the first component integration method provided in this application;

[0024] Figure 6 A flowchart illustrating an encapsulated transaction processor provided in this application;

[0025] Figure 7 A schematic diagram of the second type of component integration provided in this application;

[0026] Figure 8A Example diagram of the first type of first interface provided in this application;

[0027] Figure 8BExample diagram of the second type of first interface provided in this application;

[0028] Figure 9 A software schematic diagram of the first component integration system provided in this application;

[0029] Figure 10 A software schematic diagram of the second component integration system provided in this application;

[0030] Figure 11 A schematic diagram of a component integration device provided in this application;

[0031] Figure 12 This application provides a schematic diagram of the structure of a computing device cluster;

[0032] Figure 13 This is a schematic diagram of the connection between computing devices provided in this application. Detailed Implementation

[0033] To ensure clarity and brevity in the description of the following embodiments, a brief introduction to the relevant technologies is given first.

[0034] Product integration can refer to the process of combining multiple products or services to obtain an integrated system that can integrate multiple products or services.

[0035] Figure 1 A process architecture diagram for product integration, such as Figure 1 As shown, the products to be integrated include product A and product B. In this case, product A and product B can be developed separately according to their respective requirements. Alternatively, according to product integration specifications, products A and B can be integrated based on their common requirements to obtain an integrated system that can realize the functions of products A and B. Typically, multiple separate systems can be used to collaboratively complete the above process. For example, a requirements analysis system can be used to obtain the requirements of each product (such as the requirements of product A and product B), and the common requirements that each product must meet (such as the common requirements of product A and product B) can be obtained according to the product integration specifications. A development system can be used to develop product A and product B separately according to the above requirements, and a testing system can be used to test product A, product B, and the integration testing of product A and product B, etc.

[0036] When multiple separate systems collaborate to integrate a product, the efficiency of the integration process is affected if information cannot be exchanged between the systems in a timely manner. Therefore, a solution can be adopted... Figure 2 This demonstrates how a collaborative R&D platform enables product integration.

[0037] Figure 2 Here is an example diagram of a collaborative R&D platform, such as... Figure 2As shown, the platform integrates services A through F, and provides an entry point (e.g., entry point 1 through entry point 6) for each service. Users can obtain requirement 1 for service A using entry point 1, requirement 2 for service B using entry point 2, and so on, until all requirements corresponding to services A through B are obtained (e.g., requirement 1 through requirement 6). The integrated system is then obtained based on requirement 1 through requirement 6.

[0038] While the aforementioned R&D collaboration platform supports the provision of multiple products, each entry point only supports the provision of one service, not others. In cases requiring access to multiple services, it necessitates using the entry points corresponding to each service individually, resulting in cumbersome operations.

[0039] Based on this, this application provides a component integration method. A computing device integrates multiple components to obtain a target integrated component according to a target integrated version and the product requirements corresponding to those components. This target integrated component includes an entry point, which supports providing the product requirements corresponding to each of the multiple components. Thus, user devices do not need to access multiple entry points; they can obtain the product requirements corresponding to each of the multiple components through a single entry point, simplifying the operation. It also facilitates comparison of the product requirements corresponding to each component, allowing for optimization (e.g., adding or removing) of the product requirements corresponding to components based on the comparison results.

[0040] Figure 3 A schematic diagram of a component integration system provided in this application is shown below. Figure 3 As shown, the component integration system 300 includes a computing device 310. The computing device 310 is a common computer device. Users can initiate a component integration request to the computing device 310, which processes (e.g., integrates) multiple components to obtain the target integrated component. The computing device 310 can also output the result (e.g., the target integrated component).

[0041] The computing device 310 includes a communication interface 314, a processor 311, and a memory 312. The communication interface 314 is used to communicate with devices located outside the computing device 310. For example, a user inputs a component integration request to the computing device 310 through the communication interface 314 to integrate multiple components. Based on the received request, the computing device 310 obtains the processing result (such as the target integrated component). This communication interface can be an input / output (I / O) interface.

[0042] Processor 311 is the core of computing device 310 for both computation and control. It may include: a central processing unit (CPU), a specific integrated circuit, other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. In practical applications, computing device 310 may also include multiple processors. Processor 311 may include one or more processor cores. An operating system and other software programs are installed in processor 311, enabling it to access memory 312 and various peripheral component interconnect (PCIe) devices.

[0043] The processor 311 is connected to the memory 312 via a double data rate (DDR) bus or other types of bus. The memory 312 is the main memory of the computing device 310. The memory 312 is typically used to store various running software in the operating system. To improve the access speed of the processor 311, the memory 312 needs to have a high access speed. In traditional computer devices, dynamic random access memory (DRAM) is typically used as the memory 312. Besides DRAM, the memory 312 can also be other random access memories, such as static random access memory (SRAM). Alternatively, the memory 312 can also be a read-only memory (ROM). For example, a read-only memory could be a programmable read-only memory (PROM) or an erasable programmable read-only memory (EPROM). This embodiment does not limit the number or type of memory 312.

[0044] Optionally, in order to persistently store data (such as information from multiple components), the component integration system also includes a data storage system 313, which may be located outside the computing device 310 (e.g., Figure 3 As shown, the data storage system 313 exchanges data with the computing device 310 via a network. Optionally, the data storage system 313 can also be located inside the host, such as exchanging data with the processor 311 via the bus 316. In this case, the data storage system 313 manifests as a hard disk.

[0045] In some possible scenarios, the component integration system 300 may also include a client device 320. In this case, the user uses the client device 320 to send a component integration request to the computing device 310. The client device 120 is a terminal device, including but not limited to a personal computer, server, mobile phone, tablet computer, or smart car.

[0046] For example, Figure 3 The processor 311 in the text can be implemented through a chip, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of a chip provided in this application. For example, the chip 400 includes a core 401, a CPU 402, a system buffer 403, an input / output (I / O) device 405, and a DDR 406.

[0047] The CPU 402 is used to accept tasks (such as compression tasks, decompression tasks, component integration tasks, etc.) and call core 401 to execute the task. When chip 400 has multiple cores 401, the CPU 402 is also used for scheduling tasks. For example, the CPU 402 can be implemented by an ARM processor, which is small in size, low in power consumption, uses a 34-bit reduced instruction set, and has simple and flexible addressing. Of course, in some implementations, the CPU 402 can also be implemented by other processors.

[0048] Core 401 provides the computing power required for the acquisition and integration tasks. In one optional configuration, core 401 includes a load / store unit (LSU), a cube computing unit, a scalar computing unit, a vector computing unit, and a buffer. The LSU loads data to be processed and stores processed data. It also manages read / write operations between different buffers within the core and performs format conversions. The cube computing unit provides the core computing power for matrix multiplication. The scalar computing unit is a single-instruction single-data (SISD) processor, meaning it processes only one data item (typically an integer or floating-point number) at a time. The vector computing unit, also known as an array processor, is a processor capable of directly manipulating an array or vector for computation. The number of buffers may be one or more. For example, this buffer primarily refers to the level 1 cache (L1 buffer). The buffer is used to temporarily store data that the core 401 needs to use repeatedly, thereby reducing read / write operations from the bus. Additionally, the implementation of certain data format conversion functions also requires the source data to be located in the buffer. In this embodiment, because the buffer is located in the core, the distance between the cube computing unit in the core and the storage area where the data is located is reduced, decreasing the cube computing unit's access to the DDR 406, thereby reducing data access latency and core data processing latency.

[0049] System buffer 403 mainly refers to the level 4 buffer (L1 buffer or L4 cache), which is used to temporarily store input data, intermediate results or final results that have passed through the chip.

[0050] DDR 406 is an off-chip memory that can be replaced by high-bandwidth memory (HBM) or other off-chip memory. Located between the chip and external memory, DDR 406 overcomes the access speed limitations of shared memory read / write operations in computing resource sharing.

[0051] The I / O device 405 included in chip 400 refers to the hardware that performs data transmission, or the device that interfaces with the I / O interface. Common I / O devices include network cards, printers, keyboards, and mice. All external storage devices can also be used as I / O devices, such as hard drives, floppy disks, and optical discs.

[0052] Core 401, CPU 402, system buffer 403, I / O devices 405, and DDR 406 are connected via a bus. The bus may include a pathway for transmitting information between the aforementioned components (such as CPU 402 and system buffer 403). In addition to a data bus, the bus may also include a power bus, control bus, and status signal bus. However, for clarity, the bus may be a PCIe bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. For example, core 401 can access these I / O devices 405 via a PCIe bus. Core 401 is connected to system buffer 403 via a DDR bus. Here, different system buffers 403 may use different data buses to communicate with core 401; therefore, the DDR bus can also be replaced with other types of data buses. This embodiment does not limit the bus type.

[0053] For example, after the CPU 402 loads the data to be processed by the component integration task (such as information about multiple components) into the DDR 406, the LSU in the core 401 reads (loads) the data from the DDR 406, processes the multiple components, and obtains the processing result (such as the target integrated component). After obtaining the processing result, the LSU then loads (stores) the processing result into the DDR 406, and sends it to the data storage system 313 for persistent storage via the network interface card.

[0054] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the computing device. In other embodiments, the computing device and chip may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0055] The following is combined Figure 1 and Figure 4 The content shown provides a detailed description of the component integration method provided in this application.

[0056] Figure 5This is a flowchart illustrating the first component integration method provided in this application. This component integration method can be executed by a computing device, a computing device cluster, or components of the computing device (such as the processor, chip, or chip system of the computing device), and can also be implemented by a logic module or software. When this component integration method is executed by a computing device, the computing device can be… Figure 3 The computing device 310 and client device 320 are shown. For the hardware implementation of the computing device, please refer to the foregoing. Figure 3 The description of this will not be repeated here. When this component integration method is performed by a component of a computing device, that computing device component can be... Figure 4 The chip shown is an example. For details on the chip's hardware implementation, please refer to the preceding text. Figure 4 The description of the component integration method is omitted here. In some optional examples, this component integration method can also be executed by other computing devices; the hardware implementation of the computing devices can be found in the foregoing. Figure 3 and Figure 4 The description of that will not be repeated here.

[0057] This explanation uses a computing device executing the component integration method provided in this embodiment as an example. Figure 5 As shown, the component integration method provided in this embodiment includes the following steps S510 to S530.

[0058] S510, the computing device responds to a component integration request and acquires multiple components.

[0059] The components may include, but are not limited to, services (such as cloud services), products, threads, processes, etc. The following example illustrates the component integration method provided in this application using a cloud service as an example. Similarly, when the components are products, threads, or processes, the methods described below can still be used to integrate products, threads, processes, etc., to obtain the target integrated component, which will not be elaborated upon here.

[0060] Depending on how the computing device obtains the component integration request, the computing device may also obtain multiple components in response to the component integration request in different ways. Examples of two possible methods are given below.

[0061] Example 1: The computing device receives a component integration request sent by the user.

[0062] In this scenario, the user can determine the multiple components to be integrated based on actual application needs. The user can then use a client device to send a component integration request to the computing device based on these components. The computing device receives the component integration request sent by the user using the client device. The component integration request includes information about the multiple components to be integrated, such as the component identifier for each component. The component identifier is used to identify the component and includes, but is not limited to, component name, component number, etc. The computing device can parse the component integration request to obtain the multiple components to be integrated.

[0063] For example, based on actual application needs, a user determines that the components to be integrated include components 1 through 3. The user can then use the client device to send component integration request 1 to the computing device based on components 1 through 3. The computing device receives component integration request 1. Component integration request 1 includes the component identifier for each of components 1 through 3.

[0064] Example 2: The computing device generates a component integration request based on the user's actions.

[0065] In this scenario, the computing device can receive user actions on a first control and generate a component integration request based on those actions. This component integration request indicates multiple components to be integrated. The first control may include, but is not limited to, a first button on the computing device's input device, a first area on the computing device's display device, etc. Actions include, but are not limited to, clicking, long-pressing, swiping, etc. The computing device then parses the component integration request to obtain the multiple components.

[0066] For example, a user clicks on display area 1 of the computing device's screen. The computing device receives the user's click on display area 1, determines multiple components corresponding to display area 1 based on the set correspondence between display areas and components, and generates a component integration request 1 based on these multiple components. The computing device parses component integration request 1 and obtains the multiple components.

[0067] In some possible scenarios, computing devices can utilize version management modules to configure or access target integration versions. Computing devices can also utilize component management modules to manage or access components.

[0068] The foregoing provides two possible examples of a computing device acquiring multiple components in response to a component integration request. Depending on the specific application requirements, the computing device may also acquire multiple components using other methods, which are not limited in this application.

[0069] S520: The computing device obtains the product requirements for each of the multiple components according to the set integration specifications.

[0070] The product requirements for each component indicate the integration needs of that component. These integration requirements can refer to the requirements that each component must meet during the integration of multiple components.

[0071] An integration specification can include multiple components, and one or more product requirements for each of these components. In some cases, the integration requirements for components can also be referred to as the integration specifications for the components.

[0072] For example, Integration Specification 1 includes Components 1 to Components 3, and the corresponding product requirements for each component. Table 1 shows the correspondence between the components and product requirements in Integration Specification 1.

[0073] Table 1 shows an example of an integration specification.

[0074] Component 1 Component 2 Component 3 Product Requirements 1 √ √ √ Product Requirement 2 √ √ × Product Requirement 3 × √ √

[0075] In this application, √ indicates existence, and × indicates non-existence, which will not be elaborated further below. Specifically, in Table 1, √ components correspond to product requirements, and × components do not require corresponding product requirements. As shown in Table 1, component 1 corresponds to product requirements 1 and 2, component 2 corresponds to product requirements 1 to 3, and component 3 corresponds to product requirements 1 and 3. In this case, product requirements 1 and 2 reflect the integration requirements for component 1, product requirements 1 to 3 reflect the integration requirements for component 2, and product requirements 1 and 3 reflect the integration requirements for component 3.

[0076] In some possible scenarios, users can determine the integration specifications according to the needs of the actual application. That is to say, the components included in the integration specifications, the number of components, and the product requirements corresponding to the components may vary depending on the actual application scenario. This application does not limit this.

[0077] For example, in application scenario 1, the integration specification may include component 1 and component 2. The product requirements corresponding to component 1 may include: product requirement 1 to product requirement n. The product requirements corresponding to component 2 may include: product requirement 1 to product requirement m.

[0078] For example, in application scenario 2, the integration specification may include component 1 and component 2. The product requirements corresponding to component 1 may include: product requirement 1 to product requirement i. The product requirements corresponding to component 2 may include: product requirement 1 to product requirement j. Here, i and n are different, and j and m are different.

[0079] For example, in application scenario 3, the integration specification can include components 1 to 3. The product requirements corresponding to component 1 can include: product requirement 1 to product requirement n. The product requirements corresponding to component 2 can include: product requirement 1 to product requirement m. The product requirements corresponding to component 3 can include: product requirement 1 to product requirement k.

[0080] For example, in application scenario 4, the integration specification may include component 4 and component 5. The product requirements corresponding to component 4 may include: product requirement 1 to product requirement a. The product requirements corresponding to component 5 may include: product requirement 1 to product requirement b.

[0081] The integration specifications have been explained above with examples; the product requirements will be explained below.

[0082] In some possible scenarios, the product requirements for a component include, but are not limited to, the functionalities the component supports and the guarantees provided for those functionalities. All product requirements for a component can reflect the integration needs of the component. Taking a cloud service as an example, the product requirements for that component are illustrated below.

[0083] Example a: Cloud Service 1 is required to issue an alarm when it detects that the server load exceeds a load threshold. In this case, the product requirements for Cloud Service 1 may include, but are not limited to: developing code files that can implement the alarm function (or simply alarm development), and developing code files that can test the alarm development (or simply alarm testing). In some possible cases, to improve development efficiency, the product features for Cloud Service 1 may also include: developing code files that can learn from the alarm development (or simply alarm learning). Please refer to Table 2 below for the correspondence between Cloud Service 1 and the above product requirements.

[0084] Example b requires Cloud Service 1 to issue an alarm when the server load exceeds the load threshold. It also requires providing prompts regarding the installation method of Cloud Service 1 (or, in short, deployment prompts, installation prompts, etc.). In this scenario, the product requirements for Cloud Service 1 may include: alarm development, alarm testing, and alarm learning as in Example a, and may also include: developing code files that implement the alarm function (or, in short, deployment development), and developing code files that enable testing of deployment development (or, in short, deployment testing). In some possible scenarios, to improve development efficiency, the product features for Cloud Service 1 may also include: developing code files that enable learning from deployment development (or, in short, deployment learning). Please refer to Table 2 below for the correspondence between Cloud Service 1 and the above product requirements.

[0085] Table 2 Example of the correspondence between component and product requirements

[0086] Cloud Service 1 Cloud Service 2 Alarm Learning √ √ Alarm Development √ √ Alarm test √ √ Deployment Learning × √ Deployment and Development × √ Deployment testing × √

[0087] In Table 2, alarm development, alarm testing, and alarm learning reflect the integration requirements for cloud service 1, while alarm development, alarm testing, alarm learning, deployment learning, deployment development, and deployment testing reflect the integration requirements for cloud service 2.

[0088] In some possible scenarios, computing devices can use the product requirements management module to configure and access product requirements, ensuring that computing devices can obtain multiple product requirements according to the integration specifications.

[0089] The above examples illustrate the product requirements for the components. Depending on the actual application needs, the product requirements for the components may include other content, which this application does not limit.

[0090] The above section explained the integration specifications and product requirements with examples. The following section describes the process by which a computing device obtains the product requirements for each component among multiple components based on the integration specifications. Specifically, the computing device can filter out multiple components from the integration specifications that match the multiple components obtained from the parsed component integration request, and determine the product requirements for each of the matched components based on the integration specifications. The computing device determines the product requirements for each component among the multiple components obtained from the parsed component integration request based on the product requirements for each of the matched components. In some possible cases, if the first component and the second component have the same component identifier or support and provide the same functionality, they can be considered to be matched.

[0091] The following section uses cloud services as an example to illustrate the process by which a computing device determines the product requirements for each of the multiple components obtained from the component integration request, based on the integration specifications. This process may include the following ① to ③.

[0092] ① The computing device obtains multiple cloud services and the corresponding product requirements for each cloud service according to the integration specification.

[0093] For example, the computing device obtains multiple cloud services and corresponding product requirements as shown in Table 3 according to integration specification 1.

[0094] Table 3. Integration Specification 1 includes cloud services and corresponding product requirements.

[0095] Cloud Service 1 Cloud Service 2 Cloud Service 3 Product Requirements 1 √ √ √ Product Requirement 2 √ √ × Product Requirement 3 × √ √

[0096] ② The computing device parses the component integration request and identifies the multiple cloud services to be integrated.

[0097] For example, the computing device resolves component integration request 1 and determines that the multiple cloud services to be integrated are cloud service 1 to cloud service 3.

[0098] ③ The computing device determines the product requirements for each cloud service among multiple cloud services according to the integration specifications.

[0099] In this case, the computing device determines, according to Table 3, that the product requirements corresponding to cloud service 1 are product requirement 1 and product requirement 2, the product requirements corresponding to cloud service 2 are product requirement 1 to product requirement 3, and the product requirements corresponding to cloud service 3 are product requirement 1 and product requirement 3.

[0100] The above text, with examples, explained the process by which a computing device obtains the product requirements corresponding to each of multiple components according to the integration specifications. The following text explains the process by which the computing device integrates these multiple components to obtain the target integrated component.

[0101] S530, the computing device integrates multiple components to obtain the target integrated component based on the target integrated version and the product requirements corresponding to multiple components.

[0102] The target integration version indicates the implementation method of the product requirements. The target integration component includes an entry point. This entry point supports providing the product requirements corresponding to each of the multiple components. This single entry point can support providing all product requirements corresponding to each of the multiple components, or it can support providing only a portion of the product requirements corresponding to each of the multiple components. These partial product requirements can be the product requirements that meet a first condition among all the product requirements corresponding to the component. This first condition can be determined based on the actual application. The following explanation uses the example of this single entry point supporting the provision of all product requirements corresponding to each of the multiple components to illustrate the component integration method provided in this application.

[0103] In some possible scenarios, the target integration version includes implementations of each of the multiple product requirements. An implementation of a product requirement can refer to code files that implement that requirement. These code files can be provided in ways including, but not limited to, plugins. Depending on the specific application requirements, the implementations of the product requirements included in the target integration version can take various forms, which are described below in different scenarios.

[0104] Scenario 1: One product requirement corresponds to one implementation method.

[0105] In this scenario, a product requirement can correspond to a code file that implements that requirement. This code file can also be packaged into a plugin for use by third parties who need to implement the product requirement. For example, if product requirement 1 corresponds to code file 1, the computing device can package code file 1 to obtain plugin 1. Furthermore, if a third party includes product requirement 1, it can call plugin 1. The specific correspondence is shown in Table 4 below.

[0106] Scenario 2: Multiple product requirements correspond to one implementation method.

[0107] In this scenario, multiple product requirements can be implemented using a single code file. This code file is then encapsulated as a plugin for use by third parties who need to implement any of the multiple product requirements. For example, if product requirement 2 and product requirement 3 correspond to code file 2, the computing device can encapsulate code file 2 to obtain plugin 2. Furthermore, plugin 2 can be invoked by any third party that includes either product requirement 2 or product requirement 3.

[0108] Table 4 shows an example of a target integration version.

[0109] Implementation Product Requirements 1 Code file 1 Product Requirement 2 Code file 2 Product Requirement 3 Code file 2

[0110] The preceding text described the content related to the target integrated version. The following describes the process by which a computing device obtains the target integrated component. This process may include the following ① and ②.

[0111] ① The computing device generates multiple transactions under the target integration version based on the target integration version and the product requirements corresponding to multiple components.

[0112] One transaction is used to indicate a product requirement code file for a component.

[0113] In some possible scenarios, multiple transactions include a first transaction and a second transaction. The first transaction is determined based on the first component and the first product requirements of the first component in the target integration version. The second transaction is determined based on the second component and the first product requirements of the second component in the target integration version. Both the first and second transactions support the implementation of the first product requirements.

[0114] In some possible scenarios, the first transaction and the second transaction instruct the first code file.

[0115] In some possible scenarios, multiple transactions may also include a third transaction. The third transaction is determined based on the first component and the second product requirements of the first component in the target integration version. The third transaction supports the implementation of the second product requirements. The third transaction is used to instruct the first code file.

[0116] In some possible scenarios, multiple transactions may also include a fourth transaction. The fourth transaction is determined based on the first component and the third product requirements of the first component in the target integration version. The fourth transaction supports the implementation of the third product requirements. The fourth transaction is used to instruct the second code file.

[0117] The above text describes several transactions. The following text describes the process of a computing device generating a transaction, which may include the following (1) and (2).

[0118] (1) The computing device obtains all product requirements for each of the multiple components.

[0119] For example, the computing device determines, according to Table 3, the product requirements corresponding to cloud service 1 as product requirement 1 and product requirement 2, the product requirements corresponding to cloud service 2 as product requirement 1 to product requirement 3, and the product requirements corresponding to cloud service 3 as product requirement 1 and product requirement 3.

[0120] (2) The computing device generates transactions in the target integration version for each product requirement.

[0121] In this scenario, the computing device can generate transactions based on the product requirements corresponding to the component, and determine the code files that implement the transactions based on the target integration version. Specifically, the computing device generates one transaction for each product requirement corresponding to the component. One transaction corresponds to one product requirement for one component.

[0122] For example, the multiple cloud services to be integrated include cloud service 1 to cloud service 3. Cloud service 1 corresponds to product requirement 1 and product requirement 2, cloud service 2 corresponds to product requirement 1 to product requirement 3, and cloud service 3 corresponds to product requirement 1 and product requirement 3. The computing device can generate multiple transactions as shown in Table 5.

[0123] Table 5 shows an example of a transaction.

[0124] Cloud Service 1 Cloud Service 2 Cloud Service 3 Product Requirements 1 Transaction 11 Transaction 21 Transaction 31 Product Requirement 2 Transaction 12 Transaction 22 × Product Requirement 3 × Transaction 32 Transaction 33

[0125] After generating multiple transactions, the computing device can also determine the implementation method (e.g., code file) of each product requirement corresponding to each transaction under the target integration version. This code file may include, but is not limited to, page code files and backend code files. The page code file provides support for displaying the page in response to transaction access requests. The backend code file provides support for running the job logic in response to transaction access requests. Depending on the implementation method of the product requirements in the target integration version, one transaction among all transactions generated from all product requirements corresponding to a component, as determined by the computing device, can correspond to one code file (e.g., transaction 11 in Table 6), and at least one transaction among all transactions can also correspond to one code file (e.g., transactions 22 and 32 in Table 6).

[0126] Table 6 provides an example of the correspondence between transactions and code files.

[0127]

[0128] After determining the implementation method of each product requirement corresponding to each transaction in the target integration version, the computing device can also obtain the configuration information corresponding to each product requirement in each component based on the individual requirements of each component for each product requirement corresponding to each transaction. The computing device can determine the transaction based on the implementation method and configuration information of each transaction in the target integration version, as shown in Table 7.

[0129] Table 7 provides an example of transaction implementation.

[0130]

[0131] In some possible scenarios, computing devices can also encapsulate code files and configuration information into an application with transaction processing capabilities. For example, a computing device can encapsulate page code files and backend code files into an application. This application can also be called a transaction plugin. The computing device can manage (e.g., configure, access, etc.) transaction processors using a transaction processor management module. Alternatively, the computing device can encapsulate code files (such as page code files, backend code files, etc.) and configuration information into a transaction processor capable of handling product requirements from different components to meet the same integration needs. In some possible scenarios, a transaction processor and transaction data can constitute a transaction instance. This transaction data is used to indicate the data associated with a specific transaction. When a computing device encapsulates code and configuration information into a transaction processor, the computing device can configure a corresponding transaction processor for the transaction. This transaction processor provides support for the transaction.

[0132] Figure 6 A flowchart illustrating an encapsulated transaction processor provided in this application is shown below. Figure 6 As shown, the computing device develops code file 1 according to product requirement 1 and encapsulates code file 1 into plugin 1. The computing device obtains configuration information 11 based on the personalized requirements of cloud service 1 for product requirement 1, configuration information 12 based on the personalized requirements of cloud service 2 for product requirement 1, and configuration information 13 based on the personalized requirements of cloud service 3 for product requirement 1. The computing device uses configuration information 11 to configure plugin 1, obtaining a code file (or transaction 11) supporting product requirement 1 for cloud service 1. The computing device uses configuration information 12 to configure plugin 1, obtaining a code file (or transaction 12) supporting product requirement 1 for cloud service 1. The computing device uses configuration information 13 to configure plugin 1, obtaining a code file (or transaction 13) supporting product requirement 1 for cloud service 1. The computing device also develops code file 2 according to product requirements 2 and 3 and encapsulates code file 2 into plugin 2. Similarly, the computing device uses the above method to obtain transactions 21 to 23, 31, and 33.

[0133] ②The computing device integrates multiple components based on multiple transactions to obtain the target integrated component.

[0134] The computing device integrates multiple components based on the code files corresponding to each transaction in multiple transactions to obtain the target integrated component.

[0135] After executing S530 to obtain the target integrated component including an entry point, the computing device can also execute S540 to use that entry point to obtain the product requirements for each of the multiple components. Figure 7 A flowchart illustrating the second type of component integration provided in this application is shown below. Figure 7 As shown, the component integration method also includes S540.

[0136] S540, the computing device displays a first interface in response to an access request for the target integrated component.

[0137] The first interface includes: multiple components, multiple transactions, multiple product requirements, a first correspondence, and a second correspondence.

[0138] The multiple product requirements include the product requirements corresponding to each of the multiple components. A first correspondence indicates the correspondence between each of the multiple components and each of the multiple transactions. A second correspondence indicates the correspondence between each product requirement in the multiple product requirements and each of the multiple transactions.

[0139] The computing device can be displayed in the first interface in a variety of ways: multiple components, multiple transactions, multiple product requirements, first correspondence, and second correspondence. Examples of two possible ways are given below.

[0140] Example 1: The computing device uses a matrix to display the above content.

[0141] The first interface includes an integration matrix, which is an M-row × N-column matrix, where M is the quantity of various product requirements, N is the quantity of multiple components, and the elements included in the integration matrix are multiple transactions.

[0142] Figure 8A Example diagram of the first type of first interface provided in this application, such as Figure 8A As shown, the first interface includes matrix 1. The rows of matrix 1 are product requirement 1 to product requirement m, and the columns are component 1 to component n. The elements of matrix 1 are transactions generated based on the component and the target integration version. Figure 8A As shown in the figure, "--" indicates that the component does not have a corresponding product requirement. For example, component 1 does not have product requirement 2, component 2 does not have product requirement m, and component n does not have product requirement 1.

[0143] Example 2: The computing device displays the above content in a tree structure.

[0144] Figure 8B Example diagram of the second type of first interface provided in this application, such as Figure 8B As shown, the first interface includes N trees (e.g., tree 1 to tree N), where N is the number of components. Each component corresponds to one tree. Tree i includes j branches, and each branch of tree i represents a product requirement corresponding to component i. Each of the j branches corresponds to a leaf, and a leaf represents a transaction determined according to the product requirement. i is an integer greater than or equal to 1 and less than or equal to N, and j is an integer greater than or equal to 1.

[0145] In some possible scenarios, the first interface may also include: status information for each transaction among multiple transactions. The transaction status information may include one or more of the following: processed, processing, and unprocessed. The computing device may use different identifiers to distinguish different status information. Identifiers may include, but are not limited to, one or more of the following: text, color, symbol, icon, etc. For example, the computing device may use "√" to indicate that the transaction has been processed, "-" to indicate that the transaction is in process, and "×" to indicate that the transaction has not been processed. Alternatively, the computing device may use a green "√" to indicate that the transaction has been processed, an orange "-" to indicate that the transaction is in process, and a red "×" to indicate that the transaction has not been processed.

[0146] In some possible scenarios, computing devices can utilize the transaction management module to configure and manage transactions. Specifically, the transaction management module can be used to manage transactions, ensuring that the first interface displays multiple components, multiple transactions, multiple product requirements, and primary and secondary correspondences in a predefined manner. Furthermore, the transaction management module can also be used to manage the status information of transactions.

[0147] In some possible scenarios, the computing device may also display a first page in response to access to the target transaction. The first page may include one or more of the following: the job logic of the target transaction, job description, or a first link. This first link serves as a directive to a second page, which may include information about the target transaction. This information may include, but is not limited to, code files implementing the target transaction. The computing device can utilize a plug-in management module to view the plug-ins that support the display of the first page. The plug-in management module may be developed by calling resources from other systems.

[0148] In some possible scenarios, the computing device can also be configured with account management functions. For example, the computing device displays a prompt page asking the user to enter their login username and password, and receives and verifies the entered username and password. After successful verification, the computing device executes S540. The computing device can utilize an account management model to implement account management functions. Furthermore, the computing device can also employ a page management module to manage the prompt page.

[0149] In some possible scenarios, the computing device can also be configured to store data generated during the implementation of the component integration method by the aforementioned component management module, account management module, version management module, page management module, transaction management module, product requirement management module, and plug-in management module. For example, the computing device can use a relational database to store this data.

[0150] The preceding text uses the example of a service, product, process, or thread to illustrate the component integration method provided in this application. In some possible scenarios, the component integration method provided in this application can also integrate at least one of a service, product, process, or thread to obtain a target integrated component. For example, a computing device can also use the component integration method described above to integrate cloud services 1 to n and products 1 to m to obtain a target integrated component. This target integrated component provides an entry point that supports providing the product requirements for each cloud service from cloud services 1 to cloud services n, and the product requirements for each product from products 1 to products m, which will not be elaborated here.

[0151] Depending on the correspondence between code files and implementation methods, component integration systems can have different architectures, which will be explained below.

[0152] In scenario A, one product requirement corresponds to one code file.

[0153] In this case, the computing device can adopt Figure 9 The component integration system shown implements component integration. Figure 9 A software schematic diagram of the first component integration system provided in this application, such as... Figure 9As shown in (a), the computing device can utilize an account management module, page management module, component management module, version management module, transaction management module, product requirement management module, plug-in management module, and database to implement a component integration method, thereby obtaining a first interface displaying multiple components, multiple product requirements, and multiple transactions. The database can be a relational database. The database may include one or more of the following: a framework database, a plug-in database, etc. The framework database is used to store code files, configuration information, etc., for implementing the account management module, page management module, component management module, version management module, transaction management module, product requirement management module, and plug-in management module, as well as data generated during the operation of these modules. The plug-in database is used to store data associated with transactions, code files corresponding to plug-ins, and configuration information, etc. In some possible cases, resources provided by other systems can be used to develop and implement the code files corresponding to the plug-ins. And the above modules can be configured according to... Figure 9 The process shown in (b) integrates components.

[0154] Scenario B: Multiple products require a single code file.

[0155] In this case, the computing device can adopt Figure 10 The component integration system shown implements component integration. Figure 10 A software schematic diagram of the second component integration system provided in this application, such as... Figure 10 As shown in (a), the computing device can utilize an account management module, page management module, component management module, version management module, transaction management module, transaction processor management module, product requirement management module, plug-in management module, and database to implement a component integration method to obtain a first interface displaying multiple components, multiple product requirements, and multiple transactions. The database can be a relational database. The transaction processor management module is used to manage transaction plug-ins. The database may include one or more of the following: a framework database, a transaction database, a plug-in database, etc. The framework database is used to store code files, configuration information, etc., for implementing the account management module, page management module, component management module, version management module, transaction management module, product requirement management module, and plug-in management module, as well as data generated during the operation of these modules. The transaction database is used to store data associated with transactions. The plug-in database is used to store code files corresponding to plug-ins, as well as configuration information, etc. In some possible cases, resources provided by other systems can be used to develop code files corresponding to plug-ins. And the above modules can be configured according to... Figure 10 The process shown in (b) integrates components.

[0156] The preceding text uses the example of a computing device integrating multiple components according to a target integration version to obtain a single target integrated component to illustrate the component integration method provided in this application. In some possible examples, the computing device can also integrate multiple components according to multiple target integration versions to obtain multiple target integrated components. Here, one target integrated component corresponds to one target integration version. In this case, the computing device integrates multiple components according to one target integration version at a time, obtaining a target integrated component corresponding to that one target integration version, repeating this process multiple times until multiple target integrated components are obtained according to multiple target integration versions. The process of the computing device integrating multiple components according to one target integration version to obtain a single target integrated component is described above and will not be repeated here.

[0157] It is understood that, in order to achieve the functions in the above embodiments, the computing device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0158] The above text combines Figures 1 to 10 The component integration method provided according to this embodiment is described in detail below. Figure 11 This describes the component integration apparatus provided according to this embodiment.

[0159] Figure 11 A schematic diagram of a component integration device provided in this application is shown below. Figure 11 As shown, the component integration device 1100 includes: a transceiver module 1110, a product requirement acquisition module 1120, and a processing module 1130. The transceiver module 1110 is used to: acquire multiple components in response to a component integration request. The product requirement acquisition module 1120 is used to: acquire the product requirements corresponding to each of the multiple components according to a set integration specification. The product requirements corresponding to each component are used to indicate the integration requirements for the component. The processing module 1130 is used to: integrate the multiple components according to the target integration version and the product requirements corresponding to the multiple components to obtain a target integrated component. The target integration version indicates the implementation method of the product requirements, and the target integrated component includes an entry point that supports providing the product requirements corresponding to each of the multiple components.

[0160] For more details on the transceiver module 1110, the product requirement acquisition module 1120, and the processing module 1130, please refer to the above description of the component integration method; it will not be repeated here.

[0161] When the component integration device 1100 corresponds to the steps performed by the computing device in the component integration method described in the embodiments of this application, the above and other operations and / or functions of each module in the component integration device 1100 are respectively to implement the method flow performed by the computing device in the foregoing figures.

[0162] It is worth noting that if the above-mentioned integrated device is implemented through a software module, for example, the software module can be provided to users through a cloud service subscription model, and users can choose different subscription levels according to their needs; or, for example, the software module can also provide enterprise-level customized services with professional domain customization, interface personalization and extended functions according to the needs of users or enterprises.

[0163] In addition, the component integration device 1100 provided in this application can also be provided to users as a value-added service, and this application does not limit this.

[0164] The component integration device in this application embodiment can also be implemented in hardware, such as a computing device, chip, or processor. For specific implementation details of the computing device, please refer to [reference needed]. Figure 3 For a description of the chip and processor's specific implementation, please refer to [link / reference]. Figure 4 The description of that will not be repeated here.

[0165] The method steps in this embodiment can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a computing device. Of course, the processor and storage medium can also exist as discrete components in a network device or terminal device.

[0166] This application also provides a computing device cluster. The computing device cluster includes at least one computing device, which may be a server. In some embodiments, the computing device may also be a desktop computer, a laptop computer, or a smartphone, or other terminal device.

[0167] like Figure 12 As shown, Figure 12 This application provides a schematic diagram of a computing device cluster, which includes at least one computing device 310. The memory 312 of one or more computing devices 310 in the computing device cluster may store the same instructions for executing component integration methods.

[0168] In some possible implementations, the memory 312 of one or more computing devices 310 in the computing device cluster may also store partial instructions for executing the component integration method. In other words, a combination of one or more computing devices 310 can jointly execute instructions for executing the component integration method.

[0169] It should be noted that the memory 312 in different computing devices 310 within the computing device cluster can store different instructions, which are used to execute certain functions of the computing devices. That is, the instructions stored in the memory 312 of different computing devices 310 can implement the functions of one or more units in the transceiver module 1110, the product requirement acquisition module 1120, and the processing module 1130.

[0170] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN). Figure 13 One possible implementation is shown. For example... Figure 13 As shown, Figure 13 This application provides a schematic diagram of a connection between computing devices, where two computing devices 310A and 310B are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this possible implementation, the instructions stored in the memory 312 of computing device 310A can implement the functions of the transceiver module 1110. Simultaneously, the instructions stored in the memory 312 of computing device 310B can implement the functions of the product requirement acquisition module 1120 and the processing module 1130.

[0171] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions capable of running on a computing device or stored on any usable medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform a component integration method.

[0172] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct a computing device to perform a component integration method.

[0173] This application also provides a chip. The chip includes an interface circuit and a control circuit. The interface circuit is used to acquire a component integration request, and the control circuit is used to implement the functions of the computing device in the component integration method.

[0174] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0175] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A component integration method, characterized in that, The method includes: In response to a component integration request, retrieve multiple components; According to the established integration specifications, obtain the product requirements corresponding to each of the multiple components; the product requirements corresponding to each component are used to indicate the integration requirements for the component; Based on the target integration version and the product requirements corresponding to the multiple components, the multiple components are integrated to obtain a target integrated component; wherein, the target integration version is used to indicate the implementation method of the product requirements, and the target integrated component includes an entry point, which supports providing the product requirements corresponding to each of the multiple components.

2. The method according to claim 1, characterized in that, The step of integrating the multiple components to obtain the target integrated component based on the target integrated version and the product requirements corresponding to the multiple components includes: Based on the target integration version and the product requirements corresponding to the multiple components, multiple transactions are generated under the target integration version; a transaction includes one or more of the following: a code file for a product requirement of a component, and configuration information for a product requirement of a component; The target integrated component is obtained by integrating the multiple components based on the multiple transactions.

3. The method according to claim 2, characterized in that, The plurality of transactions include a first transaction and a second transaction. The first transaction is determined based on the first component and the first product requirements of the first component under the target integration version. The second transaction is determined based on the second component and the first product requirements of the second component under the target integration version. Both the first transaction and the second transaction support the implementation of the first product requirements.

4. The method according to claim 3, characterized in that, The first transaction and the second transaction indicate the first code file.

5. The method according to any one of claims 2-4, characterized in that, The plurality of transactions also includes a third transaction; the third transaction is determined based on the first component and the second product requirements of the first component under the target integration version, the third transaction supports the implementation of the second product requirements, and the third transaction is used to instruct the first code file.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: In response to an access request to the target integrated component, a first interface is displayed; The first interface includes one or more of the following: the plurality of components, the plurality of transactions, the status information of each transaction in the plurality of transactions, multiple product requirements, a first correspondence relationship, and a second correspondence relationship; The transaction status information includes one or more of the following: processed, processing, unprocessed. The multiple product requirements include the product requirements corresponding to each of the multiple components. The first correspondence is used to indicate the correspondence between each of the multiple components and each of the multiple transactions. The second correspondence is used to indicate the correspondence between each of the multiple product requirements and each of the multiple transactions.

7. The method according to claim 6, characterized in that, The first interface includes an integration matrix, which is an M-row × N-column matrix, where M is the quantity of the various product requirements, N is the quantity of the various components, and the elements included in the integration matrix are the various transactions.

8. A component integration device, characterized in that, The device includes: The send / receive module is used to: retrieve multiple components in response to component integration requests; The product requirement acquisition module is used to: acquire the product requirements corresponding to each of the plurality of components according to the set integration specifications; the product requirements corresponding to each component are used to indicate the integration requirements for the component; The processing module is configured to: integrate the multiple components to obtain a target integrated component based on the target integrated version and the product requirements corresponding to the multiple components; wherein the target integrated version is used to indicate the implementation method of the product requirements, and the target integrated component includes an entry point, which supports providing the product requirements corresponding to each of the multiple components.

9. The apparatus according to claim 8, characterized in that, The processing module is specifically used to: generate multiple transactions under the target integration version according to the target integration version and the product requirements corresponding to the multiple components; a transaction is used to indicate a code file for a product requirement of a component; The processing module is further specifically used to: integrate the multiple components according to the multiple transactions to obtain the target integrated component.

10. The apparatus according to claim 9, characterized in that, The plurality of transactions include a first transaction and a second transaction. The first transaction is determined based on the first component and the first product requirements of the first component under the target integration version. The second transaction is determined based on the second component and the first product requirements of the second component under the target integration version. Both the first transaction and the second transaction support the implementation of the first product requirements.

11. The apparatus according to claim 10, characterized in that, The first transaction and the second transaction indicate the first code file.

12. The apparatus according to any one of claims 9-11, characterized in that, The plurality of transactions also includes a third transaction; the third transaction is determined based on the first component and the second product requirements of the first component under the target integration version, the third transaction supports the implementation of the second product requirements, and the third transaction is used to instruct the first code file.

13. The apparatus according to any one of claims 9-12, characterized in that, The processing module is further configured to: display a first interface in response to an access request to the target integrated component; The first interface includes: the multiple components, the multiple transactions, the status information of each transaction in the multiple transactions, multiple product requirements, a first correspondence relationship, and a second correspondence relationship; The transaction status information includes one or more of the following: processed, processing, unprocessed. The multiple product requirements include the product requirements corresponding to each of the multiple components. The first correspondence is used to indicate the correspondence between each of the multiple components and each of the multiple transactions. The second correspondence is used to indicate the correspondence between each of the multiple product requirements and each of the multiple transactions.

14. The apparatus according to claim 13, characterized in that, The first interface includes an integration matrix, which is an M-row × N-column matrix, where M is the quantity of the various product requirements, N is the quantity of the various components, and the elements included in the integration matrix are the various transactions.

15. A processor, characterized in that, The processor includes an interface circuit and a control circuit; the interface circuit is used to acquire a component integration request and, in conjunction with the control circuit, execute the method of any one of claims 1-7.

16. A computing device cluster, characterized in that, The computing device cluster includes at least one computing device, and each computing device includes a processor and memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method as described in any one of claims 1-7.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions; when the computer instructions are executed in a computing device, the computing device performs the method of any one of claims 1-7.

18. A computer program product, characterized in that, When the computer program product is run in a computing device, the computing device performs the method of any one of claims 1-7.

Images