Payload description for computer messaging

• US 10,560,407 B2
• Filed: 10/06/2016
• Issued: 02/11/2020
• Est. Priority Date: 10/06/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Bachmann, Martin, Hoffner, Andreas
• Primary Examiner(s): Alam, Uzma
• Application Number:
  US15/287,571
• Publication Number:
  US 20180102997A1
• Time in Patent Office: 1,223 Days
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Various examples are directed to methods and systems for describing message payload data in computer messaging. A messaging client may receive a first message that comprises first payload data. The messaging client may identify from the first message a first metadata identifier data and send a metadata request to a metadata source indicated by the first metadata identifier data. The messaging client may receive from the metadata source first payload metadata describing the first payload data. The messaging client may identify a first payload record from the first payload data based at least in party on the first payload metadata.

Claims

1. A computer messaging system, comprising:

a messaging client device comprising at least one processor and a machine readable medium in communication with the at least one processor, wherein the messaging client device is programmed to perform operations comprising;

receiving a first message comprising first payload data and first metadata identifier data;

sending a first metadata request for first payload metadata not included in the first message, wherein the first metadata request is sent to a metadata source indicated by the first metadata identifier data, and wherein the metadata source is executed at a message broker computing device that is remote from the messaging client device;

receiving from the metadata source, the first payload metadata describing the first payload data; and

identifying a first payload record from the first payload data, wherein the identifying is based at least in part on the first payload metadata.

2. The computer messaging system of claim 1, further comprising writing the first payload metadata to a metadata cache.

3. The computer messaging system of claim 1, wherein the messaging client device is further programmed to perform operations comprising determining, before sending the first metadata request, that the first payload metadata indicated by the first metadata identifier data is not present at a metadata cache of the messaging client device.

4. The computer messaging system of claim 1, wherein the messaging client device is further programmed to perform operations comprising:

receiving a second message comprising second payload data;

identifying from the second message a second metadata identifier data;

determining that second payload metadata indicated by the second metadata identifier data is stored at a metadata cache of the messaging client device; and

based at least in party on the second payload metadata, identifying a second payload record from the second payload data.

5. The computer messaging system of claim 1, wherein sending the first metadata request comprises publishing the first metadata request to a publication/subscription service queue with reply address data describing the messaging client device.

6. The computer messaging system of claim 1, wherein the messaging client device is further programmed to perform operations comprising:

accessing transmission data to be sent to a second messaging client;

formatting the transmission data to second payload data according to second payload metadata, wherein the second payload metadata describes at least one payload record for the second payload data and at least one record field for the second payload data;

adding second metadata identifier data to the second payload data, the second metadata identifier data describing the second payload metadata; and

sending a second message to a second messaging client, the second message comprising the second payload data.

7. The computer messaging system of claim 6, wherein adding the second metadata identifier data to the second payload data comprises generating a header portion of the second payload data and writing the second metadata identifier data to the header portion.

8. The computer messaging system of claim 1, further comprising the message broker computing device, wherein the message broker computing device is programmed to perform operations comprising:

receiving the first metadata request;

determining that the first payload metadata is stored at a metadata service repository;

retrieving the first payload metadata from the metadata service repository; and

sending the first payload metadata to the messaging client device.

9. The computer messaging system of claim 1, further comprising the message broker computing device, wherein the message broker computing device is programmed to perform operations comprising:

receiving the first metadata request;

determining that the first payload metadata is not stored at a metadata service repository;

querying a metadata source to obtain the first payload metadata; and

sending the first payload metadata to the messaging client device.

10. The computer messaging system of claim 1, further comprising message broker computing device, wherein the message broker computing device is programmed to perform operations comprising:

receiving the first metadata request from a publication/subscription queue;

determining an address of the messaging client device from the first metadata request; and

sending the first payload metadata to the messaging client device at the address.

11. A computer-implemented messaging method, comprising:

receiving a first message, by a messaging client executed at a first computing device comprising at least one processor and a memory in communication with the at least one processor, wherein the first message comprises first payload data and first metadata identifier data;

sending, by the messaging client, a first metadata request for first payload metadata not included in the first message, wherein the first metadata request is sent to a metadata source indicated by the first metadata identifier data, and wherein the metadata source is executed at a message broker computing device that is remote from the first computing device;

receiving, by the messaging client and from the metadata source, the first payload metadata describing the first payload data; and

identifying, by the messaging client, a first payload record from the first payload data, wherein the identifying is based at least in part on the first payload metadata.

12. The method of claim 11, further comprising writing the first payload metadata to a metadata cache.

13. The method of claim 11, further comprising determining, by the messaging client and before sending the first metadata request, that the first payload metadata indicated by the first metadata identifier data is not present at a metadata cache of the messaging client.

14. The method of claim 11, further comprising:

receiving, by the messaging client, a second message comprising second payload data;

identifying, by the messaging client, from the second message a second metadata identifier data; and

determining, by the messaging client, that second payload metadata indicated by the second metadata identifier data is stored at a metadata cache of the messaging client.

15. The method of claim 11, wherein the metadata source comprises a metadata service, and wherein the first metadata identifier data comprises a universal resource locator (URL) for the metadata service.

16. The method of claim 11, wherein identifying the first metadata identifier data comprises reading the first metadata identifier data from a header portion of the first payload data.

17. The method of claim 11, wherein sending the first metadata request comprises publishing the first metadata request to a publication/subscription service queue with reply address data describing the messaging client.

18. The method of claim 11, further comprising:

accessing, by the messaging client, transmission data to be sent to a second messaging client;

formatting, by the messaging client, the transmission data to second payload data according to second payload metadata, wherein the second payload metadata describes at least one payload record for the second payload data and at least one record field for the second payload data;

adding, by the messaging client, second metadata identifier data to the second payload data, the second metadata identifier data describing the second payload metadata; and

sending, by the messaging client, a second message to a second messaging client, the second message comprising the second payload data.

19. The method of claim 18, wherein adding the second metadata identifier data to the second payload data comprises generating a header portion of the second payload data and writing the second metadata identifier data to the header portion.

20. A non-transitory machine readable storage medium comprising thereon instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:

receiving a first message comprising first payload data and first metadata identifier data

sending a first metadata request to for first payload metadata not included in the first message, wherein the first metadata request is sent to a metadata source indicated by the first metadata identifier data, and wherein the metadata source is executed at a message broker computing device that is remote from the at least one processor;

receiving from the metadata source, the first payload metadata describing the first payload data; and

identifying a first payload record from the first payload data, wherein the identifying is based at least in part on the first payload metadata.