CN113326409A

CN113326409A - Table display method, equipment and system

Info

Publication number: CN113326409A
Application number: CN202010132767.5A
Authority: CN
Inventors: 徐豪灿
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2020-02-29
Filing date: 2020-02-29
Publication date: 2021-08-31
Also published as: WO2021170120A1

Abstract

The application provides a table display method, which comprises the following steps: the server receives data description and style description sent by the terminal equipment, wherein the data description comprises an interface identifier of an interface, the interface is used for acquiring resource data, and the style description is used for describing a form style adopted when the resource data is presented; the server analyzes the data description and generates a query request according to the data description, wherein the query request comprises an interface identifier; the server sends a query request to an Application Program Interface (API) gateway so that the API gateway calls an interface to acquire resource data according to an interface identifier in the query request; the server receives the resource data sent by the API gateway, extracts form data from the resource number, and organizes and sorts the form data according to form styles to obtain a form; the server sends the form to the terminal device.

Description

Table display method, equipment and system

Technical Field

The present application relates to the cloud field, and in particular, to a method, a device, and a system for displaying a table.

Background

With the development of cloud technology, the quantity and the variety of resource data in a cloud system are more and more. However, the storage space in the cloud system is very limited, and the cloud system can only fixedly store part of the commonly used resource data for the user to view. However, the needs of users are diverse and different users desire to view different content.

Therefore, the existing cloud system cannot meet different requirements of users, and the user experience is greatly influenced.

Disclosure of Invention

In order to solve the above problems, the present application provides a table display method, apparatus, and system, which can autonomously define data in a table and a table style of the table, thereby satisfying diverse needs of users.

In a first aspect, a table display method is provided, the method comprising:

the method comprises the steps that a server receives data description and style description sent by terminal equipment, wherein the data description comprises an interface identifier of an interface, the interface is used for acquiring resource data, and the style description is used for describing a form style adopted when the resource data is presented;

the server analyzes the data description and generates a query request according to the data description, wherein the query request comprises the interface identifier;

the server sends a query request to an Application Program Interface (API) gateway so that the API gateway calls the interface to acquire the resource data according to the interface identifier in the query request;

the server receives the resource data sent by the API gateway, extracts table data from the resource number, and organizes and sorts the table data according to the table style to obtain a table;

and the server sends the form to the terminal equipment.

In some possible designs, the data description includes an API field and a value field, where the API field is used to provide parameters required for obtaining the resource data to an API gateway, the API field includes an interface identifier of the interface, and the value field is used for the server to rely on to extract the form data from the resource data.

In some possible designs, where the query request is an HTTP request, the API fields may further include: HTTP method, query parameters, response header fields, and data alias.

In some possible designs, the value field further includes a key and a data source, the data source is equivalent to the data alias, and the extracting the table data from the resource number includes: the server extracts the table data of the key-value index from the resource data indicated by the data source.

In a second aspect, a table display method is provided, the method comprising:

the method comprises the steps that terminal equipment obtains user input data description and style description, wherein the data description comprises an interface identifier of an interface, the interface is used for obtaining resource data, and the style description is used for describing a form style adopted when the resource data is presented;

the terminal device transmits the input data description and the style description to the server.

In some possible designs, the value field also includes a key and a data source, the data source being equivalent to the data alias.

In a third aspect, a table display method is provided, the method comprising:

the method comprises the steps that an API gateway receives a query request sent by a server, wherein the query request comprises an interface identifier, and the query request is generated according to data description sent by terminal equipment;

the API gateway calls the interface to acquire resource data according to the interface identifier in the query request;

the API gateway sends the resource data to the server.

In some possible designs, where the query request is an HTTP request, the API fields may further include: the system comprises an HTTP method, a query parameter, a response header field and a data alias, wherein the resource data are borne in the HTTP response.

In a fourth aspect, a server is provided, comprising: the device comprises a receiving module, an analyzing module, an extracting module and a sending module;

the receiving module is used for receiving data description and style description sent by terminal equipment, wherein the data description comprises an interface identifier of an interface, the interface is used for acquiring resource data, and the style description is used for describing a form style adopted when the resource data is presented;

the analysis module is used for analyzing the data description and generating an inquiry request according to the data description, wherein the inquiry request comprises the interface identifier;

the sending module is used for sending a query request to an Application Program Interface (API) gateway so that the API gateway calls the interface to acquire the resource data according to the interface identifier in the query request;

the receiving module is further configured to receive the resource data sent by the API gateway;

the extraction module is used for extracting table data from the resource number and organizing and sorting the table data according to the table style so as to obtain a table;

the sending module is further configured to send the table to the terminal device.

In some possible designs, the value field also includes a key and a data source, the data source being equivalent to the data alias,

the extraction module is specifically configured to: and extracting table data of the key value index from the resource data indicated by the data source.

In a fifth aspect, a terminal device is provided, which includes an obtaining module and a sending module;

the acquisition module is used for acquiring user input data description and style description, wherein the data description comprises an interface identifier of an interface, the interface is used for acquiring resource data, and the style description is used for describing a form style adopted when the resource data is presented;

the sending module is used for sending the input data description and the style description to the server.

In a sixth aspect, an API gateway is provided, comprising: receiving module, calling module and sending module

The receiving module is used for receiving an inquiry request sent by a server, wherein the inquiry request comprises the interface identifier, and the inquiry request is generated according to data description sent by terminal equipment;

the calling module is used for calling the interface to acquire resource data according to the interface identifier in the query request;

the sending module is used for sending the resource data to the server.

In a seventh aspect, there is provided a server comprising a memory and a processor executing a program in the memory to run a computing service and a storage service to perform the method of any of the first aspect.

In an eighth aspect, there is provided a terminal device comprising a memory and a processor executing a program in the memory to run a computing service and a storage service to perform the method of any of the second aspects.

In a ninth aspect, there is provided an API gateway comprising a memory and a processor executing a program in the memory to run a computing service and a storage service to perform the method of any of the third aspects.

A tenth aspect provides a readable storage medium comprising instructions which, when executed on a server, cause the server to perform the method of any of the first, second or third aspects.

In an eleventh aspect, there is provided a computer program product which, when read and executed by a terminal device, causes a method according to any one of the first, second or third aspects to be performed.

In the above scheme, the server may send the query request to the API gateway according to the data description input by the user at the terminal device, so that the API gateway calls the interface to obtain the resource data according to the interface identifier in the query request, and then organizes and sorts the resource data returned by the API gateway according to the style description input by the user at the terminal device, thereby obtaining the form.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

FIG. 1 is a schematic diagram of some cloud services to which the present application relates;

FIG. 2 is a schematic illustration of some form styles to which the present application relates;

FIG. 3 is a schematic diagram of a table presentation system provided herein;

FIG. 4 is a schematic diagram of the structure of some of the interfaces in the API gateway provided by the present application;

FIG. 5 is a schematic flow chart diagram of a table presentation method provided herein;

fig. 6 is a block diagram of a terminal device according to an implementation manner provided in the present application;

FIG. 7 is a schematic diagram of a server in one implementation provided herein;

FIG. 8 is a block diagram of a server implementation provided herein;

fig. 9 is a schematic structural diagram of an API gateway provided in the present application.

Detailed Description

With the development of cloud technology, cloud systems can provide more and more cloud services. As shown in fig. 1, the cloud service may be divided into a storage service, a network service, a computing service, a security service, a disaster recovery service, an application service, a big data service, a database service, and the like, which are not particularly limited herein.

The Storage Service may include an Elastic Volume Service (EVS), an Object Storage Service (OBS), and a Scalable File Service (SFS), among others.

Network services may include Virtual Private Cloud (VPC), Elastic IP (EIP), Elastic Load Balancing (ELB), Virtual Firewall (VFW), Virtual Private Network (VPN), Security Group (SG), and so on.

The computing service may include: an Elastic Cloud Server (ECS), a Bare Metal Server (BMS), an Image Management Service (IMS), and an Elastic Scaling (AS), among others.

The security services may include: program execution Authentication (ARS), Security Index Service (SIS), Security posture Awareness (SSA), Edge Firewall (EdgeFW), Host Security Service (HSS), and Database Security Service (DBSS), among others.

The disaster recovery service may include: cloud disk Backup (VBS), Cloud Server Backup (CSBS), Cloud Server master/slave Disaster recovery (CSDR), Cloud Server High Availability (CSHA), and Cloud disk High Availability (VHA), among others.

The application services may include: a Message Notification Service (SMN), a Virtual Application service (vAPP), and a microservice cloud Application platform (ServiceStage), among others.

Big data services may include: hadoop Service (HDS), Analytical DataBase (ADS), and monitoring Service (FIMAS), among others.

Data services may include an Oracle Database Service, and a Relational Database Service (RDS), among others.

It is understood that the above Cloud services are merely examples, and in other embodiments, the Cloud services may further include VMware Cloud services, public components, real-time Stream Computing Services (CS), Data Visualization (DLV), and the like, and are not limited herein.

The number of cloud services that a cloud system can provide is related to the amount of resource data the cloud system has. Specifically, the amount of resource data in the cloud system is equal to the sum of resource data that each cloud service in the cloud system has.

The resource data of EVS, OBS, SFS, …, Oracle database service, RDS will be described in detail below. For simplicity, the details of the resource data in the middle portion are omitted without affecting reading.

Taking the EVS as an example, the resource data of the EVS may include: hard Disk Name (Disk Name), hard Disk specification, charging mode, Disk mode, mount server, and so on.

Taking OBS as an example, the resource data of OBS may include: bucket name, storage category, storage usage, number of objects, and so on.

Taking SFS as an example, the resource data of SFS may include: name, type, protocol, capacity, encryption, mount address, etc. resource fields.

Taking the VPC as an example, the resource data of the VPC may include: network segment, subnet number, name (name), creation time (create _ time), and identification (id), among other resource fields.

Taking EIP as an example, the resource data of EIP may include: charging type, bandwidth, IP address, and price, etc.

Taking an ELB as an example, the resource data of the ELB may include: monitor and member, etc. resource fields.

…；

Taking an Oracle database service as an example, the resource data of the Oracle database service may include: instance name, type, backup information, capacity, maximum number of connections, TPS/QPS, port information, etc. resource fields.

Taking the RDS database service as an example, the resource data of the RDS database service may include: instance name, type, backup information, capacity, maximum number of connections, TPS/QPS, port information, etc. resource fields.

It is understood that the above resource data is for example only, and in other embodiments, more or less resource data may be included, and the resource data may include more or less resource fields, which are not specifically limited herein.

As can be seen from the above statements, the resource data in the cloud system is characterized by a huge amount and a wide variety. With the development of cloud technology, cloud systems can provide more and more cloud services, and the amount and variety of resource data in the cloud systems continue to increase. However, the storage space in the cloud system is very limited, and the cloud system can only fixedly store part of the commonly used resource data for the user to view. However, the demands of users are various, and different users desire to view different contents, for example, some customers desire the table to simultaneously present the VPC resource data and the EIP resource data, some customers desire the table to simultaneously present the DBSS resource data and the CSHA resource data, and some customers desire the table to simultaneously present the VPC resource data, the EVS resource data, and the SMN resource data, so that the existing cloud system cannot meet different demands of users.

In order to facilitate the user to perform complex statistical operation and graphical display, the resource data in the cloud system are organized and arranged into a table in a preset table style. When a user needs to view resource data in the cloud system, the cloud system presents a pre-generated table to the user. Wherein, the composition elements of the table style comprise: chart attribute elements and render attribute elements, and the like. Wherein, the chart attribute elements may include: title, column width, column header, hint, filter field, explicit or implicit, page flip configuration, etc. Rendering the property elements may include: color, font, centering, offset, hinting format, hinting location, and the like. Here, different table styles can be obtained by combining different constituent elements. In some specific real examples, the table style may be as shown in fig. 2 (a), where both the header and the table are background-free; alternatively, as shown in fig. 2 (b), the header is background color, and the table is not background color; alternatively, as shown in fig. 2 (c), the header is not background color, and the table is background color; alternatively, as shown in fig. 2 (d), the header is background color and the table is background color. It should be understood that the table style is only used as some specific examples, and in practical applications, the number of rows, columns, shading, rows, columns, widths of rows and columns, etc. of the table style may be different, and are not limited herein.

In a specific example, the organizing of the resource data in the cloud system into the table in the preset table style may be: the cloud system places all resource data belonging to storage service in a table with no bottom texture in the same header and table, places all resource data belonging to network service in a table with no bottom texture in the same header and table, places all resource data belonging to computing service in a table with no bottom texture in the same header and table, performs security service, places all resource data belonging to disaster recovery service in a table with no bottom texture in the same header and table, performs security service, places all resource data belonging to application service in a table with no bottom texture in the same header and table, performs security service, places all resource data belonging to big data service in a table with no bottom texture in the same header and table, performs security service, places all resource data belonging to database service in a table with no bottom texture in the same header and table, and placing all resource data belonging to the security service in the same table with no background print in the same header and the same table. It is understood that the above examples are only used as examples, and in other embodiments, the resource data of the same cloud service may be placed in the same table with the bottom shading, and the table is a table without the bottom shading, or the resource data of two cloud services belonging to the same class of service may be placed in the table with the bottom shading, and the table is a table with the bottom shading, and the like, which are not limited in detail here.

In the cloud system, the resource data of the table is fixed, and the table style of the table is also fixed, however, the requirements of the user on the table resource data and the table style of the table are various, for example, the user needs to present the resource data of the VPC and the resource data of the EIP at the same time, and needs a₁*b₁A table with the size, wherein a square where the resource data of the VPC in the table is located is filled with ground color to be highlighted; the user needs to present the VPC resource data and the EIP resource data at the same time, and needs a₂*b₂In the large-sized table, the head of the table needs to be filled with ground color to be highlighted, so that the conventional cloud system cannot meet different requirements of users.

In order to solve the above problems, the present application provides a table presenting method, system and related device, which can autonomously define data in a table and a table style of the table, thereby satisfying diversified needs of users.

Referring to fig. 3, fig. 3 is a schematic structural diagram of a table presentation system provided in the present application. The form presentation system of the present embodiment includes: terminal device 110, server 120, and API gateway 130. Wherein the content of the first and second substances,

terminal device 110 may be an entity for interacting with a user. A terminal device may also be referred to as a cloud terminal, client, computing device, user terminal, user agent, user unit, remote terminal, user device, or user equipment, among others. The terminal device can be a thick Client or a Thin Client (Thin Client). The terminal equipment can be a desktop computer, a notebook computer, a tablet computer and a smart phone, and can also be vehicle-mounted equipment, wearable equipment and the like. By way of example, and not limitation, in embodiments of the present invention, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

The server 120 may be a web server, the primary function of which is to provide web information browsing services. The web server may parse the HTTP protocol. When the Web server receives an HTTP request (request) sent by the terminal device 110, an HTTP response (response) is returned to the terminal device 110.

The API gateway 130 is a gateway that specifically integrates APIs. The API gateway stores a plurality of APIs, and different APIs can acquire different resource data. The number of the API integrated by the API gateway determines the capability of the API gateway for acquiring the resource data. That is to say, the greater the number of integrated APIs in the API gateway, the stronger the ability of the API gateway to obtain resource data, and conversely, the smaller the number of integrated APIs in the API gateway, the weaker the ability of the API gateway to obtain resource data. For example, the API gateway may integrate an EVS interface, an OBS interface, an SFS interface, …, an Oracle interface, an RDS interface, and the like. The EVS interface is used for being called by the API gateway, so that resource data of the EVS are obtained; the OBS interface is used for being called by the API gateway, so that the resource data of the OBS are obtained; the SFS interface is used for calling the API gateway so as to obtain SFS resource data; …, respectively; the Oracle database service interface is used for being called by the API gateway, so that resource data of the Oracle database service are obtained; the RDS database service interface is used for being called by the API gateway so as to obtain the resource data of the RDS database service. It should be understood that the above examples are merely specific examples, and in other embodiments, the API may further obtain resource data with a larger granularity or a smaller granularity, for example, the API may be a storage service interface, and the storage service interface is used for being called by an API gateway, so as to obtain resource data of various cloud services (e.g., an EVS, an OBS, an SFS, and the like) under the storage service, and the like, and is not limited herein.

