CN111934940B

CN111934940B - Configurated service request method and device, electronic equipment and storage medium

Info

Publication number: CN111934940B
Application number: CN202011019130.1A
Authority: CN
Inventors: 陈卓成
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-09-24
Filing date: 2020-09-24
Publication date: 2021-01-15
Anticipated expiration: 2040-09-24
Also published as: CN111934940A

Abstract

The embodiment of the disclosure provides a configured service request method and related equipment. The method comprises the following steps: acquiring target structured data, wherein the target structured data comprises a target configuration name and a target input parameter; generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name; sending the target request packet to a target service module through a target service interface; receiving a target return packet of a target service module response target request packet from a target service interface; analyzing the target return packet to obtain target result data; and returning the target result data. According to the technical scheme of the embodiment of the disclosure, only simple target structured data needs to be constructed, the target request packet adapted to the target service interface of the target service module can be automatically generated, the target return packet returned by the target service module is automatically analyzed, and the required target result data is read from the data stored in the target service module.

Description

Configurated service request method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer and communication technologies, and in particular, to a configured service request method and apparatus, an electronic device, and a computer-readable storage medium.

Background

With the development of information technology, in a large network, a plurality of internal general systems (such as an auditing system, a data system and the like) often exist, and each internal general system often needs to interface various business modules.

In the related art, an internal general system obtains required target service data from a target service module which is in butt joint with the internal general system and initiates target operation to the target service module so as to obtain a realization process that the target service module executes the target operation and returns a target operation result, and the realization process is relatively complicated, repeated and inefficient.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure.

Disclosure of Invention

The embodiment of the disclosure provides a configured service request method and device, an electronic device and a computer readable storage medium, which can solve the technical problems of complex, repeated and inefficient data acquisition in the related art.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

The embodiment of the disclosure provides a configured service request method, which includes: acquiring target structured data, wherein the target structured data comprises a target configuration name and a target input parameter; generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name; sending the target request packet to the target service module through the target service interface; receiving a target return packet of the target service module responding to the target request packet from the target service interface; analyzing the target return packet to obtain target result data; and sending the target result data.

The embodiment of the disclosure provides a configured service request method, which includes: determining a target configuration name; obtaining target input parameters; generating target structured data according to the target configuration name and the target input parameters; sending the target structured data; and receiving target result data returned in response to the target structured data.

The disclosed embodiment provides a configured service request device, which comprises: the system comprises a structured data acquisition unit, a data processing unit and a data processing unit, wherein the structured data acquisition unit is used for acquiring target structured data which comprises a target configuration name and a target input parameter; a target request packet generating unit, configured to generate a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name; a target request packet sending unit, configured to send the target request packet to the target service module through the target service interface; a target packet return receiving unit, configured to receive, from the target service interface, a target packet return of the target service module in response to the target request packet; a target result data obtaining unit, configured to analyze the target repackage to obtain target result data; and the target result data returning unit is used for sending the target result data.

In some exemplary embodiments of the present disclosure, the apparatus further comprises: a module interface determining unit, configured to determine the target service module and a target service interface thereof; a configuration name data name configuration unit, configured to configure a target configuration name corresponding to the target service interface and a target data name corresponding to the target result data; a module name interface name setting unit, configured to set a target module name of the target service module and a target interface name of the target service interface; a request assembly logic setting unit, configured to set a target request assembly logic of a target request packet of the target service interface, where the target request assembly logic includes a target fixed parameter and the target input parameter; and the return packet extraction logic setting unit is used for setting the target return packet extraction logic of the target return packet of the target service interface.

In some exemplary embodiments of the present disclosure, the apparatus further comprises at least one of a routing mode setting unit, a request timeout time setting unit, and a processing plug-in setting unit. The routing mode setting unit is used for setting the routing mode of the target request packet. The request timeout time setting unit is used for setting the request timeout time of the target request packet. And the processing plug-in setting unit is used for setting the processing plug-in of the target request packet.

In some exemplary embodiments of the present disclosure, the target request packet generating unit includes: a configuration information obtaining unit, configured to obtain target configuration information according to the target configuration name, where the target configuration information includes a target interface name of the target service interface and a target request assembly logic of the target request packet; a service protocol obtaining unit, configured to obtain a target service protocol of the target service module; a first service protocol object generating unit, configured to generate a first target service protocol object according to the target interface name and a target service protocol of the target service module; and the request packet generating unit is used for generating the target request packet by utilizing the first target service protocol object according to the target request assembly logic and the target input parameters.

In some exemplary embodiments of the present disclosure, the target traffic interface employs a remote invocation framework that supports a reflection mechanism. Wherein, the service agreement obtaining unit includes: a service protocol reading unit, configured to read a target service protocol of the target service module from a first target cache if the target service protocol of the target service module exists in the first target cache; a reflection obtaining service protocol unit, configured to, if a target service protocol of the target service module does not exist in the first target cache, obtain the target service protocol of the target service module by using a reflection mechanism of the remote invocation framework; and the service protocol cache unit is used for storing the target service protocol of the target service module to the first target cache.

In some exemplary embodiments of the present disclosure, the target service protocol of the target service module includes a target service protocol of each service interface in the target service module, and each service interface of the target service module includes the target service interface. The first service protocol object generating unit comprises a first target service protocol object unit. The first target service protocol object unit is configured to generate the first target service protocol object required by the target request packet by using a reflection mechanism of a target service protocol of the target service interface corresponding to the target interface name.

In some exemplary embodiments of the present disclosure, the request packet generating unit includes: an input parameter assembly unit for assembling the target input parameters into the target request assembly logic; a fixed parameter obtaining unit, configured to obtain a target fixed parameter in the target request assembly logic; a request assembly logic conversion unit for converting the target request assembly logic including the target fixed parameters and the target input parameters into the target request packet of a binary stream using the first target service protocol object.

In some exemplary embodiments of the present disclosure, the target configuration information further includes a target module name of the target service module. Wherein, the target request packet sending unit includes: a request address obtaining unit, configured to obtain a target request address of the target service module according to the name of the target module; and the initiating and calling unit is used for calling the target request address and sending the target request packet of the binary stream to the target service interface.

In some exemplary embodiments of the present disclosure, the request address obtaining unit includes: a request address reading unit, configured to, if a target request address of the target service module exists in a second target cache, read the target request address from the second target cache according to the name of the target module; a route obtaining request address unit, configured to, if a target request address of the target service module does not exist in the second target cache, obtain the target request address by using a route implementation service discovery according to the name of the target module; and the request address cache unit is used for storing the target module name and the target request address to the second target cache in an associated manner.

In some exemplary embodiments of the present disclosure, the target configuration information further comprises target loopback extraction logic. Wherein the target result data obtaining unit includes: a second service protocol object generating unit, configured to parse the target loopback packet of the binary stream into a second target service protocol object according to a reflection mechanism of a target service protocol of the target service module; a result data extraction unit, configured to extract the target result data from the second target service agreement object by using the target loopback extraction logic.

The disclosed embodiment provides a configured service request device, which comprises: a target configuration name determining unit for determining a target configuration name; a target input parameter obtaining unit for obtaining a target input parameter; the structured data generating unit is used for generating target structured data according to the target configuration name and the target input parameters; the structured data sending unit is used for sending the target structured data; and the target result data receiving unit is used for receiving the target result data returned in response to the target structured data.

The disclosed embodiments provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a configured service request method as described in the above embodiments.

An embodiment of the present disclosure provides an electronic device, including: at least one processor; a storage device configured to store at least one program that, when executed by the at least one processor, causes the at least one processor to implement the configured service request method as described in the above embodiments.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations described above.

In the technical solutions provided in some embodiments of the present disclosure, on one hand, when the required target result data needs to be acquired from the target service interface of the target service module, only a section of target structured data with a simple structure needs to be acquired, so that the target request packet adapted to the target service interface of the target service module can be automatically generated according to the target input parameter and the target configuration name in the target structured data, and then the target request packet is sent to the target service module through the target service interface; on the other hand, when a target loopback packet of the target service module responding to the target request packet is received from the target service interface, the target loopback packet can be automatically analyzed to obtain the required target result data. When new target result data needs to be acquired, the required target result data can be quickly and simply acquired without recompiling and re-uploading the service code, the fixed parameters of the target service interface of the target service module do not need to be repeatedly compiled, the efficiency of acquiring the required target result data from the target service module is improved, the access and the use of any target service interface can be quickly and simply realized, and the implementation process and the iteration cost are greatly reduced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty. In the drawings:

fig. 1 shows a schematic diagram of an exemplary system architecture to which a configured service request method or a configured service request apparatus of an embodiment of the present disclosure may be applied.

Fig. 2 is a flowchart illustrating an operation required for acquiring a service data application in the related art.

Fig. 3 is a diagram illustrating a call link for acquiring service data in the related art.

FIG. 4 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure.

Fig. 5 schematically illustrates a configuration diagram of target configuration information corresponding to a target configuration name according to an embodiment of the present disclosure.

Fig. 6 schematically shows a configuration diagram of target configuration information corresponding to a target configuration name according to an embodiment of the present disclosure.

FIG. 7 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure.

Fig. 8 schematically shows a flowchart of operations required for acquiring a service data application according to an embodiment of the present disclosure.

Fig. 9 schematically shows a call link diagram for obtaining service data according to an embodiment of the present disclosure.

FIG. 10 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure.

Fig. 11 schematically illustrates a block diagram of a configured service request device according to an embodiment of the disclosure.

Fig. 12 schematically illustrates a block diagram of a configured service request device according to an embodiment of the disclosure.

Fig. 13 schematically shows a structural schematic diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.

The described features, structures, or characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.

The drawings are merely schematic illustrations of the present disclosure, in which the same reference numerals denote the same or similar parts, and thus, a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in at least one hardware module or integrated circuit, or in different networks and/or processor means and/or microcontroller means.

In this specification, the terms "a", "an", "the", "said" and "at least one" are used to indicate the presence of at least one element/component/etc.; the terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements/components/etc. other than the listed elements/components/etc.; the terms "first," "second," and "third," etc. are used merely as labels, and are not limiting on the number of their objects.

The following detailed description of exemplary embodiments of the disclosure refers to the accompanying drawings.

Fig. 1 shows a schematic diagram of an exemplary system architecture of a configured service request method or a configured service request device, which can be applied to embodiments of the present disclosure.

As shown in fig. 1, the system architecture may include

terminal devices

101, 103 and a server 102. A medium providing a communication link may be made between the

terminal apparatuses

101, 103 and the server 102 through a network. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The server 102 may be an independent server, a server cluster or a distributed system formed by a plurality of servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, middleware service, a domain name service, a security service, a CDN (Content Delivery Network), a big data and artificial intelligence platform, and the like.

The

terminal devices

101 and 103 may be, but are not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a wearable smart device, a virtual reality device, an augmented reality device, and the like.

In the embodiment of the present disclosure, the

terminal devices

101 and 103 may be installed with various applications such as a game application, an instant messaging application, and a news application. For example, a user a may open a user interface of an internal general system, such as an auditing system or a data system, in an instant messaging application installed on the terminal device 101 (belonging to an instant messaging platform), and when the user a needs to use a certain item mark service data stored on the server 102 or the terminal device 103 by a target service module, or the user a needs to initiate a target operation to a target service interface of the target service module located on the server 102 or the terminal device 103, the user a may input a piece of target structured data in the user interface, where the target structured data includes a target configuration name and a target input parameter; the target structured data may then be sent by the terminal device 101 to a generic data module located on the terminal device 101 or on the server 102 or on the terminal device 103. When the generic data module receives the target structured data sent by the terminal device 101, it can automatically generate a target request packet adapted to the target service interface of the target service module according to the target configuration name and the target input parameter in the target structured data, and send the target request packet to the target service module through the target service interface. And after receiving the target request packet, the target service module generates a target return packet responding to the target request packet and returns the target return packet to the general data module. Then, the generic data module automatically parses the target loopback packet to obtain target result data, and returns the target result data to the terminal device 101, so that the target result data can be displayed on the display screen of the terminal device 101.

It should be understood that the number of terminal devices and servers in fig. 1 is merely illustrative, and that any number of terminal devices and servers may be present, as desired.

It should be noted that the above application scenarios are merely illustrated for the convenience of understanding the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

The following is an example of an instant messaging platform, but the disclosure is not limited thereto. A plurality of internal general systems exist in the instant messaging platform, such as an auditing system, a data system and the like. The auditing system may be configured to audit whether the data uploaded by the user of the instant messaging platform or various functions to be online meet system specifications of the instant messaging platform, for example, whether the functions meet legal compliance. The data system can be used for collecting relevant data of each business module in the instant communication platform.

Each internal general system generally needs to interface various service modules, and acquire required target service data from the interfaced target service modules or initiate target operation on the target service modules.

As shown in fig. 1, taking the example of acquiring any service data, an application (client) of an internal general system that wants to acquire the service data needs to perform the following operations:

firstly, adding a calling code in the service code of the internal general system, wherein the calling code generally adopts a C + + language to describe the docking logic of the target service interface of the docked target service module. Taking the name of the target module of the target service module as "xxx" as an example, the added calling code is as follows:

#include “xxxclient.h”

xxxReq oReq// oReq for setting parameters of traffic module xxx

xxxResp oResp// oResp as the service data returned after initiating the call of service module xxx

setParam1(val 1)// setting the fixed parameter Param1 to the value val1

Setparam2 (0)// setting the value of the input parameter Param2 to 0

Setparam3 (1)// setting the value of the input parameter Param3 to 1

xxxClient (). callxxx (oReq, oResp)// the application initiating the operation of calling the target business module

auto res = oResp.res1(), application end acquires the service data

After the calling code is added to the service code, a compilation dependency is added, for example:

dep:[

//mmbiz/xxx:xxx

client

]

and after the compiling dependence is added, compiling the online.

After compiling is carried out on line, the service data can be obtained on line.

Referring to the call link of fig. 2 again, in the related art, when the application terminal initiates the call, the application terminal needs to adapt to the target service interface of the target service module to be currently docked. Since the service protocols adopted by the service modules are various, and the service protocols adopted by different service interfaces of each service module are also various, the application end needs to perform a complex logic structure in order to be capable of adapting to the service module xxx, so that a complete target request packet for adapting to the target service interface of the service module xxx can be generated.

When the application receives a return packet returned in response to the target request packet from the service module xxx, it needs to extract the required service data according to the service return packet protocol corresponding to the target service interface.

As can be seen from fig. 1 and fig. 2, in the related art, in the implementation process of acquiring required service data from various service modules in a butt joint and initiating various operations to the various service modules, on one hand, a relatively complex programming language such as C + + is required to describe the butt joint logic of the various service modules, the logic expression threshold is high, and the implementation can be performed only by programming a developer who knows C + + programming, which has a high requirement for a wide range of users at an application end and is not suitable for large-scale popularization; on the other hand, when the service data needs to be acquired and the operation needs to be initiated, the calling code needs to be repeatedly coded, and long recompilation and online are performed, so that the implementation and modification costs are high, the implementation is complicated, and the efficiency is low.

In addition, as the functions of a plurality of service interfaces are general, a plurality of fixed parameters and filling parameters are set. Wherein fixed parameters means that the values of these parameters are fixed. The padding parameters mean that the parameters are only used in some specific service scenarios. In the related art, complex fixed parameters and filling parameters are exposed to a calling end (an application end for calling a butted service module), so that the use is not intuitive and the operation is complicated.

For example, interface parameters for the rename record include: account number, modified scene, number of pieces pulled, bias, whether a time range is needed, etc. This is designed to flexibly adapt to various acquisition record requirements. However, when the application terminal wants to obtain the service data, which is the "last renaming record", the application terminal needs to fill in fixed parameters and optional parameters, for example, in addition to the account number, every time the application terminal needs to fill in the account number (modified scene = all scenes, number of pulled pieces =1, offset =0, and no time range is needed).

The configured service request method provided by the embodiment of the disclosure is used for solving at least one technical problem in the related art. The method provided by the embodiment of the present disclosure may be executed by any electronic device, for example, the terminal device and/or the server in fig. 1 described above, which is not limited by the present disclosure.

FIG. 4 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure. The method provided in the embodiment of fig. 4 is exemplified by taking the terminal device or the server in fig. 1 as an example to execute the method, and a general data module for executing the method in the embodiment of fig. 4 may be disposed in the terminal device or the server, but the disclosure is not limited thereto. As shown in fig. 4, the method provided by the embodiment of the present disclosure may include the following steps.

In step S410, target structured data is obtained, which includes a target configuration name and target input parameters.

In the embodiment of the present disclosure, taking an example that any application terminal wants to obtain target result data, the general data module may obtain the target structured data from the corresponding application terminal. The target configuration name in the target structured data represents a unique item of business data (called target business data) or represents a unique item of operation (called target operation). The target input parameters represent parameters that need to be input in order to obtain the desired target result data.

The structured data is also called line data, is data logically expressed and realized by a two-dimensional table structure, strictly complies with data format and length specification, and is unstructured data comprising office documents, various reports, pictures, audio and video information and the like, which are opposite to the structured data.

For example, the target structured data may be as follows:

xxx/target configuration name of corresponding target service module xxx

req:{

param1: val1}// target input parameter is param1, and the value is val1

In an exemplary embodiment, the method may further include: determining the target service module and a target service interface thereof; configuring a target configuration name corresponding to the target service interface and a target data name corresponding to the target result data; setting a target module name of the target service module and a target interface name of the target service interface; setting a target request assembly logic of a target request packet of the target service interface, wherein the target request assembly logic comprises a target fixed parameter and the target input parameter; and setting target return packet extraction logic of the target return packet of the target service interface.

In this disclosure, before the universal data module receives the target structured data, it may pre-configure what the target service module and the target service interface thereof correspond to the target configuration name, set a target module name of the target service module and a target interface name of the target service interface, and configure the target configuration name corresponding to the target service interface and a target data name corresponding to the target result data to be extracted. Target request assembly logic for how to assemble the target request packet for the target service interface and target loopback extraction logic for how to extract target result data from the target loopback packet can also be configured.

The target data name may be in a text format, for example, the target configuration name may be in a character string format, for example, a combination of an english alphabet and some symbols, the target configuration name in the character string format is not easy to remember for a user at the application end, and by setting the corresponding target data name, the user may input the corresponding target data name in a user interface at the application end, that is, the target configuration name corresponding to the target data name may be searched.

In an exemplary embodiment, the method may further comprise at least one of: setting a routing mode of the target request packet; setting the request timeout time of the target request packet; and setting a processing plug-in of the target request packet.

In the embodiment of the present disclosure, in addition to the above configuration, some additional configurations may be performed, that is, some padding parameters are configured, for example, a routing mode is set, and it is determined by the routing mode whether to route the target request packet to a certain specified server of the target service module or to route the target request packet to all servers of the target service module, or in a test phase, the target request packet is routed to a server of the target service module for testing. For another example, a request timeout time of the target request packet may also be set, and when it is detected that the request time of the target request packet is greater than the set request timeout time, the corresponding target request packet may be discarded. For another example, a processing plug-in for the destination request packet may also be set.

The plug-in is a program written by an application program interface which follows a certain specification. By calling a processing plug-in, a specific processing function can be realized. For example, if some application terminals need to record the implementation process of obtaining the target result data, a recording plug-in may be called, and the corresponding recording function may be implemented by directly calling the recording plug-in without repeatedly writing the code of the recording function.

The configured target service module and its target service interface, target configuration name, target data name, target module name, target interface name, target request assembly logic, target loopback extraction logic and additional configuration can all be used as target configuration information of the target configuration name. The specific configuration process may be described with reference to fig. 5 and 6 below, for example.

In step S420, a target request packet adapted to the target service interface of the target service module is generated according to the target input parameter and the target configuration name.

In an exemplary embodiment, generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name may include: obtaining target configuration information according to the target configuration name, wherein the target configuration information comprises a target interface name of the target service interface and target request assembly logic of the target request packet; obtaining a target service protocol of the target service module; generating a first target service protocol object according to the target interface name and a target service protocol of the target service module; and generating the target request packet by utilizing the first target service protocol object and according to the target request assembly logic and the target input parameters.

In an exemplary embodiment, the target traffic interface may employ a remote invocation framework that supports a reflection mechanism. The obtaining of the target service agreement of the target service module may include: if the target service protocol of the target service module exists in the first target cache, reading the target service protocol of the target service module from the first target cache; if the target service protocol of the target service module does not exist in the first target cache, acquiring the target service protocol of the target service module by using a reflection mechanism of the remote call frame; and storing the target service protocol of the target service module to the first target cache.

In the embodiment of the present disclosure, for example, an svrkit may be adopted as the Remote Procedure Call (RPC) framework supporting the reflection mechanism, for example, it is assumed that a service framework such as an svrkit is adopted in a background of an instant messaging platform, a target service interface is an svrkit interface, and a target request packet initiated by the svrkit interface may be referred to as an svrkit request.

The svrkit is a framework, uniformly encapsulates functions of code generation, communication mode, log, reporting, overload and the like, and enables developers to write a small amount of codes, so that a stable distributed service can be realized. The terminal equipment sends an svrkit request to the target service interface, and the target service interface responds to a target return packet returned by the svrkit request, which is a process for providing service.

In the embodiment of the present disclosure, the target service protocol may adopt Protobuf. The Protobuf is a protocol of a serialized data structure which is platform-independent, language-independent, extensible, portable and efficient, and can be used for network communication and data storage. In the embodiment of the disclosure, the data transmission protocol uniformly used by the svrkit service includes Protobuf.

Therein, reflection refers to a class of applications that are capable of self-describing and self-controlling. That is, such applications implement self-representation and monitoring (interaction) of their own behavior by using some mechanism, and can adjust or modify the state and related semantics of the behavior described by the application according to the state and result of their own behavior.

In the disclosed embodiment, both Protobuf and svrkit support the reflex mechanism.

It should be noted that, although the embodiments of the present disclosure are all exemplified by svrkit + Protobuf, the present disclosure is not limited thereto, and any other remote invocation framework and service protocol capable of supporting the reflection mechanism may be adopted.

In an exemplary embodiment, the target service protocol of the target service module may include a target service protocol of each service interface in the target service module, and each service interface of the target service module includes the target service interface. Generating a first target service agreement object according to the target interface name and the target service agreement may include: and generating the first target service protocol object required by the target request packet by using a reflection mechanism of a target service protocol of the target service interface corresponding to the target interface name.

In the embodiment of the present disclosure, each target service module may include at least one service interface, and the at least one service interface includes a target service interface. The Protobuf is a complete set of service protocols, and therefore, target service protocols of target service modules adopting the Protobuf service protocols may also be different. The target service protocol of the respective target service interface of each target service module may also be different.

In an exemplary embodiment, generating the target request packet using the first target service agreement object and according to the target request assembly logic and the target input parameters may include: assembling the target input parameters into the target request assembly logic; obtaining a target fixed parameter in the target request assembly logic; converting the target request assembly logic including the target fixed parameters and the target input parameters into the target request packet of a binary stream using the first target service protocol object.

In step S430, the target request packet is sent to the target service module through the target service interface.

In an exemplary embodiment, the target configuration information may further include a target module name of the target service module. The sending the target request packet to the target service module through the target service interface may include: obtaining a target request address of the target service module according to the name of the target module; and calling the target request address, and sending the target request packet of the binary stream to the target service interface.

In an exemplary embodiment, obtaining the target request address of the target service module according to the name of the target module may include: if the target request address of the target service module exists in a second target cache, reading the target request address from the second target cache according to the name of the target module; if the target request address of the target service module does not exist in the second target cache, utilizing a route to realize service discovery according to the name of the target module, and acquiring the target request address; and storing the target module name and the target request address to the second target cache in an associated manner.

