Identifying and accessing a network device via wireless communication
Abstract
A method for wireless communication, which comprises: the reception (504) in a mobile device (114) from a server (110), through a wireless communication channel (124), of a request for an identifier (104 and 108) corresponding to a network device (102, 102 ', 106 and 106'); transmitting (506) from the mobile device to the identifier server in response to the request; receiving (508) on the mobile device from the server a network identifier corresponding to the network device; the use (510) in the mobile device of the network identifier to establish a communication with the network device through the wireless communication channel; and performing (512) a synchronization process between the mobile device and the network device, wherein the synchronization process includes synchronizing the data stored in the mobile device and the network device.

Term
0.1 yearsto projected expiry
Projected expiry 17 November 2026, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
13 claims: 4 independent, 9 dependent
- 1ES 2 804 465 T3 REIVINDICACIONES 1. Un método para la comunicación inalámbrica, el cual comprende:la recepción (504) en un dispositivo móvil (114) desde un servidor (110), a través de un canal de comunicación inalámbrica (124), de una solicitud de un identificador (104 y 108) correspondiente a un dispositivo de red (102, 102’, 106 y 106');la transmisión (506) desde el dispositivo móvil al servidor del identificador en respuesta a la solicitud;la recepción (508) en el dispositivo móvil desde el servidor de un identificador de red correspondiente al dispositivo de red;el uso (510) en el dispositivo móvil del identificador de red para establecer una comunicación con el dispositivo de red a través del canal de comunicación inalámbrica;y la realización (512) de un proceso de sincronización entre el dispositivo móvil y el dispositivo de red, en donde el proceso de sincronización incluye la sincronización de los datos almacenados en el dispositivo móvil y el dispositivo de red.
- 2El método de la reivindicación 1, en donde dicho identificador (104 y 108) comprende además una contraseña.
- 3Un método para la comunicación inalámbrica, el cual comprende:la transmisión desde un servidor (110) a un dispositivo móvil (114) de una solicitud, a través de un canal de comunicación inalámbrica (124), de un identificador correspondiente a un dispositivo de red (102, 102’, 106 y 106’);la recepción en el servidor desde el dispositivo móvil en respuesta a la solicitud del identificador a través del canal de comunicación inalámbrica;y después de recibir el identificador, la transmisión desde el servidor al dispositivo móvil de un identificador de red correspondiente al dispositivo de red, en el que el identificador de red permite que el dispositivo móvil establezca una comunicación con el dispositivo de red a través de una comunicación inalámbrica.
- 4El método de la reivindicación 1 o la reivindicación 3, en donde dicho identificador de red (104 y 108) es una dirección MAC (Control de acceso a medios) o una dirección IP de Protocolo de Internet.
- 5El método de la reivindicación 1 o la reivindicación 3, en donde dicho identificador (104 y 108) comprende un nombre de usuario.
- 6El método de la reivindicación 1 o la reivindicación 3, en donde dicho identificador (104 y 108) comprende una contraseña.
- 7El método de la reivindicación 1 o la reivindicación 3, en donde dicho canal de comunicación inalámbrica (124) se selecciona de entre la comunicación Wi-Fi®, la comunicación inalámbrica Bluetooth®, la comunicación celular, el Sistema Global para Comunicaciones Móviles (GSM), la comunicación de servicio general de paquetes vía radio (GPRS), la tecnología de comunicación de acceso múltiple por división de código (CDMA), la tecnología de comunicación de entorno GSM de datos mejorados (EDGE), la tecnología de comunicación de acceso múltiple por división de tiempo (TDMA), la tecnología de comunicación Evolution Data Only o Evolution Data Optimized (EVDO), la tecnología de comunicación de tercera generación inalámbrica (3G), la tecnología de Sistema universal de telecomunicaciones móviles (UMTS), la tecnología de comunicación de acceso múltiple por división de código de banda ancha (W-CDMA) y la tecnología de comunicación de acceso múltiple por división de código síncrono de división de tiempo (TDSCDMA).
- 8El método de la reivindicación 1 o la reivindicación 3, en donde dicho identificador de red (104 y 108) es estático o dinámico.
- 9Un dispositivo móvil (114) para la comunicación inalámbrica, comprendiendo este dispositivo móvil:medios para recibir de un servidor (110) a través de un canal de comunicación inalámbrica una solicitud de un identificador correspondiente a un dispositivo de red;medios para transmitir a dicho servidor el identificador en respuesta a dicha solicitud;medios para recibir de dicho servidor un identificador de red correspondiente al dispositivo de red;medios para usar el identificador de red para establecer una comunicación con el dispositivo de red a través del canal de comunicación inalámbrica;y medios para realizar un proceso de sincronización con el dispositivo de red, en donde el proceso de sincronización incluye la sincronización de datos almacenados en el dispositivo móvil y el dispositivo de red.
- 10El dispositivo móvil de la reivindicación 9, en donde el identificador comprende además una contraseña.
- 11Un servidor (110) para la comunicación inalámbrica, comprendiendo este servidor:ES 2 804 465 T3 medios para transmitir a un dispositivo móvil (114) una solicitud a través de un canal de comunicación inalámbrica (124) para un identificador correspondiente a un dispositivo de red;medios para recibir desde el dispositivo móvil, en respuesta a la solicitud, el identificador a través del canal de comunicación inalámbrica;y 5 medios para transmitir al dispositivo móvil, después de recibir el identificador, un identificador de red correspondiente al dispositivo de red, en donde el identificador de red permite al dispositivo móvil establecer una comunicación con el dispositivo de red a través de una comunicación inalámbrica.
- 12El dispositivo móvil (114) de la reivindicación 9 o el servidor de la reivindicación 11, en donde el mencionado 10 identificador de red es una dirección MAC (Control de acceso a medios) o una dirección IP de protocolo de Internet.
- 13El dispositivo móvil (114) de la reivindicación 9 o el servidor de la reivindicación 11, en donde el mencionado identificador comprende una contraseña.
Independent claims13
76 paragraphs in 10 sections, as filed
ES 2 804 465 T3
DESCRIPTION
Identification and access to a network device through wireless communication
BACKGROUND
[0001] Computers and handheld computing devices have become comprehensive tools that are used in a wide variety of different applications. In addition, the functionality of a computer system or handheld computing device can be enhanced by coupling these separate types of devices together to form a network environment. Within a network environment, users can easily exchange files, share information stored in a common database, pool resources, and communicate by email.
[0002] It will be appreciated that there are different types of conventional network environments. For example, one type of network environment is known as a wireless local area network, generally known as a WLAN (Wireless Local Area Network). WLANs allow a computer system or handheld computing device to connect to a local area network (LAN). It should be noted that the local area network may have multiple computers or handheld computing devices connected by cable or wirelessly, so that its users have the ability to access the same information and share data. However, there are disadvantages associated with WLANs when communicating with a LAN. For example, a LAN may have one hundred or more computers and / or handheld computing devices connected to it. Thus, if a user wants their LAN-connected handheld computing device over a WLAN to communicate with a specific LAN-connected computer that they have not previously communicated with, the typical user may be faced with a time-consuming task. and / or that it takes a long time to identify that computer from among the others connected to the LAN.
[0003] US 2002/174195 A1 and WO 03/021978 A represent the relevant prior art.
SUMMARY
[0004] An embodiment of the invention is a method that includes a mobile device that receives, through a wireless communication channel, a request for an identifier corresponding to a network device. The mobile device transmits the identifier. The mobile device receives a network identifier corresponding to the network device. The mobile device uses the network identifier to communicate with the network device through the wireless communication channel.
[0005] Still another embodiment of the invention provides a method that includes a server that transmits a request, through a wireless communication channel, for an identifier corresponding to a network device. The server receives the identifier through the wireless communication channel. After receiving the identifier, the server transmits a corresponding network identifier to the network device. It should be noted that the network identifier allows a mobile device to establish communication with the network device through wireless communication.
[0006] Still other embodiments disclose a mobile device and a server corresponding to the above methods. Although particular embodiments of the present invention have been specifically described within this summary, it will be appreciated that the invention is not limited to these embodiments. The invention is intended to encompass alternatives, modifications and equivalents that may be included within the scope of the invention, as interpreted in accordance with the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007]
Figure 1 is a block diagram of an illustrative system, in accordance with various embodiments of the invention, for identifying and accessing a computer attached to a network through a server.
Figure 2 is a block diagram of an illustrative system, in accordance with various embodiments of the invention, for identifying and accessing a computer coupled to a network.
Figure 3 is a flow chart of a method, in accordance with various embodiments of the invention, for identifying and accessing a computer coupled to a network.
Figure 4 is a flow chart of another method, in accordance with various embodiments of the invention, for identifying and accessing a computer coupled to a network.
ES 2 804 465 T3
Figure 5 is a flow diagram of a method, according to various embodiments of the invention, for a mobile device to identify and access a computing device coupled to a network.
Figure 6 is a flow chart of another method, according to various embodiments of the invention, for a mobile device to identify and access a computing device coupled to a network.
DETAILED DESCRIPTION
[0008] In the following, reference will be made in detail to various embodiments according to the invention, examples of which are illustrated in the accompanying drawings. Although the invention will be described in conjunction with various embodiments, it will be understood that these various embodiments are not intended to limit the invention. Rather, the invention is intended to encompass alternatives, modifications, and equivalents that may be included within the scope of the invention, as interpreted in accordance with the claims. Furthermore, in the following detailed description of various embodiments in accordance with the invention, numerous specific details are set forth to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the invention can be practiced without these specific details. In other cases, well-known methods, procedures, components, and circuits have not been described in detail in order not to unnecessarily obscure aspects of the invention.
[0009] Some parts of the detailed descriptions, shown below, are presented in terms of procedures, operations, logic blocks, processing and other symbolic representations of operations in data bits that can be executed in the memory of the computer. These descriptions and representations are the means used by experts in data processing techniques to convey, as efficiently as possible, the essentials of their work to other experts in the field. A procedure, a computer-executed operation, a logic block, a process, etc., are, at present and generally, intended to be a coherent sequence of operations or instructions that result in a desired result. Operations can be those that require physical manipulations of physical quantities. Generally, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. At times, it has been practical, mainly for common usage reasons, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or similar concepts.
However, it should be noted that all of these and similar terms must be associated with the appropriate physical quantities and merely constitute convenient labels applied to these quantities. Unless specifically stated otherwise, as is apparent from the following discussions, it will be appreciated that throughout the invention, analyzes using terms such as "use", "transmit", "perform", "couple", " access "," receive "," send "," generate "," determine "," store "or similar terms, refer to the actions and processes of a computer system, or a similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the records and memories of the computer system into other data similarly represented as physical quantities within the memories or records of the computer system or other storage, transmission or display devices of similar information.
[0011] Figure 1 is a block diagram of an illustrative system 100, in accordance with various embodiments of the invention, for identifying and accessing a computer (eg, 102) coupled to a network 118 through a server 110 For example, within system 100, communication may be established between mobile device 114 and server computer 110 through communication network 118. It should be noted that mobile device 114 can communicate with network 118 through one or more wireless communication channels 120. Once communication is established between server 110 and mobile device 114, server 110 may request that mobile device 114 transmit a username and password (or any other identifier or identifiers) that correspond to a computer (for example , 102) with which the mobile device 114 wishes to establish a communication later. In response to the request, mobile device 114 may transmit to server 110 the username and password (or any other identifier or identifiers) corresponding to computer 102.
[0012] After receiving the transmitted username and password, the server 110 may perform a verification or authentication of the username and password to determine if they are valid. If they are not, the server 110 may notify the mobile device 114 that the received username and password are invalid. However, if the username and password are valid, the server 110 can determine if the computer 102 that is associated with the received username and password is currently attached to the network 118. If not, the server 110 notifies mobile device 114 that computer 102 is not currently coupled to network 118. However, if the computer 102 is currently coupled to the network 118, the server 110 can determine the unique network identifier (eg, 104) of the computer 102. The server 110 can then transmit the network identifier 104 of the computer. 102 to the mobile device 114. Upon receipt of the network identifier from the
ES 2 804 465 T3 computer 102, the mobile device 114 can use it to locate and establish a communication with the computer 102 through the network 118 and the wireless communication channel 120. Once the communication is established, the mobile device 114 can access to data stored in computer 102 and vice versa. For example, mobile device 114 and computer 102 can synchronize the data stored on both devices.
[0013] System 100 includes mobile device 114, server 110, and computers 102 and 106, each of which may be coupled to network 118. It should be noted that server 110 and computer 102 can be coupled to network network 118 via cable communication technology 126 and 122, respectively, as indicated by solid lines. Computer 106 and mobile device 114 may be coupled to network 118 through one or more wireless communication channels 124 and 120, respectively, as indicated by dashed lines. However, it is understood that server 110 and computers 102 and 106 may each be coupled to network 118 using wired or wireless communication technology. It will be appreciated that server 110 and computers 102 and 106 can be implemented in a wide variety of ways. For example, the server 110 and the computers 102 and 106 may each be implemented as, but not limited to, a desktop computer system, a portable computer system, a workstation, a computing device, a mainframe computer system. or a portable computing device. It should be noted that system 100 may include one or more computers similar to computer 102 or 106. Additionally, server 110 may be implemented as a single physical computing device or as multiple physical computing devices. It is understood that mobile device 114 can be implemented in a wide variety of ways. For example, mobile device 114 can be implemented as, but not limited to, a mobile phone, a mobile computing device, a handheld portable computing device, and the like.
[0014] Within system 100 of Figure 1, mobile device 114 may include memory 116 that can be implemented with, among others, volatile and / or non-volatile memory. It should be noted that the username and password corresponding to the computer 102 that can be transmitted by the mobile device 114 can be stored in the memory 116. It is understood that the server 110 can include a memory 112 that can be implemented with, among others, a memory volatile and / or non-volatile. The network identifiers (eg, 104 and 108) associated with the computers 102 and 106 may be stored in the memory 112 of the i1o server, respectively. Within system 100, network identifiers (eg, 104 and 108) can be dynamic or static.
[0015] For example, if the network identifiers (for example, 104 and 108) of system 100 are dynamic, server 110 can use memory 112 to store one or more look-up tables (not shown) that associate the identifier of current network of each computer communicatively coupled to network 118 with its corresponding username and password (or any other identifier or identifiers). In this way, after receiving the username and password sent by the mobile device 114, the server 110 can access one or more look-up tables to determine which current network identifier (for example, 104 or 108) corresponds to the username and password received (or any other identifier or identifiers). Once the current network identifier is determined (eg 108), server 110 can send or transmit it to mobile device 114 via network 118. It is understood that a variation of this operation is that if the network identifier (eg, 104 or 108) is dynamic, mobile device 114 may send the latest network identifier to server 110, which may then send the updated network identifier to mobile device 114.
[0016] In Figure 1, if the network identifiers (for example, 104 and 108) of the system 100 are static or fixed, the server 110 can determine which network identifier corresponds to the username and password received from at least two different ways. For example, in one embodiment, when the username and password sent by mobile device 114 is received, server 110 can query any computer (eg, 102 and 106) coupled to network 118 to determine which computer, if any. is that there is one, it is associated with the username and password received. If there is no computer associated with the received username and password, the server 110 notifies the mobile device over the network 118. However, if a computer (eg 102) is associated with the username Received username and password, server 110 can then determine the network identifier (eg, 104) of computer 102 and then transmit it to mobile device 114.
In another embodiment, server 110 may use memory 112 to store one or more look-up tables (not shown) that associate the static network identifier of each computer attached to network 118 with its corresponding username and password. . In this way, after receiving the username and password sent by the mobile device 114, the server 110 can access one or more look-up tables to determine which static network identifier (for example, 104 or 108) corresponds to the username and password received. Once the static network identifier is determined (eg, 108), the server 110 can send or transmit it to the mobile device 114 over the wireless network 118. It should be noted that after receiving the static network identifier (for example, 108), the mobile device 114 can store it, thus allowing the mobile device 114 to establish communication with the computer (for example, 102) corresponding to the identifier. Static network code received (eg 108) at any time that is desirable. It is understood that network identifiers 104 and 108 can be implemented in a wide variety of ways. For example, each of
ES 2 804 465 T3 network identifiers 104 and 108 can be implemented as, among others, a MAC address (Media Access Control, "Media Access Control"), an Internet Protocol (IP, Internet Protocol) address or the like. . Each of the network identifiers 104 and 108 can be implemented as a unique identifier.
In system 100, network 118 can be implemented in a wide variety of ways. For example, network 118 may be implemented with, among others, one or more wired and / or wireless communication technologies. It should be noted that wireless communication technologies may include, but are not limited to, Wi-Fi® (Wireless Fidelity) communication technology, Bluetooth® wireless communication technology, cellular communication technology, Global System for Mobile Communications technology ( GSM, Global System for Mobile Communications), the communication technology for general packet radio service (GPRS, General Packet Radio Service), Code Division Multiple Access (CDMA) communication technology, Enhanced Data GSM Environment (EDGE) communication technology, Time Division Multiple Access communication technology (TDMA, Time Division Multiple Access), Evolution Data Only or Evolution Data Optimized (EVDO) communication technology, third-generation wireless (3G) communication technology, Universal Mobile Telecommunications System (UMTS) technology, Wideband Code Division Multiple Access (W-CDMA) communication technology, Multiple access communication technology by Time Division Synchronous Code Division Multiple Access (TDSCDMA), any wireless communication technology or any combination thereof. It will be appreciated that the wireless communication channel (s) 120 used by the mobile device 114 may be implemented with, but are not limited to, one or more of the wireless communication technologies mentioned herein. Thus, mobile device 114, server 110, and computers 102 and 106 are implemented to communicate over network 118.
In Figure 1 it can be seen that the username and password that can be requested by the server 110 and can be transmitted by the mobile device 114, can each be a unique identifier, or together they can be an identifier unique one corresponding to a computer (eg 102) with which the mobile device 114 would later wish to establish communication. Furthermore, the username and password that can be requested by the server 110 and transmitted by the mobile device 114 can be replaced by any type of identifier or unique identifiers corresponding to a computer (for example, 102) with which the mobile device 114 would like to establish communication later. Also, in various embodiments, the username and password can correspond to any shared network drive coupled to wireless network 118.
According to various embodiments, it should be noted that before any of the operations of the system 100 begins, the mobile device 114 and the computer (eg, 102) with which you want to establish communication have not been previously communicated. It will be appreciated that additional elements or components can be included as part of system 100. Furthermore, fewer elements or components can be used within system 100. In various embodiments, a user of mobile device 114 can perform the operations described with reference to system 100 automatically and without any interaction. It is understood that the operations described with reference to the system 100 can be performed by software, firmware, electronic hardware, or any combination thereof.
[0021] Figure 2 is a block diagram of an illustrative system 200, in accordance with various embodiments of the invention, for identifying and accessing a computer (eg, 106 ') coupled to a network 118. For example, within From system 200, wireless communication can be established between mobile device 114 and communication network 118. It should be noted that mobile device 114 can communicate with network 118 through one or more wireless communication channels 120. Once communication is established between mobile device 114 and network 118, mobile device 114 can receive a listing of any computers (eg, 102 'and 106') that are currently coupled to the network 118. Mobile device 114 can determine if computer 106 '(with which it would like to establish communication) is currently communicatively coupled to network 118. It should be noted that this determination may involve the use of a username and password ( or any other identifier (s)) that are associated with the computer 106 '. If it is determined that computer 106 'is currently communicatively coupled to network 118, mobile device 114 may use the username and password to establish communication with computer 106' over network 118. Once Once communication is established, mobile device 114 can access data stored in computer 106 'and vice versa. For example, mobile device 114 and computer 106 'can perform a synchronization of the data stored on both devices.
Note that system 200 includes a mobile device 114 and computers 102 'and 106', each of which may be coupled to network 118. Note that computer 102 'can be coupled to network 118 via cable communication technology 122, as indicated by a solid line. Computer 106 'and mobile device 114 may be coupled to network 118 through one or more wireless communication channels 124 and 120, respectively, as indicated by dashed lines. However, it is understood that
The computers 102 'and 106' may be coupled to the network 118 through the use of wired or wireless communication technology. Computers 102 'and 106' can be implemented in a wide variety of ways. For example, each of the computers 102 'and 106' may be implemented as, but not limited to, a desktop computing system, a portable computing system, a workstation, a computing device, a central unit computing system, or a computing device. laptop. It should be noted that system 200 may include one or more computers similar to computer 102 'or 106'. Mobile device 114 can be implemented in a wide variety of ways. For example, mobile device 114 can be implemented as, but not limited to, a mobile phone, a mobile computing device, a handheld portable computing device, and the like.
[0023] In system 200 of Figure 2, mobile device 114 may include memory 116 that may be implemented with, among others, volatile and / or non-volatile memory. Note that the username and password for computer 106 'that can be transmitted by mobile device 114 can be stored in memory 116. Identifiers 202 and 204 associated with computers 102' and 106 ', respectively, can be stored in your respective computer. It is understood that identifiers 202 and 204 can be implemented in a wide variety of ways. For example, each of identifiers 202 and 204 may be implemented as, but not limited to, a unique username and password combination, a unique username, a unique password, or any type of unique identifier or identifiers.
In Figure 2, in one embodiment, it should be noted that mobile device 114 can query any computer (eg, 102 'and 106') communicatively coupled to network 118 to determine which computer, if any, is that there is one, it is associated with the username and password. If there is no computer associated with the username and password, the mobile device 114 may provide a notification about it to the user. However, if a computer (eg, 106 ') is associated with the received username and password, the mobile device 114 can establish communication with the computer 106' over the network 118. In various embodiments, the username and password can correspond to a computer (eg, 106 ') or to any shared network drive attached to network 118.
In system 200, network 118 can be implemented in a wide variety of ways. For example, network 118 may be implemented with, among others, one or more wired and / or wireless communication technologies. It should be noted that wireless communication technologies may include, but are not limited to, Wi-Fi® (Wireless Fidelity) communication technology, Bluetooth® wireless communication technology, cellular communication technology, Global System for Mobile Communications technology ( GSM), General Packet Radio Service (GPRS) communication technology, Code Division Multiple Access (CDMA) communication technology, Enhanced data GSM environment communication technology (EDGE), Time Division Multiple Access (TDMA) communication technology, Evolution Data Only or Evolution Data Optimized (EVDO) communication technology, third-party communication technology Wireless generation (3G), Universal Mobile Telecommunications System (UMTS) technology, Broadband code division multiple access (W-CDMA) communication technology, time division synchronous code division multiple access (TDSCDMA) communication technology, any wireless communication technology, or any combination thereof. It will be appreciated that the wireless communication channel (s) 120 used by the mobile device 114 may be implemented with one or more of the wireless communication technologies mentioned herein, but are not limited thereto. Thus, mobile device 114 and computers 102 'and 106' are implemented to communicate over network 118.
According to various embodiments, it should be noted that before any of the operations of the system 200 of Figure 2 begin, the mobile device 114 and the computer (eg, 106 ') with which you want to establish communication have not been previously communicated. Note that additional elements or components can be included as part of system 200. Also, fewer elements or components can be used in system 200. In various embodiments, a user of mobile device 114 can perform the operations described with reference to system 200 automatically and without any interaction. It is understood that the operations described with reference to system 200 can be performed by software, firmware, electronic hardware, or any combination thereof.
[0027] Figure 3 is a flow diagram of a method 300, in accordance with various embodiments of the invention, for identifying and accessing a computer communicatively coupled to a network through a server. Method 300 includes illustrative processes of various embodiments of the invention that may be carried out by a processor or processors and electrical components under the control of instructions (or code), eg, software, readable and executable by a computing device. The instructions (or code) readable and executable by the computing device may reside, for example, in data storage functions such as volatile memory, non-volatile memory and / or the mass storage of data that a computing device can utilize. However, the instructions (or code) readable and executable by a computing device may reside on any type of media readable by a computing device. Although specific operations are described in method 300, such operations are illustrative. That is, the method 300 may not include all of the operations illustrated in Figure 3. In addition, the method 300 may include various other operations and / or variations of the operations.
ES 2 804 465 T3 operations shown in Figure 3. Similarly, the sequence of operations of method 300 can be modified. It should be noted that method 300 operations can be performed using software, firmware, electronic hardware, or any combination thereof.
[0028] Specifically, communication can be established between a mobile device and a server computer through a communication network. Once communication is established, the server may request that the mobile device transmit a user name and password corresponding to the computer with which the mobile device subsequently wishes to establish communication. The mobile device can wirelessly transmit the username and password corresponding to the computer to the server. The server receives the transmitted username and password. The server determines whether the computer associated with the received username and password is currently communicatively coupled to the network. If not, the server can notify the mobile device that the computer is not currently communicatively coupled to the network. However, if it is determined that the computer is currently communicatively coupled to the network, the server can determine the unique network identifier of that computer. The server can send the computer's network identifier to the mobile device. The mobile device wirelessly receives the network identifier from the computer, which it can use to locate and communicate with the computer over the network. Once communication is established, the mobile device can access the data stored on the computer and vice versa. For example, the mobile device and the computer can synchronize the data stored on both devices. According to various embodiments, it should be noted that the method computer 300 can be substituted for, but is not limited to, any network share.
[0029] In operation 302 of Figure 3, a communication can be established between a mobile device (eg 114) and a server computer (eg 110) through a communication network (eg 118) . It is understood that operation 302 can be implemented in a wide variety of ways. For example, operation 302 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0030] In step 304, once a communication is established between the mobile device and the server, the server can request that the mobile device transmit a corresponding username and password to the computer (for example, 102 or 106) with which the mobile device subsequently wishes to establish a communication. It will be appreciated that step 304 can be implemented in a wide variety of ways. For example, step 304 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0031] In operation 306 of Figure 3, the mobile device can wirelessly transmit to the server via the network the username and password corresponding to the computer. It will be appreciated that operation 306 can be implemented in a wide variety of ways. For example, operation 306 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0032] In step 308, the server can receive the transmitted username and password. It is understood that operation 308 can be implemented in a wide variety of ways. For example, operation 308 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 310 of Figure 3, the server can determine or find out if the computer associated with the received username and password is currently communicatively coupled to the network. If it is not, process 300 can proceed to step 314. However, if the computer is communicatively coupled to the network in step 310, process 300 can proceed to step 312. It is understood that operation 310 can be implemented in a wide variety of ways. For example, operation 310 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 314, the server notifies the mobile device that the computer is not currently communicatively coupled to the wireless network. It is understood that operation 314 can be implemented in a wide variety of ways. For example, the notification in step 314 can be implemented as, among others, a text message that can ultimately be read by a user of the mobile device 114, a notification signal recognized by the mobile device 114, an audio message. that can ultimately be heard by a user of mobile device 114, a graphic image that includes a message that can be viewed by a user of mobile device 114, and the like. It should be noted that operation 314 can be implemented in any manner similar to that described herein, but is not limited thereto. Upon completion of operation 314, method 300 can be exited.
[0035] In step 312 of Figure 3, the server can determine or find out the unique network identifier (eg, 104 or 108) associated with the computer. It will be appreciated that operation 312 can be implemented in a wide variety of ways. For example, operation 312 can be implemented in any manner similar to that described herein, but is not limited thereto.
ES 2 804 465 T3
In step 316, once determined, the server can transmit or send to the mobile device the network identifier associated with the computer. It is understood that operation 316 can be implemented in a wide variety of ways. For example, operation 316 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0037] In step 318 of Figure 3, the mobile device can wirelessly receive the network identifier from the computer, which the mobile device can use to locate and establish communication with the computer over the network. It will be appreciated that operation 318 can be implemented in a wide variety of ways. For example, operation 318 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 320, once communication between the mobile device and the computer is established, the mobile device can access the data stored in the computer and vice versa. It is understood that operation 320 can be implemented in a wide variety of ways. For example, in step 320, the mobile device and the computer can synchronize the data stored on both devices. It will be appreciated that operation 320 may be implemented in any manner similar to that described herein, but is not limited thereto. Upon completion of operation 320, method 300 can be exited.
[0039] Figure 4 is a flow diagram of a method 400, in accordance with various embodiments of the invention, for identifying and accessing a computer communicatively coupled to a network. Method 400 includes illustrative processes of various embodiments of the invention that may be carried out by one or more processors and electrical components under the control of instructions (or code), eg, software, readable and executable by a computing device. The instructions (or code) readable and executable by the computing device can reside, for example, in data storage functions such as volatile memory, non-volatile memory and / or the mass storage of data that can be used by a computing device. However, the instructions (or the code) readable and executable by the computing device may reside on any type of media that is readable by the computing device. Although specific operations are described in method 400, those operations are illustrative. That is, method 400 may not include all of the operations illustrated in Figure 4. In addition, method 400 may include various other operations and / or variations of the operations shown in Figure 4. Similarly, the sequence can be modified. method 400 operations. It should be noted that method 400 operations can be performed using software, firmware, electronic hardware, or any combination thereof.
[0040] Specifically, wireless communication can be established between a mobile device and a communication network. Once wireless communication has been established, the mobile device can wirelessly receive a listing or list of computers that are currently communicatively coupled to the communication network. The mobile device can determine whether a computer with which it would like to communicate is currently communicatively coupled to the network. It should be noted that this determination may include the use of a username and password associated with the computer. If the desired computer is not communicatively coupled to the network, method 400 can be abandoned. However, if it is determined that the desired computer is currently communicatively coupled to the network, the mobile device may use the username and password to establish communication with the computer over the network. Once communication is established, the mobile device can access the data stored on the computer and vice versa. For example, the mobile device and the computer can synchronize the data stored on the computer and the mobile device. According to various embodiments, it is noted that the method computer 400 can be substituted for, but is not limited to, any network share.
[0041] In operation 402 of Figure 4, wireless communication can be established between a mobile device (eg 114) and a communication network (eg 118). It is understood that operation 402 can be implemented in a wide variety of ways. For example, operation 402 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0042] In step 404, once wireless communication between the mobile device and the network is established, the mobile device can wirelessly receive a list or list of computers (eg 102 'and 106') that are currently communicatively coupled to the network. It will be appreciated that operation 404 can be implemented in a wide variety of ways. For example, operation 404 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 406 of Figure 4, the mobile device can determine whether a computer (eg 102 'or 106') with which it would like to establish communication is currently communicatively coupled to the network. It should be noted that this determination at step 406 may include the use of a username and password (eg, 202) associated with the computer (eg, 102 '). If the computer is not communicatively coupled to the network, method 400 can be abandoned. However, if the computer is
ES 2 804 465 T3 currently communicatively coupled to the network at step 406, method 400 can proceed to step 408. It should be noted that step 406 can be implemented in a wide variety of ways. For example, operation 406 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0044] In step 408, the mobile device can use the username and password to establish communication with the computer over the network. It will be appreciated that operation 408 can be implemented in a wide variety of ways. For example, operation 408 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0045] In operation 410 of Figure 4, once communication is established between the mobile device and the computer, the mobile device can access the data stored in the computer and vice versa. It is understood that operation 410 can be implemented in a wide variety of ways. For example, in one embodiment, the mobile device and the computer can synchronize the data stored in the computer and the mobile device. It should be noted that operation 410 can be implemented in any manner similar to that described herein, but is not limited thereto. After step 410 is completed, process 400 can be exited.
[0046] Figure 5 is a flow chart of a method 500, in accordance with various embodiments of the invention, for a mobile device to identify and access a computing device communicatively coupled to a network. Method 500 includes illustrative processes of various embodiments of the invention that may be carried out by a processor or processors and electrical components under the control of instructions (or code), eg, software, readable and executable by a computing device. The instructions (or code) readable and executable by the computing device can reside, for example, in data storage functions such as volatile memory, non-volatile memory and / or the mass storage of data that can be used by a computing device. However, the instructions (or code) readable and executable by the computing device may reside on any type of media readable by the computing device. Although specific operations are described in method 500, those operations are illustrative. That is, method 500 may not include all of the operations illustrated in Figure 5. In addition, method 500 may include several other operations and / or variations of the operations shown in Figure 5. Similarly, the sequence can be modified. of method 500 operations. It should be noted that method 500 operations can be performed using software, firmware, electronic hardware, or any combination thereof.
[0047] Specifically, a communication can be established between a mobile device and a server through one or more wireless communication channels. The mobile device may receive a request for one or more identifiers corresponding to a computing device. The mobile device may transmit the identifier or identifiers. The mobile device may receive one or more network identifiers corresponding to the computing device. The mobile device may use the network identifier (s) to communicate with the computing device through the wireless communication channel (s). The mobile device can perform a synchronization process with the computing device. In accordance with various embodiments, it will be appreciated that the method computing device 500 may be substituted for any shared network drive.
[0048] In operation 502 of Figure 5, a communication can be established between a mobile device (eg 114) and a server (eg 110) through one or more wireless communication channels (eg 120 ). It is understood that operation 502 can be implemented in a wide variety of ways. For example, operation 502 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0049] At step 504, the mobile device may receive a request for one or more identifiers corresponding to a computing device (eg, 102 or 106). It will be appreciated that operation 504 can be implemented in a wide variety of ways. For example, operation 504 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0050] In step 506 of Figure 5, the mobile device may transmit the identifier or identifiers (eg, username and / or password). It should be noted that operation 506 can be implemented in a wide variety of ways. For example, operation 506 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 508, the mobile device may receive one or more network identifiers (eg, 104 or 108) corresponding to the computing device. It will be appreciated that operation 508 can be implemented in a wide variety of ways. For example, operation 508 can be implemented in any manner similar to that described herein, but is not limited thereto.
ES 2 804 465 T3
[0052] In step 510 of Figure 5, the mobile device can use the network identifier or identifiers to establish communication with the computing device (eg 102 or 106) through the wireless communication channel (s) . It is understood that operation 510 can be implemented in a wide variety of ways. For example, operation 510 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0053] In step 512, the mobile device can perform a synchronization process with the computing device. It should be noted that operation 512 can be implemented in various ways. For example, operation 512 can be implemented in any manner similar to that described herein, but is not limited thereto. Upon completion of operation 512, process 500 can be exited.
[0054] Figure 6 is a flow chart of a method 600, in accordance with various embodiments of the invention, for a mobile device to identify and access a computing device coupled to a network. Method 600 includes illustrative processes of various embodiments of the invention that may be carried out by a processor or processors and electrical components under the control of instructions (or code), eg, software, readable and executable by a computing device. The instructions (or code) readable and executable by the computing device can reside, for example, in data storage functions such as volatile memory, non-volatile memory and / or the mass storage of data that can be used by a computing device. However, the instructions (or code) readable and executable by the computing device may reside on any type of readable medium of the computing device. Although specific operations are described in method 600, those operations are illustrative. That is, method 600 may not include all of the operations illustrated in Figure 6. Furthermore, method 600 may include various other operations and / or variations of the operations shown in Figure 6. Similarly, the sequence of operations of method 600 can be modified. It should be noted that method 600 operations can be performed using software, firmware, electronic hardware, or any combination thereof.
[0055] Specifically, communication can be established between a mobile device and a network through one or more wireless communication channels. The mobile device may receive a list or a list of a plurality of computing devices coupled to the network. The mobile device may use the listing (or the list) and one or more identifiers corresponding to one computing device of the plurality of computing devices to determine whether the computing device is coupled to the network. As long as the computing device is coupled to the network, the mobile device can use the identifier or identifiers to establish communication with the computing device. The mobile device can perform a synchronization process with the computing device. In accordance with various embodiments, it will be appreciated that the method computing device 600 may be substituted for any shared network drive.
In operation 602 of Figure 6, a communication can be established between a mobile device (eg 114) and a network (eg 118) through one or more wireless communication channels (eg 120). It is understood that operation 602 can be implemented in a wide variety of ways. For example, operation 602 can be implemented in any manner similar to that described herein, but is not limited thereto.
In step 604, the mobile device may receive a listing or a list of a plurality of computing devices (eg, 102 'and 106') coupled to the network. It will be appreciated that operation 604 can be implemented in a wide variety of ways. For example, operation 604 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0058] In operation 606 of Figure 6, the mobile device can use the listing (or the list) and one or more identifiers corresponding to a computing device (for example, 102 'or 106') of the plurality of computing devices to determine if the computing device is coupled to the network. It should be noted that operation 606 can be implemented in a wide variety of ways. For example, operation 606 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0059] In step 608, as long as the computing device is coupled to the network, the mobile device can use the identifier or identifiers to establish communication with the computing device. It will be appreciated that operation 608 can be implemented in a wide variety of ways. For example, operation 608 can be implemented in any manner similar to that described herein, but is not limited thereto.
[0060] In operation 610 of Figure 6, the mobile device can perform a synchronization process with the computing device. It should be noted that operation 610 can be implemented in a wide variety of ways. For example, operation 610 can be implemented in any manner similar to that described herein, but is not limited thereto. Upon completion of operation 610, process 600 can be exited.
ES 2 804 465 T3
[0061] It is understood that a network device can be substituted for any computing device, computing system or computer mentioned herein (eg 102, 102 ', 106 and / or 106'). It should be noted that a network device may include, but is not limited to, a database, a server, a network share, a portable computing device, a mobile phone, a printer, a facsimile (fax) machine, a handheld computing device or any combination thereof.
[0062] Insofar as the embodiments of the invention described above can be implemented, at least partially, using a software-controlled programmable processing device, such as a processor, microprocessor, or other digital signal processing device, or a computer data processing apparatus or system, it will be appreciated that a computer program is provided to configure a device, programmable apparatus or system in order to implement the methods and devices described above as one aspect of the present invention; The computer program may be incorporated as source code and compiled for implementation in a processing device, apparatus, or system, or it may be incorporated as object code, for example. One skilled in the art will readily understand that the terms "computer" and "computing", in their most general sense, encompass programmable devices, such as those mentioned above, and data processing computer systems and apparatus.
[0063] Conveniently, the computer program is stored on a computer medium in machine-readable format, for example, in solid-state memory or magnetic memory, such as disk or tape, in particular CD-ROM and DVD. The computer program can be supplied from a remote source embedded in the communications medium such as an electronic signal, a radio frequency carrier wave, or optical carrier waves. Such computer carriers are also envisioned as aspects of the present invention.
[0064] The foregoing descriptions of various specific embodiments, in accordance with the invention, have been presented for illustrative and descriptive purposes. They are not intended to be exhaustive or limit the invention to the precise forms described, and obviously many modifications and variations are possible in light of the above descriptions. The invention can be interpreted in accordance with the claims and their equivalents.
Contents10
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
14 members in 9 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 282421 | United States of America | – | |
| 28242105 | United States of America | A | |
| 28242105 | United States of America | A | |
| 2006044606 | United States of America | W | |
| 2006044606 | United States of America | W | |
| 282421 | – | – | – |
| PCTUS2006044606 | – | – | – |
| US20050282421 | – | – | – |
| WO2006US44606 | – | – | – |
Members14
| Document | Office | Kind | |
|---|---|---|---|
| US2007115876A1 | United States of America | A1 | |
| WO2007061814A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007061814A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP1955524A2 | European Patent Office (EPO) | A2 | |
| US8688103B2 | United States of America | B2 | |
| US2014156795A1 | United States of America | A1 | |
| US9026092B2 | United States of America | B2 | |
| EP1955524B1 | European Patent Office (EPO) | B1 | |
| PT1955524T | Portugal | T | |
| DK1955524T3 | Denmark | T3 | |
| SI1955524T1 | Slovenia | T1 | |
| PL1955524T3 | Poland | T3 | |
| HUE050089T2 | Hungary | T2 | |
| ES2804465T3This record | Spain | T3 |
Numbers
- Publication
- 2804465
- Publication, DOCDB
- 2804465
- Publication, EPODOC
- ES2804465T
- Application
- 6837860
- Application, DOCDB
- 06837860
- Application, EPODOC
- ES20060837860T
Titles2
- Spanish
- Identificación y acceso a un dispositivo de red a través de una comunicación inalámbrica
- English
- Identification and access to a network device through wireless communication
Classification
- CPC, 5
- H04L61/45
- H04W8/24
- H04L67/04
- H04L61/00
- H04L67/51
- IPC, 2
- H04L29 08
- H04L29 12