CN116361590A

CN116361590A - Data component sinking method and device under page assembly

Info

Publication number: CN116361590A
Application number: CN202310313729.3A
Authority: CN
Inventors: 刘豪; 林选伟
Original assignee: Shanghai Shuhe Information Technology Co Ltd
Current assignee: Shanghai Shuhe Information Technology Co Ltd
Priority date: 2023-03-28
Filing date: 2023-03-28
Publication date: 2023-06-30

Abstract

The invention relates to a data component sinking method and device under page assembly. The method comprises the following steps: a data assembly library is established; a page assembling step; a data acquisition step; and generating a page. The invention realizes the sinking of the data assembly under the condition of page assembly, does not need to depend on a specific service system, can uniformly manage, can acquire different contents according to scenes and gray scales, and supports the different requirement changes of a data layer.

Description

Data component sinking method and device under page assembly

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for sinking a data component under page assembly.

Background

In the current internet service, the development of the digitization age is faster and faster, the display of different users in the service is different, most of the service is required to be realized by 'thousands of people and thousands of sides' in the service, and the page with different iterations is required to be iterated as fast as possible in the time. And the page can be broken down into different parts, which we call a UI component. Each component is supported by different data, which we refer to as a data component, except for some components that have no special meaning such as parting lines, etc.

Today, micro-service systems are increasing, and the current data component maintenance approach increases the development cost of the server. No effective solution has been proposed to the above problems.

Disclosure of Invention

Based on the above, it is necessary to provide a method and an apparatus for sinking a data component under page assembly, so as to realize sinking of the data component, and not need to rely on a specific service system, and can perform unified management.

According to a first aspect of the present invention, there is provided a data component sinking method under page assembly, including:

a data assembly library establishing step, namely establishing a data assembly library to store data assemblies;

a page assembly step, namely carrying out page layout, carrying out configuration of UI components in a page, and associating the UI components with corresponding data components;

a data acquisition step, namely acquiring page layout and acquiring corresponding data according to data components associated with UI components in a page;

and generating a page, namely generating a display page according to the page layout, wherein the data in the page comprise corresponding data acquired according to the data component.

In some embodiments, in the step of obtaining data, the manner in which the data component obtains the corresponding data includes obtaining the data through at least one of a service configuration, an API configuration, and a policy configuration.

In some embodiments, in the step of obtaining data, the data component obtains corresponding data in a manner that supports gray scale management, and the data is obtained by configuring gray scales with different granularities for different data components.

In some embodiments, the data components in the data component library are classified according to the service of the data components to form different modules, and the different modules are packaged to form corresponding software packages for reference.

In some embodiments, the UI component associates a plurality of data components, the data components having business attributes, scenes, and corresponding business attributes set according to scene differences.

In some embodiments, the UI component associates corresponding data components, including defining a method for the data components, adding corresponding annotations to the method, the annotations defining two attributes: and mapping and taking out the relation of the UI component and the data component by reading the annotation.

According to a second aspect of the present invention, there is provided a data component sinking apparatus under page fitting, comprising:

the data component library establishing module is used for establishing a data component library to store data components;

the page assembly module is used for carrying out page layout, configuring UI components in the page and associating the UI components with corresponding data components;

the data acquisition module is used for acquiring page layout and acquiring corresponding data according to the data components associated with the UI components in the page;

the page generation module is used for generating a display page according to the page layout, and the data in the page comprise corresponding data acquired according to the data component.

According to a third aspect of the present invention there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterised in that the processor implements the steps of any of the methods of the embodiments described above when the computer program is executed by the processor.

According to a fourth aspect of the present invention there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of any of the methods of the embodiments described above.

By implementing the scheme of the invention, the following beneficial effects can be obtained:

1. and establishing a data component library for storing the data components, wherein the data component library is an independent item and is referenced through codes of the data component library. Sinking the data component, promoting the rapid iteration of the service, and keeping the data essence unchanged. The development cost of the server is saved, the sinking of the data components can be managed uniformly, the full quantity control components can be intuitively controlled, and the corresponding content can be rapidly screened out.

2. The data can acquire different contents according to the scene and gray scale, support different demand changes of a data layer, assist business iteration of enterprises, and can quickly generate different display pages according to different users so as to achieve thousands of people and thousands of faces.

