Request processing methods, apparatus, devices and storage media

Abstract

This application provides a request processing method, apparatus, device, and storage medium. The method includes: in response to a call to a target SPI, determining the target function point orchestration method required for executing the target SPI based on the correspondence between different participants and the function point orchestration methods of the target SPI, wherein the target SPI is invoked according to a call request initiated by a participant; executing the corresponding function points in the implementation code of the target SPI according to the target function point orchestration method, and obtaining an execution result corresponding to the call request. This application enables multiple participants to share function points in the same component using different function point orchestration methods, reducing the occurrence of identical function points being included in different components, thereby reducing code bloat and saving resources.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a request processing method, apparatus, device and storage medium. Background Technology

[0002] The middle platform system is a framework comprised of a series of execution standards, operating mechanisms, configuration management and execution systems, and an operations service team. It provides all participating parties with the ability to innovate rapidly and at low cost. After the middle platform system is established, the R&D system transforms from "centralized development to improve one's own R&D efficiency" to "distributed development to ensure global throughput and improve the R&D efficiency of participating parties," greatly enhancing the innovation efficiency of all participants.

[0003] Typically, middleware systems adopt the standard Service Provider Interface (SPI) technology architecture. From a technical framework perspective, the granularity of SPI is service-level, which is technically component-level. However, opening up the SPI granularity to participants for customization leads to the problem of bloated code. Summary of the Invention

[0004] This application provides a request processing method, apparatus, device, and storage medium to solve the problem of bloated code in the prior art where SPI is opened to participants for customization at the granularity.

[0005] In a first aspect, embodiments of this application provide a request processing method, including:

[0006] In response to a call to the target SPI, the target function point orchestration method required for executing the target SPI is determined based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked based on a call request initiated by a participant.

[0007] According to the target function point arrangement, the corresponding function points in the implementation code of the target SPI are executed to obtain the execution result corresponding to the call request.

[0008] Secondly, embodiments of this application provide a request processing method, including:

[0009] Obtain SPI registration information, which is used to register the functional points in the SPI implemented by the computing device;

[0010] Based on the SPI registration information, obtain the configuration operation for the SPI. The configuration operation is used to configure the function point orchestration method corresponding to the participants.

[0011] Based on the configuration operation, a correspondence is generated between the participants and the function point orchestration method of the SPI.

[0012] Thirdly, embodiments of this application provide a request processing apparatus, including:

[0013] The determination module is used to respond to a call to the target SPI and determine the target function point orchestration method that needs to be used to execute the target SPI based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked based on the call request for the target service initiated by the participants.

[0014] The execution module is used to execute the corresponding function points in the implementation code of the target SPI according to the target function point arrangement, and obtain the execution result corresponding to the call request.

[0015] Fourthly, embodiments of this application provide a request processing apparatus, including:

[0016] The first acquisition module is used to acquire the reported SPI registration information, which is used to register the functional points in the SPI implemented by the computing device;

[0017] The second acquisition module is used to acquire configuration operations for the SPI based on the SPI registration information. The configuration operations are used to configure the function point orchestration method corresponding to the participants.

[0018] The generation module is used to generate a correspondence between the participants and the function point orchestration method of the SPI according to the configuration operation.

[0019] Fifthly, embodiments of this application provide a computing device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of the first aspects.

[0020] In a sixth aspect, embodiments of this application provide a computer device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of the second aspects.

[0021] In a seventh aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed, implements the method as described in any one of the first aspects.

[0022] Eighthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed, implements the method as described in any one of the second aspects.

[0023] This application also provides a computer program, which, when executed by a computer, is used to implement the method as described in any of the first aspects.

[0024] This application also provides a computer program, which, when executed by a computer, is used to implement the method described in any of the second aspects.

[0025] In this embodiment, the development platform, based on SPI, supports participants in customizing finer-grained function point orchestration within SPI. The computing device containing the SPI implementation code can execute the corresponding function points in the SPI implementation code according to the participant's custom function point orchestration, obtaining the execution result corresponding to the call request initiated by the participant. This achieves customization by opening up the function points to participants at the granularity of function points, allowing multiple participants to share function points in the same component with different function point orchestration methods. This reduces the occurrence of the same function points being included in different components, thereby alleviating code bloat and saving resources. Attached Figure Description

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

[0027] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0028] Figure 2 A flowchart illustrating a request processing method provided in an embodiment of this application;

[0029] Figure 3 A flowchart illustrating a request processing method provided in another embodiment of this application;

[0030] Figure 4 A block diagram illustrating a request processing method provided in an embodiment of this application;

[0031] Figure 5 A block diagram of a request processing method provided in another embodiment of this application;

[0032] Figure 6 A block diagram of a request processing method provided in yet another embodiment of this application;

[0033] Figure 7 This is a schematic diagram of the structure of a request processing apparatus provided in an embodiment of this application;

[0034] Figure 8 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0035] Figure 9 A schematic diagram of the structure of a request processing apparatus provided in another embodiment of this application;

[0036] Figure 10 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0039] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0040] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0041] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes said element.

[0042] Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0043] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application, such as... Figure 1 As shown, this application scenario may include: multiple participants 11 and a development platform 12. The development platform 12 adopts the standard SPI technology architecture, which can provide customized development capabilities for different participants. The developers of the participants 11 can carry out development work based on the development platform 12.

[0044] Participant 11 can initiate a call request for a specific SPI customized based on development platform 12. Development platform 12 can call the SPI locally or remotely, so that the computing device where the SPI's implementation code resides executes the SPI's implementation code and obtains the execution result corresponding to the call request. Specifically, when the computing device where the SPI's implementation code resides is the same as the computing device where development platform 12 resides, development platform 12 can call the SPI locally. When the computing device where the SPI's implementation code resides is not the same as the computing device where development platform 12 resides, development platform 12 can call the SPI remotely.

[0045] Specifically, the development platform 12 can be any type of platform capable of providing customized development capabilities to participating parties. For example, the development platform 12 may include a middle platform, which is an intermediate platform integrated to improve development efficiency. This middle platform can be called a middle platform system. Enterprises may have multiple teams handling development work in different areas. Different teams can be understood as different participating parties, which may include, for example, Tmall Supermarket, International Direct Sales, and Kaola Direct Sales.

[0046] In this embodiment, the implementation code of a single SPI can be understood as a component, which can refer to a combinational logic processing module with specific practical significance. The implementation code of a single SPI can include multiple functional points (also called capability points). A functional point refers to a general, fine-grained logic processing module under a specific component. For example, the code implementing the warehouse editing processing logic can be considered a component. This component can implement four processing logics: add, delete, modify, and search. Therefore, this component can be considered to include the four functional points of add, delete, modify, and search.

[0047] Typically, the development platform 12 is opened up to participants for customization at the granularity of SPI. Different participants can customize different SPIs. For example, one participant can customize one SPI to provide filtering services, and another participant can customize another SPI to provide filtering services. Since both SPIs provide filtering services, some functionalities can be the same. However, since these two SPIs correspond to different components, the same functionalities are contained in different components, which leads to the technical problem of bloated code.

[0048] To address the technical problem of bloated code resulting from offering SPI (Integrated Function Point) at a granular level for customization by participating parties, this application embodiment proposes a development platform that, based on SPI, supports participating parties in customizing the orchestration of function points within the SPI at a finer granularity. The computing device containing the SPI implementation code can execute the corresponding function points in the SPI implementation code according to the participating party's customized function point orchestration, obtaining the execution result corresponding to the call request initiated by the participating party. This achieves the goal of allowing multiple participating parties to share function points in the same component with different function point orchestration methods by offering SPI at a granular level for customization. This reduces the occurrence of identical function points being included in different components, thereby alleviating code bloat and saving resources.

[0049] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0050] Figure 2 This is a flowchart illustrating a request processing method provided in one embodiment of this application. The execution entity in this embodiment can be the computing device where the SPI implementation code resides, such as... Figure 2 As shown, the method in this embodiment may include:

[0051] Step 21: In response to the call to the target SPI, determine the target function point orchestration method that needs to be used to execute the target SPI based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked according to the call request initiated by the participant.

[0052] Step 22: According to the target function point arrangement, execute the corresponding function point in the implementation code of the target SPI to obtain the execution result corresponding to the call request.

[0053] In this embodiment, the target SPI refers to the SPI that needs to be invoked based on the invocation request initiated by the participant. The participant can be... Figure 1 Any one of the 11 participating parties.

[0054] In one embodiment, the target SPI can be derived from... Figure 1 In this embodiment, the computing device containing the implementation code of the target SPI can be the computing device of participant 11, and participant 11's computing device can run the implementation code of the target SPI. In this case, the method provided in this embodiment can be applied to the participant implementing the target SPI. It should be noted that the participant implementing the target SPI and the participant initiating the call request can be the same participant or different participants.

[0055] In another embodiment, the target SPI can be derived from... Figure 1 The development platform 12 is implemented in this embodiment. That is, the computing device where the implementation code of the target SPI is located can be the computing device of the development platform 12. The computing device of the development platform 12 can run the implementation code of the target SPI. In this case, the method provided in this embodiment can be applied to the development platform 12.

[0056] In the case where the target SPI is implemented by the development platform, the functionalities in the target SPI's implementation code can be written by the platform's developers, or they can be obtained by converting the functionalities implemented by the participants into platform-wide capabilities. To quickly convert the functionalities implemented by the participants into the platform's implementation, the boxing principle can be used. This boxing principle can be intuitively understood as placing the functionalities implemented by the participants into boxes and moving them to the platform. Technically, this unifies the context of the functionalities (i.e., the input and output of the code). That is, the objects defined for the functionalities in the platform code must be completely consistent with the objects defined for the functionalities in the application that defines the functionalities. This ensures that the functionalities in the participants' custom SPIs can interoperate with the platform's functionalities. If the implementation logic of a certain functionality is consistent across multiple participants, then that functionality can be quickly migrated to the platform as a general functionality.

[0057] The development platform can obtain the call request initiated by the participant, determine the target SPI for responding to the call request, and invoke the target SPI according to the call request. For example, it can determine the target service for which the call request is directed, and determine the target SPI for responding to the call request based on the correspondence between different participants and SPIs for the target service. It should be noted that the specific method for determining the target SPI for responding to the call request is not limited in this embodiment.

[0058] Specifically, when the target SPI is implemented by the development platform, invoking the target SPI according to the call request can include: invoking the target SPI locally according to the call request; when the target SPI is implemented by a participant, invoking the target SPI according to the call request can include: remotely invoking the target SPI according to the call request. For example, when the target SPI is implemented by a participant, the target SPI may have a corresponding tag. The tag of the target SPI can be assigned by the service registry and can be used by the service registry to determine the computing device implementing the target SPI. In this case, when the target SPI is implemented by a participant, the development platform can call the implementation code of the target SPI implemented by the participant's computing device by addressing the target SPI to the service registry based on the target SPI's tag. It should be noted that the specific methods for locally invoking and remotely invoking the SPI can be found in the detailed descriptions in related technologies, and will not be repeated here.

[0059] In this embodiment of the application, the implementation code of the target SPI may include multiple function points, the target SPI may have at least one function point arrangement method, each function point arrangement method may correspond to one or more participants, and each function point arrangement method of the target SPI involves at least some function points in the target SPI.

[0060] For example, the computing device can locally cache the correspondence between different participants and the function point orchestration of the target SPI. For example, the function point orchestration corresponding to a particular participant in the correspondence between different participants and the target SPI can be determined as the function point orchestration required for executing the target SPI (i.e., the target function point orchestration). The target function point orchestration corresponding to this participant can be customized by exposing function points in the target SPI to that participant.

[0061] Optionally, the correspondence between different participants and the function point orchestration of the target SPI can be generated by the SPI registration management platform. In this case, the method provided in this embodiment may further include: receiving the correspondence between different participants and the function point orchestration of the target SPI configured by the SPI registration management platform. For a detailed description of the specific implementation of generating participant and function point orchestration for different SPIs, please refer to the following description.

[0062] The target function point orchestration method corresponding to the participant can be used to describe which function points in the implementation code of the target SPI need to be executed in response to a call request initiated by the participant to the target SPI, and in what order these function points are executed. Therefore, the determined target function point orchestration method can be used to characterize multiple function points of the target SPI that need to be executed and the execution order of these function points. In one embodiment, the target function point orchestration method may include identifiers of multiple function points in the target SPI arranged sequentially from front to back according to the execution order; the identifier of a function point can be the name of the function point.

