CN114968621B

CN114968621B - Data communication method, device, equipment, storage medium and system

Info

Publication number: CN114968621B
Application number: CN202210504610.XA
Authority: CN
Inventors: 张子岳; 郭鲲鹏; 王景佩
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Filing date: 2022-05-10
Publication date: 2024-07-02
Anticipated expiration: 2042-05-10

Abstract

The present disclosure relates to a data communication method, apparatus, device, storage medium, and system. The data communication method applied to the communication middleware comprises the following steps: determining a target field corresponding to a target service interface from a field set corresponding to a server based on client information in an interface call request sent by a target client; the field set comprises scope parameters of fields corresponding to each service interface deployed in the server; sending an interface calling request to a server and receiving calling response data fed back by the server; and performing field filtering on the call response data based on the target field, generating target response data, and sending the target response data to the target client. According to the embodiment of the disclosure, the field filtering logic adapting to the target service interface can be generated more flexibly, the field filtering code of the response data and the service code deployed by the service end are decoupled, the reusability of the field filtering logic is improved, and the maintenance cost of the field filtering code is reduced.

Description

Data communication method, device, equipment, storage medium and system

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data communication method, apparatus, device, storage medium, and system.

Background

With more and more functions of the application program, more and more service interfaces corresponding to the application program in the server end exist, and the service functions corresponding to the service interfaces are overlapped. When any service interface is called, the service end operates the corresponding service function and generates response data. The response data often includes field data of a plurality of service interfaces, that is, the response data includes redundant field data except for field data required by the called service interface.

In the prior art, the scheme for filtering redundant field data in response data is mainly characterized in that filtering logic of field data is hard-coded in a service code in the development process of a service interface, so that a service end executes the filtering logic in the process of executing a service function, and the purpose of filtering the redundant field data is achieved.

However, in the above scheme, each time the filtering logic of the field data is updated, the code of the relevant service part in the service end needs to be updated, so that the maintenance cost is high and the reusability is low.

Disclosure of Invention

In order to solve the technical problems, the present disclosure provides a data communication method, a device, a server, a storage medium and a system.

In a first aspect, an embodiment of the present disclosure provides a data communication method, applied to a communication middleware, including:

receiving an interface call request sent by a target client; wherein, the interface call request contains the client information of the target client;

Determining a target field corresponding to a target service interface from a field set corresponding to a server based on the client information; the field set comprises scope parameters of fields corresponding to all service interfaces deployed in the service end; the target service interface is the service interface corresponding to the interface call request;

The interface calling request is sent to the server side, and calling response data fed back by the server side are received;

And performing field filtering on the call response data based on the target field to generate target response data, and sending the target response data to the target client.

In a second aspect, an embodiment of the present disclosure further provides a data communication method, applied to an interface management platform, where the method includes:

Determining scope parameters of fields contained in each service interface deployed in the server in response to the parameter setting operation;

Generating a field set based on each scope parameter in response to a field set generating operation, and sending the field set to communication middleware; the communication middleware is used for determining a target field corresponding to a target service interface based on the field set and performing field filtering on call response data corresponding to the target service interface based on the target field; the target service interface is the called service interface.

In a third aspect, embodiments of the present disclosure further provide a data communication apparatus, configured and communication middleware, the apparatus including:

the interface call request receiving module is used for receiving an interface call request sent by the target client; wherein, the interface call request contains the client information of the target client;

The target field determining module is used for determining a target field corresponding to a target service interface from a field set corresponding to a server based on the client information; the field set comprises scope parameters of fields corresponding to all service interfaces deployed in the service end; the target service interface is the service interface corresponding to the interface call request;

the call response data receiving module is used for sending the interface call request to the server and receiving call response data fed back by the server;

And the target response data generation module is used for carrying out field filtering on the call response data based on the target field, generating target response data and sending the target response data to the target client.

In a fourth aspect, an embodiment of the present disclosure further provides a data communication apparatus, a configuration and interface management platform, the apparatus including:

the scope parameter determining module is used for determining the scope parameters of the fields contained in the service interfaces in response to the parameter setting operation;

The field set generating module is used for responding to field set generating operation, generating a field set based on each scope parameter and sending the field set to the communication middleware; the communication middleware is used for determining a target field corresponding to a target service interface based on the field set and performing field filtering on call response data corresponding to the target service interface based on the target field; the target service interface is the called service interface.

In a fifth aspect, embodiments of the present disclosure further provide an electronic device, including:

A processor;

A memory for storing executable instructions;

The processor is configured to read the executable instructions from the memory, and execute the executable instructions to implement a data communication method applied to the communication middleware described in any embodiment of the disclosure, or implement a data communication method applied to the interface management platform described in any embodiment of the disclosure.

