CN118838666A - Service processing method, device, electronic equipment and computer readable medium - Google Patents

Abstract

The application discloses a service processing method, a device, electronic equipment and a computer readable medium, relating to the technical field of computers, wherein a specific implementation mode comprises the steps of receiving a service processing request and acquiring a corresponding service identifier and an interface identifier; determining the type of the implementation point according to the interface identifier; determining a corresponding target realization point based on the service identification and the realization point type; and calling the target realization point to execute the business logic method corresponding to the target realization point. Therefore, the service logic method corresponding to the local and remote system expansion points can be called and executed at any time by calling the service identification and the target implementation point corresponding to the implementation point type, and the service processing efficiency is improved.

Description

Service processing method, device, electronic equipment and computer readable medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a service processing method, a device, an electronic apparatus, and a computer readable medium.

Background

When the business processing requiring multiparty cooperation is carried out, a plurality of cooperators need to carry out cooperative development aiming at the business expansion points in advance, and can carry out cooperative development in a mode of agreeing on a protocol or can carry out cooperative development in a mode of designating an interface. The existing developed realization point can only be called in the local virtual machine, so that the service processing is limited, and the service processing efficiency is low.

Disclosure of Invention

In view of the above, embodiments of the present application provide a service processing method, apparatus, electronic device, and computer readable medium, which can solve the problem that the existing developed implementation point can only be invoked in a local virtual machine, resulting in limited service processing and low service processing efficiency.

To achieve the above object, according to an aspect of an embodiment of the present application, there is provided a service processing method, including:

Receiving a service processing request, and acquiring a corresponding service identifier and an interface identifier;

Determining the type of the implementation point according to the interface identifier;

Determining a corresponding target realization point based on the service identification and the realization point type;

and calling the target realization point to execute the business logic method corresponding to the target realization point.

Optionally, before determining the implementation point type, the method further comprises:

responding to the interface identifier corresponding to the interface extension, and acquiring the state of the candidate extension point;

determining a target candidate expansion point in the candidate expansion points according to the state;

Obtaining realization information corresponding to the target candidate expansion points, and creating the corresponding target candidate expansion points based on the realization information.

Optionally, determining the implementation point type includes:

Determining the service attribution according to the interface identification;

And determining the type of the implementation point based on the service attribution and the target candidate expansion point.

Optionally, after creating the corresponding target candidate extension point based on the implementation information, the method further comprises:

verifying the target candidate expansion points, and modifying the states of the target candidate expansion points into expanded states;

And in response to the verification passing, modifying the state of the target candidate expansion point from the expanded state to an online state.

Optionally, after creating the corresponding target candidate extension point based on the implementation information, the method further comprises:

Binding the target candidate expansion point and the service identifier, and generating corresponding notification information;

and outputting notification information.

Optionally, before determining the implementation point type, the method further comprises:

Responding to the interface identifier corresponding to the interface modification, and acquiring corresponding modification realization information;

based on the modified implementation information, updating the service logic method of the implementation point corresponding to the interface identifier.

Optionally, determining the corresponding target implementation point includes:

determining corresponding implementation points according to the service identification and the implementation point type;

And acquiring the state of the implementation point, and determining the preset default implementation point as the target implementation point in response to the state being offline.

In addition, the application also provides a service processing device, which comprises:

the receiving unit is configured to receive the service processing request and acquire a corresponding service identifier and an interface identifier;

The implementation point type determining unit is configured to determine the type of the implementation point according to the interface identifier;

The target realization point determining unit is configured to determine a corresponding target realization point based on the service identification and the realization point type;

And the execution unit is configured to call the target realization point to execute the business logic method corresponding to the target realization point.

Optionally, the apparatus further includes a target candidate extension point creation unit configured to:

responding to the interface identifier corresponding to the interface extension, and acquiring the state of the candidate extension point;

determining a target candidate expansion point in the candidate expansion points according to the state;

Obtaining realization information corresponding to the target candidate expansion points, and creating the corresponding target candidate expansion points based on the realization information.

