CN112287216B - Information pushing method and device, server and storage medium - Google Patents
Information pushing method and device, server and storage medium Download PDFInfo
- Publication number
- CN112287216B CN112287216B CN202011149299.9A CN202011149299A CN112287216B CN 112287216 B CN112287216 B CN 112287216B CN 202011149299 A CN202011149299 A CN 202011149299A CN 112287216 B CN112287216 B CN 112287216B
- Authority
- CN
- China
- Prior art keywords
- resource
- subscription
- field
- party platform
- determining
- 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
Images
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
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)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses an information pushing method, an information pushing device, a server and a storage medium. When the server is in butt joint with the third party platforms for the first time, resources in the resource pool and a predetermined resource template are obtained, the resources in the resource pool are configured based on the resource template, field metadata and an interface list of the resources are determined, and the subscription relationship between the resource pool and each third party platform is determined according to the required subscription content sent by each third party platform, so that the purpose of configuring the subscription relationship of a plurality of third party platforms in batches can be achieved, the interface of each third party platform does not need to be subjected to customized development, and the effects of reducing development and joint debugging cost are achieved; and further receiving a subscription request sent by the third-party platform, determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation, and pushing field metadata of the target resource to the third-party platform based on an interface list of the target resource so as to achieve the purpose of pushing subscription information in a standardized manner.
Description
Technical Field
The present invention relates to information management technologies, and in particular, to an information pushing method, an information pushing apparatus, a server, and a storage medium.
Background
On the premise that the country encourages and promotes the development of 'internet + medical health', how to stimulate online doctors and inquiry resources as much as possible and how to better provide related services and patients is undoubtedly an industry-level requirement. In the current industry, more and more companies hope to provide high-quality doctor consultation and inquiry services and are reluctant to bear the extra consumption of data collection and storage, and at the moment, third-party services capable of providing professional ability are needed to output.
Generally, resource contents and data forms required by different companies are different, and in the current mode, each pair of third parties needs to develop an interface for subscription contents of the other party, configure a subscription field and push the subscription field to the third party. With this model, each new third party, one after the other, needs to be developed in a customized manner, resulting in repeated and tedious development and joint debugging costs.
Disclosure of Invention
The embodiment of the invention provides an information pushing method, an information pushing device, a server and a storage medium, which are used for carrying out batch configuration on third party platforms when the third party platforms are firstly connected, so that the effect of reducing development and joint debugging cost in the information pushing process is realized.
In a first aspect, an embodiment of the present invention provides an information push method, including:
acquiring resources in a resource pool and a predetermined resource template, configuring the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
determining a subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
receiving a subscription request sent by a third-party platform, and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
and pushing the field metadata of the target resource to the third-party platform based on the interface list of the target resource.
In a second aspect, an embodiment of the present invention further provides an information pushing apparatus, including:
the resource allocation module is used for acquiring resources in a resource pool and a predetermined resource template, allocating the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
the subscription relation determining module is used for determining the subscription relation between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
the target resource determining module is used for receiving a subscription request sent by a third-party platform and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
and the information pushing module is used for pushing the field metadata of the target resource to the third-party platform based on the interface list of the target resource.
In a third aspect, an embodiment of the present invention further provides a server, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing the computer program, implements the information pushing method according to any one of the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor implement the information pushing method according to any one of the first aspect.
According to the technical scheme provided by the embodiment, when the server is connected with the third-party platforms for the first time, the resources in the resource pool and the predetermined resource templates are obtained, the resources in the resource pool are configured based on the resource templates, the field metadata and the interface list of the resources are determined, and the subscription relationship between the resource pool and each third-party platform is determined according to the required subscription content sent by each third-party platform, so that the purpose of configuring the subscription relationships of a plurality of third-party platforms in batches can be achieved, the interface of each third-party platform does not need to be subjected to customized development, and the effects of reducing the development and joint debugging cost are achieved; and further receiving a subscription request sent by the third-party platform, determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation, and pushing field metadata of the target resource to the third-party platform based on an interface list of the target resource so as to achieve the purpose of pushing subscription information in a standardized manner.
Drawings
Fig. 1 is a schematic flowchart of an information push method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a subscription relationship according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of an information pushing method according to a second embodiment of the present invention;
fig. 4 is a data flow, i.e., a core interface call sequence diagram according to a second embodiment of the present invention;
fig. 5 is a flowchart illustrating an information pushing method according to a third embodiment of the present invention;
FIG. 6 is a logic diagram illustrating field metadata update according to a third embodiment of the present invention;
fig. 7 is a schematic structural diagram of an information pushing apparatus according to a fourth embodiment of the present invention;
fig. 8 is a schematic structural diagram of a server according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flow chart of an information pushing method according to an embodiment of the present invention, where the embodiment is applicable to a case where a server and a partner interface for the first time, configure a subscription relationship between a third-party platform and a resource pool, and perform information pushing according to the subscription relationship and a subscription request of the third-party platform, where the method may be executed by an information pushing device, where the device may be implemented by software and/or hardware and is generally integrated in a terminal or a server, and the server may be understood as an information subscription and pushing platform of a service provider. Referring specifically to fig. 1, the method may include the steps of:
s110, resources in the resource pool and a predetermined resource template are obtained, the resources in the resource pool are configured based on the resource template, and field metadata and an interface list of the resources are determined.
The resource pool represents the instantiated content of the resource template and comprises a primary key pool used for storing a primary key list of resources, such as doctor ID and commodity ID. The resources represent data integrated in the resource pool for use by the user. The resource template represents abstract definition of universal resources, such as a doctor template, a commodity template and the like, and mainly comprises field metadata and an interface list. The field metadata indicates which general data content the resource template contains. The interface list includes a full interface that defines the data source for each field in the template and an incremental interface that defines which field changes in the template are to be released by that message interface.
Optionally, interface configuration and field format configuration may be performed on resources in the resource pool based on the resource template. For example, the physician templates in the resource templates include: acquiring corresponding resources from a resource pool according to a doctor template, configuring an interface list of the corresponding resources according to the doctor ID, and configuring field metadata of the corresponding resources according to information such as the work age, the department, the examination fee and the like; for another example, the commodity templates in the resource templates include: and information such as the commodity ID, the commodity function, the commodity price and the like is obtained from the resource pool according to the commodity template, an interface list of the corresponding resource is configured according to the commodity ID, and field metadata of the corresponding resource is configured according to the information such as the commodity function, the commodity price and the like.
Optionally, the server may further determine, based on the content of the third-party platform that needs to be subscribed, a special field that needs to be subscribed by each third-party platform, and configure an expansion interface corresponding to the special field of each third-party platform. Therefore, the server can push the special fields subscribed by the third-party platform to the third-party platform through the expansion interface, and the situation that the third-party platform cannot load the subscribed content is avoided.
And S120, determining the subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform.
Wherein the third party platform refers to a partner, such as dog, hundredth, headline, and ali health, etc. The content to be subscribed can be understood as that the partner subscribes the resource pool concerned by the partner according to the self requirement, and then the server establishes the subscription relationship between the resource pool and each partner according to the content to be subscribed.
Optionally, the determining a subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform includes: determining a third party code corresponding to the third party platform and each resource primary key pool of the resource pool; and determining a corresponding relation between the third-party code and each resource primary key pool based on the required subscription content of each third-party platform, and taking the corresponding relation as the subscription relation.
Specifically explained with reference to the schematic diagram of the subscription relationship shown in fig. 2, each third-party platform corresponds to a unique third-party code (for example, a third-party platform ID), and the server determines the third-party code corresponding to each third-party platform and obtains each resource primary key pool (for example, a primary key ID) in the resource pool; the server analyzes the contents to be subscribed of each third-party platform according to each third-party code, and determines a resource pool subscribed by each third-party platform; and determining the corresponding relation between the third party code and the main key of each resource pool according to the resource pool subscribed by the third party platform, and taking each corresponding relation as the subscription relation between each third party platform and the resource pool to form the subscription relation of < the third party code-resource pool (main key ID) >.
Illustratively, the third-party platforms comprise Ali health, baidu, dog search and headline, the required subscription contents of the Ali health and the Baidu comprise respiratory experts in Hospital with the working age of more than 10 years and special medicines for treating respiratory diseases, the required subscription contents of the dog search and the headline today comprise orthopedic experts in Hospital with the working age of 5-10 years and special medicines for treating orthopedic diseases, and the server determines resource pools subscribed by the third-party platforms according to the required subscription contents of the Ali health, the Baidu, the dog search and the headline respectively and establishes subscription relations among the third-party codes of the third-party platforms and the subscribed resource pools.
It can be understood that, in this embodiment, when the server first connects to the third party platform, the resource in the resource pool may be configured in advance, and the subscription relationship between the resource pool and each third party platform is determined according to the content to be subscribed sent by each third party platform, so that the purpose of configuring the subscription relationships of a plurality of third party platforms in batch may be achieved, and it is not necessary to perform customized development on the interface of each third party platform, thereby achieving the effect of reducing the development and joint debugging costs.
S130, receiving a subscription request sent by the third-party platform, and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation.
The subscription request can be understood as an access request of a third-party platform for the required subscription content. The target resource may be understood as a resource corresponding to a subscription request. Specifically, the server receives a subscription request sent by a third-party platform, determines a third-party code of the third-party platform and a resource pool corresponding to the third-party code according to the subscription request, namely determines a subscription relationship corresponding to the subscription request, configures a subscription field according to the subscription relationship, and determines the configured subscription field as a target resource. For example, the ari health sends a subscription request of a wang doctor of a respiratory specialist to the server, the server determines a code corresponding to the ari health and a resource pool corresponding to the ari health according to the subscription request, namely, determines a subscription relation corresponding to the subscription request sent by the ari health, the server configures a subscription field according to the subscription relation, the subscription field comprises information such as an ID of the ari doctor, a working age, a department and a diagnosis fee, and the subscription field is used as a target resource.
And S140, pushing the field metadata of the target resource to a third-party platform based on the interface list of the target resource.
Optionally, the pushing, to the third party platform, field metadata of the target resource based on the interface list of the target resource includes: and packaging and sending all field metadata of the target resource to the third-party platform based on the full amount of interfaces in the interface list.
Specifically, the server calls a data assembly module to assemble field metadata of the target resource, and pushes the assembled field metadata to the third-party platform through a corresponding interface list so as to push information subscribed by the third-party platform to the third-party subscription platform.
In this embodiment, the subscription relationship is determined through the foregoing steps, the target resource is determined based on the subscription request and the subscription relationship sent by each third-party platform, and the field metadata of the target resource is pushed to the third-party platform through the interface list corresponding to the target resource, so that the purpose of pushing subscription information in a standardized manner can be achieved.
According to the technical scheme provided by the embodiment, when the server is connected with the third-party platforms for the first time, the resources in the resource pool and the predetermined resource templates are obtained, the resources in the resource pool are configured based on the resource templates, the field metadata and the interface list of the resources are determined, and the subscription relationship between the resource pool and each third-party platform is determined according to the required subscription content sent by each third-party platform, so that the purpose of configuring the subscription relationships of a plurality of third-party platforms in batches can be achieved, the interface of each third-party platform does not need to be subjected to customized development, and the effects of reducing the development and joint debugging cost are achieved; and further receiving a subscription request sent by the third-party platform, determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation, and pushing field metadata of the target resource to the third-party platform based on an interface list of the target resource so as to achieve the purpose of pushing subscription information in a standardized manner.
Example two
Fig. 3 is a flowchart illustrating an information pushing method according to a second embodiment of the present invention. The technical scheme of the embodiment adds a new step on the basis of the embodiment. Optionally, the method further comprises: monitoring a change message of at least one resource in the resource pool, and determining a primary key field corresponding to changed field metadata and changed field content according to the change message; and sending the changed field metadata to a corresponding third-party platform based on the primary key field and the subscription relation. Referring specifically to fig. 3, the method of the present embodiment may include the following steps:
s210, resources in the resource pool and a predetermined resource template are obtained, the resources in the resource pool are configured based on the resource template, and field metadata and an interface list of the resources are determined.
S220, determining the subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform.
And S230, receiving a subscription request sent by the third-party platform, and determining the target resource in the resource pool subscribed by the third-party platform based on the subscription request and the subscription relation.
S240, pushing the field metadata of the target resource to a third-party platform based on the interface list of the target resource.
S250, monitoring the change message of at least one resource in the resource pool, and determining the primary key field corresponding to the changed field metadata and the changed field content according to the change message.
Wherein the change message may be a change message of field metadata, and the primary key field may be a primary key ID of the field metadata. Optionally, the determining, according to the change message, a primary key field corresponding to the field metadata that is changed includes: analyzing the change message, and determining the label and the theme of the changed field metadata; based on the label and the theme, inquiring a resource template corresponding to the changed field metadata; and determining the primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata.
The tag can be understood as a category to which field metadata changed belongs, and the subject can be understood as changed content of the field metadata. Specifically, the server analyzes the change message of at least one resource, determines the type and the change content of the field metadata which is changed, determines a corresponding resource template according to the type and the change content of the field metadata, determines a primary key field of the field metadata which is changed according to the universal resource corresponding to the resource template, and further determines the field content after the change according to the primary key field and the theme.
For example, the server monitors a change message of the visit price of a doctor in the resource pool, analyzes the change message, determines that the type of the field metadata corresponding to the change message belongs to the doctor and the change content to the visit price change, determines the corresponding resource template to be the doctor template according to the type of the field metadata and the change content, determines the primary key field to be the doctor ID according to the general resource corresponding to the doctor template, and determines the visit price of the changed doctor according to the doctor ID and the visit price change information.
And S260, sending the changed field metadata to the corresponding third-party platform based on the primary key field and the subscription relation.
Optionally, the sending the changed field metadata to a corresponding third party platform based on the primary key field and the subscription relationship includes: determining a resource pool list comprising the primary key field, and performing parameter mapping on field metadata changed in the resource pool list; based on the subscription fields configured in the subscription relationship, screening field metadata after parameter mapping; and performing value mapping on the screened field metadata, assembling the field metadata after the value mapping, and sending the assembled field to the third-party platform based on the increment interface in the interface list.
Wherein the resource pool list can be understood as a plurality of resource pools including primary key fields of changed field metadata; the parameter mapping may be understood as mapping a parameter in a source operation to a parameter in a target operation. The subscription fields are configured in a subscription relationship, and the subscription fields of the same field metadata can be different; the value mapping may be understood as mapping one value to another value.
Specifically, the changed field metadata may be located in a plurality of resource pools, and by determining a resource pool list including the primary key field, the plurality of resource pools including the changed field metadata may be determined, and parameter mapping is performed on the changed field metadata in the resource pool list to map parameters in the source operation to parameters in the target operation; based on the subscription fields configured in the subscription relationship corresponding to each third-party platform, screening field metadata after parameter mapping to obtain the content subscribed by each third-party platform; and further carrying out value mapping on the screened field metadata, assembling the mapped field metadata, and sending the assembled field to a third-party platform through an increment interface.
Illustratively, a data flow, i.e., core interface call sequence diagram, is shown in FIG. 4. FIG. 4 includes a data source side, a core call module, and a partner. The data source side comprises a plurality of resource pools, such as a search resource pool, an inquiry resource pool, a member resource pool and a doctor pool; the core calling module can be configured in the server, and sequentially performs interface mapping, instance mapping, subscription list determination, parameter mapping, data assembly and interface pushing on resources in the resource pool; the partner is a third party platform and can include dog search, hundredth, headline, ali health and the like. If the doctor's price for visiting is modified, when the server monitors that the doctor's price for visiting is modified, the core calls the module to carry out interface mapping and instance mapping, determine that the main key field of the field metadata which is changed is the doctor ID, the field metadata which corresponds to the doctor ID can be located in an inquiry pool, a member pool and a doctor pool, determine a resource pool list comprising the doctor ID, carry out parameter mapping on the field metadata which is changed in the resource pool list, respectively screen the field metadata which is subjected to parameter mapping according to subscription fields of subscription relations established between different partners and the resource pool, for example, a field of the doctor age is not subscribed by a dog, delete the field of the doctor age which is subjected to parameter mapping according to the subscription relation corresponding to the dog, further carry out value mapping on the screened field metadata, assemble the field metadata which is subjected to value mapping, and send the assembled field to a third-party platform based on an incremental interface in the interface list, namely, the assembled field is pushed to different partners through an interface pushing function.
Optionally, before the parameter mapping is performed on the field metadata that is changed in the target resource pool, the method further includes: determining whether an expansion interface is preconfigured; if yes, obtaining the extension information of the changed field metadata based on the extension interface. By configuring the extension interface, the extension information of the changed field metadata can be pushed to the third-party platform in time, so that the third-party platform can update the changed content in time, and a user can acquire the changed push information in time.
Optionally, before the determining whether to pre-configure the expansion interface, the method further includes: determining whether to push the whole amount of the changed field metadata in the target resource pool; if yes, determining a full amount of interfaces corresponding to the changed field metadata in the interface list, and acquiring the field metadata related to the changed field metadata from the target resource pool based on the full amount of interfaces. By pushing the field metadata related to the changed field metadata to the third-party platform, the third-party platform can update the fields related to the field metadata comprehensively, and the user can acquire more comprehensive information conveniently.
According to the technical scheme provided by the embodiment, after the server is in butt joint with each third-party platform, resources in the resource pool are monitored, if change information of at least one resource in the resource pool is monitored, a primary key field corresponding to changed field metadata and changed field contents are determined according to the change information, and the changed field metadata are sent to the corresponding third-party platform based on the primary key field and the subscription relation, so that the third-party platform can update subscribed contents timely, the problem that in the prior art, if some fields in the resource pool are modified, the interfaces need to be redeveloped and deployed, and then the change information cannot be timely notified to a partner is solved, the change information of the fields can be timely notified to the partner, and a user can obtain latest push information timely. By configuring the extension interface, the extension information of the changed field metadata can be pushed to the third-party platform in time, so that the third-party platform can update the changed content in time, and a user can acquire the changed push information in time. Through with the field metadata that field metadata correlated with taking place the change propelling movement to third party's platform, the third party's platform of being convenient for is to carrying out comprehensive update to the field that is correlated with this field metadata, is favorable to the user to acquire more comprehensive information.
EXAMPLE III
Fig. 5 is a flowchart illustrating an information pushing method according to a third embodiment of the present invention. The technical solution of the present embodiment refines S250 of the above embodiment. Referring specifically to fig. 5, the method of this embodiment may include the following steps:
and S251, monitoring a change message of at least one resource in the resource pool.
S252, analyzing the change message, determining a label and a theme of the changed field metadata, inquiring a resource template corresponding to the changed field metadata based on the label and the theme, determining a primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata, and determining the changed field content according to the primary key field and the theme.
And S253, determining a resource pool list comprising the primary key field.
And S254, determining whether to push the whole amount of the field metadata changed in the target resource pool.
S255, determining a full amount of interfaces corresponding to the changed field metadata in the interface list, and acquiring the field metadata related to the changed field metadata from the target resource pool based on the full amount of interfaces.
And S256, determining whether the expansion interface is configured in advance.
S257, acquiring the expansion information of the changed field metadata based on the expansion interface, and performing parameter mapping on the changed field metadata in the resource pool list.
And S258, screening field metadata after parameter mapping based on the subscription fields configured in the subscription relationship.
S259, performing value mapping on the screened field metadata, assembling the field metadata after the value mapping, and sending the assembled field to a third party platform based on an increment interface in the interface list.
Fig. 6 is a logic diagram of field metadata update, and the steps are exemplarily explained in conjunction with fig. 6. When the price of a doctor in the main station is modified, the resource field is updated, the inquiry platform sends a message queue to the server, and the server monitors and receives the message queue; analyzing the change message, determining a label and a theme of the changed field metadata, inquiring a resource template corresponding to the changed field metadata based on the label and the theme, determining a primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata, determining changed field content according to the primary key field and the theme, and determining a resource pool list comprising the primary key field; determining whether to carry out full pushing on the field metadata changed in the target resource pool, if so, determining a full interface corresponding to the field metadata changed in the interface list, acquiring the field metadata related to the field metadata changed from the target resource pool based on the full interface, and further determining whether to carry out a step of configuring a pre-configured expansion interface, otherwise, directly determining whether to carry out a step of configuring the pre-configured expansion interface; further, if the expansion interface is determined to be configured in advance, acquiring the expansion information of the field metadata which is changed based on the expansion interface, and further executing the step of parameter mapping, otherwise, directly executing the step of parameter mapping; further, based on the subscription fields configured in the subscription relationship, field metadata after parameter mapping is screened, value mapping is performed on the screened field metadata, the field metadata after value mapping is assembled, and the assembled field is sent to a third-party platform based on an increment interface in an interface list so as to push the change information of the field to the third-party platform.
Example four
Fig. 7 is a schematic structural diagram of an information pushing apparatus according to a fourth embodiment of the present invention. Referring to fig. 7, the apparatus includes: the resource configuration module 410, the subscription relationship determination module 420, the target resource determination module 430, and the information push module 440.
The resource configuration module 410 is configured to obtain a resource in a resource pool and a predetermined resource template, configure the resource in the resource pool based on the resource template, and determine field metadata and an interface list of the resource;
a subscription relationship determining module 420, configured to determine a subscription relationship between the resource pool and each third-party platform based on the content required to be subscribed by each third-party platform;
a target resource determining module 430, configured to receive a subscription request sent by a third-party platform, and determine, based on the subscription request and the subscription relationship, a target resource in a resource pool subscribed by the third-party platform;
an information pushing module 440, configured to push, based on the interface list of the target resource, field metadata of the target resource to the third party platform.
On the basis of the foregoing technical solutions, the subscription relationship determining module 420 is further configured to determine a third party code corresponding to the third party platform and each resource primary key pool of the resource pool;
and determining a corresponding relation between the third party code and each resource primary key pool based on the required subscription content of each third party platform, and taking the corresponding relation as the subscription relation.
On the basis of the above technical solutions, the apparatus further includes: an expansion interface configuration module; the extended interface configuration module is used for determining the special fields to be subscribed of the third-party platforms based on the content to be subscribed of the third-party platforms, and configuring the extended interfaces corresponding to the special fields of the third-party platforms.
On the basis of the above technical solutions, the information pushing module 440 is further configured to package and send all field metadata of the target resource to the third party platform based on the full amount of interfaces in the interface list.
On the basis of the above technical solutions, the apparatus further includes: a change information pushing module; the system comprises a resource pool, a change information pushing module, a main key field and a changed field content, wherein the change information pushing module is used for monitoring change information of at least one resource in the resource pool, and determining a main key field corresponding to changed field metadata and changed field content according to the change information;
and sending the changed field metadata to a corresponding third-party platform based on the primary key field and the subscription relation.
On the basis of the technical schemes, the change information pushing module is also used for analyzing the change information and determining the label and the theme of the changed field metadata;
based on the label and the theme, inquiring a resource template corresponding to the changed field metadata;
and determining a primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata.
On the basis of the technical solutions, the change information pushing module is further configured to determine a resource pool list including the primary key field, and perform parameter mapping on metadata of the field changed in the resource pool list;
based on the subscription fields configured in the subscription relationship, screening field metadata after parameter mapping;
and performing value mapping on the screened field metadata, assembling the field metadata subjected to value mapping, and sending the assembled field to the third-party platform based on an increment interface in an interface list.
On the basis of the technical solutions, the change information pushing module is further configured to determine whether to pre-configure the expansion interface;
if yes, acquiring the extension information of the changed field metadata based on the extension interface.
On the basis of the technical solutions, the change information pushing module is further configured to determine whether to push the entire amount of field metadata that is changed in the target resource pool;
if yes, determining a full amount of interfaces corresponding to the changed field metadata in the interface list, and acquiring the field metadata related to the changed field metadata from the target resource pool based on the full amount of interfaces.
According to the technical scheme provided by the embodiment, when the server is connected with the third-party platforms for the first time, the resources in the resource pool and the predetermined resource templates are obtained, the resources in the resource pool are configured based on the resource templates, the field metadata and the interface list of the resources are determined, and the subscription relationship between the resource pool and each third-party platform is determined according to the required subscription content sent by each third-party platform, so that the purpose of configuring the subscription relationships of a plurality of third-party platforms in batches can be achieved, the interface of each third-party platform does not need to be subjected to customized development, and the effects of reducing the development and joint debugging cost are achieved; and further receiving a subscription request sent by the third-party platform, determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation, and pushing field metadata of the target resource to the third-party platform based on an interface list of the target resource so as to achieve the purpose of pushing subscription information in a standardized manner.
EXAMPLE five
Fig. 8 is a schematic structural diagram of a server according to a fifth embodiment of the present invention. FIG. 8 illustrates a block diagram of an exemplary server 12 suitable for use in implementing embodiments of the present invention. The server 12 shown in fig. 8 is only an example, and should not bring any limitation to the function and the scope of use of the embodiment of the present invention.
As shown in FIG. 8, the server 12 is in the form of a general purpose computing device. The components of the server 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by server 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache 32. The server 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8 and commonly referred to as a "hard drive"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set of program modules (e.g., resource configuration module 410, subscription relationship determination module 420, target resource determination module 430, and information push module 440 of an information push device) configured to perform the functions of the various embodiments of the invention.
A program/utility 44 having a set of program modules 46 (e.g., resource configuration module 410, subscription relationship determination module 420, target resource determination module 430, and information push module 440 of an information push device) may be stored, for example, in system memory 28, such program modules 46 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may comprise an implementation of a network environment. Program modules 46 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The server 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with the server 12, and/or with any devices (e.g., network card, modem, etc.) that enable the server 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the server 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the server 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the server 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, implementing an information pushing method provided by an embodiment of the present invention, the method including:
acquiring resources in a resource pool and a predetermined resource template, configuring the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
determining a subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
receiving a subscription request sent by a third-party platform, and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
and pushing the field metadata of the target resource to the third-party platform based on the interface list of the target resource.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement an information pushing method provided by the embodiment of the present invention.
Of course, those skilled in the art can understand that the processor can also implement the technical solution of an information pushing method provided by any embodiment of the present invention.
Example six
Sixth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements an information pushing method provided in an embodiment of the present invention, where the method includes:
acquiring resources in a resource pool and a predetermined resource template, configuring the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
determining a subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
receiving a subscription request sent by a third-party platform, and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
and pushing the field metadata of the target resource to the third-party platform based on the interface list of the target resource.
Of course, the computer program stored on the computer-readable storage medium provided by the embodiments of the present invention is not limited to the above method operations, and may also perform related operations in an information pushing method provided by any embodiments of the present invention.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device.
A computer readable signal medium may be embodied in a resource template, subscription relationship, target resource, etc., having computer readable program code embodied therein. Such propagated resource templates, subscription relationships, target resources, and the like. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It should be noted that, in the embodiment of the information pushing apparatus, the modules included in the embodiment are only divided according to the functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. An information pushing method, comprising:
acquiring resources in a resource pool and a predetermined resource template, configuring the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
determining a subscription relationship between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
receiving a subscription request sent by a third-party platform, and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
pushing field metadata of the target resource to the third-party platform based on the interface list of the target resource;
the information pushing method further comprises the following steps:
monitoring a change message of at least one resource in the resource pool, and determining a primary key field corresponding to changed field metadata and changed field content according to the change message;
based on the primary key field and the subscription relationship, sending the changed field metadata to a corresponding third-party platform;
the determining, according to the change message, a primary key field corresponding to the field metadata that has been changed includes:
analyzing the change message, and determining the label and the theme of the changed field metadata;
based on the label and the theme, inquiring a resource template corresponding to the changed field metadata;
and determining the primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata.
2. The method of claim 1, wherein determining the subscription relationship between the resource pool and each of the third-party platforms based on the required subscription content of each of the third-party platforms comprises:
determining a third party code corresponding to the third party platform and each resource primary key pool of the resource pool;
and determining a corresponding relation between the third party code and each resource primary key pool based on the required subscription content of each third party platform, and taking the corresponding relation as the subscription relation.
3. The method of claim 1, further comprising:
and determining the special fields required to be subscribed by the third-party platforms based on the required subscription content of the third-party platforms, and configuring the expansion interfaces corresponding to the special fields of the third-party platforms.
4. The method of claim 1, wherein pushing field metadata of the target resource to the third party platform based on the interface list of the target resource comprises:
and packaging all field metadata of the target resource and sending the field metadata to the third-party platform based on a full amount of interfaces in an interface list.
5. The method of claim 1, wherein sending the altered field metadata to a corresponding third party platform based on the primary key field and the subscription relationship comprises:
determining a resource pool list comprising the primary key field, and performing parameter mapping on field metadata changed in the resource pool list;
based on the subscription fields configured in the subscription relationship, screening field metadata after parameter mapping;
and performing value mapping on the screened field metadata, assembling the field metadata after the value mapping, and sending the assembled field to the third-party platform based on the increment interface in the interface list.
6. The method of claim 5, wherein prior to parameter mapping the field metadata that changed in the resource pool list, the method further comprises:
determining whether an expansion interface is preconfigured;
if yes, acquiring the extension information of the changed field metadata based on the extension interface.
7. The method of claim 6, wherein prior to the determining whether to pre-configure the expansion interface, the method further comprises:
determining whether to push the changed field metadata in the target resource pool in a full amount;
if yes, determining a full amount of interfaces corresponding to the changed field metadata in the interface list, and acquiring the field metadata related to the changed field metadata from the target resource pool based on the full amount of interfaces.
8. An information pushing apparatus, comprising:
the resource allocation module is used for acquiring resources in a resource pool and a predetermined resource template, allocating the resources in the resource pool based on the resource template, and determining field metadata and an interface list of the resources;
the subscription relation determining module is used for determining the subscription relation between the resource pool and each third-party platform based on the required subscription content of each third-party platform;
the target resource determining module is used for receiving a subscription request sent by a third-party platform and determining a target resource in a resource pool subscribed by the third-party platform based on the subscription request and the subscription relation;
the information pushing module is used for pushing the field metadata of the target resource to the third-party platform based on the interface list of the target resource;
the information pushing device further comprises: a change information pushing module; the system comprises a resource pool, a change information pushing module, a main key field and a changed field content, wherein the change information pushing module is used for monitoring change information of at least one resource in the resource pool, and determining a main key field corresponding to changed field metadata and changed field content according to the change information;
based on the primary key field and the subscription relationship, sending the changed field metadata to a corresponding third-party platform;
the change information pushing module is also used for analyzing the change information and determining the label and the theme of the changed field metadata;
based on the label and the theme, inquiring a resource template corresponding to the changed field metadata;
and determining the primary key field corresponding to the changed field metadata according to the resource template corresponding to the changed field metadata.
9. A server 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 information pushing method according to any one of claims 1-7 when executing the computer program.
10. A storage medium containing computer-executable instructions, which when executed by a computer processor implement the information push method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149299.9A CN112287216B (en) | 2020-10-23 | 2020-10-23 | Information pushing method and device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149299.9A CN112287216B (en) | 2020-10-23 | 2020-10-23 | Information pushing method and device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112287216A CN112287216A (en) | 2021-01-29 |
| CN112287216B true CN112287216B (en) | 2023-02-17 |
Family
ID=74424193
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011149299.9A Active CN112287216B (en) | 2020-10-23 | 2020-10-23 | Information pushing method and device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112287216B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113076153B (en) * | 2021-03-29 | 2023-09-01 | 北京京东振世信息技术有限公司 | Interface calling method and device |
| CN112860631B (en) * | 2021-04-25 | 2021-07-27 | 成都淞幸科技有限责任公司 | Efficient metadata batch configuration method |
| CN113434766B (en) * | 2021-06-30 | 2024-03-22 | 青岛海尔科技有限公司 | Subscription information pushing method and device, storage medium and electronic device |
| CN114531349A (en) * | 2022-02-21 | 2022-05-24 | 山东浪潮通软信息科技有限公司 | Method and device for configuring message subscription |
| CN115988069A (en) * | 2022-12-27 | 2023-04-18 | 中科云谷科技有限公司 | Data pushing method and device and computer storage medium |
| CN118170994A (en) * | 2024-05-15 | 2024-06-11 | 北京搜狐互联网信息服务有限公司 | Resource data processing method and device, storage medium and electronic equipment |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102780680B (en) * | 2011-05-10 | 2017-02-01 | 新浪网技术(中国)有限公司 | Method and system for backcasting data of SNS (Social Network Site) platform |
| CN102902733B (en) * | 2012-09-11 | 2016-12-21 | 北京奇艺世纪科技有限公司 | A kind of information-pushing method based on content subscription, Apparatus and system |
| CN103544323B (en) * | 2013-11-08 | 2017-01-04 | 中国农业银行股份有限公司 | A kind of data-updating method and device |
| US9762527B2 (en) * | 2015-05-26 | 2017-09-12 | International Business Machines Corporation | Following/subscribing for productivity applications |
| CN105338113B (en) * | 2015-11-25 | 2018-06-26 | 北京航空航天大学 | A kind of multi-platform data interconnection system for Urban Data resource-sharing |
| CN107918673B (en) * | 2017-12-12 | 2022-11-04 | 腾讯科技（深圳）有限公司 | Subscription data processing method and device, storage medium and computer equipment |
| CN109246220B (en) * | 2018-09-19 | 2021-08-17 | 南方科技大学 | Message pushing system and method |
| CN109558397B (en) * | 2018-10-30 | 2023-08-22 | 深圳平安医疗健康科技服务有限公司 | Data processing method, device, server and computer storage medium |
| CN111274045B (en) * | 2020-01-14 | 2024-04-16 | 平安银行股份有限公司 | Multi-platform docking method and device, computer equipment and readable storage medium |
-
2020
- 2020-10-23 CN CN202011149299.9A patent/CN112287216B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112287216A (en) | 2021-01-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112287216B (en) | Information pushing method and device, server and storage medium | |
| CN109617646B (en) | Message conversion method and device, computer equipment and computer readable storage medium | |
| CN111190882B (en) | Target template creation method and device, electronic equipment and storage medium | |
| CN112711581A (en) | Medical data verification method and device, electronic equipment and storage medium | |
| US11031112B2 (en) | Emergency department communication system | |
| CN110889013B (en) | Data association method, device, server and storage medium based on XML | |
| CN110598093B (en) | Business rule management method and device | |
| CN112465172A (en) | Hospital intelligent treatment method and device | |
| CN111400381A (en) | Data storage method and device, computer equipment and storage medium | |
| Zhang et al. | Healthcare-based on cloud electrocardiogram system: a medical center experience in middle Taiwan | |
| CN112799760A (en) | Form rendering method and device | |
| CN108154345B (en) | Event scheduling method, device, equipment and storage medium | |
| CN115910265A (en) | Paperless medical record generation method and system for hospital | |
| CN112769975B (en) | Data integration method and device, server and storage medium | |
| CN113919310A (en) | Short message content determination method and device, electronic equipment and storage medium | |
| CN113053531B (en) | Medical data processing method, medical data processing device, computer readable storage medium and equipment | |
| CN114501408A (en) | Diagnosis and treatment data processing method and device, electronic equipment and storage medium | |
| CN113778560B (en) | Method, system, equipment and medium for custom development and execution of hospital treatment process | |
| CN113760317A (en) | Page display method, device, equipment and storage medium | |
| CN112686729B (en) | Product customization method, device, electronic equipment and storage medium | |
| CN111430009B (en) | Method, device, equipment and storage medium for searching protocol matching | |
| US20210165836A1 (en) | Generating cda documents utilizing fhir resources | |
| CN111680867B (en) | Resource allocation method and device and electronic equipment | |
| CN113791762B (en) | Clinical test data conversion method and device, computer equipment and storage medium | |
| CN110289935B (en) | Decoding method, device, terminal and storage medium |
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 |