In a sixth aspect, the present disclosure provides a computer readable storage medium storing a computer program, which when executed by a processor, causes the processor to implement a data communication method applied to a communication middleware as described in any embodiment of the present disclosure, or to implement a data communication method applied to an interface management platform as described in any embodiment of the present disclosure.

In a seventh aspect, embodiments of the present disclosure further provide a data communication system, the system including: the system comprises a target client, a server and a communication middleware which are in communication connection;

the target client is used for sending an interface calling request to the communication middleware and receiving target response data sent by the communication middleware; wherein, the interface call request contains the client information of the target client;

The communication middleware is used for receiving the interface calling request, determining a target field corresponding to a target service interface from a field set corresponding to the service end based on the client information, sending the interface calling request to the service end, and receiving calling response data fed back by the service end; performing field filtering on the call response data based on the target field to generate target response data, and sending the target response data to the target client; the field set comprises scope parameters of fields corresponding to all service interfaces deployed in the service end; the target service interface is the service interface corresponding to the interface call request;

The server is used for receiving the interface call request sent by the communication middleware, responding to the interface call request to generate call response data, and sending the call response data to the communication middleware.

According to the data communication method, the device, the equipment, the storage medium and the system, in the communication middleware except the client and the server, according to the client information of the target client contained in the interface call request sent by the target client, the target field of the called target service interface is determined from the field set corresponding to the server, wherein the field set comprises the scope parameters of the fields corresponding to the service interfaces deployed in the server; the target field is utilized to carry out field filtering on call response data of the interface call request fed back by the server, and the target response data after field filtering is generated; on one hand, the field filtering codes of the response data and the service codes deployed by the server can be decoupled, so that the reusability of the field filtering logic is improved, and the maintenance cost of the field filtering codes is reduced; on the other hand, the required target field can be determined through the field set, so that the generation flexibility of the field filtering logic and the adaptation degree of the field filtering logic to the service interface are improved, and the reusability of the field filtering logic is further improved.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

Fig. 1 is a system architecture diagram of a data communication system according to an embodiment of the present disclosure;

fig. 2 is a system architecture diagram of another data communication system provided in an embodiment of the present disclosure;

fig. 3 is a flow chart of a data communication method applied to a communication middleware according to an embodiment of the disclosure;

Fig. 4 is a flowchart of a data communication method applied to an interface management platform according to an embodiment of the present disclosure;

FIG. 5 is a schematic illustration of a display of a parameter setting interface according to an embodiment of the disclosure;

Fig. 6 is a schematic structural diagram of a data communication device configured in a communication middleware according to an embodiment of the disclosure;

Fig. 7 is a schematic structural diagram of a data communication device configured in an interface management platform according to an embodiment of the disclosure;

Fig. 8 is a schematic structural diagram of a server according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

In the related art, in response to an interface call request from a client, the service side carries redundant field data because a plurality of service interfaces correspond to common codes of an application program in addition to field data required by the called service interface in response data fed back to the client. This causes problems, for example, when the client code is developed, the redundant field data contained in the response data needs to be understood, which increases the development cost; for another example, in the service online operation process, the transmission of the redundant field can cause the waste of network bandwidth, resulting in the rise of the delay of the interface; as another example, random exposure of redundant fields may introduce additional security concerns. Therefore, when developing the service code corresponding to the service interface, the related technology hard codes the field filtering logic of the service interface in the service code, so that after the service is in online operation, redundant fields in response data obtained by the service end can be filtered in the interface calling process of the client end.

However, in the above field filtering scheme for the service interface, each time the field filtering logic is modified, the service code needs to be synchronously modified, so that the maintenance cost of the field filtering logic is high, and the reusability of the field filtering process is poor.

Based on the above situation, the embodiments of the present disclosure provide a data communication scheme, so as to generate a field set in advance according to scope parameters of fields included in each service interface, and screen, in a communication middleware, a target field required by a called service interface from the field set according to client information included in an interface call request of a client, and perform field filtering on response data of the server according to the target field, so as to obtain response data of a non-redundant field required by the client, thereby not only decoupling a service code and field filtering logic, but also improving reusability of a field filtering flow, and improving flexibility of generating the field filtering logic and adapting degree thereof to the service interface, and further improving reusability of the field filtering logic.

Fig. 1 is a system architecture diagram of a data communication system according to an embodiment of the present disclosure. The system and the data communication method of the subsequent embodiments of the present disclosure belong to the same inventive concept, and in the details of the embodiments of the data communication system, reference may be made to the respective embodiments of the subsequent data communication method.

As shown in fig. 1, the data communication system 100 includes: a target client 101, a server 103, and a communication middleware 102; the target client 101 is communicatively connected to the communication middleware 102, and the communication middleware 102 is communicatively connected to the server 103.

The target client 101 is a client that initiates an interface call request in the current flow, in which an application corresponding to a service interface is installed. The target client 101 is configured to send an interface call request to the communication middleware 102, and receive target response data sent by the communication middleware 102. The target client 101 may be a mobile terminal such as a smart phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a Tablet PC (Tablet Personal Computer), a notebook PC, a Portable multimedia player (Portable MEDIA PLAYER, PMP), a vehicle-mounted terminal (e.g., a vehicle navigation terminal), a wearable device, etc., and a fixed terminal such as a digital television, a desktop computer, etc.

Communication middleware 102 is a communication component between a client and a server in which a set of fields corresponding to server 103 is stored. The communication middleware 102 is configured to receive an interface call request sent by the target client 101, screen a target field corresponding to a called target service interface from a field set based on client information in the interface call request, send the interface call request to the server 103, and receive call response data fed back by the server 103; and performing field filtering on the call response data based on the target field, generating target response data, and transmitting the target response data to the target client 101. The field set comprises scope parameters of fields corresponding to each service interface deployed in the server.

In some embodiments, the communication middleware 102 may be an interface gateway and the field sets may be implemented as related plug-ins published to the interface gateway.

In other embodiments, the communication middleware 102 may be a software development kit (Software Development Kit, SDK) component that the server 103 relies on, and the field sets may be implemented as SDK components. The server 103 refers to the SDK component by information such as version number.

The server 103 is a single server or a server cluster deployed with a service corresponding to the application program, and is configured to receive an interface call request sent by the communication middleware 102, generate call response data in response to the interface call request, and send the call response data to the communication middleware 102. The service end 103 does not execute the field filtering logic, but directly executes the called service code, so that the call response data includes the field data of each field included in the called target service interface and the field data of at least some fields included in at least one other service interface. The other service interfaces are call interfaces externally provided by other services except the called service in each service deployed by the service end.

According to the data communication system provided by the embodiment of the disclosure, in the communication middleware except the client and the server, according to the client information of the target client contained in the interface call request sent by the target client, determining the target field of the called target service interface from the field set corresponding to the server, wherein the field set comprises the scope parameters of the fields corresponding to the service interfaces deployed in the server; the target field is utilized to carry out field filtering on call response data of the interface call request fed back by the server, and the target response data after field filtering is generated; on one hand, the field filtering codes of the response data and the service codes deployed by the server can be decoupled, so that the reusability of the field filtering logic is improved, and the maintenance cost of the field filtering codes is reduced; on the other hand, the required target field can be determined through the field set, so that the generation flexibility of the field filtering logic and the adaptation degree of the field filtering logic to the service interface are improved, and the reusability of the field filtering logic is further improved.

Fig. 2 illustrates a system architecture diagram of another data communication system provided by an embodiment of the present disclosure. As shown in fig. 2, the data communication system adds an interface management platform 104 on the basis of the above embodiments, and the interface management platform 104 is communicatively connected to the communication middleware 102.

The interface management platform 104 is a device where a software platform for managing each service interface deployed by a server end is located, and may be a notebook computer, a desktop computer, a single server, a server cluster, or the like. In the embodiment of the present disclosure, to provide the visualized interaction function, the interface management platform 104 may be implemented as a device having a display function and providing a man-machine interaction function.

In the disclosed embodiment, the interface management platform 104 is at least configured to: in response to the parameter setting operation, determining scope parameters of fields contained in each service interface deployed in the server 103; and generating a field set based on each scope parameter and transmitting the field set to the communication middleware 102 in response to the field set generating operation. In this way, a developer can generate a field set for field filtering more conveniently through the visual interactive editing function provided by the interface management platform 104, and the updating efficiency of the field filtering logic can be improved through combination with the communication middleware, so that other potential safety hazard problems are avoided being introduced to the server side in the updating process, and the efficiency of processes such as establishment, auditing, effectiveness and the like of the field filtering logic can be improved.

In addition, the interface management platform 104 has basic interface management functions. For example, the interface management platform 104 may also be used to import service interface related information, generate interface meta information describing the service interface, and the like.

Based on the data communication system, the embodiment of the disclosure also provides a data communication method applied to the communication middleware, and the method can be applied to a scene of remote service call. The method may be performed by a data communication device configured in communication middleware, which may be implemented in software and/or hardware, and which may be integrated in the communication middleware. The communication middleware can be network equipment, such as various gateways, passing through in the original flow of communication between the client and the service end; or a network device, such as an intermediate server, is added in the original communication process between the client and the server; but also a device or component integrated in the server.

In some embodiments, the communication middleware includes an interface gateway or server-side dependent software development kit component. In the case that the communication middleware is a network device in the original communication flow, the communication middleware may be specifically an interface gateway. Therefore, a developer can realize the hot update of the field filtering logic only by releasing the new version field set to the interface gateway, improve the update efficiency of the field filtering logic and reduce the potential safety hazard in the service calling process. In the case where the communication middleware is a device or component integrated in the server, the communication middleware may specifically be a server-dependent SDK component. Therefore, a developer can complete the updating of the field filtering logic only by updating the field set in the SDK component and updating the component version number of the SDK component referenced by the server, and the updating efficiency of the field filtering logic can also be improved and the potential safety hazard in the service calling process can be reduced.

Fig. 3 is a schematic flow chart of a data communication method applied to a communication middleware according to an embodiment of the disclosure. As shown in fig. 3, the data communication method may include the steps of:

s310, receiving an interface call request sent by a target client.

The interface call request refers to an access request for remotely calling a certain service function through a service interface, and the interface call request at least comprises client information of a target client. The client information is related information of the target client, and may be at least one of a client type (such as a computer end and a mobile end) of the target client, an application program identifier (such as an application program name, an abbreviated code, an encoding code, etc.) of the target client for initiating a service call, an operating system type and an operating system version number carried by the client, etc. In the embodiment of the disclosure, the information dimension of the client information at least covers the parameter dimension of the scope parameter in the subsequent field set.

Specifically, the target client initiates an interface call request to the server in response to a user operation or a preset event (such as the arrival of a timer, the completion of the presentation of the loaded data, etc.). The interface call request passes through the communication middleware before reaching the server. I.e. the communication middleware receives the interface call request sent by the target client.

S320, determining a target field corresponding to the target service interface from a field set corresponding to the server based on the client information.

The field set comprises scope parameters of fields corresponding to each service interface deployed in the server. Scope parameters are parameters used to characterize in which cases a field is valid/available. Illustratively, the scope parameters include an application identifier corresponding to the service interface, an operating system type of the client that invokes the service interface, and operating system version information. The operating system version information may be an operating system version number or an operating system version number range. The target service interface is a service interface corresponding to the interface call request. The target field is a field required in response data corresponding to the target service interface.

Specifically, according to the above description, the service end includes redundant fields in response data obtained after the service interfaces are called because the service interfaces correspond to the application program common codes. Therefore, in the embodiment of the present disclosure, a scope parameter is set for a field required for each service interface, so as to ensure that a field corresponding to each service interface is valid only when the service interface is called, thereby ensuring that the response data does not include field data of redundant fields. And storing the corresponding relation of the service interface-field-scope parameters as a field set to be released into the communication middleware.

After receiving the interface call request, the communication middleware analyzes the interface call request to acquire the client information of the target client. And then, inquiring the field set by taking the client information as an index, and screening out a target field corresponding to the target service interface from the field set.

In some embodiments, the client information includes a target application identifier, a target operating system type, and an operating system version number, so that an information dimension included in the client information and a parameter dimension of a scope parameter are kept consistent, thereby reducing difficulty in subsequent field screening and improving field screening efficiency.

Accordingly, S320 includes: and matching the target application program identifier, the target operating system type and the operating system version number with the application program identifier, the operating system type and the operating system version information corresponding to the fields respectively aiming at each field in the field set, and determining the field as a target field when the matching is successful.

Specifically, the target field may be selected from the field set by traversing the field set according to the client information. In the traversal process, for each field in the field set, the target application program identifier, the target operating system type and the operating system version number in the client information are respectively matched with the application program identifier, the operating system type and the operating system version information in the scope parameters of the field in the corresponding dimension. If all three information dimensions match successfully, namely the target application identification = application identification in the scope parameter, the target operating system type = operating system type in the scope parameter, the operating system version number e operating system version information, then the field is determined as the target field and the next field is traversed according to the above procedure. If at least one of the three information dimensions does not match successfully, the next field is traversed according to the procedure described above. This allows efficient and accurate field screening with fewer matches in information dimension.

In some embodiments, the field set is generated based on scope parameters of fields corresponding to each service interface entered in the interface management platform.

The interface management platform is used for providing a visual parameter setting function of any field contained in any service interface, for example, a formalized parameter editing interface of the field contained in the service interface.