Drawings

FIG. 1 is a flow chart of some embodiments of a data component sinking method under page assembly of the present invention;

FIG. 2 is a schematic diagram of a data component model of some embodiments of the invention;

FIG. 3 is a flow chart of further embodiments of a data component sinking method under page assembly of the present invention;

FIG. 4 is a schematic diagram of some embodiments of a data component sink apparatus under page assembly of the present invention;

FIG. 5 is an internal block diagram of a computer device for implementing some embodiments of the invention.

Detailed Description

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terms used herein should be construed to have meanings consistent with their meanings in the context of the specification and relevant art and are not to be construed in an idealized or overly formal sense unless expressly so defined herein.

Before describing the specific details of the present application, the meaning of the terms that will be used in the present application will be briefly described.

UI component, data component: one page may be broken down into different parts, called UI components. Each component is supported by different data, except for some non-specifically defined, e.g., split lines, etc., which are obtained by the data component.

And (3) routing: routing refers to the network-wide process of determining an end-to-end path as a packet travels from a source to a destination. In the network domain, different routing policies determine end-to-end path differences. The design concept can also be introduced in the credit field, and refers to a series of decision set combinations, and the core is the process of different customer funds distribution strategies from end to end.

FIG. 1 illustrates a flow chart of some embodiments of a data component sinking method under page assembly of the present invention.

As shown in fig. 1, the method includes:

a data component library establishing step S102, wherein a data component library is established to store data components;

step S104 of page assembly, performing page layout, performing configuration of UI components in the page, and associating the UI components with corresponding data components;

a data acquisition step S106, namely acquiring page layout and acquiring corresponding data according to data components associated with UI components in the page;

and a page generation step S108, wherein a display page is generated according to the page layout, and the data in the page comprises corresponding data acquired according to the data component.

In some of these embodiments, the database creation step S102 includes: a data component library is newly added, and the data component related service is specially stored. The data assembly library establishes different modules according to different services. For example: borrowing, repayment, application and general module, wherein the general module stores general components. For the selection frame of the UI component, the data selection frame corresponds to a borrowing route selection (borrowing party, amount, period, etc.) in the borrowing service. Different modules may be packaged to form corresponding software packages for reference.

In some of these embodiments, the page assembly step S104 associates the UI components with corresponding data components, including: a data component is defined, and a corresponding UI component is associated. The selection box for the UI component, defined as ui_common_select, is used for different business aspects of gender, academic, occupation, income, etc. For each data Component, a method is defined, and for each method, a corresponding annotation Component is added, the annotation defining two attributes, a UI Component name type and a data Component name dataType.

For example: revenue data Component, definition @ Component (type= "ui_common_selec T", datatype= "biz_common_select_income"); an academic component, defining @ Co mpoent (type= "ui_common_select", datatype= "biz_common_sele ct_output"); and reading each annotation when the service is started, and taking out the mapping of the corresponding relation.

FIG. 2 illustrates a schematic diagram of a data component model in accordance with some embodiments of the invention. As shown in fig. 2: for UI component A, there may be biz_A1 (e.g., academic), biz_A2, and biz_A3 for the data component that we correspond to; while the same data component biz_a1 has business attributes such as: a11 (e.g., revenue), A12, A13; while a data component may have scenarios such as: the three scenes of the scene1 (such as an application page), the scene2 and the scene3 are set with corresponding values according to different scenes.

In some embodiments, the data component in the data obtaining step S106 obtains the corresponding data by:

service configuration: in the implementation method of each data component, if the service data configuration is needed to acquire data, the configuration is formulated in the code, the configuration content is read, and the corresponding data can be modified by post-production personnel at the operation interface.

API configuration: in the implementation method of each data component, if the data is required to be acquired by a three-party system, calling an interface of a corresponding service in a code to acquire the data, and finally assembling.

Policy configuration: in the implementation method of each data component, if the policy configuration is required to acquire data, the policy is called, the content of the policy return is read, and the corresponding data can be increased or decreased and modified by post-production personnel at the policy operation interface.

The three cases all comprise gray level management, gray levels with different granularity can be configured according to the requirement, and corresponding data are finally aggregated (different gray levels are set according to different users).

