Nothing Special   »   [go: up one dir, main page]

US20050114517A1 - Messaging proxy system - Google Patents

Messaging proxy system Download PDF

Info

Publication number
US20050114517A1
US20050114517A1 US10/824,200 US82420004A US2005114517A1 US 20050114517 A1 US20050114517 A1 US 20050114517A1 US 82420004 A US82420004 A US 82420004A US 2005114517 A1 US2005114517 A1 US 2005114517A1
Authority
US
United States
Prior art keywords
message
transport protocol
proxy
client
mom
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/824,200
Inventor
Silvano Maffeis
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Taiwan Semiconductor Manufacturing Co TSMC Ltd
Original Assignee
Softwired AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Softwired AG filed Critical Softwired AG
Priority to US10/824,200 priority Critical patent/US20050114517A1/en
Publication of US20050114517A1 publication Critical patent/US20050114517A1/en
Priority to US12/371,924 priority patent/US20090157836A1/en
Priority to US12/371,921 priority patent/US8650244B2/en
Priority to US12/371,917 priority patent/US20090157883A1/en
Assigned to SOFTWIRED AG reassignment SOFTWIRED AG ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MAFFEIS, SILVANO
Assigned to TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD. reassignment TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SOFTWIRED AG
Assigned to TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD. reassignment TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SOFTWIRED AG
Priority to US14/153,958 priority patent/US9906487B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/2876—Pairs of inter-processing entities at each side of the network, e.g. split proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/169—Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the invention relates to techniques for the delivery of electronic messages between hardware or software components across wireless and wireline networks, between mobile and non-mobile devices.
  • JMS Java Message oriented middleware
  • topics publish/subscribe messaging
  • queues point-to-point messaging
  • the standard describes the interface to the messaging middleware, the implementation of the middleware is not specified.
  • integration of wireless mobile devices is not specified.
  • Existing messaging middleware allows one to access the middleware from non-mobile devices (personal computers or server computers) over wireline networks (Ethernet or Token Ring). These networks usually run communication protocols such as TCP/IP, HTTP or SSL. Supporting wireless mobile devices requires the vendor of the middleware to implement a message transmission protocol atop a wireless transport protocol (such as WAP, GSM, SMS, GPRS, or UMTS) and to integrate this message transmission protocol into the middleware.
  • a wireless transport protocol such as WAP, GSM, SMS, GPRS, or UMTS
  • a further object of the invention is to provide a computer program product comprising a computer usable medium having thereon computer readable program code means for implementing on a computer connected to a wired computer network.
  • Still another object of the invention is to provide a computer program directly loadable into the memory of a mobile device and allowing the mobile device to access a messaging middleware product according to the state of the art, without needing to load that messaging middleware into the memory of the mobile device entirely.
  • the messaging proxy system outlined in this disclosure is a major technological advancement enabling users of state of the art messaging middleware products to send and receive messages to and from mobile devices, over any wireless transport protocol, without requiring that the state of the art messaging middleware be loaded into the memory of the mobile devices.
  • the system for running said message proxy installation includes a message proxy implemented by a computer program with a system architecture comprising at least one pluggable protocol adapter.
  • the proxy further comprises at least one pluggable database adapter.
  • the invention also comprises a thin message client computer program directly loadable into the memory of a mobile device.
  • This thin message client program allows a mobile device to exchange message and command tokens with a message oriented middleware according to the state of the art, by using the proxy computer program as an intermediary between the thin client and the message oriented middleware and thereby using at least one wireless transport protocol.
  • the thin message client computer program embodies a system architecture of at least one pluggable protocol adapter.
  • it also embodies a system architecture of at least one pluggable database adapter.
  • FIG. 1 provides a block diagram of a preferred embodiment of the system according to the present invention.
  • FIG. 2 shows a UML sequence diagram of an embodiment of the method according to the present invention.
  • FIG. 1 provides a block diagram of a preferred embodiment of the present invention. It more particularly shows an installation of software tools loaded on non-mobile computers and mobile wireless devices, the installation comprising:
  • the block diagram is but one example of a message proxy infrastructure deployment. Any number of message proxies, thin JMS message clients, message oriented middleware products, and message oriented middleware product clients can be present in a specific installation.
  • the message proxy 1 may be implemented on a conventional computer network server, e.g on a Windows-NT-server and may e.g. run in the background. It maintains client connections, maintains client subscriptions to JMS topics and queues, receives and forwards JMS messages, and stores JMS messages in its database, such that they will not be lost when a client is disconnected from the proxy.
  • a conventional computer network server e.g on a Windows-NT-server and may e.g. run in the background. It maintains client connections, maintains client subscriptions to JMS topics and queues, receives and forwards JMS messages, and stores JMS messages in its database, such that they will not be lost when a client is disconnected from the proxy.
  • the message proxy 1 comprises at least one pluggable transport protocol adapter.
  • FIG. 1 shows an example of six specific wireless transport protocol adapters (WAP 1 a , UMTS 1 b , HTTP 1 c , DAB/GSM Data 1 d , SMS 1 e , GPRS 1 f ). Any number of additional wireless protocol adapters 1 g can be present.
  • Pluggable protocol adapters allow the message proxy to send and receive messages to and from message clients using arbitrary wireless protocols.
  • a protocol adapter embodies an existing transport protocol, such as GPRS or TCP/IP, and also provides additional features on top of the existing transport protocol. Examples of such additional features include data encryption and guaranteed delivery of messages.
  • a protocol adapter is divided into one or more protocol objects. Each protocol object provides one part of the functionality offered by the protocol adapter. For example, a protocol object can encrypt data, or compress data, or request the sender of the data to retransmit a message which was lost on the network.
  • the message proxy 1 also comprises a database adapter. This allows the proxy to store messages and client subscription information into arbitrary databases.
  • the message proxy 1 On startup, the message proxy 1 reads its configuration data and initializes all configured protocol adapters. It also initializes the topic and queue subscriptions of all the message clients which are known to the proxy. At runtime, additional protocol adapters can be started, or running protocol adapters can be stopped, without interrupting the message proxy service (however, if a specific protocol adapter is stopped, service over this adapter is no longer available). At runtime, additional clients can be connected to the proxy, or existing clients can be disconnected from the proxy.
  • Each thin JMS message client 2 , 2 ′, 2 ′′ is installed on a mobile wireless device such as a mobilephone, a small laptop computer with a wireless modem, a palmtop device or any other device comprising a processor, a memory and communication means for communicating wirelessly. It contains a JMS programming library which is identical or similar to at least a part of the programming library used by messaging middle 3 of the state of the art.
  • the thin JMS message client library is small enough to be loaded into the memory of the mobile devices which have constrained memory and processing power.
  • the thin JMS message client mainly consists of the JMS interface. Most of the Java code necessary for implementing the interface is running on the proxy, and not on the thin JMS message client.
  • the proxy also maintains the JMS state information associated with the client. For example, the proxy stores the JMS messages which have not been acknowledged by the client yet. Also, the thin JMS message client does not need to store the names of the queues and topics it is subscribed to. This information is stored only by the proxy. Internally, the thin JMS client uses code information, such as number values, to refer to topics and queues.
  • This code information can be as small as one byte.
  • the client sends to the proxy only the JMS message and the code information related with the topic. All this considerably reduces the footprint of the thin JMS client.
  • the thin JMS message client 2 also contains a command and message transmission system comprising a transport protocol adapter 2 a , 2 a ′, 2 a ′′ used for informing the proxy of what JMS topics and queues the client wants to subscribe to.
  • a transport protocol adapter 2 a , 2 a ′, 2 a ′′ used for informing the proxy of what JMS topics and queues the client wants to subscribe to.
  • the message client 2 , 2 ′, 2 ′′ also comprises a database adapter. This allows the client to store JMS messages and other information locally, using arbitrary databases.
  • the message database is necessary to ensure that JMS messages and JMS subscriptions submitted by the client are not lost in case the client cannot communicate with the proxy due to lack of wireless network coverage, or because the proxy is not running.
  • a message client 2 , 2 ′, 2 ′′ links to the message proxy 1 , using its transport protocol adapter 2 a , 2 a ′, 2 a ′′. If a matching protocol adapter is running on the proxy, the connection is successful. Further communication between message client and message proxy is according to the familiar publish/subscribe or point-to-point model of JMS.
  • JMS topics or JMS queues are named and administered independently of the protocol adapters involved. If a client connects to the proxy using the “WAP” protocol adapter, it can communicate with a client that connected using the “GPRS” protocol adapter, if both clients use the same JMS topic or queue.
  • the protocol adapters encapsulate at least one logic needed to:
  • Protocol adapters consist of both the transport protocol mechanism, and a quality of service mechanism to improve the basic network delivery guarantee.
  • the sending protocol adapter attaches a reliability indicator such as a sequence number to all outgoing messages.
  • the reliability indicator is varied in a predefined manner upon sending a message. E.g., the sequence number is incremented by one after each sent message.
  • the receiver application uses the reliability indicator of the incoming message to detect whether a message was lost. In the described example, this is the case when the sequence number of the just received message is greater than the sequence number of the previous message, plus one.
  • the receiver sends a command token to the sender indicating which messages are to be retransmitted. The sender then retransmits the requested messages.
  • the sender keeps messages in a local database to be able to fulfill a message retransmission request.
  • the database adapters encapsulate at least one logic needed to:
  • the message client 2 implements e.g. the JMS API from Sun Microsystems. It cooperates with the proxy to achieve full JMS functionality.
  • the client wants to subscribe to a JMS queue or topic, its command subsystem creates a command token containing the subscription information.
  • the command token is then sent to the proxy using wireless communication.
  • the token is sent via a protocol adapter 2 a , 2 a ′, 2 a ′′ at the client side and received by a protocol adapter 1 a , 1 b , 1 c , 1 d , 1 e , 1 f or 1 g at the proxy side.
  • the proxy 1 On receipt of a command token, the proxy 1 reads the subscription information contained in the token, and performs a JMS subscription with the state of the art middleware, on behalf of the client.
  • Further command tokens are generated when the client wants to unsubscribe from a JMS topic or queue, when the client wants to transmit a JMS message, or for any other JMS action which is requested by the client.
  • the proxy 1 When a JMS message is received on a topic or queue the proxy 1 is subscribed to on behalf of the client, the proxy creates a message token containing the data of the JMS message. The message token is then sent to the client 2 using wireless communication. For that the token is sent via a protocol adapter 1 a , 1 b , 1 c , 1 d , 1 e , 1 f or 1 g at the proxy side, and received by the protocol adapter 2 a , 2 a ′, 2 a ′′ at the client side.
  • a JMS message is created by the client. Then, the JMS message is processed by the client. For example, the message can be visualized in a graphical user interface.
  • the JMS message oriented middleware 3 can be any JMS messaging middleware product, for example, IBM's MQSeries, SoftWired's iBus, or Progress' SonicMQ.
  • the JMS message oriented middleware client 4 is a client application implemented on a non-mobile computer, i.e. on a computer connected to a wired computer network, using a state of the art JMS message oriented middleware 3 .
  • One or more JMS message oriented middleware clients 4 according to the state of the art can be present.
  • the thin JMS message client 2 is subscribed to a topic T.
  • a topic T can, depending on the application, denote a stream of stock quotes, of sports news, or denote a transmission channel carrying digital audio.
  • a state of the art JMS message oriented middleware client 4 sends a JMS message to topic T, the message is passed first to the state of, the art JMS message oriented middleware 3 . The message will then be received by the proxy 1 on behalf of thin client 2 .
  • proxy 1 transmits the JMS message to client 2 in the form of a message token using one of its transport protocol adapters 1 a , 1 b , 1 c , 1 d , 1 e , 1 f or 1 g .
  • client 2 receives the JMS message on topic T as if it was accessing the state of the art JMS message oriented middleware 3 directly.
  • the sequence diagram of FIG. 2 shows the interactions—represented by arrows—occurring between a mobile client and a proxy during one information exchange, namely during the creation of a JMS TopicPublisher for a topic T by the mobile client and a subsequent publishing of a message published on Topic T.
  • the mobile client is symbolized by a shaded and dashed box.
  • the vertical line on the right hand side of the figure represents the message proxy.
  • the method steps are denoted by numbers which are not to be confused with the reference numerals of FIG. 1 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Sub-Exchange Stations And Push- Button Telephones (AREA)
  • Reduction Or Emphasis Of Bandwidth Of Signals (AREA)
  • Facsimile Transmission Control (AREA)

