International Business Machines Corporation

Hulu, LLC

Chaitanya Laxminarayan

Gopal Krishnan

Matthew Sanchez

Manoj Saxena

Hua Zheng

Sanjay F Kottaram

Michael Perham

Peter E Sargent

Keith Yarbrough

Hang Li

Wing Chit Mak

Eugene Chuan-Huai Wei

Joel Trunick

Sanjay Francis

Liang Xiang

Nathan A Hinish

Jay Martin Tenenbaum

Electronic data interchange (EDI) documents are validated by creating an inventory of all rules, dynamically adjusting the inventory based upon entity specific rules derived from a plurality of companion guides, determining a profile containing pointers to select rules in the inventory for each companion guide and storing the profile for each companion guide in a storage. A runtime checker can then be used to check a received EDI document with a corresponding rule set, forward the EDI document if the EDI document matches its current rule set and return the EDI document if the EDI document does not match its current rule set. EDI rules may be enforced, for example, by determining entity-specific rules from corresponding companion guides, by expressing each rule in a neutral and machine readable format, by classifying the rules and/or by creating an inventory of rules and pointers to entity-specific rules.

Cascading definition and support of EDI rules

In a streaming video system, a method determining a sequence of video programs playing on an interactive player device may include streaming a first video program including an ad break from a computer server to an interactive player device during a first streaming session. The method may further include automatically selecting a video advertisement or next program from a set of prospective video advertisements for play during the ad break or available programs, based at least in part on the first video program exclusive of any parameter based on user identity. The method may include providing the video advertisement to the interactive player device in the first streaming session at the ad break. Bases for selecting the next ad or program may include program popularity, rate of change in popularity, or other parameter. The method may be embodied in a computing apparatus or system.

Ad selection and next video recommendation in a video streaming system exclusive of user identity-based parameter

A method and apparatus to employ a service proxy to dynamically personalize Web service messages by automatically supplying the interface parameters used for communications between a Web service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specifies during configuration set up at the Web service provider's Web site and in messages used to communicate with one or more Web services. For simpler administration, the context variables may be organized in multiple kinds of hierarchies by which communications parameters specified at a higher level are automatically applied to categories at a lower level, although parameters specified directly for a lower-level category will override parameters from a higher category.

Dynamic, non-intrusive personalization of web services

A processing workflow method, system, and computer program product provide the ability; to recommend alternative programming during playback of a source media program. A media program player plays the source media program to a first viewer and provides information regarding the first viewer to a recommendation engine. The recommendation engine calculates and sends the media player a list of recommended media program candidates (including identifications of the candidates) based on the information. Prior to reaching an advertising break in the source media program, the media player transmits a request (including the identifications) for an advertisement to an advertising server and in response, receives an advertisement that is played to the first viewer during the advertising break.

Processing workflow for recommending media programs

An autodiscovery feature with an easy-to-use interface is provided to automatically collect metadata about electronic services for use within a business enterprise and to store that metadata in a metadata repository. The autodiscovery feature is used to create autodiscovery queries that are sent to electronic services to collect from the services' digests specified metadata useful for identifying the functionality of those services and integrating the services into business processes. Digests, such as RSS feeds and Atom feeds, are typically created by services to include useful metadata, such as the title of a service, the URL link to a description of the service, a brief description of the service, the publication date of the service, and other data. Autodiscovery queries can thus collect services' relevant metadata and store it in a business enterprise's metadata repository, so that the services' functionality can be quickly identified and used for business processes.

Autodiscovery of business services

A method and apparatus to employ a service proxy to personalize service messages by automatically supplying the interface parameters used for communications between a Service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specify during configuration of the messages used to communicate with one or more services. For simpler administration, the context variables may be organized in multiple kinds of hierarchies by which communications parameters specified at a higher level are automatically applied to categories at a lower level, although parameters specified directly for a lower-level category will override parameters from a higher category.

Non-intrusive personalization of web services

A method for automatic parallel processing of the steps involved in composing electronic responses to structured electronic requests where the request and the response contain some common fields of information. The process starts subsequent processing steps before the validation of the request is complete. A structurally complete, but partial response to a request is prepared as soon as it is possible to construct that response structure. The response structure is determined from personalization factors for the requestor, and a response template is created. The personalized response document is a skeleton created with known data from the minimum validation of the request, and with placeholders for data that has not yet been determined. The response is selectively populated with data from the request when the format of the response is determined. As additional information becomes available during the processing of the request, that additional data is placed into the response structure.

Parallel composition of electronic responses to electronic requests

An efficient organizer of companion guide rules is created by a validation application from the common set of rules among an industry's implementation guide and the rulebooks, such as companion guides of one or more entities, such as payers. The organizer of companion guide rules creates an inventory of all rules and a profile for each companion guide and stores each profile in metadata storage. Each profile contains pointers to code in the inventory for all the rules employed by the corresponding companion guide. After an EDI document reaches the validation application, a runtime checker engine checks metadata storage for a current rule set for the payer. A rule set is created the first time a profile is accessed during the validation process and whenever the profile is updated. The runtime checker engine attempts to validate the EDI document by comparing it to the current rule set for a payer's companion guide.

Growing community of inventors

Austin, TX, United States of America

Chaitanya Laxminarayan