WO2010043142A1 - 一种增强基于脚本业务的应用可靠性的方法、装置和*** - Google Patents
一种增强基于脚本业务的应用可靠性的方法、装置和*** Download PDFInfo
- Publication number
- WO2010043142A1 WO2010043142A1 PCT/CN2009/073804 CN2009073804W WO2010043142A1 WO 2010043142 A1 WO2010043142 A1 WO 2010043142A1 CN 2009073804 W CN2009073804 W CN 2009073804W WO 2010043142 A1 WO2010043142 A1 WO 2010043142A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- script
- data source
- information
- module
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method, apparatus and system for enhancing the reliability of application based on script services.
- Mashup is an emerging Web-based web-based data integration application, Mashup is ⁇ !
- Web API Application Programming Interface
- Mashup leverages content retrieved from external data sources to create entirely new and innovative services that combine content from more than one data source to create more value-added services.
- Mashup can take advantage of a variety of external data source formats, showing amazing compatibility, covering Public APIs (Public Application Programming Interfaces), XML (extensible Markup Language) / RSS ( Really Simple Syndication, aggregated content / aggregate format Atom and other language formats corresponding to interfaces feeds, Web server Web Services, HTML (HyperTextMark-upLanguage, Hypertext Markup Language or Hypertext Markup Language). It is widely believed that Mashup has the characteristics of Web 2.0, and Web 2.0 is a shared information platform built on the Internet. Mashup technology is also built on a variety of web applications that contribute their own services and content, while using information and services provided by others and other organizations.
- the current Mashup is mainly focused on how to create new applications based on existing sub-services and resources on the network.
- Mashup services are also becoming more and more abundant, and Mashup services available to ordinary users. It is also getting richer.
- quality assurance and management of the reliability of the Mashup business are becoming more and more difficult.
- the system cannot guarantee that the service can run normally, which seriously reduces the user experience for the Mashup application.
- the current Mashup server is a web integration platform that allows users to easily integrate data and functionality from any application with a web interface.
- the core function of Mashup is to present data and services to users, mainly including API/content providers, aggregate business servers, and aggregation service clients.
- the information content used by the aggregation service is not necessarily the content of the aggregation service server, or the data is obtained from the Web service by remote access, which is the most commonly used for the aggregation service.
- the Aggregation Business Server handles all functions, and all services and data required for the Aggregation application are called and processed by the server.
- the call to the Web service is also very common.
- the Aggregation Service Server is mainly responsible for editing and executing the application logic.
- the specific service call and data processing information is notified by the Aggregation Service Server to the service client, and then by the service client. Directly invoked and processed.
- WSDL Web Services Description Language
- Rest Real State Transfer
- the Mashup server cannot detect the data source of the Mashup service, and cannot obtain the update result of the data source information in time, and cannot guarantee the Mashup service.
- Availability reduced The application reliability of the Mashup service impairs the user experience.
- Embodiments of the present invention provide a method, an apparatus, and a system for enhancing application reliability of a script-based service, which are used to overcome a script server that cannot be detected by a script server similar to a Mashup server, and cannot acquire a data source in time.
- the problem of information update results, thereby achieving the effect of ensuring the availability of script-based services and enhancing the reliability of script-based services.
- an embodiment of the present invention provides a method for enhancing application reliability based on a script service, and the method includes the following steps:
- an embodiment of the present invention further provides a method for enhancing application reliability based on a script service, where the method includes the following steps:
- an embodiment of the present invention further provides a script-based service server, where the server includes:
- An analysis module configured to analyze data source information based on a script service
- An obtaining module configured to obtain current state information of the data source based on the script service according to the analysis result of the analysis module
- a determining module configured to determine the base according to current state information acquired by the acquiring module The available state of the script business.
- an embodiment of the present invention further provides a service access management system, where the system includes: a receiving module, configured to receive a status information subscription message sent by a script service server, and subscribe to state information of a data source based on a script service. ;
- a data source information obtaining module configured to subscribe to a message according to the status information received by the receiving module, and obtain status information of the data source based on the script service;
- a sending module configured to send current status information of the script service-based data source information acquired by the data source information obtaining module to the script-based service server.
- an embodiment of the present invention further provides a script-based service system, where the script-based service system includes a script-based service server and a service access management system:
- the script-based service server is configured to provide a script-based service to create, execute, and manage related functions, and subscribe the state of the script-based data source to the service access management system.
- the service access management system is configured to maintain information about a related data source on the network, and receive, and process, the subscription request based on the script service server.
- the technical solution of the embodiment of the present invention has the following advantages: by adding relevant analysis modules on the script-based service server, analyzing related data source information in the script-based business logic, and marking the available state of the data source based on the script service And detecting the status of the data source when the data source is unavailable, overcoming the problem that the script server cannot detect the application data source based on the script service, and cannot obtain the update information of the data source information in time, thereby ensuring the availability of the script-based service.
- the effect of the reliability of the script-based service is enhanced to ensure that the user can understand the state of the script-based service when requesting the service, avoid unnecessary service heuristics, save system resources, and improve the user experience.
- FIG. 1 is a schematic flowchart of a method for enhancing application reliability of a script-based service according to Embodiment 1 of the present invention
- FIG. 2 is a schematic flowchart of a method for enhancing application reliability of a script-based service according to Embodiment 2 of the present invention
- FIG. 3 is a schematic structural diagram of a script-based service system according to Embodiment 3 of the present invention
- FIG. 4 is a schematic structural diagram of a script-based service system including a Mashup server according to Embodiment 4 of the present invention
- FIG. 5 is a schematic flowchart of a process for creating an aggregation service based on the system according to Embodiment 5 of the present invention
- FIG. 6 is a schematic flowchart of a data source address and interface change process based on the system according to Embodiment 5 of the present invention.
- FIG. 7 is a schematic flowchart of a mashup service access process based on the system according to Embodiment 7 of the present invention.
- FIG. 8 is a schematic structural diagram of a networking of an aggregation service according to an embodiment of the present invention.
- the embodiment of the present invention mainly provides a solution for the problem that the script-based service server represented by the Mashup server cannot detect the data source based on the script service and cannot ensure the availability of the script-based service.
- the script-based service server By adding a related analysis module on the script-based service server, the information about the related data source (including the service, which is not distinguished in the text) in the script-based business logic is analyzed, and the script-based service is marked according to the analysis result for execution. Data source status verification based on the script service; further, when the data source corresponding to the script-based service is unavailable, the status of the data source is detected, and the status of the data source is subscribed to the service access management system. information, Therefore, the problem that the script server cannot detect the data source based on the script service and the data source information update result cannot be obtained in time, the effect of ensuring the availability of the script-based service is ensured, and the user can understand the script-based service when requesting the service.
- the state of avoiding unnecessary business heuristics causes the script service to be unavailable, and the update of the script-based business logic is automatically implemented by enhancing the conversion rules provided by the script service and the data source or other replacement sub-services. Enhance the usability of script-based services based on the flexibility of scripting services.
- FIG. 1 it is a schematic flowchart of a method for enhancing application-based reliability of a script-based service according to Embodiment 1 of the present invention, where the method includes the following steps:
- Step S101 Analyze data source information based on a script service.
- this step is triggered in the following two ways:
- the judging whether it is necessary to perform the available state detection on the script-based service is specifically performed by identifying the data source detection tag based on the script service.
- Step S102 Acquire current state information of the data source based on the script service according to the result of the analysis, which is specifically implemented by the following steps: And sending a status information subscription message to the service access management system according to the result of analyzing the data source information of the script service, and subscribing to the status information of the data source;
- the method further includes:
- the status information conversion rule reported by the service access management system is received, and the status information conversion rule includes the following contents:
- the current state information of the updated script service-based data source reported by the service access management system is received.
- Step S103 Determine, according to the obtained current state information, an available state based on the script service. It should be noted that, after the step, the step of saving the available state information of the script-based service may also be included, which is also within the protection scope of the present invention.
- this step specifically includes the following three situations:
- Case 3 When it is determined that the available state based on the script service is unavailable according to the obtained current state information, and the state information conversion rule reported by the service access management system is received, the current state of the script-based service is converted according to the state information conversion rule. The information is converted and matched, and when the conversion match is successful, the markup is available based on the available state of the script service. When the conversion match is unsuccessful, the markup is unavailable based on the available state of the script service.
- the following three cases are further included: in the case of receiving the script service-based creation request sent by the user side, returning the creation result based on the script service to the user side; or ,
- the state detection result based on the script service is returned to the user side.
- a registration access process of a third-party data source may be included, specifically:
- Access private service data from third-party data sources through a business adapter.
- FIG. 2 it is a schematic flowchart of a method for enhancing application-based reliability of a script service according to Embodiment 2 of the present invention, where the method includes the following steps:
- Step S201 Receive a status information subscription message sent by the script service server, and subscribe to status information of the data source based on the script service;
- Step S202 Subscribing a message according to the status information, and acquiring status information of the data source based on the script service;
- Step S203 Send current status information of the data source based on the script service to the script-based service server.
- step S203 may also be changed to status information and data source conversion rules of the script service-based data source that reports changes to the script-based service server.
- the technical solution of the embodiment of the present invention has the following advantages: receiving the subscription of the data source state information by the script service server, feeding back the current data source state information, and reporting the information change result when the data source information changes, overcoming the data source
- the change of information can not be timely feedback and management problems, and further through the reporting of data source conversion rules, the transformation of data source information is realized, the reliability of the script-based service is enhanced, the availability of script-based services is ensured, and the user can be guaranteed.
- you can understand the status of script-based services avoid unnecessary business heuristics, save system resources, and improve user experience.
- the present invention provides a script-based service system according to Embodiment 3, and a schematic structural diagram is shown in FIG. 3, including a script-based service server 1 and a service access management system 2:
- the script-based service server 1 is configured to provide a script-based service to create, execute, and manage related functions, and subscribe the status information of the data source based on the script service to the service access management system 2, including:
- the analyzing module 101 is configured to analyze data source information based on the script service;
- the obtaining module 102 is configured to obtain current state information of the data source information based on the script service according to the analysis result of the analysis module 101, and specifically includes:
- the sub-module 1021 is configured to send a status information subscription message to the service access management system 2 according to the result of analyzing the data source information of the script service according to the analysis module 101, and subscribe to the status information of the data source;
- the receiving sub-module 1022 is configured to receive current state information of the data source based on the script service reported by the service access management system 2, and/or a state information conversion rule for receiving the report 2 of the service access management system.
- the determining module 103 is configured to determine, according to the current state information acquired by the obtaining module 102, an available state based on the script service.
- script-based business server 1 also includes:
- the storage module 104 is configured to save, by the judging module 103, a judgment result of the available state based on the script service according to the available state information based on the script service. It should be noted that in the actual application scenario, the storage module 104 can be set in the script-based service server 1 or on other servers. Such a defense does not affect the scope of protection of the present invention.
- the first receiving module 105 is configured to receive a script service-based creation request sent by the user side, where the second receiving module 106 is configured to receive the execution request of the script-based service by the user side, or receive the available status detection of the script-based service. request.
- the service self-management module 107 is configured to generate, according to the execution request of the script-based service by the user-side, the second-side receiving module 106, to generate an available state detection request for the script-based service, and specifically includes: an identifier sub-module 1071, configured to identify the script-based The current available status of the business;
- the determining sub-module 1072 is configured to: when the identification sub-module 1071 identifies that the current available state of the script-based service is unavailable, determine whether the available state detection is required for the script-based service;
- the detecting sub-module 1073 is configured to generate an available state detecting request for the script-based service when the determining result of the sub-module 1072 is that the state-of-the-art detection is required for the script-based service.
- the data source conversion module 108 is configured to: when the determining module 103 determines that the available state based on the script service is unavailable, and the receiving submodule 1022 receives the state information conversion rule reported by the service access management system 2, according to the state information conversion rule The conversion is matched based on the current state information of the script service.
- script-based business server 1 also includes:
- the first sending module 109 is configured to: when the first receiving module 105 receives the script service-based creation request sent by the user side, return a script service-based creation result to the user side; the service execution module 110 is configured to When the receiving module 106 receives the execution request of the script service based on the user side, when the determining module 103 determines that the available state based on the script service is available, performing the script-based service;
- the second sending module 111 is configured to: when the second receiving module 106 receives the execution request of the script service based on the user side, return the execution result of the service execution module 110 to the script-based service to the user side,
- the state detection result based on the script service is returned to the user side.
- the data source adaptation module 112 is configured to provide a non-open data source access function, and provide a data source adapter for the third party service provider to implement the access function of the script-based service server to the third-party private data source.
- the service access management system 2 is configured to maintain information of a data source on the network, and receive, and process, a subscription request based on the script service server 1.
- the service access management system 2 is further configured to: when the state information of the data source based on the script service changes, the status information and the data source conversion rule of the data source based on the script service reported by the script service server 1 include: :
- the receiving module 21 is configured to receive a status information subscription message sent by the script service server 1, and subscribe to status information of the data source based on the script service;
- the data source information obtaining module 22 is configured to subscribe according to the status information received by the receiving module 21 a message, obtaining state information of a data source based on the script service;
- the sending module 23 is configured to send, to the script-based service server 1, the current state information of the data source information based on the script service acquired by the data source information acquiring module 22.
- the sending module 23 is further configured to report the status information and the data source conversion rule of the changed script service-based data source to the script-based service server 1 when the status information of the data source based on the script service changes.
- the service access management system 2 further includes:
- the data source information module 24 is configured to store data source information based on the script service.
- the above modules may be distributed in one device or distributed in multiple devices.
- the above modules can be combined into one module, or they can be split into multiple sub-modules.
- a storage module may be added to save the markup result, which provides a basis for subsequent verification of the script-based service availability, and overcomes the problem that the script-based server cannot detect based on The problem with the current state of the data source of the script business;
- the obtaining module can also perform state detection and adaptation on the data source when the state of the data source is unavailable, and overcome the problem that the script server cannot obtain the update result of the data source information in time;
- the third-party data source is adapted by the data source adaptation module, and the effective expansion of multiple script-based services is realized;
- the effect of ensuring the availability of the script-based service and the reliability of the script-based service are ensured, and the user can understand the state of the script-based service when requesting the service, and avoid unnecessary effects of the business trial. It saves system resources and improves the user experience.
- the above devices and systems can make corresponding changes and changes, and the above modules can be combined into one module, or can be further divided into multiple sub-modules.
- FIG. 4 is a schematic structural diagram of a script-based service system including a mashup server according to Embodiment 4 of the present invention, including a mashup server 41 and a service access management system 42.
- the mashup server 41 mainly includes a service access dynamic control module 411, a mashup execution system 412, a portal 413, a service self-management module 414, a service creation module 415, a service storage module 416, a data source analysis module 417, a data source adaptation module 418, and data.
- Source conversion module 419 mainly includes a service access dynamic control module 411, a mashup execution system 412, a portal 413, a service self-management module 414, a service creation module 415, a service storage module 416, a data source analysis module 417, a data source adaptation module 418, and data.
- Source conversion module 419 mainly includes a service access dynamic control module 411, a mashup execution system 412, a portal 413, a service self-management module 414, a service creation module 415, a service storage module 416, a data source analysis module 417, a data source adaptation module 418, and data. Source conversion
- the Portal 413, the service creation module 415, and the Mashup execution system 412 are no different from the normal Mashup server.
- the service access dynamic control module 411 mainly analyzes the user's request information to obtain the mashup application to be accessed by the user, and then detects the corresponding mashup application state information. If the mashup service is available, the service execution system is requested to execute the mashup service logic; if the mashup application state is unavailable According to the service detection label, it is determined whether the status of the corresponding data source needs to be detected, and if necessary, the data source information is detected, and if necessary, data source conversion can be performed on the Mashup business logic, and then the service status is available, and the service execution system is requested to be executed. The mashup business logic, otherwise immediately notify the user that the mashup service is unavailable.
- the service self-management module 414 mainly provides the Mashup service management function for the end user, and the user can actively request the service data source analysis module 417 to detect the service data source and update the status information of the Mashu service.
- the service storage module 416 In addition to being responsible for saving the mashup business logic, the service storage module 416 also stores the state of the mashup service logic (available, unavailable, etc.) and the data source information of the mashup service, data detection tags, and the like.
- the data source conversion module 419 will associate the relevant mashup business logic according to the data source conversion rules.
- the part of the data source is called for conversion processing so that it can adapt to the new interface rules provided by the data source or be replaced with other equivalent data sources.
- the service data source analysis module 417 is responsible for analyzing the data source information used by the Mashup business logic, and saving the data source information together with the Mashup business logic to the service storage module 416. When the status of the data source changes, the module will analyze the data in time. Affected Mashup business logic, and update the status of related business logic. If necessary, the data source conversion module 419 may be called to update the original Mashup business logic according to the data source conversion rule provided by the data source, and update the data source calling interface to a new interface or replace with another equivalent data source, thereby maximizing The limit guarantees the availability of Mashup business logic.
- the data source adaptation module 418 mainly provides a private non-open source access function. There are many functions on the network that do not provide an open interface. In order for the Mashup service to use these data sources, a third party is required to provide an adapter. The Mashup service provides access to the data source of a third-party private interface.
- the adapter here can be a packaged code or a dynamic library for use by the Mashup server.
- the Data Source Adaptation Module 418 supports third-party active registration of data source adapters to assist third-party service providers in better promoting their services and data sources.
- the service access dynamic control module 411 can be equivalent to the set of three module functions of the analysis module 101, the second receiving module 106, and the second sending module 111, and the mashup execution system 412
- the service execution module 110 is equivalent to the function of the first receiving module 105 and the first sending module 109.
- the service self-management module 414 is a self-management module 107.
- the service storage module 416 is equivalent to the storage module 104 and the data source.
- the analysis module 417 is equivalent to the function module of the acquisition module 102 and the determination module 103.
- the data source adaptation module 418 is equivalent to the data source adaptation module 112, and the data source conversion module 419 is equivalent to the data source conversion module 108. It affects the scope of protection of the present invention.
- the service access management system 42 mainly includes a data source information module 421 and a data source management module 422.
- the data source information module 421 is configured to store related data source interfaces, states, and equivalent candidate sub-services, and the like.
- the data source management module 422 is mainly responsible for acquiring related data source capabilities, and processing the data source information subscription of the mashup server 41. request.
- the data source information module 421 stores and provides data source conversion rules, and if necessary, can provide equivalent replacement sub-service interfaces.
- the most conversion rules ensure that the Mashup business logic fails in the original sub-service failure (interface change, service exit).
- the data source information module 421 can be equivalent to the data source information module 24, and the data source management module 422 is equivalent to the receiving module 21, the data source information acquiring module 22, and the sending module 23.
- the data source management module 422 is equivalent to the receiving module 21, the data source information acquiring module 22, and the sending module 23.
- the technical solution of the embodiment of the present invention has the following advantages: by adding a related analysis module on the Mashup server, the information about the relevant data source (including the service) in the Mashup service logic is analyzed, and the Mashup service is marked, thereby achieving the guarantee. Users can understand the status of the Mashup service when requesting services, avoid unnecessary effects of business trials, save system resources, and improve the user experience.
- the fifth embodiment of the present invention provides an aggregation service creation process based on the system.
- the method includes the following steps: Step S501: A user creates a service through a mashup service. The environment creates a mashup application; Step S502: When the mashup server receives the new mashup service created by the user, analyzes the related data source information invoked by the service, and if the mashup service does not subscribe to the data source information, subscribes to the service access management system. Relevant data source information;
- Step S503 The service access management system receives the subscription request, returns the relevant data source information according to the data source status, and subsequently changes the related data source information (such as status, address, interface, alternative equivalent service, etc.) This information will still be reported to the management system.
- related data source information such as status, address, interface, alternative equivalent service, etc.
- Step S504 the mashup server saves the business logic and related data source information, and the root According to the data source information, it is determined whether the current Mashup service logic is available, and the information is saved, and the Mashup service creation result is reported to the user (if the creation is successful, immediately available, or temporarily unavailable);
- the service access management system can collect and obtain data source information through relevant channels and manage the data source.
- the technical solution of the embodiment of the present invention has the following advantages: analyzing and subscribing the state information of the data source (including the service) in the logic of the newly created mashup service, and realizing the judgment and identification of the available state of the data source, Therefore, the timely identification and update of the available state information of the data source of the Mashup service is achieved, and the effect of the availability of the Mashup service is ensured.
- the sixth embodiment of the present invention proposes a data source address and interface change process based on the system, as shown in FIG. 6, which includes the following steps:
- Step S601 The service access management system learns the result of the data source status, the address, and the interface change (for example, the data source report address, the interface change), and requests the report address and the interface change notification message (including the data source) based on the subscription request of the Mashup server. Address, interface change information, old address, interface to new address, interface rule information, alternative equivalent data source, etc.).
- Step S602 The service data source analysis module of the Mashup server updates the available state of the related Mashup service logic according to the relationship between the Mashup service and the data source. If there is a related address and interface conversion rule, the data source conversion module is invoked to convert the Mashup business logic.
- Step S603 The data source conversion module of the mashup server processes the related mashup service logic according to the related address and the interface conversion rule (the protocol, the parameter type, the parameter order, and the like, and the alternative equivalent data source). Convert the successful Mashup service recovery to the available tags.
- the technical solution of the embodiment of the present invention has the following advantages: by receiving the subscription of the data source state information, and timely reporting the current state information of the data source and the subsequent change of the state information, the The status information of the corresponding data source and the accuracy of the corresponding available state on the mashup server, so as to ensure that the user can understand the state of the mashup service when requesting the service, avoid unnecessary service trials, and save system resources. Improved user experience.
- the seventh embodiment of the present invention provides a mashup service access process based on the system.
- the method includes the following steps: Step S701: A user requests to perform a mashup service logic.
- Step S702 The mashup service detects an available state of the related business logic, and executes the logic if available; if not, determines the data source detection label, and returns an unavailable prompt information to the user if the data is unavailable; if further inspection is required The data source status is followed by a subsequent step.
- Step S703 The mashup server requests the service access management system to report the data source information.
- the service access management system performs related processing according to the collected data source information.
- Step S704 The service access management system reports data source information (including an address, an interface conversion rule, an alternative sub-service replacement rule, and the like).
- Step S705 If the Mashup service finds that there is a problem with the data source status, returning the Mashup business logic unavailable prompt message to the user. If the data source address and interface change, the Mashup server updates the relevant business logical address, the interface calling code, and the Mashup business logic state is available. The Mashup server executes the updated business logic, and the third-party private address and interface, Mashup can The method is adapted by the data source adaptation module (the adaptation logic can be registered by a third party).
- Step S706 The mashup server returns a business logic execution result.
- the technical solution of the embodiment of the present invention has the following advantages: by performing a data source available state detection in a process of executing a mashup service, and further performing a state information update on an unavailable data source, the guaranteed user can request During business, you can understand the status of the Mashup service, avoid unnecessary business trials, save system resources, and improve user usage. Test.
- the present invention further provides an embodiment for understanding and implementing the environment. Based on the network structure shown in FIG. 8, the embodiment of the present invention The specific content of the proposed technical solution is as follows:
- Users can access and access related services on the Mashup server through a computer or mobile terminal. Users can create various Mashup services by means of the creation module of the Mashup service providing service. This example assumes that User A wants to send a special greeting card to his wife on the wedding anniversary. Since the user has been on a business trip, he has made a beautiful electronic rose in advance and posted it to the photo sharing service, in order to commemorate it. On the day of the day, I sent the prepared blessing information and greeting card to my wife. He created a mashup application through the Mashup server to automatically send the greeting card to his wife's mailbox.
- the main content is "I am now” + getl OC ation (information receiving terminal number) +"Business trip, today is the wedding anniversary, I personally made a greeting card for you, I hope you like it, and send a text message to remind your wife, and give yourself feedback on the results.
- the network service involved in this example is extremely networking.
- the service router SR/service gateway GW completes the service access management system function and maintains related information such as picture sharing service, location service, and MMS service. These service routers and gateways can logically connect to each other to form a network for better. Service and related applications.
- Mashup server can pass SR The GW subscribes to and queries the information about the specific sub-service.
- the message service is used as an example.
- the message service provider registers the SMS adaptation object with the data source adapter of the Mashup service, and the user can pass the message.
- Send( to, message ) The address and interface send a message, where to indicates the destination and message indicates the content of the message.
- the business logic created by user A through the service creation module of the Mashup server is as follows:
- the Mashup service saves state-related information about the business logic.
- the sub-service information maintained by the service router or gateway is referred to as the message service content as follows
- the message service provider wants to increase the sender identification information, change the address and interface of the message service, and as a message service provider, he cares about which existing Mashup service will call himself. He is only responsible for publishing.
- the new address, interface user can send a message through the send (from, to, message) address, interface, where the new from represents the sender ID. This will result in an existing Mashup service and may not be able to continue using the service.
- the message service provider also issues new and old addresses and interface conversion rules, and allows default as the default parameter for the old service.
- the conversion rule send. trans example is as follows:
- ⁇ /SubService> reports the sms (SMS) service status information (including the address and interface translation rules) to the Mashup service.
- SMS sms
- the Mashup service finds that the user A's Mashup service invokes the message service according to the saved service status information, and the Mashup server passes the data.
- the source address and interface conversion module convert the Mashup business logic.
- the converted logical fragments are as follows:
- the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both.
- the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Telephonic Communication Services (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Description
本申请要求 2008年 10月 17日递交的申请号为 20081 0167276.3、 发 明名称为 "一种增强基于脚本业务的应用可靠性的方法、 装置和***" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域,特别是涉及一种增强基于脚本业务的应用可 靠性的方法、 装置和***。
背景技术
聚合业务 Mashup是一种新兴的基于环球网 Web的数据集成应用, Mashup是^!每多个不同的支持 Web API (Application Programming Interface,应 用程序编程接口) 的应用进行堆叠、 聚合形成的新型的 Web应用。 Mashup 利用了从外部数据源检索到的内容来创建全新的创新服务,将来自不止一个 数据源的内容进行组合,创造出更加增值的服务。 Mashup所能利用的外部数 据源格式多种多样, 表现出惊人的兼容性, 涵盖 Public APIs ( Public Application Programming Interfaces, 公共应用程序编程接口) , XML ( extensible Markup Language , 可扩展标记语言) /RSS ( Really Simple Syndication, 聚合内容) /聚合格式 Atom等语言格式对应的接口 feeds , 环球 网服务器 Web Services, HTML ( HyperTextMark-upLanguage , 超文本标记语 言或超文本链接标示语言) 等。 人们普遍认为 Mashup具有 Web 2.0的特点, Web 2.0是在互联网上建立起共享信息平台。 Mashup技术也是建立在各种 Web应用程序贡献出自己的服务和内容, 同时使用其他人和其他组织提供的 信息和服务的基础上的。 随着越来越多的 Web站点公开了自己的 API, 许多 人已经在用 eBay, Amazon, Google 和 Yahoo APIs构建新的 Mashups, 使得 这种新型的 Web应用模式成为了现实。
Mashup业务越来越流行, 未来可能成为电信、互联网融合业务生成、创 建的一个重要模式;
目前的 Mashup主要关注于如何基于网络上已有的子业务和资源来组合 创建新的应用, 随着用户逐渐大量参与到 Mashup业务创建中, Mashup业务 也越来越丰富, 普通用户可用的 Mashup业务也越来越丰富。 但随着 Mashup 业务的***式增长, 对 Mashup业务的可靠性等质量保证和管理也越来越困 难。用户在使用 Mashup业务前***无法保证该业务是否可正常运行,严重降 低了对 Mashup应用的用户体验。
目前通常的 Mashup服务器是一个 Web集成平台,允许用户轻松集成来自 任意具有 Web接口的应用程序的数据和功能。
在现有的 Mashup应用架构中, Mashup的核心功能就是将数据和业务集 中起来展示给用户, 主要包括 API/内容提供者、 聚合业务服务器以及聚合业 务客户端。对于现有技术中的应用架构而言, 聚合业务所使用的信息内容并 不一定是聚合业务服务器本地的内容, 也可以是通过远程访问的方式从 Web 服务获取数据, 这是聚合业务最常用的一种, 通称为内容聚合。 在这种情况 下, 聚合业务服务器负责处理所有功能, 聚合应用需要的所有服务和数据都 由服务器进行调用和数据处理。 另外, 对于 Web服务的调用也很常见, 在这 种情况下, 聚合业务服务器主要负责编辑和执行应用逻辑, 具体的业务调用 和数据处理信息由聚合业务服务器通知业务客户端, 再由业务客户端直接进 行调用并处理, 目前互联网上基于 WSDL ( Web Services Description Language, Web服务描述语言)的 Web服务和基于 Rest (Representational State Transfer, 代表性状态通讯协议)的 Web服务很多, 这些服务都提供清晰的调 用 API, 也为聚合业务提供了丰富的选择。
在实现本发明的过程中, 发明人发现现有技术至少存在以下问题: 在现有技术中, Mashup服务器不能检测 Mashup业务的数据源, 也不能 及时获取数据源信息的更新结果, 无法保证 Mashup业务的可用性, 降低了
Mashup业务的应用可靠性, 损害了用户的使用体验。
发明内容
本发明实施例提供了一种增强基于脚本业务的应用可靠性的方法、 装 置和***, 用于克服和 Mashup服务器相类似的基于脚本服务器不能检测基 于脚本业务的数据源, 也不能及时获取数据源信息更新结果的问题, 从而达 到确保基于脚本业务的可用性, 增强基于脚本业务的可靠性的效果。
为达到上述目的, 本发明实施例一方面提出一种增强基于脚本业务的应 用可靠性的方法, 所述方法包括以下歩骤:
分析基于脚本业务数据源的信息;
根据所述分析的结果, 获取所述基于脚本业务数据源信息的当前状态信 息;
根据所述获取的当前状态信息, 判断所述基于脚本业务的可用状态。 另一方面,本发明实施例还提出一种增强基于脚本业务的应用可靠性的 方法, 所述方法包括以下歩骤:
接收基于脚本业务服务器发送的状态信息订阅消息, 订阅基于脚本业务 的数据源的状态信息;
根据所述状态信息订阅消息, 获取所述基于脚本业务的数据源的状态信 息;
向所述基于脚本业务服务器发送所述基于脚本业务的数据源信息的当 前状态信息。
另一方面, 本发明实施例还提出一种基于脚本业务服务器, 所述服务器 包括:
分析模块, 用于分析基于脚本业务的数据源信息;
获取模块, 用于根据所述分析模块分析的结果, 获取所述基于脚本业务 的数据源的当前状态信息;
判断模块, 用于根据所述获取模块所获取的当前状态信息, 判断所述基
于脚本业务的可用状态。
另一方面,本发明实施例还提出一种业务接入管理***,所述***包括: 接收模块, 用于接收基于脚本业务服务器发送的状态信息订阅消息, 订 阅基于脚本业务的数据源的状态信息;
数据源信息获取模块,用于根据所述接收模块所接收的状态信息订阅消 息, 获取所述基于脚本业务的数据源的状态信息;
发送模块,用于向所述基于脚本业务服务器发送所述数据源信息获取模 块所获取的基于脚本业务的数据源信息的当前状态信息。
另一方面, 本发明实施例还提出一种基于脚本业务***, 所述基于脚本 业务***包括基于脚本业务服务器和业务接入管理***:
所述基于脚本业务服务器, 用于提供基于脚本业务创建、 执行和管理相 关功能, 并向所述业务接入管理***订阅所述基于脚本业务的数据源的状态
^ I 自、 .;
所述业务接入管理***, 用于维护网络上相关数据源的信息, 并接收、 和处理所述基于脚本业务服务器的订阅请求。
本发明实施例的技术方案具有以下优点,通过在基于脚本业务服务器上 增加相关的分析模块, 实现对基于脚本业务逻辑中相关数据源信息进行分 析, 对基于脚本业务的数据源的可用状态进行标记, 并在数据源不可用时对 该数据源进行状态检测, 克服了基于脚本服务器无法检测基于脚本业务的应 用数据源, 不能及时获取数据源信息的更新信息的问题, 从而达到确保基于 脚本业务的可用性, 增强基于脚本业务的可靠性的效果, 保证用户在请求业 务时可以了解基于脚本业务的状态, 避免不必要的业务试探的效果, 节约了 ***资源, 改善了用户的使用体验。
附图说明
此处所说明的附图用来提供对本发明的进一歩理解, 构成本申请的一部 分, 并不构成对本发明的限定。 在附图中:
图 1为本发明实施例一所提出的一种增强基于脚本业务的应用可靠性的 方法的流程示意图;
图 2为本发明实施例二所提出的一种增强基于脚本业务的应用可靠性的 方法的流程示意图;
图 3为本发明实施例三所提出的一种基于脚本业务***的结构示意图; 图 4为本发明实施例四所提出的一种包含 Mashup服务器的基于脚本 业务***的结构示意图;
图 5 为本发明实施例五所提出的基于本***的聚合业务创建流程的 流程示意图;
图 6 为本发明实施例五所提出的基于本***的数据源地址、 接口变 更流程的流程示意图;
图 7为本发明实施例七所提出的基于本***的 Mashup业务访问流程 的流程示意图;
图 8为本发明实施例中一种聚合业务的组网结构示意图。
具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚明白, 下面结合实 施例和附图, 对本发明实施例做进一歩详细说明。 在此, 本发明的示意性实 施例及其说明用于解释本发明, 但并不作为对本发明的限定。
本发明实施例主要针对以 Mashup服务器为代表的基于脚本业务服务器 无法检测基于脚本业务的数据源, 不能确保基于脚本业务的可用性的问题, 提供了解决方案。
通过在基于脚本业务服务器上增加相关的分析模块, 实现对基于脚本业 务逻辑中相关数据源(包括业务, 本文不再区分)信息进行分析, 根据分析 结果对该基于脚本业务进行标记以供执行该基于脚本业务时进行数据源状 态验证; 进一歩的, 还可以在该基于脚本业务所对应的数据源不可用时, 对 该数据源进行状态检测, 并向业务接入管理***订阅该数据源的状态信息,
从而, 克服了基于脚本服务器不能检测基于脚本业务的数据源, 也不能及时 获取数据源信息更新结果的问题, 达到确保基于脚本业务的可用性的效果, 保证用户可以在请求业务时可以了解基于脚本业务的状态,避免不必要的业 务试探。另外针对基于脚本业务的数据源之间接口变动导致基于脚本业务不 可用的问题,通过增强基于脚本业务和数据源提供的转换规则或者其他替换 子业务, 自动实现对基于脚本业务逻辑的更新,提供基于脚本业务的灵活性, 增强基于脚本业务的可用性。
在本发明实施例中, 为了方便说明, 具体以 Mashup业务为例, 来说明 本发明实施例对于基于脚本业务所提出的技术方案的内容, 而这样的说明, 也仅是本发明的优选实施例, 这样的变化并不影响本发明的保护范围。
实施例一
如图 1所示, 为本发明实施例一所提出的一种增强基于脚本业务的应用 可靠性的方法的流程示意图, 该方法包括以下歩骤:
歩骤 S101、 分析基于脚本业务的数据源信息。
其中, 本歩骤具体通过以下两种方式触发:
( 1 ) 接收用户侧发送的基于脚本业务的创建请求; 或,
(2) 接收对基于脚本业务的可用状态检测请求, 具体包括:
当接收用户侧对基于脚本业务的执行请求, 并识别基于脚本业务的当前 可用状态为不可用时, 判断是否需要对基于脚本业务进行可用状态检测, 并 当判断的结果为需要对基于脚本业务进行可用状态检测时, 生成对基于脚本 业务的可用状态检测请求; 或,
接收用户侧直接发送的对基于脚本业务的可用状态检测请求。
其中, 判断是否需要对基于脚本业务进行可用状态检测, 具体通过识别 基于脚本业务的数据源检测标签来进行判断。
歩骤 S102、 根据分析的结果, 获取基于脚本业务的数据源的当前状态 信息, 具体通过以下歩骤实现:
根据分析基于脚本业务的数据源信息的结果, 向业务接入管理***发送 状态信息订阅消息, 订阅数据源的状态信息;
接收业务接入管理***上报的基于脚本业务的数据源的当前状态信息。 其中, 接收当前状态信息的同时, 还包括:
接收业务接入管理***上报的状态信息转换规则,状态信息转换规则具 体包括以下内容:
( 1 ) 将状态信息的已失效的地址、 接口转换为更新后的地址、 接口的
^ I 自、 .;
(2) 备选数据源替换规则, 用于将基于脚本业务中使用的已失效的数 据源信息替换为其他更新后的数据信息。
并且, 进一歩的, 当基于脚本业务的数据源信息发生变更时, 接收业务 接入管理***上报的更新的基于脚本业务的数据源的当前状态信息。
歩骤 S103、 根据获取的当前状态信息, 判断基于脚本业务的可用状态。 需要说明的是, 本歩骤之后还可以包括保存该基于脚本业务的可用状态 信息的歩骤, 这同样属于本发明的保护范围。
进一歩的, 本歩骤具体包括以下三种情况:
情况一、 当根据获取的当前状态信息, 判断基于脚本业务的可用状态为 可用时, 标记基于脚本业务的可用状态为可用;
情况二、 当根据获取的当前状态信息, 判断基于脚本业务的可用状态为 不可用, 且未接收到业务接入管理***上报的状态信息转换规则时, 标记基 于脚本业务的可用状态为不可用;
情况三、 当根据获取的当前状态信息, 判断基于脚本业务的可用状态为 不可用, 且接收到业务接入管理***上报的状态信息转换规则时, 根据状态 信息转换规则对基于脚本业务的当前状态信息进行转换匹配, 并当转换匹配 成功时, 标记基于脚本业务的可用状态为可用, 当转换匹配不成功时, 标记 基于脚本业务的可用状态为不可用。
对应上述的接收信息情况, 在歩骤 S 103之后, 还包括以下三种情况: 在接收到用户侧发送的基于脚本业务的创建请求的情况下, 向用户侧返 回基于脚本业务的创建结果; 或,
在接收用户侧对基于脚本业务的执行请求的情况下, 当基于脚本业务的 可用状态为可用时, 执行基于脚本业务, 当基于脚本业务的可用状态为不可 用时, 放弃执行基于脚本业务, 并向用户侧返回基于脚本业务的不可执行提 示信息; 或,
接收用户侧直接发送的对基于脚本业务的可用状态检测请求的情况下, 向用户侧返回基于脚本业务的状态检测结果。
需要进一歩说明的是, 在歩骤 S 101方法之前还可以包括第三方数据源 的注册接入过程, 具体为:
接收第三方数据源发送的业务适配器注册请求;
通过业务适配器访问第三方数据源的私有服务数据。
本发明实施例的技术方案具有以下优点:
通过分析基于脚本业务的数据源的信息, 以订阅的方式获取该数据源相 对应的状态信息, 根据状态信息对该基于脚本业务的数据源标记可用状态, 可选的, 还可以对标记结果保存, 为后续的基于脚本业务可用性的检验提供 依据, 克服了基于脚本服务器无法检测基于脚本业务的数据源的当前状态的 问题;
在数据源的状态为不可用时, 对该数据源进行状态检测和适配, 克服了 基于脚本服务器不能及时获取数据源信息更新结果的问题;
通过第三方数据源适配, 实现了对多种基于脚本业务的有效扩展; 通过上述的多项技术措施, 达到确保基于脚本业务的可用性, 增强基于 脚本业务的可靠性的效果,保证用户可以在请求业务时可以了解基于脚本业 务的状态, 避免不必要的业务试探的效果, 节约了***资源, 改善了用户的 使用体验。
实施例二
如图 2所示, 为本发明实施例二所提出的一种增强基于脚本业务的应用 可靠性的方法的流程示意图, 该方法包括以下歩骤:
歩骤 S201、 接收基于脚本业务服务器发送的状态信息订阅消息, 订阅 基于脚本业务的数据源的状态信息;
歩骤 S202、 根据状态信息订阅消息, 获取基于脚本业务的数据源的状 态信息;
歩骤 S203、 向基于脚本业务服务器发送基于脚本业务的数据源的当前 状态信息。
其中, 当基于脚本业务的数据源的状态信息发生变化时, 歩骤 S203还 可以变化为向基于脚本业务服务器上报变化的基于脚本业务的数据源的状 态信息和数据源转换规则。
本发明实施例的技术方案具有以下优点, 通过接收基于脚本业务服务器 对于数据源状态信息的订阅, 反馈当前的数据源状态信息, 并在数据源信息 发生变化时上报信息变化结果, 克服了数据源信息的变化不能及时反馈和进 行管理的问题, 并进一歩的通过上报数据源转换规则, 实现数据源信息的变 更转换, 增强了基于脚本业务的可靠性, 确保了基于脚本业务的可用性, 保 证用户可以在请求业务时可以了解基于脚本业务的状态,避免不必要的业务 试探的效果, 节约了***资源, 改善了用户的使用体验。
实施例三
对应上述的本发明实施例一和实施例二,本发明通过实施例三提出一种 基于脚本业务***, 结构示意图如图 3所示, 包括基于脚本业务服务器 1和 业务接入管理*** 2:
基于脚本业务服务器 1, 用于提供基于脚本业务创建、 执行和管理相关 功能, 并向业务接入管理*** 2订阅基于脚本业务的数据源的状态信息, 包 括:
分析模块 101, 用于分析基于脚本业务的数据源信息;
获取模块 102, 用于根据分析模块 101所分析的结果, 获取基于脚本业 务的数据源信息的当前状态信息, 具体包括:
订阅子模块 1021,用于根据分析模块 101分析基于脚本业务的数据源信 息的结果, 向业务接入管理*** 2发送状态信息订阅消息, 订阅数据源的状 态信息;
接收子模块 1022,用于接收业务接入管理*** 2上报的基于脚本业务的 数据源的当前状态信息,和 /或用于接收业务接入管理***上报 2的状态信息 转换规则。
判断模块 103, 用于根据获取模块 102所获取的当前状态信息, 判断基 于脚本业务的可用状态。
进一歩的, 基于脚本业务服务器 1还包括:
存储模块 104, 用于保存判断模块 103根据基于脚本业务的可用状态信 息, 对基于脚本业务的可用状态的判断结果。 需要指出的是, 在实际应用场 景中, 存储模块 104可以设置于基于脚本业务服务器 1中, 也可以设置于其 他服务器上, 这样的辩护并不影响本发明的保护范围。
第一接收模块 105, 用于接收用户侧发送的基于脚本业务的创建请求; 第二接收模块 106, 用于接收用户侧对基于脚本业务的执行请求, 或, 接收对基于脚本业务的可用状态检测请求。
业务自管理模块 107, 用于根据第二接收模块 106接收到用户侧对基于 脚本业务的执行请求,生成对基于脚本业务的可用状态检测请求,具体包括: 识别子模块 1071, 用于识别基于脚本业务的当前可用状态;
判断子模块 1072, 用于当识别子模块 1071识别基于脚本业务的当前可 用状态为不可用时, 判断是否需要对基于脚本业务进行可用状态检测;
检测子模块 1073, 用于当判断子模块 1072的判断结果为需要对基于脚 本业务进行可用状态检测时, 生成对基于脚本业务的可用状态检测请求。
数据源转换模块 108, 用于当判断模块 103判断基于脚本业务的可用状 态为不可用, 且接收子模块 1022接收到业务接入管理*** 2上报的状态信 息转换规则时,根据状态信息转换规则对基于脚本业务的当前状态信息进行 转换匹配。
进一歩的, 基于脚本业务服务器 1还包括:
第一发送模块 109, 用于在第一接收模块 105接收到用户侧发送的基于 脚本业务的创建请求的情况下, 向用户侧返回基于脚本业务的创建结果; 业务执行模块 110, 用于在第二接收模块 106接收用户侧对基于脚本业 务的执行请求的情况下, 当判断模块 103判断基于脚本业务的可用状态为可 用时, 执行基于脚本业务;
第二发送模块 111, 用于在第二接收模块 106接收用户侧对基于脚本业 务的执行请求的情况下, 向用户侧返回业务执行模块 110对基于脚本业务的 执行结果,
或,用于在第二接收模块 106接收用户侧直接发送的对基于脚本业务的 可用状态检测请求的情况下, 向用户侧返回基于脚本业务的状态检测结果。
数据源适配模块 112, 用于提供一个非开放的数据源接入功能, 为第三 方业务提供者提供一个数据源适配器, 以实现基于脚本业务服务器对第三方 私有数据源的访问功能。
业务接入管理*** 2, 用于维护网络上数据源的信息, 并接收、 和处理 基于脚本业务服务器 1的订阅请求。
其中, 业务接入管理*** 2, 还用于当基于脚本业务的数据源的状态信 息发生变化时, 向基于脚本业务服务器 1上报变化的基于脚本业务的数据源 的状态信息和数据源转换规则包括:
接收模块 21, 用于接收基于脚本业务服务器 1 发送的状态信息订阅消 息, 订阅基于脚本业务的数据源的状态信息;
数据源信息获取模块 22, 用于根据接收模块 21所接收的状态信息订阅
消息, 获取基于脚本业务的数据源的状态信息;
发送模块 23, 用于向基于脚本业务服务器 1 发送数据源信息获取模块 22所获取的基于脚本业务的数据源信息的当前状态信息。
进一歩的, 发送模块 23还用于当基于脚本业务的数据源的状态信息发 生变化时, 向基于脚本业务服务器 1上报变化的基于脚本业务的数据源的状 态信息和数据源转换规则。
进一歩的, 业务接入管理*** 2还包括:
数据源信息模块 24, 用于存储基于脚本业务的数据源信息。
上述模块可以分布于一个装置, 也可以分布于多个装置。 上述模块 可以合并为一个模块, 也可以进一歩拆分成多个子模块。
本发明实施例的技术方案具有以下优点:
通过在基于脚本服务器上增加相关的分析模块、获取模块和判断模块等 多个功能模块, 分析基于脚本业务的数据源的信息, 以订阅的方式获取该数 据源相对应的状态信息, 根据状态信息对该基于脚本业务的数据源标记可用 状态, 可选的, 还可以增加存储模块, 用以对标记结果进行保存, 为后续的 基于脚本业务可用性的检验提供依据, 克服了基于脚本服务器无法检测基于 脚本业务的数据源的当前状态的问题;
并且, 获取模块还可以在数据源的状态为不可用时, 对该数据源进行状 态检测和适配, 克服了基于脚本服务器不能及时获取数据源信息更新结果的 问题;
通过数据源适配模块对第三方数据源适配, 实现了对多种基于脚本业务 的有效扩展;
通过上述的多项技术措施, 达到确保基于脚本业务的可用性, 增强基于 脚本业务的可靠性的效果,保证用户可以在请求业务时可以了解基于脚本业 务的状态, 避免不必要的业务试探的效果, 节约了***资源, 改善了用户的 使用体验。
在实际的应用场景中, 上述的装置和***可以作出相应的更改和变 化, 上述模块可以合并为一个模块, 也可以进一歩拆分成多个子模块。
实施例四
如图 4所示,为本发明实施例四所提出的一种包含 Mashup服务器的 基于脚本业务***的结构示意图, 包括 Mashup服务器 41和业务接入管理 *** 42。
Mashup服务器 41主要包含业务访问动态控制模块 411、Mashup执行 *** 412、 Portal 413、 业务自管理模块 414、 业务创建模块 415、 业务存 储模块 416、 数据源分析模块 417、 数据源适配模块 418、 数据源转换模 块 419。
其中 Portal 413、 业务创建模块 415和 Mashup执行*** 412与普通 的 Mashup服务器没有区别。
业务访问动态控制模块 411 主要分析用户的请求信息得到用户要访 问的 Mashup应用, 然后检测对应的 Mashup应用状态信息, 如果 Mashup 业务可用就请求业务执行***执行该 Mashup业务逻辑; 如果该 Mashup 应用状态不可用则进一歩根据业务检测标签判断是否需要检测对应数据 源状态, 如果需要则检测数据源信息, 必要时可以对 Mashup业务逻辑进 行数据源转换匹配, 然后标记业务状态可用, 并请求业务执行***执行 该 Mashup业务逻辑, 否则立即通知用户该 Mashup业务不可用。
业务自管理模块 414主要为最终用户提供 Mashup业务管理功能,用 户可以主动请求业务数据源分析模块 417 对业务数据源进行检测, 更新 Mashu 业务的状态信息。
业务存储模块 416除了负责保存 Mashup业务逻辑, 还保存 Mashup 业务逻辑的状态 (可用、 不可用等) 以及 Mashup业务的数据源信息, 数 据检测标签等。
数据源转换模块 419将根据数据源转换规则对相关 Mashup业务逻辑
中调用数据源的部分进行转换处理, 使之可以适应数据源提供的新的接 口规则或是替换为其他等价数据源。
业务数据源分析模块 417负责分析 Mashup业务逻辑所使用的数据源 信息, 并把数据源信息和 Mashup业务逻辑一起保存到业务存储模块 416 中, 当数据源状态发生变化时, 该模块将及时分析出受影响的 Mashup业 务逻辑, 并更新相关业务逻辑的状态。 必要时还可以根据数据源提供的 数据源转换规则调用数据源转换模块 419对原有 Mashup业务逻辑进行更 新处理, 把数据源调用接口更新为新的接口或替换为其他等价数据源, 从而最大限度的保障 Mashup业务逻辑的可用。
数据源适配模块 418 主要提供一个私有非开放的源接入功能, 网络 上有很多功能不提供开放的接口,为了让 Mashup服务也可以使用这些数 据源, 需要第三方提供一个适配器, 该适配器实现 Mashup服务对第三方 私有接口的数据源的访问功能, 这里的适配器可以是一段封装好的代码 或动态程序库供 Mashup服务器使用。数据源适配模块 418支持第三方主 动注册数据源适配器, 以协助第三方服务提供者更好的推广其服务和数 据源。
通过上述的描述, 对应上述的本发明实施例三, 业务访问动态控制 模块 411可以相当于分析模块 101、 第二接收模块 106和第二发送模块 111 三个模块功能上的集合, Mashup执行*** 412相当于业务执行模块 110, Portal 413相当于第一接收模块 105和第一发送模块 109功能上的集合, 业 务自管理模块 414业务自管理模块 107, 业务存储模块 416相当于存储模 块 104、 数据源分析模块 417相当于获取模块 102和判断模块 103功能上 的集合、 数据源适配模块 418相当于数据源适配模块 112、 数据源转换模 块 419相当于数据源转换模块 108,这样的变化并不影响本发明的保护范围。
业务接入管理*** 42主要包括数据源信息模块 421和数据源管理模 块 422。
其中, 数据源信息模块 421 用于存储相关数据源接口、 状态、 等价 备选子服务等相关信息, 数据源管理模块 422 主要负责获取相关数据源 能力, 并处理 Mashup服务器 41的数据源信息订阅请求。
同时数据源信息模块 421 存储和提供数据源转换规则, 必要时可以 提供等价可替换子业务接口最为转换规则保证 Mashup 业务逻辑在原始 子服务失败 (接口变化、 服务退出) 可以正常运行。
通过上述的描述, 对应上述的本发明实施例三, 数据源信息模块 421 可以相当于数据源信息模块 24, 数据源管理模块 422相当于接收模块 21, 数据源信息获取模块 22和发送模块 23功能上的集合, 这样的变化并不影响 本发明的保护范围。
本发明实施例的技术方案具有以下优点, 通过在 Mashup服务器上增加 相关的分析模块, 实现对 Mashup业务逻辑中相关数据源 (包括业务) 信息 进行分析, 对 Mashup业务进行标记, 从而, 达到了保证用户可以在请求业 务时可以了解 Mashup业务的状态, 避免不必要的业务试探的效果, 节约了 ***资源, 改善了用户的使用体验。
实施例五
基于上述的本发明实施例四所提出的***, 本发明实施例五提出了 基于本***的聚合业务创建流程, 具体如图 5所示, 包括以下歩骤: 歩骤 S501、 用户通过 Mashup业务创建环境创建 Mashup应用; 歩骤 S502、 Mashup服务器接收到用户创建的新 Mashup服务时, 分 析该服务所调用的相关数据源信息,如果 Mashup服务没有订阅该数据源 信息, 则向业务接入管理***订阅相关数据源信息;
歩骤 S503、 业务接入管理***并接收订阅请求, 根据数据源状态, 返回相关数据源信息, 后续如果相关数据源信息变动 (如状态、 地址、 接口、 备选等价服务等), 业务接入管理***依然会上报这些信息。
歩骤 S504、 Mashup服务器保存业务逻辑和相关数据源信息, 以及根
据数据源信息判断当前 Mashup业务逻辑是否可用, 并保存该信息, 同时 向用户反馈 Mashup 业务创建结果 (如创建成功, 立即可用或暂不可用 等);
需要进一歩指出的是, 业务接入管理***可以通过相关途径收集获 取数据源信息, 并对数据源进行管理。
本发明实施例的技术方案具有以下优点, 通过对新创建的 Mashup业务 的逻辑中相关数据源 (包括业务) 信息进行分析和订阅数据源的状态信息, 实现对数据源可用状态的判断和标识, 从而, 达到了 Mashup业务的数据源 的可用状态信息的及时标识和更新, 保证 Mashup业务可用性的效果。
实施例六
基于上述的本发明实施例四所提出的***, 本发明实施例六提出了 基于本***的数据源地址、 接口变更流程, 具体如图 6 所示, 包括以下 歩骤:
歩骤 S601、 业务接入管理***获知数据源状态、 地址、 接口变动的 结果 (例如: 数据源上报地址、 接口更改) 并基于 Mashup服务器的订阅 请求要求上报地址、 接口更改通知消息 (包含数据源地址、 接口变动信 息, 老地址、 接口转换为新地址、 接口的规则信息、 备选等价数据源等)。
歩骤 S602、 Mashup服务器的业务数据源分析模块根据 Mashup业务 与数据源关系更新相关 Mashup业务逻辑的可用状态, 如果有相关地址、 接口转换规则, 则调用数据源转换模块对 Mashup业务逻辑进行转换。
歩骤 S603、 Mashup服务器的数据源转换模块根据相关的地址、 接口 转换规则 (协议、 参数类型、 参数顺序等变化、 备选等价数据源), 对相 关的 Mashup业务逻辑进行处理, 完成后对转换成功的 Mashup业务恢复 可用标记。
本发明实施例的技术方案具有以下优点,通过接收数据源状态信息的订 阅, 和对数据源的当前状态信息和后续的状态信息变化的及时上报, 保证了
Mashup服务器上对应数据源的状态信息和对应的可用状态的准确性, 从而, 达到了保证用户可以在请求业务时可以了解 Mashup业务的状态, 避免不必 要的业务试探的效果, 节约了***资源, 改善了用户的使用体验。
实施例七
基于上述的本发明实施例四所提出的***, 本发明实施例七提出了 基于本***的 Mashup业务访问流程, 具体如图 7所示, 包括以下歩骤: 歩骤 S701、 用户请求执行 Mashup业务逻辑。
歩骤 S702、 Mashup服务检测相关业务逻辑的可用状态, 如果可用就 执行该逻辑; 如果不可用, 则判断数据源检测标签, 如果数据不可用则 向用户返回不可用提示信息; 如果需要进一歩检测数据源状态, 则执行 后续歩骤。
歩骤 S703、 Mashup 服务器请求业务接入管理***上报数据源细信 息。 业务接入管理***根据收集的数据源信息做相关处理。
歩骤 S704、 业务接入管理***上报数据源信息 (包括地址、 接口转 化规则、 备选子服务替换规则等)。
歩骤 S705、 如果 Mashup服务发现数据源状态有问题, 则向用户返 回 Mashup 业务逻辑不可用提示信息。 如果是数据源地址、 接口变动, Mashup服务器更新相关业务逻辑地址、 接口调用代码, 并更 Mashup业 务逻辑状态为可用, Mashup服务器执行该更新后的业务逻辑, 对第三方 私有地址、 接口, Mashup可以通过数据源适配模块来方法 (适配逻辑可 有第三方注册进来)。
歩骤 S706、 Mashup服务器返回业务逻辑执行结果。
本发明实施例的技术方案具有以下优点, 通过在执行 Mashup业务的过 程中进行数据源可用状态检测, 并进而对不可用的数据源进行状态信息更新 的技术方案,,达到了保证用户可以在请求业务时可以了解 Mashup业务的状 态, 避免不必要的业务试探的效果, 节约了***资源, 改善了用户的使用体
验。
实施例八
为了使本领域技术人员更加清楚的了解上述实施例中记载的技术方 案, 具体的, 本发明还提出了解和具体实施环境的实施例, 基于如图 8 所示的网络结构, 本发明实施例所提出的技术方案的具体内容如下:
用户可以通过计算机或移动终端接入并访问 Mashup 服务器上的相 关服务。 用户可以借助于 Mashup 服务提供业务的创建模块创建各种 Mashup服务。本实例假设用户 A想在结婚纪念日给他妻子发送一份特别 的贺卡, 由于用户一直出差在外, 他提前制作了一张精美的电子玫瑰, 并发布到图片共享服务上, 为了能恰好在纪念日那天把准备好的祝福信 息和贺卡发送给妻子, 他在酒店通过 Mashup服务器创建了一个 mashup 应用自动发送贺卡到老婆的邮箱,主要内容是"我现在在" + getlOCation (信 息接收终端号码) +"出差, 今天是结婚纪念日, 我亲手做了一个贺卡送 给你, 希望你喜欢, 并发送手机短信提醒妻子, 同时给自己反馈结果信 息。 该实例所涉及的网络服务极其组网情况如上图所示。业务路由器 SR/ 业务网关 GW完成业务接入管理***功能, 维护图片共享服务、 位置服 务、 彩信服务等相关信息。 这些业务路由器、 网关逻辑上可以相互连接 组成网络以便更好的服务与相关应用。 Mashup服务器可以通过 SR、 GW 订阅、 查询相关具体子服务的信息。 这里以消息服务为例, 为了使得 Mashup服务器可以简单的调用消息服务, 消息服务提供者向 Mashup服 务的数据源适配器注册了 SMS适配对象,用户可以通过 send( to, message ) 地址、 接口发送消息, 其中 to表示发送目标, message表示消息内容。
用户 A通过 Mashup服务器的业务创建模块创建的业务逻辑如下:
*my mashup
function sendEmail(to, message, attached=null)〃发由 β件
{
var em = new Email();
if(attached=null)
em.send(to, message);
else
em.send(to, message, attached);
im.disconnect();
}
function sendSMS(from, to , message)// 发短信 {
var sms = new SMS();
sms.send(to, message);
sms.disconnect();
}
function file getfile(name)// 读耳又贺卡 {
var file = new file(name)
return file;
}
function string getlocation(usr)
{
var location = new LCS(usr)
return location.getlocation();
}
while ( true ) {
date = getDay()
If(date = "20080808")
{
File file = getfile(Jrose.jpg);
var message = "我现在在" + getlocation (接收终端号码) +"出 今天是结婚纪念日, 我亲手做了一个贺卡送给你, 希望你喜欢"
sendEmail([email protected], message, file)
sendEmail( 136XXXXXXXX , "我给你发了电子贺卡,请查收") sendEmail( 135XXXXXXXX, "发送电子贺卡成功")
exit;
}
} Mashup服务保存该业务逻辑的状态相关信息
<?xml version:" 1.0" encoding="UTF-8"?>
<mashups>
<name = "sendrose">
<state = "OK">
<checktag = "200808-08:08">
<subservice = "SMS">
<state = "OK">
<subservice>
<subservice = "Photos">
<state = "OK">
<subservice>
<subservice = "Location">
<staet = "OK">
<subservice>
</mashup> 业务路由器或网关维护的子业务信息以消息服务内容参考如下
<?xml version:" 1.0" encoding="UTF-8"?>
<SubService>
<name = "Photos">
<state = "OK">
<subscribed = "Yes">
<InterfaceChanged = "NO">
<rule>
Null
</rule>
</InterfaceChanged>
</SubService>
这样用户 A就可以执行上述 Mashup业务逻辑实现自己的需求。 为了进一歩完善服务, 消息服务提供者想增加发送者标识信息, 改 变了消息服务的地址、 接口, 作为消息服务提供者他并关心有哪些已有 的 Mashup服务会调用了自己, 他只负责发布新的地址、 接口, 用户可以 通过 send ( from, to , message) 地址、 接口发送消息, 其中新增的 from 表示发送者标识。 这样就导致已有的 Mashup服务, 可能无法继续使用该 服务。 消息服务提供者为了方便老服务对消息进行转换, 同时发布了新 老地址、 接口转换规则, 对老业务允许用 default作为默认参数。 其中转 换规则 send. trans示例如下:
<?xml version:" 1.0" encoding="UTF-8"?>
<Transform>
<match = "SMS()">
<for-each select=var >
<replace $var.send>
$ var. send(default , $parameterl , $parameter2)
</replace
</for-each >
</Transform>
业务接入管理服务收集到上述 SMS服务信息状态改变的消息后, 根 据相关的订阅信息作特殊处理。 更新 SMS服务状态。
<?xml version:" 1.0" encoding="UTF-8"?>
<SubService>
<name = "Photos">
<state = "OK">
<subscribed = "Yes">
<InterfaceChanged = "NO">
<rule>
Send, trans
</rule>
</InterfaceChanged>
</SubService> 上报 sms (短信)服务状态信息 (包括地址、接口转换规则)给 Mashup 服务, Mashup服务根据保存的服务状态信息, 发现用户 A的 Mashup服 务调用了该消息服务, 则 Mashup服务器通过数据源地址、 接口转换模块 对该 Mashup业务逻辑进行转换。 转换后的逻辑片断如下:
*my mashup
function sendEmail(to , message, attached=null)〃发由 tH牛
{
var em = new Email();
if(attached=null)
em.send(to, message);
else
em.send(to, message, attached);
im.disconnect();
}
function sendSMS(from, to , message)// 发短信
{
var sms = new SMS();
sms.send(default, to , message);
sms.disconnect();
}
综上所述, 结合本文中所公开的实施例描述的方法或算法的歩骤可以直 接用硬件、 处理器执行的软件模块, 或者二者的结合来实施。 软件模块可以 置于随机存储器(RAM)、 内存、 只读存储器(ROM)、 电可编程 ROM、 电 可擦除可编程 ROM、 寄存器、 硬盘、 可移动磁盘、 CD-ROM、 或技术领域 内所公知的任意其它形式的存储介质中。
以上所述的具体实施例, 对本发明的目的、 技术方案和有益效果进行了 进一歩详细说明, 所应理解的是, 以上所述仅为本发明的具体实施例而已, 并不用于限定本发明的保护范围, 凡在本发明的精神和原则之内, 所做的任 何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1、 一种增强基于脚本业务的应用可靠性的方法, 其特征在于, 所述方 法包括以下歩骤:
分析基于脚本业务的数据源的信息;
根据所述分析的结果, 获取所述基于脚本业务的数据源的当前状态信 息;
根据所述获取的当前状态信息, 判断所述基于脚本业务的可用状态。
2、 如权利要求 1所述的方法, 其特征在于, 所述分析基于脚本业务的 数据源信息的歩骤, 具体通过以下方式触发:
接收用户侧发送的所述基于脚本业务的创建请求; 或,
接收对所述基于脚本业务的可用状态检测请求。
3、 如权利要求 2所述的方法, 其特征在于, 所述接收对基于脚本业务 的可用状态检测请求, 具体包括:
当接收所述用户侧对所述基于脚本业务的执行请求, 并识别所述基于脚 本业务的当前可用状态为不可用时,判断是否需要对所述基于脚本业务进行 可用状态检测, 并当所述判断的结果为需要对所述基于脚本业务进行可用状 态检测时, 生成对所述基于脚本业务的可用状态检测请求; 或,
接收所述用户侧直接发送的对所述基于脚本业务的可用状态检测请求。
4、 如权利要求 3所述的方法, 其特征在于, 所述判断是否需要对所述 基于脚本业务进行可用状态检测, 具体为:
通过识别所述基于脚本业务的数据源检测标签判断是否需要对所述基 于脚本业务进行可用状态检测。
5、 如权利要求 1所述的方法, 其特征在于, 所述获取所述基于脚本业 务的数据源的当前状态信息, 具体通过以下歩骤实现:
根据所述分析基于脚本业务的数据源信息的结果, 向业务接入管理*** 发送状态信息订阅消息, 订阅所述数据源的状态信息;
接收所述业务接入管理***上报的所述基于脚本业务的数据源的当前 状态信息。
6、 如权利要求 5所述的方法, 其特征在于, 所述接收业务接入管理系 统上报的所述基于脚本业务的数据源的当前状态信息的同时, 还包括: 接收所述业务接入管理***上报的状态信息转换规则,所述状态信息转 换规则具体包括:
将所述状态信息的已失效的地址、 接口转换为更新后的地址、 接口的信
M; 或,
备选数据原替换规则,用于将所述基于脚本业务中使用的已失效的数据 源信息替换为其他更新后的数据信息。
7、 如权利要求 5所述的方法, 其特征在于, 所述接收业务接入管理系 统上报的所述基于脚本业务的数据源的当前状态信息之后, 还包括:
当所述基于脚本业务的数据源信息发生变更时,接收所述业务接入管理 ***上报的更新的所述基于脚本业务的数据源的当前状态信息。
8、 如权利要求 1或 6所述的方法, 其特征在于, 所述根据获取的当前 状态信息, 判断所述基于脚本业务的可用状态, 并保存所述基于脚本业务的 可用状态信息, 具体包括以下歩骤:
当根据获取的当前状态信息,判断所述基于脚本业务的可用状态为可用 时, 标记所述基于脚本业务的可用状态为可用;
当根据获取的当前状态信息,判断所述基于脚本业务的可用状态为不可 用, 且未接收到所述业务接入管理***上报的状态信息转换规则时, 标记所 述基于脚本业务的可用状态为不可用;
当根据获取的当前状态信息,判断所述基于脚本业务的可用状态为不可 用, 且接收到所述业务接入管理***上报的状态信息转换规则时, 根据所述 状态信息转换规则对所述基于脚本业务的当前状态信息进行转换匹配, 并当 所述转换匹配成功时, 标记所述基于脚本业务的可用状态为可用, 当所述转
换匹配不成功时, 标记所述基于脚本业务的可用状态为不可用。
9、 如权利要求 1所述的方法, 其特征在于, 所述根据获取的当前状态 信息, 判断所述基于脚本业务的可用状态之后, 还包括:
保存所述基于脚本业务的可用状态信息。
10、 如权利要求 2、 3或 9中所述的方法, 其特征在于, 所述根据获取 的当前状态信息,判断所述基于脚本业务的可用状态之后,还包括以下歩骤: 在接收到用户侧发送的所述基于脚本业务的创建请求的情况下, 向所述 用户侧返回所述基于脚本业务的创建结果; 或,
在接收所述用户侧对所述基于脚本业务的执行请求的情况下, 当所述基 于脚本业务的可用状态为可用时, 执行所述基于脚本业务, 当所述基于脚本 业务的可用状态为不可用时, 放弃执行所述基于脚本业务, 并向所述用户侧 返回所述基于脚本业务的不可执行提示信息; 或,
接收所述用户侧直接发送的对所述基于脚本业务的可用状态检测请求 的情况下, 向所述用户侧返回所述基于脚本业务的状态检测结果。
11、 如权利要求 1所述的方法, 其特征在于, 在所述分析基于脚本业务 的数据源的信息之前, 所述方法还包括:
接收第三方数据源发送的业务适配器注册请求;
基于脚本的业务服务器通过所述业务适配器访问所述第三方数据源的 私有服务数据。
12、 一种增强基于脚本业务的应用可靠性的方法, 其特征在于, 所述方 法包括以下歩骤:
接收基于脚本业务服务器发送的状态信息订阅消息, 订阅基于脚本业务 的数据源的状态信息;
根据所述状态信息订阅消息, 获取所述基于脚本业务的数据源的状态信 息;
向所述基于脚本业务服务器发送所述基于脚本业务的数据源的当前状
态信息。
13、 如权利要求 12所述的方法, 其特征在于, 在所述向基于脚本业务 服务器发送所述基于脚本业务的数据源的当前状态信息的歩骤中包括:
向所述基于脚本业务服务器发送数据源信息转换规则。
14、 一种基于脚本业务服务器, 其特征在于, 所述服务器包括: 分析模块, 用于分析基于脚本业务的数据源的信息;
获取模块, 用于根据所述分析模块分析的结果, 获取所述基于脚本业务 的数据源的当前状态信息;
判断模块, 用于根据所述获取模块所获取的当前状态信息, 判断所述基 于脚本业务的可用状态。
15、 如权利要求 14所述的服务器, 其特征在于, 所述服务器还包括: 存储模块,用于保存所述判断模块根据所述基于脚本业务的可用状态信 息, 对所述基于脚本业务的可用状态的判断结果。
16、 如权利要求 14所述的服务器, 其特征在于, 所述服务器还包括: 第一接收模块, 用于接收用户侧发送的所述基于脚本业务的创建请求; 第二接收模块, 用于接收所述用户侧对所述基于脚本业务的执行请求, 或, 接收对所述基于脚本业务的可用状态检测请求。
17、 如权利要求 16所述的服务器, 其特征在于, 所述服务器还包括: 业务自管理模块,用于根据所述第二接收模块接收到所述用户侧对所述 基于脚本业务的执行请求, 生成对所述基于脚本业务的可用状态检测请求。
18、 如权利要求 17所述的服务器, 其特征在于, 所述业务自管理模块, 具体包括:
识别子模块, 用于识别所述基于脚本业务的当前可用状态;
判断子模块,用于当所述识别子模块识别所述基于脚本业务的当前可用 状态为不可用时, 判断是否需要对所述基于脚本业务进行可用状态检测; 检测子模块,用于当所述判断子模块的判断结果为需要对所述基于脚本
业务进行可用状态检测时, 生成对所述基于脚本业务的可用状态检测请求。
19、 如权利要求 14所述的服务器, 其特征在于, 所述获取模块, 具体 包括:
订阅子模块,用于根据所述分析模块分析所述基于脚本业务的数据源信 息的结果, 向业务接入管理***发送状态信息订阅消息, 订阅所述数据源的 状态信息;
接收子模块,用于接收所述业务接入管理***上报的所述基于脚本业务 的数据源信息的当前状态信息,和 /或用于接收所述业务接入管理***上报的 状态信息转换规则。
20、 如权利要求 14或 19所述的服务器, 其特征在于, 所述服务器还包 括:
数据源转换模块,用于当所述判断模块判断所述基于脚本业务的可用状 态为不可用, 且所述接收子模块接收到所述业务接入管理***上报的状态信 息转换规则时,根据所述状态信息转换规则对所述基于脚本业务的当前状态 信息进行转换匹配。
21、 如权利要求 14或 16所述的服务器, 其特征在于, 所述服务器还包 括:
第一发送模块,用于在所述第一接收模块接收到用户侧发送的所述基于 脚本业务的创建请求的情况下, 向所述用户侧返回所述基于脚本业务的创建 结果;
业务执行模块,用于在所述第二接收模块接收所述用户侧对所述基于脚 本业务的执行请求的情况下, 当所述判断模块判断所述基于脚本业务的可用 状态为可用时, 执行所述基于脚本业务;
第二发送模块,用于在所述第二接收模块接收所述用户侧对所述基于脚 本业务的执行请求的情况下, 向所述用户侧返回所述业务执行模块对所述基 于脚本业务的执行结果, 或, 用于在所述第二接收模块接收所述用户侧直接
发送的对所述基于脚本业务的可用状态检测请求的情况下, 向所述用户侧返 回所述基于脚本业务的状态检测结果。
22、 如权利要求 14所述的服务器, 其特征在于, 所述服务器还包括: 数据源适配模块, 用于提供一个非开放的数据源接入功能, 为第三方业 务提供者提供一个数据源适配器, 以实现所述基于脚本业务服务器对第三方 私有数据源的访问功能。
23、一种业务接入管理***,其特征在于,所述业务接入管理***包括: 接收模块, 用于接收基于脚本业务服务器发送的状态信息订阅消息, 订 阅基于脚本业务的数据源的状态信息;
数据源信息获取模块,用于根据所述接收模块所接收的状态信息订阅消 息, 获取所述基于脚本业务的数据源的状态信息;
发送模块,用于向所述基于脚本业务服务器发送所述数据源信息获取模 块所获取的基于脚本业务的数据源的当前状态信息。
24、 如权利要求 23所述的业务接入管理***, 其特征在于, 所述发送 模块, 还用于当所述基于脚本业务的数据源的状态信息发生变化时, 向所述 基于脚本业务服务器上报变化的所述基于脚本业务的数据源的状态信息和 数据源转换规则。
25、 如权利要求 23所述的业务接入管理***, 其特征在于, 所述业务 接入管理***还包括:
数据源信息模块, 用于存储所述基于脚本业务的数据源信息。
26、 一种基于脚本业务***, 其特征在于, 所述基于脚本业务***包括 基于脚本业务服务器和业务接入管理***:
所述基于脚本业务服务器, 用于提供基于脚本业务创建、 执行和管理功 會 , 并向所述业务接入管理***订阅所述基于脚本业务的数据源的状态信 息;
所述业务接入管理***, 用于维护网络上数据源的信息, 并接收、 和处
理所述基于脚本业务服务器的订阅请求。
27、 如权利要求 26所述的基于脚本业务***, 其特征在于,
所述业务接入管理***,还用于当所述基于脚本业务的数据源的状态信 息发生变化时, 向所述基于脚本业务服务器上报变化的所述基于脚本业务的 数据源的状态信息和数据源转换规则。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09820218.7A EP2352083B1 (en) | 2008-10-17 | 2009-09-08 | Method, device and system for enhancing script-based application reliability |
US13/086,835 US8453158B2 (en) | 2008-10-17 | 2011-04-14 | Method, apparatus, and system for enhancing application reliability of a script-based service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810167276.3 | 2008-10-17 | ||
CN200810167276.3A CN101729491B (zh) | 2008-10-17 | 2008-10-17 | 一种增强基于脚本业务的应用可靠性的方法、装置和*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/086,835 Continuation US8453158B2 (en) | 2008-10-17 | 2011-04-14 | Method, apparatus, and system for enhancing application reliability of a script-based service |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010043142A1 true WO2010043142A1 (zh) | 2010-04-22 |
Family
ID=42106225
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073804 WO2010043142A1 (zh) | 2008-10-17 | 2009-09-08 | 一种增强基于脚本业务的应用可靠性的方法、装置和*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US8453158B2 (zh) |
EP (1) | EP2352083B1 (zh) |
CN (1) | CN101729491B (zh) |
WO (1) | WO2010043142A1 (zh) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101626363B (zh) * | 2008-07-07 | 2013-03-27 | 华为技术有限公司 | 聚合业务装置、***、聚合业务创建及使用方法 |
US8555351B2 (en) * | 2008-09-29 | 2013-10-08 | International Business Machines Corporation | Trusted database authentication through an untrusted intermediary |
US9110577B1 (en) * | 2009-09-30 | 2015-08-18 | Software AG USA Inc. | Method and system for capturing, inferring, and/or navigating dependencies between mashups and their data sources and consumers |
CN101951402B (zh) * | 2010-09-17 | 2013-02-20 | 山东中创软件工程股份有限公司 | 一种Web Service可用性跟踪检测方法、装置及*** |
CN103369012B (zh) * | 2012-04-09 | 2017-12-08 | 中兴通讯股份有限公司 | 一种业务逻辑执行装置和方法 |
US10360188B2 (en) | 2012-07-27 | 2019-07-23 | International Business Machines Corporation | Dynamic property data integration framework |
KR20140095903A (ko) * | 2013-01-25 | 2014-08-04 | 한국전자통신연구원 | 사용자 디바이스 기반 매쉬업 서비스 제공 방법 및 장치 |
CN103716206B (zh) * | 2013-12-30 | 2017-10-03 | 中国烟草总公司湖南省公司 | 业务***运行的监控方法及服务器 |
CN104702664B (zh) * | 2014-12-29 | 2020-01-03 | 惠州Tcl移动通信有限公司 | 控制任务服务器的方法及*** |
US10235146B1 (en) | 2015-09-30 | 2019-03-19 | EMC IP Holding Company LLC | Method and mechanism for composite data service generation and implementation |
CN107992347B (zh) * | 2017-10-24 | 2021-03-16 | 维沃移动通信有限公司 | 一种功能演示方法及移动终端 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1728149A (zh) * | 2004-06-01 | 2006-02-01 | 微软公司 | 用于发现并连接到数据源的方法、***和装置 |
US20070055693A1 (en) * | 2005-09-07 | 2007-03-08 | Simon Galbraith | Data recovery method |
CN101005502A (zh) * | 2007-01-25 | 2007-07-25 | 华为技术有限公司 | 业务脚本获取、控制方法及其控制***和媒体资源服务器 |
CN101202665A (zh) * | 2007-12-06 | 2008-06-18 | 中兴通讯股份有限公司 | 图形用户界面的生成方法 |
WO2008075883A1 (en) * | 2006-12-18 | 2008-06-26 | Internet Channel21 Co., Ltd. | Advertisement method by the proxy server and advertisement system operating the advertisement method |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030105846A1 (en) * | 2001-11-30 | 2003-06-05 | Koninklijke Philips Electronics N.V. | Enhanched UDDI with service push model |
CN1299200C (zh) | 2003-12-26 | 2007-02-07 | 中兴通讯股份有限公司 | 电信网管***中接口数据统一转换的方法及其*** |
US20050198206A1 (en) * | 2004-01-30 | 2005-09-08 | International Business Machines Corporation | Method and apparatus for dynamically selecting functionally equivalent Web services through a single autonomic proxy |
WO2005114411A1 (en) * | 2004-05-21 | 2005-12-01 | Computer Associates Think, Inc. | Balancing load requests and failovers using a uddi proxy |
US8700738B2 (en) * | 2005-02-01 | 2014-04-15 | Newsilike Media Group, Inc. | Dynamic feed generation |
US20070050446A1 (en) * | 2005-02-01 | 2007-03-01 | Moore James F | Managing network-accessible resources |
WO2006111002A1 (en) * | 2005-04-18 | 2006-10-26 | Research In Motion Limited | System and method for discovering wireless mobile applications |
US7716353B2 (en) * | 2005-12-21 | 2010-05-11 | Bmc Software, Inc. | Web services availability cache |
US20070233782A1 (en) * | 2006-03-28 | 2007-10-04 | Silentclick, Inc. | Method & system for acquiring, storing, & managing software applications via a communications network |
US8656342B2 (en) * | 2007-02-23 | 2014-02-18 | Accenture Global Services Limited | Composing integrated systems using GUI-based applications and web services |
WO2008111049A2 (en) * | 2007-03-09 | 2008-09-18 | Ghost, Inc. | System and method for a virtual hosted operating system |
-
2008
- 2008-10-17 CN CN200810167276.3A patent/CN101729491B/zh not_active Expired - Fee Related
-
2009
- 2009-09-08 EP EP09820218.7A patent/EP2352083B1/en not_active Not-in-force
- 2009-09-08 WO PCT/CN2009/073804 patent/WO2010043142A1/zh active Application Filing
-
2011
- 2011-04-14 US US13/086,835 patent/US8453158B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1728149A (zh) * | 2004-06-01 | 2006-02-01 | 微软公司 | 用于发现并连接到数据源的方法、***和装置 |
US20070055693A1 (en) * | 2005-09-07 | 2007-03-08 | Simon Galbraith | Data recovery method |
WO2008075883A1 (en) * | 2006-12-18 | 2008-06-26 | Internet Channel21 Co., Ltd. | Advertisement method by the proxy server and advertisement system operating the advertisement method |
CN101005502A (zh) * | 2007-01-25 | 2007-07-25 | 华为技术有限公司 | 业务脚本获取、控制方法及其控制***和媒体资源服务器 |
CN101202665A (zh) * | 2007-12-06 | 2008-06-18 | 中兴通讯股份有限公司 | 图形用户界面的生成方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101729491A (zh) | 2010-06-09 |
US8453158B2 (en) | 2013-05-28 |
EP2352083B1 (en) | 2019-03-13 |
CN101729491B (zh) | 2014-04-16 |
US20110191786A1 (en) | 2011-08-04 |
EP2352083A1 (en) | 2011-08-03 |
EP2352083A4 (en) | 2012-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010043142A1 (zh) | 一种增强基于脚本业务的应用可靠性的方法、装置和*** | |
US11997231B2 (en) | System and method for determining and communicating presence information | |
US10708376B2 (en) | Message bus service directory | |
US7254614B2 (en) | Web services push gateway | |
TWI397277B (zh) | 統一訊息服務之系統及方法 | |
US8605667B2 (en) | Systems and methods for exposing different service facades of an underlying network | |
US9191347B2 (en) | Methods of routing messages using a listener registry | |
US8755826B2 (en) | Internet security updates via mobile phone videos | |
CN103795689A (zh) | 资源订阅方法及装置 | |
ZA200700120B (en) | Method, system and computer program to enable semantic mediation for sip events through support of dynamicall binding to and changing of application semantics of si events | |
US20090240829A1 (en) | Translating between implicit and explicit publish-subscribe protocols | |
US20090067600A1 (en) | Method And Arrangement For Services Running On Service Execution Platform | |
US8881241B2 (en) | Method of and system for implementing privacy control | |
EP2247077A1 (en) | Method and apparatus for network communications | |
JP2023508790A (ja) | サービスプロバイダネットワークからのデータの提供 | |
Aijaz et al. | Enabling resource-oriented Mobile Web Server for short-lived services | |
WO2020224413A1 (zh) | 负荷控制方法、服务提供者nf及服务使用者nf | |
Akilli | Analysis of transformation capabilities between communication types of cloud application components | |
WO2008077324A1 (fr) | Procédé et système de fourniture de fonction de service | |
Lee et al. | Wireless reliable messaging protocol for web services (WS-WRM) | |
Werner et al. | Architecture and standardisation of web services | |
Falcarin et al. | Towards a Telecommunication Service Oriented Architecture |
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: 09820218 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009820218 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |