Browse Prior Art Database

A method and system for service integration in BI solution

IP.com Disclosure Number: IPCOM000236885D
Publication Date: 2014-May-21

Publishing Venue

The IP.com Prior Art Database

Abstract

This document describes a method and system that can easily integrate multiple systems in BI solution. It introduces an Universal Data Format (UDF) that can be the common language communicated between systems. It also introduces a service based web resource Self-descriptive Data Node(SDN), which can be uniquely identified and accessed by any system. BI solution is created based on the dependencies of SDN(s), which is a extensible topology map.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 11

A method and system for service integration in BI solution

Background

With the development of World Wide Web (WWW ), and with the big data trends caused by the explosion of the business and social activities, the business intelligence software had tremendous development in the past years.

Unfortunately, there is no overcall solution that can cover all the BI requirements. Generally, one mature system has strong capability in one or two aspects. For example, Query/Reporting System has strong ability to access Data Base, but weak on data analysis. Analysis System has strong analysis ability, but not data ware house access and reporting.

Meanwhile, different systems might have overlapped functionalities with its own data storage, communication and visualization methods, which makes them hard to be integrated.

Thus, we need an unified method to join data and services between systems, and the method should be simple, flexible and easy to be understood.

Description

This document defines an Universal Data Format (UDF) as communication languages between systems in BI solution.

UDF

UDF is a data resource in JavaScript Object Notation (JSON) format. UDF contains not only the data, but also the meta-data information. The meta-data information will be used by all the sub systems in BI solution to understand/process/transform the data.

An instance of UDF contains two parts: header and body. The header section defines the meta-data or descriptive information of the data, including the version, ID, transaction information, data type, data scheme etc. While the body section is the real raw data itself.

1


Page 02 of 11

Here is an example:

The Header section defines the metadata of the data contained, they are:

-version
-id
-description
-
type [atom, array, rowset, custom] -timestamp
-language
-
transaction id
-transaction parameter
-
fields

For the rowset data type, the detail information of each data field is also defined, each field may contain information as:

-id
-label
-order
-isKey -granularity -format -isMeasure -supportDrillDown -supportDrillUp -targetNode

2


Page 03 of 11

-priority -values

SDN

Self-descriptive Data Node (SDN) is an uniquely identified UDF resource on web. Each instance of node has unique URI which follows Internet URI standard (STD 66).

SDN is created by SDN service, nodes are maintained in hierarchical structure, with path like[Domain]/[Sub Domain]/SDN Name.

SDN can be considered as a sort of accessible web resource, similar as any other web resources (image, XML, audio, video etc), the content of this resource is data in UDF.

With the information contained inside SDN, data can be understood and communicated between different types of data processing and visualization system. For example, Business Intelligence (BI) system, Statistics and Analysis system, and even HTML pages if have SDN viewer engine.

With the explosion of information and the Big Data trends, we can see that the next generation of WWW will be composed by data and link...