Specifically, in the embodiment of the present disclosure, scope parameters of fields corresponding to each service interface are set through a visual parameter setting function provided by the interface management platform, and a field set is generated based on the scope parameters. Therefore, the developer can conveniently and rapidly increase and decrease the service interfaces and the corresponding fields thereof, so that the field set can be quickly and efficiently modified, the convenient management and modification of the field filtering logic can be realized, and the maintenance cost of the field filtering strategy can be further reduced. In addition, the generation efficiency and the auditing efficiency of the field filtering strategy can be improved through a visual interaction mode provided by the interface management platform, so that the field filtering strategy and the research and development flow of the service interface can realize closed loop.

It should be noted that, in view of the fact that the plurality of service interfaces correspond to the application program common code and that at least two service interfaces correspond to the same field, the embodiment of the disclosure interconnects the application program common code at the leading use of each service interface, for example, copies the common code corresponding to the same field, so as to ensure that the field filtering policies of each service interface on the application program common code are independent from each other.

S330, sending the interface call request to the server and receiving call response data fed back by the server.

Specifically, the communication middleware sends an interface call request to the server. After receiving the interface call request, the server can analyze the interface call request, execute service logic corresponding to the target service interface according to the analysis result and generate call response data. The call response data is response data directly generated by the server side, and comprises field data corresponding to the target service interface and at least part of field data corresponding to at least one other service interface. And then, the server feeds back the calling response data to the communication middleware.

S340, field filtering is carried out on the call response data based on the target field, target response data is generated, and the target response data is sent to the target client.

Specifically, the communication middleware deserializes call response data, only the field data corresponding to the target field in the call response data is reserved in the deserializing process, and the remaining field data are all removed, so that the field-filtered response data can be obtained. And then, the communication middleware sequences the response data after field filtering to generate target response data. And then, the communication middleware resends the target response data to the target client to complete a service call flow.

In some embodiments, the target application corresponding to the target client is generated based on the target field. That is, in the development process of the target client, a developer may develop the client code of the target client according to field filtering logic in the communication middleware, in addition to considering meta information of the service interface. Therefore, developers do not need to understand redundant field information in response data fed back by the server, the development difficulty of the client is reduced, and the development efficiency of the client is improved.

According to the data communication method applied to the communication middleware provided by the embodiment of the disclosure, in the communication middleware except the client and the server, according to the client information of the target client contained in the interface call request sent by the target client, the target field of the called target service interface is determined from the field set corresponding to the server, wherein the field set comprises the scope parameters of the fields corresponding to the service interfaces deployed in the server; the target field is utilized to carry out field filtering on call response data of the interface call request fed back by the server, and the target response data after field filtering is generated; on one hand, the field filtering codes of the response data and the service codes deployed by the server can be decoupled, so that the reusability of the field filtering logic is improved, and the maintenance cost of the field filtering codes is reduced; on the other hand, the required target field can be determined through the field set, so that the generation flexibility of the field filtering logic and the adaptation degree of the field filtering logic to the service interface are improved, and the reusability of the field filtering logic is further improved.

In some embodiments, the update process and the validation process of the field filtering logic can be more convenient and efficient due to the existence of the communication middleware, and other potential safety hazard problems introduced in the process can be avoided.

In an example, in a case where the communication middleware is an interface gateway, the data communication method applied to the communication middleware further includes: and in response to the field set issuing operation, updating the field set by using a new field set corresponding to the issuing operation.

In particular, if the communication middleware is implemented as an interface gateway, the developer may publish a new set of fields to the interface gateway. After detecting the field set issuing operation, the interface gateway uses the received new field set to replace the original field set, for example, uses the new field set to generate a new plug-in, and uses the new plug-in to replace the plug-in generated by the original field set to complete plug-in updating, thereby completing the hot updating of the field filtering logic.

In another example, in a case where the communication middleware is a software development kit component, the data communication method applied to the communication middleware further includes: responding to the updating operation of the field set, storing the updated field set, generating an updated software development kit component based on the updated field set, and determining a new component version number of the updated software development kit component; and sending the new component version number to the server side so that the server side refers to the updated software development kit component based on the new component version number.

Specifically, if the communication middleware is implemented as an SDK component, the communication middleware stores the updated field set uploaded by the developer to a corresponding storage location upon receiving it. The updated set of fields is then utilized to generate an updated SDK component and determine a new component version number of the updated SDK component. For example, according to the version number coding rule, a new component version number is automatically generated on the basis of the component version number of the original SDK component; or when the developer uploads the updated field set, the new component version number is uploaded synchronously. The communication middleware then sends the new component version number to the server. The server modifies its reference relationship to the SDK component, e.g., replaces the component version number in the reference relationship with a new component version number.