Optionally, the implementation point type determination unit is further configured to:

Determining the service attribution according to the interface identification;

And determining the type of the implementation point based on the service attribution and the target candidate expansion point.

Optionally, the service processing device further comprises a state modifying unit configured to:

verifying the target candidate expansion points, and modifying the states of the target candidate expansion points into expanded states;

And in response to the verification passing, modifying the state of the target candidate expansion point from the expanded state to an online state.

Optionally, the service processing device further includes an information generating unit configured to:

Binding the target candidate expansion point and the service identifier, and generating corresponding notification information;

and outputting notification information.

Optionally, the service processing device further comprises an updating unit configured to:

Responding to the interface identifier corresponding to the interface modification, and acquiring corresponding modification realization information;

based on the modified implementation information, updating the service logic method of the implementation point corresponding to the interface identifier.

Optionally, the target implementation point determining unit is further configured to:

determining corresponding implementation points according to the service identification and the implementation point type;

And acquiring the state of the implementation point, and determining the preset default implementation point as the target implementation point in response to the state being offline.

In addition, the application also provides a service processing electronic device, which comprises: one or more processors; and a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the service processing method as described above.

In addition, the application also provides a computer readable medium, on which a computer program is stored, which when executed by a processor implements the service processing method as described above.

One embodiment of the above application has the following advantages or benefits: the application obtains the corresponding service identification and interface identification by receiving the service processing request; determining the type of the implementation point according to the interface identifier; determining a corresponding target realization point based on the service identification and the realization point type; and calling the target realization point to execute the business logic method corresponding to the target realization point. Therefore, the service logic method corresponding to the local and remote system expansion points can be called and executed at any time by calling the service identification and the target implementation point corresponding to the implementation point type, and the service processing efficiency is improved.

Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the application and are not to be construed as unduly limiting the application. Wherein:

Fig. 1 is a schematic diagram of a main flow of a service processing method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a main flow of a service processing method according to an embodiment of the present application;

fig. 3 is a block diagram of a service processing method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of call logic for a business processing method according to an embodiment of the present application;

fig. 5 is a schematic diagram of main units of a service processing apparatus according to an embodiment of the present application;

FIG. 6 is an exemplary system architecture diagram in which embodiments of the present application may be applied;

fig. 7 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.

Detailed Description

Exemplary embodiments of the present application will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present application are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, in the technical solution of the present disclosure, the related aspects of collecting, updating, analyzing, processing, using, transmitting, storing, etc. of the personal information of the user all conform to the rules of the related laws and regulations, and are used for legal purposes without violating the public order colloquial. Necessary measures are taken for the personal information of the user, illegal access to the personal information data of the user is prevented, and the personal information security, network security and national security of the user are maintained.

Fig. 1 is a schematic diagram of main flow of a service processing method according to an embodiment of the present application, and as shown in fig. 1, the service processing method includes:

step S101, receiving a service processing request, and obtaining a corresponding service identifier and an interface identifier.

In this embodiment, the execution body (for example, may be a server) of the service processing method may receive the service processing request by means of a wired connection or a wireless connection. The service processing request may be, for example, a request to select an optimal implementation point to execute corresponding service logic. The optimal implementation point may be a local implementation point or a remote implementation point.

The local implementation point may be provided by an integrated end system, and the remote implementation point may be provided by a co-established end system. After receiving the service processing request, the executing body can acquire the corresponding service identifier and interface identifier. Wherein the service identifier is used for representing the type of the service. The interface identifier is used to characterize the call location of the implementation point, and the call location may be local or remote, for example.

In the embodiment of the application, one interface can correspond to one or more implementation points. Each implementation point may correspond to a business logic method in the interface.

Step S102, determining the type of the implementation point according to the interface identifier.

The interface identifier may be an interface number, for example A, B, etc., which is not particularly limited in the embodiment of the present application. By way of example, interface identifier a may represent a local interface and interface identifier B may represent a remote interface. The local implementation point can be invoked via the local interface and the remote implementation point can be invoked via the remote interface. The implementation point types may include local implementation points and remote implementation points.

