SERVICE LINKING DEVICE AND SERVICE LINKING METHOD

Description

[Technical field]

[0001] The present disclosure relates to the coordination of multiple services that constitute an application service. [Background technology]

[0002] Some application services operate in conjunction with other services. One way to facilitate this cooperation is to automatically start the service using a data model for the data used by the application service and the other services.

[0003] Patent document 1 describes an information processing device that includes an origin extraction means that extracts "origin," which is information regarding the generation relationship of data in target information that includes data and a program that processes the data, an order extraction means that extracts the order of "links," which are the relationship between data and programs, and an impact range exploration means that identifies the impact range of a first program based on the origin and order. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-45508 A Summary of the Invention [Problem to be solved by the invention]

[0005] The information processing device described in Patent Document 1 extracts the relationship between data and programs, but the extracted information is intended to be used for analyzing the extent of impact when modifying software, and is not intended to start a service in response to an event. In other words, the information processing device described in Patent Document 1 does not automatically start a service using a data model.

[0006] The technology disclosed herein has been made to solve the above problems, and aims to automatically start a service that works in conjunction with an application service using a data model. [Means for solving the problem]

[0007] The service collaboration device disclosed herein includes a data model creation unit that creates a data model that defines the data handled by an application service that operates in collaboration with multiple services and the relationships between the multiple pieces of data; a data model management unit that stores the data model and the data handled by the application service; an event detection unit that detects an event that occurs in data defined in the data model on the data model management unit; and a service startup unit that assigns the data in which an event has been detected to a corresponding service, which is a service among the multiple services that has been previously associated with the data, and starts the corresponding service. Effect of the Invention

[0008] According to the server linkage device of the present disclosure, it is possible to automatically start a corresponding service in response to an event of data defined in a data model.

[0009] The objects, features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a block diagram showing a configuration of a service collaboration device. [Diagram 2] FIG. 1 is a diagram showing the service flow in an on-demand vehicle dispatch service and data required by each service. [Diagram 3] FIG. 1 illustrates a data model represented by nodes and edges. [Figure 4] FIG. 1 illustrates a detailed example of a data model for an on-demand ride-hailing service. [Diagram 5] FIG. 4 is a diagram illustrating an operation of an event detection unit. [Figure 6] This is a diagram showing the entity of the data model. [Figure 7] This is a diagram showing an example of a one-to-one association between data elements and services. [Figure 8] This is a diagram showing an example of an N-to-one association between data elements and services. [Figure 9] This is a diagram showing an example in which data elements and services are associated one-to-one with the service startup condition. [Figure 10] This is a diagram showing the flow of event detection and service startup. [Figure 11] This is a flowchart showing the operation of the service cooperation device. [Figure 12] This is a diagram showing the hardware configuration of the service cooperation device. [Figure 13] This is a diagram showing the hardware configuration of the service cooperation device.

Mode for Carrying Out the Invention

[0011] <A. Embodiment 1> <A-1. Outline> FIG. 1 is a block diagram showing the configuration of a service cooperation device 101 according to Embodiment 1. The service cooperation device 101 performs cooperation between an application service 21 executed by an application service execution device 201 and other services necessary for the execution of the application service 21. The application service 21 is an ASP service provided by an ASP (Application Service Provider). The application service 21 is realized by cooperating with a plurality of services. In the example of FIG. 1, the application service 21 is realized by cooperating with services A, B, and C.

[0012] The service cooperation device 101 includes a data model creation unit 11, a data model management unit 12, an event detection unit 13, and a service startup unit 14.

[0013] The data model creation unit 11 creates a data model 51 according to the input of the administrator of the application service 21. The data model 51 defines the data handled by the application service 21 and the relationships between the data.

[0014] The data model management unit 12 manages the data model 51 created by the data model creation unit 11. When the application service execution device 201 executes the application service 21, data events defined in the data model 51 occur. The data events include at least one of data generation, update, or deletion. When there is a data generation event, the generated data is stored in the data model management unit 12. Also, when there is a data update event, the existing data is updated in the data model management unit 12. Also, when there is a data deletion event, the data is deleted in the data model management unit 12.

[0015] The event detection unit 13 detects data events defined in the data model 51 based on changes in the data in the data model management unit 12.

[0016] The service startup unit 14 identifies the service (hereinafter, the corresponding service) corresponding to the data for which an event has been detected among services A31, B32, and C33, gives the data element for which the event has been detected to the corresponding service, and starts the corresponding service.

[0017] Services A31, B32, and C33 are, for example, endpoints with publicly available URLs (Uniform Resource Locators). These endpoints have pre-defined operations to be executed according to the input data. Starting a service means sending pre-defined data to the endpoint or performing some kind of communication. By starting the service, the service is executed at that endpoint.

[0018] <A-2. Data Model Creation Unit 11 and Data Model Management Unit 12> 2 shows the flow of services when executing the on-demand vehicle dispatch service 34 and the data required by each service. Hereinafter, the on-demand vehicle dispatch service 34 will be taken as an example of the application service 21. The on-demand vehicle dispatch service 34 cooperates with an authentication and authorization service 35, a payment service 36, and a control service 37. The authentication and authorization service 35, the payment service 36, and the control service 37 correspond to the services A31, B32, and C33 in FIG. 1, respectively.

[0019] The services are executed in the following order: on-demand vehicle dispatch service 34, authentication and authorization service 35, payment service 36, and control service 37. The authentication and authorization service 35 authenticates users of the on-demand vehicle dispatch service 34 using an ID, password, etc. The data required by the authentication and authorization service 35 is the user. The payment service 36 is a service for paying the fare to the destination. The data required by the payment service 36 is the ticket. The control service 37 controls mobility. In other words, the control service 37 is a service for dispatching mobility and transporting the user to the destination.

[0020] The data model creation unit 11 creates a data model that defines the data required by each service and the relationships between the data, and stores the data in the data model management unit 12. Fig. 3 shows a data model 51 created by the data model creation unit 11. In the data model 51, for example, a graph database is used, and data relationships are represented by nodes 38, 39, and 40 and edges 41 and 42.

[0021] Node 38 represents "user" data required by authentication and authorization service 35. Node 39 represents "ticket" data required by payment service 36. Node 40 represents "mobility" data required by control service 37. Nodes 38 and 39 are connected by edge 41, and nodes 39 and 40 are connected by edge 42.

[0022] Figure 4 shows a detailed example of the data model 51. Each node 38, 39, 40 and each edge 41, 42 that make up the data model 51 hold labels. Also, each node 38, 39, 40 and each edge 41, 42 hold attributes as necessary.

[0023] For the node 38 representing the data required by the authentication and authorization service 35, the label is "user" and the attribute is "user ID". For the node 39 representing the data required by the payment service 36, the label is "ticket" and the attribute is "fee". For the node representing the data required by the control service 37, the label is "mobility" and the attributes are "boarding location", "alighting location", or "number of passengers". The label of the edge is, for example, "order". The application service execution device 201 processes the data in the order defined in the data model 51. The data model is only positioned as metadata and does not hold attribute values.

[0024] <A-3. Event Detection Unit 13> Figure 5 is a diagram for explaining the operation of the event detection unit 13.

[0025] In the data model management unit 12, in addition to the data model 51 created by the data model creation unit 11, the actual data used in the application service 21 (hereinafter referred to as "the entity 52 of the data model") is stored. The application service execution device 201 executes the application service 21 and stores the data generated in the process as the entity 52 of the data model in the data model management unit 12. Also, the data updated or deleted during the execution of the application service 21 is updated or deleted in the data model management unit 12 as well.

[0026] The event detection unit 13 detects events that occur in the "user" data, "ticket" data, and "mobility" data in the entity 52 of the data model stored in the data model management unit 12. An event is at least any one of data generation, update, and deletion.

[0027] FIG. 6 is a diagram showing the entity 52 of the data model. Different from the data model 51, the entity 52 of the data model holds attribute values. For example, the node 43 of the "user" data holds the attribute value "0001" of the attribute "user ID". Also, the node 44 of the "ticket" data holds the attribute value "500" of the attribute "fee". Further, the node 45 of the "mobility" data holds the attribute value "A" of the attribute "boarding place", holds the attribute value "E" of the attribute "alighting place", and holds the attribute value "2" of the attribute "number of passengers". The event detection unit 13 detects an event of data in which an attribute value is written.

[0028] <A-4. Service activation unit 14> The service activation unit 14 identifies a corresponding service that is a service corresponding to the data in which an event is detected, attaches the data to the corresponding service, and activates the corresponding service. The data and the service are pre-associated by the administrator, and the service activation unit 14 holds the association information. Note that the data element and the service do not necessarily have to be associated one-to-one, and may be associated one-to-N, N-to-1, or N-to-N. Also, activation conditions of the service may be set.

[0029] FIGS. 7 to 9 show examples of the association between the data element and the service. FIG. 7 shows an example of a one-to-one association between the data element and the service. The "user" data is associated with the authentication and authorization service 35 (https: / / x.x.x.x:port / ). Also, the "ticket" data is associated with the settlement service (https: / / y.y.y.y:port / ). Further, the "mobility" data is associated with the control service (https: / / z.z.z.z:port / ).

[0030] Figure 8 shows an example of one-to-many correspondence between data elements and services. "User" data corresponds to the authentication and authorization service 35 (https: / / xxxx:port / ) and the VV service (https: / / vvvv:port / ). "Ticket" data corresponds to the payment service (https: / / yyyy:port / ). "Mobility" data corresponds to the control service (https: / / zzzz:port / ).

[0031] FIG. 9 shows an example in which data elements and services are associated one-to-one with a service start condition. In this example, data elements and services are associated one-to-one as in the example of FIG. 7, and "creation, update" is defined as a start condition for authentication and authorization service 35. That is, service start unit 14 starts authentication and authorization service 35 when a creation or update event occurs in "user" data. Also, "creation" is defined as a start condition for payment service 36. That is, service start unit 14 starts payment service 36 when a creation event occurs in "ticket" data. Also, "creation, update, deletion" is defined as a start condition for control service 37. That is, service start unit 14 starts control service 37 when a creation, update, or deletion event occurs in "mobility" data.

[0032] 10 is a diagram showing the flow of event detection and service startup. It is assumed that "mobility" data is generated by the application service 21 executing the application service 21. The "mobility" data has an attribute value "A" for the "boarding location" attribute, an attribute value "E" for the "drop-off location" attribute, and an attribute value "2" for the "number of passengers" attribute.

[0033] When the event detection unit 13 detects the generation of "mobility" data, the service activation unit 14 refers to the association information between data elements and services, and provides the "mobility" data to the control service 37 (https: / / z.z.z.z:port / ), which is the corresponding service, to activate the control service 37. As a result, the control service 37 can grasp the information necessary for vehicle allocation, such as the boarding location, alighting location, and the number of passengers.

[0034] <A-5. Flowchart> Figure 11 is a flowchart showing the operation of the service cooperation device 101. As a preliminary preparation, the data model creation unit 11 creates a data model, and the service activation unit 14 holds the association information between data elements and services.

[0035] First, in step S101, the event detection unit 13 detects a data event.

[0036] Next, in step S102, the service activation unit 14 identifies the corresponding service of the data in which the event has occurred.

[0037] After that, in step S103, the service activation unit 14 determines whether there is a startup condition setting. If there is no startup condition setting, the service activation unit 14 activates the service in step S105.

[0038] If there is a startup condition setting in step S103, then in step S104, the service activation unit 14 determines whether the event matches the startup condition. If the event does not match the startup condition, the service activation unit 14 does not activate the service, and the process of the service cooperation device 101 ends.

[0039] If the event matches the startup condition in step S104, the service activation unit 14 activates the service in step S105, and the process of the service cooperation device 101 ends.

[0040] <A-6. Variation> In the above description, the service activation unit 14 identifies a corresponding service by associating the data defined in the data model 51 with the service on a one-to-one basis. However, the service activation unit 14 may abstract the data defined in the data model 51, and then identify the corresponding service by associating the abstracted data, which is the abstracted data, with the service. For example, when user data is defined in the data model 51, data relating to a "person" abstracted from the user data may be associated with a specific service X. Then, when data relating to a "person" is generated, the service activation unit 14 may activate the specific service X corresponding to the data relating to the "person".