[0063] In this embodiment, after determining the target function point orchestration method that the target SPI needs to be based on, the corresponding function points in the implementation code of the target SPI can be executed according to the target function point orchestration method to obtain the execution result corresponding to the call request. In one embodiment, if the target function point orchestration method includes the identifiers of multiple function points arranged in order of execution from front to back, each of the multiple function points in the implementation code of the target SPI can be executed sequentially according to the order of the identifiers of the multiple function points to obtain the execution result corresponding to the call request.

[0064] When the target SPI is implemented by the development platform, the development platform can return the execution result as the return result of the call request; when the SPI is implemented by the participating party, the participating party can return the execution result as the return result of the call target SPI to the development platform, and the development platform can return the return result as the return result of the call request.

[0065] The request processing method provided in this embodiment, in response to a call to the target SPI, determines the target function point orchestration method required for executing the target SPI based on the correspondence between different participants and the function point orchestration methods of the target SPI. According to the target function point orchestration method, the corresponding function points in the implementation code of the target SPI are executed, resulting in an execution result corresponding to the call request. This enables the SPI call to be responded to according to the function point orchestration method of the participant, allowing multiple participants to share function points in the same component with different function point orchestration methods. This reduces the occurrence of identical function points being included in different components, thereby alleviating code bloat and saving resources.

[0066] Figure 3 This is a flowchart illustrating a request processing method provided in another embodiment of this application. The method provided in this embodiment can be applied to an SPI registration management platform, which can be deployed on a computer device, such as... Figure 3 As shown, the method in this embodiment may include:

[0067] Step 31: Obtain SPI registration information. SPI registration information is used to register the function points in the SPI implemented by the computing device.

[0068] Step 32: Obtain the configuration operation for SPI based on the SPI registration information. The configuration operation is used to configure the function point orchestration method corresponding to the participants.

[0069] Step 33: Based on the configuration operation, generate the correspondence between the participants and the function point orchestration method of the SPI.

[0070] In this embodiment, obtaining SPI registration information may include receiving SPI registration information reported by a computing device, thereby enabling automatic reporting of function points in the SPI, which reduces labor costs compared to manual methods. For example, the computing device may include the computing device of the development platform and / or the computing devices of participating parties.

[0071] In one embodiment, the development toolkit provided by the development platform can support the automatic reporting of SPI registration information. For example, the development toolkit running on the computing device can automatically scan the SPIs implemented on the computing device based on code tags to obtain the identifiers of the function points in the SPI implementation. For participating computing devices, the SPI registration information can be reported to the SPI registration management platform through the service registry center. The service registry center can assign tags to the SPIs implemented on the participating computing devices. To enable the development platform to call the implementation code of the target SPI implemented on the participating computing device by addressing the target SPI to the service registry center based on its tag, the SPI tag and the identifiers of the SPI function points can be included together in the SPI registration information and reported to the SPI registration management center.

[0072] In this embodiment, after obtaining the SPI registration information, configuration operations for the SPI can be obtained based on the SPI registration information. These configuration operations can be used to configure the function point orchestration method corresponding to the participating parties. The function point orchestration method can include identifiers of multiple function points in the SPI arranged sequentially from front to back according to their execution order.

[0073] For example, in response to input operations from a participant, the configuration interface can display the identifiers of all function points of a specific SPI. It can also obtain configuration operations for that SPI through the configuration interface, allowing the participant to customize the corresponding function point orchestration. Of course, in other embodiments, configuration operations for the SPI can be obtained in other ways, and this application does not limit this. Optionally, when the same service can correspond to multiple SPIs, the configuration operations can also be used to configure the SPI corresponding to the participant.

[0074] In this embodiment of the application, after obtaining the configuration operation, a correspondence between the participants and the function point orchestration methods of the SPI can be generated based on the configuration operation. Generating the correspondence between the participants and the function point orchestration methods of the SPI may include establishing a correspondence between the participants and the function point orchestration methods of the SPI, or updating the correspondence between the participants and the function point orchestration methods of the SPI.

[0075] After generating the correspondence between participants and the function point arrangement of a certain SPI, if the computing device implementing the SPI and the device executing the method of this embodiment are different devices, the generated correspondence between participants and the function point arrangement of the SPI can also be sent to the computing device implementing the SPI. Based on this, the method provided in this application embodiment may further include: sending the correspondence between participants and the function point arrangement of the SPI to the computing device.

