TW201719442A - Digital service data exchanging method shortening the time of establishing composite digital service quality assurance data and increasing repetitions of the digital services - Google Patents

Abstract

This invention provides a digital service data exchanging method which is characterized by assembling different application services and network services to present quality assurance information of a digital service, shortening the time of establishing composite digital service quality assurance data by means of a defined data encapsulation format and a data exchanging method as well as a digital service organization object, and increasing repetitions of the digital services.

Description

Digital service data exchange method

The invention relates to a digital service data exchange method, in particular to a package service quality-related measurement index and event and a unified data exchange standard, and a digital service data exchange method for improving data reusability.

At present, in the data exchange technology, different data models exist between systems. When developing new functions, it takes more time to develop due to different data interfaces, and most of them exchange data by device angle. Therefore, in terms of processing service management, the information required for the encapsulation service is developed to develop a common data exchange standard, and the composition of the service is assembled through the common service organization object, and the relationship between the services is described, and the definition can be reused. Sub-services, without redevelopment, to improve the reusability of services and shorten the development time of new service monitoring systems.

It can be seen that there are still many shortcomings in the above existing methods, and there is still room for improvement, which needs to be improved.

In view of the shortcomings derived from the above-mentioned conventional methods, the inventors have improved and innovated, and after years of painstaking research, they finally succeeded in researching and developing a number of the present invention. Bit service data exchange method.

The invention provides a digital service data exchange method, and the steps include: A data interface module obtains a source data format externally, and determines whether the source data format is a preset package format, wherein the preset package format is an XML format; and when the source data format is a non-preset package format When a service package module converts the format of the source data format, the packaged monitoring indicator module of the service package module establishes a rule conversion of the monitoring index, and is a logic for defining the source data format for converting the format. Monitoring the indicator code and type, and obtaining the numerical value and textual description of the source data format; one service event module in the service package module includes an event data in the source data format; a service operation status rule setting module determines whether a custom rule is determined by the severity of an event, or determines the custom data by a value of a monitoring indicator; and when the source data is encapsulated; When the format is a preset package format, the source data format is encapsulated.

The present invention provides another digital service data exchange method, which comprises: setting a sub-service event in a service event module in a service package module; and a data interface module obtaining a plurality of source data formats externally and determining Whether the source data format is a preset package format, wherein the preset package format is an XML format; and when each of the source data formats is a non-preset package format, the service package module is based on the sub-service event Each of the source data formats of the preset encapsulation format is sub-service encapsulation; each of the source data formats of the non-preset encapsulation format encapsulated by the sub-services is a preset format Each of the source data formats utilizes a package monitoring indicator module in the service package module to establish a rule conversion of the monitoring index, and is a logic monitoring indicator code and type that defines each of the source data formats for conversion format, and obtains each The value of the source data format and the text description; the service event module in the service package module includes an event data in each of the source data formats; and a service operation state rule setting mode in the service package module The severity of the event is judged by a severity of the event, or after the custom rule is determined by the value of a monitoring indicator, the encapsulation of each source data format is performed.

The subservice package further includes: The package monitoring indicator module establishes a rule conversion of the monitoring index, and is a logic monitoring indicator code and type that defines the conversion format of each source data format, and obtains the numerical value and text description of each source data format; the service event module Include the event data in each of the source data formats; and the service operation status rule setting module in the service package module determines the custom rule according to the severity of the event, or the value of the monitoring indicator After determining the custom rule, the encapsulation of each source data format is performed, and the sub-service encapsulation is completed.

The event data is the data event ID, the event type, and the event occurrence. Interval, event severity, event description, service impact, service individual ID, source system code, and event type code.

The invention provides a query for a digital service data exchange method, and the steps include: The set of parsing module extracts the corresponding plurality of sub-service individual IDs according to the plurality of service individual IDs in a common fabric component database; Determining whether it is a composite encapsulation service; if the composite encapsulation service is used, searching for an indicator and an event corresponding to a sub-service; analyzing the service operation corresponding to each service individual ID through the rules of the composite encapsulation service Status, monitoring indicators, and service impact events are provided in XML format; and if not for the composite service, the corresponding source data format is obtained from the external service source and converted into an XML format.

The digital service data exchange method of the present invention has the following features compared with the prior art:

1. The present invention encapsulates measurement indicators and events related to service quality and standards for unified data exchange, and improves data reusability.

2. The present invention can reuse the digital services that have been developed through the common service organization object assembly service, so that developers can shorten the time course of new service development.

3. It can receive services encapsulated by third-party developers according to the same format, so that the quality of service is more comprehensive.

121‧‧‧First service individual

122‧‧‧Second service individual

124‧‧‧ third service individual

124‧‧‧ fourth service individual

1211‧‧‧First Service Individual Identification Number

1221‧‧‧Second Service Individual Identification Number

1231‧‧‧ Third Service Individual Identification Number

1241‧‧‧ Fourth Service Individual Identification Number

1212‧‧‧ first service individual eigenvalue

1222‧‧‧Second service individual eigenvalue

1232‧‧‧ Third service individual eigenvalue

1242‧‧‧ fourth service individual eigenvalue

111‧‧‧First service type

112‧‧‧Second service type

113‧‧‧ Third service type

114‧‧‧Fourth service type

200‧‧‧ digital service objects

210‧‧‧Digital service operation status

220‧‧‧Digital Service Monitoring Indicators

230‧‧‧Digital service events

31‧‧‧Users

32‧‧‧Digital Service Data Exchange System

33‧‧‧Community component library

34‧‧‧Service Provider

321‧‧‧Service Package Module

322‧‧‧Commercial analysis module

323‧‧‧Data Interface Module

3211‧‧‧Package Monitoring Indicator Module

3212‧‧‧Service Event Module

3213‧‧‧Service Operation Status Rule Setting Module

S410~S460‧‧‧Step process

S510~S590‧‧‧Step process

S610~S670‧‧‧Step process

71‧‧‧ITS Smart Transport Digital Service

72‧‧‧Action VPN

73‧‧‧ Fixed network VPN line

74‧‧‧ITS car machine

75‧‧‧ dispatch service platform

711‧‧‧X Racing Team

721‧‧‧APN-X

731‧‧‧Line A

732‧‧‧Special line B

741‧‧‧Car machine

742‧‧‧Car machine

743‧‧‧Car machine

751‧‧‧AP service platform

752‧‧‧DB service platform

753‧‧‧WEB service platform

1 is a diagram of the relationship between the digital service fabric objects of the present invention.

2 is a schematic diagram of an XMI data format of the digital service data exchange method of the present invention.

3 is a block diagram of the digital service data exchange system of the present invention.

4 is a flow chart of a digital service data exchange method of the present invention.

FIG. 5 is a flow chart of the digital service data exchange method of the present invention.

6 is a flow chart of the service status query of the present invention.

FIG. 7 is a schematic diagram of the practical application of the digital service data exchange method of the present invention.

The embodiments of the digital service data exchange method according to the present invention will be described below with reference to the related drawings. For the sake of understanding, the same components in the following embodiments are denoted by the same reference numerals.

The object of the present invention is to establish a digital service data exchange method, as shown in FIG. 1 , which is a relationship diagram of the digital service fabric object of the present invention, firstly describing the relationship between digital services through a defined digital service fabric object. And storing the defined data in the shared fabric component database, wherein the first service individual 121 includes a first service individual identifier 1211, a first service individual feature value 1212, and a first service type 111, and the second service entity 122 The second service individual identification code 1221, the second service individual feature value 1222, and the second service type 112 are included, and the third service individual 123 includes the third service individual identification code 1231, the third service individual feature value 1232, and the third service. Type 113, the fourth service individual 124 includes a fourth service individual identification code 1241, a fourth service individual feature value 1242, and a fourth service type 114. Secondly, the Http RESTFul interface is provided, so that the user can obtain the XML data format of the present invention according to the input digital service individual ID query service, and the schematic diagram of the XML data format of the digital service data exchange method of the present invention as shown in FIG. The digital service object 200 includes a digital service operating state 210 (status), a digital service monitoring indicator 220 (metric), and a digital service event 230 (failure). The digital service operation status 210 includes the service normal, the service exception, the service executable but error, unknown, through the package service operation status information, the user can save the time required to judge the service status when receiving the data. Digital Service Monitoring Indicator 220, describing some digits Service-related monitoring data or data, such as the CPU usage of the server host, provides the information the user needs to establish a monitoring data system. The digital service event 230 affects the event of the service, including a list of events affecting the service, and letting the user know why the service is affected. Through a consistent exchange interface, when a new composite digital service is needed, the already packaged digital service can be reused to reduce the development time of the developer.

Please refer to FIG. 3, which is a digital service data exchange system of the present invention. The architecture diagram includes a user 31, a digital service data exchange system 32, a shared fabric component database 33, and a service provider 34. The digital service data exchange system 32 includes a service package module 321 and a fabric analysis module. 322. The data interface module 323, wherein the service package module 321 further comprises a package monitoring indicator module 3211, a service event module 3212, and a service operation state rule setting module 3213.

The digital service data exchange method of the present invention can be divided into a single digital service and complex The combined digital service is as follows.

Please refer to FIG. 4, which is a flow chart of a digital service data exchange method of the present invention. The figure is a data exchange format for converting the source data into the invention by using a single digital service packaging process: step S410: firstly, the data interface module obtains the source data format; step S420: determining whether the XML format is conformed (as shown in the figure) 2)), if yes, performing the encapsulation service of the source data format in step S460; step S430: if not, the package monitoring indicator module in the service encapsulation module establishes a rule conversion of the monitoring index, and defines a monitoring indicator code required by the service. , type, and the source code contains the numerical values and text descriptions; Step S440: The service event module conversion event in the service encapsulation module must include the following field data event ID, event type, event occurrence time, event severity, event description, whether the service is affected, the service individual ID, and the source system code. And the event type code; step S450: the service operation status rule setting module in the service package module, the setting service status may be judged by the severity of the service event or the custom rule is determined by the value of the monitoring indicator; and step S460: Encapsulation services for source data formats.

Please refer to FIG. 5, which is a flow chart of a digital service data exchange method of the present invention. The figure is a data exchange format for converting the source data into the invention by using the composite digital service process: step S510: setting the related sub-service; step S520: obtaining multiple source data formats; and step S530: judging each source data format Whether it is a conforming XML format (as shown in FIG. 2), if yes, proceeding to step S550 to determine whether there are other digital services; step S540: if not, performing a package sub-digit service; step S550: determining whether there are other digital services, If yes, proceed to step S520; step S560: if not, establish a new composite service monitoring indicator, such as the number of statistical sub-services to generate a new monitoring indicator; step S570: perform a barrier root cause analysis rule, and derive a composite type from the sub-service event The service abnormal cause event; step S580: determining the service operation state according to the event and the indicator; and step S590: performing the encapsulation service of the source data format.

Each digital service will eventually provide two interfaces: Http RESTFul Interface and JMS interface. The Http RESTFul interface encapsulates the XML format of the invention to the user to query the individual status of the service, and the JMS interface is an object-based transfer between the digital services in order to speed up the query.

As shown in FIG. 6, it is a flowchart of the service status query of the present invention, and the steps are as follows. Next: Step S610: After the user inputs the service individual ID of the digital service; Step S620: The fabric analysis module first retrieves all relevant sub-service individual IDs by searching the common fabric component database; Step S630: determining whether the query process is a service of the composite type; step S640: when the query process is a composite service, after obtaining the indicators and events of the sub-services through the internal search mode, step S660 is performed to perform the package conversion; and step S650: when the query process is non-composite At the time of service, the data is obtained from the service source; step S660: performing the encapsulation service; and step S670: providing the data in XML format.

Please refer to FIG. 7 , which is a practical application of the digital service data exchange method of the present invention. The schematic diagram is taken as an example of the ITS Smart Transport Digital Service 71. The composite service consists of four sub-services, a mobile VPN 72, a fixed network VPN line 73, an ITS car machine 74, and a dispatch service platform 75, wherein the mobile VPN 72 service entity is An access point (APN, Access Point Name), the feature value is the access point name, the fixed network VPN line 73 service individual is a dedicated line, the characteristic value is the private line name, and the ITS car machine 74 serves as a vehicle device, characteristic The value is the car code, and the service platform 75 serves as a platform. The characteristic value is the platform name, such as DB platform, AP platform, ITS. The intelligent transportation digital service 71 service individual is mainly composed of the team. The characteristic value includes the team name, the fleet code, and the included sub-services. As shown in Figure 7, the access point APN-X 721 used by the X team 711 uses the fixed network VPN. Dedicated line 73 special line A 731, special line B 732, belonging car 741, car machine 742, car machine 743, dispatch service platform 75 AP service platform 751, DB service platform 752 and WEB service platform 753 support services, and will The data on each module is stored in the shared fabric component database.

To package digital services: The action VPN 72 regards the status of the mobile network service, and the data interface module collects relevant events affecting the mobile network service from the service provider. The service defines no monitoring indicators, and converts events affecting the mobile network service into definitions. Format, set the service operation status rule according to the event. If the mobile network of a local measurement point (a certain urban area) cannot connect to the access point of the query, it is judged that the service is executable but has an error, and the event that all the measurement points detect that it is completely unconnectable is a service exception; The fixed network VPN line 73 provides a package for the service line status between the service platform and the client service, and collects related line events from the data interface module to the service provider. This service defines no monitoring indicators and will affect the mobile network. The service event is converted into a defined format, and the service operation status rule is set according to the event. If there is an event, the service is abnormal; the ITS vehicle 74 collects the status of the vehicle from the data interface module and defines the service indicator. Vehicle status, such as dispatching a car, sending a car, losing the connection, not booting, etc. This service has no events, and the service status rules are set according to the state of the car, such as when the car is in the state of dispatching a car or sending a car. The package is service normal, and the service is disconnected and the status is service abnormality; the dispatch service platform 75 provides the health of the server host group that supports the service, and the service interface module serves Donor collect relevant alarm event host, the definition of this service without monitoring indicators, Convert related events into a defined format. Finally, the service operation status rule is set. One platform is supported by multiple hosts. When one of the hosts has an alarm event, the service status is encapsulated into a service executable but there is an error. If all the supported hosts have obstacles, then the package is encapsulated. The service is abnormal.

Package composite digital service: The ITS Smart Transport Digital Service 71 provides a service status for determining a fleet customer; the sub-services to be set up include the Mobile VPN 72, the Fixed Network VPN Line 73, the ITS Vehicle 74 Service, and the Service Platform 75; Encapsulation, collecting the proposed data in the composite service; setting the composite monitoring indicator rules, generating new indicators according to the sub-service collection status, collecting the vehicle service information statistical service individual (such as the car machine 741, the car machine 742, The information of the car machine 743), the indicators of the current number of vehicles, the number of lost vehicles, the number of vehicles shut down, etc., which are the monitoring indicators, are generated; the root cause analysis of the service obstacles is based on the comprehensive analysis of the event level according to all the status of the service. The event level is simply defined as normal (Normal), abnormal (Critical), executable, and error (Warning). The following is the adjustment mechanism of each service level; the action VPN 72 does not adjust according to the sub-service event level; the fixed network VPN line 73, the alarm line of the dedicated line has an event value is the critical value (Critical), otherwise one of the events has an event The degree of adjustment is the warning value (Warning). For example, the X team 711 service has two fixed network VPN lines (line A 731, dedicated line B 732), as a mechanism for mutual backup. If there are events on both lines, the alarm level is critical (Critical), otherwise If one of the events has an event, the adjustment level is Warning; the vehicle service, because each unit will have no benefit, here is the threshold value based on the number of counted vehicles. If it exceeds 70%, it is judged that the service is executable but the error is provided to the user and the maintenance personnel for reference. The dispatch service platform 75 is not adjusted according to the sub-service event level; and the service operation status is set. (560), based on the highest level of impact of all events for the operational status of the service (Exception > Executable but error > Service OK).

Query service individual status: The user uses the service individual ID to query, for example, using the service individual ID of the X team 711 to query the composite service ITS smart transportation number as the service status, first find the relevant sub-service individual ID through the shared fabric component database, and collect different sub-services. Digital service data, from the action VPN 72 query service individual APN-X 721; self-fixed network VPN line 73 query line A 731, line B 732 status; ITS car machine 74 query car machine 741, car machine 742, car machine 743 The status of the service platform 75, the AP service platform 751, the DB service platform 752 and the WEB service platform 753 service operation status; after the rules set in the package service, finally back to the XML format data (Figure 2 As shown in the figure, the user can judge whether the service is normal according to the service operation status. In the related event, the cause of the service abnormality can be found. For example, the ITS smart transportation digital service 71 has a large number of lost vehicles, and the information corresponding to the package has If the APN-X 721 containing the mobile VPN 72 has a serious obstacle event, it can be inferred that the action VPN 72 causes a large number of lost vehicles, reducing the time for the back-end users to find the cause of the obstacle.

Other service applications: To create a new composite service, such as MOD service, the method steps are like establishing an ITS smart transport digital Service 71, which defines the service fabric object, encapsulates the service (encapsulation service rule establishment, provides service lookup interface). It is observed that there is the same sub-service, fixed network VPN line 73, at this time the sub-service can be reused, reducing the time required to re-encapsulate the service.

In summary, the present invention has achieved the desired effect under the prior art, and is not familiar with the skill of the art, and its progress and practicality have been consistent with patents. Apply for the requirements, and file a patent application in accordance with the law, and ask your bureau to approve the application for the invention patent, in order to encourage creation, to the sense of virtue.

The above is intended to be illustrative only and not limiting. Any other equivalent modifications or alterations of the present invention are intended to be included in the scope of the appended claims.

S410~S460‧‧‧Step process

Claims (6)

A digital service data exchange method, the method comprising: a data interface module externally obtaining a source data format, and determining whether the source data format is a preset package format, wherein the preset package format is an XML format; When the source data format is a non-preset package format, a service package module converts the logic of the source data format into a format; and the packaged monitoring indicator module of the service package module establishes a rule conversion of the monitoring index. Defining the source data format to convert the logical format of the monitoring indicator code and type, and obtaining the numerical value and text description of the source data format; one service event module in the service package module includes an event data in the source data Within the format; a service operation status rule setting module in the service package module determines a custom rule based on the severity of an event, or determines the custom rule by using a value of a monitoring indicator to perform the source Encapsulation of the data format; and when the source data format is a preset package format, the source data format is performed Packaging services. The method for exchanging digital service data according to claim 1, wherein the event data is a data event ID, an event type, an event occurrence time, an event severity, an event description, an impact service, a service individual ID, and a source system code. And the event type code. A digital service data exchange method includes the steps of: setting a sub-service event in a service event module in a service package module; and a data interface module externally obtaining a plurality of source data formats, and determining each source data Whether the format is a preset package format, where the preset package format is an XML format; When the source data format is a non-preset package format, the service package module performs sub-service encapsulation on each of the source data formats of the non-preset package format according to the sub-service event; Setting the source data format of the package format and the source data format of the preset format, using a package monitoring indicator module in the service package module to establish a rule conversion of the monitoring index, and defining each source data format Performing a logical monitoring indicator code and type of the conversion format, and obtaining a numerical value and a textual description of each of the source data formats; the service event module in the service packaging module includes an event data in each of the source data formats; And a service operation status rule setting module in the service package module determines a custom rule based on the severity of an event, or judges the custom rule by using a value of the monitoring indicator, and performs each source data A composite package service in the format. For example, the digital service data exchange method described in claim 3, wherein the sub-service package further comprises: the package monitoring indicator module establishes a rule conversion of the monitoring index, and is a logic for defining the conversion format of each source data format. An indicator code, a type, and a numerical value and a textual description of each of the source data formats; the service event module includes the event data in each of the source data formats; and the service operation status rule setting in the service package module The module determines the custom rule according to the severity of the event, or determines the custom rule by using the value of the monitoring indicator, and performs encapsulation of each source data format to complete the sub-service encapsulation. The method for exchanging digital service data according to claim 3, wherein the event data is a data event ID, an event type, an event occurrence time, an event severity, an event description, an impact service, a service individual ID, and a source system code. And the event type code. A digital service data exchange method, the steps comprising: The set of parsing module extracts the corresponding plurality of sub-service individual IDs according to the plurality of service individual IDs in a common fabric component database; determines whether it is a composite encapsulation service; if the composite encapsulation service, the search obtains a corresponding one Indicators and events of the sub-service; analyzing the service operation status, monitoring indicators and service impact events corresponding to the individual IDs of the service through the rules of the composite encapsulation service, provided in an XML format; and if not for the composite service, Then, the corresponding source data format is obtained from the external service source and converted into an XML format.