In a specific embodiment of the present application, the implementation manner of the API gateway 130 may include the following two types:

in the first method, as shown in fig. 4 (a), a plurality of APIs are integrated in the same API gateway. For example, the same API gateway may integrate the EVS interface, OBS interface, SFS interface, …, Oracle interface, and RDS interface. It should be understood that the above example is only used as a specific example, in practical applications, the number of the APIs integrated by the integration interface in the same API gateway may be more or less, and the granularity of the APIs integrated in the same API gateway may be more or less, and is not limited in particular herein.

In the second approach, as shown in fig. 4 (b), a plurality of APIs are integrated in different API gateways. For example, the API gateway 1 may integrate the EVS interface, OBS interface, SFS interface, and the like in the storage service, the API gateway 2 may integrate the VPC interface, EIP interface, ELB interface, VFW interface, VPN interface, SG interface, and the like in the network service, …, and the API gateway n may integrate the data service. It should be understood that the above example is only used as a specific example, in practical applications, the number of the APIs integrated in the API gateway may be more or less, and the granularity of the APIs integrated in the API gateway may be more or less, and is not limited in detail herein.

It can be understood that the first mode may be applicable to application scenarios with a small number of APIs, the second mode may be applicable to scenarios with a large number of APIs, and a user may perform setting according to actual needs.

The process of table presentation will be described below in conjunction with the table presentation system shown in FIG. 3:

the user enters the data description and the style description on the terminal device. Here, the data description and the style description will be separately introduced in detail.

The DATA description may include an API field and a value (DATA) field. Wherein, the API field may include: interface identification, HTTP method, query parameters, response header fields, and data alias. The interface Identifier may be an interface Uniform Resource Identifier (URI) used to indicate that a user needs to call an API for obtaining Resource data, the HTTP method may be a GET method used to obtain a Resource of a URI instruction, and the query parameter may be any one of marker, limit, page _ reverse, id, content _ id, listener _ id, enable _ whitelist, and whitelist, etc. The response header field is used to describe the field that gets the resource data from the returned response. And the data alias is the identifier of the acquired resource data. The DATA field may include: key, data source, and decoration. The key value is used for describing the resource field needing to be acquired from the acquired resource data. The data source is the data alias in the API field. The modification is used to describe modifications applied to data in the acquired resource field, such as time zone modification, currency modification, standard format time (format time) modification, Universal Unique Identifier (UUID) modification, and the like.

In a specific embodiment, the data description may be represented in JSON format. For example, assuming that a user needs to call three interfaces, i.e. VPC, EIP and ELB, to obtain resource data, the description of the data can be expressed as:

the data description can be input by a user on a data source editing interface of the terminal device, wherein the data source editing interface is a medium for interaction and information exchange between the cloud system and the user, and is used for realizing conversion between an internal form of information and a human-acceptable form. After the data description is input by the user, the terminal equipment performs format check and character missing check on the data description.

The style description may include a title field, a column width field, a column header field, a hint field, a filter field, a explicitly hidden field, a page flip configuration field, a color field, a font field, a center field, an offset field, a hint format field, and a hint location field, among others. Usually, a default style description is stored in the cloud system, and a user only needs to modify the default style description. For example, if the user needs to modify the color of the form, the RGB values of the color fields may be modified in the style description. If the user does not modify the default style description, the cloud system may directly employ the default style description.

In a particular embodiment, the style description may be represented in the JSON format. For example, assuming that the background color of the table is modified to be RGBA (245, 54, 54, 0.9), where the red component has a value of 245, the green component has a value of 54, the blue component has a value of 54, and the transparency is 0.9, the style description can be expressed as:

the style description can be input by a user on a style editing interface of the terminal equipment, wherein the style editing interface is a medium for interaction and information exchange between the cloud system and the user and is used for realizing conversion between an internal form of information and a human-acceptable form. After the style description is input by the user, the terminal equipment performs format check and special character check on the style description.

The terminal device sends the input data description and the style description to the server after acquiring the user input data description and the style description. Accordingly, the server receives the data description and the style description sent by the terminal device.

After receiving the DATA description and the style description, the server parses the DATA description to obtain the API field and the DATA field. The server then generates an HTTP request based on the interface identification, HTTP method, query parameters, and response header fields in the API fields. Then, the server performs Token authentication on the HTTP request. And under the condition that Token authentication passes, the server searches the corresponding API gateway according to the interface identifier in the API field.

And the server sends the HTTP request to the corresponding API gateway. Accordingly, the API gateway receives the HTTP request sent by the server.

After receiving the HTTP request sent by the server, the API gateway acquires the interface identifier, the HTTP method, the query parameter and the response header field from the HTTP request. Then, the API gateway is a GET method according to the HTTP method, so that the server is determined to need to acquire the resource data from the API gateway. Then, the API gateway queries according to the interface identifier and the query parameter to obtain corresponding resource data, and encapsulates the resource data in the HTTP response. Continuing with the example described in the above data, the API gateway identifies "api.pubic. com/VPCs" according to the interface of the VPC interface and the call parameter "marker" of the VPC interface: the '10' calls a VPC interface so as to obtain the VPC resource data, and encapsulates the VPC resource data in a 'VPCs' field in an HTTP response; com/EIPs according to the interface identification "api.pubc. com/EIPs" of the EIP interface, and the call parameter "limit" of the EIP interface: "100" calls the EIP interface, thereby obtaining the resource data of the EIP, and encapsulates the resource data of the EIP in the "publicips" field in the HTTP response; com/ELBs, and the call parameter "marker" of the ELB interface: "10" calls the ELB interface to obtain the ELB's resource data, and encapsulates the ELB's resource data in the "quereyElbs" field in the HTTP response.

The API gateway sends the HTTP response to the server. Accordingly, the server receives the HTTP response sent by the API gateway.

And after receiving the HTTP response sent by the API gateway, the server reads the corresponding resource data from the HTTP response according to the response header field and sets a data alias for the corresponding resource data. Continuing with the example described in the above data as an example, the server obtains the VPC resource data from the VPCs field of the HTTP response according to the VPCs field, and sets an alias "quereyVpcs" for the VPC resource data; acquiring resource data of the EIP from a publics field of the HTTP response according to the publics field, and setting an alias (quereyEips) for the resource data of the EIP; and acquiring the resource data of the ELB from the loadholders field of the HTTP response according to the loadholders field, and setting an alias of 'quereyElbs' for the resource data of the ELB.

Then, the server processes the resource DATA obtained from the HTTP response according to the DATA field, thereby obtaining each column (or row) DATA of the table. Continuing with the example described in the above DATA as an example, the server reads the resource field with the keyword "name" as the DATA of the first column (or row) of the table from the resource DATA with the alias "quereyVpcs" according to the first row in the DATA field; according to a second row in the DATA field, reading a resource field with a key word of 'creation time (creation _ time)' from resource DATA with the alias of 'quereyVpcs' as DATA of a second column (or row) of the table, and performing standard format time modification on the DATA; according to the third row in the DATA field, reading the resource field with the keyword of 'identification (id)' from the resource DATA with the alias of 'quereyVpcs' as the DATA of the third column (or row) of the table, and carrying out UUID decoration on the DATA; according to the fourth row in the DATA field, reading a resource field with a key word of 'IP address (IP _ address)' from the resource DATA with the alias of 'quereyEips' as DATA of the fourth column (or row) of the table; according to the fifth line in the DATA field, reading a resource field with a keyword of price (price) from the resource DATA with the alias of quereyEips as the DATA of the fifth column (or row) of the table, and performing currency modification on the DATA; reading a resource field with a key of 'listener (listener)' from the resource DATA with the alias of 'quereyElbs' according to a sixth row in the DATA field as DATA of a sixth column (or row) of the table; according to the sixth row in the DATA field, the resource field with the key "member" is read from the resource DATA with the alias "quereyElbs" as the DATA of the sixth column (or row) of the table. In a specific embodiment, the effect of extracting the form DATA from the resource DATA obtained from the HTTP response according to the DATA field and processing the form DATA by the server can be as follows:

finally, the server generates a table according to the record pairs of the style descriptions. Continuing with the example of style description above, the server may generate a table as shown in table 1 according to the description pair of style descriptions:

TABLE 1

Also, the table style of the generated table is a table with the background color RGBA (245, 54, 54, 0.9).

The server sends the table to the terminal device. Accordingly, the terminal device receives the table transmitted by the server.

Referring to fig. 5, fig. 5 is a flowchart illustrating a table presenting method provided in the present application. The form presentation method of the present embodiment includes the steps of:

s101: the terminal device obtains the user input data description and the style description. The data description comprises an interface identifier, the interface is used for acquiring resource data, and the style description is used for describing a table style adopted when the resource data is presented.

In a particular embodiment, the DATA description may include an API field and a value (DATA) field. Wherein, the API field may include: interface identification, HTTP method, query parameters, response header fields, and data alias. The interface Identifier may be an interface Uniform Resource Identifier (URI) used to indicate that a user needs to call an API for obtaining Resource data, the HTTP method may be a GET method used to obtain a Resource of a URI instruction, and the query parameter may be any one of marker, limit, page _ reverse, id, content _ id, listener _ id, enable _ whitelist, and whitelist, etc. The response header field is used to describe the field that gets the resource data from the returned response. And the data alias is the identifier of the acquired resource data. The DATA field may include: key, data source, and decoration. The key value is used for describing the resource field needing to be acquired from the acquired resource data. The data source is the data alias in the API field. The modification is used to describe modifications applied to data in the acquired resource field, such as time zone modification, currency modification, standard format time (format time) modification, Universal Unique Identifier (UUID) modification, and the like.

In a specific embodiment, the data description can be input by a user on a data source editing interface of the terminal device, wherein the data source editing interface is a medium for interaction and information exchange between the cloud system and the user, and is used for realizing conversion between an internal form and a human-acceptable form of information. After the data description is input by the user, the terminal equipment performs format check and character missing check on the data description.

In a particular embodiment, the style description may include a title field, a column width field, a column header field, a hint field, a filter field, a explicitly hidden field, a flip configuration field, a color field, a font field, a center field, an offset field, a hint format field, and a hint location field, among others. Usually, a default style description is stored in the cloud system, and a user only needs to modify the default style description. For example, if the user needs to modify the color of the table, the corresponding RGB values may be modified in the style description. If the user does not modify the default style description, the cloud system may directly employ the default style description.

S102: the terminal device transmits the input data description and the style description to the server. Accordingly, the server receives the data description and the style description sent by the terminal device.

S103: and the server analyzes the data description and generates a query request according to the data description.

In a specific embodiment, the query request includes the interface identifier. When the server and the API gateway communicate with each other via an HTTP protocol, the query request may be an HTTP query request, where the HTTP query request carries an identifier of the interface, and the HTTP query request further needs to include: HTTP methods, query parameters, and response header fields, among others. It is understood that when the server and the API gateway communicate with each other via other protocols, the query request may be in other forms, and is not limited in detail herein.

In a specific embodiment, the server parses the DATA description to obtain the API field and the DATA field. The server generates an HTTP request according to the interface identification, the HTTP method, the query parameters and the response header field in the API field. After generating the HTTP request, the server performs Token authentication on the HTTP request.

S104: and the server sends a query request to the API gateway. Correspondingly, the API gateway receives the query request sent by the server.

S105: and the API gateway calls the interface to acquire resource data according to the interface identifier.

In a specific embodiment, the obtained resource data may be carried in the query response. When the server and the API gateway communicate with each other via the HTTP protocol, the query response may be an HTTP response, and the HTTP response carries the acquired resource data.

In a specific embodiment, the API gateway is a GET method according to the HTTP method, thereby determining that the server needs to obtain the resource data from the API gateway. Then, the API gateway queries according to the interface identifier and the query parameter to obtain corresponding resource data, and encapsulates the resource data in the HTTP response.

S106: and the API gateway sends the resource data to the server. Correspondingly, the server receives the resource data sent by the API gateway.

S107: and the server extracts table data from the resource data and organizes and sorts the table data according to the table style to obtain a table.

S108: and the server sends the form to the terminal equipment. Correspondingly, the terminal equipment receives the table sent by the server.

S109: and the terminal equipment presents the table.

For the sake of simplicity, the above table presenting method is not described in detail, and please refer to fig. 1 to 4 and the related description, which are not described herein.

The present application also provides a form presentation system, comprising: terminal equipment, server and API gateway. The terminal equipment is connected with the server, and the server is connected with the API gateway.

Referring to fig. 6, fig. 6 is a block diagram of a structure of an implementation of a terminal device provided in the present application. As shown in fig. 6, the terminal device may include: a host 210, an output device 220, and an input device 230.

The host 210 may be integrated including: one or more processors, a clock module, and a power management module. The clock module integrated in the host 210 is mainly used for generating clocks required for data transmission and timing control for the processor. The power management module integrated in the host 210 is mainly used to provide stable, high-precision voltages to the processor, the output device 220, and the input device 230. The host 210 also incorporates memory for storing various software programs and/or sets of instructions. In particular implementations, the memory may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory may store an operating system, such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory may also store a communication program that may be used to communicate with one or more input devices or output devices. The memory can also store a user interface program, and the user interface program can vividly display the content image of the browser through a graphical operation interface and receive the control operation of a user on the browser through input controls such as a menu, a dialog box and a key. Memory 115 may also store one or more programs. These programs may include: social applications, such as Facebook; image management applications, such as photo albums; map-like applications such as google maps, and the like.

The output device 220 mainly includes a Display, which may include a Cathode Ray Tube (CRT) Display, a Plasma Display Panel (PDP), a Liquid Crystal Display (LCD), and so on. Taking the display as an LCD as an example, the liquid crystal display includes a liquid crystal panel and a backlight module, wherein the liquid crystal panel includes a polarizing film, a glass substrate, a black matrix, a color filter, a protective film, a common electrode, an alignment layer, a liquid crystal layer (liquid crystal, spacer, sealant), a capacitor, a display electrode, a prism layer, and a light scattering layer. The backlight module includes: an illumination light source, a reflection plate, a light guide plate, a diffusion sheet, a brightness enhancement film (prism sheet), a frame, and the like.

The input devices may include a keyboard and a mouse. The keyboard and the mouse are the most common and the most main input devices, English letters, numbers, punctuations and the like can be input into a computer through the keyboard, so that commands, input data and the like are sent to the computer, and the vertical and horizontal coordinate positioning can be quickly carried out through the mouse, so that the operation is simplified. The keyboard may include a Mechanical keyboard, a plastic film keyboard (Mechanical), a conductive rubber keyboard (Membrane), a contactless electrostatic capacitance keyboard (capacities), and the like, and the mouse may include a rolling ball mouse, an optical mouse, a wireless mouse, and the like.

Referring to fig. 7, fig. 7 is a block diagram of a structure of another implementation manner of a terminal device provided in the present application. As shown in fig. 7, the terminal device may include: baseband chip 310, memory 315, including one or more computer-readable storage media, Radio Frequency (RF) module 316, peripheral system 317. These components may communicate over one or more communication buses 314.

The peripheral system 317 is mainly used to implement an interactive function between the terminal device 310 and a user/external environment, and mainly includes an input/output device of the terminal device 300. In a specific implementation, the peripheral system 317 may include: a touch screen controller 318, a camera controller 319, an audio controller 320, and a sensor management module 321. Wherein each controller may be coupled to a respective peripheral device, such as a touch screen 323, a camera 324, audio circuitry 325, and sensors 326. In some embodiments, a gesture sensor of sensors 326 may be used to receive gesture control operations of user input. The pressure sensor of the sensor 326 may be disposed below the touch screen 323, and may be configured to collect a touch pressure applied to the touch screen 323 when a user inputs a touch operation through the touch screen 323. It should be noted that the peripheral system 317 may also include other I/O peripherals.

The baseband chip 310 may integrally include: one or more processors 311, a clock module 312, and a power management module 313. The clock module 312 integrated in the baseband chip 310 is mainly used for generating clocks required for data transmission and timing control for the processor 311. The power management module 313 integrated in the baseband chip 310 is mainly used for providing stable and high-precision voltage for the processor 311, the rf module 36 and peripheral systems.

A Radio Frequency (RF) module 316 for receiving and transmitting radio frequency signals mainly integrates a receiver and a transmitter of the terminal device 300. Radio Frequency (RF) module 316 communicates with a communication network and other communication devices via radio frequency signals. In particular implementations, the Radio Frequency (RF) module 316 may include, but is not limited to: an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chip, a SIM card 3161, a storage medium, and the like. In addition, the radio frequency module can also comprise a WIFI 3162, a Bluetooth and other short-distance wireless communication module. In some embodiments, the Radio Frequency (RF) module 316 may be implemented on a separate chip.

Referring to fig. 8, fig. 8 is a block diagram of a server implementation manner provided in the present application. As shown in fig. 8, the server may include: a first processor 410, a first memory 420, an intelligent network card 430 and a bus 440.

The first processor 410 may be one or more general-purpose processors, wherein a general-purpose processor may be any type of device capable of Processing electronic instructions, including a Central Processing Unit (CPU), a microprocessor, a microcontroller, a host processor, a controller, and an Application Specific Integrated Circuit (ASIC), among others. The first processor 410 executes various types of digitally stored instructions, such as software or firmware programs stored in the first memory 420. In a particular embodiment, the first processor 410 may be an x86 processor or the like. The first processor 410 sends commands to the first memory 420 through the physical interface to accomplish storage related tasks, for example, the first processor 410 may provide commands including read commands, write commands, copy commands, erase commands, and so on. The commands may specify operations related to particular pages and blocks of the first memory 420. As one example, one command may request that data be written to a particular physical page, or another command may request that a particular physical block be erased. Multiple virtual machines may be virtualized within the first processor 410, and a respective operating system may be installed on each virtual machine.

The first Memory 420 may include a Random Access Memory (RAM), a flash Memory (flash Memory), and the like, and may also be a RAM, a Read-only Memory (ROM), a Hard Disk Drive (HDD), or a Solid-state Drive (SSD).

The smart card 430 is also called a Network interface controller, a Network interface card, or a Local Area Network (LAN) adapter. Each intelligent network card 430 has a unique MAC address, which is burned into a read-only memory chip by the manufacturer of the intelligent network card 430 during production. The smart card 430 includes a second processor 431, a second memory 432, and a transceiver 433. The second processor 431 is similar to the first processor 420, however, the performance requirements of the second processor 431 may be lower than the performance requirements of the first processor 420. In a particular embodiment, the second processor 431 can be an ARM processor or the like. The second memory 432 may also be a flash memory, an HDD, or an SDD, and the storage capacity of the second memory 432 may be smaller than that of the first memory 420. The transceiver 433 may be configured to receive and transmit messages and upload the received messages to the second processor 431 for processing. The intelligent network card 430 may further include a plurality of ports, and the ports may be any one or more of three types of interfaces, i.e., a thick cable interface, a thin cable interface, and a twisted pair interface.

Referring to fig. 9, fig. 9 is a schematic structural diagram of an API gateway provided in the present application. The API gateway of the present embodiment includes: a processor 510, a memory 520, a transceiver 530, and a bus 540.

Processor 510 may be one or more general-purpose processors, which may be any type of device capable of Processing electronic instructions, including a Central Processing Unit (CPU), a microprocessor, a microcontroller, a host processor, a controller, and an Application Specific Integrated Circuit (ASIC), among others. Processor 510 executes various types of digitally stored instructions, such as software or firmware programs stored in memory 520. In a particular embodiment, the processor 510 may be an x86 processor or the like. The processor 510 sends commands to the first memory 520 through the physical interface to accomplish storage related tasks, for example, the processor 510 may provide commands including read commands, write commands, copy commands, erase commands, and the like. The commands may specify operations related to particular pages and blocks of the first memory 420. As one example, one command may request that data be written to a particular physical page, or another command may request that a particular physical block be erased. Multiple virtual machines may be virtualized within processor 510, and a respective operating system may be installed on each virtual machine.

The Memory 520 may include a Random Access Memory (RAM), a flash Memory (flash Memory), and the like, and may also be a RAM, a Read-only Memory (ROM), a Hard Disk Drive (HDD), or a Solid-state Drive (SSD). The memory 520 may store an EVS interface, an OBS interface, an SFS interface, and the like, and the API gateway 2 may integrate a VPC interface, an EIP interface, an ELB interface, a VFW interface, a VPN interface, an SG interface, and the like in the network service.

