Middleware-based business platform capability calling method and device, equipment and medium

Abstract

The invention discloses a service platform capability calling method and device based on middleware, equipment and a medium, and the method comprises the steps: sending a user identification obtaining request to the middleware through a target application, and enabling the middleware to forward the user identification obtaining request to a target service platform; generating a user identifier according to the current user information through the target service platform, and returning the user identifier to the middleware; associating the target application and the target service platform with the user identifier through the middleware to obtain a user association identifier, and returning the user association identifier to the target application; and binding the user association identifier with the current session through the target application, and calling the data interface capability of the target service platform from the middleware by using the user association identifier. The application development and integration efficiency is improved, and the method can be widely applied to the technical field of software development.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a method, device, equipment and medium for calling business platform capabilities based on middleware. Background Art

[0002] With the popularization of digital transformation, more and more digital business platforms for urban and rural management have emerged, including smart communities, digital villages, digital cities, etc. There are also many companies on the market that keep up with the digital transformation strategy and build different business platforms in communities, villages, etc. for different customer groups. Due to differences in markets, user groups, etc., the infrastructure of business platforms may also be different, but in fact, they sometimes have the same requirements for the applications they use. Business platforms generally have two options for application needs, one is self-developed applications, and the other is to introduce external applications through ecological cooperation. Due to the different underlying logic of the business platform, no matter which method the business platform chooses, it is necessary to repeatedly develop or integrate the application, which affects the efficiency of application development and integration.

[0003] Terminology explanation:

[0004] Business Platform: A business platform is a comprehensive digital system or framework designed to support and manage the core business processes, operations and services of an enterprise or organization. The platform usually has integration capabilities and integrates various technical tools and applications to improve business efficiency, data management and decision support capabilities.

[0005] Application: refers to a program or software component that is specially designed and developed to run on a specific business platform. These applications are designed to expand or enhance the functionality of the business platform to meet specific business needs and improve operational efficiency.

[0006] Integration: The process of seamlessly connecting and coordinating different business platforms, applications and business processes. Its purpose is to unify and coordinate the independent parts so that they can interoperate effectively, thereby achieving data sharing, process optimization and overall business efficiency improvement. Summary of the invention

[0007] The purpose of the present invention is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0008] To this end, an object of an embodiment of the present invention is to provide a middleware-based service platform capability calling method, which improves the efficiency of application development and integration.

[0009] Another object of an embodiment of the present invention is to provide a service platform capability calling device based on middleware.

[0010] In order to achieve the above technical objectives, the technical solutions adopted by the embodiments of the present invention include:

[0011] On the one hand, an embodiment of the present invention provides a method for calling a service platform capability based on middleware, comprising the following steps:

[0012] Sending a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target service platform;

[0013] Generate a user ID according to the current user information through the target service platform, and return the user ID to the middleware;

[0014] Associating the target application and the target service platform with the user identifier through the middleware to obtain a user association identifier, and returning the user association identifier to the target application;

[0015] The user association identifier is bound to the current session through the target application, and the data interface capability of the target service platform is called to the middleware using the user association identifier.

[0016] Furthermore, in one embodiment of the present invention, the target application is located at the application layer, the target business platform is located at the business platform layer, the business platform layer and the application layer are decoupled through the middleware, the business platform layer is used to provide corresponding data interface capabilities according to different application scenarios, the middleware is used to abstract and unify the data interface capabilities of the business platform layer to form a unified external business interface capability, and provide the business interface capability through the capability interface of the middleware, and the application layer is used to call the data interface capabilities of the business platform layer through the capability interface of the middleware.

[0017] Further, in an embodiment of the present invention, sending a user identification acquisition request to the middleware through the target application so that the middleware forwards the user identification acquisition request to the target service platform specifically includes:

[0018] In response to a user entering an application on the target service platform, jumping from the target service platform to the target application;

[0019] identifying the service platform information carried in the jump request address through the target application, generating a user identification acquisition request according to the service platform information, and then sending the user identification acquisition request to the middleware;

[0020] The service platform information carried in the user identification acquisition request is identified by the middleware, and the user identification acquisition request is forwarded to the target service platform according to the service platform information.

[0021] Further, in an embodiment of the present invention, the using the user association identifier to call the data interface capability of the target service platform to the middleware specifically includes:

[0022] When the user needs to obtain business platform data during the operation of the target application, an interface capability call request is generated according to the data requirement and the user association identifier, and the interface capability call request is sent to the middleware;

[0023] The middleware identifies the data requirement and the user association identifier carried in the interface capability call request, determines the corresponding target business platform and the user identifier according to the user association identifier, verifies the validity of the user identifier in the target application, and converts the capability interface of the middleware into the capability interface of the target business platform, and then forwards the interface capability call request to the target business platform;

[0024] Identify the data requirement and the user association identifier carried in the interface capability call request through the target business platform, determine the corresponding user identifier according to the user association identifier, verify the validity of the user identifier in the middleware, and return the business platform data to the middleware according to the data requirement;

[0025] The business platform data is format-converted by the middleware, and the business platform data after format conversion is returned to the target application through the capability interface of the middleware.

[0026] Furthermore, in one embodiment of the present invention, the target application is developed by the following steps:

[0027] Determine a first data interface capability list of each of the target service platforms that the target application needs to call, and integrate the first data interface capability list to obtain a second data interface capability list;

[0028] Constructing the middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining the third data interface capability list of the middleware that has been developed, determining the fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities;

[0029] The target application is developed according to the middleware, so that the application business data generated by the target application is stored in the target application, and the business platform data that needs to be obtained is obtained by calling the capability interface of the middleware.

[0030] Furthermore, in one embodiment of the present invention, the target application is integrated into the target service platform through the following steps:

[0031] Determine a first data interface capability list of each of the target service platforms that the target application needs to call, and integrate the first data interface capability list to obtain a second data interface capability list;

[0032] Constructing the middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining the third data interface capability list of the middleware that has been developed, determining the fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities;

[0033] The target application already owned by the ecological partner is modified so that the target application is connected to the capability interface of the middleware according to the first data interface capability list, and then the modified target application is integrated into the target business platform.

[0034] Furthermore, in one embodiment of the present invention, the middleware-based service platform capability calling method further includes the following steps:

[0035] Determine a target data interface capability according to the second data interface capability list, where the target data interface capability is at least one data interface capability that does not exist on the target service platform;

[0036] Determining that a plurality of the target service platforms that do not have the target data interface capability are first service platforms;

[0037] The target data interface capability is newly added to the first service platform, or when the target application requests the first service platform to call the target data interface capability, the middleware provides default content for the target interface capability.

[0038] On the other hand, an embodiment of the present invention provides a middleware-based service platform capability calling device, comprising:

[0039] A user identification request module, used to send a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target service platform;

[0040] A user identification returning module, used to generate a user identification according to the current user information through the target service platform, and return the user identification to the middleware;

[0041] An association identifier generation module, used to associate the target application and the target service platform with the user identifier through the middleware to obtain a user association identifier, and return the user association identifier to the target application;

[0042] The data interface capability calling module is used to bind the user association identifier to the current session through the target application, and use the user association identifier to call the data interface capability of the target business platform to the middleware.

[0043] On the other hand, an embodiment of the present invention provides an electronic device, comprising a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein the program, when executed by the processor, realizes the middleware-based business platform capability calling method as described above.

[0044] On the other hand, an embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium used for computer-readable storage, and the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the middleware-based business platform capability calling method as described above.

[0045] The advantages and beneficial effects of the present invention will be partly given in the following description, partly become apparent from the following description, or be understood through the practice of the present invention:

[0046] The embodiment of the present invention sends a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target business platform, generates a user identification according to the current user information through the target business platform, and returns the user identification to the middleware, associates the target application and the target business platform with the user identification through the middleware to obtain the user association identification, and returns the user association identification to the target application, binds the user association identification to the current session through the target application, and uses the user association identification to call the data interface capability of the target business platform to the middleware. The embodiment of the present invention provides a middleware for enterprises with multiple digital business platforms, which unifies the data interface capabilities of different specifications provided by different business platforms and provides them to the application through the capability interface of the middleware, so that the application can obtain the business platform data through the capability interface provided by the middleware during research and development or integration, realizes the decoupling between the application and the business platform, avoids the need to repeatedly develop applications or repeatedly integrate applications under normal circumstances, reduces duplication of work, and improves the efficiency of application development and integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solution in the embodiments of the present invention, the following introduction is made to the drawings required for use in the embodiments of the present invention. It should be understood that the drawings introduced below are only for the convenience of clearly describing some embodiments of the technical solution of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0048] Figure 1 A step flow chart of a method for calling a service platform capability based on middleware provided in an embodiment of the present invention;

[0049] Figure 2 A schematic diagram of the architecture of the business platform layer, middleware and application layer provided for an embodiment of the present invention;

[0050] Figure 3 A step flow chart of step S101 provided in an embodiment of the present invention;

[0051] Figure 4 A step flow chart of step S104 provided in an embodiment of the present invention;

[0052] Figure 5 A flowchart of steps for application development provided by an embodiment of the present invention;

[0053] Figure 6 A flowchart of the steps of application integration provided by an embodiment of the present invention;

[0054] Figure 7Another step flow chart of the middleware-based service platform capability calling method provided in an embodiment of the present invention;

[0055] Figure 8 A schematic diagram of the structure of a middleware-based service platform capability invocation device provided in an embodiment of the present invention;

[0056] Fig. 9 A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention;

[0057] Fig.10 A schematic diagram of the structure of a storage medium provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0058] Embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limitations on the present application. It should be noted that, although the functional module division is performed in the system schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order from the module division in the system schematic diagram or the flow chart. For the step numbers in the following embodiments, they are only set for the convenience of explanation, and the order between the steps is not limited in any way. The execution order of each step in the embodiment can be adaptively adjusted according to the understanding of those skilled in the art.

[0059] In the description of the present invention, the meaning of "a plurality" is two or more. If there is a description of the first or the second, it is only for the purpose of distinguishing the technical features, and it cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those commonly understood by technicians in the technical field of this application. The terms used in this document are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0060] The middleware-based service platform capability calling method provided in the embodiment of the present invention can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a set-top box, etc.; the server side can be configured as an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the middleware-based service platform capability calling method, etc., but is not limited to the above forms.

[0061] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0062] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0063] The business platform and the application are usually not too coupled, but in order to improve the user experience, the business platform is usually required to provide information such as users, organization accounts, and organization members. The present invention aims to reduce the workload of repeated development or repeated integration by adding a middleware that connects the business platform and the application, one side of which is connected to the business platform, and different business platforms provide their own data capabilities, while the other side of the middleware provides a unified and standardized data interface for application integration or development. This middleware development method that supports single-time development or integration of applications to multiple business platforms can greatly reduce the workload of duplication and improve development or integration efficiency when an enterprise with multiple digital business platforms develops or integrates external applications while meeting the needs of multiple business platforms to access applications at the same time.

[0064] like Figure 1 FIG. 1 is a flow chart showing a method for calling a service platform capability based on middleware according to an embodiment of the present invention. Figure 1 The embodiment of the present invention provides a method for calling a service platform capability based on middleware, which specifically includes the following steps:

[0065] S101, sending a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target business platform;

[0066] S102, generating a user identifier according to current user information through the target business platform, and returning the user identifier to the middleware;

[0067] S103, associating the target application and the target business platform with the user identifier through the middleware to obtain the user association identifier, and returning the user association identifier to the target application;

[0068] S104: Bind the user association identifier to the current session through the target application, and use the user association identifier to call the data interface capability of the target business platform to the middleware.

[0069] The embodiments of the present invention are applicable to companies with multiple digital business platform business directions, such as the company with smart community and digital village business platform businesses. According to the ideas of the present invention, middleware (hereinafter referred to as middleware) that supports single application development or integration to multiple business platforms is developed to abstract and unify the data interfaces of multiple business platforms within the enterprise. For applications with the same needs, the application is developed independently of the business platform. During development, the application's own data is stored in the application itself, and the data related to the business platform is finally developed by calling the data capabilities provided by the middleware. The use conditions include the business platform, middleware and the application itself. The application can be reused on multiple business platforms, and the middleware and application only need to be developed or integrated once.

[0070] An embodiment of the present invention provides a middleware for an enterprise with multiple digital business platforms. The middleware unifies the data interface capabilities of different specifications provided by different business platforms and provides them to applications through the capability interface of the middleware. When the application is developed or integrated, the business platform data can be obtained through the capability interface provided by the middleware, thereby achieving decoupling between the application and the business platform, avoiding the need to repeatedly develop applications or repeatedly integrate applications under normal circumstances, reducing duplication of work, and improving the efficiency of application development and integration.