Specifically, before determining the implementation point type, the service processing method further includes: responding to the interface identifier corresponding to the interface modification, and acquiring corresponding modification realization information; based on the modified implementation information, updating the service logic method of the implementation point corresponding to the interface identifier.

The interface identification may also be used to characterize whether an interface is to be newly created or modified. For example, when the interface identifier includes build (only as an example and not specifically limited herein), it indicates that an interface is to be newly created; when revise (which is only an example and not specifically defined herein) is included in the interface identifier, then it is indicated that the interface is to be modified.

The execution body can modify the service logic method of the implementation point corresponding to the existing interface. When the interface identifier in the service processing request corresponds to the service logic method of the implementation point of the corresponding interface to be modified, the corresponding modification implementation information is called to update the service logic method of the implementation point corresponding to the interface identifier. For example, the modification implementation information may include a modified interface name, a target implementation point to be modified in each implementation point corresponding to the modified interface, and service logic to be replaced.

Step S103, determining corresponding target realization points based on the service identification and the realization point type.

Specifically, determining a corresponding target implementation point includes: determining corresponding implementation points according to the service identification and the implementation point type; and acquiring the state of the implementation point, and determining the preset default implementation point as the target implementation point in response to the state being offline.

The service identifier, for example bizCode =a, and the implementation point type may be, for example, a local implementation point, for example, an SPI 3 implementation point corresponding to the local service in fig. 4. The implementation point type may also be a remote implementation point, for example, an SPI 1 implementation point, an SPI 2 implementation point, and the like corresponding to the service party a in fig. 4.

As shown in fig. 4, when the service identifier is bizCode =a and the implementation point type is a remote implementation point, the corresponding implementation point determined by the service identifier and the implementation point type together may be one or more of the SPI 1 implementation point and the SPI 2 implementation point corresponding to the service party a. Then, the execution body may obtain the determined state of the corresponding implementation point, where the state may be, for example, an extended state, an up state, a down state, and the like. For example, when the determined state of the corresponding implementation point is offline, the default implementation point of the integrated end may be invoked instead, where the default implementation point may include preset execution logic that is general to the service.

Step S104, the target realization point is called to execute the business logic method corresponding to the target realization point.

When determining the target implementation point, the corresponding service logic method can be called and executed according to the type of the target implementation point, such as a local implementation point or a remote implementation point.

The embodiment obtains the corresponding service identifier and interface identifier by receiving the service processing request; determining the type of the implementation point according to the interface identifier; determining a corresponding target realization point based on the service identification and the realization point type; and calling the target realization point to execute the business logic method corresponding to the target realization point. Therefore, the service logic method corresponding to the local and remote system expansion points can be called and executed at any time by calling the service identification and the target implementation point corresponding to the implementation point type, and the service processing efficiency is improved.

Fig. 2 is a schematic flow chart of a service processing method according to an embodiment of the present application, and as shown in fig. 2, the service processing method includes:

step S201, receiving a service processing request, and obtaining a corresponding service identifier and an interface identifier.

Step S202, responding to the interface identification corresponding to the interface expansion, and acquiring the state of the candidate expansion point.

The interface identification may also be used to characterize whether an interface is to be newly created or modified. For example, when the interface identifier includes build (only as an example and not specifically limited herein), it indicates that an interface needs to be newly created, that is, interface expansion needs to be performed; when revise (which is only an example and not specifically defined herein) is included in the interface identifier, then it is indicated that the interface is to be modified. For example, when the execution subject determines that the interface identifier includes building, the interface needs to be expanded, a state of a candidate expansion point on the configuration platform is obtained, and the candidate expansion point and the application to which the state belongs are searched for.

Step S203, determining target candidate expansion points in the candidate expansion points according to the states.

Specifically, candidate expansion points with expandable states can be screened out to serve as expandable candidate expansion points. The number of expandable candidate expansion points may be one or more. When the number of the expandable candidate expansion points is a plurality, the execution body may acquire the resource occupancy rate of each expandable candidate expansion point, and determine the expandable candidate expansion point with the lowest resource occupancy rate as the target candidate expansion point.

Step S204, obtaining realization information corresponding to the target candidate expansion points, and creating the corresponding target candidate expansion points based on the realization information.

The implementation information corresponding to the target candidate extension point may include the application, remote procedure call (Remote Procedure Call, RPC) protocol supporting call, etc., and the implementation information corresponding to the target candidate extension point is not specifically limited in the embodiment of the present application.

Specifically, after creating the corresponding target candidate extension point based on the implementation information, the service processing method further includes: verifying the target candidate expansion points, and modifying the states of the target candidate expansion points into expanded states; and in response to the verification passing, modifying the state of the target candidate expansion point from the expanded state to an online state.

For example, the execution body may call the co-building end to fill in the SPI extension point interface implementation information in the service implementation interface (Service Provider Interface, SPI) configuration platform according to the approved target candidate extension point ID, submit an interface verification request, and modify the state of the target candidate extension point to an SPI extended state. And then, an integrated terminal tester can verify whether the realization of the target candidate extension point SPI RPC provided by the co-building terminal can be successfully invoked, whether the data structure meets the specification, and whether the monitoring performance meets the requirement (gray scale and white list). And if the target candidate expansion point is in the on-line SPI state, modifying the state of the target candidate expansion point into the on-line SPI state through approval. At this time, the common-build-end SPI expansion point realizes that online is really completed.

Specifically, after creating the corresponding target candidate extension point based on the implementation information, the service processing method further includes: binding the target candidate expansion point and the service identifier, and generating corresponding notification information; and outputting notification information.

For example, the execution body may call the co-building end to implement the SPI extension point in a custom manner, bind the created SPI extension point according to a preset specification to implement the logic and service identifier bizCode, and complete the RPC interface on-line. Corresponding notification information, for example, "service party a, SPI 1 realizes that the point is online", is generated, and the content and format of the generated notification information are not particularly limited in the embodiment of the present application, and the notification information is output to a terminal held by a user.

Step S205, according to the interface identification, determining the service attribution.

The interface identifier may carry an address identifier, which may be, for example, local or remote. Where local may represent local and remote may represent remote. The content of the interface identifier in the embodiment of the application is not particularly limited. When the interface is identified as local, the corresponding service attribution can be local, and when the interface is identified as remote, the corresponding service attribution can be remote.

Step S206, determining the type of the implementation point based on the service attribution and the target candidate expansion point.

For example, when the service attribution is local, according to the target candidate extension point (for example, SPI 3 implementation point), the implementation point type is determined as follows: local + SPI 3 implementation point.

Step S207, based on the service identification and the realization point type, determining the corresponding target realization point.

For example, when the implementation point type is a remote+spi 1 implementation point and the service identifier is bizCodeA, the corresponding target implementation point may be an SPI 1 implementation point of the service party a.

Step S208, the target realization point is called to execute the business logic method corresponding to the target realization point.

And acquiring a corresponding service logic method from the attribution of the target implementation point, and executing the acquired service logic method to realize service processing and improve service processing efficiency.

Fig. 3 is a block diagram of a service processing method according to an embodiment of the present application. In an embodiment of the application, SPI: service Provider Interface, a set of interfaces provided by java for implementation or extension by third parties, may be used to frame the extension and enable components. The role of the SPI is to find service implementations for these extended APIs. The business processing method of the embodiment of the application can be realized by searching for the service locally/remotely. And (3) an integration end: refers to a business system integrating SPI registration, discovery, routing and calling capabilities. The integrated party provides general service logic, and personalized logic of the co-building party service system can be called through the service identification and SPI description in an SPI enhancement mode. The integrator typically provides orchestration capability for the generic logic + the personalized logic. And (3) at the co-construction end: refers to a service system for realizing SPI interface description, namely personalized logic. SPI expansion Point: and an SPI open function point defined by the SPI configuration platform. SPI expansion point implementation: and a unit for realizing SPI extended point service logic in the service system. One SPI extension point implementation can be provided by an integrated end system (local SPI extension point implementation) or a co-build end system (remote SPI extension point implementation).

As shown in fig. 3, the SPI configuration platform: the method is divided into an Admin control console and a configuration center. The Admin console may modify/pull the configuration from the configuration center. The Admin console provides an interactive interface, and can be used for an integrated end to input SPI expansion point information, including an SPI interface, description information, belonging application, supported interface protocols and the like. The method can also be used for searching SPI expansion points by the co-building end, inputting co-building end information for interface expansion application aiming at the expansion points, generating globally unique expansion point realization ID and service identifier bizCode after the application is approved, and binding with the SPI expansion points. The configuration center stores the data stored by the Admin console and provides a subscription and push mechanism for data change events. Routing layer: the system consists of an RPC registration center and an SPI registration and routing center. The SPI registry subscribes SPI expansion point information from the configuration center, and respectively searches remote (realized by using an RPC calling mode) and local (realized by using an integrated end system local JVM calling) SPI expansion point realization information from the RPC registry and an integrated end local Spring container. The RPC registry provides registration and subscription of the RPC interface. Co-building end system: multiple co-building end systems are supported. The co-building end system is a provider for realizing the remote SPI expansion point, is responsible for registering an interface to the RPC registration center according to the SPI expansion point, and transmits a context (service identifier bizCode) in the interface for route matching for subscribing and calling by the integrated end system. Integrated end system (is a local SPI provider): RPC discovery and RPC invocation. Specifically: RPC discovery: all realization information of the appointed SPI expansion point and corresponding service identifiers bizCode are queried from the RPC registration center to the SPI registration and routing center; RPC call: whether to call a remote RPC interface or a local SPI is determined according to the SPI extension point implementation information, and which implementation point is called is determined according to the service identification bizCode +extension point implementation information so as to realize efficient service processing.

Fig. 4 is a schematic diagram of call logic of a service processing method according to an embodiment of the present application. As shown in fig. 4, the calling end system (the calling end system with service identifier bizCode is a co-building end system, and the co-building party applies to SPI configuration and distributes to service identifier bizCode, for example, service party a, i.e. co-building end a, and also may initiate an interface call (such as initiating a PC search call, an applet search call, and PC and applet are calling end systems), the called end is a universal logic integrated end system, when processing a logic registered as an SPI extension point (for example, extension points SPI1, SPI2, and SPI3 for which SPI registration has been performed) (assuming that computer search does not use price ordering, applet search uses price ordering, such that a price ordering function may be registered as an SPI extension point), the integrated end system is responsible for calling the SPI route, based on RPC protocol/call, querying the SPI extension point implementation information of the SPI registration center, and completing the implementation point call according to the extension point implementation information and service identifier bizCode (for example bizCode =a or bizCode =b). bizCode =a corresponds to business a and bizCode =b corresponds to business B. For a calling end system without a service identifier bizCode, the integrated end system will call default local service implementation by default (e.g., call SPI3 implementation point by default to complete service processing).

Co-building development can be carried out before the service logic method is called, specifically: and the integrated end issues SPI expansion point interfaces, belonging application, RPC protocol supporting calling and interface description information on the SPI configuration platform. And the default implementation of the SPI expansion point is realized on the online of the integrated end application system, and the set state is an SPI expandable state. The co-building end searches an expansion point with expandable state and belongs to an application in the SPI configuration platform, and submits an expansion request. And the SPI configuration platform management node examines the qualification of the co-building end of the submitted application, and completes authority approval through workflow. And generating a globally unique extension point realization ID and a service identifier bizCode, and informing the co-building end by mail. And the common-building end realizes SPI expansion points in a self-defined manner, realizes the bizCode relation with the SPI expansion points according to the specification and completes the on-line of the RPC interface. And the co-building terminal fills in SPI expansion point interface realization information in the SPI configuration platform according to the approved expansion point ID, submits an interface verification request, and changes the state into an SPI expanded state. The integrated terminal test node verifies whether SPI RPC realization provided by the co-building terminal can be successfully invoked, whether the data structure meets the specification, and whether the monitoring performance meets the requirement (gray scale and white list). If the SPI is in the normal state, the SPI is in the normal state through approval. At this time, the common-build-end SPI expansion point realizes that online is really completed. The common building end modifies SPI expansion point, and like a common RPC interface provider, the common building end transparently completes modification and online, and the integrated end does not sense. And after submitting a request for offline at the SPI configuration platform, an administrator adds a service identifier corresponding to the co-building end into a blacklist after approval, and the integrated end system gives up calling the SPI implementation and then calls the default implementation of the integrated end. Thereby laying a foundation for improving the service processing efficiency. The protocol is light in weight and good in expansibility, and the corresponding service logic method can be executed by routing to the appointed implementation point according to the service identification, the spi interface description and the local/remote description.

Fig. 5 is a schematic diagram of main units of a service processing apparatus according to an embodiment of the present application. As shown in fig. 5, the service processing apparatus 500 includes a receiving unit 501, an implementation point type determining unit 502, a target implementation point determining unit 503, and an executing unit 504.

The receiving unit 501 is configured to receive the service processing request, and obtain the corresponding service identifier and the interface identifier.

The implementation point type determining unit 502 is configured to determine the implementation point type according to the interface identifier.

The target implementation point determining unit 503 is configured to determine a corresponding target implementation point based on the service identifier and the implementation point type.

And the execution unit 504 is configured to call the target implementation point to execute the business logic method corresponding to the target implementation point.

In some embodiments, the apparatus further comprises a target candidate extension point creation unit, not shown in fig. 5, configured to: responding to the interface identifier corresponding to the interface extension, and acquiring the state of the candidate extension point; determining a target candidate expansion point in the candidate expansion points according to the state; obtaining realization information corresponding to the target candidate expansion points, and creating the corresponding target candidate expansion points based on the realization information.

In some embodiments, the implementation-point type determination unit 502 is further configured to: determining the service attribution according to the interface identification; and determining the type of the implementation point based on the service attribution and the target candidate expansion point.

In some embodiments, the service processing apparatus further comprises a state modifying unit, not shown in fig. 5, configured to: verifying the target candidate expansion points, and modifying the states of the target candidate expansion points into expanded states; and in response to the verification passing, modifying the state of the target candidate expansion point from the expanded state to an online state.

In some embodiments, the service processing apparatus further comprises an information generating unit, not shown in fig. 5, configured to: binding the target candidate expansion point and the service identifier, and generating corresponding notification information; and outputting notification information.

In some embodiments, the service processing apparatus further comprises an updating unit, not shown in fig. 5, configured to: responding to the interface identifier corresponding to the interface modification, and acquiring corresponding modification realization information; based on the modified implementation information, updating the service logic method of the implementation point corresponding to the interface identifier.

In some embodiments, the target implementation point determination unit 503 is further configured to: determining corresponding implementation points according to the service identification and the implementation point type; and acquiring the state of the implementation point, and determining the preset default implementation point as the target implementation point in response to the state being offline.

Note that, the service processing method and the service processing apparatus of the present application have a corresponding relationship in terms of implementation contents, and therefore, the description of the repeated contents is not repeated.

Fig. 6 illustrates an exemplary system architecture 600 to which a business processing method or business processing apparatus of embodiments of the present application may be applied.

As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used as a medium to provide communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may interact with the server 605 via the network 604 using the terminal devices 601, 602, 603 to receive or send messages, etc. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 601, 602, 603.

The terminal devices 601, 602, 603 may be various electronic devices having a business processing screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 605 may be a server providing various services, such as a background management server (by way of example only) providing support for business process requests submitted by users using the terminal devices 601, 602, 603. The background management server can receive the service processing request and acquire the corresponding service identifier and interface identifier; determining the type of the implementation point according to the interface identifier; determining a corresponding target realization point based on the service identification and the realization point type; and calling the target realization point to execute the business logic method corresponding to the target realization point. Therefore, the service logic method corresponding to the local and remote system expansion points can be called and executed at any time by calling the service identification and the target implementation point corresponding to the implementation point type, and the service processing efficiency is improved.

It should be noted that, the service processing method provided in the embodiment of the present application is generally executed by the server 605, and accordingly, the service processing apparatus is generally disposed in the server 605.

It should be understood that the number of terminal devices, networks and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 7, there is illustrated a schematic diagram of a computer system 700 suitable for use in implementing an embodiment of the present application. The terminal device shown in fig. 7 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present application.

As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the computer system 700 are also stored. The CPU701, ROM702, and RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output section 707 including a Cathode Ray Tube (CRT), a liquid crystal credit authorization query processor (LCD), and the like, and a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.

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

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

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

The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor includes a receiving unit, an implementation point type determining unit, a target implementation point determining unit, and an executing unit. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs, which when executed by one of the devices, cause the device to receive a service processing request, and obtain a corresponding service identifier and interface identifier; determining the type of the implementation point according to the interface identifier; determining a corresponding target realization point based on the service identification and the realization point type; and calling the target realization point to execute the business logic method corresponding to the target realization point.

According to the technical scheme of the embodiment of the application, the service logic method corresponding to the local and remote system expansion points is called and executed at any time by calling the service identification and the target realization point corresponding to the realization point type, so that the service processing efficiency is improved.

The above embodiments do not limit the scope of the present application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of the present application.

Claims (10)

1. A method for processing a service, comprising:

Receiving a service processing request, and acquiring a corresponding service identifier and an interface identifier;

determining the type of the implementation point according to the interface identifier;

determining a corresponding target realization point based on the service identifier and the realization point type;

And calling the target realization point to execute the business logic method corresponding to the target realization point.

2. The method of claim 1, wherein prior to said determining the type of implementation point, the method further comprises:

responding to the interface identifier corresponding to the interface expansion, and acquiring the state of the candidate expansion point;

determining a target candidate expansion point in the candidate expansion points according to the state;

Obtaining the realization information corresponding to the target candidate expansion points, and creating the corresponding target candidate expansion points based on the realization information.

3. The method of claim 2, wherein the determining the implementation point type comprises:

determining the service attribution according to the interface identification;

and determining the type of the implementation point based on the service attribution and the target candidate expansion point.

4. The method of claim 2, wherein after the creating the corresponding target candidate extension point based on the implementation information, the method further comprises:

verifying the target candidate expansion points, and modifying the states of the target candidate expansion points into expanded states;

and in response to the verification passing, modifying the state of the target candidate expansion point from the expanded state to an online state.

5. The method of claim 2, wherein after the creating the corresponding target candidate extension point based on the implementation information, the method further comprises:

binding the target candidate expansion point and the service identifier, and generating corresponding notification information;

And outputting the notification information.

6. The method of claim 1, wherein prior to said determining the type of implementation point, the method further comprises:

Responding to the interface identifier corresponding to interface modification, and acquiring corresponding modification realization information;

And updating the service logic method of the implementation point corresponding to the interface identifier based on the modification implementation information.

7. The method of claim 1, wherein the determining the corresponding target realization point comprises:

determining a corresponding implementation point according to the service identifier and the implementation point type;

And acquiring the state of the implementation point, and determining a preset default implementation point as a target implementation point in response to the state being offline.

8. A service processing apparatus, comprising:

the receiving unit is configured to receive the service processing request and acquire a corresponding service identifier and an interface identifier;

An implementation point type determining unit configured to determine an implementation point type according to the interface identifier;

A target implementation point determining unit configured to determine a corresponding target implementation point based on the service identifier and the implementation point type;

And the execution unit is configured to call the target realization point to execute the business logic method corresponding to the target realization point.

9. A business processing electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

When executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-7.

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