WO2011115471A1 - Integrated service delivery platform system and method thereof - Google Patents
Integrated service delivery platform system and method thereof Download PDFInfo
- Publication number
- WO2011115471A1 WO2011115471A1 PCT/MY2010/000262 MY2010000262W WO2011115471A1 WO 2011115471 A1 WO2011115471 A1 WO 2011115471A1 MY 2010000262 W MY2010000262 W MY 2010000262W WO 2011115471 A1 WO2011115471 A1 WO 2011115471A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- component
- server
- application
- components
- service
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- the present invention relates to an architecture for integrated service delivery platform, more particularly relates to the integration of components into various servers according to their functional areas for easy deployment.
- a service delivery platform is generally used to deliver the services to devices used by users that are . based on network or service provider resources used in services provided by the service provider or by a third party that uses these features to extend their applications. As the number of services offered by various network providers continues to increase, there is a corresponding increase in the number of systems, devices and components that process and store information for the end users.
- a system for providing integrated service delivery platform for multiple domains comprises of an integrated platform having components operable to provide functions, the components are mapped into a plurality of servers according to their functional areas which include analytics functional server which involves in decision making activities, information retrieval functional server which involves processing information -from the Web, tracking functional server which provides verbal interfaces, and at least one shared functional server which provides common functions among all domains, and an application server providing access communication of communication devices with the integrated platform to perform requested functions.
- a method for providing integrated service delivery platform for multiple domains comprising the steps of identifying the required servers for running a requested application, provoking the identified servers, registering the identified servers to the UDDI sever by the triggered servlet, and executing the integrated platform to perform the requested application.
- Figure 1 depicts a block diagram of an integrated service delivery platform system of the present invention
- Figure 2 shows an architecture of the integrated platform of the present invention
- Figure 3 is a flowchart of the method for an integrated platform of the present invention
- Figure 4 is a flowchart for execution of the integrated platform
- Figure 5 illustrates a block diagram showing example of the system used by Public Complaints Bureau (PCB)
- Figure 6 is a flowchart of the method for figure 5;
- Figure 7 shows a flowchart for execution of the integrated platform for PCB in summarizing text
- Figure 8 shows a flowchart for execution of the integrated platform for PCB in categorizing text
- Figure 9 depicts a block diagram showing example of the system used by i-Logistic
- Figure 10 is a flowchart of the method for figure 9;
- Figure 11 shows a flowchart for execution of the integrated platform for i-Logistic in profiling order
- Figure 12 shows a flowchart for execution of the integrated platform for i-Logistic in optimizing order
- Figure 13 shows a flowchart for execution of the integrated platform for i-Logistic in updating order pool.
- a system (10) in accordance to the present invention provides an integration of components into various servers based on their functional areas for easy deployment in multiple domains.
- the functional areas categorization being identified include but not limited to analytical, information retrieval and tracking. Beside the components for these functional areas, there is also a shared functional area which contains components that are common among all domains.
- the architecture enables efficient and rapid deployment of applications by service providers who seek to provide services to users.
- a service delivery platform substantially automates sales, order management, provisioning, billing and operations management.
- the service delivery platform of the present invention relies on a functionality-based components in various servers that maximizes flexible deployment
- FIG 1 is a block diagram of architecture of an integrated service delivery platform system (10) of the present invention.
- the system (10) includes an application server (11) which defines an interface for communication and data transfer between users with communication devices (12) such as mobile phones, PDAs, laptops, computers etc and an integrated platform (13) of the present invention.
- the integrated platform is a block diagram of architecture of an integrated service delivery platform system (10) of the present invention.
- the system (10) includes an application server (11) which defines an interface for communication and data transfer between users with communication devices (12) such as mobile phones, PDAs, laptops, computers etc and an integrated platform (13) of the present invention.
- the integrated platform such as mobile phones, PDAs, laptops, computers etc.
- proxy (13) comprising a proxy server (14) used to manage the service provides' servers and a common server (15) where both proxy (14) and common (15) servers contain respective components that are common among all domains and these servers (14, 15) are mapped into a common sub-platform in the shared functional area. They are in the shared functional area as the components in the common (15) and proxy (14) servers are not only used by the external clients but also can be used by components within the integrated platform
- the integrated platform (13) also includes a decision support system (DSS) server (16) that provides set of service-based components that can be consumed by any DSS application in decision making process, an information server (17) which consists of components that enables users to obtain information from the world wide web and at the same time perform some processing on these data to make it more meaningful for the user, and a mobile server (18) which comprises component that provides verbal interface.
- DSS server (16) is mapped into a decision support system sub-platform in the analytic functional area, whereas information server (17) is mapped into an information sub-platform in the information retrieval functional area and the mobile server (18) is mapped into a mobile sub-platform in the tracking functional area.
- the core of the information required by the integrated platform (13) resides in a knowledge database (19) which can be stored in multiple triple-stores.
- the decision support system (DSS) server (16) which supports business decision making activities includes service-based components such as but not limited to Rule-Based Reasoner (RBR) component (20) , decision model management (DMM) component (21) , workflow management (WFM) component (22) and data miner component (23) as shown in Figure 2.
- RBR Rule-Based Reasoner
- DMM decision model management
- WFM workflow management
- DSS data miner component
- Rule-based reasoner (RBR) component (20) it provides service to infer a conclusion regarding a problem that cannot be observed directly such as a particular type of reasoning which uses "if-then-else" rule statements and the rules are simply patterns and knowledge engine searches for patterns in the rules that match patterns in the data.
- the DMM component (21) that includes at least one decision model which is an axiomatic system that contains at least one action axiom.
- the DMM component (21) there are several models of decision making in the DMM component (21) and each decision model is based on different set of assumptions and offered unique insight into the decision-making process.
- the DMM component (21) helps to simplify the building of decision models and execution of decision models by offering the functionalities of model builder service and model executor service.
- WFM workflow
- the data miner component (23) in the DSS server (16) provides service to analyze data in the database and produces a regression formula based on the given input and output table fields.
- the information server (17) which stores and manages business information with a web interface, includes components such as but not limited to text annotator component (24), source preprocessor component (25) , ontology-based categorizer (OBC) component (26) and ontology-based summarizer (OBS) component (27).
- components such as but not limited to text annotator component (24), source preprocessor component (25) , ontology-based categorizer (OBC) component (26) and ontology-based summarizer (OBS) component (27).
- the text annotator component (24) , it provides services for the extraction of domain-specific (ontology driven) relations from documents.
- the need for text annotator is driven by need to annotate using GATE API by building a component.
- the text annotator component will take a natural language document or corpus as the input and it will map the gazetteer lists to ontology classes and load it to ANNIE pipeline with the required JAPE rules .
- the document or corpus will be processed by the ANNIE. It will then return the annotations with the relations and since the text annotator is a web service enabled component, all receiving and sending operations must follow simple object access protocol (SOAP) for exchanging information in the over the web.
- SOAP simple object access protocol
- the source preprocessor component (25) provides service to extract plain text from a PDF or HTML file as most information from the web is provided in different type of documents, such as HTML and PDF documents. There is a need to extract plain text from HTML and PDF documents for further text processing.
- the source preprocessor component (25) takes a URL that links to a HTML or a PDF file and extracts plain text from the file. The plain text is then uploaded to a file server. After that, the component (25) returns URL of the extracted text document which will be stored in the file server and since the source preprocessor component (25) is a web service enabled component, all receiving and sending operations will follow the SOAP architecture too.
- ontology-based categorizer (OBC) component (26) it provides service to determine the category of a document and categorizes the document into that determined category. This categorizer component (26) will get the feature vector of a document and will label the document a respective category.
- ontology-based summarizer (OBS) component (27) provides service to extract key points from a plain text document and create a summary based on it. The OBS component (27) takes the URL of the plain text file and generates a summary based on it. The summary is then stored in a file server and the component (27) returns.the URL of the summarized text document.
- the mobile server (18) which includes text to speech (TTS) component (28) designed to provide software with a verbal interface
- TTS text to speech
- TTS component (28) designed to provide software with a verbal interface
- TTS component will be invoked after the content aggregator finished collecting contents from the Web. This component will provide text-to-audio conversion and store the audio file into the database .
- the common server (15) which contains components that are common among all domains includes but not limited to KB handler component (29) , intelligent search component (30) , web profiler component (31) and data integrator (DIR) component (32). Basically, the common server (15) provides create, read, update and delete (CRUD) function on the knowledge database (19).
- the KB handler component (29) deals with all interfaces to the knowledge database (19) and provides the..functionality of .adding, editing and deleting data from the knowledge database (19) .
- the intelligent search component (30) allows user to query the knowledge database (19) using natural language and the input to the service will include free text questions, e.g questions that start with the x what' questions.
- the web profiler component (31) it allows for retrieval of information from the knowledge database (19) according to the profile of the user and a profile ontology will be used together with this service.
- DIR data integrator
- the objective of this component (32) is to address the problem of integrating data retrieved from multiple heterogeneous data sources and the focus of data integrator component (32) is theoretical work and numerous open problems to be solved.
- the Proxy server (14) includes components that are common among all domains namely service proxy component (33) and service discovery and registry (SOAR) component (34) .
- the service proxy component (33) provides a single point of contact for the web service client to access web services in the integrated platform (13) .
- User of the platform (13) accesses the components through the service proxy (33) which will locate the components from the Universal Description Discovery and Integration (UDDI) server (35) using SDAR (34) .
- UDDI Universal Description Discovery and Integration
- FIG 3 illustrates the flowchart for the integrated platform (13) deployment.
- the necessary service providers for the identified domain are first identified (41) .
- the servers for the identified service providers are started (42) and during the startup of the servers, the servlet will be triggered which will then register (43) itself to the UDDI server (35) .
- the system then continues with the platform execution as shown in Figure 4.
- User requests for the application using the communication devices (12) such as notebooks, desktop, mobile phones, pda, etc through the application server (11) .
- the application server (11) Upon processing the request, the application server (11) then requests services from the integrated platform (13) through the Proxy server (14) .
- the service proxy component (33) will request SDAR component (34) in the Proxy server (14) to search for the -requested function (45). Then the SDAR component (34) will look up (46) the requested service from the UDDI server (35) . If the service exists (47), the Proxy server (14) will direct the request to the relevant server of service provider where the UDDI server (35) returns (48) the identified server address to the SDAR component (34) , followed by the SDAR component (34) returns (49) to the Service proxy component (33) to request (50) function from the identified server. The identified server executes (51) the requested function and returns results (52) to the application server (11) via the Proxy server (14).
- the architecture of the integrated platform (13) as shown in Figure 5 and flowchart as shown in Figures 6, 7 and 8 show example on how the service has been used by the Public Complaint Bureau (PCB) to retrieve and classify the information from online news, web sites, blogs, etc.
- PCB Public Complaint Bureau
- User may request for the application to summarize text (53) and categorize text (54) where the steps are shown in detailed in figure 7 and 8 respectively.
- This summarizing text function is done by the information server (17) using the ontology-based summarizer (OBS) component (27) and the categorizing text function is done by the information server (17) using the ontology-based categorizer (OBC) component (26) .
- OBS ontology-based summarizer
- OBC ontology-based categorizer
- the architecture of the integrated platform (13) as shown in Figure 9 and flowchart as shown in Figures 10, 11, 12 and 13 show an example on how the service has been used by i-Logistic enterprise management system to analyze and propose suitable vehicle for every order shipment.
- User may request for the application to profile the order (55) , then optimize the order (56) by merging orders and recommending vehicles and lastly update orders pool (57) as shown in Figure 10 where the steps are shown in detailed in figures 11, 12 and 13 respectively.
- the profiling order, optimizing order and updating order pool functions are done by the DSS server (16) using the workflow management (WFM) component (22) .
Abstract
A system (10) for providing integrated service delivery platform for multiple domains comprises of an integrated platform (13) having components operable to provide functions, the components are mapped into a plurality of servers according to their functional areas which include analytics functional server (16) which involves in decision making activities, information retrieval functional server (17) which involves processing information from the Web, tracking functional server (18) which provides verbal interfaces, and at least one shared functional server (14, 15) which provides common functions among all domains, and an application server (11) providing access communication of communication devices (12) with the integrated platform (13) to perform requested functions.
Description
Integrated Service Delivery Platform System and Method Thereof Field of Invention
The present invention relates to an architecture for integrated service delivery platform, more particularly relates to the integration of components into various servers according to their functional areas for easy deployment.
Background of Invention
A service delivery platform is generally used to deliver the services to devices used by users that are. based on network or service provider resources used in services provided by the service provider or by a third party that uses these features to extend their applications. As the number of services offered by various network providers continues to increase, there is a corresponding increase in the number of systems, devices and components that process and store information for the end users.
In telecommunication, service providers not only have to deal with the services and platform but also support business processes to
provide services to their customers. Existing systems do not provide a solution which enables easy deployment of platform for multiple domains based on its functional areas. Most of the current platform deployment involves deployment of all the components in the platform which in turn results in redundancy. Deployment of additional components might be substantially unrelated and not easily aggregated.
Therefore there is a need of the present invention to provide a system which packaging components into various servers according to their functionalities. Selective servers deployment are made possible as the Proxy server is used to manage the service providers' servers in the present invention.
Other objects of this invention will become apparent on the reading of this entire disclosure.
Summary of Invention
In one aspect of the present invention, a system for providing integrated service delivery platform for multiple domains is disclosed. The system comprises of an integrated platform having
components operable to provide functions, the components are mapped into a plurality of servers according to their functional areas which include analytics functional server which involves in decision making activities, information retrieval functional server which involves processing information -from the Web, tracking functional server which provides verbal interfaces, and at least one shared functional server which provides common functions among all domains, and an application server providing access communication of communication devices with the integrated platform to perform requested functions.
In another aspect of the present invention, a method for providing integrated service delivery platform for multiple domains is disclosed. The method comprising the steps of identifying the required servers for running a requested application, provoking the identified servers, registering the identified servers to the UDDI sever by the triggered servlet, and executing the integrated platform to perform the requested application.
Brief Description of the Drawings
Other objects, features, and advantages of the invention will be apparent from the following description when read with reference to the accompanying drawings. In the drawings, wherein like reference numerals denote corresponding parts throughout the several views:
Figure 1 depicts a block diagram of an integrated service delivery platform system of the present invention;
Figure 2 shows an architecture of the integrated platform of the present invention; Figure 3 is a flowchart of the method for an integrated platform of the present invention;
Figure 4 is a flowchart for execution of the integrated platform; Figure 5 illustrates a block diagram showing example of the system used by Public Complaints Bureau (PCB) ;
Figure 6 is a flowchart of the method for figure 5;
Figure 7 shows a flowchart for execution of the integrated platform for PCB in summarizing text;
- .. - .. - ..
Figure 8 shows a flowchart for execution of the integrated platform for PCB in categorizing text;
Figure 9 depicts a block diagram showing example of the system used by i-Logistic;
Figure 10 is a flowchart of the method for figure 9;
Figure 11 shows a flowchart for execution of the integrated platform for i-Logistic in profiling order;
Figure 12 shows a flowchart for execution of the integrated platform for i-Logistic in optimizing order; and Figure 13 shows a flowchart for execution of the integrated platform for i-Logistic in updating order pool.
Detailed Description of the Preferred Embodiments
In the following detailed description, numerous specific details •are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known methods, procedures and/or components have not been described in detail so as not to obscure the invention. Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.
A system (10) in accordance to the present invention provides an integration of components into various servers based on their functional areas for easy deployment in multiple domains. The functional areas categorization being identified include but not limited to analytical, information retrieval and tracking. Beside the components for these functional areas, there is also a shared functional area which contains components that are common among all domains. The architecture enables efficient and rapid deployment of applications by service providers who seek to provide services to users. A service delivery platform substantially
automates sales, order management, provisioning, billing and operations management. The service delivery platform of the present invention relies on a functionality-based components in various servers that maximizes flexible deployment
Referring now to the drawing, figure 1 is a block diagram of architecture of an integrated service delivery platform system (10) of the present invention. The system (10) includes an application server (11) which defines an interface for communication and data transfer between users with communication devices (12) such as mobile phones, PDAs, laptops, computers etc and an integrated platform (13) of the present invention. The integrated platform
(13) comprising a proxy server (14) used to manage the service provides' servers and a common server (15) where both proxy (14) and common (15) servers contain respective components that are common among all domains and these servers (14, 15) are mapped into a common sub-platform in the shared functional area. They are in the shared functional area as the components in the common (15) and proxy (14) servers are not only used by the external clients but also can be used by components within the integrated platform
(13) .
The integrated platform (13) also includes a decision support system (DSS) server (16) that provides set of service-based components that can be consumed by any DSS application in decision making process, an information server (17) which consists of components that enables users to obtain information from the world wide web and at the same time perform some processing on these data to make it more meaningful for the user, and a mobile server (18) which comprises component that provides verbal interface. The DSS server (16) is mapped into a decision support system sub-platform in the analytic functional area, whereas information server (17) is mapped into an information sub-platform in the information retrieval functional area and the mobile server (18) is mapped into a mobile sub-platform in the tracking functional area. The core of the information required by the integrated platform (13) resides in a knowledge database (19) which can be stored in multiple triple-stores.
The decision support system (DSS) server (16) which supports business decision making activities includes service-based components such as but not limited to Rule-Based Reasoner (RBR) component (20) , decision model management (DMM) component (21) , workflow management (WFM) component (22) and data miner component
(23) as shown in Figure 2. The DSS application developers may integrate DSS components with their DSS application which will then reduce their development process as DSS server provides components for all the major parts of decision making process.
In the Rule-based reasoner (RBR) component (20), it provides service to infer a conclusion regarding a problem that cannot be observed directly such as a particular type of reasoning which uses "if-then-else" rule statements and the rules are simply patterns and knowledge engine searches for patterns in the rules that match patterns in the data. Whereas in the DMM component (21), that includes at least one decision model which is an axiomatic system that contains at least one action axiom. Preferably, there are several models of decision making in the DMM component (21) and each decision model is based on different set of assumptions and offered unique insight into the decision-making process. The DMM component (21) helps to simplify the building of decision models and execution of decision models by offering the functionalities of model builder service and model executor service.
In the workflow (WFM) component (22), it provides service to automate the entire decision making process and acts as a backbone
in connecting all the DSS components together to make a decision. Therefore it simplifies the defining decision-making process and integrating other components of . DSS package. And lastly the data miner component (23) in the DSS server (16) provides service to analyze data in the database and produces a regression formula based on the given input and output table fields.
The information server (17) which stores and manages business information with a web interface, includes components such as but not limited to text annotator component (24), source preprocessor component (25) , ontology-based categorizer (OBC) component (26) and ontology-based summarizer (OBS) component (27).
In the text annotator component (24) , it provides services for the extraction of domain-specific (ontology driven) relations from documents. The need for text annotator is driven by need to annotate using GATE API by building a component. The text annotator component will take a natural language document or corpus as the input and it will map the gazetteer lists to ontology classes and load it to ANNIE pipeline with the required JAPE rules . The document or corpus will be processed by the ANNIE. It will then return the annotations with the relations and since the text annotator is a
web service enabled component, all receiving and sending operations must follow simple object access protocol (SOAP) for exchanging information in the over the web. While on the contrary, the source preprocessor component (25) provides service to extract plain text from a PDF or HTML file as most information from the web is provided in different type of documents, such as HTML and PDF documents. There is a need to extract plain text from HTML and PDF documents for further text processing. The source preprocessor component (25) takes a URL that links to a HTML or a PDF file and extracts plain text from the file. The plain text is then uploaded to a file server. After that, the component (25) returns URL of the extracted text document which will be stored in the file server and since the source preprocessor component (25) is a web service enabled component, all receiving and sending operations will follow the SOAP architecture too.
In the ontology-based categorizer (OBC) component (26) , it provides service to determine the category of a document and categorizes the document into that determined category. This categorizer component (26) will get the feature vector of a document and will label the document a respective category.
Whereas, ontology-based summarizer (OBS) component (27) provides service to extract key points from a plain text document and create a summary based on it. The OBS component (27) takes the URL of the plain text file and generates a summary based on it. The summary is then stored in a file server and the component (27) returns.the URL of the summarized text document.
The mobile server (18) which includes text to speech (TTS) component (28) designed to provide software with a verbal interface Other than reading the text, user has alternative to listen to the text audio on the device. When an application talks more like a real human voice, the application making it easier for the user to understand and promoting retention of the contents. TTS component (28) will be invoked after the content aggregator finished collecting contents from the Web. This component will provide text-to-audio conversion and store the audio file into the database .
The common server (15) which contains components that are common among all domains includes but not limited to KB handler component (29) , intelligent search component (30) , web profiler component (31) and data integrator (DIR) component (32). Basically, the
common server (15) provides create, read, update and delete (CRUD) function on the knowledge database (19).
The KB handler component (29) deals with all interfaces to the knowledge database (19) and provides the..functionality of .adding, editing and deleting data from the knowledge database (19) . On the other hand, the intelligent search component (30) allows user to query the knowledge database (19) using natural language and the input to the service will include free text questions, e.g questions that start with the xwhat' questions. In the web profiler component (31), it allows for retrieval of information from the knowledge database (19) according to the profile of the user and a profile ontology will be used together with this service. And lastly in the data integrator (DIR) component (32), it provides services to combine data residing at different sources and providing users with the unified view of these data. The objective of this component (32) is to address the problem of integrating data retrieved from multiple heterogeneous data sources and the focus of data integrator component (32) is theoretical work and numerous open problems to be solved.
The Proxy server (14) includes components that are common among all domains namely service proxy component (33) and service discovery and registry (SOAR) component (34) . The service proxy component (33) provides a single point of contact for the web service client to access web services in the integrated platform (13) . User of the platform (13) accesses the components through the service proxy (33) which will locate the components from the Universal Description Discovery and Integration (UDDI) server (35) using SDAR (34) .
Figure 3 illustrates the flowchart for the integrated platform (13) deployment. To begin for the deployment, the necessary service providers for the identified domain are first identified (41) . Then, the servers for the identified service providers are started (42) and during the startup of the servers, the servlet will be triggered which will then register (43) itself to the UDDI server (35) . The system then continues with the platform execution as shown in Figure 4. User requests for the application using the communication devices (12) such as notebooks, desktop, mobile phones, pda, etc through the application server (11) . Upon processing the request, the
application server (11) then requests services from the integrated platform (13) through the Proxy server (14) . After the Proxy server (14) received request (44) from the application server (11), the service proxy component (33) will request SDAR component (34) in the Proxy server (14) to search for the -requested function (45). Then the SDAR component (34) will look up (46) the requested service from the UDDI server (35) . If the service exists (47), the Proxy server (14) will direct the request to the relevant server of service provider where the UDDI server (35) returns (48) the identified server address to the SDAR component (34) , followed by the SDAR component (34) returns (49) to the Service proxy component (33) to request (50) function from the identified server. The identified server executes (51) the requested function and returns results (52) to the application server (11) via the Proxy server (14).
The architecture of the integrated platform (13) as shown in Figure 5 and flowchart as shown in Figures 6, 7 and 8 show example on how the service has been used by the Public Complaint Bureau (PCB) to retrieve and classify the information from online news, web sites, blogs, etc. User may request for the application to summarize text (53) and categorize text (54) where the steps are shown in detailed
in figure 7 and 8 respectively. This summarizing text function is done by the information server (17) using the ontology-based summarizer (OBS) component (27) and the categorizing text function is done by the information server (17) using the ontology-based categorizer (OBC) component (26) .
The architecture of the integrated platform (13) as shown in Figure 9 and flowchart as shown in Figures 10, 11, 12 and 13 show an example on how the service has been used by i-Logistic enterprise management system to analyze and propose suitable vehicle for every order shipment. User may request for the application to profile the order (55) , then optimize the order (56) by merging orders and recommending vehicles and lastly update orders pool (57) as shown in Figure 10 where the steps are shown in detailed in figures 11, 12 and 13 respectively. The profiling order, optimizing order and updating order pool functions are done by the DSS server (16) using the workflow management (WFM) component (22) .
As will be readily apparent to those skilled in the art, the present invention may easily be produced in other specific forms without departing from its essential characteristics. The present embodiments is, therefore, to be considered as merely illustrative
and not restrictive, the scope of the invention being indicated by the claims rather than the foregoing description, and all changes which come within therefore intended to be embraced therein .
Claims
1. A system (10) for providing integrated service delivery platform for multiple domains comprising:
an integrated platform (13) having components .operable to provide functions, said components are mapped into a plurality of servers according to their functional areas which include:
analytics functional server (16) which involves in decisionmaking activities ;
information retrieval functional server (17) which involves processing information from the Web;
tracking functional server (18) which provides verbal interfaces; and
at least one shared functional server (14, 15) which provides common functions among all domains; and
an application server (11) providing access communication of communication devices (12) with said integrated platform (13) to perform requested functions.
2. The system (10) as claimed in claim 1, wherein said analytics functional server (16) is a decision support system (DSS) server which includes service-based components such as but not limited to rule-based reasoner (RBR) component (20), decision model management (DMM) component (21), workflow management (WFM) component (22) and data miner component ( 23 ) .
3. The system (10) as claimed in claim 2, wherein said rule-based reasoner (RBR) component (20) includes in performing function to infer a conclusion regarding a problem that cannot be observed directly.
4. The system (10) as claimed in claim 2, wherein said decision model management (DMM) component (21) includes at least one decision model which is based on different set of assumptions and offered unique insight into the decision making processes.
5. The system (10) as claimed in claim 2, wherein said workflow management (WFM) component (22) includes an application to automate the entire decision making process and connecting all the DSS components together for decision making.
6. The system (10) as claimed in claim 2, wherein said data miner component (23) includes an application to analyze data in the database and the regression formula based on the given input and output table fields.
7. The system (10) as claimed in claim 1, wherein said information retrieval functional server (17) is an information server which includes components such as but not limited. to text annotator component (24), source preprocessor component (25), ontology-based categorizer (OBC) component (26) and ontology-based summarizer (OBS) component (27) .
8. The system (10) as claimed in claim 7, wherein said text annotator component (24) includes an application for extraction of domain-specific relations from documents.
9. The system (10) as claimed in claim 7, wherein said source preprocessor component (25) includes an application for extraction plain text from a PDF or HTML files.
10. The system (10) as claimed in claim 7, wherein said ontology-based categorizer (OBC) component (26) includes an application to determine the category of a document and categorize the document into the determined category.
11. The system (10) as claimed in claim 7, wherein said ontology-based summarizer (OBS) component (27) includes an application to extract key points from a plain text document and create a summary based on it.
12. The system (10) as claimed in claim 1, wherein said tracking functional server (18) is a mobile server which includes text to speech (TTS) component (28).
13. The system (10) as claimed in claim 12, wherein said text to speech (TTS) component (28) includes an application to provide text-to-audio conversion and stores the audio file into the database.
14. The system (10) as claimed in claim 1, wherein said shared functional servers (14, 15) are Proxy server and common server respectively .
15. The system (10) as claimed in claim 14, wherein said common server (15) includes components such as but not limited to KB handler component (29), intelligent search component (30), web profiler component (31) and data integrator (DIR) component (32) .
16. The system (10) as claimed in claim 15, wherein said KB handler component (29) includes an application for dealing with all interfaces to the knowledge database (19) and provides the functionality of adding, editing and deleting data from the knowledge database (19) .
17. The system (10) as claimed in claim 15, wherein said intelligent search component (30) includes an application to allow user to query the knowledge database (19) by using natural language.
18. The system (10) as claimed in claim 15, wherein said web profiler component (31) includes an application which allows for retrieval of information from the knowledge database.
19. The system (10) as claimed in claim 15, wherein said data integrator (DIR) component (32) includes an application to combine data residing at different sources and provides users with the unified view of these data.
20. The system (10) as claimed in claim 14, wherein said Proxy server (14) includes components such as but not limited to service proxy component (33) and service discovery and registry (SDAR) component ( 34 ) .
21. The system (10) as claimed in claim 20, wherein said service proxy component (33) includes an application that provides a single point of contact for the web service client to access web services.
22. The system (10) as claimed in claim 20, wherein said service discovery and registry (SDAR) component (34) includes an application to locate the components from the UDDI server (35) .
23. A method for providing integrated service delivery platform for multiple domains, said method comprising the steps of:
identifying (41) the required servers for running a requested application;
provoking (42) the identified servers;
registering (43) said identified servers to the UDDI sever (35) by the triggered servlet; and
executing the integrated platform (13) to perform said requested application.
24. The method as claimed in claim 23, wherein said step of executing the integrated platform (13) further comprising the steps of:
receiving request (44) by a Proxy server (14) from an application server ( 11 ) ;
locating servers (45) for performing the requested functions by said Proxy server (14);
connecting (47) to the servers of where the functions reside in; executing said requested functions by said identified servers; and returning results (52) to said application server (11) by said identified servers via said Proxy server (14).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MYPI2010001215A MY147279A (en) | 2010-03-18 | 2010-03-18 | Integrated service delivery platform system and method thereof |
MYPI2010001215 | 2010-03-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011115471A1 true WO2011115471A1 (en) | 2011-09-22 |
Family
ID=44649421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/MY2010/000262 WO2011115471A1 (en) | 2010-03-18 | 2010-11-10 | Integrated service delivery platform system and method thereof |
Country Status (2)
Country | Link |
---|---|
MY (1) | MY147279A (en) |
WO (1) | WO2011115471A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140173115A1 (en) * | 2012-12-13 | 2014-06-19 | Level 3 Communications, Llc | Responsibility-based Peering |
US20140372588A1 (en) | 2011-12-14 | 2014-12-18 | Level 3 Communications, Llc | Request-Response Processing in a Content Delivery Network |
US9634918B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation sequencing in a content delivery framework |
CN107862166A (en) * | 2017-12-12 | 2018-03-30 | 哈尔滨工业大学 | A kind of intelligent Simulation experiment design system and design method |
US10652087B2 (en) | 2012-12-13 | 2020-05-12 | Level 3 Communications, Llc | Content delivery framework having fill services |
US10701148B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having storage services |
US10701149B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having origin services |
US10791050B2 (en) | 2012-12-13 | 2020-09-29 | Level 3 Communications, Llc | Geographic location determination in a content delivery framework |
CN113726744A (en) * | 2021-08-02 | 2021-11-30 | 南京南瑞信息通信科技有限公司 | Visual safety alarm processing system and method based on task arrangement |
US11368548B2 (en) | 2012-12-13 | 2022-06-21 | Level 3 Communications, Llc | Beacon services in a content delivery framework |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040215711A1 (en) * | 2002-03-14 | 2004-10-28 | Openwave Systems Inc. | Mobile services platform architecture |
US20050164704A1 (en) * | 2004-01-23 | 2005-07-28 | Winsor Gerald W. | User profile service |
US20070150480A1 (en) * | 2005-04-11 | 2007-06-28 | Hans Hwang | Service delivery platform |
US20080140759A1 (en) * | 2006-03-21 | 2008-06-12 | Conner Peter A | Dynamic service-oriented architecture system configuration and proxy object generation server architecture and methods |
-
2010
- 2010-03-18 MY MYPI2010001215A patent/MY147279A/en unknown
- 2010-11-10 WO PCT/MY2010/000262 patent/WO2011115471A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040215711A1 (en) * | 2002-03-14 | 2004-10-28 | Openwave Systems Inc. | Mobile services platform architecture |
US20050164704A1 (en) * | 2004-01-23 | 2005-07-28 | Winsor Gerald W. | User profile service |
US20070150480A1 (en) * | 2005-04-11 | 2007-06-28 | Hans Hwang | Service delivery platform |
US20080140759A1 (en) * | 2006-03-21 | 2008-06-12 | Conner Peter A | Dynamic service-oriented architecture system configuration and proxy object generation server architecture and methods |
Cited By (68)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140372588A1 (en) | 2011-12-14 | 2014-12-18 | Level 3 Communications, Llc | Request-Response Processing in a Content Delivery Network |
US9451045B2 (en) | 2011-12-14 | 2016-09-20 | Level 3 Communications, Llc | Content delivery network |
US9456053B2 (en) | 2011-12-14 | 2016-09-27 | Level 3 Communications, Llc | Content delivery network |
US9516136B2 (en) | 2011-12-14 | 2016-12-06 | Level 3 Communications, Llc | Customer-specific request-response processing in a content delivery network |
US11838385B2 (en) | 2011-12-14 | 2023-12-05 | Level 3 Communications, Llc | Control in a content delivery network |
US11218566B2 (en) | 2011-12-14 | 2022-01-04 | Level 3 Communications, Llc | Control in a content delivery network |
US10841398B2 (en) | 2011-12-14 | 2020-11-17 | Level 3 Communications, Llc | Control in a content delivery network |
US10187491B2 (en) | 2011-12-14 | 2019-01-22 | Level 3 Communications, Llc | Request-response processing an a content delivery network |
US9722883B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Responsibility-based peering |
US9749192B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Dynamic topology transitions in a content delivery framework |
US9628347B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Layered request processing in a content delivery network (CDN) |
US9628346B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Devices and methods supporting content delivery with reducer services |
US9628343B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Content delivery framework with dynamic service network topologies |
US9634918B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation sequencing in a content delivery framework |
US9634907B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9634905B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation systems, methods, and devices |
US9634904B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Framework supporting content delivery with hybrid content delivery services |
US9634906B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9641402B2 (en) | 2012-12-13 | 2017-05-02 | Level 3 Communications, Llc | Configuring a content delivery network (CDN) |
US9641401B2 (en) | 2012-12-13 | 2017-05-02 | Level 3 Communications, Llc | Framework supporting content delivery with content delivery services |
US9647900B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Devices and methods supporting content delivery with delivery services |
US9647901B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Configuring a content delivery network (CDN) |
US9647899B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Framework supporting content delivery with content delivery services |
US9654354B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with delivery services network |
US9654353B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with rendezvous services network |
US9654356B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services |
US9654355B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with adaptation services |
US9661046B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services |
US9660876B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Collector mechanisms in a content delivery network |
US9660875B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with rendezvous services having dynamically configurable log information |
US9660874B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with delivery services having dynamically configurable log information |
US9667506B2 (en) | 2012-12-13 | 2017-05-30 | Level 3 Communications, Llc | Multi-level peering in a content delivery framework |
US9705754B2 (en) | 2012-12-13 | 2017-07-11 | Level 3 Communications, Llc | Devices and methods supporting content delivery with rendezvous services |
US9722882B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with provisioning |
US9628342B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Content delivery framework |
US9722884B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Event stream collector systems, methods, and devices |
US9749191B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Layered request processing with redirection and delegation in a content delivery network (CDN) |
US9628345B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Framework supporting content delivery with collector services network |
US9749190B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Maintaining invalidation information |
US9755914B2 (en) | 2012-12-13 | 2017-09-05 | Level 3 Communications, Llc | Request processing in a content delivery network |
US9787551B2 (en) * | 2012-12-13 | 2017-10-10 | Level 3 Communications, Llc | Responsibility-based request processing |
US9819554B2 (en) | 2012-12-13 | 2017-11-14 | Level 3 Communications, Llc | Invalidation in a content delivery framework |
US9847917B2 (en) | 2012-12-13 | 2017-12-19 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9887885B2 (en) | 2012-12-13 | 2018-02-06 | Level 3 Communications, Llc | Dynamic fill target selection in a content delivery framework |
US10135697B2 (en) | 2012-12-13 | 2018-11-20 | Level 3 Communications, Llc | Multi-level peering in a content delivery framework |
US10142191B2 (en) | 2012-12-13 | 2018-11-27 | Level 3 Communications, Llc | Content delivery framework with autonomous CDN partitioned into multiple virtual CDNs |
US9628344B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Framework supporting content delivery with reducer services network |
US10608894B2 (en) | 2012-12-13 | 2020-03-31 | Level 3 Communications, Llc | Systems, methods, and devices for gradual invalidation of resources |
US10652087B2 (en) | 2012-12-13 | 2020-05-12 | Level 3 Communications, Llc | Content delivery framework having fill services |
US10700945B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Role-specific sub-networks in a content delivery framework |
US10701148B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having storage services |
US10701149B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having origin services |
US10708145B2 (en) | 2012-12-13 | 2020-07-07 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback from health service |
US10742521B2 (en) | 2012-12-13 | 2020-08-11 | Level 3 Communications, Llc | Configuration and control in content delivery framework |
US10791050B2 (en) | 2012-12-13 | 2020-09-29 | Level 3 Communications, Llc | Geographic location determination in a content delivery framework |
US10826793B2 (en) | 2012-12-13 | 2020-11-03 | Level 3 Communications, Llc | Verification and auditing in a content delivery framework |
US10841177B2 (en) | 2012-12-13 | 2020-11-17 | Level 3 Communications, Llc | Content delivery framework having autonomous CDN partitioned into multiple virtual CDNs to implement CDN interconnection, delegation, and federation |
US20150180724A1 (en) * | 2012-12-13 | 2015-06-25 | Level 3 Communications, Llc | Dynamic fill target selection in a content delivery framework |
US10862769B2 (en) | 2012-12-13 | 2020-12-08 | Level 3 Communications, Llc | Collector mechanisms in a content delivery network |
US20140173115A1 (en) * | 2012-12-13 | 2014-06-19 | Level 3 Communications, Llc | Responsibility-based Peering |
US11368548B2 (en) | 2012-12-13 | 2022-06-21 | Level 3 Communications, Llc | Beacon services in a content delivery framework |
US10931541B2 (en) | 2012-12-13 | 2021-02-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with dynamically configurable log information |
US10992547B2 (en) | 2012-12-13 | 2021-04-27 | Level 3 Communications, Llc | Rendezvous systems, methods, and devices |
US11121936B2 (en) | 2012-12-13 | 2021-09-14 | Level 3 Communications, Llc | Rendezvous optimization in a content delivery framework |
US20140173131A1 (en) * | 2012-12-13 | 2014-06-19 | Level 3 Communications, Llc | Responsibility-based request processing |
CN107862166B (en) * | 2017-12-12 | 2020-12-11 | 哈尔滨工业大学 | Intelligent simulation experiment design system and design method |
CN107862166A (en) * | 2017-12-12 | 2018-03-30 | 哈尔滨工业大学 | A kind of intelligent Simulation experiment design system and design method |
CN113726744A (en) * | 2021-08-02 | 2021-11-30 | 南京南瑞信息通信科技有限公司 | Visual safety alarm processing system and method based on task arrangement |
Also Published As
Publication number | Publication date |
---|---|
MY147279A (en) | 2012-11-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011115471A1 (en) | Integrated service delivery platform system and method thereof | |
Michlmayr et al. | End-to-end support for QoS-aware service selection, binding, and mediation in VRESCo | |
US7958131B2 (en) | Method for data management and data rendering for disparate data types | |
US20140337372A1 (en) | Method of providing program using semantic mashup technology | |
US20120203734A1 (en) | Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata | |
US8849854B2 (en) | Method and system for providing detailed information in an interactive manner in a short message service (SMS) environment | |
JP2014527651A (en) | System and method for determining interpersonal influence information using text content from interpersonal dialogue | |
Makris et al. | Efficient and adaptive discovery techniques of web services handling large data sets | |
US9123021B2 (en) | Searching linked content using an external search system | |
Dustdar et al. | Adaptive service binding with lightweight semantic web services | |
Phalnikar et al. | Survey of QoS based web service discovery | |
JP2022096632A (en) | Computer-implemented method, computer system, and computer program (ranking datasets based on data attributes) | |
CN105653360A (en) | Method and system for cross-app function acquisition | |
CN111159590A (en) | Serial connection method and device based on front-end and back-end service call links | |
US20190347672A1 (en) | Memory augmentation in support of web interactions | |
Chiplunkar et al. | Dynamic Discovery of Web Services using WSDL | |
Criado et al. | Reusability and discovery models in software systems: a systematic literature review. | |
Zheng et al. | An intents-based approach for service discovery and integration | |
Bianchini et al. | Characterization and search of web services through intensional knowledge | |
US20230306436A1 (en) | Network computing system to implement content management platform for network services | |
Lau et al. | Semantic web service adaptation model for a pervasive learning scenario | |
Boukhadra et al. | DA5DCsws: a distributed architecture for semantic web services discovery and composition | |
Sinha et al. | On the fly integration of applications using context aware approach | |
Rykowski | Management of information changes by the use of software agents | |
Jayaprakash et al. | Semantic service selection using genetic algorithm |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10848061 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10848061 Country of ref document: EP Kind code of ref document: A1 |