Consistent interface for feed event, feed event document and feed event type

US9237425B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9237425-B2
Application numberUS-201213398264-A
CountryUS
Kind codeB2
Filing dateFeb 16, 2012
Priority dateFeb 16, 2012
Publication dateJan 12, 2016
Grant dateJan 12, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a feed event, a feed event document, and/or a feed event type business object.

First claim

Opening claim text (preview).

What is claimed is: 1. A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about events and user input for which users are notified in a feed system, the medium comprising: program code for receiving a first message via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry, the first message received from a heterogeneous application executing in an environment of computer systems providing message-based services, the first message for querying information about feed events according to specified selection elements, the first message including a first message package derived from the common business object model, the first message package hierarchically organized in memory based on the common business object model, the first message package including: at a first hierarchical level in the first message package, a feed event query message entity; and at the first hierarchical level in the first message package, a feed event package comprising, at a second hierarchical level in the first message package, a feed event entity, where the feed event entity includes, at a third hierarchical level in the first message package, a universally unique identifier (UUID), system administrative data, and at least one creation identity entity; program code for processing the first message according to the hierarchical organization of the first message package, where processing the first message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the first message; and program code for sending a second message to the heterogeneous application responsive to the first message, where the second message includes a second message package derived from the common business object model to provide consistent semantics with the first message package. 2. The computer readable medium of claim 1 , wherein the feed event entity further includes at least one of the following: a source object name, a source object type name, source change context eXtensible Markup Language (XML) encoded text, a source object identifier (ID), source object add/delete nodes XML encoded text, a source object has children indicator, a source parent object ID, and a children counter value. 3. A distributed system operating in a landscape of computer systems providing message-based services defined in a service registry, the system comprising: at least one processor operable to execute computer readable instructions embodied on non-transitory media; a graphical user interface executable by the at least one processor and comprising computer readable instructions, embedded on non-transitory media, for querying information about feed events according to specified selection elements using a request; a first memory storing a user interface controller executable by the at least one processor for processing the request and involving a message including a first message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the first message package hierarchically organized based on the common business object model, the hierarchical organization of the first message package including: at a first hierarchical level in the first message package, a feed event query message entity; and at the first hierarchical level in the first message package, a feed event package comprising, at a second hierarchical level in the first message package, a feed event entity, where the feed event entity includes, at a third hierarchical level in the first message package, a universally unique identifier (UUID), system administrative data, and at least one creation identity entity; and a second memory, remote from the graphical user interface, storing a plurality of service interfaces executable by the at least one processor and derived from the common business object model to provide consistent semantics with messages derived from the common business object model, where one of the service interfaces is operable to process the message via the service interface according to the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the message. 4. The distributed system of claim 3 , wherein the first memory is remote from the graphical user interface. 5. The distributed system of claim 3 , wherein the first memory is remote from the second memory. 6. A non-transitory computer readable medium including program code for providing a message-based interface for exchanging a language-dependent document describing an event or an input created directly by a user, the medium comprising: program code for receiving a first message via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry, the first message received from a heterogeneous application executing in an environment of computer systems providing message-based services, the first message for querying feed event documents according to specified selection elements, the first message including a first message package derived from the common business object model, the first message package hierarchically organized in memory based on the common business object model, the first message package including: at a first hierarchical level in the first message package, a feed event document query message entity; and at the first hierarchical level in the first message package, a feed event document package comprising, at a second hierarchical level in the first message package, a feed event document entity, where the feed event document entity includes, at a third hierarchical level in the first message package, a universally unique identifier (UUID), a feed event UUID, a feed event type code, at least one feed event type entity, and at least one feed event entity; program code for processing the first message according to the hierarchical organization of the first message package, where processing the first message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the first message; and program code for sending a second message to the heterogeneous application responsive to the first message, where the second message includes a second message package derived from the common business object model to provide consistent semantics with the first message package. 7. The computer readable medium of claim 6 , wherein the feed event document entity further includes at least one of the followin

Assignees

Inventors

Classifications

  • H04W4/12Primary

    Messaging; Mailboxes; Announcements · CPC title

  • Office automation; Time management · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9237425B2 cover?
A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, so…
Who is the assignee on this patent?
Vins Miro, Mendicino Vincent, Wodtke Dirk, and 9 more
What technology area does this patent fall under?
Primary CPC classification H04W4/12. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 12 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).