MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES
    1.
    发明申请
    MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES 审中-公开
    基于消息要求的消息路由

    公开(公告)号:US20100325215A1

    公开(公告)日:2010-12-23

    申请号:US12487656

    申请日:2009-06-19

    IPC分类号: G06F15/173 G06F15/16

    摘要: Architecture for enabling messages to be routed between network servers based on message requirements related to version, capabilities, and features, for example. The message requirements designate delivery over a transport path compatible with the message requirements. The message requirements can include a particular version or other features related to different software applications that require compatibility in message handling. Routing information is maintained related to a transport server or other network transport entity compatible with the message requirements and through which the message can be routed. The message is routed to the compatible transport server for delivery to the destination while avoiding delivery to transport servers incompatible with the message requirements.

    摘要翻译: 基于与版本,功能和功能有关的消息要求,使消息在网络服务器之间路由的体系结构。 消息要求指定通过与消息要求兼容的传输路径进行传送。 消息要求可以包括与消息处理中需要兼容性的不同软件应用相关的特定版本或其他功能。 维护路由信息与传输服务器或与消息要求兼容的其他网络传输实体相关,并且可以通过该路由信息路由消息。 消息被路由到兼容的传输服务器以传送到目的地,同时避免传送到不符合消息要求的传输服务器。

    Transport high availability via acknowledge management
    2.
    发明授权
    Transport high availability via acknowledge management 有权
    通过确认管理传输高可用性

    公开(公告)号:US08352558B2

    公开(公告)日:2013-01-08

    申请号:US12368312

    申请日:2009-02-10

    IPC分类号: G06F15/16

    CPC分类号: H04L51/06 H04L51/30

    摘要: Architecture that facilitates transport high availability for messaging services by providing the ability of a receiving entity (e.g., receiving message transfer agent (MTA)) to detect if a sending entity (e.g., sending MTA or client) is a legacy sending entity. When the receiving entity detects that the sending entity is a legacy system, by advertising transport high availability capability to the sending entity, if the sending entity does not opt-in to this capability, the receiving entity keeps the sending entity client “on hold”, that is, waiting for an acknowledgement (ACK) until the receiving entity delivers the message to the next hops (immediate destinations). This approach maintains at least two copies of the message until the message is successfully delivered (to the next hop(s)). Hence, if the legacy sending entity or the receiving entity fails, the message is still delivered successfully.

    摘要翻译: 通过提供接收实体(例如,接收消息传送代理(MTA))的能力来检测发送实体(例如,发送MTA或客户端)是否是传统发送实体,促进了消息传送服务的高可用性的架构。 当接收实体检测到发送实体是传统系统时,通过向发送实体发送传输高可用性能力,如果发送实体不选择该能力,则接收实体保持发送实体客户端处于保持状态, 是等待确认(ACK),直到接收实体将消息传递到下一跳(即时目的地)。 该方法维护消息的至少两个副本,直到消息成功传递(下一跳)为止。 因此,如果传统发送实体或接收实体失败,则该消息仍然成功传送。

    High availability message transfer system for side effect messages
    3.
    发明授权
    High availability message transfer system for side effect messages 有权
    用于副作用信息的高可用性消息传输系统

    公开(公告)号:US08069211B2

    公开(公告)日:2011-11-29

    申请号:US12358281

    申请日:2009-01-23

    IPC分类号: G06F13/00

    CPC分类号: H04L51/30

    摘要: Architecture that protects side effect messages by associating the side effect messages with a primary (redundant) message that was received by a transport mechanism (e.g., a message transport agent). Side effect messages are considered “side effects” of a primary message that caused generation of the side effect messages. The primary message is only considered fully delivered after the primary message and all associated side effect messages are delivered, after which the source of the primary message is ACK'd (sent an “ACKnowledgement” message). Hence, in case of hardware failures after the primary message was delivered, but before delivery of side effect messages, the redundancy approach used triggers re-delivery of the primary message and re-generation and delivery of the side effect messages.

    摘要翻译: 通过将副作用消息与由传输机制(例如,消息传输代理)接收的主(冗余)消息相关联来保护副作用消息的架构。 副作用消息被认为是导致副作用消息的产生的主要消息的“副作用”。 主消息仅在主消息和所有相关的副作用消息被传递之后才被认为是完全传递的,之后主消息的源被ACK'(发送“确认”消息)。 因此,在发送主消息之后但在发送副作用消息之前的硬件故障的情况下,所使用的冗余方法触发了主消息的重新传递,并且重新生成和传递副作用消息。

    TRANSPORT HIGH AVAILABILITY VIA ACKNOWLEDGE MANAGEMENT
    4.
    发明申请
    TRANSPORT HIGH AVAILABILITY VIA ACKNOWLEDGE MANAGEMENT 有权
    通过承诺管理运输高可用性

    公开(公告)号:US20100205257A1

    公开(公告)日:2010-08-12

    申请号:US12368312

    申请日:2009-02-10

    IPC分类号: G06F15/16

    CPC分类号: H04L51/06 H04L51/30

    摘要: Architecture that facilitates transport high availability for messaging services by providing the ability of a receiving entity (e.g., receiving message transfer agent (MTA)) to detect if a sending entity (e.g., sending MTA or client) is a legacy sending entity. When the receiving entity detects that the sending entity is a legacy system, by advertising transport high availability capability to the sending entity, if the sending entity does not opt-in to this capability, the receiving entity keeps the sending entity client “on hold”, that is, waiting for an acknowledgement (ACK) until the receiving entity delivers the message to the next hops (immediate destinations). This approach maintains at least two copies of the message until the message is successfully delivered (to the next hop(s)). Hence, if the legacy sending entity or the receiving entity fails, the message is still delivered successfully.

    摘要翻译: 通过提供接收实体(例如,接收消息传送代理(MTA))的能力来检测发送实体(例如,发送MTA或客户端)是否是传统发送实体,促进了消息传送服务的高可用性的架构。 当接收实体检测到发送实体是遗留系统时,通过向发送实体发送传输高可用性能力,如果发送实体不选择该能力,则接收实体保持发送实体客户端“保持” ,即等待确认(ACK),直到接收实体将消息传递到下一跳(即时目的地)为止。 该方法维护消息的至少两个副本,直到消息成功传递(下一跳)为止。 因此,如果传统发送实体或接收实体失败,则该消息仍然成功传送。

    TRANSPORT HIGH AVAILABILITY FOR SIDE EFFECT MESSAGES
    5.
    发明申请
    TRANSPORT HIGH AVAILABILITY FOR SIDE EFFECT MESSAGES 有权
    运输高效率的副作用信息

    公开(公告)号:US20100191810A1

    公开(公告)日:2010-07-29

    申请号:US12358281

    申请日:2009-01-23

    IPC分类号: G06F15/82

    CPC分类号: H04L51/30

    摘要: Architecture that protects side effect messages by associating the side effect messages with a primary (redundant) message that was received by a transport mechanism (e.g., a message transport agent). Side effect messages are considered “side effects” of a primary message that caused generation of the side effect messages. The primary message is only considered fully delivered after the primary message and all associated side effect messages are delivered, after which the source of the primary message is ACK'd (sent an “ACKnowledgement” message). Hence, in case of hardware failures after the primary message was delivered, but before delivery of side effect messages, the redundancy approach used triggers re-delivery of the primary message and re-generation and delivery of the side effect messages.

    摘要翻译: 通过将副作用消息与由传输机制(例如,消息传输代理)接收的主(冗余)消息相关联来保护副作用消息的架构。 副作用消息被认为是导致副作用消息的产生的主要消息的“副作用”。 主消息仅在主消息和所有相关的副作用消息被传递之后才被认为是完全传递的,之后主消息的源被ACK'(发送“确认”消息)。 因此,在发送主消息之后但在发送副作用消息之前的硬件故障的情况下,所使用的冗余方法触发了主消息的重新传递,并且重新生成和传递副作用消息。