[0076] The method provided in this embodiment obtains SPI registration information, which is used to register the function points in the SPI implemented by the computing device. Based on the SPI registration information, it obtains configuration operations for the SPI, which are used to configure the function point orchestration method corresponding to the participants. Based on the configuration operations, it generates a correspondence between the participants and the function point orchestration methods. This enables the SPI to be customized by the participants at the function point granularity, allowing the participants to customize the function point orchestration method of the SPI as needed. This allows multiple participants to share the function points in the same component with different function point orchestration methods, reducing the occurrence of the same function points being included in different components, thereby reducing code bloat and saving resources.

[0077] Taking the development platform as an example, in one embodiment, the implementation block diagram of the request processing method provided in this application embodiment can be as follows: Figure 4 As shown. Figure 4 In this context, the basic platform is included in the middleware, while the external host machine is not. The external host machine can be understood as a computing device outside the middleware. The basic platform can define the name of the SPI (Service Provider Interface). Both the basic platform and the external host machine can implement the SPI defined by the basic platform, that is, implement the specific processing logic of the SPI defined by the basic platform. Specifically, the SPI implemented by the external host machine is... Figure 4 The "customized SPI implementation code" in the document.

[0078] Figure 4 The reporting arrow from "the implementation code of the customized SPI" to "the service address of the customized SPI implementation" indicates that the external host registers the service with the service registry, so that the service registry can assign a tag to the customized SPI.

[0079] The hook function (i.e., the first hook function) in the development toolkit on the external host machine can automatically scan and report SPI registration information through the service registry. The SPI registration information can include the SPI's tag and the identifier of the SPI's function points. For example... Figure 4 As shown, the first hook function can address the registration information reporting service address in the service registry center, and actively report the SPI registration information to the SPI registration & management through remote calls. The SPI registration & management can be understood as the aforementioned SPI registration management platform.

[0080] SPI registration and management can obtain SPI registration information reported by the external host. Based on the SPI registration information, configuration operations can be obtained. These operations can generate the correspondence between participants and the SPIs implemented by the external host, as well as the correspondence between the function point orchestration methods of the participants and the SPIs implemented by the external host. Configuration messages for configuring the correspondence between participants and the SPIs implemented by the external host can also be sent to the planning platform. The hook function in the planning platform's development toolkit (which can be referred to as the second hook function) can filter configuration messages, allowing the planning platform to update its local cache configuration based on these messages. Additionally, SPI registration and management can also send configuration messages for configuring the correspondence between participants and the function point orchestration methods of the SPIs implemented by the external host. The first hook function on the external host can filter these configuration messages, allowing the external host to update its local cache configuration based on these messages. This process... Figure 4 Not shown in the image.

[0081] like Figure 4 As shown, in the warehouse entry decision application scenario, when a participant (denoted as participant x) initiates a call request for a certain service, the call request can first reach the warehouse entry decision entry point of the planning infrastructure platform. The platform's general filtering node can filter according to the configuration of the local cache. Specifically, based on the local cache's mapping relationship between participants and SPIs for that service, if the SPI corresponding to participant x is implemented by the planning infrastructure platform, the call request can be filtered out and invoked through a local call. If the SPI corresponding to participant x is not implemented by the planning infrastructure platform, the call request can be intercepted by a customized SPI routing hook.

[0082] The customized SPI routing hook can address the customized SPI implementation service address in the service registry based on the mapping relationship between the generated SPI tag and the service address. It then invokes the customized SPI implementation code on the external host machine via remote call. The first hook function on the external host machine can control the execution of the corresponding function points in the customized SPI implementation code according to the function point arrangement of participant x, obtaining the execution result corresponding to the call request. The execution result can be returned to the customized SPI routing hook through the customized SPI implementation service address in the service registry, and the customized SPI routing hook can return the execution result as the return result of the call request.

[0083] It should be noted that, Figure 4 The implementation block diagram shown is for illustrative purposes only.

[0084] Taking the warehouse entry decision-making scenario as an example, from the perspective of process division, such as Figure 5As shown, it can be divided into three stages: function point management, open participant configuration, and warehouse entry decision execution.

[0085] During the function point management phase, the development platform can register its locally implemented SPI (which can be uniformly referred to as the general verification component) for verification to the SPI registration management platform, and the participating party's computing devices can register their implemented SPI (which can be uniformly referred to as the participant-customized verification component) for verification to the SPI registration management platform. The general verification component may include, for example, multiple functions such as obtaining prohibited warehouse information, filtering lines through prohibited warehouses, obtaining order warehouse information, filtering lines through order warehouses, and filtering based on filing logic. The participant-customized verification component may include, for example, multiple functions such as filtering based on the international direct-sales blacklist, verifying the consistency of Koala filings, and filtering for entry into international platform source warehouses.

[0086] During the open participant configuration phase, the arrangement of corresponding function points for participants can be configured based on the function points included in the general verification component and the participant-customized verification component. For example, the general extraction component can be configured to include multiple function points such as product warehousing relationship acquisition and product registration information acquisition. The general filtering component can be configured to include multiple function points such as registration condition filtering and merchant warehouse ordering relationship filtering. The participant-customized filtering component can be configured to include multiple function points such as international direct sales blacklist filtering.

[0087] During the warehouse entry decision-making stage, the function point arrangement method corresponding to the participants can be determined according to the configuration, and the corresponding function points in the components can be executed according to the determined function point arrangement method.

[0088] Taking the warehouse entry decision-making scenario as an example, from the perspective of layered implementation, such as Figure 6 As shown, it can be divided into three layers: base layer, control layer, and base layer.

[0089] The base layer can include an automatic function point registration component, a function point configuration & orchestration component, a function point routing component, and a white-box component. The automatic function point registration component is used by compute nodes to automatically register function points in their implemented SPIs. The SPI configuration & function point orchestration component is used by compute nodes to update the SPIs corresponding to the participants in their local cache and the function point orchestration methods corresponding to the participants. The function point routing component is used by compute nodes to execute the corresponding function points in the SPI implementation code according to the function point orchestration method. The white-box component is used by compute nodes to record the decision results of which function point orchestration method to use for easy tracking.

[0090] The control layer may include an SPI configuration component and a function point management component. The SPI configuration component can be used to obtain configuration operations and generate a correspondence between participants and SPIs based on the configuration operations. The function point management component can be used to obtain configuration operations and generate a correspondence between participants and function point orchestration methods based on the configuration operations.

[0091] The execution layer can include international direct sales filtering schemes, user-to-manufacturer (C2M) filtering schemes, and Koala direct sales filtering schemes. Each filtering scheme can be implemented as a component, and the functional points in each component can be customized by the corresponding participants. For example, the international direct sales filtering scheme can include multiple functional points such as obtaining prohibited warehouse transfer information, filtering through prohibited warehouse transfer routes, obtaining order warehouses, filtering through order warehouses, and filtering industry lists. The C2M filtering scheme and Koala direct sales filtering scheme can include multiple functional points such as obtaining prohibited warehouse transfer information, filtering through prohibited warehouse transfer routes, obtaining order warehouses, filtering through order warehouses, and filtering through filing logic.

[0092] Figure 7 This is a schematic diagram of the structure of a request processing apparatus provided in an embodiment of this application; see attached drawing. Figure 7 As shown, this embodiment provides an apparatus that can perform the above-described... Figure 2 The method provided in the illustrated embodiment, specifically, the apparatus may include:

[0093] The determination module 71 is used to respond to the call to the target SPI, and determine the target function point orchestration method that needs to be used to execute the target SPI based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked according to the call request for the target service initiated by the participants.

[0094] The execution module 72 is used to execute the corresponding function points in the implementation code of the target SPI according to the target function point arrangement, and obtain the execution result corresponding to the call request.

[0095] In one embodiment, the target function point orchestration method includes identifiers of multiple function points arranged sequentially from front to back in the target SPI according to the execution order; the execution module 72 is specifically used to execute each of the multiple function points in the implementation code of the target SPI in the order of the identifiers of the multiple function points, and obtain the execution result corresponding to the call request.

[0096] In one embodiment, the target SPI is implemented by a participant, and the method is applied to the participant.

[0097] In one embodiment, the target SPI is implemented by a development platform, and the method is applied to the development platform.

[0098] In one embodiment, the apparatus provided in this embodiment may further include: a calling module, configured to acquire the calling request initiated by the participating party, determine the target SPI responding to the calling request, and call the target SPI locally according to the calling request.

[0099] In one embodiment, the target function point orchestration method corresponding to the participant is obtained by opening up the function points in the target SPI to the participant for customization.

[0100] In one embodiment, the apparatus provided in this embodiment may further include: a receiving module, used to receive the correspondence configured by the SPI registration management platform.

