×

Inbound and outbound data handling for recurring revenue asset management

  • US 10,078,677 B2
  • Filed: 03/15/2013
  • Issued: 09/18/2018
  • Est. Priority Date: 06/18/2012
  • Status: Active Grant
First Claim
Patent Images

1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

  • receiving, at a recurring revenue management system from an external client data system, a first unit of data;

    determining, in response to the receiving, that the first unit of data received at the recurring revenue management system lacks at least one data aspect necessary to create a fully populated instance of a data object, the data object including a plurality of data fields and requiring the plurality of data fields to be fully populated in order for the data object to be made available for use in the recurring revenue management system;

    creating, by the recurring revenue management system and based on the first unit of data, a first instance of a skeletal object in a repository of the recurring revenue management system, the skeletal object resembling a structure of the data object and comprising a plurality of unpopulated data fields;

    partially populating the first instance of the skeletal object by populating one or more of the plurality of unpopulated data fields of the first instance of the skeletal object with at least some data extracted from the received first unit of data;

    making the partially populated first instance of the skeletal object available for use in the recurring revenue management system;

    receiving, by the recurring revenue management system from the external client data system, a second unit of data;

    extracting, by the recurring revenue management system, additional data from the second unit of data, the additional data including a reference to the skeletal object or the first unit of data;

    further populating, based on the reference, the first instance of the skeletal object by populating one or more of the plurality of unpopulated data fields of the first instance of the skeletal object with the additional data extracted from the second unit of data received by the recurring revenue management system;

    generating, by the recurring revenue management system, a second instance of the skeletal object;

    combining, by the recurring revenue management system, the second instance of the skeletal object with the first instance of the skeletal object to create the fully populated instance of the data object, the combining comprising implementing a matching algorithm, the matching algorithm matching external identifier strings that are added as annotations to the first instance of the skeletal object made available for use in the recurring revenue management system; and

    presenting the fully populated instance of the data object to the external client data system.

View all claims
  • 7 Assignments
Timeline View
Assignment View
    ×
    ×