Schema-based dynamic parse/build engine for parsing multi-format messages

• US 7,694,287 B2
• Filed: 06/29/2005
• Issued: 04/06/2010
• Est. Priority Date: 06/29/2005
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Devassey, Shajen, Singh, Thakur L., Carlson, Mark, Singh, Kamlakar, Garrison, Sara K.
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): DAO, THUY CHAN
• Application Number:
  US11/172,397
• Publication Number:
  US 20070005613A1
• Time in Patent Office: 1,742 Days
• Field of Search: 717/136, 717141-144, 719/311, 719/313, 709206-207
• US Class Current: 717/143
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 69/03 Protocol definition or specification protocol conformance testing H04L1/244
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A parse/build engine that can handle multi-format financial messages. The engine converts the different format messages into a common format, and the common format message is then processed by the business service application. A parser examines the message and determines an appropriate schema for the particular format of message received. The schema is a data structure in a schema registry that includes a grammar structure for the received format as well as pointers to handlers for converting the different fields of the message into the internal message format using the grammar structure (the “grammar” can include field sequence, field type, length, character encoding, optional and required fields, etc.). The handlers are individually compiled. As formats change, new formats or changes to old formats can be dynamically added to the parse/build engine by loading new schema and handlers.

Claims

1. A method for parsing messages into a common canonical internal message format, comprising:

receiving a message comprising a plurality of fields;

storing a number of bytes of the received message as an offset;

providing a plurality of handlers, each handler being code for parsing at least one of said fields using grammar for said field, each said handler being separately compiled;

determining one or more schemas for the fields of the message, each schema pointing to one of said handlers and containing a grammar definition for one or more fields;

translating the one or more fields of the message into said common canonical internal message format using said handlers, wherein said common canonical internal message format comprises a hierarchical structure of possible fields, and wherein said parsing is only done for the one or more fields in said message, and only corresponding fields in said common canonical internal message format are populated; and

decrementing the offset as said handlers are used, wherein the translation is complete when the decremented offset equals a defined value.

2. The method of claim 1, further comprising dynamically loading said one or more schemas without recompiling the other schema and handlers.

3. The method of claim 1, further comprising determining a subsequent schema from said translating, and iterating the process of claim 1 for said subsequent schema on said message.

4. The method of claim 1, further comprising processing said message in said common canonical internal message format by a business services application.

5. The method of claim 4 wherein said processing by said business services application includes modifying values in said fields.

6. The method of claim 5, further comprising:

determining a second set of one or more schemas for building said message in said common canonical internal message format, after said processing, into an external message format;

determining field definitions and handlers in the second set of one or more schemas that correspond to the one or more fields included in said message; and

building the one or more fields of the external message format using said handlers.

7. The method of claim 1, wherein the message comprises a financial transaction.

8. The method of claim 1 further comprising:

determining any necessary fields other than the one or more fields in the message that are required for an output message; and

adding the necessary fields other than the one or more fields in the message to the common canonical internal message object, if any were determined, wherein the one or more fields and necessary fields are the only included fields populated in the internal message object.

9. The method of claim 1 wherein the received message is an ISO 8583 financial message.

10. The method of claim 1 further comprising setting an error flag in the common canonical internal message format upon failure of the translating step.

11. A method for parsing messages into a common canonical internal message format, comprising:

receiving a message comprising a plurality of fields;

storing a number of bytes of the received message as an offset;

providing a plurality of handlers, each handler being code for parsing at least one of said fields using grammar for said field, each said handler being separately compiled;

determining one or more schemas for the fields of the message, each schema pointing to one of said handlers and containing a grammar definition for one or more fields, wherein each message field included in said schema is identified by an object ID, said object ID being an index pointing to a particular location in said common canonical internal message format;

translating the one or more fields of the message into said common canonical internal message format using said handlers; and

decrementing the offset as said handlers are used, wherein the translation is complete when the decremented offset equals a defined value.

12. A computer readable storage medium comprising instructions for an engine configured to parse/build messages, the engine comprising:

a plurality of handlers, each handler being code for parsing at least one of the fields of a received message using grammar for said field, each said handler being separately compiled;

a plurality of schemas for different types of messages, each schema pointing to one of said handlers and containing a grammar definition for one or more fields of a message;

a common canonical internal message format object, said handlers being configured to populate the common canonical internal message format object with only fields found in the message and/or required fields, wherein said common canonical internal message format comprises a hierarchical structure of possible fields; and

a parser that maintains an offset indicating a number of bytes of the received message, wherein the parser component decrements the offset as the handlers populate the common canonical internal message format, the parse being complete when the decremented offset equals a defined value.

13. The computer readable storage medium of claim 12, further comprising a business service module configured to process the message in the common canonical internal message format.

14. The computer readable storage medium of claim 13, wherein the engine is configured to build a message from the common canonical internal message format, the engine comprising:

a second set of one or more schemas, the second set of schemas including field definitions usable in parsing fields in the message from the common canonical internal message format to an external message format; and

one or more handlers for the second set of schemas, the handlers being configured to parse fields the message from the common canonical internal message format using the field definitions in the second set of schemas to the external message format.

15. A method for parsing messages into a common canonical internal message format, comprising:

receiving a message comprising a plurality of fields;

storing a number of bytes of the received message as an offset;

providing a plurality of handlers, each handler being code for parsing at least one of said fields using grammar for said field, each said handler being separately compiled;

determining one or more schemas for the fields of the message, each schema pointing to one of said handlers and containing a grammar definition for one or more fields;

translating all of the one or more fields of the message into said common canonical internal message format using said handlers, wherein said common canonical internal message format contains at least all of the fields of said received message and said common canonical internal message format comprises a hierarchical structure of possible fields; and

decrementing the offset as said handlers are used, wherein the translation is complete when the decremented offset equals a defined value.

16. The method of claim 15, further comprising adding at least one field to said common canonical internal message format, wherein said field is not included in the received message.

17. The method of claim 16, further comprising creating an output message from said common canonical internal message format, wherein said output message contains at least one field not present in the common canonical internal message format.