会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 22. 发明申请
    • TRANSPORT HIGH AVAILABILITY FOR SIDE EFFECT MESSAGES
    • 运输高效率的副作用信息
    • US20100191810A1
    • 2010-07-29
    • US12358281
    • 2009-01-23
    • Victor BoctorTodd C. LuttinenJeffrey B. Kay
    • Victor BoctorTodd C. LuttinenJeffrey B. Kay
    • G06F15/82
    • 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'(发送“确认”消息)。 因此,在发送主消息之后但在发送副作用消息之前的硬件故障的情况下,所使用的冗余方法触发了主消息的重新传递,并且重新生成和传递副作用消息。
    • 23. 发明申请
    • EXTENSIBILITY FOR HOSTED MESSAGING SERVERS
    • 传播消息服务器的可扩展性
    • US20100185735A1
    • 2010-07-22
    • US12356552
    • 2009-01-21
    • Wilbert De GraafJeffrey B. KayKhalid RazzagSaeed NoursalehiVictor Boctor
    • Wilbert De GraafJeffrey B. KayKhalid RazzagSaeed NoursalehiVictor Boctor
    • G06F15/16
    • G06Q10/107
    • Architecture for messaging server extensibility without the need to update or make changes to the messaging server by routing selected messages to a remote location for processing by custom code or third-party code. The messaging server routes the selected messages based server analysis of the messages and in view of configuration data (or conditions) for routing messages. The remote location processes the message and can instruct the messaging server to accept, reject, or redirect the message. Additionally, the remote location can modify the message and instruct the messaging server to process the modified message. The hosted organization can configure triggers to have the messaging server call to a web service with the messages, which extends the functionality of the messaging server.
    • 用于消息传递服务器可扩展性的体系结构,无需通过将所选消息路由到远程位置来更新或更改消息传递服务器,以便通过自定义代码或第三方代码进行处理。 消息收发服务器根据消息的服务器分析和针对路由消息的配置数据(或条件)路由所选消息。 远程位置处理消息并且可以指示消息传递服务器接受,拒绝或重定向消息。 此外,远程位置可以修改消息并指示消息传递服务器处理修改的消息。 托管组织可以配置触发器以使邮件服务器通过邮件调用Web服务,这扩展了邮件服务器的功能。
    • 25. 发明授权
    • Techniques to normalize names efficiently for name-based speech recognition grammars
    • 基于名称的语音识别语法有效地对名称进行归一化的技术
    • US08990080B2
    • 2015-03-24
    • US13359919
    • 2012-01-27
    • Mini VarkeyBernardo SanaVictor BoctorDiego Carlomagno
    • Mini VarkeyBernardo SanaVictor BoctorDiego Carlomagno
    • G10L15/00G10L15/19
    • G10L15/19
    • Techniques to normalize names for name-based speech recognition grammars are described. Some embodiments are particularly directed to techniques to normalize names for name-based speech recognition grammars more efficiently by caching, and on a per-culture basis. A technique may comprise receiving a name for normalization, during name processing for a name-based speech grammar generating process. A normalization cache may be examined to determine if the name is already in the cache in a normalized form. When the name is not already in the cache, the name may be normalized and added to the cache. When the name is in the cache, the normalization result may be retrieved and passed to the next processing step. Other embodiments are described and claimed.
    • 描述了基于名称的语音识别语法规范化名称的技术。 一些实施例特别涉及通过缓存和每个文化基础更有效地对基于名称的语音识别语法的名称进行规范化的技术。 一种技术可以包括在名称处理期间接收用于归一化的名称,用于基于名称的语音生成过程。 可以检查归一化缓存以确定名称是否已经以标准化形式存在于高速缓存中。 当名称不在缓存中时,名称可能会被归一化并添加到缓存中。 当名称在缓存中时,可以检索归一化结果并将其传递到下一个处理步骤。 描述和要求保护其他实施例。
    • 26. 发明授权
    • Throttling non-delivery reports based on root cause
    • 根据根本原因调整不送货报告
    • US08484512B2
    • 2013-07-09
    • US12751141
    • 2010-03-31
    • Sara L. ManningVictor BoctorTodd Carlyle Luttinen
    • Sara L. ManningVictor BoctorTodd Carlyle Luttinen
    • G06F11/00
    • H04L65/4076
    • A root cause for a failed attempted delivery of a message is attempted to be determined before sending a non-delivery report (NDR) for the failed message. When a message fails without a known cause, the root cause is determined using the context of the message. For a given context, the root cause may be determined by a single failure or it may be determined by the relative number of failed messages delivery are deferred from being delivered, as is generation of the corresponding same context. While determining the root cause of the problem, any messages failing NDR(s), to allow time for corrective action to occur. If the problem is resolved within a predetermined time period, the deferred messages are delivered without having to issue NDR(s).
    • 在发送失败消息的未送达报告(NDR)之前,尝试确定尝试传递消息失败的根本原因。 当消息在没有已知原因的情况下失败时,使用消息的上下文来确定根本原因。 对于给定的上下文,根本原因可以由单个故障确定,或者可以由失败的消息的递送的相对数量来确定,因为生成相应的上下文。 在确定问题的根本原因的同时,任何失败的NDR消息,以允许发生纠正措施的时间。 如果问题在预定时间段内解决,则递送的消息被传送而不必发行NDR。
    • 27. 发明申请
    • Using Distributed Source Control in a Centralized Source Control Environment
    • 在集中源控制环境中使用分布式源代码控制
    • US20130159365A1
    • 2013-06-20
    • US13328272
    • 2011-12-16
    • Victor BoctorTheodore Albert Bucher
    • Victor BoctorTheodore Albert Bucher
    • G06F17/30
    • G06F16/178G06F8/71G06F16/116G06F16/162G06F16/1844G06F16/273
    • A method is presented for using a distributed source control system with a centralized source control system. A first set of files is obtained from a source control repository and stored on a first electronic computing device. The first set of files comprises all or part of a code base in the centralized source control system. A request is received for at least part of the code base from a second electronic computing device in a distributed source control system. As a result of the request, at least a part of the first set of files is sent to the second electronic computing device. A change set for the first set of files is received from the second electronic computing device. The change set is processed to be in a format compatible with the source control repository. The change set is submitted to the source control repository.
    • 提出了一种使用具有集中式源控制系统的分布式源控制系统的方法。 第一组文件从源控制存储库获得并存储在第一电子计算设备上。 第一组文件包括集中式源控制系统中的全部或部分代码库。 从分布式源控制系统中的第二电子计算设备接收至少部分代码库的请求。 作为请求的结果,第一组文件的至少一部分被发送到第二电子计算设备。 从第二电子计算设备接收到用于第一组文件的改变集合。 更改集被处理为与源代码管理库兼容的格式。 更改集提交到源代码管理库。
    • 29. 发明授权
    • Transport high availability via acknowledge management
    • 通过确认管理传输高可用性
    • US08352558B2
    • 2013-01-08
    • US12368312
    • 2009-02-10
    • Victor BoctorTodd C. LuttinenJeffrey B. KayJesse M. DoughertyMalcom Pearson
    • Victor BoctorTodd C. LuttinenJeffrey B. KayJesse M. DoughertyMalcom Pearson
    • G06F15/16
    • H04L51/06H04L51/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),直到接收实体将消息传递到下一跳(即时目的地)。 该方法维护消息的至少两个副本,直到消息成功传递(下一跳)为止。 因此,如果传统发送实体或接收实体失败,则该消息仍然成功传送。