It should be noted that the SDK component may be deployed in the server, that is, the communication middleware is deployed in the server. Thus, the update process of the SDK component is executed by the server.

The embodiment of the disclosure also provides a data communication method applied to the interface management platform, and the method can be applied to a scene of remote service call. The method may be performed by a data communication device configured in an interface management platform, which may be implemented in software and/or hardware.

Fig. 4 is a flowchart illustrating a data communication method applied to an interface management platform according to an embodiment of the present disclosure. As shown in fig. 4, the data communication method applied to the interface management platform may include the steps of:

S410, in response to the parameter setting operation, determining the scope parameters of fields contained in each service interface deployed in the server.

Specifically, each service interface and its corresponding field can be displayed in the interface management platform, and a visual function for setting parameters for the field is provided. In this way, the developer can interactively parameter set fields displayed in the interface management platform. And the interface management platform responds to the parameter setting operation and can determine the scope parameters of the fields corresponding to each service interface.

In some embodiments, S410 includes: responding to the triggering operation of any service interface, displaying a parameter setting interface corresponding to the service interface, and displaying each field and parameter setting control contained in the service interface in the parameter setting interface; and responding to the triggering operation of the parameter setting control corresponding to any field, displaying a parameter input interface corresponding to the triggered field at a preset position of the parameter setting interface, and responding to the input operation of the parameter input interface, and determining the scope parameters of the triggered field.

Specifically, each service interface is displayed in a form or tree form in the interface management platform. The developer may perform triggering operations such as clicking, touching, voice control, etc., on either service interface. In response to the trigger operation, the interface management platform displays a parameter setting interface 500 as shown in fig. 5. The parameter setting interface 500 displays therein interface meta information 501 of a certain service interface and fields corresponding to the service interface, such as fields subordinate to a request body "and response data" query "in fig. 5, and displays a parameter setting control 502 at a corresponding position of each field (fig. 5 is exemplified in the last column of the table of the formalization). In FIG. 5, three field dimensions are contained in parameter settings control 502, namely, an application identification "App-id," an Operating System type "Operating-System," and Operating System version information "version.

The developer may trigger the operation by the parameter setting control 502 for any of the fields displayed in the parameter setting interface 500. In response to the trigger operation, the interface management platform displays a floating window or jumps to a new page in the parameter setting interface 500, and displays a parameter input interface in the floating window or the new page. The parameter input interface can provide parameter candidate controls of a drop-down box or parameter input controls of a text box and the like. The developer may then perform parameter input operations on the parameter input interface, such as selecting candidate parameter values, inputting parameter values via a keyboard or voice or touch, and the like. For example, an application program identifier is input, an operating system type is selected to be an android system type, an Ios system type or a saint system type, and the minimum version number and the maximum version number of an operating system version are input. The interface management platform then determines scope parameters for the triggered fields in response to the parameter entry operation.

S420, generating a field set based on each scope parameter in response to the field set generation operation, and sending the field set to the communication middleware; the communication middleware is used for determining a target field corresponding to the target service interface based on the field set and carrying out field filtering on call response data corresponding to the target service interface based on the target field; the target service interface is the called service interface.

Specifically, the interface management platform also provides related controls that generate a set of fields. The developer can trigger the control. And the interface management platform responds to the triggering operation and generates a field set by utilizing the scope parameters of the fields corresponding to the service interfaces determined in the process. Then, the interface management platform transmits the field set to the communication middleware in response to the field set issuing operation performed by the developer, so that the communication middleware performs the steps of S310 to S340 described above.

According to the data communication method applied to the interface management platform, through the interactive operation of the visualized interface management platform, the setting of the scope parameters of the fields corresponding to each service interface and the generation and release of the field set are realized, the generation efficiency and the update efficiency of the field set are improved, and therefore the universality and the reusability of field filtering logic in the communication middleware are improved.

The following is an embodiment of a data communication apparatus provided in the embodiment of the present invention, which belongs to the same inventive concept as the data communication method of the above embodiments, and reference may be made to the embodiments of the data communication method for details that are not described in detail in the embodiments of the data communication apparatus.

Fig. 6 is a schematic structural diagram of a data communication device configured in a communication middleware according to an embodiment of the disclosure. As shown in fig. 6, the data communication apparatus 600 configured in the communication middleware may include:

An interface call request receiving module 610, configured to receive an interface call request sent by a target client; the interface call request comprises client information of a target client;

A target field determining module 620, configured to determine, based on the client information, a target field corresponding to the target service interface from a field set corresponding to the server; the field set comprises scope parameters of fields corresponding to all service interfaces deployed in the service end; the target service interface is a service interface corresponding to the interface call request;

The call response data receiving module 630 is configured to send an interface call request to the server, and receive call response data fed back by the server;

the target response data generating module 640 is configured to perform field filtering on the call response data based on the target field, generate target response data, and send the target response data to the target client.

According to the data communication device configured in the communication middleware provided by the embodiment of the disclosure, in the communication middleware except the client and the server, according to the client information of the target client contained in the interface calling request sent by the target client, a target field of a called target service interface is determined from a field set corresponding to the server, wherein the field set comprises scope parameters of fields corresponding to all service interfaces deployed in the server; the target field is utilized to carry out field filtering on call response data of the interface call request fed back by the server, and the target response data after field filtering is generated; on one hand, the field filtering codes of the response data and the service codes deployed by the server can be decoupled, so that the reusability of the field filtering logic is improved, and the maintenance cost of the field filtering codes is reduced; on the other hand, the required target field can be determined through the field set, so that the generation flexibility of the field filtering logic and the adaptation degree of the field filtering logic to the service interface are improved, and the reusability of the field filtering logic is further improved.

In some embodiments, the field set is generated based on scope parameters of fields corresponding to each service interface entered in the interface management platform; the interface management platform is used for providing a visualized parameter setting function of any field contained in any service interface.

In some embodiments, the scope parameters include an application identification corresponding to the service interface, an operating system type of the client invoking the service interface, and operating system version information.

In some embodiments, the client information includes a target application identification, a target operating system type, and an operating system version number;

accordingly, the target field determination module 620 is specifically configured to:

And matching the target application program identifier, the target operating system type and the operating system version number with the application program identifier, the operating system type and the operating system version information corresponding to the fields respectively aiming at each field in the field set, and determining the field as a target field when the matching is successful.

In some embodiments, the communication middleware includes an interface gateway or server-side dependent software development kit component.

In some embodiments, the data communication apparatus 600 configured in the communication middleware further includes a field set update module for:

under the condition that the communication middleware is an interface gateway, responding to field set release operation, and updating the field set by using a new field set corresponding to the release operation;

Or alternatively

In the case that the communication middleware is a software development kit component, storing an updated field set in response to an update operation of the field set, generating an updated software development kit component based on the updated field set, and determining a new component version number of the updated software development kit component;

and sending the new component version number to the server side so that the server side refers to the updated software development kit component based on the new component version number.

In some embodiments, the target application corresponding to the target client is generated based on the target field.

The data communication device configured in the communication middleware provided by the embodiment of the invention can execute the data communication method applied to the communication middleware provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Fig. 7 is a schematic structural diagram of a data communication device configured in an interface management platform according to an embodiment of the disclosure. As shown in fig. 7, the data communication apparatus 700 configured in the interface management platform may include:

a scope parameter determining module 710, configured to determine a scope parameter of each field included in each service interface in response to the parameter setting operation;

A field set generating module 720, configured to generate a field set based on each of the scope parameters in response to a field set generating operation, and send the field set to the communication middleware; the communication middleware is used for determining a target field corresponding to a target service interface based on the field set and performing field filtering on call response data corresponding to the target service interface based on the target field; the target service interface is the called service interface.

According to the data communication device configured on the interface management platform, through the interactive operation of the visualized interface management platform, the setting of the scope parameters of the fields corresponding to each service interface and the generation and release of the field set are realized, the generation efficiency and the update efficiency of the field set are improved, and therefore the universality and the reusability of field filtering logic in the communication middleware are improved.

In some embodiments, the response parameter setting operation 710 is specifically for:

responding to the triggering operation of any service interface, displaying a parameter setting interface corresponding to the service interface, and displaying each field and parameter setting control contained in the service interface in the parameter setting interface;

And responding to the triggering operation of the parameter setting control corresponding to any field, displaying a parameter input interface corresponding to the triggered field at a preset position of the parameter setting interface, and responding to the input operation of the parameter input interface, and determining the scope parameters of the triggered field.

The data communication device configured on the interface management platform provided by the embodiment of the invention can execute the data communication method applied to the interface management platform provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

It should be noted that, in the above embodiment of the data communication apparatus, each included module is only divided according to the functional logic, but not limited to the above division, so long as the corresponding function can be implemented; in addition, the specific names of the functional modules are also only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present disclosure.

The disclosed embodiments also provide an electronic device that may include a processor and a memory that may be used to store executable instructions. The processor may be configured to read the executable instructions from the memory and execute the executable instructions to implement the data communication method applied to the communication middleware or the data communication method applied to the interface management platform in the foregoing embodiments.

