阅读说明：本技术 跨应用系统的信息传递方法及系统 (Information transmission method and system of cross-application system ) 是由 周万 于 2021-07-26 设计创作，主要内容包括：本发明涉及一种跨应用系统的信息传递方法及系统,属于信息传递技术领域,该方法及系统通过设置共享数据库,各目标系统均与共享数据库相连,使得共享数据库记录所有目标系统之间通信的消息内容,从而使得在出现问题时,用户可以调取共享数据库中记录的消息内容进行查看,精准定位问题点,提升问题处理时效。(The invention relates to an information transmission method and an information transmission system of a cross-application system, which belong to the technical field of information transmission.)

1. An information delivery system across application systems, comprising: the system comprises a shared database, a calling module and a plurality of target systems; the target systems are respectively connected with the shared database; the calling module is connected with the shared database;

the shared database is used for receiving and storing context content operated by each target system, and the context content comprises: at least one of information of a message originator target system, information of a message recipient target system, and a message timestamp;

the calling module is used for receiving a calling request, and calling corresponding context content in the shared database according to the calling request so as to enable a user to check the context content.

2. The information delivery system of claim 1, wherein the target system comprises: the system comprises a portal system, a supply and demand system, a work order system and a directory system;

the portal system is used for generating service list information and writing the service list information into the shared database as context information;

the supply and demand system is used for generating a demand sheet according to the service sheet information, performing demand circulation according to the demand sheet, issuing work order information to the work order system, and writing the work order information into the shared database as context; the work order information comprises a service order number, a demand number and demand content;

the work order system is used for processing the work order information, creating and managing the work order, displaying a corresponding work order processing page according to the operation of a user so that the user can process the work order, and writing the action process information of the whole work order system into the shared database as context;

and the directory system is used for acquiring the context information, cataloging according to the context information to obtain a cataloging result, and writing the cataloging result into the shared database.

3. The information delivery system according to claim 2, wherein the portal system is configured to generate a service ticket, number the service ticket to obtain numbered service ticket information, and write the service ticket information as context information into the shared database.

4. The information delivery system of claim 2, wherein the supply and demand system is configured to invoke a work order API interface to issue work order information.

5. The information delivery system of claim 2, wherein the work order system is configured to generate an inventory sub-process based on the work order information and assign a work order ID to each work order; and generating a to-do message and a to-do work order.

Technical Field

The invention belongs to the technical field of information transmission, and particularly relates to an information transmission method and system of a cross-application system.

Background

In the context of big data, in order to process data, a data service system is usually constructed, for example, a system of governance of government data and a service platform constructed by numerous big data offices currently, and a general data service system architecture may include the following subsystems: the system comprises a basic supporting platform, a trusted sharing platform, a big data basic platform, a data directory system, a data map system, a data resource pool, a supply and demand scheduling system, a data asset management platform, a data resource portal and the like.

In the existing data service system, message interaction among subsystems is frequent, coupling is tight, and each subsystem is developed by different software manufacturers, and when problems occur in the process of system joint debugging and operation, problem information is difficult to track and position, so that the problem processing timeliness is poor.

Disclosure of Invention

The invention provides an information transmission method and an information transmission system of a cross-application system, which effectively solve the technical problems that problem information is difficult to locate and problem processing timeliness is poor in the prior art.

The technical scheme provided by the invention is as follows:

in one aspect, a cross-application information delivery method is applied to a cross-application information delivery system including a shared database and a plurality of target systems, and the method includes:

based on the shared database, receiving and storing context content of each target system operation, wherein the context content comprises: at least one of information of a message originator target system, information of a message recipient target system, and a message timestamp;

and receiving a calling request, and calling corresponding context content in the shared database according to the calling request so as to enable a user to check the context content.

In yet another aspect, an information delivery system across application systems includes: the system comprises a shared database, a calling module and a plurality of target systems; the target systems are respectively connected with the shared database; the calling module is connected with the shared database;

