会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 3. 发明授权
    • System and method for handling of destination host side congestion
    • 用于处理目的主机端拥塞的系统和方法
    • US08605578B1
    • 2013-12-10
    • US13115299
    • 2011-05-25
    • Rama K. GovindarajuPeter HochschildRajeev SivaramSridhar Raman
    • Rama K. GovindarajuPeter HochschildRajeev SivaramSridhar Raman
    • H04J1/16H04J3/14H04L1/00H04L12/26H04L12/28G01R15/16
    • H04L47/18H04L1/1838H04L47/12H04L47/266H04L47/30H04L47/32
    • Systems and methods are provided for managing congestion at a destination host in a network. A transport layer system manages receive buffer for application processes running on the destination host. Upon receiving the first packet of a new message from a source host, the system determines if there is enough free space in the receive buffer at the destination host to be reserved for the entire message. The system allocates receive buffer for the entire message if there is enough free receive buffer space. If there is not enough free buffer space, the system drops the message and sends a negative acknowledgment to the source host. The source host pauses transmission to the destination host upon receiving the negative acknowledgment. The system sends a resume message to the source host when there is enough free buffer. The source host retransmits the dropped message upon receiving the resume message.
    • 提供了系统和方法来管理网络中的目的主机的拥塞。 传输层系统管理在目标主机上运行的应用进程的接收缓冲区。 在从源主机接收到新消息的第一分组时,系统确定在目的主机处的接收缓冲器中是否有足够的可用空间来为整个消息保留。 如果有足够的空闲接收缓冲区空间,系统将为整个消息分配接收缓冲区。 如果没有足够的可用缓冲区空间,系统将丢弃该消息,并向源主机发送否定确认。 源主机收到否定确认后,暂停向目的地主机的传输。 当有足够的可用缓冲区时,系统会向源主机发送一条简历消息。 源主机在接收到恢复消息后重新发送丢弃的消息。
    • 5. 发明授权
    • Push mechanism for efficiently sending aggregated data items to client
    • 推送机制,有效地将汇总的数据项发送给客户端
    • US08260864B2
    • 2012-09-04
    • US12030836
    • 2008-02-13
    • Giselli Panontini De Souza SanaDaniel V KlingSridhar RamanJim R Van EatonRussell L Simpson
    • Giselli Panontini De Souza SanaDaniel V KlingSridhar RamanJim R Van EatonRussell L Simpson
    • G06F15/16
    • H04L65/1069H04L67/02H04L67/06H04L67/24H04L67/26
    • A server push model for client/server communications. The push architecture operates on top of a non-push (e.g., request/response) protocol (e.g., HTTP) to combine notifications from multiple data sources (e.g., email, text messaging, etc.). The server can be a middle-tier server (or proxy) to which a single web client registers interest in one or more notification types from one or more data sources. The mid-tier server aggregates the notifications from the various data sources and delivers the notifications to the requesting client via a single “push” pipe. The web client then distributes each notification to the appropriate parts of the client user interface. A producer/consumer locking mechanism eliminates blocking threads waiting on a mutual exclusion lock. A notification throttling mechanism distinguishes different types of notifications in order to guarantee that the client is not overloaded with too much information.
    • 用于客户端/服务器通信的服务器推送模型。 推送架构在非推送(例如,请求/响应)协议(例如,HTTP)之上操作以组合来自多个数据源(例如,电子邮件,文本消息等)的通知。 服务器可以是一个中间层服务器(或代理),一个Web客户端向一个或多个数据源注册一个或多个通知类型的兴趣。 中间层服务器聚合来自各种数据源的通知,并通过单个“推送”管道将通知发送到请求的客户端。 然后,Web客户机将每个通知分发到客户端用户界面的相应部分。 生产者/消费者锁定机制消除了阻塞线程等待互斥锁。 通知限制机制区分不同类型的通知,以保证客户端没有过多的信息。