[0101] Figure 7 The device shown can perform Figure 2 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 2 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 2 The descriptions in the illustrated embodiments will not be repeated here.

[0102] In one possible implementation, Figure 7 The structure of the device shown can be implemented as a computing device. For example... Figure 8 As shown, the computing device may include a processor 81 and a memory 82. The memory 82 is used to store data that supports the computing device in performing the above-described tasks. Figure 2 In the illustrated embodiment, the processor 81 is configured to execute a program stored in the memory 82.

[0103] The program includes one or more computer instructions, wherein the one or more computer instructions, when executed by the processor 81, can perform the following steps:

[0104] In response to a call to the target SPI, the target function point orchestration method required for executing the target SPI is determined based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked based on a call request initiated by a participant.

[0105] According to the target function point arrangement, the corresponding function points in the implementation code of the target SPI are executed to obtain the execution result corresponding to the call request.

[0106] Optionally, processor 81 is also used to perform the aforementioned Figure 2 All or part of the steps in the illustrated embodiments.

[0107] The computing device may also include a communication interface 83 for communicating with other devices or communication networks.

[0108] Figure 9 A schematic diagram of the structure of a request processing apparatus provided in another embodiment of this application; see attached drawing. Figure 9 As shown, this embodiment provides an apparatus that can perform the above-described... Figure 3 The method provided in the illustrated embodiment, specifically, the apparatus may include:

[0109] The first acquisition module 91 is used to acquire the reported SPI registration information, which is used to register the functional points in the SPI implemented by the computing device;

[0110] The second acquisition module 92 is used to acquire configuration operations for the SPI based on the SPI registration information. The configuration operations are used to configure the function point orchestration method corresponding to the participants.

[0111] The generation module 93 is used to generate a correspondence between the participants and the function point arrangement of the SPI according to the configuration operation.

[0112] In one embodiment, the function point orchestration method includes identifiers of multiple function points arranged sequentially from front to back in the SPI according to their execution order.

[0113] In one embodiment, the apparatus provided in this embodiment further includes a sending module, used to send the correspondence between the participants and the function point arrangement of the SPI to the computing device.

[0114] Figure 9 The device shown can perform Figure 3 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 3 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 3 The descriptions in the illustrated embodiments will not be repeated here.

[0115] In one possible implementation, Figure 9 The structure of the device shown can be implemented as a computer device. For example... Figure 10 As shown, the computer device may include a processor 101 and a memory 102. The memory 102 is used to store data that supports the computer device in performing the above-described tasks. Figure 3 In the illustrated embodiment, the processor 101 is configured to execute a program stored in the memory 102.

[0116] The program includes one or more computer instructions, wherein when executed by processor 101, the one or more computer instructions can perform the following steps:

[0117] Obtain SPI registration information, which is used to register the functional points in the SPI implemented by the computing device;

[0118] Based on the SPI registration information, obtain the configuration operation for the SPI. The configuration operation is used to configure the function point orchestration method corresponding to the participants.

[0119] Based on the configuration operation, a correspondence is generated between the participants and the function point orchestration method of the SPI.

[0120] Optionally, the processor 101 is also used to perform the aforementioned Figure 3 All or part of the steps in the illustrated embodiments.

[0121] The computer device may also include a communication interface 103 for communicating with other devices or communication networks.

[0122] In addition, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, which, when executed, performs the following: Figure 2 The method described in the illustrated embodiment.

[0123] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed, performs the following... Figure 3 The method described in the illustrated embodiment.

[0124] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0125] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of a necessary general-purpose hardware platform, or by a combination of hardware and software. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a computer product. This application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0126] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable device, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0127] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0128] These computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0129] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0130] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0131] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, linked lists, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A request processing method, characterized in that, This application is used in scenarios where a development platform employs a Service Provider Interface (SPI) technology architecture to provide customized development capabilities for different participants. The implementation code of a single SPI, which the development platform exposes to the participants for customization, includes multiple functional points that are also exposed for customization. This results in multiple functional point orchestration methods for the single SPI, each involving at least some of the multiple functional points included in the single SPI implementation code, including: In response to a call to the target SPI, the target function point orchestration method required for executing the target SPI is determined based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked based on a call request initiated by a participant. According to the target function point arrangement, the corresponding function points in the implementation code of the target SPI are executed to obtain the execution result corresponding to the call request.