[0071] like Figure 2 FIG. 1 is a schematic diagram of the architecture of the business platform layer, middleware and application layer provided by an embodiment of the present invention, referring to FIG. Figure 2 As an optional implementation method, the target application is located at the application layer, the target business platform is located at the business platform layer, the business platform layer and the application layer are decoupled through middleware, the business platform layer is used to provide corresponding data interface capabilities according to different application scenarios, the middleware is used to abstract and unify the data interface capabilities of the business platform layer, form a unified external business interface capability, and provide business interface capabilities through the capability interface of the middleware, and the application layer is used to call the data interface capabilities of the business platform layer through the capability interface of the middleware.

[0072] Specifically, the present invention adds middleware that supports single application development or integration into multiple business platforms based on the internal business platform of the enterprise, such as Figure 2 As shown, the main architecture has the following three layers:

[0073] The bottom layer is the business platform layer, which provides data capabilities with different data structures according to different customers and different user scenarios;

[0074] The middle layer is the middleware layer, which abstracts and unifies the business interfaces to form a unified external business interface capability;

[0075] The top layer is the application layer. Regardless of whether the application is self-developed or introduced by the ecosystem, it is decoupled from the business platform. The application data is only stored in the application itself. When it comes to business platform data, it does not directly call the capabilities provided by the business platform, but calls the capabilities provided by the middleware.

[0076] like Figure 3 FIG. 1 is a flowchart of step S101 provided in an embodiment of the present invention, referring to FIG. Figure 3 As an optional implementation, the target application sends a user identification acquisition request to the middleware, so that the middleware forwards the user identification acquisition request to the target business platform, which specifically includes:

[0077] S1011, in response to the user's application entry operation on the target service platform, jumping from the target service platform to the target application;

[0078] S1012, identifying the business platform information carried in the jump request address through the target application, generating a user identification acquisition request according to the business platform information, and then sending the user identification acquisition request to the middleware;

[0079] S1013. The middleware identifies the service platform information carried in the user identification acquisition request, and forwards the user identification acquisition request to the target service platform according to the service platform information.

[0080] Specifically, in the business platform, enter the Web application that needs to be used; the Web application initiates a request to the middleware to obtain the current user by identifying the platform and module information carried in the request address; after the middleware identifies the platform, it converts it into the capability interface provided by the platform and initiates a request to the corresponding platform; after the corresponding platform receives the request to obtain the current user, it obtains the current user information, generates a unique identifier for the application where the current user is located, and returns it to the middleware; after the middleware obtains the user identifier, it integrates the user identifier, platform and application to generate a user association identifier that can be traced back to the user identifier, platform and application and has a validity period, and returns the user association identifier to the application; after the application obtains the user association identifier, it binds the user association identifier to the current session.

[0081] like Figure 4 FIG. 1 is a flowchart of step S104 provided in an embodiment of the present invention, referring to FIG. Figure 4 As an optional implementation, the user association identifier is used to call the data interface capability of the target business platform to the middleware, which specifically includes:

[0082] S1041. When the user needs to obtain business platform data during the operation of the target application, an interface capability call request is generated according to the data requirement and the user association identifier, and the interface capability call request is sent to the middleware;

[0083] S1042, identifying the data requirements and user association identifier carried in the interface capability call request through the middleware, determining the corresponding target business platform and user identifier according to the user association identifier, verifying the validity of the user identifier in the target application, and converting the capability interface of the middleware into the capability interface of the target business platform, and then forwarding the interface capability call request to the target business platform;

[0084] S1043, identifying the data requirements and user association identifier carried in the interface capability call request through the target business platform, determining the corresponding user identifier according to the user association identifier, verifying the validity of the user identifier in the middleware, and returning the business platform data to the middleware according to the data requirements;

[0085] S1044. Convert the format of the business platform data through the middleware, and return the format-converted business platform data to the target application through the capability interface of the middleware.

[0086] Specifically, when the function operated by the user needs to obtain business platform data, the application obtains the user association identifier and calls the capability interface provided by the middleware through the user identifier; after receiving the request, the middleware verifies the validity of the user identifier in the application, confirms the validity, traces back to the user's platform source and the user identifier of the user on the platform, converts the capability interface to the capability interface of the corresponding platform, and carries the user identifier; after receiving the request, the business platform verifies the validity of the user identifier in the middleware, and returns the data normally according to the business data capability; after the middleware obtains the returned data, it converts the data format according to the capability interface provided to the outside and returns it to the application; after the application obtains the business platform data, it performs normal logical processing.

[0087] like Figure 5 FIG. 1 is a flowchart of a step of application development provided by an embodiment of the present invention, referring to FIG. Figure 5 As an optional implementation, the target application is developed by the following steps:

[0088] S201, determining a first data interface capability list of each target business platform that the target application needs to call, and integrating the first data interface capability list to obtain a second data interface capability list;

[0089] S202, constructing middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining a third data interface capability list of the developed middleware, determining a fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities;

[0090] S203: Develop a target application according to the middleware, so that the application business data generated by the target application is stored in the target application, and the business platform data that needs to be obtained is obtained by calling the capability interface of the middleware.

[0091] like Figure 6 FIG. 1 is a flowchart of a step of application integration provided by an embodiment of the present invention, referring to FIG. Figure 6 As an optional implementation, the target application is integrated into the target business platform through the following steps:

[0092] S301, determining a first data interface capability list of each target business platform that the target application needs to call, and integrating the first data interface capability list to obtain a second data interface capability list;

[0093] S302, constructing middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining a third data interface capability list of the developed middleware, determining a fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities;

[0094] S303: Transform the existing target application of the ecological partner so that the target application is connected to the capability interface of the middleware according to the first data interface capability list, and then integrate the transformed target application into the target business platform.

[0095] The process of application development and application integration is described below in conjunction with a specific embodiment.

[0096] There are business platform A and business platform B in a certain enterprise. Due to business development, business platform A and business platform B need to provide customers with two applications, application 1 and application 2. After the enterprise decision, it is decided to implement application 1 through self-research and application 2 through ecosystem introduction. The specific process is as follows:

[0097] 1) Analyze and sort out the data interface capability lists a that application 1 and application 2 need to call on business platform A and business platform B respectively;

[0098] 2) Connect the data interface capabilities of business platform A and business platform B to form a unified data interface capability list b.

[0099] 3) For the unified data interface capability list b, if the middleware has not been developed, then develop middleware that supports single application development or integration into multiple business platforms;

[0100] 4) If the development of the middleware has been completed, compare the interface capability list provided by the middleware to confirm the capability interface list c that needs to be added to the middleware;

[0101] 5) For the capability interface list c that needs to be added, abstract and unify the data of the interfaces provided by business platform A and business platform B so that the returned data fields have the same or similar meanings. Develop capability interface list c on the middleware according to the abstracted and unified structure. Capability interface list c and the interface capability list already provided mentioned in 4) form interface list b;

[0102] 6) During the development of application 1, the data of application 1 and middleware are clearly divided. The application business data generated by the application is stored in the application, and the operation involving the business platform data calls the capability interface provided by the middleware. The application that is finally developed can be directly used on business platform A or business platform B;

[0103] 7) When application 2 is introduced through the ecosystem, it needs to be transformed by the ecosystem partner. During the transformation, application 2 is connected to the capability interface provided by the middleware. After the transformation is completed, application 2 can be directly used in business platform A or B.

[0104] The embodiment of the present invention reduces the one-time development of application 1 on business platform A and business platform B, and also reduces the one-time integration of application 2 on business platform A and business platform B. In addition, a series of capability exposure interfaces are accumulated and can be used for subsequent application development or integration.

[0105] like Figure 7 FIG. 1 is another flow chart of the middleware-based service platform capability calling method provided in an embodiment of the present invention. Figure 7 As an optional implementation, the middleware-based service platform capability calling method further includes the following steps:

[0106] S401, determining a target data interface capability according to a second data interface capability list, where the target data interface capability is a data interface capability that does not exist in at least one target service platform;

[0107] S402, determining that a plurality of target service platforms that do not have target data interface capabilities are first service platforms;

[0108] S403: Add a target data interface capability to the first service platform, or, when the target application requests the first service platform to call the target data interface capability, provide default content for the target interface capability through the middleware.

[0109] Specifically, after obtaining the second data interface capability list, if there is a data interface capability that does not exist in one of the business platforms, it is necessary to confirm whether the business platform adds the data interface capability when providing the capability to the application, or the middleware provides default content for the interface capability.

[0110] The above is an explanation of the method steps of the embodiment of the present invention. It can be recognized that the embodiment of the present invention provides a middleware for enterprises with multiple digital business platforms, which unifies the data interface capabilities of different specifications provided by different business platforms and provides them to applications through the capability interface of the middleware, so that when the application is developed or integrated, the business platform data can be obtained through the capability interface provided by the middleware, realizing the decoupling between the application and the business platform, avoiding the need to repeatedly develop applications or repeatedly integrate applications under normal circumstances, reducing duplication of work, and improving the efficiency of application development and integration.