the shared database is used for receiving and storing context content operated by each target system, and the context content comprises: at least one of information of a message originator target system, information of a message recipient target system, and a message timestamp;

the calling module is used for receiving a calling request, and calling corresponding context content in the shared database according to the calling request so as to enable a user to check the context content.

Optionally, the target system includes: the system comprises a portal system, a supply and demand system, a work order system and a directory system;

the portal system is used for generating service list information and writing the service list information into the shared database as context information;

the supply and demand system is used for generating a demand sheet according to the service sheet information, performing demand circulation according to the demand sheet, issuing work order information to the work order system, and writing the work order information into the shared database as context; the work order information comprises a service order number, a demand number and demand content;

the work order system is used for processing the work order information, creating and managing the work order, displaying a corresponding work order processing page according to the operation of a user so that the user can process the work order, and writing the action process information of the whole work order system into the shared database as context;

and the directory system is used for acquiring the context information, cataloging according to the context information to obtain a cataloging result, and writing the cataloging result into the shared database.

Optionally, the portal system is configured to generate a service ticket, number the service ticket to obtain service ticket information with a number, and write the service ticket information as context information into the shared database.

Optionally, the supply and demand system is configured to call a work order API interface and issue work order information.

Optionally, the work order system is configured to generate an inventory sub-process according to the work order information, and allocate a work order ID to each work order; and generating a to-do message and a to-do work order.

The invention has the beneficial effects that:

according to the information transmission method and system of the cross-application system, the shared database is arranged, and all target systems are connected with the shared database, so that the shared database records the message content of communication among all target systems, and therefore when a problem occurs, a user can call the message content recorded in the shared database to check, the problem point is accurately positioned, and the problem processing timeliness is improved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic flowchart of an information delivery method across application systems according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of an information delivery system of a cross-application system according to an embodiment of the present invention.

Reference numerals: 21-a target system; 22-shared database; 23-calling module; 211-a portal system; 212-supply and demand systems; 213-work order system; 214-directory system.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.

In order to at least solve the technical problem proposed in the present invention, an embodiment of the present invention provides an information transfer method across application systems.

Fig. 1 is a schematic flowchart of an information transfer method across application systems according to an embodiment of the present invention, and referring to fig. 1, the method according to the embodiment of the present invention is applied to an information transfer system across application systems including a shared database and a plurality of target systems, and the method according to the embodiment of the present invention may include the following steps:

s11, based on the shared database, receiving and storing the context content of each target system operation, the context content includes: at least one of information of a message originator target system, information of a message recipient target system, and a message timestamp;

and S12, receiving the calling request, and calling the corresponding context content in the shared database according to the calling request so as to enable the user to check the context content.

In a specific implementation process, any one of the information delivery systems across application systems, which is provided with a shared database and includes a plurality of target systems, may be defined as the information delivery system across application systems of the present application, and the information delivery method across application systems provided by itself is applied in the information delivery system across application systems of the target.

For example, each target system writes the context content into the shared database respectively during operation, so that when each system has a problem, a user can call the corresponding context content through the shared database to check the context content. The user can send a calling request, so that corresponding context content is called, problem points are accurately positioned, problems are quickly solved, and responsibility division is well performed.

According to the information transmission method of the cross-application system, the shared database is arranged, and all target systems are connected with the shared database, so that the shared database records the message content of communication among all target systems, and therefore when a problem occurs, a user can call the message content recorded in the shared database to check, accurately locate the problem point and improve the problem processing timeliness.

Based on a general inventive concept, the embodiment of the present invention further provides an information delivery system across application systems.

Fig. 2 is a schematic structural diagram of an information delivery system of a cross-application system according to an embodiment of the present invention, and as shown in fig. 2, the system according to the embodiment of the present invention may include the following components: a shared database 22, a calling module 23 and a plurality of target systems 21; the plurality of target systems 21 are respectively connected with the shared database 22; the recall module 23 is connected to the shared database 22. The shared database 22 is configured to receive and store context content of each target system, where the context content includes: at least one of information of a message originator target system, information of a message recipient target system, and a message timestamp; the retrieving module 23 is configured to receive a retrieving request, and retrieve, according to the retrieving request, corresponding context content from the shared database, so that the user can view the context content.

