CN110750711B - Data pushing method, device, computer equipment and storage medium - Google Patents
Data pushing method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110750711B CN110750711B CN201910842161.8A CN201910842161A CN110750711B CN 110750711 B CN110750711 B CN 110750711B CN 201910842161 A CN201910842161 A CN 201910842161A CN 110750711 B CN110750711 B CN 110750711B
- Authority
- CN
- China
- Prior art keywords
- sub
- component
- pushing
- editable
- assembly
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a data pushing method, a device, computer equipment and a storage medium, wherein the data pushing method comprises the following steps: acquiring a data pushing request sent by a client, wherein the data pushing request comprises a user ID; based on the user ID, acquiring a corresponding user role and a history pushing rule; if the state corresponding to the historical push rule is a default state, creating a default push rule corresponding to the user ID based on the user role, wherein the default push rule comprises at least one editable component corresponding to the user role and at least one default push parameter corresponding to each editable component; pushing and displaying the editable components on the current interface based on default pushing parameters corresponding to each editable component; the editable components are hidden or displayed in sequence at the current interface per each current push parameter in the historical push rules. The method ensures that the data push system accords with user preference, provides a more simplified and direct current interface for the user, and improves the information utilization rate.
Description
Technical Field
The present invention relates to the field of internet information display technologies, and in particular, to a data pushing method, a data pushing device, a computer device, and a storage medium.
Background
With the development of information technology and internet technology, people use the internet to perform information retrieval or realize business processes has become a mainstream trend. Most enterprises have deployed their own networks on the internet or APP on intelligent terminals. The vast network information often brings 'information disorientation' to users no matter the network or the APP, and meanwhile, the constant template design of the network or the APP brings inconvenience to users for information review. Because of the different focus of each user, each user has different reference requirements for functional components on the corporate network or APP. How to push interesting information to users and improve the information utilization rate become a problem to be solved urgently.
Disclosure of Invention
The embodiment of the invention provides a data pushing method, a data pushing device, computer equipment and a storage medium, which are used for solving the problem of pushing interested information to a user and improving the information utilization rate.
A data pushing method, comprising:
acquiring a data pushing request sent by a client, wherein the data pushing request comprises a user ID;
based on the user ID, acquiring a corresponding user role and a history pushing rule;
if the state corresponding to the historical push rule is a default state, creating a default push rule corresponding to the user ID based on the user role, wherein the default push rule comprises at least one editable component corresponding to the user role and at least one default push parameter corresponding to each editable component;
Pushing and displaying the editable components on the current interface based on default pushing parameters corresponding to each editable component;
acquiring a parameter editing request, wherein the parameter editing request comprises current push parameters corresponding to default push parameters;
updating default pushing parameters corresponding to the editable component in the historical pushing rules to be current pushing parameters based on the parameter editing request;
the editable components are hidden or displayed in sequence at the current interface per each current push parameter in the historical push rules.
A data pushing apparatus comprising:
the data pushing request comprises a user ID;
the pushing rule acquisition module is used for acquiring corresponding user roles and historical pushing rules based on the user ID;
the pushing rule creating module is used for creating a default pushing rule corresponding to the user ID based on the user role if the state corresponding to the historical pushing rule is a default state, wherein the default pushing rule comprises at least one editable component corresponding to the user role and at least one default pushing parameter corresponding to each editable component;
the pushing editable component module is used for pushing and displaying the editable components on the current interface based on default pushing parameters corresponding to each editable component;
The parameter editing request comprises current push parameters corresponding to default push parameters;
the updating pushing parameter module is used for updating default pushing parameters corresponding to the editable component in the history pushing rule to be current pushing parameters based on the parameter editing request;
and the hiding and editable component module is used for hiding or displaying the editable component in sequence on the current interface according to each current pushing parameter in the history pushing rule.
A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the data pushing method described above when executing the computer program.
A computer readable storage medium storing a computer program which when executed by a processor implements the data push method described above.
According to the data pushing method, device, computer equipment and storage medium, the default pushing parameters corresponding to the editable component can be updated by receiving the parameter editing request sent by the client, the current pushing parameters closer to the client requirement are obtained, the editable component is displayed or hidden according to the current pushing parameters, so that the data pushing system is more in accordance with user preferences, a more simplified and direct current interface is provided for a user, and the information utilization rate is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an application environment of a data pushing method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a data pushing method according to an embodiment of the invention;
FIG. 3 is another flow chart of a data pushing method according to an embodiment of the present invention;
FIG. 4 is another flow chart of a data pushing method according to an embodiment of the present invention;
FIG. 5 is another flow chart of a data pushing method according to an embodiment of the present invention;
FIG. 6 is another flow chart of a data pushing method according to an embodiment of the present invention;
FIG. 7 is another flow chart of a data pushing method according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a data pushing device according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of a computer device in accordance with an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The data pushing method provided by the embodiment of the invention can be applied to an application environment as shown in fig. 1, and is applied to a data pushing system, wherein the data pushing system comprises a client and a server, and the client communicates with the server through a network. The client is also called a client, and refers to a program corresponding to a server and providing local services for the client. The client may be installed on, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, portable wearable devices, and other computer devices. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers.
In an embodiment, as shown in fig. 2, a data pushing method is provided, and the method is applied to the server in fig. 1 for illustration, and specifically includes the following steps:
s10, acquiring a data pushing request sent by a client, wherein the data pushing request comprises a user ID.
Wherein the data push request is a request initiated by the client to the server to push the editable component to the application server, wherein the editable component is a dynamic component associated with the user ID and capable of performing an addition or deletion action, for example, for a financial client, the editable component may include a property component for querying property details, a personal information component for recording login or personal identity information of the financial client, and the like.
The user ID is an identification used by the server to distinguish each client.
In step S10, the server may obtain the user ID based on the data push request, so that preference information corresponding to the user ID may be extracted, and content related to the preference of the user ID may be pushed to the client in time, so that time for loading irrelevant content and network traffic are saved, and information utilization rate is improved.
S20, based on the user ID, acquiring the corresponding user role and the history pushing rule.
The user roles are actively selected by the user to participate in the data pushing system when the user registers in the data pushing system, for example, for the financial data pushing system, the user roles corresponding to the client side comprise a common financial client, a high-grade financial client, a financial counter staff member, a financial loan staff member, a high-grade financial staff member and the like.
The history push rule is a rule that the client sets all editable components that can be displayed on the current interface based on personal preferences, and the position, manner, order, or shielding manner in which each editable component is displayed. It can be appreciated that the data pushing system provides a corresponding default pushing rule for each user role by default, and the client can form a historical pushing rule corresponding to the user ID after performing custom modification based on the default pushing rule.
Specifically, the server may receive a default pushing rule corresponding to a user role and perform user-defined modification on the default pushing rule corresponding to the user role by the client corresponding to the user ID, so as to form a history pushing rule corresponding to the user ID, so that a personalized interface corresponding to the history pushing rule is pushed to the client corresponding to the user ID at the current interface and the subsequent interface. Examples are as follows:
the user role corresponding to the user ID is A, the default pushing rule corresponding to the A comprises a rule 1, a rule 2, a rule 3 and a rule 4, the client can delete the rule 4 and modify parameters in the rule 2 at the same time, and the modified default pushing rule forms a history pushing rule corresponding to the current user ID. Further, a reservation rule which cannot be modified or deleted can be reserved in the default pushing rule so as to maintain the consistency of the whole system and the applicability of the basic functions.
In step S20, the server may timely acquire the corresponding history push rule based on the user ID,
s30, if the state corresponding to the historical push rule is a default state, creating a default push rule corresponding to the user ID based on the user role, wherein the default push rule comprises at least one editable component corresponding to the user role and at least one default push parameter corresponding to each editable component.
Where the editable components are the largest display modules that make up the current interface, it is understood that each editable component may also include sub-components, etc.
The default push parameters are default parameters set for the manner in which the editable component is displayed on the current interface, including component type, display location, content presentation manner, loading order, or masking manner, etc. Specifically, the component type is the type of displayable sub-components included in each editable component, such as a data report, a media player or a website link icon, etc.; for the data report with the component type, the types of the sub-components can comprise a class A report, a class B report, a class C report and the like.
The display position is the specific pixel display position of the editable component on the current interface.
The content display mode is a display mode of a plurality of displayable subassemblies corresponding to different component types. For example, a manner of acquiring a mouse hovering position and magnifying and displaying a website link icon corresponding to the mouse position may be adopted for the plurality of website link icons.
It will be appreciated that in this embodiment, the component type, display location, content presentation mode, loading order, or shielding mode may be set by the client as needed. Meanwhile, the system locks and sets individual parameters in component types, display positions, content display modes, loading orders or shielding modes and the like, namely, the parameters which are locked and set are not modifiable, and the functional availability and the overall style consistency of the system are ensured while the flexibility of the system is reserved.
In step S30, the server provides the default push rule for the client terminal that just created the user role, so that the client terminal can perform personalized setting based on the default push rule, and meanwhile, an editable module based on the user role is obtained, and the function availability and the overall style consistency of the system can be ensured while the flexibility of the system is reserved.
S40, pushing and displaying the editable components on the current interface based on default pushing parameters corresponding to each editable component.
In step S40, the server pushes and displays the editable components on the current interface based on the default pushing parameters corresponding to each editable component, that is, the server displays the default editable components on the current interface for the client of the first login data pushing system based on the user role, so as to provide all the original editable components that can be screened and referenced for the client.
S50, acquiring a parameter editing request, wherein the parameter editing request comprises current push parameters corresponding to default push parameters.
The parameter editing request is a request that the client performs personalized setting based on default pushing parameters corresponding to each editable component to generate current pushing parameters, wherein the pushing parameters can comprise a loading order, a shielding component or a content display mode and the like so as to acquire the current pushing parameters which are more suitable for the requirements of the client.
Specifically, after the client can make a custom modification based on the default loading order, the loadable components which may be frequently used by the client are preferentially displayed on the current interface; the client may set whether to display or mask the editable component at the current interface through the functionality of the mask component.
Preferably, for the locking parameters in the default pushing rule, that is, parameters which cannot be modified or deleted, if the client does not need to be shielded, the current interface is displayed in a concise manner; the client may first determine the component type of the editable component through a content display manner, for example, if the component type is a data report, the client may set a display form of each data report in the editable component to be at least one of a bar graph, a fan graph, a line graph, a histogram, and the like.
In step S50, the server may receive the current push parameters sent by the client and update the default push parameters to meet the diversified and personalized setting requirements of the client, so that the current interface is concise and easy to use.
S60, updating default pushing parameters corresponding to the editable component in the historical pushing rules to be current pushing parameters based on the parameter editing request.
Specifically, the server replaces the current push parameters sent by the client with default push parameters in the original default push rules to form historical push rules, and the state corresponding to the historical push rules is understandably updated at this time.
In step S60, the server synchronously updates the current push parameters obtained after each default push parameter is modified into the history push rule, and as can be understood, when the client logs in again based on the same user ID, the server can load each editable component based on the updated history push rule; meanwhile, the client can set a shielding mode corresponding to a certain editable component in the default pushing parameters as shielding, so that the shielded editable component is hidden in the current interface, the display space of the current interface is saved, the information utilization rate is improved, and the time for loading irrelevant data is saved.
S70, hiding or displaying the editable components in sequence on a current interface according to each current pushing parameter in the history pushing rule.
Specifically, the server displays the current interface according to the history pushing rule corresponding to each editable component, and hides the shielded editable components at the interface; and for the displayable editable component, displaying the current interface according to the updated current pushing parameters and the display sequence set by the editable component.
In step S70, the server may push and display each editable component matching with the client preference on the current interface based on the updated history pushing rule, so as to provide the corresponding interface for the client in a fast and direct manner, and accelerate the loading speed of the system.
In the data pushing method provided by the embodiment, the server can update the default pushing parameters corresponding to the editable component by receiving the parameter editing request sent by the client, obtain the current pushing parameters closer to the client requirement, and display the editable component or hide the editable component according to the current pushing parameters, so that the data pushing system is more in line with the user preference, provides a more simplified and direct current interface for the user, and improves the information utilization rate.
In one embodiment, the editable component includes at least one original sub-component. As shown in fig. 3, before step S10, that is, before the data push request sent by the client is acquired, the data push method specifically further includes the following steps:
s101, acquiring a set building request sent by a client, wherein the set building request comprises a user role, a set requirement and a target nesting mode, and the set requirement comprises at least one sub-set requirement.
Wherein the original sub-component is a base component preset by the server based on one of a plurality of functions corresponding to each user role (each function corresponding to an editable component). For example, for each user role, an editable component of personal information is set, and the editable component comprises a user account information sub-component, a user integration sub-component, a user head portrait sub-component, a user favorites sub-component and the like.
The set-up request is a request for the client to add a sub-component in the corresponding editable component based on the system functionality requirements. The target nesting mode is a selected display mode of the sub-component in the editable component of the current interface, such as displaying according to icons, displaying according to characters or self-ordering according to click quantity.
The sub-component requirement is a request for the server to generate a sub-component corresponding to the editable module.
In step S101, the server may receive the request for building the assembly sent by the client, flexibly add the sub-assembly in the new editable assembly, and enrich the expandability of the system.
S102, processing each sub-assembly requirement by using a modularized algorithm tool to form an original sub-assembly corresponding to the sub-assembly requirement.
The module call algorithm is to call the sub-assembly algorithm which is formed independently, so that the repeated use rate of the algorithm is improved.
Specifically, the server may provide a plurality of saved modules and corresponding module display forms (corresponding modularized algorithms), and select a target module, that is, a modularized algorithm corresponding to the target module, through a selected instruction of the client, call the target module into an area or column corresponding to the subassembly requirement, so as to form an original subassembly corresponding to the subassembly requirement.
In step S102, the server can quickly form the original sub-assembly corresponding to the sub-assembly requirement based on the modularized algorithm, so as to improve the implementation efficiency of the original sub-assembly and the repeated use rate of the algorithm.
S103, according to a target nesting mode, each original sub-assembly is realized in an assembly area on a current interface by adopting a nesting mode algorithm.
Among them, the nested style algorithm (cascading style sheet, cascading Style Sheets) is a computer language for representing file styles such as HTML (an application of standard general markup language) or XML (a subset of standard general markup language). The CSS not only can statically modify the web page, but also can dynamically format each element of the web page in cooperation with various scripting languages. The CSS can accurately control the typesetting of element positions in the webpage at a pixel level, supports almost all font size styles, and has the capability of editing webpage objects and model styles.
In step S103, the server can display each original sub-component in a diversified manner on the current interface according to the target nesting manner, enrich the page display form, and better conform to the user preference.
In steps S101 to S103, the server may accept the request for building the assembly sent by the client, flexibly add the sub-assembly in the new editable assembly, and enrich the scalability of the system. The server can quickly form the original sub-assembly corresponding to the sub-assembly requirement based on the modularized algorithm, and the realization efficiency of the original sub-assembly and the repeated use rate of the algorithm are improved. The server can display each original sub-assembly in a diversified mode on the current interface according to the target nesting mode, enriches the page display form and is more in line with the preference of the user.
In one embodiment, the original subassembly includes a displayable subassembly. As shown in fig. 4, after step S40, that is, after the editable component is pushed and displayed on the current interface, the data pushing method further specifically includes the following steps:
s401, acquiring an update sub-assembly request sent by a client, pushing an editable sub-assembly interface corresponding to an editable assembly based on the update sub-assembly request, wherein the editable sub-assembly interface comprises a displayable sub-assembly area and a sub-assembly area to be selected, and each displayable sub-assembly on the displayable sub-assembly area is arranged and displayed according to loading priority.
Wherein the update sub-component request is a request to request the server to update the display mode of the existing sub-component.
The editable sub-assembly interface is an imaging interface of the manually draggable sub-assembly presented to the client, so that the client can conveniently perform manual operation based on the imaging interface. Preferably, the editable sub-component interface can also provide an algorithm editing interface, so that a high-level editor can quickly edit the preference interface based on the algorithm editing interface.
The displayable subassembly area is an original subassembly displayable at the current interface, and it is understood that the alternate subassembly area is an area that provides all of the original subassemblies.
In step S401, the server may screen and sort the original sub-components on the sub-component area to be selected based on the update sub-component request to form a displayable sub-component that can be on the current interface, and further improve the flexibility of the client to selectively set the current interface.
S402, pushing at least one original sub-component corresponding to the editable component in the sub-component area to be selected based on the user role.
In step 402, the server pushes all original sub-components corresponding to the editable components in the sub-component area to be selected for flexible selection by the client.
S403, acquiring a target sub-component which is sent by the client and is confirmed based on at least one original sub-component and a loading priority corresponding to the target sub-component.
Wherein the loading priority is the order in which the original sub-components are displayed in the editable component of the current interface. The server may default to the component selection order of the client, or may add according to the addition order set by the client.
Specifically, the server defaults to loading priority according to the selection order of the clients, that is, the server pushes each displayable sub-component on the current interface according to the selection order of the clients.
In step S403, the server obtains all original sub-components selected by the client and the loading priorities corresponding to the original sub-components, so that the client can conveniently and timely obtain the common original sub-components on the current interface.
S404, adding the target sub-component to the displayable sub-component area, and/or,
in step S404, the server displays the selected original sub-assembly as a target sub-assembly and the loading priority corresponding to each target sub-assembly on the area where the sub-assembly can be displayed, so that the client can clearly know all the selected target sub-assemblies, and the subsequent interface editing based on the target sub-assemblies is facilitated.
S405, acquiring a sub-component to be deleted, which is sent by the client and is determined based on the displayable sub-component in the displayable sub-component area.
In step S405, the server may further obtain an instruction of the sub-component to be deleted sent by the client, so as to adjust the displayable sub-components that are not related to the client requirement in time, and improve the real-time adjustability of the requirement of each displayable sub-component of the current interface.
S406, deleting the sub-components to be deleted from the displayable sub-component area, and correspondingly adjusting the loading priority corresponding to each of the other displayable sub-components.
In step S406, the server may simply and directly delete the sub-component to be deleted from the displayable sub-component area, that is, the current interface does not display the sub-component to be deleted any more, so as to save the display space of the current interface.
In steps S401 to S406, the server may screen and sort the original sub-components on the sub-component area to be selected based on the update sub-component request to form a displayable sub-component that can be at the current interface, and further improve the flexibility of the client to selectively set the current interface. The server acquires all original subassemblies selected by the client and the loading priorities corresponding to the original subassemblies, so that the client can conveniently and timely acquire common original subassemblies on the current interface. The server takes the selected original sub-assembly as a target sub-assembly and displays the target sub-assembly on the area of the displayable sub-assembly according to the loading priority corresponding to each target sub-assembly, so that the client can clearly know all the selected target sub-assemblies, and the subsequent interface editing based on the target sub-assemblies is facilitated. The server can also acquire an instruction of the sub-assembly to be deleted, which is sent by the client, so as to timely adjust the displayable sub-assemblies which are not related to the requirements of the client at present, and improve the real-time adjustability of the requirements of each displayable sub-assembly of the current interface. The server can simply and directly delete the sub-component to be deleted from the region of the displayable sub-component, namely the current interface does not display the sub-component to be deleted any more, and the display space of the current interface is saved.
In an embodiment, as shown in fig. 5, after step S20, that is, after obtaining the corresponding user role and the history push rule, the data push method further specifically includes the following steps:
s201, if the state corresponding to the history pushing rule is an updated state, acquiring each current pushing parameter in the history pushing rule.
The current push parameters are new parameters which are recorded by the server and are set by the client and meet personal preferences to replace default push parameters.
In step S201, the server reads the current pushing parameters corresponding to all the displayable subassemblies corresponding to each editable subassembly in the history pushing rule, and can obtain the display mode and sequence of each editable subassembly, so that all the editable subassemblies can be generated correspondingly and quickly on the current interface.
S202, the step of hiding or displaying the editable components in sequence on the current interface according to each current pushing parameter in the history pushing rule is executed.
Step S202 is the same as step S70, and is not repeated here.
In step S202, the server may push and display each editable component matching with the client preference on the current interface based on the updated history pushing rule, so as to provide the corresponding interface for the client in a fast and direct manner, thereby accelerating the loading speed of the system.
In steps S201 to S202, the server reads the current pushing parameters corresponding to all the displayable subassemblies corresponding to each editable subassembly in the history pushing rule, and can obtain the display mode and sequence of each editable subassembly, so that all the editable subassemblies can be generated correspondingly and quickly on the current interface. The server can push and display each editable component matched with the preference of the client on the current interface based on the updated history pushing rule, and provide a corresponding interface for the client in a quick and direct mode, so that the loading speed of the system is increased.
In one embodiment, the current interface includes a recommendation sub-component area; the editable component includes at least one displayable sub-component. As shown in fig. 6, after step S70, that is, after each current push parameter in the push rule is hidden or the editable component is displayed in sequence on the current interface, the data push method further specifically includes the following steps:
s701, acquiring a timing task, wherein the timing task comprises task time.
Specifically, the server may implement the timing tasks in jdk (Java Development Kit, software development kit in Java language) in its own library using Timer or scheduledThreadPoolExecutor. The timing task is set as a specific set time (task time), and when the current time of the system reaches the set time, the task of the Timer or the scheduledThreadPoolExecutor can be triggered.
In step S701, the server may periodically adjust the task time of the data push system through the timing task setting, so that the server may make adjustments in time based on the usage habits of the user, so as to better conform to the user preference.
S702, if the current time of the system reaches the task time, counting the corresponding adoption times of each displayable subassembly.
The number of times of adoption is the number of times each displayable subassembly is used by the client in two task times. Specifically, each time the client clicks a displayable subassembly, the server automatically adds 1 to the number of adoption times corresponding to the displayable subassembly. It will be appreciated that after the statistics are completed, the server may zero out the number of applications corresponding to the displayable subassembly.
In step S702, the server may directly read the number of times of adoption corresponding to the displayable subassembly when the current time of the system satisfies the task time, so as to perform subsequent sorting adjustment based on the number of times of adoption.
S703, arranging the sub-assemblies in descending order of the number of the adoption corresponding to each displayable sub-assembly, and obtaining a list of the number of the adoption corresponding to the displayable sub-assembly.
The adoption number list is a descending order list of the corresponding adoption numbers of each displayable subassembly, and the use frequency of each displayable subassembly can be seen in an intuitive ordering mode.
In step S703, the server may form a list of the number of adoption times, and the frequency of use of each displayable subcomponent is visible in an intuitively ordered manner.
S704, taking the top N displayable subassemblies in the adoption number list as target recommendation subassemblies, and pushing the target recommendation subassemblies to a recommendation subassembly area for display.
Specifically, in this embodiment, N may be set to the number of editable components where the displayable sub-components are located on the current interface. For example, the editable component currently corresponds to 6 displayable sub-components, at which point the server may set N to 6.
If ten displayable subassemblies exist on the adoption number list obtained after the server is sequenced, at this time, the server can select the first six subassemblies as target recommendation subassemblies.
In step S704, the server may select a specified number of target recommendation sub-components according to the usage habit of the client to display the target recommendation sub-components on the current interface, and select displayable sub-components with higher usage frequency, so that the client can acquire the target display sub-components in time.
In steps S701 to S704, the server may periodically adjust the task time of the data push system through the timed task setting, so that the server may make adjustments in time based on the usage habits of the user, so as to better conform to the user preference. The server can directly read the number of adoption times corresponding to the displayable sub-assembly when the current time of the system meets the task time, so that the subsequent sorting adjustment is carried out based on the number of adoption times. The server may form a list of the number of adoption times, with the frequency of use of each displayable subcomponent visible in an intuitive ordering manner. The server can select a specified number of target recommendation sub-components to display on the current interface according to the use habit of the client, and select displayable sub-components with higher use frequency, so that the client can acquire the target display sub-components in time.
In one embodiment, as shown in fig. 7, in step S70, each current pushing parameter in the history pushing rule is hidden or displayed in sequence on the current interface, and specifically includes the following steps:
s71, acquiring the component type of the editable component based on the history pushing rule.
Wherein the component type is the type of functionality that the component can provide.
In step S71, the server may read the component type of the editable component based on the history push rule, so as to subsequently continue to receive the parameter settings of the client related to the component type based on the component type.
S72, if the component type is a data report, acquiring a content display mode in a history pushing rule, wherein the content display mode comprises at least one current pushing parameter in a bar graph, a fan graph, a line graph, a stem leaf statistical graph or a histogram.
Specifically, in order to display content on the current interface more intuitively, abundantly or with strong applicability, the server may set different optional content display modes for each data type. For the data report, at least one display mode of a bar graph, a fan graph, a line graph, a stem leaf statistical graph or a histogram is provided, so that a client can conveniently select a proper data display mode based on different application scenes.
In step S72, the server may provide multiple content display modes for the component types of the data report, so that the current interface better meets the personalized requirements of the client.
S73, updating and displaying the data report form on the current interface according to the current pushing parameters.
In step S73, the server may display the current push parameters corresponding to the content display mode selected by the client at the current interface, so that the client may immediately see the use effect, and the method is fast and convenient.
S74, if the component type is a hidden component, hiding the editable component on the current interface, and correspondingly adjusting the positions of all other editable components on the current interface.
In step S74, when the displayable parameters in the current push parameters corresponding to the component types are set to be hidden, the server hides the editable components at the current interface. The setting is applicable to a locking component, for example, a certain locking component is a default component and a deletion component of the system, and is not required for the client temporarily, at this time, the client can set the displayable parameters corresponding to the locking component to be hidden, so as to save the space of the current interface.
In steps S71 to S74, the server may read the component type of the editable component based on the history push rule, so as to continue to receive the parameter settings of the client related to the component type based on the component type. The server can provide various content display modes for the component types of the data report, so that the current interface meets the personalized requirements of the client. The server can instantly display the current push parameters corresponding to the content display mode selected by the client side on the current interface, so that the client side can instantly see the use effect, and the method is quick and convenient. And when the displayable parameters in the current push parameters corresponding to the component types are set to be hidden, the server hides the editable components on the current interface. The setting is applicable to a locking component, for example, a certain locking component is a default component and a deletion component of the system, and is not required for the client temporarily, at this time, the client can set the displayable parameters corresponding to the locking component to be hidden, so as to save the space of the current interface.
In the data pushing method provided by the embodiment, the server can update the default pushing parameters corresponding to the editable component by receiving the parameter editing request sent by the client, obtain the current pushing parameters closer to the client requirement, and display the editable component or hide the editable component according to the current pushing parameters, so that the data pushing system is more in line with the user preference, provides a more simplified and direct current interface for the user, and improves the information utilization rate.
Further, the server can receive the request for building the assembly sent by the client, flexibly add the sub-assemblies in the new editable assembly, and enrich the expandability of the system. The server can quickly form the original sub-assembly corresponding to the sub-assembly requirement based on the modularized algorithm, and the realization efficiency of the original sub-assembly and the repeated use rate of the algorithm are improved. The server can display each original sub-assembly in a diversified mode on the current interface according to the target nesting mode, enriches the page display form and is more in line with the preference of the user.
Further, the server can screen and sort the original sub-components on the sub-component area to be selected based on the update sub-component request to form displayable sub-components which can be on the current interface, and further improve the elasticity degree of the current interface selected and set by the client. The server acquires all original subassemblies selected by the client and the loading priorities corresponding to the original subassemblies, so that the client can conveniently and timely acquire common original subassemblies on the current interface. The server takes the selected original sub-assembly as a target sub-assembly and displays the target sub-assembly on the area of the displayable sub-assembly according to the loading priority corresponding to each target sub-assembly, so that the client can clearly know all the selected target sub-assemblies, and the subsequent interface editing based on the target sub-assemblies is facilitated. The server can also acquire an instruction of the sub-assembly to be deleted, which is sent by the client, so as to timely adjust the displayable sub-assemblies which are not related to the requirements of the client at present, and improve the real-time adjustability of the requirements of each displayable sub-assembly of the current interface. The server can simply and directly delete the sub-component to be deleted from the region of the displayable sub-component, namely the current interface does not display the sub-component to be deleted any more, and the display space of the current interface is saved.
Further, the server reads the current pushing parameters corresponding to all the displayable subassemblies corresponding to each editable subassembly in the history pushing rule, and can acquire the display mode and sequence of each editable subassembly, so that all the editable subassemblies can be generated correspondingly and rapidly on the current interface. The server can push and display each editable component matched with the preference of the client on the current interface based on the updated history pushing rule, and provide a corresponding interface for the client in a quick and direct mode, so that the loading speed of the system is increased.
Further, the server can periodically adjust the task time of the data push system through the timing task setting, so that the server can make adjustment in time based on the use habit of the user, and the user preference is more met. The server can directly read the number of adoption times corresponding to the displayable sub-assembly when the current time of the system meets the task time, so that the subsequent sorting adjustment is carried out based on the number of adoption times. The server may form a list of the number of adoption times, with the frequency of use of each displayable subcomponent visible in an intuitive ordering manner. The server can select a specified number of target recommendation sub-components to display on the current interface according to the use habit of the client, and select displayable sub-components with higher use frequency, so that the client can acquire the target display sub-components in time.
Further, the server may read the component type of the editable component based on the history push rule, so that subsequent parameter settings for the component type of the client continue to be received based on the component type. The server can provide various content display modes for the component types of the data report, so that the current interface meets the personalized requirements of the client. The server can instantly display the current push parameters corresponding to the content display mode selected by the client side on the current interface, so that the client side can instantly see the use effect, and the method is quick and convenient. And when the displayable parameters in the current push parameters corresponding to the component types are set to be hidden, the server hides the editable components on the current interface. The setting is applicable to a locking component, for example, a certain locking component is a default component and a deletion component of the system, and is not required for the client temporarily, at this time, the client can set the displayable parameters corresponding to the locking component to be hidden, so as to save the space of the current interface.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
In an embodiment, a data pushing device is provided, where the data pushing device corresponds to the data pushing method in the foregoing embodiment one by one. As shown in fig. 8, the data pushing apparatus includes an acquire push request module 10, an acquire push rule module 20, a create push rule module 30, a push editable component module 40, an acquire edit request module 50, an update push parameter module 60, and a hide editable component module 70. The functional modules are described in detail as follows:
the acquisition push request module 10 is configured to acquire a data push request sent by a client, where the data push request includes a user ID.
The push rule acquisition module 20 is configured to acquire a corresponding user role and a history push rule based on the user ID.
The create push rule module 30 is configured to create a default push rule corresponding to a user ID based on a user role if a state corresponding to the historical push rule is a default state, where the default push rule includes at least one editable component corresponding to the user role, and at least one default push parameter corresponding to each editable component.
The pushing editable component module 40 is configured to push and display the editable components on the current interface based on default pushing parameters corresponding to each editable component.
The get edit request module 50 is configured to obtain a parameter edit request, where the parameter edit request includes a current push parameter corresponding to a default push parameter.
The update push parameter module 60 is configured to update, based on the parameter editing request, a default push parameter corresponding to the editable component in the history push rule to be a current push parameter.
The hidden editable component module 70 is configured to hide or sequentially display the editable components on the current interface according to each current pushing parameter in the history pushing rule.
Preferably, the data pushing device further comprises an acquisition build request module 101, a formation of an original sub-assembly module 102 and an implementation of the original sub-assembly module 103.
The system comprises an acquisition building request module, a building request module and a storage module, wherein the acquisition building request module is used for acquiring a set building request sent by a client, the set building request comprises a user role, a set requirement and a target nesting mode, and the set requirement comprises at least one sub-set requirement.
And forming an original sub-assembly module, wherein the original sub-assembly module is used for processing each sub-assembly requirement by adopting a modularized algorithm tool to form an original sub-assembly corresponding to the sub-assembly requirement.
And the original sub-assembly module is realized and is used for realizing each original sub-assembly in the assembly area on the current interface by adopting a nested pattern algorithm according to the target nesting mode.
Preferably, the data pushing device further comprises an update acquisition request module, an original sub-component pushing module, an acquisition target component module, an addition target sub-component module, an acquisition sub-component to be deleted module and a deletion sub-component to be deleted module.
The updating request module is used for acquiring an updating sub-assembly request sent by the client, pushing an editable sub-assembly interface corresponding to the editable assembly based on the updating sub-assembly request, wherein the editable sub-assembly interface comprises a displayable sub-assembly area and a sub-assembly area to be selected, and each displayable sub-assembly on the displayable sub-assembly area is arranged and displayed according to the loading priority.
And the pushing original sub-assembly module is used for pushing at least one original sub-assembly corresponding to the editable assembly in the area of the sub-assembly to be selected based on the user role.
The target component obtaining module is used for obtaining the target sub-component confirmed based on the at least one original sub-component and the loading priority corresponding to the target sub-component sent by the client.
An add target subcomponent module for adding target subcomponents to displayable subcomponent areas, and/or,
the module for obtaining the sub-component to be deleted is used for obtaining the sub-component to be deleted, which is sent by the client and is determined based on the displayable sub-component in the displayable sub-component area.
And the module for deleting the sub-components to be deleted is used for deleting the sub-components to be deleted from the displayable sub-component area, and correspondingly adjusting the loading priority corresponding to each of the other displayable sub-components.
Preferably, the data pushing device further comprises a pushing parameter acquisition module and a pushing parameter hiding module.
The push parameter acquisition module is used for acquiring each current push parameter in the history push rule if the state corresponding to the history push rule is an updated state.
And the hidden pushing parameter module is used for executing the step of hiding or displaying the editable component in sequence on the current interface according to each current pushing parameter in the history pushing rule.
Preferably, the data pushing device further comprises a timed task acquisition module, a statistics adoption number module, a acquisition number list module and a pushing recommendation sub-assembly module.
The timing task acquisition module is used for acquiring timing tasks, wherein the timing tasks comprise task time.
And the statistics and adoption number module is used for counting the corresponding adoption number of each displayable subassembly if the current time of the system reaches the task time.
And the acquisition frequency list module is used for arranging the acquisition frequency lists according to the descending order of the adoption frequency corresponding to each displayable subassembly, and acquiring the adoption frequency list corresponding to the displayable subassembly.
And the pushing recommendation sub-assembly module is used for pushing the target recommendation sub-assembly to the recommendation sub-assembly area for display by taking the top N displayable sub-assemblies in the adoption number list as the target recommendation sub-assemblies.
Preferably, the hidden editable component module includes an acquire component type unit, an acquire presentation mode unit, an update data report unit, and a hidden editable component unit.
And the component type obtaining unit is used for obtaining the component type of the editable component based on the history pushing rule.
The display mode obtaining unit is used for obtaining a content display mode in the history pushing rule if the component type is a data report, wherein the content display mode comprises at least one current pushing parameter in a bar graph, a fan graph, a line graph, a stem leaf statistical graph or a histogram.
And the updating data report unit is used for updating and displaying the data report on the current interface according to the current pushing parameters.
And the hidden editable component unit is used for hiding the editable component on the current interface and correspondingly adjusting the positions of all other editable components on the current interface if the component type is the hidden component.
For specific limitations of the data pushing device, reference may be made to the above limitation of the data pushing method, and no further description is given here. The modules in the data pushing device may be implemented in whole or in part by software, hardware, or a combination 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.
In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 9. The computer device includes a processor, a memory, a network interface, and a database 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, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for data related to the data pushing method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a data push method.
In an embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the data pushing method of the above embodiment when executing the computer program, for example, S10 to S70 shown in fig. 2. Alternatively, the processor, when executing the computer program, implements the functions of the modules/units of the data pushing device in the above embodiments, such as the functions of the modules 10 to 70 shown in fig. 8. To avoid repetition, no further description is provided here.
In an embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the data pushing method of the above embodiment, for example, S10 to S70 shown in fig. 2. Alternatively, the computer program, when executed by the processor, implements the functions of the modules/units in the data pushing device in the above-described device embodiments, such as the functions of the modules 10 to 70 shown in fig. 8. To avoid repetition, no further description is provided here.
Those skilled in the art will appreciate that implementing all or part of the above described methods 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 embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments of the present application 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 direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
The above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (7)
1. The data pushing method is characterized by comprising the following steps of:
obtaining a set-up request sent by a client, wherein the set-up request comprises a user role, a set requirement and a target nesting mode, and the set requirement comprises at least one sub-set requirement;
Processing each subassembly requirement by adopting a modularized algorithm tool to form an original subassembly corresponding to the subassembly requirement, wherein the original subassembly comprises a displayable subassembly;
according to the target nesting mode, each original sub-assembly is realized in an assembly area on a current interface by adopting a nesting mode algorithm;
acquiring a data push request sent by a client, wherein the data push request comprises a user ID;
based on the user ID, acquiring a corresponding user role and a history pushing rule;
if the state corresponding to the historical push rule is a default state, creating a default push rule corresponding to the user ID based on the user role, wherein the default push rule comprises at least one editable component corresponding to the user role and at least one default push parameter corresponding to each editable component;
pushing and displaying the editable components on a current interface based on default pushing parameters corresponding to each editable component, wherein the editable components comprise at least one original sub-component;
acquiring a parameter editing request, wherein the parameter editing request comprises a current push parameter corresponding to the default push parameter;
Updating the default pushing parameters corresponding to the editable component in the history pushing rule to be the current pushing parameters based on the parameter editing request;
hiding or displaying the editable component in sequence on the current interface according to each current pushing parameter in the history pushing rule;
wherein, after pushing and displaying the editable component at the current interface, the data pushing method further comprises:
acquiring an update sub-assembly request sent by a client, pushing an editable sub-assembly interface corresponding to the editable assembly based on the update sub-assembly request, wherein the editable sub-assembly interface comprises a displayable sub-assembly area and a sub-assembly area to be selected, and each displayable sub-assembly on the displayable sub-assembly area is arranged and displayed according to loading priority;
pushing at least one original sub-component corresponding to the editable component in the sub-component area to be selected based on the user role;
acquiring a target sub-component which is sent by a client and is confirmed based on at least one original sub-component and a loading priority corresponding to the target sub-component;
adding the target subassembly to the displayable subassembly area, and/or,
Acquiring a sub-component to be deleted, which is sent by a client and is determined based on the displayable sub-component in the displayable sub-component area;
and deleting the sub-component to be deleted from the displayable sub-component area, and correspondingly adjusting the loading priority corresponding to each of the rest displayable sub-components.
2. The data pushing method of claim 1, wherein after the obtaining the corresponding user role and history pushing rule, the data pushing method further comprises:
if the state corresponding to the history pushing rule is an updated state, acquiring each current pushing parameter in the history pushing rule;
and executing the step of hiding or displaying the editable components in sequence on the current interface according to each current pushing parameter in the historical pushing rule.
3. The data pushing method of claim 1, wherein the current interface comprises a recommended subcomponent area; the editable component includes at least one displayable sub-component;
after hiding or displaying the editable components in order at the current interface by each of the current push parameters in the history push rules, the data push method further includes:
Acquiring a timing task, wherein the timing task comprises task time;
if the current time of the system reaches the task time, counting the corresponding adoption times of each displayable subassembly;
arranging according to the descending order of the number of adoption times corresponding to each displayable subassembly, and obtaining a list of the number of adoption times corresponding to the displayable subassemblies;
and pushing the target recommendation sub-assembly to the recommendation sub-assembly area to display, wherein the top N displayable sub-assemblies in the adoption frequency list are used as target recommendation sub-assemblies.
4. The data pushing method according to claim 1, wherein hiding or displaying the editable component in order at the current interface per each of the current push parameters in the history push rule comprises:
acquiring the component type of the editable component based on the history pushing rule;
if the component type is a data report, acquiring a content display mode from the history pushing rule, wherein the content display mode comprises at least one current pushing parameter in a bar graph, a fan graph, a line graph, a stem leaf statistical graph or a histogram;
Updating and displaying the data report on the current interface according to the current pushing parameters;
and if the component type is a hidden component, hiding the editable component on the current interface, and correspondingly adjusting the positions of all the other editable components on the current interface.
5. A data pushing apparatus, comprising:
the method comprises the steps of obtaining a building request module, wherein the building request module is used for obtaining a building request of a component sent by a client, the building request of the component comprises a user role, a component requirement and a target nesting mode, and the component requirement comprises at least one sub-component requirement;
an original sub-assembly module is formed and is used for processing each sub-assembly requirement by adopting a modularized algorithm tool to form an original sub-assembly corresponding to the sub-assembly requirement;
an original sub-assembly realization module for realizing each original sub-assembly in an assembly area on a current interface by adopting a nested pattern algorithm according to the target nesting mode;
the data pushing request comprises a user ID;
the pushing rule acquisition module is used for acquiring corresponding user roles and historical pushing rules based on the user ID;
The pushing rule creating module is used for creating a default pushing rule corresponding to the user ID based on the user role if the state corresponding to the historical pushing rule is a default state, wherein the default pushing rule comprises at least one editable component corresponding to the user role and at least one default pushing parameter corresponding to each editable component;
the pushing editable component module is used for pushing and displaying the editable components on a current interface based on default pushing parameters corresponding to each editable component, and the editable components comprise at least one original sub-component;
the parameter editing request comprises a current push parameter corresponding to the default push parameter;
the updating pushing parameter module is used for updating the default pushing parameter corresponding to the editable component in the history pushing rule to be the current pushing parameter based on the parameter editing request;
the hidden editable component module is used for hiding or displaying the editable components in sequence on the current interface according to each current pushing parameter in the history pushing rule;
The device comprises an update request module, an update request module and a display module, wherein the update request module is used for obtaining an update sub-assembly request sent by a client, pushing an editable sub-assembly interface corresponding to the editable assembly based on the update sub-assembly request, and the editable sub-assembly interface comprises a displayable sub-assembly area and a sub-assembly area to be selected, wherein each displayable sub-assembly on the displayable sub-assembly area is arranged and displayed according to loading priority;
a pushing original sub-assembly module, configured to push, based on the user role, at least one original sub-assembly corresponding to the editable assembly in the sub-assembly area to be selected;
the target component acquisition module is used for acquiring a target sub-component which is sent by a client and is confirmed based on at least one original sub-component and a loading priority corresponding to the target sub-component;
an add target subassembly module for adding the target subassembly to the displayable subassembly area at the loading priority, and/or,
the module for obtaining the sub-component to be deleted is used for obtaining the sub-component to be deleted, which is sent by the client and is determined based on the displayable sub-component in the displayable sub-component area;
and the module for deleting the sub-component to be deleted is used for deleting the sub-component to be deleted from the displayable sub-component area and correspondingly adjusting the loading priority corresponding to each of the other displayable sub-components.
6. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the data pushing method according to any of claims 1 to 4 when executing the computer program.
7. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the data push method according to any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910842161.8A CN110750711B (en) | 2019-09-06 | 2019-09-06 | Data pushing method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910842161.8A CN110750711B (en) | 2019-09-06 | 2019-09-06 | Data pushing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750711A CN110750711A (en) | 2020-02-04 |
| CN110750711B true CN110750711B (en) | 2023-07-28 |
Family
ID=69276064
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910842161.8A Active CN110750711B (en) | 2019-09-06 | 2019-09-06 | Data pushing method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750711B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP7115507B2 (en) * | 2020-04-27 | 2022-08-09 | 横河電機株式会社 | Software development environment providing system, software development environment providing method, and software development environment providing program |
| CN112434198B (en) * | 2020-11-24 | 2024-05-24 | 深圳市明源云科技有限公司 | Chart component recommending method and device |
| CN113806639A (en) * | 2021-10-11 | 2021-12-17 | 郭鹏杰 | Personalized preference adaptation method, device, medium and terminal equipment |
| CN114153963A (en) * | 2021-11-30 | 2022-03-08 | 北京达佳互联信息技术有限公司 | Document recommendation method and device, computer equipment and medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130933A (en) * | 2010-01-13 | 2011-07-20 | 中国移动通信集团公司 | Recommending method, system and equipment based on mobile Internet |
| CN109472670A (en) * | 2018-11-02 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Product data method for pushing, device, computer equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4428952B2 (en) * | 2003-07-14 | 2010-03-10 | キヤノン株式会社 | User interface control apparatus and method |
-
2019
- 2019-09-06 CN CN201910842161.8A patent/CN110750711B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130933A (en) * | 2010-01-13 | 2011-07-20 | 中国移动通信集团公司 | Recommending method, system and equipment based on mobile Internet |
| CN109472670A (en) * | 2018-11-02 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Product data method for pushing, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750711A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110750711B (en) | Data pushing method, device, computer equipment and storage medium | |
| EP3531257B1 (en) | Application interface management method and apparatus | |
| CN108304498B (en) | Webpage data acquisition method and device, computer equipment and storage medium | |
| US11763076B2 (en) | Document applet generation | |
| CN108762760B (en) | Software interface self-defining method, device, computer equipment and storage medium | |
| US10725611B1 (en) | Optimizing presentation of interactive graphical elements based on contextual relevance | |
| CN112016023B (en) | Service processing method, device, terminal and storage medium | |
| US11403653B2 (en) | Distributing electronic surveys via third-party content | |
| US20220417342A1 (en) | System and method for pushing information, and device and storage medium thereof | |
| CN111596911A (en) | Method and device for generating control, computer equipment and storage medium | |
| CN109284488B (en) | Method, device and medium for modifying front-end table column data based on local storage | |
| CN112131837B (en) | Service report configuration method, device, computer equipment and storage medium | |
| CN109040767B (en) | Live broadcast room loading method, system, server and storage medium | |
| CN115098098A (en) | Page generation method, page display method and device | |
| CN110968314A (en) | Page generation method and device | |
| CN109753612B (en) | Questionnaire display control method and device, storage medium and electronic equipment | |
| CN111061532B (en) | Wallpaper display method and terminal equipment | |
| CN115933943A (en) | Image display method and device and storage medium | |
| JP2023067734A (en) | Method for displaying state information, device, apparatus, and storage medium | |
| CN113687809A (en) | Information display method and device, electronic equipment and readable storage medium | |
| CN112861041B (en) | Media content display method and device, electronic equipment and storage medium | |
| US11579755B1 (en) | Dynamic address-based dashboard customization | |
| CN113672829B (en) | Page display method and device, electronic equipment and storage medium | |
| EP4319118A1 (en) | Information interaction method and apparatus, and electronic device | |
| KR102436215B1 (en) | System and method for recommending file based on artificial intelligence |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |