CN101009002A - Method and system for realizing data sharing between isomer systems - Google Patents

Abstract

The present invention provides a method and system for realizing data sharing between heterogeneous systems. The application system sends a query request to the processing system, and the processing system extracts the user's source data according to the received query request, and then sends it to the application system. The application system Convert the received source data into target data and provide it to the user. There is no need to set the storage space for the purpose data in the processing system, which reduces the cost of the storage device, and the data transfer between the processing system and the application system does not require manual intervention, which reduces the cost of maintenance personnel, thereby reducing the cost of The cost required for data sharing between heterogeneous systems. In addition, data is transmitted between the application system and the processing system through network services, without copying all user data, and the transmission speed is fast and the delay is small. Users can make the presentation of the target data more flexible according to their preferences.

Description

Method and system for realizing data sharing among heterogeneous systems

technical field

The invention relates to data sharing technology, in particular to a method and system for realizing data sharing among heterogeneous systems.

Background technique

With the development of Internet technology and the increasing demand for cross-platform, the data sharing business among heterogeneous platforms is increasing day by day. In general, data sharing is realized by manual intervention, such as hard disk data copy, file transfer protocol (FTP, File Transfer Protocol) transmission, etc. With the continuous promotion and evolution of Web Services (WS, Web Services) technology, it is possible to use WS technology to solve data transmission between heterogeneous systems.

WS is mainly to build a common platform-independent and language-independent technical layer on the basis of various existing heterogeneous platforms. Applications on various platforms rely on this technical layer to realize mutual connection and integration.

In general, the processing system is used to complete various user data management, business data calculation and other operations; the application system provides a service platform for specific businesses. In order to enable users to obtain the user data they want to query through the application system, it is necessary to realize data sharing between the processing system and the application system. For example: the processing system can be a business operation support system (BOSS, Business Operation Support System), and the application system can be an electronic bill (eBill) system, a customer care (eCare) system, etc. The BOSS system can regularly perform accounting operations on the users in the system every month, and generate detailed Extensible Markup Language (XML, eXtensible Markup Language) for each user's consumption while calculating the consumption amount, discount amount, and payment amount of each user in the current month bill. The generation of the bill file is based on the bill style definition in the BOSS system. Users can query bills through the eBill system, and data sharing between the BOSS system and the eBill system is required.

At present, in order to enable users to use data files outside the processing system, a batch style conversion unit is often set inside the processing system. Taking the BOSS system as an example, a batch style conversion unit is set up in the BOSS system, and maintenance personnel convert all XML bills into Hypertext Makeup Language (HTML, Hypertext Makeup Language) bills at one time by inputting commands. Among them, the XML bill is only for query and use by users in the BOSS system, and the HTML bill is for copying and use by other application systems. All XML bills and HTML bills are saved in the BOSS system. Then, in order for the user to obtain the user bill outside the BOSS system, the HTML bill generated in the BOSS system needs to be copied to the application system for the user to query and use. Users can browse HTML files on the page through the interactive unit in the application system.

The system for implementing data sharing between heterogeneous systems in the above prior art is shown in FIG. 1 , wherein the processing system 100 includes: a business processing unit 101 , a storage unit 102 , and a style conversion unit 103 .

The business processing unit 101 is used for related operations such as management and calculation of user data, generates XML data and stores it in the storage unit 102; the style conversion unit 103 reads the XML data in the storage unit 102, and The XML style language (XSL, eXtensibleStylesheet Language) style is converted into HTML data and stored in the storage unit 102, and then sent to the application system 110.

The application system 110 includes an interaction unit 111 and a storage unit 112 . The user inputs a query index through the interaction unit 111, and the interaction unit reads the HTML data that the user is looking for from the storage unit 112 through the query index, and then feeds back to the user. The storage unit 112 is configured to store the HTML data sent by the processing unit 100 .

Although the technical solution mentioned above realizes data sharing between heterogeneous systems, it has the following disadvantages: when the number of users in the processing system is huge, it is necessary to store all XML data and HTML data in the processing system, which requires A large amount of storage space increases the investment in storage equipment. In addition, each data copy in the processing system and application system must be performed under the condition of manual intervention, for example, checking the storage space, inputting commands to copy, etc., which increases maintenance costs. Therefore, realizing data sharing between heterogeneous systems in the prior art requires relatively high costs.

Contents of the invention

In view of this, the first purpose of the embodiments of the present invention is to provide a method for implementing data sharing among heterogeneous systems, so as to reduce the cost required for data sharing among heterogeneous systems.

The second purpose of the embodiments of the present invention is to provide a method for providing shared data, so as to reduce the cost required for data sharing among heterogeneous systems.

The third object of the embodiments of the present invention is to provide a system for realizing data sharing among heterogeneous systems, so as to reduce the cost required for data sharing among heterogeneous systems.

The fourth object of the embodiments of the present invention is to provide a processing system to reduce the cost required for data sharing among heterogeneous systems.

The fifth object of the embodiment of the present invention is to provide an application system to reduce the cost required for data sharing among heterogeneous systems.

In order to achieve the above first objective, the embodiment of the present invention provides a method for realizing data sharing between heterogeneous systems, the method is as follows: the application system sends a query request to the processing system; the processing system extracts the user data according to the received query request source data, and then send the source data to the application system; the application system converts the received source data into target data and provides it to the user.

In order to achieve the above second objective, an embodiment of the present invention provides a method for providing shared data, which is characterized in that a query request is received, user's source data is extracted according to the query request, and then the source data is sent.

In order to achieve the above third objective, an embodiment of the present invention provides a system for realizing data sharing between heterogeneous systems, the system includes: a processing system and an application system;

The application system sends a query request to the processing system; the application system converts the received source data into target data;

The processing system extracts the user's source data according to the received query request and sends it to the application system.

In order to achieve the fourth objective above, an embodiment of the present invention provides a processing system, which includes: a WS server, a business processing unit, and a storage unit;

The WS server receives the query request, parses out the query index in the query request, reads the source data that the user wants to query from the storage unit according to the query index, and then sends the source data that the user wants to query;

The business processing unit manages and calculates user data, and stores the user's source data in the storage unit;

The storage unit is used to store user's source data.

In order to achieve the above fifth objective, the embodiment of the present invention also provides an application system, the application system includes: an interaction unit, a WS client and a conversion unit;

The interaction unit sends the query index input by the user to the WS client; provides the purpose data sent by the conversion unit to the user;

WS client, after receiving the query index sent by the interaction unit, sends a query request to the processing system; after receiving the source data, sends the source data to the conversion unit;

The conversion unit receives the source data sent by the WS client, converts it into destination data, and sends it to the interaction unit.

It can be seen from the above technical solutions that the method and system provided by the embodiments of the present invention do not need to set a storage space for the target data in the processing system, which reduces the cost on the storage device; and the processing system and the application system Data transmission can be completed without manual intervention, reducing maintenance costs, thereby reducing the cost required for data sharing among heterogeneous systems.

Description of drawings

FIG. 1 is a system structure diagram for realizing data sharing between heterogeneous systems in the prior art;

FIG. 2 is a system structure diagram for realizing data sharing between heterogeneous systems provided by an embodiment of the present invention;

FIG. 3 is a flowchart of a method for realizing data sharing between heterogeneous systems provided by an embodiment of the present invention;

FIG. 4 is a flowchart of a method for implementing bill sharing among heterogeneous systems provided by an embodiment of the present invention;

Fig. 5 is a schematic diagram of an XML bill structure provided by an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solution, and advantages of the present invention more clear, the present invention will be described in detail below in conjunction with the accompanying drawings and specific embodiments.

The method provided by the embodiment of the present invention mainly includes: the application system sends a query request to the processing system, and the processing system extracts the source data of the user according to the received query request, and then sends it to the application system, and the application system converts the received source data into The purpose data is provided to the user.

Wherein, the method for providing shared data is: receiving a query request, extracting the user's source data according to the query request, and then sending the source data.

The source data may be XML data, and the target data may be HTML data. The following embodiments are described by taking XML data and HTML data as examples. But it is not limited to the above embodiment, and it is also applicable to other forms of source data and target data.

First, the system for realizing data sharing among heterogeneous systems provided by the present invention is described. As shown in FIG. 2 , the system includes a processing system 200 and an application system 210 .

The application system 210 sends a query request to the processing system 200. The processing system 200 extracts the user's XML data according to the received query request and sends it to the application system 210. The application system 210 converts the received XML data into HTML data and provides it to the user.

The application system 210 includes: an interaction unit 211 , a WS client 212 , and a conversion unit 213 .

The interaction unit 211 sends the query index input by the user to the WS client 212; and provides the HTML data sent by the conversion unit 213 to the user.

The interactive unit can be a browser, which can provide users with query pages to facilitate the input of query indexes; HTML data can also be provided to users through pages.

For example, in the eBill system, the query index may be the user's phone number and month; in the order quantity query system, the query index may be the product name and date. You can enter the user's phone number and month through the page on the eBill system to inquire about the call fee.

The WS client 212 sends a query request to the processing system 200 after receiving the query index sent by the interaction unit 211 ; and sends the XML data to the style conversion unit 213 after receiving the XML data sent by the processing system 200 .

The query request may be sent in the form of a data packet, and the data packet of the query request includes the information of the query index.

The XML data is the relevant data that the processing system replies to the user of the application system to query.

The conversion unit 213 receives the XML data sent by the WS client, converts it into HTML data, and sends it to the interaction unit 211 .

Wherein, the conversion unit 213 may include: a style conversion unit 223 and a storage unit 233;

The style conversion unit 223 is used to receive the XML data sent by the WS client 212, convert it into HTML data, and store it in the storage unit 233;

The storage unit 233 is used to store the HTML data converted by the style conversion unit 223 and submit it to the interaction unit 211 . Here, the storage unit can facilitate long-term use of the HTML data by the user.

The conversion unit 213 may also only include the style conversion unit 223 , and submit the converted HTML data to the interaction unit 211 directly.

The interaction unit 211 is further configured to send the conversion program identifier selected by the user to the style conversion unit 223 .

Wherein, the style conversion unit 223 includes two parts: a converter and a conversion program storage subunit. The conversion program storage subunit is used to store the conversion program. The converter receives the XML data sent by the WS client 212, reads the corresponding conversion program in the conversion program storage unit according to the conversion program identifier sent by the interaction unit 211, and converts the XML data into HTML data in a style corresponding to the selected conversion program, Send to the interaction unit 211.

The converter may be an XML style transformation (XSLT, eXtensible Stylesheet LanguageTranslate) processor. The conversion program is XSL style, and different conversion programs can be selected. Each conversion program corresponds to an XSL style, and XML data can be converted into HTML data of different styles.

XSL is a style language designed for XML, because most browsers still do not support XML, so XSL should be used to convert XML to HTML.

For example, in the bill query system, the user can select a conversion program and choose his favorite HTML bill style, for example, setting the bill style to a yellow background or a simple display style.

The processing system 200 includes: a WS server 201 , a business processing unit 202 , and a storage unit 203 .

The WS server 201 receives the query request sent by the application system 210 , parses out the query index in the query request, reads the XML data to be queried by the user from the storage unit 203 according to the query index, and sends it to the application system 210 .

Wherein, the XML data sent to the application system may be sent in the form of an XML data stream, and the XML data stream is returned to the application system in a response packet; it may also be sent in the form of an XML file.

The service processing unit 202 manages and calculates user data, and stores the user's XML data in the storage unit 203 .

The XML contains elements and attributes used by markup languages, methods of sorting and nesting, and data types.

The storage unit 203 is used to store user's XML data.

The above-mentioned data transmission between the processing system 200 and the application system 210, that is, the data transmission between the WS server 201 and the WS client 212, is realized through Web Services Definition Language (WSDL, Web Services Definition Language).

The WSDL includes message formats, Internet protocols, and addresses used in communication between the WS server and the WS client.

What the WS client sends to the WS server is a query request, which includes the query index; what the WS server sends to the WS client is a query response, which includes the entire XML data, so as to realize the transfer of user data.

The method for realizing data sharing among heterogeneous systems provided by the present invention is described below. As shown in Figure 3, it mainly includes the following steps:

Step 301: the application system sends a query request to the processing system.

In this step, the user first inputs a query index to the application system, for example, enters the query index on the page through a browser, and then the application system sends a query request to the processing system according to the query index input by the user.

The query request sent by the application system to the processing system may be encapsulated in a data packet and sent, and the data packet of the query request includes the information of the query index.

In order to realize this step, a WS client may first be set in the application system, and a query request is sent to the processing system through the WS client.

Step 302: The processing system extracts the user's XML data according to the received query request, and then sends it to the application system.

In this step, the WS server can be set in the processing system first, and the query request sent by the application system can be received through the WS server, and the query index in the query request can be parsed out, and the XML data to be queried by the user can be extracted according to the query index, and sent to the application system.

The XML data sent to the application system can be sent in the form of an XML data stream, and the XML data stream is returned to the application system in a response packet; it can also be sent in the form of an XML file, and the XML file can be copied to the application system middle.

The XML contains elements and attributes used by markup languages, methods of sorting and nesting, and data types.

In the above step 301 and step 302, the data between the application system and the processing system is transmitted through the network, and the data transmission is realized by Web Services Definition Language (WSDL, Web Services Definition Language). The WSDL includes message formats, Internet protocols, and addresses used in communication between the application system and the processing system.

Step 303: the application system converts the received XML data into HTML data and provides it to the user.

In this step, the application system receives the XML data, combines different conversion programs, and converts the XML data into HTML data corresponding to the conversion program through the converter.

The converter may be an XML style transformation (XSLT, eXtensible StylesheetLanguage Translate) processor.

Wherein the conversion program is an XSL style. XLS is a style language specially designed for XML. Users can choose different XSL styles to convert into different styles of HTML data according to their own needs and preferences. In the prior art, the same XSL style is used in the processing system so that the HTML data style seen by the user is all the same, but in the solution of the present invention, the method of using the XSL style in the application system is used, so that the HTML data The display is more convenient and flexible.

The application system can provide the generated HTML data to the user in the form of a page through the browser.

The method provided by the present invention will be described in detail below by taking the operator's provision of user telephone charge bill inquiry service as an example. At this time, the processing system provided by the operator is the BOSS system, and the application system is the eBill system. The user wants to inquire about the telephone bill of a certain month. The process is shown in Figure 4, mainly including the following steps:

Step 401: Enter phone number and month into eBill system.

Here, the telephone number and month to be queried are used as the query index.

Step 402: The WS client in the eBill system is triggered to send a bill query request to the BOSS system through the network.

In this step, the eBill system sends a bill query request (GetCustomerBillRequest) to the BOSS system through the network, which includes the queried phone number and the queried month.

Step 403: The WS server in the BOSS system parses out the inquired phone number and month after receiving the query request, and finds the user's XML bill according to the phone number and month.

Wherein, the XML bill includes: billing item names and characteristics, sorting and nesting of billing items, and data types of billing items.

For example, in the XML bill shown in Figure 5, the root node bill of the bill is first included, and the child nodes include fee information, user information, a structure for summarizing usage by service category, and a structure for describing detailed bill information, etc. Wherein, the fee information may include the balance of the previous period, the payable of the current period, and payment rules. User information may include user deposit, user number, account period and other related user information. The structure of summarizing usage by service category can include: fee summarization combination, usage summarization combination, etc.

Step 404: The WS server in the BOSS system puts the XML bill in a response packet and returns it to the eBill system.

The BOSS system returns the eBill system bill query response (GetCustomerBillReply) in the form of a response packet, which contains the entire XML bill.

Step 405: After receiving the XML bill, the eBill system determines the XSL style according to the bill style selected by the user, and uses the XSLT processor to combine the XSL style with the XML bill to generate an HTML bill.

For example: the user selects the bill style as a yellow background and a simple style. After the eBill system receives the XML bill, it can generate an HTML bill that meets the user's needs according to the bill style selected by the user.

Step 406: The phone bill is displayed in the form of a page on the browser.

At this time, the user can browse to the telephone charge bill that he inquired, and can print or download it to an external device.

The present invention is based on WS technology, the application system sends a query request to the processing system, and the processing system extracts the source data of the user according to the received query request, and then sends it to the application system, and the application system converts it into target data and provides it to the user, thereby completing the different The sharing of data between structural systems does not need to set up storage space for the purpose data in the processing system, which reduces the cost of storage devices; and the data transfer between the processing system and the application system can be completed without manual intervention, reducing maintenance The cost of personnel, thereby reducing the cost required for data sharing among heterogeneous systems.

Furthermore, because the data transmission between the application system and the processing system is realized by WDSL through the network, the transmission speed is very fast, and only the information inquired by the user is transmitted to the application system when the user inquires, while in the prior art it is necessary to All user data is copied, so the time delay caused by the need to copy a large amount of data in the prior art is solved.

Furthermore, users can select the style of the target data according to their own needs and preferences, and apply different conversion programs. Compared with the prior art, the unified conversion program is used in the batch style conversion unit in the processing system, so that the style of the target data Show more flexibility.

Claims (16)

1. A method for realizing data sharing between heterogeneous systems, characterized in that the application system sends a query request to the processing system; the processing system extracts the user's source data according to the received query request, and then sends the source data to the application system ; The application system converts the received source data into target data. 2. The method according to claim 1, wherein the sending the source data to the application system is: the processing system sends the source data to the application system in the form of a source data stream, or sends it in the form of a source data file to the application system. 3. The method according to claim 1, characterized in that, the application system sends the query request to the processing system and the processing system sends the user's source data to the application system, which is realized through the Web Service Description Language (WSDL). 4. The method according to claim 1, 2 or 3, wherein the source data is Extensible Markup Language XML data; the target data is Hypertext Link Markup Language HTML data. 5. A method for providing shared data, characterized in that a query request is received, source data of a user is extracted according to the query request, and then the source data is sent. 6. The method according to claim 5, wherein the query request includes a query index input by the user to the application system; The extraction of the user's source data is: the processing system parses out the query index in the query request, and extracts the source data to be queried by the user according to the query index. 7. The method according to claim 5, wherein the source data is XML data. 8. A system for realizing data sharing between heterogeneous systems, characterized in that the system includes: a processing system and an application system, wherein, The application system sends a query request to the processing system; converts the received source data into target data and provides it to the user; The processing system extracts the user's source data according to the received query request and sends it to the application system. 9. The system according to claim 8, wherein the processing system is an operation support system (BOSS); The application system is an electronic bill eBill system or a customer care eCare system. 10. The system according to claim 8, wherein the source data is XML data; the target data is HTML data. 11. A processing system, characterized in that the processing system includes: a WS server, a business processing unit, and a storage unit; The WS server receives the query request, parses out the query index in the query request, reads the source data that the user wants to query from the storage unit according to the query index, and then sends the source data that the user wants to query; The business processing unit manages and calculates user data, and stores the user's source data in the storage unit; The storage unit is used to store user's source data. 12. The processing system according to claim 11, wherein the source data is XML data; the target data is HTML data. 13. An application system, characterized in that the application system includes: an interaction unit, a WS client, and a conversion unit; The interaction unit sends the query index input by the user to the WS client; provides the purpose data sent by the conversion unit to the user; WS client, after receiving the query index sent by the interaction unit, sends a query request to the processing system; after receiving the source data, sends the source data to the conversion unit; The conversion unit receives the source data sent by the WS client, converts it into destination data, and sends it to the interaction unit. 14. The application system according to claim 13, wherein the conversion unit comprises a style conversion unit and a storage unit, The style conversion unit is used to receive the source data sent by the WS client, convert it into destination data, and store it in the storage unit; The storage unit is used to store the target data converted by the style conversion unit and provide it to the interaction unit. 15. The application system according to claim 13, wherein the interaction unit is further configured to send the conversion program identifier selected by the user to the style conversion unit; The style conversion unit includes: a converter and a conversion program storage subunit; The converter receives the source data sent by the WS client, reads the corresponding conversion program in the conversion program storage subunit according to the conversion program identifier selected by the user, and converts the source data into the target data corresponding to the read conversion program; The conversion program storage subunit stores the conversion program. 16. The system according to claim 13, 14 or 15, wherein the source data is XML data; the target data is HTML data.

Images