Transceiver 530 may be used to receive and transmit messages and to upload received messages to processor 510 for processing.

It is understood that the terminal device shown in fig. 6 or fig. 7 may perform the steps performed by the terminal device in the table presenting method shown in fig. 5, the server shown in fig. 8 may perform the steps performed by the server in the table presenting method shown in fig. 5, and the API gateway shown in fig. 9 may perform the steps performed by the API gateway in the table presenting method shown in fig. 5, which is not limited in this time.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, memory Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Claims

1. A method of displaying a form, the method comprising:

the server receives the resource data sent by the API gateway, extracts table data from the resource data, and organizes and sorts the table data according to the table style to obtain a table;

and the server sends the form to the terminal equipment.

2. The method of claim 1, wherein the data description comprises an API field and a value field, wherein the API field is used to provide parameters required for obtaining the resource data to an API gateway, the API field comprises an interface identifier of the interface, and the value field is used for the server to rely on to extract the table data from the resource data.

3. The method of claim 2, wherein in the case that the query request is an HTTP request, the API field further comprises: HTTP method, query parameters, response header fields, and data alias.

4. The method of claim 2 or 3, wherein the value field further comprises a key and a data source, the data source being equivalent to the data alias,

the extracting of the table data from the resource number comprises: the server extracts the table data of the key-value index from the resource data indicated by the data source.

5. A method of displaying a form, the method comprising:

6. The method of claim 5, wherein the data description comprises an API field and a value field, wherein the API field is used for providing parameters required for obtaining the resource data to an API gateway, the API field comprises an interface identifier of the interface, and the value field is used for the server to rely on to extract the table data from the resource data.

7. The method of claim 6, wherein in the case that the query request is an HTTP request, the API field further comprises: HTTP method, query parameters, response header fields, and data alias.

8. The method of claim 6 or 7, wherein the value field further comprises a key and a data source, wherein the data source is equivalent to the data alias.

9. A method of displaying a form, the method comprising:

the API gateway sends the resource data to the server.

10. The method of claim 9, wherein the data description comprises an API field and a value field, wherein the API field is used to provide parameters required for obtaining the resource data to an API gateway, the API field comprises an interface identifier of the interface, and the value field is used for the server to rely on to extract the table data from the resource data.

11. The method of claim 10, wherein in the case that the query request is an HTTP request, the API field further comprises: the system comprises an HTTP method, a query parameter, a response header field and a data alias, wherein the resource data are borne in the HTTP response.

12. The method of claim 10 or 11, wherein the value field further comprises a key and a data source, wherein the data source is equivalent to the data alias.

13. A server, comprising: the device comprises a receiving module, an analyzing module, an extracting module and a sending module;

14. The server according to claim 13, wherein the data description includes an API field and a value field, wherein the API field is used to provide an API gateway with parameters required for obtaining the resource data, the API field includes an interface identifier of the interface, and the value field is used for the server to rely on to extract the table data from the resource data.

15. The server according to claim 14, wherein in the case that the query request is an HTTP request, the API field further comprises: HTTP method, query parameters, response header fields, and data alias.

16. The server of claim 14 or 15, wherein the value field further comprises a key and a data source, the data source being equivalent to the data alias,

17. The terminal equipment is characterized by comprising an acquisition module and a sending module;

18. The terminal device according to claim 17, wherein the data description includes an API field and a value field, wherein the API field is used to provide an API gateway with parameters required for obtaining the resource data, the API field includes an interface identifier of the interface, and the value field is used by the server to extract the table data from the resource data.

19. The terminal device according to claim 18, wherein in case that the query request is an HTTP request, the API field further comprises: HTTP method, query parameters, response header fields, and data alias.

20. The terminal device of claim 18 or 19, wherein the value field further comprises a key and a data source, wherein the data source is identical to the data alias.

21. An API gateway, comprising: receiving module, calling module and sending module

the sending module is used for sending the resource data to the server.

22. The API gateway of claim 21, wherein the data description comprises an API field and a value field, wherein the API field is configured to provide parameters required for obtaining the resource data to an API gateway, the API field comprises an interface identifier of the interface, and the value field is configured to be relied upon by the server to extract the table data from the resource data.

23. The API gateway of claim 22 wherein in the case that the query request is an HTTP request, the API fields further comprise: the system comprises an HTTP method, a query parameter, a response header field and a data alias, wherein the resource data are borne in the HTTP response.

24. An API gateway as claimed in claim 22 or claim 23 wherein said value field further comprises a key and a data source, said data source being equivalent to said data alias.

25. A server comprising a memory and a processor executing programs in the memory to run computing services and storage services to perform the method of any of claims 1 to 4.

26. A terminal device comprising a memory and a processor executing a program in the memory to run a computing service and a storage service to perform the method of any of claims 5 to 8.

27. An API gateway comprising a memory and a processor executing a program in the memory to run a computing service and a storage service to perform the method of any of claims 9 to 12.

28. A readable storage medium comprising instructions which, when executed on a server, cause the server to perform the method of any one of claims 1 to 4.

29. A readable storage medium, comprising instructions which, when executed on a terminal device, cause the terminal device to perform the method of any one of claims 5 to 8.

30. A readable storage medium comprising instructions that, when executed on an API gateway, cause the API gateway to perform the method of any of claims 9 to 12.