Patents by Inventor Oleg Mikulinsky

Oleg Mikulinsky has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Publication number: 20040002979
    Abstract: A system, method and computer readable medium for mapping file identifications is disclosed. The method on a server includes receiving a file from a first partner, wherein the file is intended for a second partner. The file includes a first partner ID. If the server finds in a database a second partner ID corresponding to the first partner ID, the server integrates the second partner ID with the file and proceeds to send the file to the second partner. If the server does not find in the database a second partner ID corresponding to the first partner ID, the server generates a global file ID for the file. Then the server integrates the global file ID with the file and proceeds to send the file to the second partner. Subsequently, the server enters a link between the first partner ID and the second partner ID in the database.
    Type: Application
    Filed: June 27, 2002
    Publication date: January 1, 2004
    Applicant: PartnerCommunity, Inc.
    Inventors: Wayne Charles Seguin, Oleg Mikulinsky
  • Publication number: 20020147726
    Abstract: A method and system and computer readable medium for: (1) the creation and representation of business rule definitions, (2) the creation and representation of enforcing rule handlers, (3) the creation and representation of a framework to check the existence of rules then, apply the appropriate handler, (4) and the distribution of the rule definitions and handlers to clients. The present invention defines a rule language and provides a framework that separates the definition of the rules, the enforcing handler, the system at which rules are generated and the system at which rules are enforced. Further, in one embodiment, the present invention uses standard XML notations to define rules and standard XSL and XSLT processing instructions to enforce rules. Using standard XML, XSL and SXLT allows clients to use off-the-shelf XML parser and XSL processors in lieu of developed code or rule based engines.
    Type: Application
    Filed: March 20, 2002
    Publication date: October 10, 2002
    Applicant: PARTNERCOMMUNITY, INC.
    Inventors: Ramzi Yehia, John Yin, Wayne Charles Seguin, Oleg Mikulinsky
  • Publication number: 20020091579
    Abstract: A method and system for managing and correlating orders in a multilateral environment. The multilateral environment includes two or more trading partners trading goods and services. The system is based on a hub and spoke architecture. The hub presents to each of the partners using a partner system a user interface for receiving an order. The order when received is parsed into tags. Each tag represents a predefined field in an order such as price, quantity, delivery date and other contractual terms. These tags are placed into a database schema using a naming structure that is identical to the naming structure used for the tag values so that elements in the database schema can be populated directly from the tag values. Each partner in the value chain, which supplies a good and service for the order, forms one or more hierarchical contractual relationships. Contract tag values are retrieved for each trading partner in the hierarchical contractual relationship.
    Type: Application
    Filed: January 9, 2001
    Publication date: July 11, 2002
    Applicant: PartnerCommunity, Inc.
    Inventors: Ramzi Yehia, John Yin, Oleg Mikulinsky
  • Publication number: 20020091614
    Abstract: A method and system for reconciling contracts in a multilateral environment. The multilateral environment includes two or more trading partners trading goods and services. The system is based on a hub and spoke architecture. The hub presents to each of the partners using a partner system a user interface for receiving a contract. The contract when received is parsed into requested tags. Each requested tag represents a predefined field in a contract such as price, quantity, delivery date and other contractual terms. These requested tags are placed into a database schema using a naming structure that is identical to the naming structure used for the requested tag values so that elements in the database schema can be populated directly from the requested tag values. Each partner in the value chain, which supplies a good and service for the contract, forms a hierarchical contractual relationship. Contract tag values are retrieved for each trading partner in the hierarchical contractual relationship.
    Type: Application
    Filed: January 9, 2001
    Publication date: July 11, 2002
    Inventors: Ramzi Yehia, John Yin, Oleg Mikulinsky