[0041] In the above description, the service initiation unit 14 initiates a corresponding service after the event detection unit 13 detects that an event has occurred in the data. However, the service initiation unit 14 may initiate a corresponding service before an event has occurred in the data.

[0042] For example, when the application service execution device 201 attempts to generate user data, it transmits a request for generating the user data to the service collaboration device 101, and the request is stored in the data model management unit 12. When the service collaboration device 101 responds to the application service execution device 201 that the request is permitted, the application service execution device 201 generates the user data.

[0043] With this configuration, the event detection unit 13 detects a user data generation event in advance based on a user data generation request stored in the data model management unit 12. Then, the service initiation unit 14 can initiate a service corresponding to the user data before the user data is actually generated.

[0044] 9, a start condition for a corresponding service is set for each data defined in data model 51. The start condition for a corresponding service may be freely set by the user. For example, a condition may be set such that a corresponding service is started when two pieces of data are present.

[0045] The service startup unit 14 may have a criterion for judgment, which is a predetermined condition that the value of the data should satisfy, for the data for which a generation or update event has occurred, and may verify the validity of the data in light of the criterion. For example, assume that a criterion is predetermined such that the value of newly generated data is not less than 5 and less than 50. The service startup unit 14 may verify the data for which the event has occurred and start the corresponding service only when it determines that there is no problem.

[0046] After starting the corresponding service, the service startup unit 14 may associate the data that triggered the start of the corresponding service with the corresponding service and the startup time of the corresponding service, and accumulate it as a service startup history. Thereby, when a failure occurs in the corresponding service, it becomes possible to identify the data that caused the failure.

[0047] <A-7. Effect> The service cooperation device 101 according to Embodiment 1 includes a data model creation unit 11 that creates a data model 51 that defines data handled by an application service 21 that operates in cooperation with a plurality of services A31, B32, and C33 and the relationships between the plurality of data, a data model management unit 12 that stores the data model 51 and the data handled by the application service 21, an event detection unit 13 that detects an event occurring in the data defined by the data model 51 on the data model management unit 12, and a service activation unit 14 that assigns the data for which the event has been detected to a corresponding service, which is a service pre-associated with the data among the plurality of services, and activates the corresponding service. Therefore, according to the service cooperation device 101, the corresponding service can be automatically activated in response to an event of the data defined by the data model, and the cooperation between the application service 21 and other services can be smoothly performed. Further, without modifying the service itself, by only changing the definition of the data model, it is possible to add a new service or change an existing service. Also, from the definition of the data model, the activation order and dependency relationship between services can be easily grasped, improving maintainability.

[0048] <B. Hardware Configuration> In the above service cooperation device 101, the data model creation unit 11, the data model management unit 12, the event detection unit 13, and the service activation unit 14 are realized by a processing circuit 81 shown in FIG. 12. That is, the processing circuit 81 includes the data model creation unit 11, the data model management unit 12, the event detection unit 13, and the service activation unit 14 (hereinafter referred to as "the data model creation unit 11 etc."). For the processing circuit 81, dedicated hardware may be applied, or a processor that executes a program stored in a memory may be applied. The processor is, for example, a central processing unit, a processing device, an arithmetic device, a microprocessor, a microcomputer, a DSP (Digital Signal Processor), or the like.

[0049] When the processing circuit 81 is a dedicated hardware, the processing circuit 81 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination of these. Each function of the data model creation unit 11 and the like may be realized by a plurality of processing circuits 81, or the functions of each unit may be realized by a single processing circuit.

