Method having multiple interfaces with distinguished...

Details Method having multiple interfaces with distinguished... Method having multiple interfaces with distinguished...

2000-06-05

2004-09-28

Lim, Krisa (Department: 2153)

Electrical computers and digital processing systems: interprogra

Application program interface

Reexamination Certificate

active

06799318

ABSTRACT:

TECHNICAL FIELD
This invention relates generally to communication between electronic devices and, more particularly, relates to methods to transfer data and objects between electronic devices.
BACKGROUND OF THE INVENTION
OBEX (Object Exchange) is a protocol that is similar to the Hypertext Transfer Protocol (HTTP). It provides the same basic functionality in a lighter fashion using a client-server model. OBEX consists of a protocol and an application framework. The application framework is built on top of the protocol and is used to ensure interoperability between devices and applications using OBEX. The protocol consists of a format for communication between devices and applications and a set of functions. The functions include initiating a connection, disconnecting a connection, sending an object from a client to a server (push operation), and requesting that a server return an object to a client (pull operation).
Presently, there are 3 transports—IP, IrDA, and Bluetooth—that OBEX can operate over. Applications and devices need to know transport specific information before using a particular transport. OBEX applications typically have to be re-written each time a transport using a different protocol becomes available. More transports are becoming available that use OBEX. Re-writing OBEX applications for each new transport is time consuming and destabilizing and adds to both the development and testing effort. A method is needed whereby applications can be run on new transports that become available without having to be re-written.
SUMMARY OF THE INVENTION
In view of the aforementioned problems, OBEX is implemented in such a way as to expose a protocol independent interface. This allows OBEX applications to communicate without having to know transport specific information. The main advantage to this approach is that OBEX applications will not need to be re-written when a new protocol for OBEX becomes available. Only a small piece of transport specific data needs to be updated in order for the application to work over the new transport.
The OBEX services reside on top of an OBEX layer. The OBEX layer communicates with the transports with a interface that is independent of the transport protocol and other interfaces are provided when connections are created. The OBEX layer allocates packets and post them down to the transports for incoming data from an application or module. When an incoming data packet is received from a transport, the layer determines which of the OBEX services should receive notification, abstracts the OBEX data and provides it to the appropriate OBEX services. The OBEX layer generates outbound packets for data passed into the OBEX layer by an OBEX service. The layer generates the correct headers for the protocol being used and sends the outbound packets down to the appropriate transport for sending to an application or module.
Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments which proceeds with reference to the accompanying figures.


REFERENCES:
patent: 5136716 (1992-08-01), Harvey et al.
patent: 5386568 (1995-01-01), Wold et al.
patent: 5425028 (1995-06-01), Britton et al.
patent: 5548723 (1996-08-01), Pettus
patent: 5572724 (1996-11-01), Watanabe et al.
patent: 5612898 (1997-03-01), Huckins
patent: 5706437 (1998-01-01), Kirchner et al.
patent: 5710908 (1998-01-01), Man
patent: 5758186 (1998-05-01), Hamilton et al.
patent: 5987517 (1999-11-01), Firth et al.
patent: 6023698 (2000-02-01), Lavey et al.
patent: 6032198 (2000-02-01), Fujii et al.
patent: 6247020 (2001-06-01), Minard
patent: 6351776 (2002-02-01), O'Brien et al.
patent: 6408342 (2002-06-01), Moore et al.
patent: 6434617 (2002-08-01), Clough et al.
patent: 6591295 (2003-07-01), Diamond et al.
Artisoft, “Using NodeRunner/SI with NDIS,” 1993, 8 pages.
Moore, “Windows, Wireless Architecture”, 71 pages.
Ray et al., “Bluetooth Stack in Windows”, 30 pages.
Specification of the Bluetooth System,v1.0B, Dec. 1, 1999.
Riku Mettala et al.,Bluetooth Protocol Architecture(White Paper), v1.0, Nokia Mobile Phones, Sep. 29, 1999.
Brent Miller et al.,Mapping Salutation Architecture APIs to Bluetooth Service Discovery Layer(White Paper), v1.0, IBM Corporation, Jul. 1, 1999.
IEEE Standard, 802.11,Part 11: Wireless LAN Medium Access Control(MAC)and Physical Layer(PHY)Specifications,1stEd. 1999, and Supplements 802.11a-1999 and 802.11b-1999.
Bob O'Hara and Al Petrick,IEEE 802.11 Handbook A Designer's Companion,Dec. 1999.
Pat Megowan et al.,IrDA Object Exchange Protocol,v1.2, Counterpoint Systems Foundry, Inc. Microsoft Corporation, Mar. 18, 1999.

Affiliated with

Also associated with

Rating

Method having multiple interfaces with distinguished... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method having multiple interfaces with distinguished..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method having multiple interfaces with distinguished... will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3215643