Abstract

A messaging proxy system is disclosed for the purpose of delivering data in the form of a portable message format from a producer running on a mobile or non-mobile computer, over any wireless network, by passing this data through an intermediary proxy computer program, to one or more recipients running on mobile or non-mobile computers. The system includes a message proxy computer program with at least one pluggable transport protocol adapter. The proxy contains a command subsystem for sending and receiving command- and message-tokens to and from the mobile clients. The system further includes a thin messaging middleware client to run on mobile devices. The thin messaging middleware client includes at least one pluggable protocol adapter. The client also comprises a command subsystem for sending and receiving command- and message-tokens to and from the proxy. The proxy also contains a communication subsystem for sending and receiving messages via a state of the art message oriented middleware.

Description

    FIELD OF THE INVENTION
  • The invention relates to techniques for the delivery of electronic messages between hardware or software components across wireless and wireline networks, between mobile and non-mobile devices.
    • BACKGROUND OF THE INVENTION
  • Message oriented middleware (MOM) has been available for many years. In October 1998, an industry standard emerged from Sun Microsystems, the Java Message Service (JMS). At a programming interface level, this standard describes how a messaging middleware is accessed from a Java application. The two main abstractions of JMS are “topics” (publish/subscribe messaging) and “queues” (point-to-point messaging). While the standard describes the interface to the messaging middleware, the implementation of the middleware is not specified. Also, integration of wireless mobile devices (such as phones, pagers, personal digital assistants or laptops) is not specified.
  • Existing messaging middleware allows one to access the middleware from non-mobile devices (personal computers or server computers) over wireline networks (Ethernet or Token Ring). These networks usually run communication protocols such as TCP/IP, HTTP or SSL. Supporting wireless mobile devices requires the vendor of the middleware to implement a message transmission protocol atop a wireless transport protocol (such as WAP, GSM, SMS, GPRS, or UMTS) and to integrate this message transmission protocol into the middleware.
  • This leads to limited applicability for the following reasons:
      • State of the art JMS messaging middleware requires more computer memory than is available on mobile devices.
      • Mobile devices, which are often disconnected from a corporate network, are unsupported in state of the art JMS messaging middleware products.
      • Wireless protocols such as WAP, SMS, GPRS or UMTS are not supported by state of the art JMS messaging middleware products, unless the TCP/IP, HTTP or SSL protocol is used atop those wireless protocols.
      • Though state of the art JMS messaging middleware products support communication protocols such as TCP/IP, HTTP, and SSL, they do not support any other communication protocols.
  • Further, there are considerable performance impacts, as TCP, HTTP or SSL were designed for wireline networks and thus do not perform well on wireless networks.
    • SUMMARY OF THE INVENTION
  • A first object of the invention is therefore to provide a system for the delivery of data between applications serving as clients and running on mobile wireless devices and applications running on computers of a wired network. Another object of the invention is to provide a method for delivering data between an application serving as client and running on a mobile wireless device and an application running on a computer of a wired network. Yet another object of the invention is to provide a computer program loadable into the memory of a computer usable for delivering messages between clients on mobile wireless devices and applications running on computers. A further object of the invention is to provide a computer program product comprising a computer usable medium having thereon computer readable program code means for implementing on a computer connected to a wired computer network. Still another object of the invention is to provide a computer program directly loadable into the memory of a mobile device and allowing the mobile device to access a messaging middleware product according to the state of the art, without needing to load that messaging middleware into the memory of the mobile device entirely.
  • The messaging proxy system outlined in this disclosure is a major technological advancement enabling users of state of the art messaging middleware products to send and receive messages to and from mobile devices, over any wireless transport protocol, without requiring that the state of the art messaging middleware be loaded into the memory of the mobile devices.
  • The system for running said message proxy installation includes a message proxy implemented by a computer program with a system architecture comprising at least one pluggable protocol adapter. In a preferred embodiment of the invention, the proxy further comprises at least one pluggable database adapter.
  • The invention also comprises a thin message client computer program directly loadable into the memory of a mobile device. This thin message client program allows a mobile device to exchange message and command tokens with a message oriented middleware according to the state of the art, by using the proxy computer program as an intermediary between the thin client and the message oriented middleware and thereby using at least one wireless transport protocol. The thin message client computer program embodies a system architecture of at least one pluggable protocol adapter. Preferably, it also embodies a system architecture of at least one pluggable database adapter.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • In the following, an example of an embodiment of the invention is described with reference to drawings. In the drawings:
  • FIG. 1 provides a block diagram of a preferred embodiment of the system according to the present invention, and
  • FIG. 2 shows a UML sequence diagram of an embodiment of the method according to the present invention.
    • DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Now with reference to the drawing, FIG. 1 provides a block diagram of a preferred embodiment of the present invention. It more particularly shows an installation of software tools loaded on non-mobile computers and mobile wireless devices, the installation comprising:
      • A message proxy 1,
      • Thin JMS message clients 2, 2′, 2″ linked to the proxy 1 with a wireless communication protocol,
      • JMS message oriented middleware 3 according to the state of the art, and
      • A JMS message oriented middleware client 4.
  • The block diagram is but one example of a message proxy infrastructure deployment. Any number of message proxies, thin JMS message clients, message oriented middleware products, and message oriented middleware product clients can be present in a specific installation.
  • The message proxy 1 may be implemented on a conventional computer network server, e.g on a Windows-NT-server and may e.g. run in the background. It maintains client connections, maintains client subscriptions to JMS topics and queues, receives and forwards JMS messages, and stores JMS messages in its database, such that they will not be lost when a client is disconnected from the proxy.
  • The message proxy 1 comprises at least one pluggable transport protocol adapter. FIG. 1 shows an example of six specific wireless transport protocol adapters (WAP 1 a, UMTS 1 b, HTTP 1 c, DAB/GSM Data 1 d, SMS 1 e, GPRS 1 f). Any number of additional wireless protocol adapters 1 g can be present. Pluggable protocol adapters allow the message proxy to send and receive messages to and from message clients using arbitrary wireless protocols. A protocol adapter embodies an existing transport protocol, such as GPRS or TCP/IP, and also provides additional features on top of the existing transport protocol. Examples of such additional features include data encryption and guaranteed delivery of messages. A protocol adapter is divided into one or more protocol objects. Each protocol object provides one part of the functionality offered by the protocol adapter. For example, a protocol object can encrypt data, or compress data, or request the sender of the data to retransmit a message which was lost on the network.
  • The message proxy 1 also comprises a database adapter. This allows the proxy to store messages and client subscription information into arbitrary databases.
  • On startup, the message proxy 1 reads its configuration data and initializes all configured protocol adapters. It also initializes the topic and queue subscriptions of all the message clients which are known to the proxy. At runtime, additional protocol adapters can be started, or running protocol adapters can be stopped, without interrupting the message proxy service (however, if a specific protocol adapter is stopped, service over this adapter is no longer available). At runtime, additional clients can be connected to the proxy, or existing clients can be disconnected from the proxy.
  • Each thin JMS message client 2, 2′, 2″ is installed on a mobile wireless device such as a mobilephone, a small laptop computer with a wireless modem, a palmtop device or any other device comprising a processor, a memory and communication means for communicating wirelessly. It contains a JMS programming library which is identical or similar to at least a part of the programming library used by messaging middle 3 of the state of the art. The thin JMS message client library is small enough to be loaded into the memory of the mobile devices which have constrained memory and processing power.
  • Such a small footprint of the thin JMS message client library is achieved by offloading from the client to the proxy most of the computations and most of the state information which a JMS client application ought to perform or to maintain. The thin JMS message client mainly consists of the JMS interface. Most of the Java code necessary for implementing the interface is running on the proxy, and not on the thin JMS message client. The proxy also maintains the JMS state information associated with the client. For example, the proxy stores the JMS messages which have not been acknowledged by the client yet. Also, the thin JMS message client does not need to store the names of the queues and topics it is subscribed to. This information is stored only by the proxy. Internally, the thin JMS client uses code information, such as number values, to refer to topics and queues. This code information can be as small as one byte. The actual representation of those queues and topics, which can be hundreds or thousands of bytes for each topic or queue, is contained in the proxy. When the thin JMS client wishes to publish a message on a certain topic, the client sends to the proxy only the JMS message and the code information related with the topic. All this considerably reduces the footprint of the thin JMS client.
  • The thin JMS message client 2 also contains a command and message transmission system comprising a transport protocol adapter 2 a, 2 a′, 2 a″ used for informing the proxy of what JMS topics and queues the client wants to subscribe to.
  • The message client 2, 2′, 2″ also comprises a database adapter. This allows the client to store JMS messages and other information locally, using arbitrary databases. The message database is necessary to ensure that JMS messages and JMS subscriptions submitted by the client are not lost in case the client cannot communicate with the proxy due to lack of wireless network coverage, or because the proxy is not running.
  • A message client 2, 2′, 2″ links to the message proxy 1, using its transport protocol adapter 2 a, 2 a′, 2 a″. If a matching protocol adapter is running on the proxy, the connection is successful. Further communication between message client and message proxy is according to the familiar publish/subscribe or point-to-point model of JMS.
  • JMS topics or JMS queues are named and administered independently of the protocol adapters involved. If a client connects to the proxy using the “WAP” protocol adapter, it can communicate with a client that connected using the “GPRS” protocol adapter, if both clients use the same JMS topic or queue.
  • The protocol adapters encapsulate at least one logic needed to:
      • Interface with a transport protocol, such as HTTP, WAP or GSM Data.
      • Specify and guarantee a quality of service for the message delivery.
  • Certain transport protocols operate in a “best effort” delivery mode. Thus, simply adapting to a specific protocol is not always enough (unless “best effort” is the desired message delivery guarantee). Thus, protocol adapters consist of both the transport protocol mechanism, and a quality of service mechanism to improve the basic network delivery guarantee.
  • Network reliability is improved as follows. The sending protocol adapter attaches a reliability indicator such as a sequence number to all outgoing messages. The reliability indicator is varied in a predefined manner upon sending a message. E.g., the sequence number is incremented by one after each sent message. The receiver application uses the reliability indicator of the incoming message to detect whether a message was lost. In the described example, this is the case when the sequence number of the just received message is greater than the sequence number of the previous message, plus one. In the event of message loss, the receiver sends a command token to the sender indicating which messages are to be retransmitted. The sender then retransmits the requested messages. The sender keeps messages in a local database to be able to fulfill a message retransmission request.
  • The database adapters encapsulate at least one logic needed to:
      • Interface with a database product, such as PointBase, Oracle, DB/2, or Sybase, OR to interface with a portable database access software such as JDBC or ODBC.
      • Store and retrieve JMS messages and JMS subscription requests.
  • The message client 2 implements e.g. the JMS API from Sun Microsystems. It cooperates with the proxy to achieve full JMS functionality. When the client wants to subscribe to a JMS queue or topic, its command subsystem creates a command token containing the subscription information. The command token is then sent to the proxy using wireless communication. To this end, the token is sent via a protocol adapter 2 a, 2 a′, 2 a″ at the client side and received by a protocol adapter 1 a, 1 b, 1 c, 1 d, 1 e, 1 f or 1 g at the proxy side.
  • On receipt of a command token, the proxy 1 reads the subscription information contained in the token, and performs a JMS subscription with the state of the art middleware, on behalf of the client.
  • Further command tokens are generated when the client wants to unsubscribe from a JMS topic or queue, when the client wants to transmit a JMS message, or for any other JMS action which is requested by the client.
  • When a JMS message is received on a topic or queue the proxy 1 is subscribed to on behalf of the client, the proxy creates a message token containing the data of the JMS message. The message token is then sent to the client 2 using wireless communication. For that the token is sent via a protocol adapter 1 a, 1 b, 1 c, 1 d, 1 e, 1 f or 1 g at the proxy side, and received by the protocol adapter 2 a, 2 a′, 2 a″ at the client side.
  • On receipt of such a message token by a thin JMS message client 2, a JMS message is created by the client. Then, the JMS message is processed by the client. For example, the message can be visualized in a graphical user interface.
  • The JMS message oriented middleware 3 according to the state of the art can be any JMS messaging middleware product, for example, IBM's MQSeries, SoftWired's iBus, or Progress' SonicMQ.
  • The JMS message oriented middleware client 4 is a client application implemented on a non-mobile computer, i.e. on a computer connected to a wired computer network, using a state of the art JMS message oriented middleware 3. One or more JMS message oriented middleware clients 4 according to the state of the art can be present.
  • For the describing an example of the communication between different examples, it is assumed that the thin JMS message client 2 is subscribed to a topic T. Such a topic T can, depending on the application, denote a stream of stock quotes, of sports news, or denote a transmission channel carrying digital audio. When a state of the art JMS message oriented middleware client 4 sends a JMS message to topic T, the message is passed first to the state of, the art JMS message oriented middleware 3. The message will then be received by the proxy 1 on behalf of thin client 2. Next, proxy 1 transmits the JMS message to client 2 in the form of a message token using one of its transport protocol adapters 1 a, 1 b, 1 c, 1 d, 1 e, 1 f or 1 g. Finally, client 2 receives the JMS message on topic T as if it was accessing the state of the art JMS message oriented middleware 3 directly.
  • In order to show this procedure in more detail, in the following an example of the method for delivering information between applications running on mobile wireless devices and serving as clients and applications running on non-mobile computers is described with reference to FIG. 2.
  • The sequence diagram of FIG. 2 shows the interactions—represented by arrows—occurring between a mobile client and a proxy during one information exchange, namely during the creation of a JMS TopicPublisher for a topic T by the mobile client and a subsequent publishing of a message published on Topic T. In the diagram, the mobile client is symbolized by a shaded and dashed box. The vertical line on the right hand side of the figure represents the message proxy. The method steps are denoted by numbers which are not to be confused with the reference numerals of FIG. 1.
    • 1. A JMS TopicPublisher object “Pub” is created, upon request of the application, for JMS publish/subscribe topic “T”. Later, “Pub” will allow the mobile client application to publish a JMS message on topic “T”.
    • 2. The Thin Message Client Library creates a command token containing the information which is needed by the proxy for allocating a JMS TopicPublisher, on behalf of the client. The command token contains a code information (e.g. a one-byte number) denoting a ‘Create a publisher’ command. It also contains the JMS topic “T” the publisher shall be tied to (e.g. a one-byte number), as well as an information Code “P” (e.g. a one-byte number) denoting the publisher.
    • 3. The proxy creates a JMS TopicPublisher “Pub” for topic “T” on behalf of the thin client.
    • 4. The proxy associates TopicPublisher “Pub” with the code information “P”. This can be done by storing the TopicPublisher “Pub” into a data dictionary, using code information “P” as the search key.
    • 5. The client application creates a JMS message “msg” containing application specific information, e.g., a book order. This step, of course, as well as the subsequent step 6, can be carried out following to or simultaneously to steps 3 and 4.
    • 6. The client application now publishes JMS message “msg” on topic “T”, using TopicPublisher “Pub”.
    • 7. The Thin Message Client Library creates a command token containing the information which is needed by the proxy for publishing the message using state-of-the-art JMS middleware. The command token contains a code information (e.g. a one-byte number) denoting a ‘Do publish’ command. It also contains the code information for the TopicPublisher (Code “P”) as well as the message “msg”.
    • 8. The proxy retrieves the TopicPublisher “Pub”, which is associated with Code “P”. This publisher “pub” was associated with Code “T” in Step 4.
    • 9. Finally, the proxy publishes the JMS message “msg” on topic “T” using a state of the art JMS middleware. Concretely, the proxy forwards the message “msg” on topic “T” to a state of the art JMS application using JMS.
    GLOSSARY OF TERMS USED
    • TCP: Transmission Control Protocol
    • IP: Internet Protocol
    • HTTP: Hypertext Transfer Protocol
    • WAP: Wireless Application Protocol
    • WDP: WAP Wireless Datagram Protocol
    • SSL: Secure Socket Layer
    • JMS: Java Message Service (http://java.sun.com/products/jms/)
    • PDA: Personal Digital Assistant
    • SMS: Short Messaging Service
    • GSM: Global System for Mobile Telecommunication
    • DAB: Digital Audio Broadcast
    • JDBC: Java Database Connectivity (http://java.sun.com/products/jdbc/)
    • ODBC: Microsoft's Open Database Connectivity
    • MOM: Message Oriented Middleware

Claims (14)

1. A system for delivering information between applications running on mobile wireless devices and serving as clients and applications running on computers, said computers being connected to a wired computer network, the system comprising
a proxy implemented on a computer connected to the computer network, and wireless communication means for establishing a communication channel between the proxy and the clients,
the clients each comprising a programming library corresponding to at least a fraction of a programming library used by a message oriented middleware (MOM) and a transport protocol adapter with a logic to interface with a transport protocol, thus defining at least one communication transport protocol for a communication on said communication channel,
the proxy comprising at least one transport protocol adapter with a logic to interface with said communication transport protocol.
2. The system of claim 1, whereby the proxy comprises at least one of a wireless transport protocol adapter implemented before start-up of the message proxy and of a wireless transport protocol adapter implemented by a program code at run-time of the message proxy.
3. The system of claim 1, whereby said at least one transport protocol adapter supports HTTP or SMS or WAP or WDP or GPRS or UMTS.
4. The system of claim 1, whereby a local database is provided on at least one of the clients and on the proxy, allowing the client and the proxy to store information in case of disconnection.
5. The system of claim 4, whereby at least one pluggable database adapter is provided allowing the client and the proxy to use any database product.
6. The system of claim 1, whereby the clients are implemented in the JAVA programming language.
7. The system according of claim 1, whereby the clients are implemented according to the JMS specification.
8. The system of claim 1, whereby the clients support the JMS publish/subscribe messaging model.
9. The system of claim 1, whereby said clients support the JMS point-to-point messaging model.
10. A method of delivering information between a first application running on a mobile wireless device and serving as client and a second application running on a computer, the computer being connected to a wired computer network, comprising the steps of,
providing a programming library corresponding to at least a fraction of a programming library used by a message oriented middleware (MOM) and a transport protocol adapter with a logic to interface with a transport protocol,
creating, on the wireless device, code information representing at least one of a topic and of queue contained in a MOM programming library,
transmitting the code information to a proxy implemented on a computer connected to the computer network
simultaneously or subsequently, transmitting message data specific to the first application to the proxy and
creating, by the proxy, at least one MOM command referred to by the code information
forwarding the message data to the second application using the MOM command referred to by the code information.
11. A computer program for being run on a computer connected to a wired computer network, comprising program code means for implementing
at least one transport protocol adapter with a logic to interface with a transport protocol,
means for receiving at least one of MOM command tokens and of MOM message tokens from an application running on a mobile wireless device serving as client, via said transport protocol adapter and using said transport protocol,
means for sending MOM message tokens to a client via said transport protocol adapter and using said transport protocol, and
means for exchanging MOM message tokens with a MOM client implemented on a computer of said wired computer network.
12. The computer program of claim 11 comprising software code for implementing means for receiving and sending JMS MOM tokens.
13. A computer program product comprising a computer usable medium having thereon computer readable program code means for implementing on a computer connected to a wired computer network
at least one transport protocol adapter with a logic to interface with a transport protocol,
means for receiving at least one of MOM command tokens and of MOM message tokens from an application running on a mobile wireless device serving as client, via said transport protocol adapter and using said transport protocol,
means for sending MOM message tokens to a client via said transport protocol adapter and using said transport protocol, and
means for exchanging MOM message tokens with a MOM client implemented on a computer of said wired computer network
14. A computer program for being run on a mobile wireless device comprising program code means for implementing a programming library corresponding to at least a fraction of a programming library used by a MOM and a transport protocol adapter with a logic to interface with a transport protocol.
US10/824,200 2000-07-07 2004-04-13 Messaging proxy system Abandoned US20050114517A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US10/824,200 US20050114517A1 (en) 2000-07-07 2004-04-13 Messaging proxy system
US12/371,924 US20090157836A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US12/371,921 US8650244B2 (en) 2000-07-07 2009-02-17 Messaging proxy system
US12/371,917 US20090157883A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US14/153,958 US9906487B2 (en) 2000-07-07 2014-01-13 Messaging proxy system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/611,629 US6721779B1 (en) 2000-07-07 2000-07-07 Messaging proxy system
US10/824,200 US20050114517A1 (en) 2000-07-07 2004-04-13 Messaging proxy system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/611,629 Continuation US6721779B1 (en) 2000-07-07 2000-07-07 Messaging proxy system

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US12/371,917 Division US20090157883A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US12/371,924 Division US20090157836A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US12/371,921 Division US8650244B2 (en) 2000-07-07 2009-02-17 Messaging proxy system

Publications (1)

Publication Number Publication Date
US20050114517A1 true US20050114517A1 (en) 2005-05-26

Family

ID=24449789

Family Applications (6)

Application Number Title Priority Date Filing Date
US09/611,629 Expired - Lifetime US6721779B1 (en) 2000-07-07 2000-07-07 Messaging proxy system
US10/824,200 Abandoned US20050114517A1 (en) 2000-07-07 2004-04-13 Messaging proxy system
US12/371,921 Expired - Lifetime US8650244B2 (en) 2000-07-07 2009-02-17 Messaging proxy system
US12/371,917 Abandoned US20090157883A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US12/371,924 Abandoned US20090157836A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US14/153,958 Expired - Lifetime US9906487B2 (en) 2000-07-07 2014-01-13 Messaging proxy system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/611,629 Expired - Lifetime US6721779B1 (en) 2000-07-07 2000-07-07 Messaging proxy system

Family Applications After (4)

Application Number Title Priority Date Filing Date
US12/371,921 Expired - Lifetime US8650244B2 (en) 2000-07-07 2009-02-17 Messaging proxy system
US12/371,917 Abandoned US20090157883A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US12/371,924 Abandoned US20090157836A1 (en) 2000-07-07 2009-02-17 Messaging Proxy System
US14/153,958 Expired - Lifetime US9906487B2 (en) 2000-07-07 2014-01-13 Messaging proxy system

Country Status (8)

Country Link
US (6) US6721779B1 (en)
EP (1) EP1299980B1 (en)
KR (1) KR100810170B1 (en)
CN (2) CN1671144A (en)
AT (1) ATE433244T1 (en)
AU (1) AU2001263715A1 (en)
DE (1) DE60138887D1 (en)
WO (1) WO2002005507A2 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040127250A1 (en) * 2002-09-23 2004-07-01 Bjorn Bjare Middleware application message/event model
US20050240654A1 (en) * 2004-04-21 2005-10-27 Andreas Wolber Message-oriented middleware provider having multiple server instances integrated into a clustered application server infrastructure
US20060176271A1 (en) * 2005-02-07 2006-08-10 Microsoft Corporation Interface for consistent program interaction with auxiliary computing devices
US20080274766A1 (en) * 2007-04-13 2008-11-06 Hart Communication Foundation Combined Wired and Wireless Communications with Field Devices in a Process Control Environment
US20080273486A1 (en) * 2007-04-13 2008-11-06 Hart Communication Foundation Wireless Protocol Adapter
US20090010203A1 (en) * 2007-04-13 2009-01-08 Hart Communication Foundation Efficient Addressing in Wireless Hart Protocol
US20090046675A1 (en) * 2007-04-13 2009-02-19 Hart Communication Foundation Scheduling Communication Frames in a Wireless Network
US20100110916A1 (en) * 2008-06-23 2010-05-06 Hart Communication Foundation Wireless Communication Network Analyzer
US20110029656A1 (en) * 2004-09-13 2011-02-03 The Boeing Company Systems and methods enabling interoperability between network-centric operation (nco) environments
US20110216656A1 (en) * 2007-04-13 2011-09-08 Hart Communication Foundation Routing Packets on a Network Using Directed Graphs
US8325627B2 (en) 2007-04-13 2012-12-04 Hart Communication Foundation Adaptive scheduling in a wireless network
US11201919B2 (en) * 2014-05-27 2021-12-14 Commvault Systems, Inc. Offline messaging between a repository storage operation cell and remote storage operation cells via an intermediary media agent
US11336740B2 (en) * 2020-04-16 2022-05-17 Deutsche Telekom Ag Proxy-based messaging system of a telecommunication network

Families Citing this family (111)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8090856B1 (en) 2000-01-31 2012-01-03 Telecommunication Systems, Inc. Intelligent messaging network server interconnection
US7689696B2 (en) * 2000-01-31 2010-03-30 Telecommunication Systems, Inc. System and method for re-directing requests from browsers for communications over non-IP based networks
US7003571B1 (en) * 2000-01-31 2006-02-21 Telecommunication Systems Corporation Of Maryland System and method for re-directing requests from browsers for communication over non-IP based networks
EP1257957A4 (en) * 2000-02-16 2003-05-21 Bea Systems Inc Workflow integration system for enterprise wide electronic collaboration
WO2001077912A2 (en) * 2000-03-31 2001-10-18 Mdsi Mobile Data Solutions Inc. Configurable scheduling system
US7522911B2 (en) * 2000-04-11 2009-04-21 Telecommunication Systems, Inc. Wireless chat automatic status tracking
US20010049702A1 (en) * 2000-06-05 2001-12-06 Sun Microsystems, Inc. Service side filtering XML messages in a distributed network
US6721779B1 (en) * 2000-07-07 2004-04-13 Softwired Ag Messaging proxy system
US7483983B1 (en) * 2000-11-13 2009-01-27 Telecommunication Systems, Inc. Method and system for deploying content to wireless devices
US7127517B2 (en) * 2000-12-27 2006-10-24 International Business Machines Corporation Protocol adapter framework for integrating non-IIOP applications into an object server container
US20030041175A2 (en) * 2001-05-03 2003-02-27 Singhal Sandeep K Method and System for Adapting Short-Range Wireless Access Points for Participation in a Coordinated Networked Environment
US7536697B2 (en) 2001-06-19 2009-05-19 Accenture Global Services Gmbh Integrating enterprise support systems
US7216181B1 (en) * 2001-07-31 2007-05-08 Sprint Communications Company L.P. Middleware brokering system
US7152094B1 (en) * 2001-07-31 2006-12-19 Sprint Communications Company L.P. Middleware brokering system adapter
US8086665B1 (en) 2001-08-21 2011-12-27 Rockstar Bidco, LP Technique for enabling a plurality of software components to communicate in a software component matrix environment
US7454459B1 (en) * 2001-09-04 2008-11-18 Jarna, Inc. Method and apparatus for implementing a real-time event management platform
US7552222B2 (en) 2001-10-18 2009-06-23 Bea Systems, Inc. Single system user identity
US7546462B2 (en) * 2001-10-18 2009-06-09 Bea Systems, Inc. Systems and methods for integration adapter security
US20030115366A1 (en) * 2001-12-18 2003-06-19 Robinson Brian R. Asynchronous message delivery system and method
US7308482B2 (en) * 2002-02-12 2007-12-11 At&T Bls Intellectual Property, Inc. Methods and systems for communicating with service technicians in a telecommunications system
US7516447B2 (en) 2002-02-22 2009-04-07 Bea Systems, Inc. Methods and apparatus for building, customizing and using software abstractions of external entities
US7424717B2 (en) 2002-05-01 2008-09-09 Bea Systems, Inc. Systems and methods for business process plug-in development
US7257645B2 (en) * 2002-05-01 2007-08-14 Bea Systems, Inc. System and method for storing large messages
US7155438B2 (en) 2002-05-01 2006-12-26 Bea Systems, Inc. High availability for event forwarding
US8135772B2 (en) 2002-05-01 2012-03-13 Oracle International Corporation Single servlets for B2B message routing
US7222148B2 (en) 2002-05-02 2007-05-22 Bea Systems, Inc. System and method for providing highly available processing of asynchronous service requests
US7484224B2 (en) 2002-05-02 2009-01-27 Bae Systems, Inc. Adapter deployment without recycle
US7627631B2 (en) * 2002-05-02 2009-12-01 Bea Systems, Inc. Systems and methods for collaborative business plug-ins
US7350184B2 (en) * 2002-05-02 2008-03-25 Bea Systems, Inc. System and method for enterprise application interactions
US20030208539A1 (en) * 2002-05-02 2003-11-06 Gildenblat Ilya G. Event-driven information publication
US7676538B2 (en) 2002-05-02 2010-03-09 Bea Systems, Inc. Systems and methods for application view transactions
US7493628B2 (en) 2002-05-02 2009-02-17 Bea Systems, Inc. Shared common connection factory
US8166311B1 (en) * 2002-06-20 2012-04-24 At&T Intellectual Property I, Lp Methods and systems for promoting authentication of technical service communications in a telecommunications system
US6988099B2 (en) * 2002-06-27 2006-01-17 Bea Systems, Inc. Systems and methods for maintaining transactional persistence
JP4373060B2 (en) * 2002-08-14 2009-11-25 株式会社エヌ・ティ・ティ・ドコモ Distributed processing system and proxy node, user side node and method in distributed processing system
US8606859B2 (en) * 2002-10-17 2013-12-10 Tibco Software Inc. Method and system to communicate messages in a computer network
US7650591B2 (en) 2003-01-24 2010-01-19 Bea Systems, Inc. Marshaling and un-marshaling data types in XML and Java
US7752599B2 (en) 2003-02-25 2010-07-06 Bea Systems Inc. Systems and methods extending an existing programming language with constructs
US7774697B2 (en) 2003-02-25 2010-08-10 Bea Systems, Inc. System and method for structuring distributed applications
US7584474B2 (en) 2003-02-25 2009-09-01 Bea Systems, Inc. Systems and methods for transaction chaining
US7293038B2 (en) 2003-02-25 2007-11-06 Bea Systems, Inc. Systems and methods for client-side filtering of subscribed messages
US7539985B2 (en) * 2003-02-26 2009-05-26 Bea Systems, Inc. Systems and methods for dynamic component versioning
US7076772B2 (en) * 2003-02-26 2006-07-11 Bea Systems, Inc. System and method for multi-language extensible compiler framework
US7650276B2 (en) 2003-02-26 2010-01-19 Bea Systems, Inc. System and method for dynamic data binding in distributed applications
US20040230955A1 (en) * 2003-02-26 2004-11-18 Bea Systems, Inc. System for multi-language debugging
US7707564B2 (en) 2003-02-26 2010-04-27 Bea Systems, Inc. Systems and methods for creating network-based software services using source code annotations
US7299454B2 (en) * 2003-02-26 2007-11-20 Bea Systems, Inc. Method for multi-language debugging
US20050108682A1 (en) * 2003-02-26 2005-05-19 Bea Systems, Inc. Systems for type-independent source code editing
US8032860B2 (en) * 2003-02-26 2011-10-04 Oracle International Corporation Methods for type-independent source code editing
US7636722B2 (en) 2003-02-28 2009-12-22 Bea Systems, Inc. System and method for describing application extensions in XML
US7444620B2 (en) 2003-02-28 2008-10-28 Bea Systems, Inc. Systems and methods for a common runtime container framework
US7650592B2 (en) 2003-03-01 2010-01-19 Bea Systems, Inc. Systems and methods for multi-view debugging environment
GB0305066D0 (en) 2003-03-06 2003-04-09 Ibm System and method for publish/subscribe messaging
US7418711B1 (en) * 2003-04-28 2008-08-26 Sprint Communications Company L.P. Messaging bridge that facilitates communication with a mainframe environment
NO20032418D0 (en) * 2003-05-27 2003-05-27 Ericsson Telefon Ab L M Aggregation of non-blocking, durable state machines on an "EnterpriseJava Bean" platform
NO20032419D0 (en) * 2003-05-27 2003-05-27 Ericsson Telefon Ab L M Non-blocking, durable state machines in an "Enterprise Java Bean" platform
CN100403744C (en) * 2003-09-08 2008-07-16 华为技术有限公司 System and method for communication between media gateway controller and media gateway
US7707592B2 (en) * 2003-10-10 2010-04-27 Telefonaktiebolaget L M Ericsson (Publ) Mobile terminal application subsystem and access subsystem architecture method and system
DE102004017247A1 (en) * 2004-04-05 2005-10-27 Vionti Gmbh Method for sending, relaying, receiving messages e.g. SMS, requires message to be sent in transmission step via RF path to network gateway
US20050264581A1 (en) * 2004-05-21 2005-12-01 Bea Systems, Inc. Dynamic program modification
US20050278335A1 (en) * 2004-05-21 2005-12-15 Bea Systems, Inc. Service oriented architecture with alerts
US20050273517A1 (en) * 2004-05-21 2005-12-08 Bea Systems, Inc. Service oriented architecture with credential management
US20050267892A1 (en) * 2004-05-21 2005-12-01 Patrick Paul B Service proxy definition
US20050273847A1 (en) * 2004-05-21 2005-12-08 Bea Systems, Inc. Programmable message processing stage for a service oriented architecture
US20060031354A1 (en) * 2004-05-21 2006-02-09 Bea Systems, Inc. Service oriented architecture
US20060031432A1 (en) * 2004-05-21 2006-02-09 Bea Systens, Inc. Service oriented architecture with message processing pipelines
US20060031930A1 (en) * 2004-05-21 2006-02-09 Bea Systems, Inc. Dynamically configurable service oriented architecture
US20060069791A1 (en) * 2004-05-21 2006-03-30 Bea Systems, Inc. Service oriented architecture with interchangeable transport protocols
US20050273521A1 (en) * 2004-05-21 2005-12-08 Bea Systems, Inc. Dynamically configurable service oriented architecture
US20060031433A1 (en) * 2004-05-21 2006-02-09 Bea Systems, Inc. Batch updating for a service oriented architecture
US20050270970A1 (en) * 2004-05-21 2005-12-08 Bea Systems, Inc. Failsafe service oriented architecture
US20050273516A1 (en) * 2004-05-21 2005-12-08 Bea Systems, Inc. Dynamic routing in a service oriented architecture
US7310684B2 (en) * 2004-05-21 2007-12-18 Bea Systems, Inc. Message processing in a service oriented architecture
US20050278374A1 (en) * 2004-05-21 2005-12-15 Bea Systems, Inc. Dynamic program modification
US20060031353A1 (en) * 2004-05-21 2006-02-09 Bea Systems, Inc. Dynamic publishing in a service oriented architecture
US20060136555A1 (en) * 2004-05-21 2006-06-22 Bea Systems, Inc. Secure service oriented architecture
US20050267947A1 (en) * 2004-05-21 2005-12-01 Bea Systems, Inc. Service oriented architecture with message processing pipelines
US20060007918A1 (en) * 2004-05-21 2006-01-12 Bea Systems, Inc. Scaleable service oriented architecture
US20060080220A1 (en) * 2004-08-13 2006-04-13 Kevin Samuel Liquidity book system and method
US20060136932A1 (en) * 2004-12-16 2006-06-22 Bose Anuradha A Monitoring messages in a distributed data processing system
US20060168626A1 (en) * 2005-01-21 2006-07-27 U-Turn Media Corporation Methods and systems for providing video content to a mobile client
US20060168578A1 (en) * 2005-01-21 2006-07-27 U-Turn Media Corporation Methods and systems for managing a mobile client in a client-server system connected via a public network
CA2493907A1 (en) * 2005-01-24 2006-07-24 Oz Communications Wireless e-mail system
WO2006089391A1 (en) * 2005-02-22 2006-08-31 Nextair Corporation Mobile device having extensible software for presenting server-side applications, software and methods
KR100818296B1 (en) * 2005-12-08 2008-03-31 한국전자통신연구원 System and method for managing postal devices using rfid
US7739391B2 (en) * 2006-02-16 2010-06-15 Softwired Ag Gateway for wireless mobile clients
US7512408B2 (en) * 2006-02-16 2009-03-31 Softwired Ag Scalable wireless messaging system
US8676876B2 (en) * 2006-06-27 2014-03-18 International Business Machines Corporation Synchronizing an active feed adapter and a backup feed adapter in a high speed, low latency data communications environment
US8296778B2 (en) * 2006-06-27 2012-10-23 International Business Machines Corporation Computer data communications in a high speed, low latency data communications environment
US8122144B2 (en) * 2006-06-27 2012-02-21 International Business Machines Corporation Reliable messaging using redundant message streams in a high speed, low latency data communications environment
US20080082690A1 (en) * 2006-09-29 2008-04-03 Dell Products L.P. System and method for the dynamic loading of protocol adapters
US8311046B2 (en) 2006-11-28 2012-11-13 Core Wireless Licensing S.A.R.L. Method for the delivery of messages in a communication system
US8996394B2 (en) * 2007-05-18 2015-03-31 Oracle International Corporation System and method for enabling decision activities in a process management and design environment
US8185916B2 (en) 2007-06-28 2012-05-22 Oracle International Corporation System and method for integrating a business process management system with an enterprise service bus
US8505038B2 (en) * 2008-01-28 2013-08-06 Blue Coat Systems, Inc. Method and system for enhancing MS exchange (MAPI) end user experiences in a split proxy environment
US9191623B2 (en) * 2008-12-15 2015-11-17 Adobe Systems Incorporated Transmitting datastreams to late joining broadcast subscribers
US10552239B2 (en) 2009-12-01 2020-02-04 International Business Machines Corporation Message recall
CN102170618A (en) * 2010-02-26 2011-08-31 国际商业机器公司 Short message processing method and equipment
US8620724B2 (en) 2010-04-20 2013-12-31 Accenture Global Services Limited Integration framework for enterprise content management systems
KR101219637B1 (en) 2012-02-08 2013-01-09 윤경숙 Message oriented middleware device for message communication processing using numeralized topic
US9348927B2 (en) 2012-05-07 2016-05-24 Smart Security Systems Llc Systems and methods for detecting, identifying and categorizing intermediate nodes
US9325676B2 (en) 2012-05-24 2016-04-26 Ip Ghoster, Inc. Systems and methods for protecting communications between nodes
US10778659B2 (en) 2012-05-24 2020-09-15 Smart Security Systems Llc System and method for protecting communications
WO2015116768A2 (en) 2014-01-29 2015-08-06 Sipn, Llc Systems and methods for protecting communications
CA2881417C (en) * 2012-08-09 2020-12-29 Charter Communications Operating, Llc System and method bridging cloud based user interfaces
EP2747349A1 (en) * 2012-12-20 2014-06-25 Thomson Licensing Home network and method of operation thereof
CN106254460A (en) * 2016-08-05 2016-12-21 浪潮软件股份有限公司 Method for accessing message middleware from mobile terminal
US10326720B2 (en) * 2017-05-05 2019-06-18 Dell Products L.P. Messaging queue service API optimization system
US11194930B2 (en) 2018-04-27 2021-12-07 Datatrendz, Llc Unobtrusive systems and methods for collecting, processing and securing information transmitted over a network
CN113132376B (en) * 2021-04-14 2022-11-22 腾讯科技（深圳）有限公司 Media data processing method, device and system, electronic equipment and storage medium
CN114979259B (en) * 2022-03-31 2024-11-01 全通金信控股(广东)有限公司 Message queue proxy device

Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5680551A (en) * 1993-10-21 1997-10-21 Sybase, Inc. Electronic messaging method of and system for heterogeneous connectivity and universal and generic interfacing for distributed applications and processes residing in wide variety of computing platforms and communication transport facilities
US5948066A (en) * 1997-03-13 1999-09-07 Motorola, Inc. System and method for delivery of information over narrow-band communications links
US5987256A (en) * 1997-09-03 1999-11-16 Enreach Technology, Inc. System and process for object rendering on thin client platforms
US6108696A (en) * 1997-11-14 2000-08-22 Online Anywhere Method and apparatus to connect a general purpose computer to a special purpose system
US6115741A (en) * 1996-03-14 2000-09-05 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US6119167A (en) * 1997-07-11 2000-09-12 Phone.Com, Inc. Pushing and pulling data in networks
US6122671A (en) * 1995-12-08 2000-09-19 Amsc Subsidiary Corporation Mobile communications from computer aided dispatch system via a customer premises gateway for satellite communication system
US6141686A (en) * 1998-03-13 2000-10-31 Deterministic Networks, Inc. Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control
US6167449A (en) * 1997-11-19 2000-12-26 Apple Computer, Inc. System and method for identifying and locating services on multiple heterogeneous networks using a query by type
US6253367B1 (en) * 1998-11-18 2001-06-26 Micrografx, Inc. Method and system for transforming dynamic content for use on the internet
US6256635B1 (en) * 1998-05-08 2001-07-03 Apple Computer, Inc. Method and apparatus for configuring a computer using scripting
US6256676B1 (en) * 1998-11-18 2001-07-03 Saga Software, Inc. Agent-adapter architecture for use in enterprise application integration systems
US20010014910A1 (en) * 1995-04-28 2001-08-16 Bobo Charles R. Systems and methods for storing, delivering, and managing messages
US6321338B1 (en) * 1998-11-09 2001-11-20 Sri International Network surveillance
US6324584B1 (en) * 1997-11-26 2001-11-27 International Business Machines Corp. Method for intelligent internet router and system
US6343287B1 (en) * 1999-05-19 2002-01-29 Sun Microsystems, Inc. External data store link for a profile service
US6347340B1 (en) * 2000-02-18 2002-02-12 Mobilesys, Inc. Apparatus and method for converting a network message to a wireless transport message using a modular architecture
US6351771B1 (en) * 1997-11-10 2002-02-26 Nortel Networks Limited Distributed service network system capable of transparently converting data formats and selectively connecting to an appropriate bridge in accordance with clients characteristics identified during preliminary connections
US20020049858A1 (en) * 2000-01-14 2002-04-25 Frietas Nathaniel X. Software architecture for wireless data and method of operation thereof
US6393014B1 (en) * 1997-06-03 2002-05-21 At&T Wireless Services, Inc. Method and system for providing data communication with a mobile station
US6424841B1 (en) * 1999-02-18 2002-07-23 Openwave Systems Inc. Short message service with improved utilization of available bandwidth
US20020120719A1 (en) * 2000-03-31 2002-08-29 King-Hwa Lee Web client-server system and method for incompatible page markup and presentation languages
US6453320B1 (en) * 1999-02-01 2002-09-17 Iona Technologies, Inc. Method and system for providing object references in a distributed object environment supporting object migration
US6466974B1 (en) * 1998-12-04 2002-10-15 Sun Microsystems, Inc. Environment for creating and managing network management software objects
US6473759B1 (en) * 1999-01-12 2002-10-29 International Business Machines Corporation Method and system for accessing java applications
US20020178126A1 (en) * 2001-05-25 2002-11-28 Beck Timothy L. Remote medical device access
US6513019B2 (en) * 1999-02-16 2003-01-28 Financial Technologies International, Inc. Financial consolidation and communication platform
US6522641B1 (en) * 1998-06-02 2003-02-18 Nortel Networks Limited Integrated data centric network (IDCN)
US6549773B1 (en) * 1998-09-21 2003-04-15 Nokia Mobile Phones Limited Method for utilizing local resources in a communication system
US6591272B1 (en) * 1999-02-25 2003-07-08 Tricoron Networks, Inc. Method and apparatus to make and transmit objects from a database on a server computer to a client computer
US6721779B1 (en) * 2000-07-07 2004-04-13 Softwired Ag Messaging proxy system
US6877023B1 (en) * 2000-01-28 2005-04-05 Softwired, Inc. Messaging system for delivering data in the form of portable message formats between message clients
US20050240621A1 (en) * 2000-05-22 2005-10-27 Mci, Inc. Method and system for managing partitioned data resources
US7155490B1 (en) * 2000-03-01 2006-12-26 Freewebs Corporation System and method for providing a web-based operating system
US7458082B1 (en) * 2000-05-09 2008-11-25 Sun Microsystems, Inc. Bridging between a data representation language message-based distributed computing environment and other computing environments using proxy service

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5329619A (en) * 1992-10-30 1994-07-12 Software Ag Cooperative processing interface and communication broker for heterogeneous computing environments
US5566225A (en) * 1994-11-21 1996-10-15 Lucent Technologies Inc. Wireless data communications system for detecting a disabled condition and simulating a functioning mode in response to detection
US5758257A (en) * 1994-11-29 1998-05-26 Herz; Frederick System and method for scheduling broadcast of and access to video programs and other data using customer profiles
DE19632258C1 (en) 1996-08-09 1997-12-11 Siemens Ag Message handling system for data communications system
US6044372A (en) * 1997-07-18 2000-03-28 Dazel Corporation Method and apparatus for publishing information to a communications network and enabling subscriptions to such information
US6222533B1 (en) 1997-08-25 2001-04-24 I2 Technologies, Inc. System and process having a universal adapter framework and providing a global user interface and global messaging bus
US6484196B1 (en) * 1998-03-20 2002-11-19 Advanced Web Solutions Internet messaging system and method for use in computer networks
US6324564B1 (en) * 1998-06-02 2001-11-27 Nettech Systems, Inc. Optimized wireless communication system
US6212548B1 (en) * 1998-07-30 2001-04-03 At & T Corp System and method for multiple asynchronous text chat conversations
US6473748B1 (en) * 1998-08-31 2002-10-29 Worldcom, Inc. System for implementing rules
US6748455B1 (en) * 1999-02-23 2004-06-08 Microsoft Corporation Object connectivity through loosely coupled publish and subscribe events with filtering
AU778101B2 (en) * 1999-06-14 2004-11-18 Integral Development Corporation System and method for conducting web-based financial transactions in capital markets
US6651086B1 (en) * 2000-02-22 2003-11-18 Yahoo! Inc. Systems and methods for matching participants to a conversation
US7302643B1 (en) * 2000-03-20 2007-11-27 International Business Machines Corporation System and method for scheduled events to subscribe to live information topics
US6928280B1 (en) * 2000-03-20 2005-08-09 Telephia, Inc. Method and system for measuring data quality of service in a wireless network using multiple remote units and a back end processor
US6950857B1 (en) * 2000-03-31 2005-09-27 Palmsource, Inc. Secure server-based indentification for simplified online transaction processing with palmtop computer
US20010049702A1 (en) * 2000-06-05 2001-12-06 Sun Microsystems, Inc. Service side filtering XML messages in a distributed network
US7210099B2 (en) * 2000-06-12 2007-04-24 Softview Llc Resolution independent vector display of internet content
US7587497B1 (en) * 2000-06-20 2009-09-08 Palmsource Inc. Information exchange between a handheld device and another computer system using an exchange manager and uniform resource locator (URL) strings
US6738808B1 (en) * 2000-06-30 2004-05-18 Bell South Intellectual Property Corporation Anonymous location service for wireless networks
US8041817B2 (en) * 2000-06-30 2011-10-18 At&T Intellectual Property I, Lp Anonymous location service for wireless networks
JP2002063719A (en) * 2000-08-18 2002-02-28 Fujitsu Ltd Magnetic recording medium, its manufacturing method and metallic mold
CA2361861A1 (en) * 2001-11-13 2003-05-13 Ibm Canada Limited-Ibm Canada Limitee Wireless messaging services using publish/subscribe systems
CA2391733A1 (en) * 2002-06-26 2003-12-26 Ibm Canada Limited-Ibm Canada Limitee Framework to access a remote system from an integrated development environment
US7739391B2 (en) * 2006-02-16 2010-06-15 Softwired Ag Gateway for wireless mobile clients

Patent Citations (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5680551A (en) * 1993-10-21 1997-10-21 Sybase, Inc. Electronic messaging method of and system for heterogeneous connectivity and universal and generic interfacing for distributed applications and processes residing in wide variety of computing platforms and communication transport facilities
US20010014910A1 (en) * 1995-04-28 2001-08-16 Bobo Charles R. Systems and methods for storing, delivering, and managing messages
US6122671A (en) * 1995-12-08 2000-09-19 Amsc Subsidiary Corporation Mobile communications from computer aided dispatch system via a customer premises gateway for satellite communication system
US6115741A (en) * 1996-03-14 2000-09-05 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US5948066A (en) * 1997-03-13 1999-09-07 Motorola, Inc. System and method for delivery of information over narrow-band communications links
US6393014B1 (en) * 1997-06-03 2002-05-21 At&T Wireless Services, Inc. Method and system for providing data communication with a mobile station
US6119167A (en) * 1997-07-11 2000-09-12 Phone.Com, Inc. Pushing and pulling data in networks
US5987256A (en) * 1997-09-03 1999-11-16 Enreach Technology, Inc. System and process for object rendering on thin client platforms
US6351771B1 (en) * 1997-11-10 2002-02-26 Nortel Networks Limited Distributed service network system capable of transparently converting data formats and selectively connecting to an appropriate bridge in accordance with clients characteristics identified during preliminary connections
US6108696A (en) * 1997-11-14 2000-08-22 Online Anywhere Method and apparatus to connect a general purpose computer to a special purpose system
US6167449A (en) * 1997-11-19 2000-12-26 Apple Computer, Inc. System and method for identifying and locating services on multiple heterogeneous networks using a query by type
US6324584B1 (en) * 1997-11-26 2001-11-27 International Business Machines Corp. Method for intelligent internet router and system
US6141686A (en) * 1998-03-13 2000-10-31 Deterministic Networks, Inc. Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control
US6256635B1 (en) * 1998-05-08 2001-07-03 Apple Computer, Inc. Method and apparatus for configuring a computer using scripting
US6522641B1 (en) * 1998-06-02 2003-02-18 Nortel Networks Limited Integrated data centric network (IDCN)
US6549773B1 (en) * 1998-09-21 2003-04-15 Nokia Mobile Phones Limited Method for utilizing local resources in a communication system
US6321338B1 (en) * 1998-11-09 2001-11-20 Sri International Network surveillance
US6253367B1 (en) * 1998-11-18 2001-06-26 Micrografx, Inc. Method and system for transforming dynamic content for use on the internet
US6256676B1 (en) * 1998-11-18 2001-07-03 Saga Software, Inc. Agent-adapter architecture for use in enterprise application integration systems
US6466974B1 (en) * 1998-12-04 2002-10-15 Sun Microsystems, Inc. Environment for creating and managing network management software objects
US6473759B1 (en) * 1999-01-12 2002-10-29 International Business Machines Corporation Method and system for accessing java applications
US6453320B1 (en) * 1999-02-01 2002-09-17 Iona Technologies, Inc. Method and system for providing object references in a distributed object environment supporting object migration
US6513019B2 (en) * 1999-02-16 2003-01-28 Financial Technologies International, Inc. Financial consolidation and communication platform
US7310615B2 (en) * 1999-02-16 2007-12-18 Goldensource Corporation Financial data reporting system with alert notification feature and free-form searching capability
US6424841B1 (en) * 1999-02-18 2002-07-23 Openwave Systems Inc. Short message service with improved utilization of available bandwidth
US6591272B1 (en) * 1999-02-25 2003-07-08 Tricoron Networks, Inc. Method and apparatus to make and transmit objects from a database on a server computer to a client computer
US6343287B1 (en) * 1999-05-19 2002-01-29 Sun Microsystems, Inc. External data store link for a profile service
US20020049858A1 (en) * 2000-01-14 2002-04-25 Frietas Nathaniel X. Software architecture for wireless data and method of operation thereof
US6877023B1 (en) * 2000-01-28 2005-04-05 Softwired, Inc. Messaging system for delivering data in the form of portable message formats between message clients
US7489704B2 (en) * 2000-01-28 2009-02-10 Softwired, Inc. Messaging system for delivering data in the form of portable message formats between message clients
US6347340B1 (en) * 2000-02-18 2002-02-12 Mobilesys, Inc. Apparatus and method for converting a network message to a wireless transport message using a modular architecture
US7155490B1 (en) * 2000-03-01 2006-12-26 Freewebs Corporation System and method for providing a web-based operating system
US20020120719A1 (en) * 2000-03-31 2002-08-29 King-Hwa Lee Web client-server system and method for incompatible page markup and presentation languages
US7458082B1 (en) * 2000-05-09 2008-11-25 Sun Microsystems, Inc. Bridging between a data representation language message-based distributed computing environment and other computing environments using proxy service
US20050240621A1 (en) * 2000-05-22 2005-10-27 Mci, Inc. Method and system for managing partitioned data resources
US6721779B1 (en) * 2000-07-07 2004-04-13 Softwired Ag Messaging proxy system
US20020178126A1 (en) * 2001-05-25 2002-11-28 Beck Timothy L. Remote medical device access

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7478395B2 (en) * 2002-09-23 2009-01-13 Telefonaktiebolaget L M Ericsson (Publ) Middleware application message/event model
US20040127250A1 (en) * 2002-09-23 2004-07-01 Bjorn Bjare Middleware application message/event model
US20050240654A1 (en) * 2004-04-21 2005-10-27 Andreas Wolber Message-oriented middleware provider having multiple server instances integrated into a clustered application server infrastructure
US7664818B2 (en) * 2004-04-21 2010-02-16 Sap (Ag) Message-oriented middleware provider having multiple server instances integrated into a clustered application server infrastructure
US8166150B2 (en) * 2004-09-13 2012-04-24 The Boeing Company Systems and methods enabling interoperability between network-centric operation (NCO) environments
US20110029656A1 (en) * 2004-09-13 2011-02-03 The Boeing Company Systems and methods enabling interoperability between network-centric operation (nco) environments
US7784065B2 (en) * 2005-02-07 2010-08-24 Microsoft Corporation Interface for consistent program interaction with auxiliary computing devices
US20060176271A1 (en) * 2005-02-07 2006-08-10 Microsoft Corporation Interface for consistent program interaction with auxiliary computing devices
US8670749B2 (en) 2007-04-13 2014-03-11 Hart Communication Foundation Enhancing security in a wireless network
US8406248B2 (en) 2007-04-13 2013-03-26 Hart Communication Foundation Priority-based scheduling and routing in a wireless network
US20090052429A1 (en) * 2007-04-13 2009-02-26 Hart Communication Foundation Synchronizing Timeslots in a Wireless Communication Protocol
US20080274766A1 (en) * 2007-04-13 2008-11-06 Hart Communication Foundation Combined Wired and Wireless Communications with Field Devices in a Process Control Environment
US8942219B2 (en) 2007-04-13 2015-01-27 Hart Communication Foundation Support for network management and device communications in a wireless network
US20080273486A1 (en) * 2007-04-13 2008-11-06 Hart Communication Foundation Wireless Protocol Adapter
US20090010233A1 (en) * 2007-04-13 2009-01-08 Hart Communication Foundation Wireless Gateway in a Process Control Environment Supporting a Wireless Communication Protocol
US20110216656A1 (en) * 2007-04-13 2011-09-08 Hart Communication Foundation Routing Packets on a Network Using Directed Graphs
US20090010203A1 (en) * 2007-04-13 2009-01-08 Hart Communication Foundation Efficient Addressing in Wireless Hart Protocol
US8169974B2 (en) 2007-04-13 2012-05-01 Hart Communication Foundation Suspending transmissions in a wireless network
US8230108B2 (en) 2007-04-13 2012-07-24 Hart Communication Foundation Routing packets on a network using directed graphs
US8325627B2 (en) 2007-04-13 2012-12-04 Hart Communication Foundation Adaptive scheduling in a wireless network
US8356431B2 (en) 2007-04-13 2013-01-22 Hart Communication Foundation Scheduling communication frames in a wireless network
US20090046675A1 (en) * 2007-04-13 2009-02-19 Hart Communication Foundation Scheduling Communication Frames in a Wireless Network
US8892769B2 (en) 2007-04-13 2014-11-18 Hart Communication Foundation Routing packets on a network using directed graphs
US8451809B2 (en) 2007-04-13 2013-05-28 Hart Communication Foundation Wireless gateway in a process control environment supporting a wireless communication protocol
US8570922B2 (en) 2007-04-13 2013-10-29 Hart Communication Foundation Efficient addressing in wireless hart protocol
US8660108B2 (en) 2007-04-13 2014-02-25 Hart Communication Foundation Synchronizing timeslots in a wireless communication protocol
US20080279204A1 (en) * 2007-04-13 2008-11-13 Hart Communication Foundation Increasing Reliability and Reducing Latency in a Wireless Network
US8670746B2 (en) 2007-04-13 2014-03-11 Hart Communication Foundation Enhancing security in a wireless network
US8676219B2 (en) 2007-04-13 2014-03-18 Hart Communication Foundation Combined wired and wireless communications with field devices in a process control environment
US8798084B2 (en) 2007-04-13 2014-08-05 Hart Communication Foundation Increasing reliability and reducing latency in a wireless network
US8441947B2 (en) 2008-06-23 2013-05-14 Hart Communication Foundation Simultaneous data packet processing
US20100110916A1 (en) * 2008-06-23 2010-05-06 Hart Communication Foundation Wireless Communication Network Analyzer
US11201919B2 (en) * 2014-05-27 2021-12-14 Commvault Systems, Inc. Offline messaging between a repository storage operation cell and remote storage operation cells via an intermediary media agent
US11336740B2 (en) * 2020-04-16 2022-05-17 Deutsche Telekom Ag Proxy-based messaging system of a telecommunication network

Also Published As

Publication number Publication date
US20140129657A1 (en) 2014-05-08
US20090178063A1 (en) 2009-07-09
DE60138887D1 (en) 2009-07-16
AU2001263715A1 (en) 2002-01-21
US6721779B1 (en) 2004-04-13
KR20030021243A (en) 2003-03-12
CN1456005A (en) 2003-11-12
US20090157883A1 (en) 2009-06-18
WO2002005507A3 (en) 2002-06-13
CN1201539C (en) 2005-05-11
KR100810170B1 (en) 2008-03-06
EP1299980B1 (en) 2009-06-03
CN1671144A (en) 2005-09-21
WO2002005507A2 (en) 2002-01-17
US8650244B2 (en) 2014-02-11
ATE433244T1 (en) 2009-06-15
US9906487B2 (en) 2018-02-27
EP1299980A2 (en) 2003-04-09
US20090157836A1 (en) 2009-06-18

Similar Documents

Publication Publication Date Title
US6721779B1 (en) Messaging proxy system
EP0950969B1 (en) Method and system for out-tasking conversions of message attachments
US6877023B1 (en) Messaging system for delivering data in the form of portable message formats between message clients
US9143382B2 (en) Automatic download of web content in response to an embedded link in an electronic mail message
US20040121789A1 (en) Method and apparatus for communicating information in a global distributed network
US6795864B2 (en) System using lookup service proxy object having code and request rate for managing rate at which client can request for services from server are transmitted
US7746824B2 (en) Method and apparatus for establishing multiple bandwidth-limited connections for a communication device
GB2428828A (en) Publish/subscribe messaging system
US20070211699A1 (en) Wireless services provider network system and method
EP1421759B1 (en) Terminals adapted to act as relay servers for distributing packets in a client-server network
KR20030073459A (en) System for interoperability between a MMS phone and a non-MMS phone and method thereof
WO2001088653A2 (en) An e-mail management system for wireless pcd

Legal Events

Date Code Title Description
AS Assignment

Owner name: SOFTWIRED AG, SWITZERLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MAFFEIS, SILVANO;REEL/FRAME:022291/0406

Effective date: 20000913

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD.,

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SOFTWIRED AG;REEL/FRAME:027219/0894

Effective date: 20111031

Owner name: TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD.,

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SOFTWIRED AG;REEL/FRAME:027225/0341

Effective date: 20111031