With regard to the system in the above-described embodiment, the specific manner in which each portion performs operations has been described in detail in relation to the embodiment, and will not be set forth in detail herein.

On the basis of the foregoing embodiment, optionally, the target system includes: portal system 211, supply and demand system 212, work order system 213, and directory system 214. The portal system 211 is configured to generate service ticket information, and write the service ticket information as context information into the shared database. The supply and demand system 212 is used for generating a demand sheet according to the service sheet information, performing demand circulation according to the demand sheet, issuing work sheet information to the work sheet system, and writing the work sheet information into the shared database as context; and the work order information comprises a service order number, a demand number and demand content. And the work order system 213 is used for cataloging the work order information, displaying a corresponding work order processing page according to the operation of the user, so that the user can process the work order, and writing the action process information of the whole work order system into the shared database as context. And the directory system 214 is configured to obtain the context information, perform cataloging according to the context information to obtain a cataloging result, and write the cataloging result into the shared database.

Optionally, the portal system is configured to generate a service ticket, number the service ticket to obtain service ticket information with a number, and write the service ticket information as context information into the shared database.

For example, the gateway system 211 may generate a service ticket after each portal initiates a demand, assign a number to the service ticket, and write the information as context information into the shared database. Wherein, the user can put forward the own requirement through the portal.

Optionally, the supply and demand system is configured to call a work order API interface and issue work order information.

For example, the supply and demand system 212 may generate a demand sheet after being started, and issue an inventory task in the process of demand circulation. At this time, the supply and demand system 212 calls the work order API interface to issue, transfers information such as the service order number, the demand number, and the demand content (e.g., marital-related data items), and writes the information into the shared database.

In some embodiments, optionally, the work order system is configured to generate an inventory sub-process according to the work order information, and allocate a work order ID to each work order; and generating a to-do message and a to-do work order.

For example, after the supply and demand system issues the work order, the work order system may receive and process the work order, and the specific receiving and processing process may be: generating cataloging sub-processes and cataloging process node examples, and distributing a work order ID for each work order; adding a new catalogued work order into the work order list; sending a notification message to a responsibility department to catalog responsible persons to form a to-be-handled message and a to-be-handled work order; and uniformly managing the context information of each work order, and indexing by using the service ID and the work order ID.

The work order system can also dispatch the cataloging tasks, and the specific dispatching processing flow can be as follows: and displaying a work order processing operation menu to a user: processing, delegation, assignment, shutdown, evaluation, etc.; the system tracks and displays the processing process of the work order, the response time, the total duration and other information, and sends early warning information to the work order which is about to exceed the period.

The user can also carry out a work order system, check a list of work orders to be processed under the name of the user, and carry out operations such as processing, delegation, assignment, closing, evaluation and the like. For example, in "processing", the user may click a processing button to call up a corresponding work order processing page to perform processing.

For example, the directory system may read context content, perform form display of content to be catalogued, perform a cataloguing process, write back a processing result to shared data after the cataloguing process is completed, and notify the work order system that the cataloguing task is completed.

In this embodiment, the work order system may further send a message to the supply and demand system, carrying the service ID, the work order ID, and the processing result context information (e.g., directory code, directory name). The supply and demand system can also automatically associate the catalogue with the demand sheet.

According to the information transmission system of the cross-application system, the shared database is arranged, and each target system is connected with the shared database, so that the shared database records the message content of communication among all target systems, and therefore when a problem occurs, a user can call the message content recorded in the shared database to check, accurately locate the problem point and improve the problem processing timeliness.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.

It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present invention, the meaning of "a plurality" means at least two unless otherwise specified.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.

In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.