In step S440, a target loopback packet of the target service module responding to the target request packet is received from the target service interface.

When the target service module receives the target request packet, the target service module responds to the target request packet to generate a target loopback packet, and the target loopback packet comprises target result data. And then sends the target return packet to the universal data module through the target service interface.

In step S450, the target loopback packet is analyzed to obtain target result data.

In an exemplary embodiment, the target configuration information may further include target loopback extraction logic. Analyzing the target return packet to obtain target result data may include: analyzing the target return packet of the binary stream into a second target service protocol object according to a reflection mechanism of a target service protocol of the target service module; and extracting the target result data from the second target service protocol object by using the target loopback packet extraction logic.

The target loopback packet extraction logic is a logic for extracting required target result data from the target loopback packet.

Specifically, the process of the generic data module automatically generating a target request packet adapted to the target service interface of the target service module and sending the target request packet to the target service interface to obtain the target result data may include the following steps:

firstly, according to a target configuration name in target structured data sent by an application terminal, acquiring complete target configuration information required by a target service interface of a target service module.

The target configuration information represents information required for initiating a target request packet to a target service interface of a target service module, such as a target configuration name, a target service module and a target module name thereof, a target service interface and a target interface name thereof, a target data name, target request assembly logic, target return packet extraction logic, and the like.

And secondly, according to the target module name in the target configuration information, service discovery is realized by utilizing, for example, an instant messaging platform to unify routing, and a target request address of a target service module is obtained.

In the embodiment of the present disclosure, the target request address may include, for example, an IP (Internet Protocol) address and a port number of the target service module. Because the services provided by the target business module are typically distributed across multiple machines (e.g., servers), routing-related logic is required to find a server that can handle the corresponding target request packet.

Since the service discovery is realized through the uniform routing to obtain the target request address of the target service module, a large performance consumption is caused. In order to optimize the performance consumption, when the target request address is acquired for the first time, the target request address may be acquired by implementing service discovery through a uniform route, and then the target request address may be cached in the first target cache in association with the target module name. Therefore, when the target request address needs to be acquired next time, only the target module name needs to be directly read from the first target cache, so that the performance consumption is reduced, and the acquisition speed is increased.

And thirdly, acquiring a Protobuf service protocol (namely a target service protocol) of the target service module by using a reflection mechanism of the svrkit. The Protobuf service protocol may include field names, field types, and the like.

The method for acquiring the Protobuf service protocol of the target business module by using the reflection mechanism of the svrkit can cause larger performance consumption. In order to optimize the performance consumption, when the Protobuf service protocol of the target service module is obtained through the reflection mechanism of the svrkit for the first time, the Protobuf service protocol of the target service module and the name of the target module may be cached in a second target cache in an associated manner. Therefore, when the Protobuf service protocol of the target service module needs to be acquired next time, only the Protobuf service protocol needs to be directly read from the second target cache according to the name of the target module, so that the performance consumption is reduced, and the acquisition speed is accelerated.

And step four, according to the target interface name of the target service interface in the target configuration information and the Protobuf service protocol of the target service module obtained in the step three, dynamically generating a Protobuf object (namely the first target service protocol object) required by the target request packet by using a reflection mechanism of Protobuf.

In the related art, binary data assembly required by a target request packet is realized by a programming and compiling mode to realize corresponding logic, and each piece of programming code can only generate one type of request data of a binary stream for a specific service module and a service interface, so that the method is called a static generation mode. In the embodiment of the present disclosure, the dynamic generation of the Protobuf object required by the target request packet means that the reflection mechanism of the Protobuf can be used to generate request data of a binary stream applicable to a plurality of service modules and service interfaces.

And fifthly, dynamically assembling a target request packet of the binary stream by using a reflection mechanism of Protobuf according to the target request assembly logic in the target configuration information.

The Protobuf object required by the dynamic generation of the target request packet may be defined according to a protocol of Protobuf, and a target data packet of a legal binary stream may be assembled according to the target input parameter.

And sixthly, initiating service call according to the target request address obtained in the second step, calling the target service interface, and sending the target data packet of the binary stream to the target service module.

And seventhly, analyzing the data of the binary stream in the target return packet into a Protobuf object (a second target service protocol object) by using a reflection mechanism of Protobuf according to the Protobuf service protocol of the target service module obtained in the third step.

And eighthly, extracting corresponding target result data from the Protobuf objects obtained by analyzing the target loopback according to the target loopback extraction logic in the target configuration information.

In step S460, the target result data is transmitted.

And then, the universal data module sends the target result data to the application terminal. At this time, the target result data is already processed into a format of a general Protocol of the application end by using the second target service Protocol object, so that the application end does not need to analyze the target loopback packets by using different service loopback packet protocols according to different target service protocols adopted by each target service interface of each target service module any more, and in the embodiment of the present disclosure, the application end may directly use the general Protocol (for example, a Transmission Control Protocol/IP Protocol) adopted by the application end to obtain the target result data.

On one hand, when the required target result data is required to be acquired from the target service interface of the target service module, only a section of target structured data with a simple structure is required to be acquired, namely, a target request packet adapting to the target service interface of the target service module can be automatically generated according to the target input parameter and the target configuration name in the target structured data, and then the target request packet is sent to the target service module through the target service interface; on the other hand, when a target loopback packet of the target service module responding to the target request packet is received from the target service interface, the target loopback packet can be automatically analyzed to obtain the required target result data. When new target result data needs to be acquired, the required target result data can be quickly and simply acquired without recompiling and re-uploading the service code, the fixed parameters of the target service interface of the target service module do not need to be repeatedly compiled, the efficiency of acquiring the required target result data from the target service module is improved, the access and the use of any target service interface can be quickly and simply realized, and the implementation process and the iteration cost are greatly reduced.

Fig. 5 and 6 schematically show configuration diagrams of target configuration information corresponding to a target configuration name according to an embodiment of the present disclosure.

As shown in fig. 5 and 6, the generic data module provides a visual interface with rich auxiliary information, which can be used to help developers to implement configuration of target configuration information of target configuration names with low threshold. After configuration, the system can be used in each accessed internal general system.

As shown in fig. 5, taking the target service module to be remotely called XXX live broadcast as an example, the service interfaces of the target service module, such as service interface XXX1 with serial number 8, service interface XXX2 with serial number 32, service interface XXX3 with serial number 11, service interface XXX4 with serial number 19, and service interface XXX5 with serial number 81, are listed on the left side. The developer can select any one of them as the target business interface.

With continued reference to fig. 5, in the input box at the upper right side, a piece of invocation information in JSON (JavaScript Object Notation, JS Object Notation, a lightweight data exchange format) format may be input, and the formatted annotation is added after the corresponding line, and a standard expression of the annotation of the corresponding line is predefined, for example, it is assumed that:

{

“key1”:value1, //xxxx1

“key2”:value2, //xxxx2

“key3”:value3, //xxxx3

}

by right-clicking on the annotation, a visualization interface such as that shown in fig. 6 may be displayed in accordance with the standard representation of the predefined annotation.

In the visualization interface as shown in fig. 6, basic information, application-side call configuration, data item description, and parameter description can be configured.

The configuration of the basic information may include the following: inputting Arabic numerals, such as 0, as serial numbers of the target configuration names into the input boxes of the data _ id; data _ name, which can input target configuration name in the input box behind, can be represented by character string, and represents only one project mark service data or target operation; a unique target data name can be configured in an input box after the data name; the target module name can be configured in the input box after the module name; the target interface name may be configured in the input box after the "interface name".

For example:

module name: mmbizattr// target module name

Interface name: get// target interface name

It should be noted that, obtaining the target result data by the target configuration name is an optional manner, and the user may also select other development manners to obtain.

Optionally, a further description of the data of the basic information may be input in an input box after the "introduction", and the user may search the introduction content in the application.

Optionally, the use introduction of each target input parameter in the target configuration name and the like can also be input in the input box after the "remark", for example, the name of the target input parameter, the type of the parameter, which values can be taken, and what the meaning of different values is, in the following parameter description, which is convenient for use.

Optionally, maintainer information, such as a maintainer name, of the target configuration information for maintaining the target configuration name may be input in an input box after the "maintainer"; entering creator information such as a creator name of the target configuration information for creating the target configuration name in an input box after "creator"; the last reviewer information, for example, the last reviewer name, of the target configuration information that last revises the target configuration name is entered in the input box after the "last reviewer".

The calling configuration of the application end is a filling selection parameter, the filling selection parameter needs to be set when a special requirement exists, and the default value is used when the value is 0 or null. The developer can choose whether to turn on the item, for example, whether to do any one or more of the additional configurations in the embodiments described above.

For example, since the requested target service module, which is generally a distributed service, is deployed on multiple servers, the setting of the routing mode can determine to which servers the target request packet is sent, which is often used in a scenario where the servers have local caching logic.

For another example, the request timeout time may be configured to be 1000ms, and when the target request packet does not obtain a response after exceeding the request timeout time, the target request packet is discarded, so that the target request packet can achieve a protection effect on the service logic, avoid that the service logic at the calling is blocked for too long, and reduce the probability of no response.

For another example, whether to add a processing plug-in to the request for obtaining the target service data may be configured. For example, a processing plug-in of "call record" is added, and the position of the processing plug-in the target input parameter is configured, so that each subsequent call can be realized, and call record information is added to a certain record list corresponding to the target input parameter.

Wherein, the data item description is used to define the target loopback extraction logic, and fig. 6 is exemplified by the example of obtaining target service data. The developer can configure the name of the default return field, whether the configuration is array, whether the configuration is JSON, whether a default value is selected, etc. here.

In the embodiment of the present disclosure, a target loopback packet extraction logic of a target service interface is defined, the target loopback packet may be understood as a JSON, and the target loopback packet extraction logic may be a designated corresponding extraction field.

For example, target wrap: { "nickname": xxxx, "signature": xxx.,. said } is a logic configuration corresponding to an extracted nickname (nickname) and signature (signature), the corresponding extracted fields are nickname and signature, and the target business data may be a certain field or a combination thereof.

In the column of parameter description, a developer may define parameters corresponding to the target configuration name, where the parameter type of each parameter is bound, and the parameter type may be selected to be fixed or input, where selecting a fixed parameter type indicates that the corresponding parameter is a fixed parameter; and if the input parameter type is selected, the corresponding parameter is the input parameter.

The fixed parameters indicate that a user of the application end does not need to set the fixed parameters, and developers determine the values of the fixed parameters during configuration, so that the user of the application end does not need to input repeatedly; and the input parameters indicate that the user needing the application end indicates what the corresponding target input parameters are in the target structured data of the application end.

As shown in fig. 6, for example, assuming that the target input parameter includes a parameter 0 and a parameter 1, and the parameter type thereof is an input parameter, the names of the parameter 0 and the parameter 1, a key (key), whether an array is present, whether JSON is present, and what the default value is, may be set, respectively. Assuming that the fixed parameter is parameter 2, the parameter type can be set as the fixed parameter, and the name, key (key), whether array, JSON, and what default value of parameter 2 are set respectively.

According to the configurations of fig. 5 and 6 described above, the target request assembly logic of the target service interface can be defined, and the target request packet can be understood as a JSON, which is generally a combination of fixed parameters and target input parameters.

For example, the destination request packet: { "bizuin": xxxx, "use _ cache": 1}

Wherein the use _ cache can be a fixed parameter, and the value of the use _ cache is fixed to 1; bizuin represents the target input parameter extracted from the field, and may take the value xxxx. The above-mentioned destination request packet provides necessary information required for extracting destination result data.

The configured service request method provided by the embodiment of the disclosure can share and use the pre-configured target configuration information for multiple times through one-time configuration when the application terminal initiates calling, and can automatically adapt to the target service interface of the target service module according to the target request assembly logic in the target configuration information, thereby simplifying the generation process of the target request packet, avoiding recompilation and online every time, and improving the efficiency. And the target loopback packet can be automatically analyzed according to the target loopback packet extraction logic in the target configuration information and converted into the target loopback packet of the general protocol, so that the application end does not need to adopt the corresponding service loopback packet protocol to extract target result data from the target loopback packet aiming at the target service protocol of the target service interface of each target service module.

FIG. 7 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure. The method provided by the embodiment of the present disclosure may be executed by any electronic device, for example, the terminal device in fig. 1 described above, on which the application terminal is installed, which is not limited in this disclosure.

As shown in fig. 7, the method provided by the embodiment of the present disclosure may include the following steps.

In step S710, a target configuration name is determined.

In the embodiment of the present disclosure, a user of a terminal device may input a target data name in a user interface of an application, and a universal data module returns a target configuration name corresponding to the target data name, so that the target configuration name may be determined.

In step S720, target input parameters are obtained.

The meaning of the target input parameter may be displayed in a user interface of the application. Alternatively, the user directly inputs the target input parameter.

In step S730, target structured data is generated according to the target configuration name and the target input parameter.

The form of the target structured data can refer to the above-described embodiments.

In step S740, the target structured data is sent.

The application end can call the uniform calling interface provided by the universal data module and initiate the calling of the target service interface of the target service module according to the target structured data. Namely, the universal data module receives the target structured data, then constructs a target request packet, and sends the target request packet to the target service interface.

In step S750, target result data returned in response to the target structured data is received.

And the universal data module analyzes the received target repackage responding to the target request package, extracts target result data and returns the target result data to the application end.

The target result data in the embodiment of the present disclosure may be target service data or a response result returned by instructing the target service module to execute the target operation.

When the application terminal initiates the call of the target service module, the configurated service request method provided by the embodiment of the disclosure only needs to construct a section of simple target structured data, and does not need to adapt to a target service interface of the target service module, thereby reducing the process of constructing a target request packet with complex logic, and the implementation process is simple and quick.

For example, as shown in fig. 8, with the method provided by the embodiment of the present disclosure, in order to obtain the required target service data, the application end only needs to add a section of target structured data in the service code, and thus can obtain the target service data online.

Referring to the schematic diagram of the call link shown in fig. 9, with the method provided in the embodiment of the present disclosure, the application end may construct a simple section of target structured data by using a general logic, and then send the target structured data to the configured general data module, and the general data module may automatically generate a complete target request packet adapted to the target service interface of the target service module according to the configured target configuration information, that is, the general data module completes the process of constructing the complex logic. Then, the generic data module sends the target request packet to the target service interface of the target service module xxx. And then, the universal data module receives a target loopback packet returned by the target service module xxx, performs value taking of a designated field according to configured target loopback packet extraction logic, analyzes to obtain target result data, returns to return the target loopback packet to the application end by adopting a universal protocol, and the application end can take out the target service data by adopting the universal logic to obtain the target service data.

The general logic refers to logic that each application terminal can initiate the call of each target service module in general, and it is not necessary to compile a corresponding call code and compile an online for each target service interface of each target service module.

Referring to fig. 2, 3 and fig. 8 and 9, taking the auditing system as an example, during the service iteration, the auditing system often supplements the field for assisting auditing, for example, after a video article is newly added, the auditing system needs to supplement the article type field. In the related technology, C + + code needs to be written, and before the C + + code is pushed to an auditing system, an article type data pulling operation is newly added, and then compiling, debugging and online are performed. By adopting the method provided by the embodiment of the disclosure, for the application end, the requirement can be completed only by checking the newly added field by the auditing system to select the data source 'article type'. The newly added data source does not need programming, compiling, debugging and online, only needs simple configuration, and all places can be shared and used through one-time configuration.

For another example, taking the target service data of the nickname data acquired in the auditing system as an example, the nickname data acquisition process is compared:

the related technology comprises the following steps: a section of C + + code is used to perform encapsulation of a target request packet, disassembly of a target loopback packet, addition of compilation dependency, call logic of a dependent header file, a target service module and a target service interface, and the like, and approximately 200 characters need to be written. And at each place where the target service data is obtained, the obtaining of the calling code is completely realized, and the nickname data can be obtained subsequently after compiling and uploading for 1 hour.

The mode that this disclosure embodiment provided: the universal data module configures target configuration information (target module name, target interface name and target input parameters), and writing 100-less characters can be realized. After the target structured data is saved, the target structured data can be shared for use. That is, once configuration, the corresponding target configuration information can be used in various places by means of a unique target configuration name, and the configuration can be validated without compiling.

FIG. 10 schematically illustrates a flow diagram of a configured service request method according to an embodiment of the disclosure. As shown in fig. 10, the method provided by the embodiment of the present disclosure may include the following steps.

In step S1, the target configuration information of the target service interface of the target service module is configured in the generic data module.

In step S2, when the application needs to obtain the target service data, a piece of target structured data is added to the service code.

In step S3, the application sends the target structured data to the generic data module.

In step S4, after the generic data module receives the target structured data sent by the application, the target configuration information configured in step S1 is obtained according to the target structured data, and then the target request packet adapted to the target service interface of the target service module is automatically assembled according to the target request assembly logic in the target configuration information.

In step S5, the generic data module sends the target request packet to the target service interface of the target service module.

In step S6, after the target service module receives the target request packet through its target service interface, it responds to the target request packet to generate a target loopback packet, and sends the target loopback packet to the generic data module.

In step S7, after the generic data module receives the target loopback packet returned by the target service interface of the target service module, it automatically parses the target service data required in the target loopback packet according to the target loopback packet extraction logic in the target configuration information.

In step S8, the generic data module returns the parsed target service data to the application end, and the application end receives the required target service data.

The specific implementation process can refer to the description of other embodiments.

On one hand, the configured service request method provided by the embodiment of the disclosure enables an internal general system to be butted to various service modules through the same interface in a configuration mode; a set of special target request assembly logic is customized, the service interface use logic can be expressed with low threshold and high efficiency, and the svrkit request is dynamically assembled and initiated; on the other hand, the target repackage can be analyzed in real time and dynamically disassembled through the configured target repackage extraction logic. Compiling is not needed, so that testing and online zero-waiting are realized, the efficiency of developers and application terminals is improved, and the implementation and iteration cost is greatly reduced.

Any one of the above methods provided by the embodiments of the present disclosure may be implemented by using Cloud computing and Cloud storage technology in Cloud technology (Cloud technology), for example, the general data module and/or the target service module may be disposed in a Cloud server.

The cloud technology is a hosting technology for unifying series resources such as hardware, software, network and the like in a wide area network or a local area network to realize data calculation, storage, processing and sharing.

The cloud technology is a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied based on a cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture-like websites and more web portals. With the high development and application of the internet industry, each article may have its own identification mark and needs to be transmitted to a background system for logic processing, data in different levels are processed separately, and various industrial data need strong system background support and can only be realized through cloud computing.

Cloud computing (cloud computing) is a computing model that distributes computing tasks over a pool of resources formed by a large number of computers, enabling various application systems to obtain computing power, storage space, and information services as needed. The network that provides the resources is referred to as the "cloud". Resources in the "cloud" appear to the user as being infinitely expandable and available at any time, available on demand, expandable at any time, and paid for on-demand.

As a basic capability provider of cloud computing, a cloud computing resource pool (called as an Infrastructure as a Service (IaaS) platform for short) is established, and multiple types of virtual resources are deployed in the resource pool and are selectively used by external clients.

According to the logic function division, a PaaS (Platform as a Service) layer can be deployed on an IaaS (Infrastructure as a Service) layer, a SaaS (Software as a Service) layer is deployed on the PaaS layer, and the SaaS can be directly deployed on the IaaS. PaaS is a platform on which software runs, such as a database, a web container, etc. SaaS is a variety of business software, such as web portal, sms, and mass texting. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.

A distributed cloud storage system (hereinafter, referred to as a storage system) refers to a storage system that integrates a large number of storage devices (storage devices are also referred to as storage nodes) of different types in a network through application software or application interfaces to cooperatively work by using functions such as cluster application, grid technology, and a distributed storage file system, and provides a data storage function and a service access function to the outside.

At present, a storage method of a storage system is as follows: logical volumes are created, and when created, each logical volume is allocated physical storage space, which may be the disk composition of a certain storage device or of several storage devices. The application end stores data on a certain logical volume, namely, the data is stored on a file system, the file system divides the data into a plurality of parts, each part is an object, the object not only contains the data but also contains additional information such as data identification (ID, ID entry), the file system writes each object into a physical storage space of the logical volume respectively, and the file system records storage location information of each object, so that when the application end requests to access the data, the file system can enable the application end to access the data according to the storage location information of each object.

The process of allocating physical storage space for the logical volume by the storage system specifically includes: physical storage space is divided in advance into stripes according to a group of capacity measures of objects stored in a logical volume (the measures often have a large margin with respect to the capacity of the actual objects to be stored) and Redundant Array of Independent Disks (RAID), and one logical volume can be understood as one stripe, thereby allocating physical storage space to the logical volume.

Fig. 11 schematically illustrates a block diagram of a configured service request device according to an embodiment of the disclosure. The apparatus provided by the embodiment of the present disclosure may be disposed on any electronic device, for example, the terminal device and/or the server in fig. 1, which is not limited in this disclosure.

As shown in fig. 11, the configured service request apparatus 1100 provided by the embodiment of the present disclosure may include: a structured data acquisition unit 1110, a target request packet generation unit 1120, a target request packet transmission unit 1130, a target return packet reception unit 1140, a target result data acquisition unit 1150, and a target result data return unit 1160.

The structured data obtaining unit 1110 may be configured to obtain target structured data, where the target structured data includes a target configuration name and a target input parameter. The target request packet generating unit 1120 may be configured to generate a target request packet adapted to a target service interface of the target service module according to the target input parameter and the target configuration name. The target request packet sending unit 1130 may be configured to send the target request packet to the target service module through the target service interface. The destination loopback receiving unit 1140 may be configured to receive a destination loopback of the destination service module responding to the destination request packet from the destination service interface. The target result data obtaining unit 1150 may be configured to parse the target loopback packet to obtain target result data. The target result data returning unit 1160 may be used to transmit the target result data.

On one hand, when the required target result data is required to be acquired from the target service interface of the target service module, only a section of target structured data with a simple structure needs to be acquired, that is, a target request packet adapted to the target service interface of the target service module can be automatically generated according to the target input parameter and the target configuration name in the target structured data, and then the target request packet is sent to the target service module through the target service interface; on the other hand, when a target loopback packet of the target service module responding to the target request packet is received from the target service interface, the target loopback packet can be automatically analyzed to obtain the required target result data. When new target result data needs to be acquired, the required target result data can be quickly and simply acquired without recompiling and re-uploading the service code, the fixed parameters of the target service interface of the target service module do not need to be repeatedly compiled, the efficiency of acquiring the required target result data from the target service module is improved, the access and the use of any target service interface can be quickly and simply realized, and the implementation process and the iteration cost are greatly reduced.

In an exemplary embodiment, the configured service request apparatus 1100 may further include: a module interface determining unit, configured to determine the target service module and a target service interface thereof; a configuration name data name configuration unit, configured to configure a target configuration name corresponding to the target service interface and a target data name corresponding to the target result data; the module name interface name setting unit can be used for setting a target module name of the target service module and a target interface name of the target service interface; a request assembly logic setting unit, configured to set a target request assembly logic of a target request packet of the target service interface, where the target request assembly logic includes a target fixed parameter and the target input parameter; and the loopback extraction logic setting unit can be used for setting the target loopback extraction logic of the target loopback of the target service interface.

In an exemplary embodiment, the configured service request device 1100 may further include at least one of a routing mode setting unit, a request timeout time setting unit, and a processing plug-in setting unit. The routing mode setting unit may be configured to set a routing mode of the destination request packet. The request timeout time setting unit may be configured to set a request timeout time of the target request packet. The processing plug-in setting unit may be configured to set a processing plug-in of the destination request packet.

In an exemplary embodiment, the target request packet generating unit 1120 may include: a configuration information obtaining unit, configured to obtain target configuration information according to the target configuration name, where the target configuration information includes a target interface name of the target service interface and a target request assembly logic of the target request packet; a service protocol obtaining unit, configured to obtain a target service protocol of the target service module; a first service protocol object generating unit, configured to generate a first target service protocol object according to the target interface name and a target service protocol of the target service module; a request packet generating unit, configured to generate the target request packet by using the first target service protocol object and according to the target request assembly logic and the target input parameter.

In an exemplary embodiment, the target traffic interface may employ a remote invocation framework that supports a reflection mechanism. Wherein, the service agreement obtaining unit may include: a service protocol reading unit, configured to read a target service protocol of the target service module from a first target cache if the target service protocol of the target service module exists in the first target cache; a reflection obtaining service protocol unit, configured to obtain a target service protocol of the target service module by using a reflection mechanism of the remote invocation framework if the target service protocol of the target service module does not exist in the first target cache; a service protocol cache unit, configured to store a target service protocol of the target service module in the first target cache.

In an exemplary embodiment, the target service protocol of the target service module may include a target service protocol of each service interface in the target service module, and each service interface of the target service module includes the target service interface. Wherein the first service protocol object generating unit may include a first target service protocol object unit. The first target service protocol object unit may be configured to generate the first target service protocol object required by the target request packet by using a reflection mechanism of a target service protocol of the target service interface corresponding to the target interface name.

In an exemplary embodiment, the request packet generating unit may include: an input parameter assembly unit operable to assemble the target input parameters into the target request assembly logic; a fixed parameter obtaining unit, configured to obtain a target fixed parameter in the target request assembly logic; a request assembly logic conversion unit, operable to convert the target request assembly logic including the target fixed parameters and the target input parameters into the target request packet of a binary stream using the first target service protocol object.

In an exemplary embodiment, the target configuration information may further include a target module name of the target service module. The destination request packet sending unit 1130 may include: a request address obtaining unit, configured to obtain a target request address of the target service module according to the name of the target module; and the initiating and calling unit can be used for calling the target request address and sending the target request packet of the binary stream to the target service interface.

In an exemplary embodiment, the request address obtaining unit may include: a request address reading unit, configured to, if a target request address of the target service module exists in a second target cache, read the target request address from the second target cache according to the name of the target module; a route obtaining request address unit, configured to, if a target request address of the target service module does not exist in the second target cache, obtain the target request address by using a route implementation service to discover according to the name of the target module; and the request address cache unit may be configured to store the target module name and the target request address in the second target cache in an associated manner.

In an exemplary embodiment, the target configuration information may further include target loopback extraction logic. The target result data obtaining unit 1150 may include: a second service protocol object generating unit, configured to parse the target loopback packet of the binary stream into a second target service protocol object according to a reflection mechanism of a target service protocol of the target service module; a result data extraction unit operable to extract the target result data from the second target service agreement object using the target loopback extraction logic.

The specific implementation of each unit in the configured service request device provided in the embodiment of the present disclosure may refer to the content in the configured service request method, and is not described herein again.

Fig. 12 schematically illustrates a block diagram of a configured service request device according to an embodiment of the disclosure. The apparatus provided by the embodiment of the present disclosure may be disposed on any electronic device, for example, the terminal device in fig. 1, which is not limited in this disclosure.

As shown in fig. 12, the configured service request apparatus 1200 provided by the embodiment of the present disclosure may include: a target configuration name determining unit 1210, a target input parameter obtaining unit 1220, a structured data generating unit 1230, a structured data transmitting unit 1240, and a target result data receiving unit 1250.

The target configuration name determining unit 1210 may be configured to determine a target configuration name. The target input parameter obtaining unit 1220 may be used to obtain a target input parameter. The structured data generating unit 1230 may be configured to generate the target structured data according to the target configuration name and the target input parameter. The structured data sending unit 1240 may be configured to send the target structured data. Target result data receiving unit 1250 may be used to receive target result data returned in response to the target structured data.

It should be noted that although in the above detailed description several units of the device for action execution are mentioned, this division is not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.

Reference is now made to fig. 13, which illustrates a schematic diagram of an electronic device suitable for use in implementing embodiments of the present application. The electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

Referring to fig. 13, an electronic device provided in an embodiment of the present disclosure may include: a processor 1301, a communication interface 1302, a memory 1303, and a communication bus 1304.

Wherein, the processor 1301, the communication interface 1302 and the memory 1303 complete the communication with each other through the communication bus 1304.

Alternatively, the communication interface 1302 may be an interface of a communication module, such as an interface of a GSM (Global System for Mobile communications) module. The processor 1301 is used to execute programs. The memory 1303 stores programs. The program may comprise a computer program comprising computer operating instructions. Wherein, can include in the procedure: and (5) a program of a game application terminal.

The processor 1301 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement embodiments of the present disclosure.

The memory 1303 may include a Random Access Memory (RAM) memory, and may further include a non-volatile memory (e.g., at least one disk memory).

Among them, the procedure can be specifically used for: acquiring target structured data, wherein the target structured data comprises a target configuration name and a target input parameter; generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name; sending the target request packet to the target service module through the target service interface; receiving a target return packet of the target service module responding to the target request packet from the target service interface; analyzing the target return packet to obtain target result data; and returning the target result data. Alternatively, the program may be specifically for: determining a target configuration name; obtaining target input parameters; generating target structured data according to the target configuration name and the target input parameters; sending the target structured data; and receiving target result data returned in response to the target structured data.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations of the embodiments described above.

It is to be understood that any number of elements in the drawings of the present disclosure are by way of example and not by way of limitation, and any nomenclature is used for differentiation only and not by way of limitation.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A configured service request method, applied to a generic data module, the method comprising:

acquiring target structured data from an application end, wherein the target structured data comprises a target configuration name and target input parameters;

generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name;

sending the target request packet to the target service module through the target service interface;

receiving a target return packet of the target service module responding to the target request packet from the target service interface;

analyzing the target return packet to obtain target result data;

sending the target result data to the application end;

generating a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name, wherein the generating of the target request packet comprises:

obtaining target configuration information according to the target configuration name, wherein the target configuration information comprises a target interface name of the target service interface and target request assembly logic of the target request packet;

obtaining a target service protocol of the target service module;

generating a first target service protocol object according to the target interface name and a target service protocol of the target service module;

and generating the target request packet by utilizing the first target service protocol object and according to the target request assembly logic and the target input parameters.

2. The method of claim 1, further comprising:

determining the target service module and a target service interface thereof;

configuring a target configuration name corresponding to the target service interface and a target data name corresponding to the target result data;

setting a target module name of the target service module and a target interface name of the target service interface;

setting a target request assembly logic of a target request packet of the target service interface, wherein the target request assembly logic comprises a target fixed parameter and the target input parameter;

and setting target return packet extraction logic of the target return packet of the target service interface.

3. The method of claim 2, further comprising at least one of:

setting a routing mode of the target request packet;

setting the request timeout time of the target request packet;

and setting a processing plug-in of the target request packet.

4. The method of claim 1, wherein the target service interface employs a remote invocation framework that supports a reflection mechanism; wherein, obtaining the target service protocol of the target service module comprises:

if the target service protocol of the target service module exists in the first target cache, reading the target service protocol of the target service module from the first target cache;

if the target service protocol of the target service module does not exist in the first target cache, acquiring the target service protocol of the target service module by using a reflection mechanism of the remote call frame;

and storing the target service protocol of the target service module to the first target cache.

5. The method according to claim 1, wherein the target service protocol of the target service module includes a target service protocol of each service interface in the target service module, and each service interface of the target service module includes the target service interface; generating a first target service protocol object according to the target interface name and the target service protocol, wherein the generating of the first target service protocol object comprises:

