Patent Grant
7039033
This invention relates generally to wireless devices in a wireless network using short-range radio signals.
A user has numerous wireless devices for accessing and processing information. For example, a user may have a cellular telephone for communicating with others, a personal digital assistant (“PDA”) for storing contact information, a laptop computer for storing and processing files, a digital camera for obtaining images and a pager for being contacted. Each one of these devices also may access remote information on a private or public network, such as the Internet. However, this system suffers from several disadvantages.
First, typically only a single device originates and can access the Internet at a time.
Second, Internet protocol (“IP”) addresses are held while connected to the Internet. This can be expensive and use scarce IP address resources.
Third, each device requires its own security management, such as a Virtual Private Network (“VPN”) and firewall software component.
Fourth, there is no ability to share, add to or manage the services of the numerous wireless devices. In particular, there is no communication between wireless devices. If a user obtains a wireless device having an additional service, such as extra persistence storage, other wireless devices typically are not capable of using the extra persistence storage.
Bluetooth™ technology (www.bluetooth.com) provides wireless communications between devices. Yet, Bluetooth™ technology also suffers from many disadvantages. Bluetooth™ technology does not allow for a “plug and play” capability at a wireless device application level. In other words, a wireless device cannot merely be turned on and Bluetooth™ technology recognizes it and establishes a communication protocol. If a user desires a wireless device to communicate with a Bluetooth™ technology device, the added wireless device must have software drivers and applications loaded to operate. Otherwise, the Bluetooth™ technology device is not able to communicate with the newly added wireless device. This makes it difficult to add new functionality or types of wireless devices. Bluetooth™ technology does not provide an open environment for software programmers to provide application software components for wireless devices. Further, Bluetooth™ technology does not allow devices to share information and resources at an application level.
Therefore, it is desirable to provide a system of wireless devices which can effectively communicate with each other and access information on the Internet. The system of wireless devices should efficiently use IP resources and security management. The wireless devices should effectively share and manage services and allow for seamless plug and play capability. The system should allow for new functionality and types of wireless devices.
A system, coupled to a cellular network, provides access to the Internet according to an embodiment of the present invention. The system comprises a wireless gateway device, coupled to the cellular network, having a network manager software component for accessing information from the Internet responsive to a first short-range radio signal. A first wireless device is coupled to the wireless gateway device. The first wireless device provides the first short-range radio signal.
According to an embodiment of the present invention, the first wireless device is selected from a group consisting of a desktop computer, a laptop computer, a personal digital assistant, a headset, a printer, a pager, a watch, digital camera and an equivalent thereof.
According to an embodiment of the present invention, the wireless gateway device is a cellular telephone using a Global System for Mobile communications (“GSM”) protocol.
According to an embodiment of the present invention, the wireless gateway device is a cellular telephone using a Code Division Multiple Access (“CDMA”) protocol.
According to an embodiment of the present invention, the wireless gateway device is a cellular telephone using a Time Division Multiple Access (“TDMA”) protocol.
According to an embodiment of the present invention, the first wireless device is a thin terminal.
According to an embodiment of the present invention, the first wireless device includes a Bluetooth™ processor having a 2.4 GHZ transmitter.
According to an embodiment of the present invention, the wireless gateway device includes a Bluetooth™ processor having a 2.4 GHZ transmitter.
According to an embodiment of the present invention, the network manager software component includes a plug and play software component for loading and executing software for the first wireless device.
According to an embodiment of the present invention, the network manager software component includes a PIN number management software component for obtaining and supplying PIN numbers.
According to embodiment of the present invention, the network manager software component includes a service repository software component for obtaining and providing an availability of a service from the first wireless device.
According to an embodiment of the present invention, the first wireless device includes an application software component for providing a service. The network manager software component includes a management software component for accessing the service.
According to an embodiment of the present invention, the system further comprises a second wireless device coupled to the wireless gateway device. The second wireless device provides a short-range signal. The first wireless device communicates with the second wireless device through the wireless gateway device.
According to an embodiment of the present invention, the system further comprises a second wireless device coupled to the wireless gateway device. The wireless gateway device provides access to the Internet for the first and second wireless devices.
According to an embodiment of the present invention, the network manager software component operates with an operating system software component.
According to an embodiment of the present invention, the operating system component is a Linux, EPOC or a PocketPC operating system.
According to an embodiment of the present invention, the wireless gateway device includes 1) an application software component for providing a service, and 2) an application server software component coupled to the network management software component.
According to an embodiment of the present invention, the wireless gateway device further includes a firewall software component.
According to an embodiment of the present invention, the wireless gateway device includes a VPN software component.
According to an embodiment of the present invention, a hand-held device for providing a personal area network is provided. The hand-held device comprises a storage device coupled to a processor. The storage device stores a software component for controlling the processor. The processor operates with the component to provide a short-range radio Internet protocol communication between the first hand-held wireless device and a second hand-held wireless device.
According to an embodiment of the present invention, a Bluetooth™ transmitter is coupled to the processor.
According to an embodiment of the present invention, a GSM transmitter is coupled to the processor.
According to an embodiment of the present invention, a wireless hand-held device accesses a router in a personal network. The wireless hand-held device comprises a storage device coupled to a processor. The storage device stores a software component for controlling the processor. The processor operates with the component to provide a first short-range radio signal to the router for accessing the Internet and a second short-range radio signal to the router for accessing another wireless hand-held device.
According to an embodiment of the present invention, an article of manufacture, including a computer readable medium is provided. The article of manufacture comprises an application software component for providing a service. An application server software component provides the application software component. The article of manufacture also includes an Internet protocol network manager software component and an operating system software component. Also, a short-range radio software component for providing a short-range radio signal and a cellular software component for providing a communications signal to a cellular network is included with the article of manufacture.
Other aspects and advantages of the present invention can be seen upon review of the figures, the detailed description, and the claims that follow.
a–b are hardware block diagrams of a wireless gateway device and wireless hand held device according to an embodiment of the present invention.
a–b are software block diagrams for a wireless gateway device according to an embodiment of the present invention.
a–b illustrate multiple wireless devices coupled to a wireless gateway device according to an embodiment of the present invention.
I. System Overview
The following description and claims relate to a system that accesses information from a wide area network (“WAN”), such as the Internet, and local wireless devices in response to short-range radio signals. The network may also be an IP based public or private network, such as a corporate secured network using VPN.
In alternate embodiments of the present invention, other local wireless technologies such as 802.11 or HomeRF signals are used to communicate between gateway device 106 and terminals 107.
In an embodiment of the present invention, gateway device 106 is coupled to cellular network 105 by cellular signals 111 using a protocol, such as a Global and System for Mobile communications (“GSM”) protocol. In alternate embodiments, a Code Division Multiple Access (“CDMA”), CDMA 2000 or Time Division Multiple Access (“TDMA”), or General Packet Radio Service (“GPRS”) protocol is used.
In an alternate embodiment of the present invention, gateway device 106 is coupled to a landline network by an Ethernet, Digital Subscriber Line (“DSL”), or cable modem connection, singly or in combination.
In an embodiment of the present invention, gateway device 106 is a cellular telephone.
Cellular network 105 is coupled to a wireless carrier internal network or carrier backbone 104. In an embodiment of the present invention, server 102 is coupled to carrier backbone 104. In an alternate embodiment of the present invention, carrier backbone 104 is coupled to Internet 103. Server 101 is coupled to Internet 103. In an embodiment of the present invention, servers 101 and 102 provide information, such as web pages or application software components to terminals 107 by way of gateway device 106. In an embodiment of the present invention, terminals 107 share services and communicate by way of gateway device 106.
II. Gateway/Handheld Device Hardware
In an embodiment, PMG device 201 is also illustrated in
a illustrates a hardware block diagram of gateway device 106 in an embodiment of the present invention. Gateway device 106 includes both internal and removable memory. In particular, gateway device 106 includes internal FLASH (or Electrically Erasable Programmable Read-Only Memory (“EEPROM”) and static Random Access Memory (“SRAM”) memory 302 and 303, respectively. Removable FLASH memory 304 is also used in an embodiment of the present invention. Memories 302, 303 and 304 are coupled to bus 305. In an embodiment of the present invention, bus 305 is an address and data bus. Application processor 301 is likewise coupled to bus 305. In an embodiment of the present invention, processor 301 is a 32 bit processor.
Bluetooth™ processor 307 is also coupled to bus 305. Bluetooth™ RF circuit 309 is coupled to Bluetooth™ processor 307 and antenna 313. Processor 307, RF circuit 309 and antenna 313 transmit and receive short-range radio signals to and from terminals 107 illustrated in
Cellular, such as GSM, signals are transmitted and received using digital circuit 306, analog circuit 308, transmitter 310, receiver 311 and antenna 312. Digital circuit 306 is coupled to bus 305. In alternate embodiments, gateway device 106 includes a display, a speaker, a microphone, a keypad and a touchscreen, singly or in combination thereof.
b illustrates device 350 that is a hand-held device in an embodiment of the present invention. Device 350, in an embodiment of the present invention, is one of the terminals 107 illustrated in
III. Gateway Software
In an embodiment of the present invention, gateway software 400, or components of gateway software 400, is stored in an article of manufacture, such as a computer readable medium. For example, gateway software 400 is stored in a magnetic hard disk, an optical disk, a floppy disk, CD-ROM (Compact Disk ReadOnly Memory), RAM (Random Access Memory), ROM (Read-Only Memory), or other readable or writeable data storage technologies, singly or in combination. In yet another embodiment, gateway software 400, or components thereof, is downloaded from server 101 illustrated in
Gateway software 400 includes telecommunication software or physical layer protocol stacks, in particular cellular communications software 401 and short-range radio communications software 402. In an embodiment, communication software 401 is a GPRS baseband software component used with processor 306 to transmit and receive cellular signals. In an embodiment, communication software 402 is a Bluetooth™ baseband software component used with processor 307 to transmit and receive short-range radio signals.
In an embodiment of the present invention, operating system 403 is used to communicate with telecommunications software 401 and 402. In an embodiment of the present invention, operating system 403 is a Linux operating system, EPOC operating system available from Symbian software of London, United Kingdom or a PocketPC or a Stinger operating system available from Microsoft of Redmond, Wash. Operating system 403 manages hardware and enables execution space for gateway device software components.
Network Management software 404 is used to provide a number of functions according to embodiments of the present invention: 1) routing, 2) device plug and play, 3) PIN number management, 4) network device management, and 5) service repository. In an embodiment of the present invention, network management software 404 is programmed in C++ software language.
Smart phone application software 405 communicates with operating system 403 and is used in a cellular telephone embodiment of the present invention.
1st and 2nd software application components 406 communicate with management software 404 and provide additional services to a user. For example, application components 406 may include: 1) a stock quote application for providing stock quotes, 2) a personal information manager application including calendars, to do lists, emails, or contacts, 3) a synchronization software application for synchronizing databases, 4) a telephony application for providing telephone services, or 5) a location application for providing a current location of a gateway device.
Furthermore, Graphics User Interface (“GUI”) 407 is provided to allow a user-friendly interface.
a illustrates detailed gateway software architecture 500. In an embodiment of the present invention, network management software 404 illustrated in
PAN router 404c establishes a PAN network, implementing communication primitives, IP networking, IP services and similar tasks.
PAN server 404b is responsible for implementing PAN oriented services such as plug and play, terminal enumeration, application loading, storage space and other services. In an embodiment, PAN server 404b communicates directly with applications 406 using application drivers.
PAN application server 404a is responsible for implementing user and terminal oriented services and enables thin terminals. In an embodiment of the present invention, PAN application server 404a implements such applications as a GUI 407, a remote terminal driver application, a location application, a telephony application or an equivalent thereof.
a, like
PAN router 404c enables a fully meshed IP based network. In an embodiment of the present invention, each terminal can leverage the existing IP protocol, exchange data with other terminals and gain access to a WAN through PAN router 404c.
b illustrates software components of PAN router 404c. In an embodiment of the present invention, routing component 550, Bluetooth™ LAN access Profile component 551, Dynamic Host Configuration Protocol/Point-to-Point Protocol (“DHCP/PPP”) component 552 and Network Address Translator (“NAT”) component 553 are used in PAN router 404c. In an alternate embodiment, Domain Naming Service (“DNS”) component 554, Tunneling and Optimization component 555 and Security component 556, singly or in combination are used in PAN router 404c.
Routing component 550 is implemented in Router 404c in order to realize a fully meshed IP network with access to a WAN. A routing component is responsible for imitating a fully meshed network based on a Master/Slave network.
Routing component 550 enables exchange of IP packets between two terminals, broadcasting of IP packets between all terminals on a PAN and routing of IP packets to and from a WAN.
A Bluetooth™ LAN Access Profile (“LAP”) component 551 is used in order to enable terminals to seamlessly use IP base networking. LAP component 551 enables terminals to exchange IP packets between themselves and PAN router 404c. LAP component 551 is implemented over a PPP serial Bluetooth™ connection. In an embodiment of the present invention, terminals, such as Smart terminals, include LAP chipsets.
DHCP and PPP components 552 are used in order to enable an IP network. PPP realizes an IP network layered over LAP component 551.
DHCP component manages a PAN's IP address space and IP services, enabling terminals to get IP networking properties, such as an IP address for a terminal, an address of a DNS and an address of a default gateway device.
NAT component 553 translates a private IP address to and from a real IP address. Since mobile networks are typically capable of only providing a single IP address, the terminals will have to use private IP addresses supplied by NAT component 553.
DNS component 554 translates services between human readable names and IP addresses. DNS component 554 enables a terminal to query another terminal's address based on the other terminal's name and to query for the IP address of a named service on a WAN.
Tunneling and Optimization component 555 allows terminals to use standard protocols. For example, accessing a WAN through a cellular GPRS/CDMA network using TCP/IP yields poor results because TCP/IP does not behave well over a bandwidth limited, high latency and high packet loss network, such as GPRS/CDMA.
Tunneling and Optimization component 555 is used to enable practical usage of IP in such networks. When using cellular, the tunnel will be between a mobile device having a PAN router and a landline operator's network. The tunneling and optimization network translates IP packets to more efficient transport methods for the specific access technology, and vice versa in a fully transparent fashion.
Accessing a WAN can typically be done in two ways: unsecured when accessing a public network, such as the Internet, or secured when accessing a private network, such as an Enterprise network, file system or Exchange server.
Security component 556 is a centralized managed way for controlling access to a secured private WAN. In order to avoid each one of the terminals from implementing its own security scheme and methods, a centralized security component 556 is used. In an embodiment of the present invention, security component 556 is a firewall 556a, VPN 556b or URL filter 556c, singly or in combination.
In this scenario, a user is a traveling professional, who has a PDA and needs to synchronize the PDA against a corporate Exchange server while on the road. This synchronization needs to be done securely as the only way to enter the corporate network is via a certified and an information technology (“IT”) manager approved VPN.
The user has a gateway device enabled handset with an embedded PAN router 404c and VPN client, which the IT manager installed.
As the user turns on the PDA, which is a Bluetooth™ equipped PDA with a LAP component 551, the PDA connects to a gateway device handset via the LAP. The PDA receives a local PAN IP address.
The user loads the PDA synchronization software, which is configured to synchronize against the corporate Exchange server. When hitting the “Synchronize” button, the PDA opens a TCP connection to the IP address
The IP packets travel across the Bluetooth™ air interface to the handset using a PPP protocol. At the handset, the packets go through a NAT component and a local IP address is translated to a real Internet IP address. The real IP address goes to the VPN, which identifies the destination as the corporate LAN. The VPN packages the packet over its Internet tunnel, encrypts and signs it. The packet is then sent through the cellular air interface to the operator and the Internet, reaching the corporate VPN and Exchange servers. The PDA is totally unaware of this process.
PAN server 404b allows code to be downloaded to a PAN and executed in a central way. Similarly, PAN server 404b shares and stores data in a centralized manner.
PAN server 404b uses media abstraction layer 504 in order to communicate with terminals 107. PAN server 404b transfers services and devices enumerations to PAN router 404c; while, a terminal ID number is provided to PAN server 404b from PAN router 404c. A terminal ID is a unique code for identifying a particular terminal. Finally, a PIN number is transferred from PAN server 404b to PAN router 404c.
In an embodiment of the present invention, PAN server 404b loads an executable application software component to a selected terminal. Application server 404a retrieves the application software component locally from gateway device 106 memory or from either server 102 or 103 as illustrated in
Backend middleware 485 provides a PIN number to router 404c. In an embodiment of the present invention, backend middleware 485 is stored on a server coupled to cellular network 105 shown in
When a new terminal is introduced to a PAN, the software to support this terminal needs to be located, downloaded and executed. The Plug and Play component is responsible for identifying the introduction of the new terminal and deciding on the software needed to be downloaded.
An example of the Plug and Play usage is when a new thin terminal, like a messaging terminal, is introduced to a PAN. The terminal itself, being thin, has no embedded application code or data. The appropriate software package (messaging software in this case) needs to be found, downloaded and executed. The Plug and Play component will identify the messaging terminal and resolve the needed software to support it.
Adding new capabilities to a PAN involves the loading of executable code to a PAN execution environment. Application loading can be a result of many events: plug and play component 701 can generate an application loading for supporting a new terminal on a PAN, a user can decide to actively load an application to a PAN or an operator on a cellular network can decide to load an application to a PAN. Application loader 705 is responsible for application software code transfer and execution.
Whenever gateway device 106 and a terminal become aware of each other, a pairing process takes place between them. For example, gateway device 801 and terminal 802 are paired as illustrated in
PAN server 404b will supply a PIN number upon an explicit request of another component, such as PAN router 404c. In an alternate embodiment, Application server 404b will supply PIN number information for terminals in order for them to establish a Bluetooth™ channel with other terminals without a gateway device 107 as a mediator.
In an embodiment of the present invention, PIN numbers are available from backend middleware 485. In alternate embodiments of the present invention, applications 406 provide a PIN number. For example, an application may allow a user to enter a PIN number or an application may cause backend middleware 485 to generate a PIN number. In an embodiment of the present invention, an application that supplies a PIN number states its origin.
There are two methods for obtaining PIN numbers. First, a push method occurs when the source of the PIN number transfers the PIN number when it becomes available. Second, a query method occurs when router 404c queries the source of the PIN number for a PIN number according to a certain criteria. A push method is preferred because it enables an immediate response to a request for a PIN number. However, if the PIN number is not available when a request arrives at the source of the PIN number, PAN server 404b attempts to obtain the PIN number using the query method. When the push method is used, the stimulus comes from the PIN number information source.
PIN number management software component 702 maintains a local database of PIN numbers with some attributes. An attribute may include a terminal class or terminal ID. PIN number management software component 702 adds, deletes and retrieves PIN numbers from the database. PIN number software component 702 also may retrieve all PIN numbers associated with a screen terminal class. In an embodiment, PIN number management software component 702 will have a persistent database. In an alternate embodiment, PIN number management software component 702 will not have a persistent database.
In alternate embodiments of the present invention, PIN number management 702 is a central storage location for PAN databases and/or caching. The storage component supports implementation of a file system that can be accessed by a terminal. Also, a storage component may have automatic backup to a backend server or transparent storage.
Management software component 703 provides functions to configure a PAN.
First, management software component 703 provides a disconnect service function that forces specific applications to disconnect from a specific service.
Second, management software component 703 provides a disconnect terminal function that forces specific applications to disconnect from all services of a specific terminal.
Third, management software component 703 provides a disable service function that halts any usage of a specific terminal's service.
Fourth, management software component 703 provides a disable terminal function that halts any usage of all services of a specific terminal.
The disconnecting functions described above allow a high priority application to obtain a service from an application using the service. The disabling functions allow for high priority applications to create personal area network restrictions.
Service repository software component 704 is used to cease offering services. PIN Number management 702 is used to delete a PIN number and abstraction layer I/O is used to halt service's data traffic.
Service repository software component 704 allows applications 406, which run on a gateway device 106 or terminals 107, to discover what services are offered by a PAN, and to determine the characteristics of the available services. The service could be offered by remote terminal, such as an application in terminal 806 illustrated in
Service repository software component 704 offers a plurality of functions.
First, service repository software component 704 provides service registration of a service offered by application, or a hardware capability offered by terminal driver.
Second, service repository software component 704 provides service unregistration that cancels a registered service.
Third, service repository software component 704 provides registered services that suit a specific class.
Fourth, service repository software component 704 also provides searching of services. This function describes whether listed terminals support listed services. This function enables an application to quickly locate a specific service. A search of a general class of service, such as a search for a printers may be performed. Likewise, a search for specific attributes associated with that service, for example laser or color, is provided. Further, a search for specific instance of a service, for example a HP LaserJet model GTI, is also provided.
Fifth, service repository software component 704 provides the capability of describing the participating terminals in a personal area network. The existence of these terminals is derived from a service registration function.
Sixth, service repository software component 704 provides a disabling function that ceases offering an unfriendly service.
Seventh, service repository software component 704 also provides an enabling function that cancels service disabling.
Eighth, service repository software component 704 provides a terminal disabling function that ceases offering all the services associated with an unfriendly terminal.
Ninth, service repository software component 704 provides a terminal enabling function that cancels terminal disabling.
In an embodiment, an application does not have to discover a service in order to connect with a terminal. If an application has previous knowledge of a terminal's service, the application needs to only search for the specific terminal.
In an embodiment of the present invention, service repository component 704 describes the terminals and the services that are available at a particular time, but service repository software component 704 does not describe the current status of the services. A service might be available in a PAN but not necessarily accessible since another application is exclusively using the service.
Since service repository software component 704 operates with local and remote applications, a uniform interface is used. In an embodiment of the present invention, remote applications use a Bluetooth™ Service Discovery Protocol (“SDP”) to discover what services gateway device 106 offers. Similarly, local applications use SDP in an embodiment of the present invention.
Application Server component 404a illustrated in
In an embodiment of the present invention, application server component 404a includes two components: 1) an execution environment and 2) services for being able to successfully execute software on a multi-terminal PAN, such as a file system.
Thin terminals, being optimized for low cost will not include an IP capability in most cases. Instead, they will use the native protocols offered by the PAN's physical layer. This does not conflict with the PAN router 404c since thin terminals are an extended remote I/O for applications running on a PAN application server 404a. All the logic, protocols and standard compatibility is implemented in the application server, in which standard protocols like IP are implemented and used.
In an embodiment of the present invention, a thin messaging terminal includes a color Liquid Crystal Display (“LCD”), QWERTY keypad, Bluetooth™ chipset and a small software stack for displaying graphical screens received over the Bluetooth™ air interface and transmit keypad actions back over the Bluetooth™ air interface.
When a terminal is turned on for the first time, a Plug and Play component 701 in the gateway device 106 identifies that this is a new terminal. Gateway device 106 communicates with Plug and Play component 701 in order to retrieve the needed software package to be executed on an application server 404a. In an embodiment of the present invention, a Plug and Play component 701 contains a URL for a chatting application package.
Application loader 705 gets the URL and loads the new package to PAN application server 404a in a gateway device 106 and executes the chatting software application. The chatting application software identifies the messaging device by enumerating a PAN for terminals and capabilities, and attaches itself to the right remote graphical driver and the remote keypad driver.
Now, all user interactions for the chatting application is displayed on the messaging terminal, and the keypad entries on the terminal are sent to the chatting application.
In this embodiment of the present invention, the terminal is used only for I/O and user interaction. The actual chatting logic is executed in application server 404a, which is located in gateway device 106.
IV. Gateway Device/Terminal Operations
First, PAN router 404c requests a PIN number from PIN number management component 702. Second, if a PIN number is available, PIN number management 702 transfers the PIN number to PAN router 404c. Otherwise, PIN number management 702 attempts to obtain the PIN number from other sources, such as applications 406 or backend middleware 485, and transfers the PIN number to PAN router 404c. Third, PAN router 404c notifies plug and play 701 that a pairing has ended and delivers a terminal ID to plug and play 701. Fourth, plug and play 701 resolves the terminal package URL with backend middleware 485 if a package is not locally available; otherwise, the package is loaded and executed. Finally, if the package contains drivers, the driver's services are offered to service repository 704.
Backend middleware 485 or an application acquires a PIN number. Second, the acquired PIN number is offered to PIN number management 702 by either backend middleware 485 or applications 406. In an alternate embodiment of the present invention, a PIN number is offered with additional characteristics of the associated terminal. PIN number information is then accepted and stored with the attributes in a database of PIN number management 702.
There are two methods for a gateway device 106 application to inquire for a specific service. The first terminal method includes the application asking service repository 704 to describe the terminals in the current personal area network and to describe whether any of these terminals provide the requested service. In an embodiment of the present invention, an application sorts the available terminals in order of preference. The application then queries abstraction layer I/O whether the most preferred terminal's service is available.
The second service method includes an application querying service repository 704 to provide the registered services that suit a requested service class. The application then searches the registered services to determine which capabilities are provided by the registered services. In an embodiment of the present invention, an application sorts the available services in order of preference. The application then queries abstract layer I/O whether the most preferred service is available.
Media abstraction layer 504 obtains an SDP of a remote terminal application. Media abstraction layer 504 passes the SDP call to service repository 704. Service repository 704 answers media abstraction layer 504, using SDP, according to services that are registered. The abstraction layer 504 then sends the answers to an application on remote terminal.
In an alternate embodiment, service repository 704 pushes new services to a Bluetooth™ stack SDP database. The Bluetooth™ stack replies automatically and generates an SDP request.
In response to a network configuration signal from a high priority application in applications 406, management component 703 generates a delete PIN number signal to PIN number management component 702 which deletes the PIN number associated with the selected terminal. Management component 703 generates a disable signal to service repository component 704 to cease offering all the services associated with the selected terminal. Management component 703 generates a disable service signal to abstraction layer I/O in order to halt all the transport to and from the selected terminal's services.
Abstraction layer I/O sends halt notifications to the applications that are currently using the selected terminal's services. Abstraction layer I/O then stops any data transport to and from the selected terminal's services.
V. Conclusion
The foregoing description of the preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, thereby enabling others skilled in the art to understand the invention for various embodiments and with the various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5442680 | Schellinger et al. | Aug 1995 | A |
| 5457737 | Wen | Oct 1995 | A |
| 5572528 | Shuen | Nov 1996 | A |
| 5742237 | Bledsoe | Apr 1998 | A |
| 5771438 | Palermo et al. | Jun 1998 | A |
| 5774791 | Strohallen et al. | Jun 1998 | A |
| 5793763 | Mayes et al. | Aug 1998 | A |
| 5805166 | Hall et al. | Sep 1998 | A |
| 5838252 | Kikinis | Nov 1998 | A |
| 5896369 | Warsta et al. | Apr 1999 | A |
| 5929848 | Albukerk et al. | Jul 1999 | A |
| 5978386 | Hamalainen et al. | Nov 1999 | A |
| 5987011 | Toh | Nov 1999 | A |
| 5987033 | Boer et al. | Nov 1999 | A |
| 6064734 | Hasegawa et al. | May 2000 | A |
| 6067291 | Kamerman et al. | May 2000 | A |
| 6069896 | Borgstahl et al. | May 2000 | A |
| 6078789 | Bodenmann et al. | Jun 2000 | A |
| 6085098 | Moon et al. | Jul 2000 | A |
| 6130602 | O'Toole et al. | Oct 2000 | A |
| 6151628 | Xu et al. | Nov 2000 | A |
| 6192257 | Ray | Feb 2001 | B1 |
| 6198948 | Sudo et al. | Mar 2001 | B1 |
| 6218958 | Eichstaedt et al. | Apr 2001 | B1 |
| 6223029 | Stenman et al. | Apr 2001 | B1 |
| 6243581 | Jawanda | Jun 2001 | B1 |
| 6265788 | Davidson et al. | Jul 2001 | B1 |
| 6282183 | Harris et al. | Aug 2001 | B1 |
| 6298443 | Colligan et al. | Oct 2001 | B1 |
| 6326926 | Shoobridge et al. | Dec 2001 | B1 |
| 6333973 | Smith et al. | Dec 2001 | B1 |
| 6343276 | Barnett | Jan 2002 | B1 |
| 6405027 | Bell | Jun 2002 | B1 |
| 6430408 | Dorenbosch | Aug 2002 | B1 |
| 6434537 | Grimes | Aug 2002 | B1 |
| 6446127 | Schuster et al. | Sep 2002 | B1 |
| 6452910 | Vij et al. | Sep 2002 | B1 |
| 6459882 | Palermo et al. | Oct 2002 | B1 |
| 6463078 | Engstrom et al. | Oct 2002 | B1 |
| 6487180 | Borgstahl et al. | Nov 2002 | B1 |
| 6519460 | Haartsen | Feb 2003 | B1 |
| 6532366 | Chung et al. | Mar 2003 | B1 |
| 6600428 | O'Toole et al. | Jul 2003 | B1 |
| 6600734 | Gernert | Jul 2003 | B1 |
| 6630925 | Östergård et al. | Oct 2003 | B1 |
| 6633759 | Kobayashi | Oct 2003 | B1 |
| 6636489 | Fingerhut | Oct 2003 | B1 |
| 6654616 | Pope et al. | Nov 2003 | B1 |
| 6665549 | Reed | Dec 2003 | B1 |
| 6690929 | Yeh | Feb 2004 | B1 |
| 6763012 | Lord et al. | Jul 2004 | B1 |
| 6763247 | Hollstrom et al. | Jul 2004 | B1 |
| 6871063 | Schiffer | Mar 2005 | B1 |
| 20010047424 | Alastalo et al. | Nov 2001 | A1 |
| 20020010008 | Bork et al. | Jan 2002 | A1 |
| 20020010683 | Aune | Jan 2002 | A1 |
| 20020037700 | Dooley et al. | Mar 2002 | A1 |
| 20020055333 | Davies et al. | May 2002 | A1 |
| 20020058502 | Stanforth | May 2002 | A1 |
| 20020063472 | Irvin | May 2002 | A1 |
| 20020065099 | Bjorndahl | May 2002 | A1 |
| 20020065817 | Ito et al. | May 2002 | A1 |
| 20020068559 | Sharma et al. | Jun 2002 | A1 |
| 20020068600 | Chihara et al. | Jun 2002 | A1 |
| 20020069037 | Hendrickson et al. | Jun 2002 | A1 |
| 20020082054 | Keinonen et al. | Jun 2002 | A1 |
| 20020086718 | Bigwood et al. | Jul 2002 | A1 |
| 20020091633 | Proctor | Jul 2002 | A1 |
| 20020102974 | Raith | Aug 2002 | A1 |
| 20020118663 | Dorenbosch et al. | Aug 2002 | A1 |
| 20020128051 | Liebenow | Sep 2002 | A1 |
| 20020132610 | Chaplin et al. | Sep 2002 | A1 |
| 20020142762 | Chmaytelli et al. | Oct 2002 | A1 |
| 20020143952 | Sugiarto et al. | Oct 2002 | A1 |
| 20020155830 | Iyer | Oct 2002 | A1 |
| 20020160764 | Gorsuch | Oct 2002 | A1 |
| 20030013438 | Darby | Jan 2003 | A1 |
| 20030017810 | Janninck et al. | Jan 2003 | A1 |
| 20030022699 | Lin | Jan 2003 | A1 |
| 20030027563 | Herle et al. | Feb 2003 | A1 |
| 20030032417 | Minear et al. | Feb 2003 | A1 |
| 20030050058 | Walsh et al. | Mar 2003 | A1 |
| 20030054765 | Botteck | Mar 2003 | A1 |
| 20030060188 | Gidron | Mar 2003 | A1 |
| 20030060189 | Minear et al. | Mar 2003 | A1 |
| 20030078036 | Chang et al. | Apr 2003 | A1 |
| 20030091917 | Davenport et al. | May 2003 | A1 |
| 20030114105 | Haller et al. | Jun 2003 | A1 |
| 20030115351 | Giobbi | Jun 2003 | A1 |
| 20030122856 | Hubbard | Jul 2003 | A1 |
| 20030143992 | Humphrey et al. | Jul 2003 | A1 |
| 20030153280 | Kopp et al. | Aug 2003 | A1 |
| 20030187807 | Matsubara et al. | Oct 2003 | A1 |
| 20030214940 | Takken | Nov 2003 | A1 |
| 20030224773 | Deeds | Dec 2003 | A1 |
| 20030232616 | Gidron et al. | Dec 2003 | A1 |
| 20040001467 | Cromer et al. | Jan 2004 | A1 |
| 20040048671 | Rowe | Mar 2004 | A1 |
| 20040066769 | Ahmavaara et al. | Apr 2004 | A1 |
| 20040192384 | Anastasakos et al. | Sep 2004 | A1 |
| 20040196812 | Barber | Oct 2004 | A1 |
| Number | Date | Country |
|---|---|---|
| 3153213 | Apr 2001 | JP |
| WO 9948315 | Sep 1999 | WO |
| WO 0039967 | Jul 2000 | WO |
| WO 01048977 | Jul 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20020163895 A1 | Nov 2002 | US |