In some embodiments, the electronic device may be a communication middleware such as an interface gateway or an SDK component; in other embodiments, the electronic device may be a device in which the interface management platform resides.

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

As shown in fig. 8, the electronic device 800 may include a processing means (e.g., a central processor, a graphics processor, etc.) 801 that may perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 802 or programs loaded from a storage 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the information processing apparatus 800 are also stored. The processing device 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output interface (I/O interface) 805 is also connected to the bus 804.

In general, the following devices may be connected to the I/O interface 805: input devices 806 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 807 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, etc.; storage 808 including, for example, magnetic tape, hard disk, etc.; communication means 809. The communication means 809 may allow the electronic device 800 to communicate wirelessly or by wire with other devices to exchange data.

It should be noted that the electronic device 800 shown in fig. 8 is only an example, and should not impose any limitation on the functions and application scope of the embodiments of the present disclosure. That is, while FIG. 8 illustrates an electronic device 800 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 809, or installed from storage device 808, or installed from ROM 802. When the computer program is executed by the processing device 801, the above-described functions defined in the data communication method applied to the communication middleware or the data communication method applied to the interface management platform of any embodiment of the present disclosure are performed.

The embodiments of the present disclosure also provide a computer-readable storage medium storing a computer program, which when executed by a processor, causes the processor to implement a data communication method applied to a communication middleware or a data communication method applied to an interface management platform in any embodiment of the present disclosure.

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

In some embodiments, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP, and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the steps of the data communication method applied to the communication middleware or the data communication method applied to the interface management platform described in any of the embodiments of the present disclosure.

In an embodiment of the present disclosure, computer program code for performing the operations of the present disclosure may be written in one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

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

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. A method of data communication, applied to communication middleware, comprising:

2. The method of claim 1, wherein the set of fields is generated based on the scope parameters of the fields corresponding to each of the service interfaces entered in an interface management platform; the interface management platform is used for providing a visual parameter setting function of any field contained in any service interface.

3. The method according to claim 1 or 2, wherein the scope parameters include an application program identifier corresponding to the service interface, an operating system type of a client that invokes the service interface, and operating system version information.

4. The method of claim 3, wherein the client information includes a target application identification, a target operating system type, and an operating system version number;

The determining, based on the client information, the target field corresponding to the target service interface from the field set corresponding to the server includes:

And for each field in the field set, matching the target application program identifier, the target operating system type and the operating system version number with the application program identifier, the operating system type and the operating system version information corresponding to the field respectively, and determining the field as the target field when the matching is successful.

5. The method of claim 1, wherein the communication middleware comprises an interface gateway or the server-side dependent software development kit component.

6. The method of claim 5, wherein in the case where the communication middleware is the interface gateway, the method further comprises:

Responding to a field set release operation, and updating the field set by utilizing a new field set corresponding to the release operation;

Or in the case that the communication middleware is the software development kit component, the method further comprises:

storing an updated field set in response to an update operation of the field set, generating an updated software development kit component based on the updated field set, and determining a new component version number of the updated software development kit component;

And sending the new component version number to the server so that the server references the updated software development kit component based on the new component version number.

7. The method of claim 1, wherein the target application corresponding to the target client is generated based on the target field.

8. A method of data communication, applied to an interface management platform, comprising:

9. The method of claim 8, wherein determining scope parameters for fields included in each service interface in response to a parameter setting operation comprises:

And responding to the triggering operation of the parameter setting control corresponding to any field, displaying a parameter input interface corresponding to the triggered field at a preset position of the parameter setting interface, and responding to the input operation of the parameter input interface, and determining the scope parameter of the triggered field.

10. A data communication apparatus, configured in communication middleware, comprising:

11. A data communication apparatus, configured on an interface management platform, comprising:

12. An electronic device, comprising:

A processor;

A memory for storing executable instructions;

Wherein the processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the data communication method applied to the communication middleware according to any one of claims 1 to 7, or implement the data communication method applied to the interface management platform according to claim 8 or 9.

13. A computer readable storage medium, characterized in that the storage medium stores a computer program, which when executed by a processor causes the processor to implement the data communication method applied to the communication middleware according to any one of the preceding claims 1 to 7 or to implement the data communication method applied to the interface management platform according to any one of the preceding claims 8 or 9.

14. A data communication system, comprising: the system comprises a target client, a server and a communication middleware which are in communication connection;

15. The system of claim 14, wherein the data communication system further comprises an interface management platform communicatively coupled to the communication middleware for:

Determining the scope parameters of the fields contained in the service interfaces deployed in the service end in response to a parameter setting operation;

And generating the field set based on each scope parameter in response to a field set generating operation, and sending the field set to the communication middleware.