TECHNICAL FIELD

The present disclosure relates to systems and methods for communicating messages between a web service and a non-web service.

BACKGROUND

An Open Mission Systems (OMS) standard is an initiative focused on a creation of a common architecture for mission system payloads and subsystems that enable greater reuse and decreased integration risk for mission systems. A goal of the OMS standard is to develop industry consensus for a non-proprietary mission system architectural standard that enables affordable technical refresh and insertion, simplified mission systems integration, service reuse and interoperability, and competition across a lifecycle. As an example, the OMS standard can be used to define an aircraft mission system architecture that employs a service-oriented architecture, a defined message schema, software services application program interfaces (APIs), and isolate safety-critical aircraft subsystems.

SUMMARY

The present disclosure relates to systems and methods for communicating messages between a web service and a non-web service.

In an example, a system can include a web service interface (WSI) and a service directory. The WSI can be configured to communicate with a non-web service to receive reader data and/or writer data. The reader data can identify one or more services that have been granted permission to retrieve data provided by the non-web service, and the writer data can identify one or more services that have been granted permission to provide data to the non-web service. The service directory can be configured to provide the WSI with non-web service subscriber data and/or non-web service publisher data for the non-web service in response to receiving the reader and/or writer data. The non-web service subscriber data can identify a web service as a subscriber of data provided by the non-web service and the non-web service publisher data can identify the web service as a publisher of data from which the non-web service is enabled to retrieve data. The WSI can be configured to provide the web service subscriber data and/or web service publisher data to the non-web service to enable the non-web service to communicate with the web service.

In another example, a system can include memory to store machine readable instructions and data. The system can further include one or more processors to access the memory and execute the machine-readable instructions. The machine-readable instructions can cause the processor to receive reader data and/or writer data generated by a non-web service. The reader data can identify one or more services that have been granted permission to retrieve data provided by the non-web service and the writer data can identify one or more services that have been granted permission to provide data to the non-web service. The machine-readable instructions can further cause the processor to store at a publisher-subscriber database the reader and/or writer data for the non-web service and query the publisher-subscriber database for subscribers of data provided by the non-web service and/or publishers of data from which the non-web service is enabled to retrieve data. The machine-readable instructions can further cause the processor to generate non-web service subscriber data and/or non-web service publisher data in response to the querying of the publisher-subscriber database, and cause the non-web service subscriber data and/or non-web service publisher data to be provided to a WSI associated with the non-web service to provide the non-web service subscriber data and/or non-web service publisher data to the non-web service to enable the non-web service to communicate with the web service.

In a further example, a method can include receiving, at WSI, reader data and/or writer data generated by a non-web service. The WSI can be located at a critical abstract layer of a system configured according to an open mission system (OMS) standard that includes the non-web service. The method can further include generating, at a service directory, non-web service subscriber data and/or non-web service publisher data for the non-web service in response to storing the reader and/or writer data in a subscriber-publisher database, causing, at the WSI, the non-web service subscriber data and/or non-web service publisher data to be provided to the non-web service to enable the non-web service to communicate with a web service, and receiving, at the service directory, one or more web service requests for subscribers of data provided by the web service and/or publishers of data from which the web service is enabled to retrieve data. The publishers of data can include the non-web service. The method can further include generating web service subscriber data and/or web service publisher data in response to the one or more web service requests, and causing, at the service directory, the web service subscriber data and/or web service publisher data to be provided to the web service to enable the web service to communicate with the non-web service.