According to the invention, in the micro-servitization system, the application service system can refer to the application module and the universal module content in the data component library to support the corresponding service. If the components are updated, corresponding data components are required to be created in a data component library, and then the corresponding jar packets are updated in a common way by other service systems to realize the decoupling of the corresponding services.

FIG. 3 illustrates a flow chart of further embodiments of a data component sinking method under page assembly of the present invention.

As shown in fig. 3: firstly, acquiring a layout, and triggering according to clicking actions of a user on an APP; then acquiring a page flow, and acquiring an executable page flow (such as first walking A page and then walking B page) based on the user request parameters; then, obtaining a page, wherein the last node selects a page flow, and the page flow is currently executed to obtain the page which should be presented to the user (for example, the first entering flow is A page); then acquiring page layout, acquiring page layout of a page to be presented to a user, and acquiring data in the modes of service configuration, strategy configuration, interface acquisition and the like through an analysis data component; and finally, constructing the guest layout by using the obtained data, and presenting the page to the user.

FIG. 4 illustrates a schematic diagram of some embodiments of a data component sink apparatus under page assembly of the present invention.

As shown in fig. 4, the data component sinking device under page assembly in the embodiment includes:

a data component library creation module 100 for creating a data component library to store data components;

the page assembly module 200 is used for carrying out page layout, configuring UI components in a page, and associating the UI components with corresponding data components;

the data acquisition module 300 is configured to acquire a page layout, and acquire corresponding data according to a data component associated with a UI component in the page;

the page generating module 400 is configured to generate a presentation page according to the page layout, where the data in the page includes corresponding data obtained according to the data component.

In some embodiments, in the data acquisition module, the data component acquires the corresponding data by at least one of service configuration, API configuration, and policy configuration.

In some embodiments, in the data acquisition module, the data component acquires corresponding data in a manner that supports gray scale management, and the data is acquired by configuring gray scales with different granularities for different data components.

In some embodiments, the UI component associates a plurality of data components, wherein the data components have service attributes and scenes, and the corresponding service attributes are set according to different scenes.

In some of these embodiments, the UI component associates the corresponding data component, including defining a method for the data component, adding to the method a corresponding annotation defining two attributes: and mapping and taking out the relation of the UI component and the data component by reading the annotation.

For a specific definition of the data component sinking device under page assembly, reference may be made to the definition of the data component sinking method under page assembly hereinabove, and the description thereof will not be repeated here. The above-mentioned respective modules in the data component sinking apparatus under page assembly may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

The invention also provides a computer device, which can be a terminal, and the internal structure diagram of the computer device can be shown in fig. 5. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by the processor, implements the page-assembled data component sinking method described above. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like. It will be appreciated by those skilled in the art that the structure shown in FIG. 5 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

The invention also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the above-described page-mounted data assembly sinking method.

Those skilled in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the method embodiments described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus (Rambus), direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.

Thus, embodiments of the present invention have been described in detail. In order to avoid obscuring the concepts of the invention, some details known in the art have not been described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.

While certain specific embodiments of the invention have been described in detail by way of example, it will be appreciated by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the invention. It will be understood by those skilled in the art that the foregoing embodiments may be modified and equivalents substituted for elements thereof without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.

Claims

1. A method for sinking a data component under page assembly, comprising the steps of:

2. The method of sinking data components of claim 1,

in the step of data acquisition, the data component acquires the corresponding data in a manner including acquiring the data through at least one of service configuration, API configuration and policy configuration.

3. The method of sinking data components of claim 1,

in the data acquisition step, the data acquisition mode of the data components supports gray level management, and data are acquired by configuring gray levels with different granularities for different data components.

4. The method of sinking data components of claim 1,

and the data components in the data component library are classified according to different services of the data components to form different modules, and the different modules are packed to form corresponding software packages for reference.

5. The method of sinking data components of claim 1,

the UI component is associated with a plurality of data components, the data components have service attributes and scenes, and the corresponding service attributes are set according to different scenes.

6. The method of sinking data components of claim 1,

the associating the UI components with the corresponding data components comprises: a method is defined for each data component, and a corresponding annotation is added to each method, the annotation defining two attributes: and mapping and taking out the relation of the UI component and the data component by reading the annotation.

7. A data component sinking apparatus under page assembly, comprising:

8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1 to 6 when the computer program is executed by the processor.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.