CA2683998C - Device detection and service discovery system and method for a mobile ad hoc communications network - Google Patents
Device detection and service discovery system and method for a mobile ad hoc communications network Download PDFInfo
- Publication number
- CA2683998C CA2683998C CA2683998A CA2683998A CA2683998C CA 2683998 C CA2683998 C CA 2683998C CA 2683998 A CA2683998 A CA 2683998A CA 2683998 A CA2683998 A CA 2683998A CA 2683998 C CA2683998 C CA 2683998C
- Authority
- CA
- Canada
- Prior art keywords
- nearby device
- discovered nearby
- middleware software
- discovered
- application
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
Abstract
An apparatus comprises a memory device and a processor disposed in communication with the memory device. The processor is configured to conduct an inquiry to discover nearby devices and to determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery. When the discovered nearby device does not provide an indication that it may include the middleware software the processor disconnects communication session establishment with the discovered nearby device. When the discovered nearby device provides an indication that it may include the middleware software, the processor creates a wireless short-range communication connection to the discovered nearby device. The processor confirms whether the nearby device includes the middleware software by requesting corresponding information from the discovered nearby device via the wireless short-range communication connection and when the discovered nearby device includes the middleware software, the processor executes the middleware software to perform application and service discovery with the discovered nearby device.
Description
DEVICE DETECTION AND SERVICE DISCOVERY
SYSTEM AND METHOD
FOR A MOBILE AD HOC COMMUNICATIONS NETWORK
FIELD OF THE INVENTION
[00021 The disclosed invention relates, in general, to communication between devices connected to a wireless communications network. In particular, the disclosed invention is a system and method for performing device detection and service discovery in a mobile ad hoc communications network.
SYSTEM AND METHOD
FOR A MOBILE AD HOC COMMUNICATIONS NETWORK
FIELD OF THE INVENTION
[00021 The disclosed invention relates, in general, to communication between devices connected to a wireless communications network. In particular, the disclosed invention is a system and method for performing device detection and service discovery in a mobile ad hoc communications network.
BACKGROUND OF THE IIWENTION
[00031 Short-range wireless systems have a range of less than one hundred meters, but may connect to the Internet to provide communication over longer distances.
Short-range wireless systems include, but are not limited to, a wireless personal area network (PAN) and a wireless local area network (LAN). A wireless PAN uses low-cost, low-power wireless devices that have a typical range of ten meters. An example of a wireless PAN technology is the Bluetooth Standard. The Bluetooth Standard operates in the 2.4 GHz Industrial, Scientific, and Medical (ISM) band and provides a peak air-link speed of one Mbps and a power consumption low enough for use in personal, portable electronics such as a personal digital assistance or mobile phone. A
description of the Bluetooth communication protocol and device operation principles is in Bluetooth Special Interest Group. Specification of the Bluetooth Standard, version 1.0B, volumes 1 and 2, December 1999. A wireless LAN is more costly than a wireless PAN, but has a longer range. An example of a wireless LAN technology is the IEEE 802.11 Wireless LAN
Standard and the HIPERLAN Standard. The HIPERLAN Standard operates in the 5 GHz Unlicensed-National Infonnation Infrastructure (U-NII) band and provides a peak air-link speed between ten and one hundred Mbps.
[0004] An ad hoc network is a short-range wireless system comprising an arbitrary collection of wireless devices that are physically close enough to exchange information. An ad hoc network is constructed quickly with wireless devices joining and leaving the network as they enter and leave the proximity of the remaining wireless devices. An ad hoc iietwork also may include one or more access points, that is, stationary wireless devices operating as a stand-alone server or as gateway connections to other networks.
[00051 In the future, the Bluetooth Standard will likely support the interconnection of multiple piconets to form a multi-hop ad hoc network, or scattemet. In a scatternet, a connecting device forwards traffic between different piconets.
The connecting device may serve as a master device in one piconet, but as a slave device or a master device in another piconet. Thus, the connecting devices join the piconets that.
comprise a scatternet by adapting the timing and hop sequence to the respective piconet and possibly changing the roles that they serve from a master device to a slave device.
[00031 Short-range wireless systems have a range of less than one hundred meters, but may connect to the Internet to provide communication over longer distances.
Short-range wireless systems include, but are not limited to, a wireless personal area network (PAN) and a wireless local area network (LAN). A wireless PAN uses low-cost, low-power wireless devices that have a typical range of ten meters. An example of a wireless PAN technology is the Bluetooth Standard. The Bluetooth Standard operates in the 2.4 GHz Industrial, Scientific, and Medical (ISM) band and provides a peak air-link speed of one Mbps and a power consumption low enough for use in personal, portable electronics such as a personal digital assistance or mobile phone. A
description of the Bluetooth communication protocol and device operation principles is in Bluetooth Special Interest Group. Specification of the Bluetooth Standard, version 1.0B, volumes 1 and 2, December 1999. A wireless LAN is more costly than a wireless PAN, but has a longer range. An example of a wireless LAN technology is the IEEE 802.11 Wireless LAN
Standard and the HIPERLAN Standard. The HIPERLAN Standard operates in the 5 GHz Unlicensed-National Infonnation Infrastructure (U-NII) band and provides a peak air-link speed between ten and one hundred Mbps.
[0004] An ad hoc network is a short-range wireless system comprising an arbitrary collection of wireless devices that are physically close enough to exchange information. An ad hoc network is constructed quickly with wireless devices joining and leaving the network as they enter and leave the proximity of the remaining wireless devices. An ad hoc iietwork also may include one or more access points, that is, stationary wireless devices operating as a stand-alone server or as gateway connections to other networks.
[00051 In the future, the Bluetooth Standard will likely support the interconnection of multiple piconets to form a multi-hop ad hoc network, or scattemet. In a scatternet, a connecting device forwards traffic between different piconets.
The connecting device may serve as a master device in one piconet, but as a slave device or a master device in another piconet. Thus, the connecting devices join the piconets that.
comprise a scatternet by adapting the timing and hop sequence to the respective piconet and possibly changing the roles that they serve from a master device to a slave device.
[00061 A Bluetooth device includes, but is not limited to, a mobile telephone, personal or laptop computer, radio-frequency identification tag, and personal electronic device such as a personal digital assistant (PDA), pager, or portable-computing device.
Each Bluetooth device includes application and operating system programs designed to find other Bluetooth devices as they enter and leave the communication range of the network. The requesting Bluetooth device in a client role and the responding Bluetooth device in a server role establish a link between the two devices. The requesting and responding Bluetooth device use the link and a service discovery protocol to discover the services offered by the other Bluetooth device and how to connect to those services.
[0007] Prior art systems follow similar patterns of behavior for service discovery protocols. A service description, created using a description language and an appropriate vocabulary, is advertised or made available for query matching. Some prior art systems advertise the service description by pushing the description to a directory and requiring the advertisers to discover the directory. Other prior art systems advertise the service description by making the descriptions available for peer-to-peer discovery. A
client device that needs to discover the service description composes a query using a query language and a matching vocabulary and uses either a query protocol or a decentralized query-processing server to deliver the query.
[0008] Service discovery protocols in the prior art systems require sending and replying to inquiry messages. If no other device is present, the inquiry messages are sent in vain. To avoid excessive power consumption, the prior art systems typically require a human user to manually initiate device detection when another device of interest is present. For example, a human user manually initiates device detection when connecting a cellular telephone to a laptop computer to handle data communications or when connecting a wireless headset to a laptop computer to deliver digital audio.
These prior art systems rely upon three assumptions. First, an application can be freely started because the presence of its services is guaranteed. Second, an application performs service discovery when it first needs a service. Third, the composition of the network does not change during the lifetime of the application.
[00091 Thus, there is a need for a device detection and service discovery protocol that will avoid excessive power consumption and allow an application resident in one device to automatically find a counterpart application or some other resource resident in any of the remaining devices within the ad hoc communications network. The protocol does not require a human user to manually initiate device detection to find the counterpart application or other resource. Furthermore, the protocol will accommodate a network environment in which the presence of a particular service is not guaranteed and in which the composition of the network is dynamic because devices frequently enter and leave the network. The disclosed invention addresses this need.
SUMMARY OF THE INVENTION
[0010] A computer system, method, and computer program product for performing device detection and service discovery in a mobile ad hoc communications network. The method comprises conducting an inquiry of the inobile ad hoc communications network to discover nearby devices. If the inquiry indicates that the nearby devices may include a middleware layer, the method further comprises creating a connection to each of the nearby devices and confirming whether each of the nearby devices include the middleware layer. For each of the nearby devices that include the middleware layer, the method further comprises executing the middleware layer to perform application and service discovery, and to launch applications and services.
[00111 In one embodiment, the mobile ad hoc communications network is a Bluetooth network. Conducting the inquiry includes sending a Bluetooth inquiry command and receiving a Bluetooth inquiry result command that includes an indication that the device may include the middleware layer. Creating the connection to a device that may include the middleware layer includes sending a Bluetooth paging request message to the device and receiving a Bluetooth paging accept message.
Confirming that the device includes the middleware layer includes sending a recognition request message to the device and receiving a recognition response message. Executing the middleware -layer to perform application and service discovery includes receiving a notification message from a device with a copy of a local application directory, storing an update to a combined application directory based on a comparison of the local and combined application directory, and sending the update to the combined application directory to each device in the Bluetooth network. In addition, executing the middleware layer includes launching a local application based on a reference in the combined application directory, and connecting the local application to a counterpart application executing on the device.
[OO11A] Accordingly, in one aspect of the present invention there is provided an apparatus comprising:
Each Bluetooth device includes application and operating system programs designed to find other Bluetooth devices as they enter and leave the communication range of the network. The requesting Bluetooth device in a client role and the responding Bluetooth device in a server role establish a link between the two devices. The requesting and responding Bluetooth device use the link and a service discovery protocol to discover the services offered by the other Bluetooth device and how to connect to those services.
[0007] Prior art systems follow similar patterns of behavior for service discovery protocols. A service description, created using a description language and an appropriate vocabulary, is advertised or made available for query matching. Some prior art systems advertise the service description by pushing the description to a directory and requiring the advertisers to discover the directory. Other prior art systems advertise the service description by making the descriptions available for peer-to-peer discovery. A
client device that needs to discover the service description composes a query using a query language and a matching vocabulary and uses either a query protocol or a decentralized query-processing server to deliver the query.
[0008] Service discovery protocols in the prior art systems require sending and replying to inquiry messages. If no other device is present, the inquiry messages are sent in vain. To avoid excessive power consumption, the prior art systems typically require a human user to manually initiate device detection when another device of interest is present. For example, a human user manually initiates device detection when connecting a cellular telephone to a laptop computer to handle data communications or when connecting a wireless headset to a laptop computer to deliver digital audio.
These prior art systems rely upon three assumptions. First, an application can be freely started because the presence of its services is guaranteed. Second, an application performs service discovery when it first needs a service. Third, the composition of the network does not change during the lifetime of the application.
[00091 Thus, there is a need for a device detection and service discovery protocol that will avoid excessive power consumption and allow an application resident in one device to automatically find a counterpart application or some other resource resident in any of the remaining devices within the ad hoc communications network. The protocol does not require a human user to manually initiate device detection to find the counterpart application or other resource. Furthermore, the protocol will accommodate a network environment in which the presence of a particular service is not guaranteed and in which the composition of the network is dynamic because devices frequently enter and leave the network. The disclosed invention addresses this need.
SUMMARY OF THE INVENTION
[0010] A computer system, method, and computer program product for performing device detection and service discovery in a mobile ad hoc communications network. The method comprises conducting an inquiry of the inobile ad hoc communications network to discover nearby devices. If the inquiry indicates that the nearby devices may include a middleware layer, the method further comprises creating a connection to each of the nearby devices and confirming whether each of the nearby devices include the middleware layer. For each of the nearby devices that include the middleware layer, the method further comprises executing the middleware layer to perform application and service discovery, and to launch applications and services.
[00111 In one embodiment, the mobile ad hoc communications network is a Bluetooth network. Conducting the inquiry includes sending a Bluetooth inquiry command and receiving a Bluetooth inquiry result command that includes an indication that the device may include the middleware layer. Creating the connection to a device that may include the middleware layer includes sending a Bluetooth paging request message to the device and receiving a Bluetooth paging accept message.
Confirming that the device includes the middleware layer includes sending a recognition request message to the device and receiving a recognition response message. Executing the middleware -layer to perform application and service discovery includes receiving a notification message from a device with a copy of a local application directory, storing an update to a combined application directory based on a comparison of the local and combined application directory, and sending the update to the combined application directory to each device in the Bluetooth network. In addition, executing the middleware layer includes launching a local application based on a reference in the combined application directory, and connecting the local application to a counterpart application executing on the device.
[OO11A] Accordingly, in one aspect of the present invention there is provided an apparatus comprising:
5 a memory device; and a processor disposed in communication with the memory device, the processor configured to:
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middieware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
[OO11B] According to another aspect of the present invention there is provided a method for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
directory, and connecting the local application to a counterpart application executing on the device.
[0011A] Accordingly, in one aspect of the present invention there is provided an apparatus comprising:
5 a memory device; and a processor disposed in communication with the memory device, the processor configured to:
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
[OO11B] According to another aspect of the present invention there is provided a method for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
5a when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnecting communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
creating a wireless short-range communication connection to the discovered nearby device;
confirming whether the discovered nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when the discovered nearby device includes the middleware software layer:
executing the middleware software to perform application and service discovery with said discovered nearby device.
[0011C] According to yet another aspect of the present invention there is provided a system for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
means for conducting an inquiry to discover nearby devices;
means for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
means for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
means for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
means for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and 5b means for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
[0011D] According to still yet another aspect of the present invention there is provided a computer readable medium embodying computer program code for performing device detection and service discovery in a mobile ad hoc communications network, said computer program code comprising:
program code for conducting an inquiry to discover nearby devices;
program code for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
program code for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
program code for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
program code for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and program code for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
5c BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying figures best illustrate the details of the device detection and service discovery system and method for a mobile ad hoc communications network, both as to its structure and operation. Like reference numbers and designations in these figures refer to like elements.
[0013] Figure 1 is a network diagram that illustrates the interaction of the devices that comprise a mobile ad hoc communications network, in accordance with one embodiment of the present invention.
[0014] Figure 2A is a block diagram that illustrates the hardware and software components comprising server 110 shown in Figure 1, in accordance with one embodiment of the present invention.
[0015] Figure 2B is a block diagram that illustrates the hardware and software components comprising terminal 120 shown in Figure 1, in accordance with one embodiment of the present invention.
[0016] Figure 3A is a flow diagram of an embodiment of server 110 performing device detection and service discovery for a mobile ad hoc communications network.
(0017] Figure 3B is a flow diagram of an embodiment of terminal 120 performing device detection and service discovery for a mobile ad hoc communications network.
100181 Figure 4A is an exemplary block diagram of the data flow before a terminal enters a mobile ad hoc communications network.
[0019] Figure 4B shows the exemplary block diagram of Figure 4A after the terminal enters the mobile ad hoc communications network.
[0020] Figure 5 is a flow diagram of an embodiment of a process that illustrates the message flow during establishment of a communication session between terminal X and terminal Y in a mobile ad hoc communications network.
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middieware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
[OO11B] According to another aspect of the present invention there is provided a method for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
directory, and connecting the local application to a counterpart application executing on the device.
[0011A] Accordingly, in one aspect of the present invention there is provided an apparatus comprising:
5 a memory device; and a processor disposed in communication with the memory device, the processor configured to:
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
[OO11B] According to another aspect of the present invention there is provided a method for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
5a when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnecting communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
creating a wireless short-range communication connection to the discovered nearby device;
confirming whether the discovered nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when the discovered nearby device includes the middleware software layer:
executing the middleware software to perform application and service discovery with said discovered nearby device.
[0011C] According to yet another aspect of the present invention there is provided a system for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
means for conducting an inquiry to discover nearby devices;
means for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
means for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
means for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
means for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and 5b means for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
[0011D] According to still yet another aspect of the present invention there is provided a computer readable medium embodying computer program code for performing device detection and service discovery in a mobile ad hoc communications network, said computer program code comprising:
program code for conducting an inquiry to discover nearby devices;
program code for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
program code for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
program code for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
program code for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and program code for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
5c BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying figures best illustrate the details of the device detection and service discovery system and method for a mobile ad hoc communications network, both as to its structure and operation. Like reference numbers and designations in these figures refer to like elements.
[0013] Figure 1 is a network diagram that illustrates the interaction of the devices that comprise a mobile ad hoc communications network, in accordance with one embodiment of the present invention.
[0014] Figure 2A is a block diagram that illustrates the hardware and software components comprising server 110 shown in Figure 1, in accordance with one embodiment of the present invention.
[0015] Figure 2B is a block diagram that illustrates the hardware and software components comprising terminal 120 shown in Figure 1, in accordance with one embodiment of the present invention.
[0016] Figure 3A is a flow diagram of an embodiment of server 110 performing device detection and service discovery for a mobile ad hoc communications network.
(0017] Figure 3B is a flow diagram of an embodiment of terminal 120 performing device detection and service discovery for a mobile ad hoc communications network.
100181 Figure 4A is an exemplary block diagram of the data flow before a terminal enters a mobile ad hoc communications network.
[0019] Figure 4B shows the exemplary block diagram of Figure 4A after the terminal enters the mobile ad hoc communications network.
[0020] Figure 5 is a flow diagram of an embodiment of a process that illustrates the message flow during establishment of a communication session between terminal X and terminal Y in a mobile ad hoc communications network.
DETAILED DESCRIPTION OF THE INVENTION
100211 Figure 1 is a network diagram that illustrates the interaction of the devices that comprise a mobile ad hoc communications network, in accordance with one embodiment of the present invention. In one embodiment, the mobile ad hoc communications network is a Bluetooth piconet that includes one master device and up to seven active slave devices. As shown in Figure 1, piconet 100 includes server 110 and five instances of terminal 120. Server 110 maintains the network clock and is the communication manager for each instance of terminal 120. Server 110 typically initiates an exchange of data with an instance of terminal 120. Two instances of terminal 120 typically communicate through the server 110 however, if two instances of terminal 120 communicate directly, one instance will assume the role of server, or master, and the other instance will assume the role of client, or slave.
[0022] Each device in the mobile ad hoc communications network will either assume the role of a terminal device or a server device. A terminal device is a consumer of services that a single user operates. A terminal device includes devices such as a mobile phone or PDA. A server is typically a stationary device and only produces services. A server device creates a hotspot around them for using their services.
"Hotspot" refers to the radio coverage area provided by the server device for detecting devices and discovering services offered by the applications hosted in the server. If the server device is not stationary, one of the terminal devices in the network will assume the role of application directory server and perform device detection and service discovery functions for the remaining terminal devices in the network. The disclosed invention introduces two roles among such terminal devices, application directory servers and terminals, where application directory servers serve terminals in device detection and service discovery. If stationary servers with hotspots exist, servers typically act as application directory servers however, device detection and service discovery is possible without such a stationary server because one of the terminals will assume the application directory server duties.
[0023] The disclosed invention categorizes an application as a server-based application, terminal-to-terminal application, foreground application, background application, or generic application component. A server-based application requires a server to produce a service. A terminal-to-terminal application requires at least two terminal devices to implement a service without the presence of a server device. A
foreground application is an application resident in a terminal device that a user accesses via the user interface of the terminal device. A background application is an application resident in a terminal device that may start without any intervention by the user. A
generic application component can be used either as a standalone application or as a component of another application.
[0024) An application may be further categorized as either active, passive, new, or rejected. An active application is a foreground or background application that is resident in (i.e., stored in memory) the terminal. A passive application is resident in the terminal, but has not yet been started. In another embodiment, the passive application is started, but is not actively looking for other instances of the same application. A new application is not yet resident in the terminal, but might be in the future. A rejected application is not resident in the terminal and has been marked by the user as an application that should never be resident in the terininal. In another embodiment, the rejected application was once resident in the terminal, but was subsequently deleted and marked as rejected. In yet another embodiment, the rejected application never resided in the terminal, but is of a type of application that the user has marked as rejected.
[00251 Service discovery in a mobile ad hoc communications network differentiates between a resident application and an unloaded application. A
resident application is stored in the tenninal memory and loaded as either a foreground application or a background application. An unloaded application is not yet stored or loaded in the terminal, but has been accepted by the user. Typically, when an application was previously used, but has been overwritten to reclaim space, the application is considered unloaded. Thus, starting an unloaded application may require first downloading the application.
[00261 Service discovery ftom the perspective of the te.rniinal device requires categorizing the status of an application as either an active resident application, active unloaded application, passive resident application, passive unloaded application, rejected application, or new application. An active resident application is loaded in the terminal-and looking for peers, servers, or clients. An active unloaded application is not loaded in the terminal, but is still looking for such counterpart applications that could be automatically downloaded if found interesting. A passive resident application is loaded in the terminal, but is not looking for counterpart applications. A passive unloaded application is not loaded in the terminal, but was once accepted by the user.
A rejected application is an application that a user has requested to exclude from the terminal device.
A new application is not loaded in the terminal device, but the user might have seen an application in an earlier server for instance.
[0027] Figure 2A is a block diagram that illustrates the hardware and software components comprising server 110 shown in Figure 1, in accordance with one embodiment of the present invention. Server 110 is a general-purpose wireless device., Bus 200 is a communication medium that connects keypad 201, display 202, central processing unit (CPU) 203, and radio frequency (RF) adapter 204 to memory 210.
RF
adapter 204 connects via a wireless link to terminal 120 and is the mechanism that facilitates network traffic between server 110 and termina1120.
100281 CPU 203 performs the methods of the disclosed invention by executing the sequences of operational instructions that comprise each computer program resident in, or operative on, memory 210. Memory 210 includes operating system software 211, application programs 212, and middleware software 220. Operating system software 211 controls keypad 201, display 202, RF adapter 204, and the management of memory 210.
Application programs 212 control the interactions between a user and server 110.
Middleware software 220 includes an application program interface (API) 221 that help an application program running on server 110 find and communicate with a counterpart application running on terminal 120. To quickly locate each application, middleware software 220 also includes application directory 230 to track the role assumed by each application that is resident in each device in piconet 100.
[00291 Figure 2B is a block diagram that illustrates the hardware and software components comprising terminal 120 shown in Figure 1, in accordance with one embodiment of the present invention. Termina1120 is a general-purpose wireless device.
Bus 250 is a communication medium that connects keypad 251, display 252, CPU
253, and RF adapter 254 to memory 260. RF adapter 254 connects via a wireless link to server.
100211 Figure 1 is a network diagram that illustrates the interaction of the devices that comprise a mobile ad hoc communications network, in accordance with one embodiment of the present invention. In one embodiment, the mobile ad hoc communications network is a Bluetooth piconet that includes one master device and up to seven active slave devices. As shown in Figure 1, piconet 100 includes server 110 and five instances of terminal 120. Server 110 maintains the network clock and is the communication manager for each instance of terminal 120. Server 110 typically initiates an exchange of data with an instance of terminal 120. Two instances of terminal 120 typically communicate through the server 110 however, if two instances of terminal 120 communicate directly, one instance will assume the role of server, or master, and the other instance will assume the role of client, or slave.
[0022] Each device in the mobile ad hoc communications network will either assume the role of a terminal device or a server device. A terminal device is a consumer of services that a single user operates. A terminal device includes devices such as a mobile phone or PDA. A server is typically a stationary device and only produces services. A server device creates a hotspot around them for using their services.
"Hotspot" refers to the radio coverage area provided by the server device for detecting devices and discovering services offered by the applications hosted in the server. If the server device is not stationary, one of the terminal devices in the network will assume the role of application directory server and perform device detection and service discovery functions for the remaining terminal devices in the network. The disclosed invention introduces two roles among such terminal devices, application directory servers and terminals, where application directory servers serve terminals in device detection and service discovery. If stationary servers with hotspots exist, servers typically act as application directory servers however, device detection and service discovery is possible without such a stationary server because one of the terminals will assume the application directory server duties.
[0023] The disclosed invention categorizes an application as a server-based application, terminal-to-terminal application, foreground application, background application, or generic application component. A server-based application requires a server to produce a service. A terminal-to-terminal application requires at least two terminal devices to implement a service without the presence of a server device. A
foreground application is an application resident in a terminal device that a user accesses via the user interface of the terminal device. A background application is an application resident in a terminal device that may start without any intervention by the user. A
generic application component can be used either as a standalone application or as a component of another application.
[0024) An application may be further categorized as either active, passive, new, or rejected. An active application is a foreground or background application that is resident in (i.e., stored in memory) the terminal. A passive application is resident in the terminal, but has not yet been started. In another embodiment, the passive application is started, but is not actively looking for other instances of the same application. A new application is not yet resident in the terminal, but might be in the future. A rejected application is not resident in the terminal and has been marked by the user as an application that should never be resident in the terininal. In another embodiment, the rejected application was once resident in the terminal, but was subsequently deleted and marked as rejected. In yet another embodiment, the rejected application never resided in the terminal, but is of a type of application that the user has marked as rejected.
[00251 Service discovery in a mobile ad hoc communications network differentiates between a resident application and an unloaded application. A
resident application is stored in the tenninal memory and loaded as either a foreground application or a background application. An unloaded application is not yet stored or loaded in the terminal, but has been accepted by the user. Typically, when an application was previously used, but has been overwritten to reclaim space, the application is considered unloaded. Thus, starting an unloaded application may require first downloading the application.
[00261 Service discovery ftom the perspective of the te.rniinal device requires categorizing the status of an application as either an active resident application, active unloaded application, passive resident application, passive unloaded application, rejected application, or new application. An active resident application is loaded in the terminal-and looking for peers, servers, or clients. An active unloaded application is not loaded in the terminal, but is still looking for such counterpart applications that could be automatically downloaded if found interesting. A passive resident application is loaded in the terminal, but is not looking for counterpart applications. A passive unloaded application is not loaded in the terminal, but was once accepted by the user.
A rejected application is an application that a user has requested to exclude from the terminal device.
A new application is not loaded in the terminal device, but the user might have seen an application in an earlier server for instance.
[0027] Figure 2A is a block diagram that illustrates the hardware and software components comprising server 110 shown in Figure 1, in accordance with one embodiment of the present invention. Server 110 is a general-purpose wireless device., Bus 200 is a communication medium that connects keypad 201, display 202, central processing unit (CPU) 203, and radio frequency (RF) adapter 204 to memory 210.
RF
adapter 204 connects via a wireless link to terminal 120 and is the mechanism that facilitates network traffic between server 110 and termina1120.
100281 CPU 203 performs the methods of the disclosed invention by executing the sequences of operational instructions that comprise each computer program resident in, or operative on, memory 210. Memory 210 includes operating system software 211, application programs 212, and middleware software 220. Operating system software 211 controls keypad 201, display 202, RF adapter 204, and the management of memory 210.
Application programs 212 control the interactions between a user and server 110.
Middleware software 220 includes an application program interface (API) 221 that help an application program running on server 110 find and communicate with a counterpart application running on terminal 120. To quickly locate each application, middleware software 220 also includes application directory 230 to track the role assumed by each application that is resident in each device in piconet 100.
[00291 Figure 2B is a block diagram that illustrates the hardware and software components comprising terminal 120 shown in Figure 1, in accordance with one embodiment of the present invention. Termina1120 is a general-purpose wireless device.
Bus 250 is a communication medium that connects keypad 251, display 252, CPU
253, and RF adapter 254 to memory 260. RF adapter 254 connects via a wireless link to server.
110 or another terminal 120 and is the mechanism that facilitates network traffic between server 110 and terminal 120.
[00301 CPU 253 performs the methods of the disclosed invention by executing the sequences of operational instructions that comprise each computer program resident in, or operative on, memory 260. Memory 260 includes operating system software 261, application programs 262, and rniddleware software 270. Operating system software 261 controls keypad 251, display 252, RF adapter 254, and the management of memory 260.
Application programs 262 control the interactions between a user and terminal 120.
Middleware software 270 includes an API 271 that help an application program running on terminal 120 find and communicate with a counterpart application running on server 110 or another terminal 120. To quiclcly locate each application, middleware software 270 also includes application directory 280 to track the role assumed by each application that is resident in each device in piconet 100.
100311 In one embodiment, the configuration of memory 210 and memory 260 is identical. In another embodiment, the configuration of memory 210 and memory 260.
only includes the software necessary to perform the essential tasks of server 110 and terminal 120, respectively. For example, if terminal 120 needs to receive a general inquiry access code, but does not need to send a general inquiry access code message, only the software that receives this message will reside in memory 260.
[00321 An application executing on a ternainal is constantly searching for a counterpart application, that is, another instance of the same application that can communicate with the application. Each instance of an application assumes a particular role. Communication between an application and a counterpart application is only meaningful if the roles are complementary. For example, an application that assumes the role of "client" can communicate with a counterpart application that assumes the role of, "server". Middleware software is a software layer with an API that negotiates the communication between two applications to help an application find a counterpart application with the correct role. Thus, an application installed in a terminal and activated, will query the API for a continuous stream of new counterpart applications that are of interest.
[00331 A new application is installed by "installer" applications that use middleware for finding counterparts and installing the new application into the local storage of a terminal. The actual finding and selection of new applications takes place in the application level. Initially, the installer application will be a dedicated "browser-5 supplier" (i.e., client-server) application that accesses counterpart applications in servers, browses their available application databases, allows a user to pick the applications to install, and downloads and installs the new applications. Later, the corresponding functionality may be added to a wireless access protocol (WAP) and hypertext markup language (HTML) browsers.
[00301 CPU 253 performs the methods of the disclosed invention by executing the sequences of operational instructions that comprise each computer program resident in, or operative on, memory 260. Memory 260 includes operating system software 261, application programs 262, and rniddleware software 270. Operating system software 261 controls keypad 251, display 252, RF adapter 254, and the management of memory 260.
Application programs 262 control the interactions between a user and terminal 120.
Middleware software 270 includes an API 271 that help an application program running on terminal 120 find and communicate with a counterpart application running on server 110 or another terminal 120. To quiclcly locate each application, middleware software 270 also includes application directory 280 to track the role assumed by each application that is resident in each device in piconet 100.
100311 In one embodiment, the configuration of memory 210 and memory 260 is identical. In another embodiment, the configuration of memory 210 and memory 260.
only includes the software necessary to perform the essential tasks of server 110 and terminal 120, respectively. For example, if terminal 120 needs to receive a general inquiry access code, but does not need to send a general inquiry access code message, only the software that receives this message will reside in memory 260.
[00321 An application executing on a ternainal is constantly searching for a counterpart application, that is, another instance of the same application that can communicate with the application. Each instance of an application assumes a particular role. Communication between an application and a counterpart application is only meaningful if the roles are complementary. For example, an application that assumes the role of "client" can communicate with a counterpart application that assumes the role of, "server". Middleware software is a software layer with an API that negotiates the communication between two applications to help an application find a counterpart application with the correct role. Thus, an application installed in a terminal and activated, will query the API for a continuous stream of new counterpart applications that are of interest.
[00331 A new application is installed by "installer" applications that use middleware for finding counterparts and installing the new application into the local storage of a terminal. The actual finding and selection of new applications takes place in the application level. Initially, the installer application will be a dedicated "browser-5 supplier" (i.e., client-server) application that accesses counterpart applications in servers, browses their available application databases, allows a user to pick the applications to install, and downloads and installs the new applications. Later, the corresponding functionality may be added to a wireless access protocol (WAP) and hypertext markup language (HTML) browsers.
10 [00341 Service discovery is viewed as a three-step process. First, new potential applications are found and will be considered for installation. Second, active installed applications begin to search for counterpart application. Third, active installed applications begin searching for common resources such as printers (i.e., resource discovery). The disclosed invention relies upon the applications to perform resource discovery. Typically, a terminal application communicates with its counterpart application and use local (i.e., server) resources. If an application uses a private resource, the associated service discovery is implemented by the application in a standard (e.g., Bluetooth or Bluetooth/Java) way not supported by the terminal middleware software.
[0035] Figure 3A is a flow diagram of an embodiment of server 110 performing device detection and service discovery for a mobile ad hoc communications network.
The process begins when server 110 sends a general inquiry access code message to terminal 120 (step 300). Terminal 120 receives the message and sends an acknowledgment response message to server 110 (step 302). Server 110 accesses middleware software 220 to request a socket connection with terminal 120 (step 304). In response to establishing the socket connection, server 110 receives a message from terminal 120 that includes a local application directory listing all of the applications that are locally resident on terminal 110 (step 306). Server 110 compares the list of applications resident on terminal 120 to a combined application directory resident on server 110. Server 110 updates the combined application directory by adding to the combined application directory each entry in the local application directory that does not appear in the combined application directory (step 308). Server 110 sends a portion of the updated combined application directory to each terminal 120 in piconet 100 (step 310). The portion may vary for each terminal 120 and includes each entry in the combined application directory that is a counterpart application to an application resident in terminal 120. In another embodiment, server 110 sends the entire combined application directory to each tenninal 120 in piconet 100 and relies upon terminal 120 to retain the pertinent entries. Instances of middleware software in terminal 120 and server 110 begin to schedule the newly found counterpart application pairs for execution (step 312). In one embodiment, the scheduled applications make use of any other Bluetooth profile and protocol. In another embodiment, an application that is an installer application may suggest to the user other applications that the user should download.
Once server 110 downloads and starts a new application, counterpart matching repeats and the new application becomes a part of the middleware scheduling.
[00361 Figure 3B is a flow diagram of an embodiment of terminal 120 performing device detection and service discovery for a mobile ad hoc coinmunications network.
The process begins when terminal 120 receives a general inquiry access code message from server 110 (step 320). Terminal 120 generates and sends an acknowledgment response message to server 110 (step 322). Terminal 120 sends a message to server 110-that includes a local application directory that includes all of the applications that are locally resident on terminal 110 (step 324). Server 110 compares the list of applications resident on terminal 120 to a combined application directory resident on server 110.
Server 110 updates the combined application directory by adding to the combined application directory each entry in the local application directory that does not appear in the combined application directory. Terminal 120 receives from server 110 a portion of the updated combined application directory (step 326). Server 110 customizes the portion for terminal 120 to include each entry in the combined application directory that is a counterpart application to an application resident in terminal 120. In another embodiment, server 110 sends the entire combined application directory to terminal 120 and relies on terminal 120 to retain the pertinent entries. Instances of middleware software in terminal 120 and server 110 begin scheduling these newly found counterpart application pairs for execution (step 328).
100371 Figures 4A and 4B are exemplary block diagrams showing the content of the application directory before and after terminal X and terminal Y enter a mobile ad hoc.
communications network served by server S. Figure 4A shows the configuration of application directory 404, application directory 415, and application directory 425 before terminal X and terminal Y enter a communication network managed by server S, a master device. Application C 401 resides in server S memory 400 and accesses middleware software 403 via API 402. Middleware software 403 registers application C 401 with application directory 404 by adding a table entry to indicate that application C resides in the local device (i.e., server S) and assumes the role of server. Application A 411 and application B 412 reside in terminal X memory 410 and access middleware software 414 via API 413. Middleware software 414 registers application A 411 and application B 412 with application directory 415 by adding a table entry to indicate that application A
resides in the local device (i.e., terminal X) and assumes the role of client and that application B resides in the local device (i.e., terminal X) and assumes the role of peer.
Application B 421 and application C 422 reside in terminal Y memory 420 and access' middleware software 424 via API 423. Middleware software 424 registers application B
421 and application C 422 with application directory 425 by adding a table entry to indicate that application B resides in the local device (i.e., terminal Y) and assumes the role of peer and that application C resides in the local device (i.e., terminal Y) and assumes the role of client.
[00381 Figure 4B shows the configuration of application directory 404, application directory 415, and application directory 425 after terminal X and terminal Y
enter the communication network managed by server S, a master device. Server S
assunles the role of an application directory server (ADS) and mediates the registration of the applications residing in each device in piconet 100. Server S adds a table entry to"
application directory 404 for each application residing in a device on piconet 100. Thus, server S adds an entry for application A residing in terminal X in a client role, application B residing in terminal X in a peer role, application B residing in terminal Y
in a peer role, and application C residing in terminal Y in a client role. Server S also updates application directory 415 in terminal X and application directory 425 in terminal Y with application registrations that may be interesting to those terminal devices.
As shown in Figure 4B, terminal X and terminal Y both host application B in a peer role.
Since, a peer-to-peer communication session between application B on terminal X and application B on terminal Y is likely, server S adds an entry to application directory 415 for application B residing in terminal Y in a peer role and an entry to application directory 425 for application B residing in terminal X in a peer role. Also, since a client-server communication session between application C on terniinal Y and application C
on server S is likely, server S adds an entry to application directory 425 for application C residing in server S in a server role. Finally, there is no counterpart in piconet 100 for application A on terminal X.
[00391 As shown in Figures 4A and 4B, the disclosed data items for each entry in the middleware software application directory server include a device identifier (e.g., "local", an address, or other unique identifier), an application identifier (e.g., application name or other unique identifier), and a role for the application (e.g., "client", "server", "peer", etc.). In another embodiment, the data items can be expanded to include fields for the local applications (i.e., device = "local") and fields for remote applications in other terminals or servers. The fields for the local applications include:
= Name - An identifier for the application (e.g., supplier name and data to compare different versions and hardware variants);
= Myrole - The role that the application takes in the local device;
= Partner role - The role that the application assumes from interesting counterparts (e.g., peer, client, and server are the most common roles);
= Residency - Either RESIDENT (installed and currently in memory), UNLOADED (installed once, not currently in memory, but can be re-downloaded automatically), REJECTED (indicates to the new application installer that it should ignore the application), or NEW (the application is not installed or rejected);
= State - Either RUNNING (has communications, is now working with its remote counterparts, but there may be either only one, or more, applications that can use the communications at a time), WAITING (in execution but does not have any communications), STARTABLE (active, if a matching peer with the right partner role is found, the middleware software starts this application, downloading the software first if needed), COMPLETE (all counterpart applications are aware), or PASSIVE (user must do something to start application);
[0035] Figure 3A is a flow diagram of an embodiment of server 110 performing device detection and service discovery for a mobile ad hoc communications network.
The process begins when server 110 sends a general inquiry access code message to terminal 120 (step 300). Terminal 120 receives the message and sends an acknowledgment response message to server 110 (step 302). Server 110 accesses middleware software 220 to request a socket connection with terminal 120 (step 304). In response to establishing the socket connection, server 110 receives a message from terminal 120 that includes a local application directory listing all of the applications that are locally resident on terminal 110 (step 306). Server 110 compares the list of applications resident on terminal 120 to a combined application directory resident on server 110. Server 110 updates the combined application directory by adding to the combined application directory each entry in the local application directory that does not appear in the combined application directory (step 308). Server 110 sends a portion of the updated combined application directory to each terminal 120 in piconet 100 (step 310). The portion may vary for each terminal 120 and includes each entry in the combined application directory that is a counterpart application to an application resident in terminal 120. In another embodiment, server 110 sends the entire combined application directory to each tenninal 120 in piconet 100 and relies upon terminal 120 to retain the pertinent entries. Instances of middleware software in terminal 120 and server 110 begin to schedule the newly found counterpart application pairs for execution (step 312). In one embodiment, the scheduled applications make use of any other Bluetooth profile and protocol. In another embodiment, an application that is an installer application may suggest to the user other applications that the user should download.
Once server 110 downloads and starts a new application, counterpart matching repeats and the new application becomes a part of the middleware scheduling.
[00361 Figure 3B is a flow diagram of an embodiment of terminal 120 performing device detection and service discovery for a mobile ad hoc coinmunications network.
The process begins when terminal 120 receives a general inquiry access code message from server 110 (step 320). Terminal 120 generates and sends an acknowledgment response message to server 110 (step 322). Terminal 120 sends a message to server 110-that includes a local application directory that includes all of the applications that are locally resident on terminal 110 (step 324). Server 110 compares the list of applications resident on terminal 120 to a combined application directory resident on server 110.
Server 110 updates the combined application directory by adding to the combined application directory each entry in the local application directory that does not appear in the combined application directory. Terminal 120 receives from server 110 a portion of the updated combined application directory (step 326). Server 110 customizes the portion for terminal 120 to include each entry in the combined application directory that is a counterpart application to an application resident in terminal 120. In another embodiment, server 110 sends the entire combined application directory to terminal 120 and relies on terminal 120 to retain the pertinent entries. Instances of middleware software in terminal 120 and server 110 begin scheduling these newly found counterpart application pairs for execution (step 328).
100371 Figures 4A and 4B are exemplary block diagrams showing the content of the application directory before and after terminal X and terminal Y enter a mobile ad hoc.
communications network served by server S. Figure 4A shows the configuration of application directory 404, application directory 415, and application directory 425 before terminal X and terminal Y enter a communication network managed by server S, a master device. Application C 401 resides in server S memory 400 and accesses middleware software 403 via API 402. Middleware software 403 registers application C 401 with application directory 404 by adding a table entry to indicate that application C resides in the local device (i.e., server S) and assumes the role of server. Application A 411 and application B 412 reside in terminal X memory 410 and access middleware software 414 via API 413. Middleware software 414 registers application A 411 and application B 412 with application directory 415 by adding a table entry to indicate that application A
resides in the local device (i.e., terminal X) and assumes the role of client and that application B resides in the local device (i.e., terminal X) and assumes the role of peer.
Application B 421 and application C 422 reside in terminal Y memory 420 and access' middleware software 424 via API 423. Middleware software 424 registers application B
421 and application C 422 with application directory 425 by adding a table entry to indicate that application B resides in the local device (i.e., terminal Y) and assumes the role of peer and that application C resides in the local device (i.e., terminal Y) and assumes the role of client.
[00381 Figure 4B shows the configuration of application directory 404, application directory 415, and application directory 425 after terminal X and terminal Y
enter the communication network managed by server S, a master device. Server S
assunles the role of an application directory server (ADS) and mediates the registration of the applications residing in each device in piconet 100. Server S adds a table entry to"
application directory 404 for each application residing in a device on piconet 100. Thus, server S adds an entry for application A residing in terminal X in a client role, application B residing in terminal X in a peer role, application B residing in terminal Y
in a peer role, and application C residing in terminal Y in a client role. Server S also updates application directory 415 in terminal X and application directory 425 in terminal Y with application registrations that may be interesting to those terminal devices.
As shown in Figure 4B, terminal X and terminal Y both host application B in a peer role.
Since, a peer-to-peer communication session between application B on terminal X and application B on terminal Y is likely, server S adds an entry to application directory 415 for application B residing in terminal Y in a peer role and an entry to application directory 425 for application B residing in terminal X in a peer role. Also, since a client-server communication session between application C on terniinal Y and application C
on server S is likely, server S adds an entry to application directory 425 for application C residing in server S in a server role. Finally, there is no counterpart in piconet 100 for application A on terminal X.
[00391 As shown in Figures 4A and 4B, the disclosed data items for each entry in the middleware software application directory server include a device identifier (e.g., "local", an address, or other unique identifier), an application identifier (e.g., application name or other unique identifier), and a role for the application (e.g., "client", "server", "peer", etc.). In another embodiment, the data items can be expanded to include fields for the local applications (i.e., device = "local") and fields for remote applications in other terminals or servers. The fields for the local applications include:
= Name - An identifier for the application (e.g., supplier name and data to compare different versions and hardware variants);
= Myrole - The role that the application takes in the local device;
= Partner role - The role that the application assumes from interesting counterparts (e.g., peer, client, and server are the most common roles);
= Residency - Either RESIDENT (installed and currently in memory), UNLOADED (installed once, not currently in memory, but can be re-downloaded automatically), REJECTED (indicates to the new application installer that it should ignore the application), or NEW (the application is not installed or rejected);
= State - Either RUNNING (has communications, is now working with its remote counterparts, but there may be either only one, or more, applications that can use the communications at a time), WAITING (in execution but does not have any communications), STARTABLE (active, if a matching peer with the right partner role is found, the middleware software starts this application, downloading the software first if needed), COMPLETE (all counterpart applications are aware), or PASSIVE (user must do something to start application);
= Type - Either FOREGOUND (when the application terminates, the state will be PASSIVE), or BACKGROUND (if the application terminates, the state will be STARTABLE);
= Unload - Either AUTOMATIC (middleware may remove code when the application has terminated), or UNINSTALL (user must confirm removals);
= Icon - Creates a visual image of the application for the user; and = Timeout - Sets a time limit that the middleware software uses to detect, for example, when the application is in an unproductive software loop.
[00401 The fields for the remote applications include:
= Device - An address for establishing communications with the terminal or server storing the application instance;
= Name - An identifier for the application; and = My role - The role that the application takes in the remote device.
[00411 The client-server roles of the applications are independent of the roles of the devices as a terminal device and an application directory server.
Typically, the device acting as an application directory server hosts applications acting in a server role and the terminal devices act in the client role for the same application. In another embodiment, two terminal devices each send a general inquiry access code message and listen for a reply. The terminal device that receives a response first will assume the server role and proceed according to the procedure in Figure 3A. Another terminal device that receives the inquiry message will assume the tenninal role, and proceed according to Figure 3B.
Thus, the disclosed invention supports terminal-to-term.inal scenarios (e.g., one of identical handheld devices automatically becoming an ADS) and does not require predetermined application directory servers.
[0042] Figure 5 is a flow diagram of an embodiment of a process that illustrates the message flow during establishment of a communication session between terminal X
and terminal Y in a mobile ad hoc communications network. In one embodiment, terminal X and terminal Y are mobile devices such as terminal 120 shown in Figure 1 and Figure 2B. In another embodiment, terininal X is a mobile device such as terminal 120 shown in Figure 1 and Figure 2B and terminal Y is a mobile device such as server 110 shown in Figure 1 and Figure 2A.
[00431 As shown in Figure 5, terminal X initiates the communication by sending an inquiry request message to the mobile ad hoc communications network. Since terminal Y is a nearby device, terminal Y receives the inquiry request message and sends an inquiry response message to terminal X. In one embodiment, the inquiry request 5 message is a Bluetooth inquiry command and the inquiry response message is a Bluetooth inquiry result command. In another embodiment, the inquiry request message is a Bluetooth inquiry command and the inquiry response message is a Bluetooth inquiry result command modified to indicate that the terminal sending the Bluetooth inquiry result command includes a middleware layer. In one embodiment, the middleware layer 10 includes dedicated middleware software providing advanced application and service discovery and execution. In one embodiment, the modification to the Bluetooth inquiry result command is to the Class of Device (CoD) parameters. For example, if the terminal sending the Bluetooth inquiry result command includes the middleware layer, the terminal will set at least the "ad hoc networking aware" bit (bit 16) to on (1).
= Unload - Either AUTOMATIC (middleware may remove code when the application has terminated), or UNINSTALL (user must confirm removals);
= Icon - Creates a visual image of the application for the user; and = Timeout - Sets a time limit that the middleware software uses to detect, for example, when the application is in an unproductive software loop.
[00401 The fields for the remote applications include:
= Device - An address for establishing communications with the terminal or server storing the application instance;
= Name - An identifier for the application; and = My role - The role that the application takes in the remote device.
[00411 The client-server roles of the applications are independent of the roles of the devices as a terminal device and an application directory server.
Typically, the device acting as an application directory server hosts applications acting in a server role and the terminal devices act in the client role for the same application. In another embodiment, two terminal devices each send a general inquiry access code message and listen for a reply. The terminal device that receives a response first will assume the server role and proceed according to the procedure in Figure 3A. Another terminal device that receives the inquiry message will assume the tenninal role, and proceed according to Figure 3B.
Thus, the disclosed invention supports terminal-to-term.inal scenarios (e.g., one of identical handheld devices automatically becoming an ADS) and does not require predetermined application directory servers.
[0042] Figure 5 is a flow diagram of an embodiment of a process that illustrates the message flow during establishment of a communication session between terminal X
and terminal Y in a mobile ad hoc communications network. In one embodiment, terminal X and terminal Y are mobile devices such as terminal 120 shown in Figure 1 and Figure 2B. In another embodiment, terininal X is a mobile device such as terminal 120 shown in Figure 1 and Figure 2B and terminal Y is a mobile device such as server 110 shown in Figure 1 and Figure 2A.
[00431 As shown in Figure 5, terminal X initiates the communication by sending an inquiry request message to the mobile ad hoc communications network. Since terminal Y is a nearby device, terminal Y receives the inquiry request message and sends an inquiry response message to terminal X. In one embodiment, the inquiry request 5 message is a Bluetooth inquiry command and the inquiry response message is a Bluetooth inquiry result command. In another embodiment, the inquiry request message is a Bluetooth inquiry command and the inquiry response message is a Bluetooth inquiry result command modified to indicate that the terminal sending the Bluetooth inquiry result command includes a middleware layer. In one embodiment, the middleware layer 10 includes dedicated middleware software providing advanced application and service discovery and execution. In one embodiment, the modification to the Bluetooth inquiry result command is to the Class of Device (CoD) parameters. For example, if the terminal sending the Bluetooth inquiry result command includes the middleware layer, the terminal will set at least the "ad hoc networking aware" bit (bit 16) to on (1).
15 Alternatively, if the terminal sending the Bluetooth inquiry result command includes the middleware layer, the terminal will set the "ad hoc networking aware" bit (bit 16) to on (1), and the "location info" bit (bit 17) to off (0). Alternatively, if the terminal sending the Bluetooth inquiry result command includes the middleware layer, the terminal will set.
the "ad hoc networlcing aware" bit (bit 16) to on (1), and the "telephony capable" bit (bit 22) to on (1). Alternatively, if the tenninal sending the Bluetooth inquiry result coinmand includes the middleware layer, the terminal will set the "ad hoc networking aware" bit (bit 16) to on (1), the "location info" bit (bit 17) to off (0), and the "telephony capable" bit (bit 22) to on (1). In yet another einbodiment, the modification to the Bluetooth inquiry result command is not necessary, if a dedicated indication parameter to indicate the presence of the middleware software is introduced to the Bluetooth inquiry result command specifications.
[00441 Following the inquiry, as shown in Figure 5, terminal X may create a connection to each nearby device indicating possible possession of the middleware layer by the inquiry response message, such as terminal Y, by sending a paging request message. If terminal Y does not indicate possible possession of the middleware layer (e.g., by setting the "ad-hoc networking aware" bit (bit 16) to off (0)), no paging request message is transmitted and the communication session is disconnected. After conducting an inquiry including an indication that terminal Y possibly includes a middleware layer, terminal X sends the paging message request, as discussed above. Terminal Y
receives the paging request message and optionally sends a paging accept message to accept the connection request. In one embodiment, the paging request message is a Bluetooth create connection coinmand and the paging accept message is a Bluetooth accept connection request command.
[00451 Following the connection to each nearby device, as shown in Figure 5, terminal X sends a recognition request message to confirm whether a nearby device such as terminal Y definitely includes the middleware layer. Terminal Y receives the recognition request message and sends a recognition response message to terminal X. In one embodiment, the receipt of the recognition response message is confirmation that terminal Y includes the middleware layer. In another embodiment, the content of the recognition response message will indicate whether terminal Y includes the middleware layer. In one embodiment, the recognition request message atid the recognition response message utilize the Bluetooth Service Discovery Protocol (SDP). If terminal Y
does not include the middleware layer, the communication session may be disconnected.
[00461 Following the confirmation that a nearby device such as terminal Y
includes the middleware layer, as shown in Figure 5, terminal X and terminal Y
use the middleware layer to discover and launch applications and services. In one embodiment, terminal X and terminal Y use the methods disclosed in the flow diagrams shown in Figure 3A and Figure 3B to discover and launch applications and services.
[0047] Although the, disclosed embodiments describe a fully functioning device detection and service discovery system and method for a mobile ad hoc communications network, the reader should understand that other equivalent embodiments exist.
Since numerous modifications and variations will occur to those who review this disclosure, the device detection and service discovery system and method for a mobile ad hoc communications network is not limited to the exact construction and operation illustrated and disclosed. Accordingly, this disclosure intends all suitable modifications and equivalents to fall within the scope of the claims.
the "ad hoc networlcing aware" bit (bit 16) to on (1), and the "telephony capable" bit (bit 22) to on (1). Alternatively, if the tenninal sending the Bluetooth inquiry result coinmand includes the middleware layer, the terminal will set the "ad hoc networking aware" bit (bit 16) to on (1), the "location info" bit (bit 17) to off (0), and the "telephony capable" bit (bit 22) to on (1). In yet another einbodiment, the modification to the Bluetooth inquiry result command is not necessary, if a dedicated indication parameter to indicate the presence of the middleware software is introduced to the Bluetooth inquiry result command specifications.
[00441 Following the inquiry, as shown in Figure 5, terminal X may create a connection to each nearby device indicating possible possession of the middleware layer by the inquiry response message, such as terminal Y, by sending a paging request message. If terminal Y does not indicate possible possession of the middleware layer (e.g., by setting the "ad-hoc networking aware" bit (bit 16) to off (0)), no paging request message is transmitted and the communication session is disconnected. After conducting an inquiry including an indication that terminal Y possibly includes a middleware layer, terminal X sends the paging message request, as discussed above. Terminal Y
receives the paging request message and optionally sends a paging accept message to accept the connection request. In one embodiment, the paging request message is a Bluetooth create connection coinmand and the paging accept message is a Bluetooth accept connection request command.
[00451 Following the connection to each nearby device, as shown in Figure 5, terminal X sends a recognition request message to confirm whether a nearby device such as terminal Y definitely includes the middleware layer. Terminal Y receives the recognition request message and sends a recognition response message to terminal X. In one embodiment, the receipt of the recognition response message is confirmation that terminal Y includes the middleware layer. In another embodiment, the content of the recognition response message will indicate whether terminal Y includes the middleware layer. In one embodiment, the recognition request message atid the recognition response message utilize the Bluetooth Service Discovery Protocol (SDP). If terminal Y
does not include the middleware layer, the communication session may be disconnected.
[00461 Following the confirmation that a nearby device such as terminal Y
includes the middleware layer, as shown in Figure 5, terminal X and terminal Y
use the middleware layer to discover and launch applications and services. In one embodiment, terminal X and terminal Y use the methods disclosed in the flow diagrams shown in Figure 3A and Figure 3B to discover and launch applications and services.
[0047] Although the, disclosed embodiments describe a fully functioning device detection and service discovery system and method for a mobile ad hoc communications network, the reader should understand that other equivalent embodiments exist.
Since numerous modifications and variations will occur to those who review this disclosure, the device detection and service discovery system and method for a mobile ad hoc communications network is not limited to the exact construction and operation illustrated and disclosed. Accordingly, this disclosure intends all suitable modifications and equivalents to fall within the scope of the claims.
Claims (36)
1. An apparatus comprising:
a memory device; and a processor disposed in communication with the memory device, the processor configured to:
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
a memory device; and a processor disposed in communication with the memory device, the processor configured to:
conduct an inquiry to discover nearby devices;
determine whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnect communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
create a wireless short-range communication connection to the discovered nearby device;
confirm whether said nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when said discovered nearby device includes the middleware software:
execute the middleware software to perform application and service discovery with said discovered nearby device.
2. The apparatus of claim 1, wherein the middleware software includes a service discovery protocol and at least one computer program, each computer program comprising at least one sequence of operational instructions.
3. The apparatus of claim 1, wherein when said discovered nearby device includes the middleware software, the processor is further configured to:
execute the middleware software to launch applications and services.
execute the middleware software to launch applications and services.
4. The apparatus of claim 1, wherein to confirm that said discovered nearby device includes the middleware software, the processor is further configured to:
send a recognition request message to said discovered nearby device; and receive a recognition response message from said discovered nearby device.
send a recognition request message to said discovered nearby device; and receive a recognition response message from said discovered nearby device.
5. The apparatus of claim 4, wherein the recognition request message is a Bluetooth Service Discovery Protocol request and the recognition response message is a Bluetooth Service Discovery Protocol response.
6. The apparatus of claim 1, wherein to execute the middleware software to perform application and service discovery, the processor is further configured to:
receive a notification message from said discovered nearby device, the notification message including a local application directory stored in said discovered nearby device;
store an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and send an update message to said discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in said discovered nearby device.
receive a notification message from said discovered nearby device, the notification message including a local application directory stored in said discovered nearby device;
store an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and send an update message to said discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in said discovered nearby device.
7. The apparatus of claim 6, wherein the processor is further configured to:
launch a local application based on a reference in the combined application directory; and connect the local application to a counterpart application executing on said discovered nearby device.
launch a local application based on a reference in the combined application directory; and connect the local application to a counterpart application executing on said discovered nearby device.
8. The apparatus of claim 1, wherein to conduct the inquiry, the processor is further configured to:
send an inquiry request message to a coverage area within the mobile ad hoc communications network; and receive an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
send an inquiry request message to a coverage area within the mobile ad hoc communications network; and receive an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
9. The apparatus of claim 8, wherein the inquiry request message is a Bluetooth inquiry command, and the inquiry response message is a Bluetooth inquiry result command.
10. The apparatus of claim 1, wherein to create the connection, the processor is further configured to:
send a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device; and receive a paging accept message from the discovered nearby device.
send a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device; and receive a paging accept message from the discovered nearby device.
11. A method for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnecting communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
creating a wireless short-range communication connection to the discovered nearby device;
confirming whether the discovered nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when the discovered nearby device includes the middleware software layer:
executing the middleware software to perform application and service discovery with said discovered nearby device.
conducting an inquiry to discover nearby devices;
determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
when the discovered nearby device does not provide an indication that it may include the middleware software:
disconnecting communication session establishment with the discovered nearby device;
when the discovered nearby device provides an indication that it may include the middleware software:
creating a wireless short-range communication connection to the discovered nearby device;
confirming whether the discovered nearby device includes the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and when the discovered nearby device includes the middleware software layer:
executing the middleware software to perform application and service discovery with said discovered nearby device.
12. The method of claim 11, wherein the confirming further comprises:
sending a recognition request message to the discovered device; and receiving a recognition response message from the discovered nearby device.
sending a recognition request message to the discovered device; and receiving a recognition response message from the discovered nearby device.
13. The method of claim 12, wherein the receiving of the recognition response message confirms that the discovered nearby device includes the middleware software.
14. The method of claim 12, wherein the recognition response message includes a confirmation that the discovered nearby device includes the middleware software.
15. The method of claim 14, wherein setting at least one bit in the recognition response message to at least one predetermined value is the confirmation.
16. The method of claim 11, wherein the middleware software includes a service discovery protocol and at least one computer program, each computer program comprising at least one sequence of operational instructions.
17. The method of claim 11, wherein when the discovered nearby device includes the middleware software, the method further comprises:
executing the middleware software to launch applications and services.
executing the middleware software to launch applications and services.
18. The method of claim 11, wherein the conducting of the inquiry further comprises:
sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
19. The method of claim 18, wherein the inquiry request message is a Bluetooth inquiry command, and the inquiry response message is a Bluetooth inquiry result command.
20. The method of claim 19, wherein setting at least one bit in the Bluetooth inquiry result command to at least one predetermined value is the indication.
21. The method of claim 11, wherein the creating of the connection further comprises:
sending a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device; and receiving a paging accept message from the discovered nearby device.
sending a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device; and receiving a paging accept message from the discovered nearby device.
22. The method of claim 11, wherein the confirming further comprises:
sending a recognition request message to the discovered nearby device; and receiving a recognition response message from the discovered nearby device.
sending a recognition request message to the discovered nearby device; and receiving a recognition response message from the discovered nearby device.
23. The method of claim 11, wherein the executing of the middleware software to perform application and service discovery further comprises:
receiving a notification message from the discovered nearby device, the notification message including a local application directory stored in the discovered nearby device;
storing an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and sending an update message to the discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in the discovered nearby device.
receiving a notification message from the discovered nearby device, the notification message including a local application directory stored in the discovered nearby device;
storing an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and sending an update message to the discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in the discovered nearby device.
24. The method of claim 11, further comprising:
launching a local application based on a reference in the combined application directory; and connecting the local application to a counterpart application executing on the discovered nearby device.
launching a local application based on a reference in the combined application directory; and connecting the local application to a counterpart application executing on the discovered nearby device.
25. A system for performing device detection and service discovery in a mobile ad hoc communications network, comprising:
means for conducting an inquiry to discover nearby devices;
means for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
means for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
means for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
means for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and means for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
means for conducting an inquiry to discover nearby devices;
means for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
means for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
means for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
means for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and means for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
26. The system of claim 25, wherein the middleware software includes a service discovery protocol and at least one computer program, each computer program comprising at least one sequence of operational instructions.
27. The system of claim 25, further comprising:
means for executing the middleware software to launch applications and services when the discovered nearby device includes the middleware software.
means for executing the middleware software to launch applications and services when the discovered nearby device includes the middleware software.
28. The system of claim 25, wherein the means for conducting the inquiry further comprises:
means for sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and means for receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
means for sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and means for receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
29. A computer readable medium embodying computer program code for performing device detection and service discovery in a mobile ad hoc communications network, said computer program code comprising:
program code for conducting an inquiry to discover nearby devices;
program code for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
program code for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
program code for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
program code for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and program code for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
program code for conducting an inquiry to discover nearby devices;
program code for determining whether a discovered nearby device provides an indication that it may include a middleware software, the middleware software configured for providing application and service discovery;
program code for disconnecting communication session establishment with the discovered nearby device when the discovered nearby device does not provide an indication that it may include the middleware software;
program code for creating a wireless short-range communication connection to the discovered nearby device when the discovered nearby device provides an indication that it may include the middleware software;
program code for confirming that the discovered nearby device includes the middleware software when the discovered nearby device provides an indication that it may include the middleware software by requesting corresponding information from said discovered nearby device via the wireless short-range communication connection; and program code for executing the middleware software to perform application and service discovery with said discovered nearby device when the discovered nearby device includes the middleware software.
30. The computer readable medium of claim 29, wherein the middleware software includes a service discovery protocol and at least one computer program, each computer program comprising at least one sequence of operational instructions.
31. The computer readable medium of claim 29, wherein the computer readable medium further stores:
program code for executing the middleware software to launch applications and services when the discovered nearby device includes the middleware software.
program code for executing the middleware software to launch applications and services when the discovered nearby device includes the middleware software.
32. The computer readable medium of claim 29, wherein the program code for conducting the inquiry further comprises:
program code for sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and program code for receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
program code for sending an inquiry request message to a coverage area within the mobile ad hoc communications network; and program code for receiving an inquiry response message from the discovered nearby device, the inquiry response message including the indication.
33. The computer readable medium of claim 29, wherein the program code for creating the connection further comprises:
program code for sending a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device;
and program code for receiving a paging accept message from the discovered nearby device.
program code for sending a paging request message to a coverage area within the mobile ad hoc communications network directed to the discovered nearby device;
and program code for receiving a paging accept message from the discovered nearby device.
34. The computer readable medium of claim 29, wherein the program code for confirming that the discovered nearby device includes the middleware software further comprises:
program code for sending a recognition request message to the discovered nearby device; and program code for receiving a recognition response message from the discovered nearby device.
program code for sending a recognition request message to the discovered nearby device; and program code for receiving a recognition response message from the discovered nearby device.
35. The computer readable medium of claim 29, wherein the program code for executing the middleware software to perform application and service discovery further comprises:
program code for receiving a notification message from the discovered nearby device, the notification message including a local application directory stored in the discovered nearby device;
program code for storing an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and program code for sending an update message to the discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in the discovered nearby device.
program code for receiving a notification message from the discovered nearby device, the notification message including a local application directory stored in the discovered nearby device;
program code for storing an update to a combined application directory, the update based on a comparison of the local application directory and the combined application directory; and program code for sending an update message to the discovered nearby device, the update message including an update portion of the combined application directory for updating the local application directory stored in the discovered nearby device.
36. The computer readable medium of claim 35, wherein the program code for executing the middleware software to perform application and service discovery further comprises:
program code for launching a local application based on a reference in the combined application directory; and program code for connecting the local application to a counterpart application executing on the discovered nearby device.
program code for launching a local application based on a reference in the combined application directory; and program code for connecting the local application to a counterpart application executing on the discovered nearby device.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/284,135 | 2002-10-31 | ||
| US10/284,135 US6909721B2 (en) | 2002-10-31 | 2002-10-31 | Device detection and service discovery system and method for a mobile ad hoc communications network |
| US10/662,407 | 2003-09-16 | ||
| US10/662,407 US7590097B2 (en) | 2002-10-31 | 2003-09-16 | Device detection and service discovery system and method for a mobile ad hoc communications network |
| CA2501566A CA2501566C (en) | 2002-10-31 | 2003-10-30 | Device detection and service discovery system and method for a mobile ad hoc communications network |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2501566A Division CA2501566C (en) | 2002-10-31 | 2003-10-30 | Device detection and service discovery system and method for a mobile ad hoc communications network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2683998A1 CA2683998A1 (en) | 2004-05-13 |
| CA2683998C true CA2683998C (en) | 2010-09-21 |
Family
ID=32174810
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2683998A Expired - Fee Related CA2683998C (en) | 2002-10-31 | 2003-10-30 | Device detection and service discovery system and method for a mobile ad hoc communications network |
Country Status (3)
| Country | Link |
|---|---|
| US (3) | US6909721B2 (en) |
| CN (1) | CN100550795C (en) |
| CA (1) | CA2683998C (en) |
Families Citing this family (143)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7835372B2 (en) * | 2002-05-13 | 2010-11-16 | Weilin Wang | System and method for transparent wireless bridging of communication channel segments |
| US7852796B2 (en) * | 2002-05-13 | 2010-12-14 | Xudong Wang | Distributed multichannel wireless communication |
| US7069483B2 (en) * | 2002-05-13 | 2006-06-27 | Kiyon, Inc. | System and method for identifying nodes in a wireless mesh network |
| US8780770B2 (en) * | 2002-05-13 | 2014-07-15 | Misonimo Chi Acquisition L.L.C. | Systems and methods for voice and video communication over a wireless network |
| US7957356B2 (en) | 2002-05-13 | 2011-06-07 | Misomino Chi Acquisitions L.L.C. | Scalable media access control for multi-hop high bandwidth communications |
| US7941149B2 (en) * | 2002-05-13 | 2011-05-10 | Misonimo Chi Acquistion L.L.C. | Multi-hop ultra wide band wireless network communication |
| US8060626B2 (en) * | 2008-09-22 | 2011-11-15 | Sony Computer Entertainment America Llc. | Method for host selection based on discovered NAT type |
| US8224985B2 (en) * | 2005-10-04 | 2012-07-17 | Sony Computer Entertainment Inc. | Peer-to-peer communication traversing symmetric network address translators |
| US6909721B2 (en) * | 2002-10-31 | 2005-06-21 | Nokia Corporation | Device detection and service discovery system and method for a mobile ad hoc communications network |
| US20040162804A1 (en) * | 2003-02-18 | 2004-08-19 | Michael Strittmatter | System and method for searching for wireless devices |
| NO322710B1 (en) * | 2003-04-29 | 2006-11-27 | Telenor Asa | An interface device with open and closed devices for communicating services in a personal network. |
| US7406500B2 (en) * | 2003-05-20 | 2008-07-29 | International Business Machines Corporation | Techniques for providing a virtual workspace comprised of a multiplicity of electronic devices |
| US7668903B2 (en) * | 2003-07-07 | 2010-02-23 | Xerox Corporation | Method and apparatus for dynamically delivering service profiles to clients |
| US7362724B2 (en) * | 2003-07-09 | 2008-04-22 | Motorola, Inc. | Method for rigid body discovery and peer-to-peer ranging in a scatternet and communications node |
| KR100629484B1 (en) * | 2003-07-11 | 2006-09-28 | 삼성전자주식회사 | Apparatus and method for routing path establishment in scatternet |
| US7545941B2 (en) * | 2003-09-16 | 2009-06-09 | Nokia Corporation | Method of initializing and using a security association for middleware based on physical proximity |
| US7313120B2 (en) * | 2003-09-16 | 2007-12-25 | Nokia Corporation | Application control in peer-to-peer ad-hoc communication networks |
| US20050058109A1 (en) * | 2003-09-16 | 2005-03-17 | Jan-Erik Ekberg | Mechanism for improving connection control in peer-to-peer ad-hoc networks |
| US7523220B2 (en) * | 2003-09-17 | 2009-04-21 | Microsoft Corporation | Metaspace: communication middleware for partially connected mobile ad hoc networks |
| KR100576935B1 (en) * | 2003-12-22 | 2006-05-10 | 한국전자통신연구원 | Ontology-based service discovery system and method for ad hoc networks |
| US8959187B2 (en) * | 2004-02-23 | 2015-02-17 | Apple Inc. | Method and system for proximity-based information retrieval and exchange in ad hoc networks |
| US20050193106A1 (en) * | 2004-03-01 | 2005-09-01 | University Of Florida | Service discovery and delivery for ad-hoc networks |
| US7263345B2 (en) * | 2004-03-17 | 2007-08-28 | Nokia Corporation | System and method for remote service information |
| US20050272454A1 (en) * | 2004-06-07 | 2005-12-08 | Lucent Technologies, Inc. | Method and apparatus for providing a low-latency, high-accuracy indication-to-speak and abandon call |
| GB2415325A (en) * | 2004-06-15 | 2005-12-21 | Mitel Networks Corp | Spontaneous discovery of remote service profiles |
| US7769409B2 (en) * | 2004-06-23 | 2010-08-03 | Sony Computer Entertainment America Inc. | Network participant status evaluation |
| EP1635513B1 (en) * | 2004-09-09 | 2007-02-21 | Siemens Aktiengesellschaft | Data processing device for ad-hoc network and ad-hoc network therefor |
| DE102004047370A1 (en) * | 2004-09-29 | 2006-03-30 | Siemens Ag | Method for operating an ad hoc communication network and corresponding device |
| US7464168B1 (en) * | 2004-10-19 | 2008-12-09 | Sun Microsystems, Inc. | Mechanism for decentralized entity presence |
| US8014321B2 (en) * | 2004-10-22 | 2011-09-06 | Microsoft Corporation | Rendezvousing resource requests with corresponding resources |
| US20080288659A1 (en) | 2006-11-09 | 2008-11-20 | Microsoft Corporation | Maintaining consistency within a federation infrastructure |
| US7730220B2 (en) | 2004-10-22 | 2010-06-01 | Microsoft Corporation | Broadcasting communication within a rendezvous federation |
| US20110082928A1 (en) * | 2004-10-22 | 2011-04-07 | Microsoft Corporation | Maintaining consistency within a federation infrastructure |
| US7958262B2 (en) * | 2004-10-22 | 2011-06-07 | Microsoft Corporation | Allocating and reclaiming resources within a rendezvous federation |
| US8392515B2 (en) * | 2004-10-22 | 2013-03-05 | Microsoft Corporation | Subfederation creation and maintenance in a federation infrastructure |
| US7694167B2 (en) * | 2004-10-22 | 2010-04-06 | Microsoft Corporation | Maintaining routing consistency within a rendezvous federation |
| US20060090003A1 (en) * | 2004-10-22 | 2006-04-27 | Microsoft Corporation | Rendezvousing resource requests with corresponding resources |
| US8095601B2 (en) * | 2004-10-22 | 2012-01-10 | Microsoft Corporation | Inter-proximity communication within a rendezvous federation |
| US8549180B2 (en) * | 2004-10-22 | 2013-10-01 | Microsoft Corporation | Optimizing access to federation infrastructure-based resources |
| US8095600B2 (en) * | 2004-10-22 | 2012-01-10 | Microsoft Corporation | Inter-proximity communication within a rendezvous federation |
| KR100703319B1 (en) * | 2004-10-29 | 2007-04-03 | 삼성전자주식회사 | Searching method for company id using in a bluetooch equipment |
| JP4164490B2 (en) * | 2004-12-17 | 2008-10-15 | キヤノン株式会社 | Communication device, profile information acquisition method, and program |
| WO2006084924A1 (en) * | 2005-02-10 | 2006-08-17 | Wilico Wireless Networking Solutions, Sa | Method and system for customised local-area wireless communication and access device |
| US7697894B2 (en) * | 2005-03-01 | 2010-04-13 | Nokia Corporation | Method and system for tactile confirmation of service bookmarks |
| US8204027B2 (en) * | 2005-05-05 | 2012-06-19 | International Business Machines Corporation | Administering requests for data communications connections in a wide area network that includes a plurality of networks |
| US7359674B2 (en) * | 2005-05-10 | 2008-04-15 | Nokia Corporation | Content distribution & communication system for enhancing service distribution in short range radio environment |
| JP4421517B2 (en) * | 2005-06-07 | 2010-02-24 | 株式会社東芝 | Information processing server, remote operation system, and remote operation method |
| KR100737616B1 (en) | 2005-07-20 | 2007-07-10 | 엘지전자 주식회사 | Apparatus and method for acquiring application information of short-range communication terminal |
| CN101233738B (en) | 2005-07-29 | 2013-06-19 | 皇家飞利浦电子股份有限公司 | System and method for context dependent service discovery for mobile medical devices |
| US20070047435A1 (en) * | 2005-08-31 | 2007-03-01 | Motorola, Inc. | Advertising availability for ad-hoc networking based on stored device history |
| US20070110012A1 (en) * | 2005-11-14 | 2007-05-17 | Abu-Amara Hosame H | Device and method for tracking usage of content distributed to media devices of a local area network |
| US7606937B2 (en) * | 2005-12-02 | 2009-10-20 | Microsoft Corporation | Next site for distributed service connections |
| ES2276620B1 (en) * | 2005-12-09 | 2008-06-16 | Wilico Wireless Networking Solutions, S.A. | METHOD OF SHORT RADIO COMMUNICATION INDIVIDUALIZED AND DEVICE FOR IMPLEMENTATION. |
| KR100703375B1 (en) * | 2005-12-12 | 2007-04-03 | 삼성전자주식회사 | Method for managing log in bluetooth of wireless terminal |
| US8559350B2 (en) | 2005-12-20 | 2013-10-15 | Microsoft Corporation | Mechanism to convey discovery information in a wireless network |
| US8478300B2 (en) * | 2005-12-20 | 2013-07-02 | Microsoft Corporation | Proximity service discovery in wireless networks |
| US7613426B2 (en) * | 2005-12-20 | 2009-11-03 | Microsoft Corporation | Proximity service discovery in wireless networks |
| EP1966940B1 (en) * | 2006-01-31 | 2012-08-15 | Panasonic Corporation | Method for selective service updates for communication networks |
| US7333464B2 (en) * | 2006-02-01 | 2008-02-19 | Microsoft Corporation | Automated service discovery and wireless network set-up |
| US8863221B2 (en) * | 2006-03-07 | 2014-10-14 | Samsung Electronics Co., Ltd. | Method and system for integrating content and services among multiple networks |
| JP4585479B2 (en) * | 2006-03-30 | 2010-11-24 | 株式会社東芝 | Server apparatus and video distribution method |
| US7548547B2 (en) * | 2006-03-31 | 2009-06-16 | Microsoft Corporation | Controlling the transfer of terminal server data |
| CN101051924B (en) * | 2006-04-06 | 2011-05-18 | 华为技术有限公司 | Equipment managing method for user's networks and user's network managing entity |
| US20070264991A1 (en) * | 2006-05-15 | 2007-11-15 | Microsoft Corporation | Services near me: discovering and connecting to available wireless services utilizing proximity discovery |
| US10681151B2 (en) | 2006-05-15 | 2020-06-09 | Microsoft Technology Licensing, Llc | Notification framework for wireless networks |
| US8175613B2 (en) * | 2006-08-04 | 2012-05-08 | Misonimo Chi Acquisitions L.L.C. | Systems and methods for determining location of devices within a wireless network |
| KR100748096B1 (en) | 2006-09-29 | 2007-08-09 | 한국전자통신연구원 | Adaptive service discovery method in mobile ad-hoc network(manet) |
| US8616976B2 (en) | 2006-11-07 | 2013-12-31 | Core Wireless Licensing S.A.R.L. | Gaming via peer-to-peer networks |
| US20080123665A1 (en) * | 2006-11-28 | 2008-05-29 | Honeywell International Inc. | Uwb sensor array network structure |
| US7734717B2 (en) * | 2006-12-05 | 2010-06-08 | Nokia Corporation | Software distribution via peer-to-peer networks |
| EP2092664A4 (en) * | 2006-12-07 | 2013-10-16 | Misonimo Chi Acquisition L L C | System and method for timeslot and channel allocation |
| US8285851B2 (en) | 2007-01-08 | 2012-10-09 | Apple Inc. | Pairing a media server and a media client |
| WO2008122750A1 (en) * | 2007-04-05 | 2008-10-16 | British Telecommunications Public Limited Company | Network-intelligent scanner |
| US7849139B2 (en) | 2007-05-02 | 2010-12-07 | Ouri Wolfson | Adaptive search in mobile peer-to-peer databases |
| US7853669B2 (en) | 2007-05-04 | 2010-12-14 | Microsoft Corporation | Mesh-managing data across a distributed set of devices |
| US7995478B2 (en) | 2007-05-30 | 2011-08-09 | Sony Computer Entertainment Inc. | Network communication with path MTU size discovery |
| JPWO2009001553A1 (en) * | 2007-06-26 | 2010-08-26 | パナソニック株式会社 | Communication method, communication system, mobile node, server, and node |
| US8681691B2 (en) | 2007-07-25 | 2014-03-25 | Microsoft Corporation | Base station initiated proximity service discovery and connection establishment |
| US7974574B2 (en) * | 2007-07-25 | 2011-07-05 | Microsoft Corporation | Base station initiated proximity service discovery and connection establishment |
| US9417934B2 (en) * | 2007-08-31 | 2016-08-16 | Core Wireless Licensing S.A.R.L. | Information distribution in a dynamic multi-device environment |
| US8385823B2 (en) * | 2007-10-03 | 2013-02-26 | Samsung Electronics Co., Ltd | Method and system for communication in near field communication network |
| US20090110177A1 (en) * | 2007-10-31 | 2009-04-30 | Nokia Corporation | Dynamic Secondary Phone Book |
| US8493888B2 (en) * | 2007-11-08 | 2013-07-23 | Nokia Corporation | Connectivity architecture for service discovery |
| US20090141692A1 (en) * | 2007-11-30 | 2009-06-04 | Mika Kasslin | Optimized ad hoc networking |
| JP4314297B2 (en) * | 2007-12-03 | 2009-08-12 | 株式会社東芝 | Information processing apparatus, device selection processing method, and program |
| US7908393B2 (en) * | 2007-12-04 | 2011-03-15 | Sony Computer Entertainment Inc. | Network bandwidth detection, distribution and traffic prioritization |
| US20090161579A1 (en) * | 2007-12-20 | 2009-06-25 | Mika Saaranen | Method, system, and apparatus for implementing network capable input devices |
| US9105031B2 (en) | 2008-02-22 | 2015-08-11 | Microsoft Technology Licensing, Llc | Authentication mechanisms for wireless networks |
| WO2009106930A1 (en) * | 2008-02-27 | 2009-09-03 | Nokia Corporation | Transport independent architecture |
| WO2009106932A1 (en) * | 2008-02-27 | 2009-09-03 | Nokia Corporation | Buffer control for multi-transport architectures |
| US7856506B2 (en) | 2008-03-05 | 2010-12-21 | Sony Computer Entertainment Inc. | Traversal of symmetric network address translator for multiple simultaneous connections |
| US8484174B2 (en) * | 2008-03-20 | 2013-07-09 | Microsoft Corporation | Computing environment representation |
| US9753712B2 (en) * | 2008-03-20 | 2017-09-05 | Microsoft Technology Licensing, Llc | Application management within deployable object hierarchy |
| US9298747B2 (en) | 2008-03-20 | 2016-03-29 | Microsoft Technology Licensing, Llc | Deployable, consistent, and extensible computing environment platform |
| US8572033B2 (en) | 2008-03-20 | 2013-10-29 | Microsoft Corporation | Computing environment configuration |
| US20090248737A1 (en) * | 2008-03-27 | 2009-10-01 | Microsoft Corporation | Computing environment representation |
| US20090276520A1 (en) * | 2008-05-05 | 2009-11-05 | Lockheed Martin Corporation | Method and apparatus for server election, discovery and selection in mobile ad hoc networks |
| US8090616B2 (en) | 2008-09-08 | 2012-01-03 | Proctor Jr James Arthur | Visual identification information used as confirmation in a wireless communication |
| EP2175366B1 (en) | 2008-10-08 | 2012-10-10 | Research In Motion Limited | Server for sending new application portions to mobile wireless communications devices and related methods |
| US8180891B1 (en) * | 2008-11-26 | 2012-05-15 | Free Stream Media Corp. | Discovery, access control, and communication with networked services from within a security sandbox |
| US20100235523A1 (en) * | 2009-03-16 | 2010-09-16 | Robert Garcia | Framework for supporting multi-device collaboration |
| US20100233960A1 (en) * | 2009-03-16 | 2010-09-16 | Brian Tucker | Service discovery functionality utilizing personal area network protocols |
| US10277683B2 (en) | 2009-03-16 | 2019-04-30 | Apple Inc. | Multifunctional devices as virtual accessories |
| US8285860B2 (en) * | 2009-03-16 | 2012-10-09 | Apple Inc. | Efficient service discovery for peer-to-peer networking devices |
| JP2010258687A (en) * | 2009-04-23 | 2010-11-11 | Fujitsu Ltd | Wireless communication apparatus |
| US8775633B2 (en) * | 2009-07-08 | 2014-07-08 | Nokia Corporation | Service information exchange in wireless network |
| US8478820B2 (en) * | 2009-08-26 | 2013-07-02 | Qualcomm Incorporated | Methods and systems for service discovery management in peer-to-peer networks |
| US8478776B2 (en) | 2009-10-30 | 2013-07-02 | Qualcomm Incorporated | Methods and systems for peer-to-peer network discovery using multi-user diversity |
| US8825818B2 (en) | 2009-11-10 | 2014-09-02 | Qualcomm Incorporated | Host initiated connection to a device |
| US9372728B2 (en) * | 2009-12-03 | 2016-06-21 | Ol Security Limited Liability Company | System and method for agent networks |
| US8730928B2 (en) * | 2010-02-23 | 2014-05-20 | Qualcomm Incorporated | Enhancements for increased spatial reuse in ad-hoc networks |
| US8825873B2 (en) * | 2010-03-01 | 2014-09-02 | Apple Inc. | Using a service discovery request to find available devices |
| US20110320530A1 (en) | 2010-06-29 | 2011-12-29 | International Business Machines Corporation | Method for processing a unit of work |
| US9977819B2 (en) * | 2010-08-09 | 2018-05-22 | Ianywhere Solutions, Inc. | Sharing data on mobile devices |
| US8838686B2 (en) * | 2010-11-03 | 2014-09-16 | Verizon Patent And Licensing Inc. | Method and apparatus for delivery of content to a mobile device |
| US8924570B2 (en) * | 2010-11-23 | 2014-12-30 | International Business Machines Corporation | Temporary collaborative ad-hoc network of hardware nodes to perform function |
| US9026603B2 (en) | 2011-06-30 | 2015-05-05 | Broadcom Corporation | Device configuration including a master communications device with a slave device extension |
| US20130013438A1 (en) * | 2011-07-05 | 2013-01-10 | Li-Hui Chen | Grouping Method for Group-buying Based on Wireless Communication Protocol |
| CN105376725B (en) * | 2011-07-05 | 2018-12-28 | 宏达国际电子股份有限公司 | Wireless service provider method |
| US10523804B2 (en) | 2011-09-16 | 2019-12-31 | Samsung Electronics Co., Ltd. | Method and system for searching for object in network |
| KR101930510B1 (en) * | 2011-09-16 | 2018-12-19 | 삼성전자주식회사 | Method and system for searching object in network |
| US8755331B2 (en) * | 2011-12-13 | 2014-06-17 | International Business Machines Corporation | Determining a physical location of a wireless mobile device |
| US8805281B2 (en) * | 2012-02-29 | 2014-08-12 | Cellco Partnership | Controlling device functions of a mobile terminal in a restricted area |
| US10123187B2 (en) * | 2012-04-17 | 2018-11-06 | Qualcomm Incorporated | Methods and apparatus for multiplexing application identifiers for peer-to-peer discovery systems |
| US9563336B2 (en) * | 2012-04-26 | 2017-02-07 | Liveperson, Inc. | Dynamic user interface customization |
| JP6008617B2 (en) | 2012-06-29 | 2016-10-19 | キヤノン株式会社 | COMMUNICATION DEVICE, ITS CONTROL METHOD, AND PROGRAM |
| KR101389214B1 (en) * | 2012-09-04 | 2014-04-24 | 주식회사 엘지씨엔에스 | Remote managing system and method |
| US9071330B2 (en) * | 2012-09-07 | 2015-06-30 | Qualcomm Innovation Center, Inc. | Peer-to-peer communication initiated by shared physical experience |
| US9130942B2 (en) | 2013-02-05 | 2015-09-08 | Qualcomm Incorporated | Optimizing recipient application selection in a multiple application environment using equivalence classes for applications |
| US9122554B2 (en) * | 2013-02-08 | 2015-09-01 | Microsoft Technology Licensing, Llc | Pervasive service providing device-specific updates |
| CN104243526A (en) * | 2013-06-20 | 2014-12-24 | 中兴通讯股份有限公司 | Method, device, terminal and network side equipment for application sharing |
| US9936448B2 (en) * | 2013-11-06 | 2018-04-03 | Lg Electronics Inc. | Method for transmitting and receiving data in wireless communication system and apparatus for performing the same |
| US9277573B2 (en) | 2013-11-21 | 2016-03-01 | At&T Intellectual Property I, L.P. | Method and apparatus for establishing an ad hoc communication with an unknown contact |
| US9258695B2 (en) | 2013-12-16 | 2016-02-09 | Nokia Technologies Oy | Method, apparatus, and computer program product for service discovery in short-range communication environment |
| US9380119B2 (en) | 2013-12-16 | 2016-06-28 | Nokia Technologies Oy | Method, apparatus, and computer program product for network discovery |
| US9398437B2 (en) | 2013-12-16 | 2016-07-19 | Nokia Technologies Oy | Method, apparatus, and computer program product for service discovery in wireless short-range communication |
| US9258193B2 (en) | 2014-01-14 | 2016-02-09 | Nokia Technologies Oy | Method, apparatus, and computer program product for wireless network cluster discovery and concurrency management |
| TWI572155B (en) * | 2014-05-30 | 2017-02-21 | 絡達科技股份有限公司 | Multi-role bluetooth device and connection method thereof |
| US20170347311A1 (en) * | 2016-05-25 | 2017-11-30 | Qualcomm Incorporated | Identification and/or profiling of stationary users and mobile users |
| JP7006411B2 (en) * | 2018-03-16 | 2022-01-24 | 株式会社リコー | Information processing equipment, information processing methods, and programs |
| US10791460B2 (en) * | 2019-01-30 | 2020-09-29 | Visa International Service Association | Terminal type identification in interaction processing |
| US10819557B1 (en) * | 2019-05-03 | 2020-10-27 | Servicenow, Inc. | Systems and methods for selective discovery of services |
| US20220101335A1 (en) * | 2020-09-28 | 2022-03-31 | Arris Enterprises Llc | Identification of unsupported device capability to service provider for enhancement and customer attraction |
Family Cites Families (97)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US662407A (en) * | 1899-06-15 | 1900-11-27 | American Soda Fountain Company | Carbonator. |
| US662470A (en) * | 1900-03-15 | 1900-11-27 | William Scott | Chuck. |
| US784215A (en) * | 1903-07-09 | 1905-03-07 | James E Humphrey | Dinner-pail. |
| EP0123540A3 (en) | 1983-04-20 | 1985-01-02 | RAYCHEM CORPORATION (a California corporation) | Conductive polymers and devices containing them |
| DE69417983T2 (en) | 1993-10-20 | 1999-09-16 | Sumitomo Chemical Co | Statistical propylene copolymer composition |
| FR2718553B1 (en) | 1994-04-12 | 1996-06-14 | Metalogic | System and method for interactive dialogue between a user and a telematic server. |
| US6112103A (en) | 1996-12-03 | 2000-08-29 | Puthuff; Steven H. | Personal communication device |
| US6219696B1 (en) | 1997-08-01 | 2001-04-17 | Siemens Corporate Research, Inc. | System for providing targeted internet information to mobile agents |
| US6901241B2 (en) | 1998-02-11 | 2005-05-31 | Telefonaktiebolaget L M Ericsson (Publ) | System, method and apparatus for secure transmission of confidential information |
| CA2275673A1 (en) * | 1998-06-23 | 1999-12-23 | Andre Dion | Plant containerizing and watering device |
| US6198941B1 (en) | 1998-08-07 | 2001-03-06 | Lucent Technologies Inc. | Method of operating a portable communication device |
| US20050058149A1 (en) * | 1998-08-19 | 2005-03-17 | Howe Wayne Richard | Time-scheduled and time-reservation packet switching |
| DE69937353T2 (en) | 1998-08-21 | 2008-07-17 | Union Biometrica, Inc., Somerville | INSTRUMENT FOR THE ANALYSIS AND SELECTIVE DISTRIBUTION OF OBJECT SAMPLES |
| US6757715B1 (en) | 1998-09-11 | 2004-06-29 | L.V. Partners, L.P. | Bar code scanner and software interface interlock for performing encrypted handshaking and for disabling the scanner in case of handshaking operation failure |
| EP1022876B1 (en) | 1999-01-25 | 2006-04-19 | International Business Machines Corporation | Service advertisements in wireless local networks |
| EP1024628B1 (en) | 1999-01-29 | 2008-09-17 | Wistron Corporation | Adjacency-bound service discovery |
| US6577849B1 (en) | 1999-02-03 | 2003-06-10 | Motorola, Inc. | Method and apparatus for providing additional information about a broadcast |
| US6604140B1 (en) * | 1999-03-31 | 2003-08-05 | International Business Machines Corporation | Service framework for computing devices |
| AU5084500A (en) | 1999-05-21 | 2000-12-12 | International Business Machines Corporation | Method and apparatus for initializing secure communications among, and for exclusively pairing wireless devices |
| DE69928451T2 (en) | 1999-09-03 | 2006-07-27 | Nokia Corp. | MAP INTERFACE FOR REPLACING MESSAGES WITH A SERVICE CONTROL POINT |
| US7028032B1 (en) | 1999-09-28 | 2006-04-11 | International Business Machines Corporation | Method of updating network information addresses |
| US6751463B1 (en) | 1999-10-04 | 2004-06-15 | Telecommunication Systems, Inc. | Intelligent queue for information teleservice messages with superceding updates |
| GB2355889A (en) | 1999-10-26 | 2001-05-02 | Endeavour Consulting Ltd | Controlling operation of a device within a restricted area by detecting the presence of the device and instructing it to restrict its operation |
| US6601093B1 (en) * | 1999-12-01 | 2003-07-29 | Ibm Corporation | Address resolution in ad-hoc networking |
| SE9904683L (en) | 1999-12-17 | 2001-06-18 | Ericsson Telefon Ab L M | Method and system for establishing a short-range radio connection |
| WO2001045064A1 (en) | 1999-12-17 | 2001-06-21 | Gateway, Inc. | Method and device for controlling the operation of electronic devices in an aircraft |
| US6614899B1 (en) | 2000-01-31 | 2003-09-02 | Nortel Networks Limited | Method and apparatus for providing advanced IP telephony services in an intelligent endpoint |
| GB0007940D0 (en) * | 2000-04-01 | 2000-05-17 | Hewlett Packard Co | Gathering information from short-range portals |
| US6714797B1 (en) | 2000-05-17 | 2004-03-30 | Nokia Corporation | System and method for the transfer of digital data to a mobile device |
| US20020012329A1 (en) * | 2000-06-02 | 2002-01-31 | Timothy Atkinson | Communications apparatus interface and method for discovery of remote devices |
| AU2001264840A1 (en) | 2000-06-08 | 2001-12-17 | Motorola, Inc. | Mobile ip push service |
| US20020044549A1 (en) | 2000-06-12 | 2002-04-18 | Per Johansson | Efficient scatternet forming |
| IL153841A0 (en) | 2000-07-10 | 2003-07-31 | Viven Ltd | Broadcast content over cellular telephones |
| US6591266B1 (en) | 2000-07-14 | 2003-07-08 | Nec Corporation | System and method for intelligent caching and refresh of dynamically generated and static web content |
| FI113319B (en) * | 2000-09-29 | 2004-03-31 | Nokia Corp | Selection of a service producing network element in a telecommunication system |
| EP1207707B1 (en) | 2000-11-17 | 2008-08-13 | Sony Deutschland GmbH | Transmission of carry-on objects using a wireless ad-hoc networking environment |
| US20020073204A1 (en) | 2000-12-07 | 2002-06-13 | Rabindranath Dutta | Method and system for exchange of node characteristics for DATA sharing in peer-to-peer DATA networks |
| US20040015403A1 (en) | 2000-12-21 | 2004-01-22 | International Business Machines Corporation | Method, system, and business method for wireless fast business |
| US20030006911A1 (en) | 2000-12-22 | 2003-01-09 | The Cadre Group Inc. | Interactive advertising system and method |
| EP1419137A2 (en) | 2001-01-18 | 2004-05-19 | Cognis Deutschland GmbH & Co. KG | Method for producing acyl amino acids |
| US7197565B2 (en) * | 2001-01-22 | 2007-03-27 | Sun Microsystems, Inc. | System and method of using a pipe advertisement for a peer-to-peer network entity in peer-to-peer presence detection |
| WO2002057917A2 (en) * | 2001-01-22 | 2002-07-25 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
| US7668958B2 (en) | 2001-10-18 | 2010-02-23 | Intel Corporation | Method for discovery and routing using a priori knowledge in the form of application programme within mobile AD-HOC networks |
| US7190961B2 (en) * | 2001-10-18 | 2007-03-13 | Intel Corporation | Method for discovery and routing within mobile ad-hoc networks |
| US6981210B2 (en) | 2001-02-16 | 2005-12-27 | International Business Machines Corporation | Self-maintaining web browser bookmarks |
| US8126982B2 (en) | 2001-02-16 | 2012-02-28 | International Business Machines Corporation | Method, network device and computer program product for performing service discovery in a pervasive network |
| US20020124046A1 (en) | 2001-02-20 | 2002-09-05 | Fischer William A. | Peripheral devices which manage application upload to computing devices |
| GB0105075D0 (en) | 2001-03-01 | 2001-04-18 | Red M Communications Ltd | An interactive display system |
| US7584269B2 (en) | 2001-03-09 | 2009-09-01 | International Business Machines Corporation | Method for providing kiosk service offerings in a personal area network |
| DE10112409B4 (en) | 2001-03-13 | 2005-06-16 | M-Creations Gmbh | Method and system for data management, and appropriate use of the method and / or the system |
| US20020178216A1 (en) | 2001-03-13 | 2002-11-28 | Stefan Walther | Method and system for data management |
| GB2373966B (en) | 2001-03-30 | 2003-07-09 | Toshiba Res Europ Ltd | Mode monitoring & identification through distributed radio |
| US7715533B2 (en) | 2001-04-27 | 2010-05-11 | Hewlett-Packard Development Company, L.P. | Brokering of information acquisition by devices in a wireless network |
| US6950646B2 (en) | 2001-04-27 | 2005-09-27 | Hewlett-Packard Development Company, L.P. | Information acquisition decision making by devices in a wireless network |
| US7099951B2 (en) | 2001-05-24 | 2006-08-29 | Vixs, Inc. | Method and apparatus for multimedia system |
| US6842460B1 (en) * | 2001-06-27 | 2005-01-11 | Nokia Corporation | Ad hoc network discovery menu |
| JP2003016347A (en) | 2001-07-02 | 2003-01-17 | Nec Corp | Method and system for distributing area advertisement information, and portable terminal installed with the system |
| US20030013483A1 (en) | 2001-07-06 | 2003-01-16 | Ausems Michiel R. | User interface for handheld communication device |
| US20030054806A1 (en) | 2001-08-15 | 2003-03-20 | Raymond Ho | System and method for defining, creating and deploying wireless applications |
| US7089298B2 (en) | 2001-08-20 | 2006-08-08 | Nokia Corporation | Naming distribution method for ad hoc networks |
| US20030061364A1 (en) | 2001-09-26 | 2003-03-27 | International Business Machines Corporation | Method and system in electronic commerce for providing a secure wireless connection service for mobile personal area networks |
| US7020464B2 (en) | 2001-10-09 | 2006-03-28 | Microsoft Corporation | System and method for providing agent-free and no-packet overhead mobility support with transparent session continuity for mobile devices |
| US20030110218A1 (en) | 2001-12-12 | 2003-06-12 | Stanley Randy P. | Local caching of images for on-line conferencing programs |
| US20030115415A1 (en) | 2001-12-18 | 2003-06-19 | Roy Want | Portable memory device |
| US6985696B2 (en) | 2001-12-20 | 2006-01-10 | Motorola, Inc. | Method and apparatus for facilitating wireless communications with a nonautomotive roaming object |
| US7133663B2 (en) | 2001-12-20 | 2006-11-07 | Accenture Global Services, Gmbh | Determining the context of surroundings |
| US20030131059A1 (en) | 2002-01-08 | 2003-07-10 | International Business Machines Corporation | Method, system, and program for providing information on scheduled events to wireless devices |
| US7158176B2 (en) | 2002-03-01 | 2007-01-02 | Nokia Corporation | Prioritization of files in a memory |
| US7184423B2 (en) | 2002-04-23 | 2007-02-27 | Machine Talker Inc. | Self coordinated machine network |
| US7551930B2 (en) | 2002-05-06 | 2009-06-23 | Nokia Corporation | Location-based services for mobile stations using short range wireless technology |
| US6631269B1 (en) | 2002-05-23 | 2003-10-07 | Interdigital Technology Corporation | Signaling connection admission control in a wireless network |
| US7103313B2 (en) * | 2002-06-05 | 2006-09-05 | Nokia Corporation | Automatic determination of access point content and services for short-range wireless terminals |
| US7254406B2 (en) * | 2002-06-10 | 2007-08-07 | Suman Beros | Method and apparatus for effecting a detection of mobile devices that are proximate and exhibit commonalities between specific data sets, or profiles, associated with the persons transporting the mobile devices |
| US7047041B2 (en) | 2002-06-17 | 2006-05-16 | Nokia Corporation | Method and device for storing and accessing personal information |
| US7455591B2 (en) | 2002-06-28 | 2008-11-25 | Igt | Redundant gaming network mediation |
| AU2003250670A1 (en) | 2002-07-23 | 2004-02-09 | Research In Motion Limited | Data store management system and method for wireless devices |
| US7484225B2 (en) * | 2002-08-08 | 2009-01-27 | Sun Microsystems, Inc. | System and method for describing and identifying abstract software modules in peer-to-peer network environments |
| US20040038645A1 (en) | 2002-08-20 | 2004-02-26 | Jukka Rcunamaki | Carrier sensing multiple access with collision avoidance (CSMA/CA) scheme optimized for a priori known carrier usage for low duty cycle systems |
| US8204992B2 (en) * | 2002-09-26 | 2012-06-19 | Oracle America, Inc. | Presence detection using distributed indexes in peer-to-peer networks |
| US20040063498A1 (en) | 2002-09-30 | 2004-04-01 | Sony Corporation | System and method for flexibly implementing a wireless gaming network |
| US20040075675A1 (en) | 2002-10-17 | 2004-04-22 | Tommi Raivisto | Apparatus and method for accessing services via a mobile terminal |
| US20040082383A1 (en) | 2002-10-24 | 2004-04-29 | Motorola, Inc | Methodology and wireless device for interactive gaming |
| US6909721B2 (en) | 2002-10-31 | 2005-06-21 | Nokia Corporation | Device detection and service discovery system and method for a mobile ad hoc communications network |
| US7421276B2 (en) | 2003-04-09 | 2008-09-02 | Nortel Networks Limited | Method, apparatus and system of configuring a wireless device based on location |
| US7209827B2 (en) | 2003-03-07 | 2007-04-24 | Ntt Docomo, Inc. | Server apparatus, terminal device, and information providing system |
| JP4470415B2 (en) | 2003-08-05 | 2010-06-02 | 日本電気株式会社 | Portable information terminal device |
| US7545941B2 (en) | 2003-09-16 | 2009-06-09 | Nokia Corporation | Method of initializing and using a security association for middleware based on physical proximity |
| US7313120B2 (en) | 2003-09-16 | 2007-12-25 | Nokia Corporation | Application control in peer-to-peer ad-hoc communication networks |
| US20050058109A1 (en) | 2003-09-16 | 2005-03-17 | Jan-Erik Ekberg | Mechanism for improving connection control in peer-to-peer ad-hoc networks |
| US7190943B2 (en) | 2003-09-16 | 2007-03-13 | Microtune (Texas), L.P. | System and method for frequency translation with harmonic suppression using mixer stages |
| US7145437B2 (en) | 2003-10-16 | 2006-12-05 | Nokia Corporation | Method, terminal and computer program product for adjusting power consumption of a RFID reader associated with a mobile terminal |
| US20050114756A1 (en) | 2003-11-26 | 2005-05-26 | Nokia Corporation | Dynamic Internet linking system and method |
| GB2410153B (en) | 2004-01-19 | 2006-02-01 | Toshiba Res Europ Ltd | Network service information discovery method and communication device |
| US7263345B2 (en) | 2004-03-17 | 2007-08-28 | Nokia Corporation | System and method for remote service information |
| US7697894B2 (en) | 2005-03-01 | 2010-04-13 | Nokia Corporation | Method and system for tactile confirmation of service bookmarks |
| US7359674B2 (en) | 2005-05-10 | 2008-04-15 | Nokia Corporation | Content distribution & communication system for enhancing service distribution in short range radio environment |
| US20060268896A1 (en) | 2005-05-31 | 2006-11-30 | Sakari Kotola | System and method for services functionality |
-
2002
- 2002-10-31 US US10/284,135 patent/US6909721B2/en not_active Expired - Lifetime
-
2003
- 2003-09-16 US US10/662,407 patent/US7590097B2/en active Active
- 2003-10-30 CN CNB2003801023759A patent/CN100550795C/en not_active Expired - Lifetime
- 2003-10-30 CA CA2683998A patent/CA2683998C/en not_active Expired - Fee Related
-
2005
- 2005-04-11 US US11/102,761 patent/US7492777B2/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN100550795C (en) | 2009-10-14 |
| US20040087274A1 (en) | 2004-05-06 |
| US7492777B2 (en) | 2009-02-17 |
| US6909721B2 (en) | 2005-06-21 |
| CN1708924A (en) | 2005-12-14 |
| US20050185660A1 (en) | 2005-08-25 |
| CA2683998A1 (en) | 2004-05-13 |
| US7590097B2 (en) | 2009-09-15 |
| US20040085947A1 (en) | 2004-05-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2683998C (en) | Device detection and service discovery system and method for a mobile ad hoc communications network | |
| JP4563425B2 (en) | Device detection and service discovery system and method for mobile ad hoc communication networks | |
| EP1517488A2 (en) | Mechanism for improving connection control in peer-to-peer ad-hoc networks | |
| US7313120B2 (en) | Application control in peer-to-peer ad-hoc communication networks | |
| EP1440588B1 (en) | Customized messaging between wireless access point and services | |
| KR101088718B1 (en) | Mobile wlan gateway | |
| US8442549B2 (en) | Automatic discovery and connectivity protocol for bluetooth scatternet formation | |
| CN104967614A (en) | Method and device for supporting failover between network protocols | |
| US7894829B2 (en) | Wireless communication terminal and method for checking wireless broadband internet service area using position detection system | |
| US9301078B2 (en) | Network-intelligent scanner | |
| WO2008024099A2 (en) | Peer-to-peer network and user information discovery and sharing for mobile users and devices | |
| KR100938471B1 (en) | Discovery engine for resource sharing using wireless sensor network, the discovery metohd and the registration method thereof | |
| Hämäläinen et al. | Service Discovery in Mobile Peer-to-Peer Environment | |
| CN117407026A (en) | Intelligent device firmware upgrading method and device, medium and device | |
| JP2004128753A (en) | Public radio internet service system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20141030 |