and generating the first target service protocol object required by the target request packet by using a reflection mechanism of a target service protocol of the target service interface corresponding to the target interface name.

6. The method of claim 1, wherein generating the target request packet using the first target service agreement object and according to the target request assembly logic and the target input parameters comprises:

assembling the target input parameters into the target request assembly logic;

obtaining a target fixed parameter in the target request assembly logic;

converting the target request assembly logic including the target fixed parameters, the target input parameters into the target request packet of binary stream using the first target service protocol object.

7. The method of claim 6, wherein the target configuration information further comprises a target module name of the target business module; wherein sending the target request packet to the target service module through the target service interface comprises:

obtaining a target request address of the target service module according to the name of the target module;

and calling the target request address, and sending the target request packet of the binary stream to the target service interface.

8. The method of claim 7, wherein obtaining the target request address of the target service module according to the target module name comprises:

if the target request address of the target service module exists in a second target cache, reading the target request address from the second target cache according to the name of the target module;

if the target request address of the target service module does not exist in the second target cache, utilizing a route to realize service discovery according to the name of the target module, and acquiring the target request address;

and storing the target module name and the target request address to the second target cache in an associated manner.

9. The method of claim 1, wherein the target configuration information further comprises target loopback extraction logic; analyzing the target return packet to obtain target result data, wherein the analyzing comprises:

analyzing the target return packet of the binary stream into a second target service protocol object according to a reflection mechanism of a target service protocol of the target service module;

and extracting the target result data from the second target service protocol object by using the target loopback packet extraction logic.

10. A configured service request method is applied to an application end, and the method comprises the following steps:

determining a target configuration name;

obtaining target input parameters;

generating target structured data according to the target configuration name and the target input parameters;

sending the target structured data to a universal data module so that the universal data module generates a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name, sending the target request packet to the target service module through the target service interface, receiving a target return packet of the target service module responding to the target request packet from the target service interface, and analyzing the target return packet to obtain target result data;

receiving the target result data returned by the universal data module in response to the target structured data;

the generating, by the universal data module, a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name includes:

obtaining a target service protocol of the target service module;

11. A configured service request device, for application to a generic data module, the device comprising:

the system comprises a structured data acquisition unit, a data processing unit and a data processing unit, wherein the structured data acquisition unit is used for acquiring target structured data from an application end, and the target structured data comprises a target configuration name and a target input parameter;

a target request packet generating unit, configured to generate a target request packet adapted to a target service interface of a target service module according to the target input parameter and the target configuration name;

a target request packet sending unit, configured to send the target request packet to the target service module through the target service interface;

a target packet return receiving unit, configured to receive, from the target service interface, a target packet return of the target service module in response to the target request packet;

a target result data obtaining unit, configured to analyze the target repackage to obtain target result data;

the target result data returning unit is used for sending the target result data to the application end;

wherein the target request packet generating unit includes:

a configuration information obtaining unit, configured to obtain target configuration information according to the target configuration name, where the target configuration information includes a target interface name of the target service interface and a target request assembly logic of the target request packet;

a service protocol obtaining unit, configured to obtain a target service protocol of the target service module;

a first service protocol object generating unit, configured to generate a first target service protocol object according to the target interface name and a target service protocol of the target service module;

and the request packet generating unit is used for generating the target request packet by utilizing the first target service protocol object according to the target request assembly logic and the target input parameters.

12. The apparatus of claim 11, further comprising:

a module interface determining unit, configured to determine the target service module and a target service interface thereof;

a configuration name data name configuration unit, configured to configure a target configuration name corresponding to the target service interface and a target data name corresponding to the target result data;

a module name interface name setting unit, configured to set a target module name of the target service module and a target interface name of the target service interface;

a request assembly logic setting unit, configured to set a target request assembly logic of a target request packet of the target service interface, where the target request assembly logic includes a target fixed parameter and the target input parameter;

and the return packet extraction logic setting unit is used for setting the target return packet extraction logic of the target return packet of the target service interface.

13. The apparatus according to claim 12, wherein the apparatus further comprises at least one of a routing mode setting unit, a request timeout setting unit, a processing plug-in setting unit; wherein,

the routing mode setting unit is used for setting the routing mode of the target request packet;

the request overtime setting unit is used for setting the request overtime of the target request packet;

the processing plug-in setting unit is used for setting the processing plug-in of the target request packet.

14. The apparatus of claim 11, wherein the target traffic interface employs a remote invocation framework that supports a reflection mechanism; wherein the service agreement obtaining unit includes:

a service protocol reading unit, configured to read a target service protocol of the target service module from a first target cache if the target service protocol of the target service module exists in the first target cache;

a reflection obtaining service protocol unit, configured to, if a target service protocol of the target service module does not exist in the first target cache, obtain the target service protocol of the target service module by using a reflection mechanism of the remote invocation framework;

and the service protocol cache unit is used for storing the target service protocol of the target service module to the first target cache.

15. The apparatus according to claim 11, wherein the target service protocol of the target service module includes a target service protocol of each service interface in the target service module, and each service interface of the target service module includes the target service interface;

wherein the first service protocol object generating unit includes:

a first target service protocol object unit, configured to generate the first target service protocol object required by the target request packet by using a reflection mechanism of a target service protocol of the target service interface corresponding to the target interface name.

16. The apparatus of claim 11, wherein the request packet generating unit comprises:

an input parameter assembly unit for assembling the target input parameters into the target request assembly logic;

a fixed parameter obtaining unit, configured to obtain a target fixed parameter in the target request assembly logic;

a request assembly logic conversion unit for converting the target request assembly logic including the target fixed parameters and the target input parameters into the target request packet of a binary stream using the first target service protocol object.

17. The apparatus of claim 16, wherein the target configuration information further comprises a target module name of the target business module; wherein the target request packet transmitting unit includes:

a request address obtaining unit, configured to obtain a target request address of the target service module according to the name of the target module;

and the initiating and calling unit is used for calling the target request address and sending the target request packet of the binary stream to the target service interface.

18. The apparatus of claim 17, wherein the request address obtaining unit comprises:

a request address reading unit, configured to, if a target request address of the target service module exists in a second target cache, read the target request address from the second target cache according to the name of the target module;

a route obtaining request address unit, configured to, if a target request address of the target service module does not exist in the second target cache, obtain the target request address by using a route implementation service discovery according to the name of the target module;

and the request address cache unit is used for storing the target module name and the target request address to the second target cache in an associated manner.

19. The apparatus of claim 11, wherein the target configuration information further comprises target loopback extraction logic; wherein the target result data obtaining unit includes:

a second service protocol object generating unit, configured to parse the target loopback packet of the binary stream into a second target service protocol object according to a reflection mechanism of a target service protocol of the target service module;

a result data extraction unit, configured to extract the target result data from the second target service agreement object by using the target loopback extraction logic.

20. A configured service request apparatus, applied to an application, the apparatus comprising:

a target configuration name determining unit for determining a target configuration name;

a target input parameter obtaining unit for obtaining a target input parameter;

the structured data generating unit is used for generating target structured data according to the target configuration name and the target input parameters;

the structured data sending unit is used for sending the target structured data to a general data module, the general data module comprises a target request packet generating unit, a target request packet sending unit, a target loopback packet receiving unit and a target result data obtaining unit, the target request packet generating unit is used for generating a target request packet which is matched with a target service interface of a target service module according to the target input parameter and the target configuration name, the target loopback packet receiving unit is used for sending the target request packet to the target service module through the target service interface and receiving the target loopback packet of the target service module responding to the target request packet from the target service interface, and the target result data obtaining unit is used for analyzing the target loopback packet and obtaining target result data;

a target result data receiving unit, configured to receive the target result data returned by the generic data module in response to the target structured data;

wherein the target request packet generating unit includes:

21. A computer-readable storage medium having stored thereon computer-executable instructions for performing the method of any one of claims 1 to 10.

22. An electronic device, comprising:

at least one processor;

a storage device configured to store at least one program that, when executed by the at least one processor, causes the at least one processor to implement the method of any one of claims 1 to 10.