会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明申请
    • Message Exchanger
    • 消息交换器
    • US20060235983A1
    • 2006-10-19
    • US11426581
    • 2006-06-26
    • Andrew LaymanGopal KakivayaSatish ThatteHenrik NielsenRobert Atkinson
    • Andrew LaymanGopal KakivayaSatish ThatteHenrik NielsenRobert Atkinson
    • G06F15/16
    • G06F17/30896G06F9/547H04L67/02H04L69/22
    • Using a message exchanger (“message exchanger”), data messages are exchanged between entities in a decentralized, distributed, potentially heterogeneous, network environment. The message exchanger employs XML (extensible Markup Language). To accomplish this, the entities on both ends of the message exchange understand, identify, and parse the message format. The message exchanger defines such a mechanism. Data messages are broken down into two portions—one portion (the body) is intended from an ultimate destination and the other portion (the header) is intended for intermediate destination and/or the ultimate destination. The body may be defined so that it must be understood by the ultimate destination. The header may be defined so that it must be understood or changed. Regardless, the data in the body is delivered intact to the ultimate destination. The message exchanger defines a message envelope exchange format in XML over a transport protocol, such as HTTP (HyperText Transport Protocol). This format allows for the execution of RPC (Remote Procedure Call) over XML, but it can be used for any message exchange over a network.
    • 使用消息交换器(“消息交换器”),在分散的,分布式的,潜在的异构网络环境中的实体之间交换数据消息。 消息交换机采用XML(可扩展标记语言)。 为了实现这一点,消息交换两端的实体理解,识别和解析消息格式。 消息交换机定义了这样的机制。 数据消息分为两部分 - 一部分(身体)来自最终目的地,而另一部分(标题)用于中间目的地和/或最终目的地。 身体可以被定义为使其必须被最终目的地理解。 标题可以被定义为必须被理解或改变。 无论如何,身体中的数据完整地传送到终极目的地。 消息交换器通过传输协议(例如HTTP(超文本传输​​协议))在XML中定义消息包络交换格式。 该格式允许通过XML执行RPC(远程过程调用),但它可以用于通过网络进行的任何消息交换。
    • 2. 发明申请
    • Object persister
    • 对象持续
    • US20060277458A9
    • 2006-12-07
    • US10893731
    • 2004-07-16
    • Andrew LaymanGopal KakivayaSatish Thatte
    • Andrew LaymanGopal KakivayaSatish Thatte
    • G06F17/00
    • G06F9/546G06F9/4493G06F9/465
    • Here is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialed object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.
    • 这里描述了一个对象持久化的实现,它将序列化对象以保留对象的数据结构及其当前数据。 序列化对象使用XML编码并插入到消息中。 该消息通过网络发送到实体。 这样的传输是使用诸如HTML之类的标准因特网协议执行的。 接收实体接收到序列化对象后,反序列化对象即可使用。 对象持久化不是包含引用对象在序列化对象中的副本,而是包含对这些对象的引用。 这样可以避免同一对象的冗余包含,并且可能无限地包含正在被序列化的对象本身。
    • 3. 发明申请
    • Object persister
    • 对象持续
    • US20060123333A9
    • 2006-06-08
    • US10892744
    • 2004-07-16
    • Andrew LaymanGopal KakivayaSatish Thatte
    • Andrew LaymanGopal KakivayaSatish Thatte
    • G06F17/00
    • G06F9/546G06F9/4493G06F9/465
    • Herein is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.
    • 这里描述了对象持久化的实现,其将对象序列化以保留对象的数据结构及其当前数据。 序列化对象使用XML编码并插入到消息中。 该消息通过网络发送到实体。 这样的传输是使用诸如HTML之类的标准因特网协议执行的。 在接收到序列化对象后,接收实体反序列化对象使用它。 对象持久化不是包含引用对象在序列化对象中的副本,而是包含对这些对象的引用。 这样可以避免同一个对象的冗余包含,并且可能无限地包含被序列化的对象本身。
    • 5. 发明申请
    • Generalized protocol mapping
    • 广义协议映射
    • US20060085560A1
    • 2006-04-20
    • US10956849
    • 2004-10-01
    • David LangworthySatish Thatte
    • David LangworthySatish Thatte
    • G06F15/16
    • H04L67/2823H04L67/02H04L67/28
    • Signals are mapped from one protocol to another protocol. A first protocol is received, and a mapping interface is generated to a second protocol. The first protocol is then mapped to the second protocol in accordance with the mapping interface. The mapping interface may comprise a coordination map. Moreover, a state diagram may be generated that is based on the first protocol, prior to mapping the first protocol to the second protocol. The first protocol may be an abstract protocol or a web services business activity protocol, for example, and the second protocol may be another abstract protocol, a concrete interface, a web services interface, a common language runtime interface, or a business process execution language for web services, for example.
    • 信号从一个协议映射到另一个协议。 接收到第一协议,并且生成到第二协议的映射接口。 然后根据映射界面将第一协议映射到第二协议。 映射界面可以包括协调图。 此外,在将第一协议映射到第二协议之前,可以生成基于第一协议的状态图。 例如,第一协议可以是抽象协议或Web服务业务活动协议,并且第二协议可以是另一抽象协议,具体接口,Web服务接口,公共语言运行时接口或业务流程执行语言 例如用于Web服务。
    • 6. 发明申请
    • Processing convoy workflow scenarios
    • 处理车队工作流场景
    • US20050015776A1
    • 2005-01-20
    • US10452961
    • 2003-06-02
    • Bimal MehtaJohannes KleinLee GraberPaul MaybeeSriram BalasubramanianSanjib SahaSatish ThattePaul Ringseth
    • Bimal MehtaJohannes KleinLee GraberPaul MaybeeSriram BalasubramanianSanjib SahaSatish ThattePaul Ringseth
    • G06F3/00G06F9/46
    • G06F9/54G06F2209/542
    • An XLANG/s compiler detects convoy scenarios during compilation and generates runtime directives to correctly correlate incoming messages with business process instances. A convoy scenario, present in event driven processes, is defined by a correlation set initialized during a receive operation which is provided to a subsequent receive operation. The compiler detects those convoy scenarios by analyzing the control and dataflow of a XLANG/s program. Three convoy patterns are distinguished: (1) activation convoys, (2) uniform sequential convoys, and (3) non-uniform sequential convoys. XLANG/s allows declarative descriptions of convoy scenarios without requiring an understanding of the low-level details supporting their correct execution. Convoy scenarios are processed by statically analyzing a written workflow application to deduce the nature and type of convoy scenarios used by the application. Information is extracted at compile time to support the runtime infrastructure. The runtime infrastructure is tightly integrated with the underlying correlation and subscription evaluation framework.
    • XLANG / s编译器在编译期间检测车队场景,并生成运行时指令,将传入的消息与业务流程实例正确关联。 存在于事件驱动过程中的车队场景由在提供给后续接收操作的接收操作期间初始化的相关集定义。 编译器通过分析XLANG / s程序的控制和数据流来检测这些车队场景。 三个车队模式有区别:(1)活动车队,(2)统一的顺序车队,(3)不均匀的顺序车队。 XLANG / s允许对车队场景的声明性描述,而不需要了解支持其正确执行的低级细节。 通过静态分析书面工作流应用程序来演绎应用程序使用的车队场景的性质和类型来处理方便情景。 在编译时提取信息以支持运行时基础设施。 运行时基础架构与底层的相关和订阅评估框架紧密集成。
    • 7. 发明授权
    • Single virtual client for multiple client access and equivalency
    • 单个虚拟客户端,用于多个客户端访问和等效
    • US07921189B2
    • 2011-04-05
    • US11602085
    • 2006-11-20
    • Rahul KapoorRolando Jimenez SalgadoSatish ThatteYi MaoRicard Roma I DalfóAnuj BansalSaji Varkey
    • Rahul KapoorRolando Jimenez SalgadoSatish ThatteYi MaoRicard Roma I DalfóAnuj BansalSaji Varkey
    • G06F15/177
    • H04L67/306H04L67/24H04W8/18Y10S707/99931
    • A single virtual image of client information centrally located at an always-on network location for maintaining equivalency among multiple user devices. The image can be accessed by the user devices when coming online to upload and receive changes in the client information. A mid-tier system can be employed as the always-on central location with which the user client machines can communicate to maintain the same set of client information. Services in support thereof include an ownership service for dynamic selection of a designated client machine to take ownership for performing the actions on one client machine and arbitration of duplicate requests, a notification service for allowing data sources to publish cache update instructions to a central place, a roaming service for allowing clients machines to share state with each other, and an encryption service for secure storage and communications of client information.
    • 客户端信息的单个虚拟映像集中位于永远在线的网络位置,用于维护多个用户设备之间的等效性。 用户设备上线时可以访问该图像,上传并接收客户端信息的更改。 中层系统可以用作始终在线的中心位置,用户客户机可以通过该中心位置进行通信以维护相同的客户端信息。 支持的服务包括用于动态选择指定的客户端机器的所有权服务以获得用于执行一个客户端机器上的动作和对重复请求的仲裁,用于允许数据源将高速缓存更新指令发布到中心位置的通知服务, 用于允许客户机彼此共享状态的漫游服务,以及用于安全存储和客户端信息通信的加密服务。
    • 9. 发明授权
    • Versioning and concurrency control for multiple client access of data
    • 数据的多客户端访问的版本控制和并发控制
    • US07805420B2
    • 2010-09-28
    • US11602069
    • 2006-11-20
    • Rahul KapoorRolando Jimenez SalgadoKaushik RajSatish ThatteXiaoyu Wu
    • Rahul KapoorRolando Jimenez SalgadoKaushik RajSatish ThatteXiaoyu Wu
    • G06F17/30
    • G06F17/30348
    • Versioning and concurrency control architecture of data operations on data of a data source by multiple independent clients of a user. Data operation messages between the clients and the data source are intercepted and tracked for serialization control to a data view instance of the data source. The architecture can be located as an always-on centrally-located system (e.g., mid-tier), accommodate data operations that include create, read, update, delete, and query (CRUDQ) against data sources, and provides support for distributed transactions, locking, versioning, and reliable messaging, for example, for data sources that do not expose such capabilities. A hash is employed for version control and to control changes at the data source. The central system also provides logic for the individual CRUDQ operations, and granular error classification to enable retries whenever possible.
    • 由用户的多个独立客户端对数据源的数据进行数据操作的版本控制和并发控制架构。 客户端和数据源之间的数据操作消息被拦截并被跟踪以便对数据源的数据视图实例进行串行化控制。 该体系结构可以作为始终处于中心位置的系统(例如,中间层)进行定位,适应数据源的数据操作,包括创建,读取,更新,删除和查询(CRUDQ),并为分布式事务提供支持 ,锁定,版本控制和可靠的消息传递,例如,对于不暴露此类功能的数据源。 使用哈希来进行版本控制,并控制数据源的更改。 中央系统还为单个CRUDQ操作提供了逻辑,并且在可能的情况下进行了细粒度的错误分类,以便重试。