[0050] When the processing circuit 81 is a processor, the functions of the data model creation unit 11 and the like are realized by a combination of software, etc. (software, firmware, or software and firmware). The software, etc. is described as a program and stored in a memory. As shown in Fig. 13, a processor 82 applied to the processing circuit 81 realizes the functions of each unit by reading and executing a program stored in a memory 83. That is, the service collaboration device 101 includes a memory 83 for storing a program that, when executed by the processing circuit 81, results in the execution of the steps of: a data model creation unit 11 creating a data model 51 that defines data handled by an application service 21 that operates in cooperation with a plurality of services A31, B32, and C33 and relationships between the plurality of data; a data model management unit 12 storing the data model 51 and the data handled by the application service 21; an event detection unit 13 detecting an event that has occurred in the data defined in the data model 51 on the data model management unit 12; and a service initiation unit 14 assigning the data in which the event has been detected to a corresponding service that is a service that is previously associated with the data among the plurality of services, and initiating the corresponding service. In other words, this program can be said to cause a computer to execute the procedure or method of the data model creation unit 11, etc. Here, the memory 83 may be, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), an HDD (Hard Disk Drive), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a DVD (Digital Versatile Disk) and its drive device, or any storage medium to be used in the future.

[0051] The above describes a configuration in which each function of the data model creation unit 11, etc. is realized either by hardware or software, etc. However, the present invention is not limited to this, and a configuration in which part of the data model creation unit 11, etc. is realized by dedicated hardware and another part is realized by software, etc. For example, the function of the data model creation unit 11 can be realized by a processing circuit as dedicated hardware, and the other functions can be realized by the processing circuit 81 as the processor 82 reading and executing a program stored in the memory 83.

[0052] As described above, the processing circuit can realize each of the above functions by hardware, software, or a combination of these. The data model management unit 12 is composed of a memory 83.

[0053] In addition, each embodiment can be freely combined, and each embodiment can be appropriately modified or omitted. The above description is an example in all respects. It is understood that countless modified examples not illustrated can be assumed. [Explanation of symbols]

[0054] 11 data model creation unit, 12 data model management unit, 13 event detection unit, 14 service startup unit, 21 application service, 31 service A, 32 service B, 33 service C, 34 on-demand vehicle dispatch service, 35 authorization service, 36 payment service, 37 control service, 38, 39, 40, 43, 44, 45 nodes, 41, 42 edges, 51 data model, 52 data model entity, 81 processing circuit, 82 processor, 83 memory, 101 service collaboration device, 201 application service execution device.

Claims

1. a data model creation unit that creates a data model that defines data handled by an application service that operates in cooperation with a plurality of services and relationships between the plurality of data; a data model management unit that stores the data model and the data handled by the application service; an event detection unit that detects, on the data model management unit, an event that occurs in the data defined in the data model; a service activation unit that assigns the data in which the event has been detected to a corresponding service that is a service among the plurality of services that is previously associated with the data, and activates the corresponding service. Service integration device.

2. The event includes at least one of generation, deletion, and update of the data. The service collaboration device according to claim 1 .

3. the service initiation unit associates abstract data obtained by abstracting the data defined in the data model with the plurality of services; the corresponding service is a service among the plurality of services that corresponds to the abstraction data of the data in which the event is detected; The service collaboration device according to claim 1 .

4. The service initiation unit associates abstracted data obtained by abstracting the data defined in the data model with the plurality of services; the corresponding service is a service among the plurality of services that corresponds to the abstraction data of the data in which the event is detected; The service collaboration device according to claim 2 .

5. the event being either a creation or an update of the data; the service initiation unit initiates the corresponding service only when the value of the data in which the event is detected satisfies a predetermined condition. The service collaboration device according to claim 1 .

6. the service initiation unit accumulates a service initiation history linking the corresponding service with the data assigned to the corresponding service when the corresponding service is initiated; The service collaboration device according to any one of claims 1 to 4.

7. The service initiation unit accumulates a service initiation history linking the corresponding service with the data assigned to the corresponding service when the corresponding service is initiated. The service collaboration device according to claim 5 .

8. a data model creation unit creating a data model that defines data handled by an application service that operates in cooperation with a plurality of services and relationships between the plurality of data; a data model management unit that stores the data model and the data handled by the application service; an event detection unit detects, on the data model management unit, an event that has occurred in the data defined in the data model; a service initiation unit assigns the data in which the event has been detected to a corresponding service, which is a service among the plurality of services and is previously associated with the data, and initiates the corresponding service. How to link services.

Images