[0111] Compared with the prior art, the embodiments of the present invention also have the following advantages:

[0112] 1. By adding middleware, the coupling between application development and business platform is reduced, thus greatly improving application development efficiency;

[0113] 2. Providing a unified and standardized capability interface through middleware reduces the dependence of ecological cooperation suppliers on the internal business platform of the enterprise, avoids multiple integration of ecological cooperation suppliers, and thus reduces integration costs;

[0114] 3. When introducing applications into the business platform, the interfaces are sorted out and unified to form a virtuous cycle of sustainable development. The middleware has a capability interface ledger for multiple business platforms. Since multiple business platforms provide capabilities at the same time, the phenomenon of isolated islands caused by inconsistent application docking processes when each business platform provides capabilities is avoided.

[0115] like Figure 8 FIG. 1 is a schematic diagram of a structure of a middleware-based service platform capability calling device according to an embodiment of the present invention. Figure 8 The embodiment of the present invention provides a service platform capability calling device based on middleware, comprising:

[0116] A user identification request module, used to send a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target business platform;

[0117] A user ID return module is used to generate a user ID according to the current user information through the target business platform and return the user ID to the middleware;

[0118] An association identifier generation module is used to associate the target application and the target business platform with the user identifier through the middleware, obtain the user association identifier, and return the user association identifier to the target application;

[0119] The data interface capability calling module is used to bind the user association identifier to the current session through the target application, and use the user association identifier to call the data interface capability of the target business platform to the middleware.

[0120] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0121] The embodiment of the present invention also provides an electronic device, the electronic device comprising: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, and the program is executed by the processor to realize the above-mentioned middleware-based service platform capability calling method. The electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.

[0122] like Fig. 9 FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention, referring to FIG. Fig. 9 , an embodiment of the present invention provides an electronic device, including:

[0123] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention;

[0124] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the middleware-based service platform capability calling method of the embodiment of the present invention;

[0125] Input / output interface 903, used to implement information input and output;

[0126] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0127] A bus 905 that transmits information between the various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0128] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0129] like Fig.10 FIG. 1 is a schematic diagram of a storage medium according to an embodiment of the present invention. Fig.10 The embodiment of the present invention also provides a storage medium, which is a computer-readable storage medium used for computer-readable storage. The storage medium stores one or more programs 1001, and the one or more programs 1001 can be executed by one or more processors to implement the above-mentioned middleware-based business platform capability calling method.

[0130] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0131] The embodiment of the present invention also discloses a computer program product or a computer program, wherein the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes Figure 1 The method shown.

[0132] In some selectable embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the above-mentioned boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided by way of example, for the purpose of providing a more comprehensive understanding of technology. The disclosed method is not limited to the operation and logic flow presented herein. Selectable embodiments are expected, wherein the order of various operations is changed and the sub-operation of a part for which is described as a larger operation is performed independently.

[0133] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise specified to the contrary, one or more of the above-mentioned functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the present invention. More specifically, in view of the properties, functions and internal relationships of the various functional modules in the device disclosed herein, the actual implementation of the module will be understood within the conventional skills of the engineer. Therefore, those skilled in the art can implement the present invention set forth in the claims without excessive experimentation using ordinary techniques. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0134] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the above methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0135] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in conjunction with such instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in conjunction with such instruction execution systems, devices or apparatuses.

[0136] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the above-mentioned program is printed, since the above-mentioned program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or processing in other suitable ways as necessary, and then stored in a computer memory.

[0137] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0138] In the above description of this specification, the description with reference to the terms "one embodiment / example", "another embodiment / example" or "certain embodiments / examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0139] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

[0140] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art may make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A method for calling business platform capabilities based on middleware, characterized in that: The following steps are involved: Sending a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target service platform; Generate a user ID according to the current user information through the target service platform, and return the user ID to the middleware; Associating the target application and the target service platform with the user identifier through the middleware to obtain a user association identifier, and returning the user association identifier to the target application; The user association identifier is bound to the current session through the target application, and the user association identifier is used to call the data interface capability of the target service platform to the middleware.

2. A method for calling business platform capabilities based on middleware according to claim 1, characterized in that: The target application is located at the application layer, and the target business platform is located at the business platform layer. The business platform layer and the application layer are decoupled through the middleware. The business platform layer is used to provide corresponding data interface capabilities according to different application scenarios. The middleware is used to abstract and unify the data interface capabilities of the business platform layer to form a unified external business interface capability, and provide the business interface capability through the capability interface of the middleware. The application layer is used to call the data interface capabilities of the business platform layer through the capability interface of the middleware.

3. A method for calling business platform capabilities based on middleware according to claim 1, characterized in that: The step of sending a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target service platform, specifically includes: In response to a user entering an application on the target service platform, jumping from the target service platform to the target application; identifying the service platform information carried in the jump request address through the target application, generating a user identification acquisition request according to the service platform information, and then sending the user identification acquisition request to the middleware; The service platform information carried in the user identification acquisition request is identified by the middleware, and the user identification acquisition request is forwarded to the target service platform according to the service platform information.

4. The method for calling business platform capabilities based on middleware according to claim 1, characterized in that: The step of using the user association identifier to call the data interface capability of the target business platform to the middleware specifically includes: When the user needs to obtain business platform data during the operation of the target application, an interface capability call request is generated according to the data requirement and the user association identifier, and the interface capability call request is sent to the middleware; The middleware identifies the data requirement and the user association identifier carried in the interface capability call request, determines the corresponding target business platform and the user identifier according to the user association identifier, verifies the validity of the user identifier in the target application, and converts the capability interface of the middleware into the capability interface of the target business platform, and then forwards the interface capability call request to the target business platform; Identify the data requirement and the user association identifier carried in the interface capability call request through the target business platform, determine the corresponding user identifier according to the user association identifier, verify the validity of the user identifier in the middleware, and return the business platform data to the middleware according to the data requirement; The business platform data is format-converted by the middleware, and the business platform data after format conversion is returned to the target application through the capability interface of the middleware.

5. The method for calling business platform capabilities based on middleware according to claim 1, characterized in that: The target application is developed by the following steps: Determine a first data interface capability list of each of the target service platforms that the target application needs to call, and integrate the first data interface capability list to obtain a second data interface capability list; Constructing the middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining the third data interface capability list of the middleware that has been developed, determining the fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities; The target application is developed according to the middleware, so that the application business data generated by the target application is stored in the target application, and the business platform data that needs to be obtained is obtained by calling the capability interface of the middleware.

6. The method for calling the service platform capability based on middleware according to claim 1, characterized in that: The target application is integrated into the target service platform through the following steps: Determine a first data interface capability list of each of the target service platforms that the target application needs to call, and integrate the first data interface capability list to obtain a second data interface capability list; Constructing the middleware according to the data interface capability list so that the middleware provides corresponding data interface capabilities through the capability interface, or obtaining the third data interface capability list of the middleware that has been developed, determining the fourth data interface capability list that needs to be added to the middleware according to the second data interface capability list and the third data interface capability list, and adding a capability interface to the middleware according to the fourth data interface capability list to provide corresponding data interface capabilities; The target application already owned by the ecological partner is modified so that the target application is connected to the capability interface of the middleware according to the first data interface capability list, and then the modified target application is integrated into the target business platform.

7. A method for calling business platform capabilities based on middleware according to claim 5 or 6, characterized in that: The middleware-based service platform capability calling method further comprises the following steps: Determine a target data interface capability according to the second data interface capability list, where the target data interface capability is at least one data interface capability that does not exist on the target service platform; Determining that a plurality of the target service platforms that do not have the target data interface capability are first service platforms; The target data interface capability is newly added to the first service platform, or when the target application requests the first service platform to call the target data interface capability, the middleware provides default content for the target interface capability.

8. A service platform capability calling device based on middleware, characterized in that: include: A user identification request module, used to send a user identification acquisition request to the middleware through the target application, so that the middleware forwards the user identification acquisition request to the target service platform; A user identification returning module, used to generate a user identification according to the current user information through the target service platform, and return the user identification to the middleware; An association identifier generation module, used to associate the target application and the target service platform with the user identifier through the middleware to obtain a user association identifier, and return the user association identifier to the target application; The data interface capability calling module is used to bind the user association identifier to the current session through the target application, and use the user association identifier to call the data interface capability of the target business platform to the middleware.

9. An electronic device, characterized in that: The electronic device includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the middleware-based business platform capability calling method as described in any one of claims 1 to 7 are realized.

10. A storage medium, the storage medium being a computer-readable storage medium, used for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the middleware-based service platform capability calling method as described in any one of claims 1 to 7.

Images