2. The method according to claim 1, characterized in that, The target function point orchestration method includes the identifiers of multiple function points in the target SPI arranged sequentially from front to back according to the execution order; The step of executing the corresponding function points in the implementation code of the target SPI according to the target function point arrangement to obtain the execution result corresponding to the call request includes: executing each of the multiple function points in the implementation code of the target SPI in sequence according to the arrangement order of the identifiers of the multiple function points to obtain the execution result corresponding to the call request.

3. The method according to claim 1 or 2, characterized in that, The target SPI is implemented by the participating party, and the method is applied to the participating party.

4. The method according to claim 1 or 2, characterized in that, The target SPI is implemented by the development platform, and the method is applied to the development platform.

5. The method according to claim 3, characterized in that, Before determining the target function point orchestration method required for executing the target SPI based on the correspondence between different participants and the function point orchestration methods of the target SPI in response to a call to the target SPI, the method further includes: Obtain the invocation request initiated by the participating party; Determine the target SPI that responds to the invocation request; The target SPI is invoked locally according to the invocation request.

6. The method according to claim 1, characterized in that, The method further includes receiving the correspondence configured by the SPI registration management platform.

7. A request processing method, characterized in that, This application is used in scenarios where a development platform employs a Service Provider Interface (SPI) technology architecture to provide customized development capabilities for different participants. The implementation code of a single SPI, which the development platform exposes to the participants for customization, includes multiple functional points that are also exposed for customization. This results in multiple functional point orchestration methods for the single SPI, each involving at least some of the multiple functional points included in the single SPI implementation code, including: Obtain SPI registration information, which is used to register the functional points in the SPI implemented by the computing device; Based on the SPI registration information, obtain the configuration operation for the SPI. The configuration operation is used to configure the function point orchestration method corresponding to the participants. Based on the configuration operation, a correspondence is generated between the participants and the function point orchestration methods of the SPI, thereby obtaining a target SPI with multiple function point orchestration methods, and each function point orchestration method involves at least some of the function points among the multiple function points included in its implementation code.

8. The method according to claim 7, characterized in that, The function point arrangement method includes the identifiers of multiple function points in the SPI arranged sequentially from front to back according to the execution order.

9. The method according to claim 7, characterized in that, The method further includes sending the correspondence between the participants and the function point arrangement of the SPI to the computing device.

10. A request processing apparatus, characterized in that, This application is used in scenarios where a development platform employs a Service Provider Interface (SPI) technology architecture to provide customized development capabilities for different participants. The implementation code of a single SPI, which the development platform exposes to the participants for customization, includes multiple functional points that are also exposed for customization. This results in multiple functional point orchestration methods for the single SPI, each involving at least some of the multiple functional points included in the single SPI implementation code, including: The determination module is used to respond to a call to the target SPI and determine the target function point orchestration method that needs to be used to execute the target SPI based on the correspondence between different participants and the function point orchestration method of the target SPI. The target SPI is invoked based on the call request for the target service initiated by the participants. The execution module is used to execute the corresponding function points in the implementation code of the target SPI according to the target function point arrangement, and obtain the execution result corresponding to the call request.

11. A request processing apparatus, characterized in that, This application is used in scenarios where a development platform employs a Service Provider Interface (SPI) technology architecture to provide customized development capabilities for different participants. The implementation code of a single SPI, which the development platform exposes to the participants for customization, includes multiple functional points that are also exposed for customization. This results in multiple functional point orchestration methods for the single SPI, each involving at least some of the multiple functional points included in the single SPI implementation code, including: The first acquisition module is used to acquire the reported SPI registration information, which is used to register the functional points in the SPI implemented by the computing device; The second acquisition module is used to acquire configuration operations for the SPI based on the SPI registration information. The configuration operations are used to configure the function point orchestration method corresponding to the participants. The generation module is used to generate a correspondence between the participants and the function point orchestration methods of the SPI according to the configuration operation, thereby obtaining a target SPI with multiple function point orchestration methods, and each function point orchestration method involves at least some of the function points among the multiple function points included in its implementation code.

12. A computing device, characterized in that, include: A memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of claims 1 to 6.

13. A computer device, characterized in that, include: A memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of claims 7 to 9.

14. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed, implements the method as described in any one of claims 1 to 9.

Images