EP3100225A1 - Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile - Google Patents

Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile

Info

Publication number
EP3100225A1
EP3100225A1 EP16721341.2A EP16721341A EP3100225A1 EP 3100225 A1 EP3100225 A1 EP 3100225A1 EP 16721341 A EP16721341 A EP 16721341A EP 3100225 A1 EP3100225 A1 EP 3100225A1
Authority
EP
European Patent Office
Prior art keywords
electronic device
computing device
mobile computing
unique identifier
user
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.)
Withdrawn
Application number
EP16721341.2A
Other languages
German (de)
English (en)
Other versions
EP3100225A4 (fr
Inventor
Jed Putterman
Brandon S. LAIDLAW
Margaret L. TAYLOR
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
MEDEA INC.
Original Assignee
Medea Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/789,648 external-priority patent/US10009709B2/en
Application filed by Medea Inc filed Critical Medea Inc
Publication of EP3100225A1 publication Critical patent/EP3100225A1/fr
Publication of EP3100225A4 publication Critical patent/EP3100225A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • FIG. 5 is a flow chart of an embodiment for implementing an electronic device management service.
  • FIG. 6 is a block diagram depicting an example computing device, in accordance with an embodiment of the present invention.
  • the sleeve may be plastic, polymer, rubber, or other flexible material.
  • the sleeve may stretch to conform to the shape of the object that it is fit around.
  • portable displays may be interchangeable between objects and be associated with the object it is attached to.
  • Other embodiments may include an electronic device molded or printed onto the outer surface of the object or embedded within the material of the object.
  • Such an electronic device may include a display that is visible when viewing the object.
  • the electronic device may be powered using a power source, such as a battery, solar cells, or other similar power sources.
  • the low power electronic display device 135 includes a wireless module that periodically broadcasts a low power radio signal 125.
  • the low power radio signal may be broadcast every second, every 2 seconds, every half second, every 10 seconds, or at some other interval.
  • the low power radio signal may be transmitted using a protocol such as
  • the mobile computing device 110 may establish and/or maintain a wireless connection with a wireless carrier and/or with a local area network (e.g., via a wireless access point attached to the local area network). Through the wireless connection to the wireless carrier or local area network (LAN), the mobile computing device may establish and/or maintain a connection to an electronic device management service 120. Responsive to receiving the low power radio signal, the mobile computing device 110 may generate a query that includes the received unique identifier (or a portion thereof, such as the major and minor) and information that identifies a user of the mobile computing device. The information that identifies the user of the mobile computing device may be user account information of a user logged into the electronic device controller application. The mobile computing device 110 may also determine its current location (e.g., latitude and longitude) and include the current location in the query. The mobile computing device 110 may then transmit the query to the electronic device management service 120 via the connection 132.
  • a wireless connection e.g., via a wireless access point attached to the local area network.
  • the mobile computing device 110 is able to quickly determine which low power electronic devices of interest (e.g., those manufactured by a particular OEM) are nearby without having to connect to every Bluetooth-enabled device and read its characteristics. This may reduce discovery time for Bluetooth devices from minutes down to seconds.
  • low power electronic devices of interest e.g., those manufactured by a particular OEM
  • this may be performed even if the user of the mobile computing device 110 does not have access to the low power electronic display device 135.
  • FIG. 2 is a block diagram depicting an example system architecture 200 including a low power electronic device 210, one or more computing devices 226, and a server computing device 250.
  • system architecture 200 corresponds to system architecture 100 of FIG. 1.
  • Low power electronic device 210 may be communicably coupled to the one or more mobile computing devices 226 via wireless connections. As discussed above, these wireless connections (e.g., Bluetooth connections) may be established responsive to server computing device 250 determining that the mobile computing devices
  • Display module 212 may include an electronic visual display that may be illuminated to display an image or alphanumeric message.
  • the image or alphanumeric message may be static or may be displayed in a manner that appears to show movement (e.g., motion picture or scrolling text).
  • the electronic visual display may include light emitting diodes (LEDs), organic light emitting diodes (OLEDs), liquid crystal display (LCD), or other similar display technology.
  • Display module 212 may have a variety of sizes and include pixels of various colors. In one example, display module 212 may cover a portion of an object's exterior face or the entire exterior face of the object in all angles (0 degrees to 360 degrees).
  • Sensor module 214 may include one or more sensor devices for gathering data associated with the object and/or low power electronic display device 210.
  • the sensor devices may include audio sensors (e.g., microphones), motion sensors (e.g., accelerometer, gyroscope, etc.), fluid measuring sensors (e.g., mechanical gyrator), lights sensors (e.g., ambient light sensor), location sensors (e.g., global positioning system sensors (GPS)), temperature sensor (e.g., thermometer), or other similar sensing devices.
  • Data generated by sensor module 214 may be forwarded by mobile computing devices 226 to server computing device 250 for processing. For example, an audio signal may be sent to server computing device 250 to perform speech to text processing.
  • Wireless module 216 may enable low power electronic device 210 to receive and transmit messages and commands.
  • Wireless module 216 may include a transmitter, receiver, transceiver, memory, antenna, and so forth for communicating with a computing device (e.g., with mobile computing devices 226).
  • wireless module 216 includes a Bluetooth wireless adapter capable of communicating using multiple different Bluetooth based protocols.
  • wireless module 216 may include a wireless adapter that uses protocols for Near Field Communication (NFC), Wi-Fi®, infrared (IR), Linux® wireless, Zigbee®, any other low frequency RF modulation, microwave, radar, or other similar connections.
  • NFC Near Field Communication
  • IR infrared
  • Linux® wireless Zigbee®
  • any other low frequency RF modulation microwave, radar, or other similar connections.
  • wireless module 216 when wireless module 216 receives a connection request from a mobile computing device 226, wireless module 216 checks for a password included in the connection request. Wireless module 216 checks the received password against a stored password in the memory 220. If the passwords match, then wireless module 216 permits a wireless connection to be established. If the passwords fail to match, then no connection may be established. Thus, in embodiments the lower power electronic device 210 may only accept application programming interface (API) requests that are sent with the correct password.
  • API application programming interface
  • Mobile computing devices 226 may be any portable devices capable of communicating with low power electronic device 210 that include an electronic device controller application 230 installed thereon. Examples include smart phones, tablet computers, laptops, etc.
  • Mobile computing devices 226 may include a listening module 228 and the electronic device controller 230.
  • Listening module 228 may run in a background of mobile computing devices 226 and may listen for low energy radio signals that include a unique identifier 222 of any low power electronic device 210 manufactured by a particular OEM. Such low energy radio signals may be short range signals that are periodically broadcast by the wireless module 216. Responsive to receiving such a low energy radio signal, listening module 228 may load electronic device controller application 230. Alternatively, listening module 228 may perform other operations such as generate a query and send the query to the server computing device 250.
  • electronic device controller application 230 is a program
  • electronic device controller application 230 may be a downloadable application for a mobile device.
  • mobile devices may include Android®, iPhone®, or Blackberry® devices capable of running a software application (e.g., Android Smart Bottle software App, iPhone Smart
  • electronic device controller application 230 may be firmware and/or a hardware logic on a mobile computing device 226.
  • Electronic device controller application 226 acts both as a controller for low power electronic devices (which may lack their own user interfaces) and as a proxy for providing network connectivity (e.g., an Internet connection) to the low power electronic devices 210.
  • electronic device controller application 230 includes a user interface 232, a device connecting module 234 and a proxy module 236.
  • Proxy module 236 communicates with electronic device management service 251 on behalf of low power electronic devices. Proxy module 236 may establish a connection to electronic device management service 251 on server computing device 250 via network 242.
  • Network 242 may include a public network (e.g., the Internet), a private network (e.g., a local area network (LAN) or wide area network (WAN)), or a combination thereof.
  • Network 242 may also include a wired network (e.g., Ethernet network), a wireless network (e.g., an 802.11 network or a Wi-Fi network), a cellular network (e.g., a Long Term Evolution (LTE) network), or combination thereof, and may include a wireless access point, network routers, switches or other similar network devices.
  • a public network e.g., the Internet
  • a private network e.g., a local area network (LAN) or wide area network (WAN)
  • Network 242 may also include a wired network (e.g., Ethernet network), a wireless network (e.g., an 802.11 network or a Wi-Fi network), a cellular network (e.g., a Long Term Evolution (LTE) network), or combination thereof
  • proxy module 236 may forward that data to server computing device 250 for processing by electronic device management service 251. Proxy module 236 may generate queries and/or other messages for electronic device management service 251, which may include the data received from the low power electronic device as well as other data generated or received by mobile computing device 226.
  • Data from the low power electronic device 210 may include a unique identifier assigned to the low power electronic device 210, a battery state of the low power electronic device, messages stored on the low power electronic device, acceleration data, speech data, rotational data, proximity sensor data, light sensor data, temperature data, and so on.
  • Data from the mobile computing device 226 may include location data, user account data, date and time, signal strength data (e.g., of the low energy radio signal received from the low power electronic device 210), and so on.
  • Electronic device management service 251 may include a rules engine 254
  • Proxy module 236 may then receive a response message from the electronic device management service 251 based on an output of the rules engine 254. For example, proxy module 236 may receive an indication as to whether the user of the mobile computing device has permission to access the low power electronic device 210. Proxy module 236 may additionally receive messages to be displayed to the user via user interface 232 and/or instructions to send messages and/or commands to the low power electronic device 210. Such messages and/or instructions may be sent to the low power electronic device 210 whether or not the user has access to the low power electronic device.
  • User interface 232 acts as a remote user interface for low power electronic device
  • the user interface may display a presence of the low power electronic device 210 as well as command options for controlling the low power electronic device 210.
  • One example command option includes a command to generate a new message and/or send the new message to the low power electronic device 210. If a user selects a generate message option, user interface 232 may present a virtual keyboard with
  • the set unique identifier command changes a value of a unique identifier assigned to the low power electronic device.
  • Low power electronic devices may be manufactured with a default identifier, and that identifier may be replaced with a unique identifier after the low power electronic device is powered on by a user for a first time.
  • the unique identifier is a pair of integers (e.g., a major and a minor as defined by the iBeacon protocol). These numerical values in one embodiment are each 2 byte values.
  • the two numerical values may be combined to create a single larger numerical value (e.g., a 4 byte numerical value). By combining, for example, two independent 2 byte values, each of which has 65,536 possible unique values into a single unique 4 byte value, the number of possible unique values is increased many times to 4,294,967,296 possible values.
  • Device connecting module 234 is responsible for establishing wireless
  • device connecting module 234 establishes a wireless connection to the low power electronic device responsive to determining that a user of the user device has permission to access the low power electronic device. Such a determination may be made in response to mobile computing device 226 receiving a response from electronic device management service 251 indicating the permission.
  • electronic device controller application 230 may cache information on the unique identifiers that the user has permission to access. Responsive to receiving a low power radio signal broadcast by low power electronic device 210, electronic device controller application 230 may compare the received unique identifier to cached unique identifiers. If the received unique identifier matches a cached unique identifier, then electronic device controller application 230 may determine that the user has permission to access the low power electronic device 210 without waiting for a response from electronic device management service 251.
  • device connecting module 234 may wait until an instruction to send a command to the low power electronic device 210 is received via the user interface (from a user) or from electronic device management service 215. Responsive to receiving such an instruction, device connecting module 234 may establish the wireless connection to low power electronic device 210. By waiting to establish the wireless connection until data is to be exchanged with the low power electronic device 210, a battery life of the low power electronic device may be conserved.
  • Server computing device 250 may be a desktop computer, rackmount server, blade server, or other physical machine used to host a server.
  • Server computing device 250 hosts electronic device management service 251.
  • server computing device 250 includes a virtual machine monitor (also referred to as a hypervisor) that hosts virtual machines, and the electronic device management service is a service that executes in a virtual machine hosted by the server computing device 250.
  • electronic device management service 251 may be a cloud based service that is hosted by Amazon's® Elastic Compute Cloud (EC2).
  • EC2 Amazon's® Elastic Compute Cloud
  • Authorization module 256 is responsible for determining whether a user of a mobile computing device 226 is authorized to access a low power electronic device.
  • Electronic device management service 251 may receive a query from a mobile computing device 226 (e.g., from a proxy module 236), the query including a unique identifier of a low power electronic device and user account information of a user of the mobile computing device.
  • Authorization module 256 may perform a lookup on the user account and the unique identifier, which may be stored in a data structure (e.g., a database, table, etc.) including assigned unique identifiers 262 and user accounts 264.
  • a user may have access to a low power electronic device if that user owns the device or if access to the device has been shared with the user (e.g., by the owner).
  • messaging module 258 sends a response message back to the mobile computing device 226 indicating that the user has access permissions. Otherwise the messaging module 258 may send a response indicating that the user does not have such access permissions.
  • a low power electronic device may have a default unique identifier, and may not be associated with any user account.
  • authorization module 256 may determine an unused unique identifier, and may assign that unused unique identifier to the low power electronic device.
  • Authorization module 256 may generate an ownership record for the user account associated with the received query, where the ownership record includes the unique identifier.
  • Messaging module 258 may transmit a response to the mobile computing device 226 from which the query was received, where the response includes the assigned unique identifier.
  • an owner may share ownership of the electronic device with other users.
  • the owner merely provides an address of the additional user (e.g., via the user interface 232 of an electronic device controller application 230 or a web interface provided by the electronic device management service 251).
  • Messaging module 258 then sends an offer email that includes a hyperlink to a location from which the electronic device controller application may be downloaded.
  • the recipient downloads and installs the electronic device controller application onto their computing device (e.g., onto a mobile computing device), that user may access the electronic device and perform actions such as set, modify and display messages on that electronic device as if it was their own.
  • an owner may revoke access privileges to an electronic device or a user with which access has been shared may terminate access privileges.
  • Rules engine 254 may include one or more rules, and may apply these rules to generate commands, perform actions, and/or generate messages based on received data. Actions that are performed may include sending messages and/or notifications to specific users (e.g., to owners), sending messages to mobile computing devices for presentation thereon, sending commands to mobile computing devices that cause them to connect to low power electronic devices and send or forward commands to those low power electronic devices (e.g., to display a message on a low power electronic device), and so on.
  • authorization module 256 is a component of rules engine 254, and is implemented via an authorization rule and/or a new device rule. Rules engine 254 may include any number of rules, which may be used to perform many different actions. Some example rules and resultant actions are provided, but should not be construed as limiting the scope of the rules engine.
  • a user of the computing device 240 may use the web browser to access a web page provided by electronic device management service 251.
  • the web page may indicate users who have come within range of low power electronic devices owned by the user, the times of such encounters, locations of those low power electronic devices, and so forth.
  • a user may send a response back to electronic device management service 251.
  • the response may include a command to send a message to the electronic device, a command to send a message to the mobile computing device and/or a command to perform another action.
  • the electronic device management service 251 may then perform the action in accordance with the command in the response.
  • a second example rule is a customer welcoming rule.
  • electronic device management service 251 receives a query from a mobile computing device of a user who does not own a low power electronic device 210.
  • the query may include the user account information of the user of the mobile computing device and the unique identifier of the low power electronic device 210.
  • Rules engine 254 may apply the customer welcoming rule, and determine that the mobile computing device is not associated with an owner of the low power electronic device 210 and came within range of the low power electronic device 210 during business hours. Responsive to such a determination, rules engine 254 may cause messaging module 258 to generate a personalized message welcoming the individual having the user account.
  • Messaging module 258 may send this personalized message to the mobile computing device 226 with an instruction for the personalized message to be displayed on the mobile computing device and/or to be forwarded to the low power electronic device 210 and displayed thereon.
  • the message may be a personalized message that welcomes a user associated with the user account to a bar or other establishment that owns the low power electronic device 210.
  • the message may also be a personalized advertisement or other personalized message.
  • low power electronic devices may be logically divided into one or more groups, and a user may select a group to send a message and/or command to.
  • a user with access to multiple electronic devices may generate any desired groupings and/or hierarchical structure of groupings for controlling the electronic devices. This enables the user to easily select a set of electronic devices and perform the same action with regards to each of these electronic devices. For example, a user may generate a top level group for all of the electronic devices in a store, and different second level groups for each floor of the store. The user may then select the top level group to select all electronic devices in the store, or one of the second level groups to select all of the electronic devices on one of the floors.
  • FIGS. 3-5 depict flow charts of multiple illustrative examples of methods 300, 400, 450 and 500 (hereafter "methods") for controlling a low power electronic device using a mobile phone and/or remote server.
  • the methods and each of their individual functions, routines, subroutines, or operations may be performed by processing logic of an electric display device (method 300), mobile computing device (methods 400, 450) or server computing device (method 500) executing the method.
  • the processing logic may include hardware, software, firmware, or a combination thereof.
  • processing logic may include a general purpose and/or special purpose processor that executes instructions for performing the methods.
  • processing logic determines whether a requestor of the connection satisfies one or more security criteria. In one embodiment, processing logic determines whether the connection request includes a password that matches a password that is stored on the low power electronic device. If the passwords match (or other security criterion is met), the method continues to block 320. Otherwise, the method returns to block 305.
  • processing logic establishes a wireless connection to the requestor.
  • This wireless connection may be established in accordance with a second wireless protocol.
  • the wireless connection is a bidirectional peer-to-peer Bluetooth connection established in accordance with the Bluetooth protocol.
  • processing logic may receive an additional command to perform some other action.
  • processing logic executes the command and performs the action.
  • the command may be configured in accordance with an API of the low power electronic device. Examples of commands include commands to report a battery level, commands to turn on, turn off or change a current mode of operation, and so on.
  • the low power electronic device may include onboard sensors such as temperature sensors, sensors that detect a volume or amount of contents of a container to which the low power electronic device is attached, motion sensors, light sensors, proximity sensors, and so on. In such an instance, additional commands may be commands to report on any such sensor measurements.
  • processing logic of a mobile computing device executing a listener module waits for a low energy radio signal.
  • processing logic receives a low energy radio signal that includes a unique identifier of an electronic device.
  • the unique identifier may include a UUID and a pair of numerical values that combine to form a unique value.
  • processing logic may check a UUID included in the radio signal at block 406 to determine if the electronic device is of a type that the listener module is listening for. If the UUID matches a stored UUID (e.g., corresponds to a particular OEM), then processing logic may load an electronic device controller application at block 408. If the UUID does not match a stored UUID, then the method returns to block 402.
  • a stored UUID e.g., corresponds to a particular OEM
  • processing logic generates a query including the unique identifier
  • processing logic sends the query to a device management service running on a server computing device.
  • processing logic receives a response from the server computing device.
  • processing logic determines from the response whether the user has permission to access the low power electronic device. If the user does not have such access, the method returns to block 402, and does not notify the user of the presence of the low power electronic device. If the user does have permission to access the low power electronic device, the method continues to block 430.
  • processing logic notifies the user of the presence of the low power electronic device and provides control options for controlling the device.
  • the notification and control options may be displayed via a graphical user interface on the mobile computing device.
  • processing logic receives a user command to access the electronic device.
  • the command may be a command to send a message to the electronic device, to retrieve information from the electronic device, to change a mode of the electronic device, and so on.
  • processing logic establishes a wireless connection to the electronic device (e.g., a Bluetooth connection).
  • processing logic sends a command to the electronic device via the wireless connection to cause the electronic device to perform the desired action. The method may then end, or the user may provide additional user commands for further execution.
  • processing logic of a mobile computing device receives a low energy radio signal that includes a unique identifier of an electronic device.
  • processing logic generates a query including the unique identifier, a location of the mobile computing device and an identification of a user of the mobile computing device (e.g., user account information).
  • processing logic sends the query to a device management service running on a server computing device.
  • processing logic determines whether a user of the mobile computing device has permission to access the low power electronic device. If so, the method continues to block 472, and processing logic notifies the user of the presence of the electronic device and provides control options. If the user does not have access permission, the method proceeds to block 474.
  • processing logic establishes a wireless connection to the electronic device.
  • processing logic sends an instruction to the low power electronic device via the wireless connection.
  • processing logic determines whether a response has been received from the electronic device. If a response is received, the method continues to block 480, and the response is forwarded to the device management service. If no response is received, the method continues to block 482, and processing logic waits for an instruction to terminate the connection. Alternatively, processing logic may automatically terminate the connection after a predetermined time period (e.g., after 2 seconds, 5 seconds, etc.) if no additional instructions are received.
  • a predetermined time period e.g., after 2 seconds, 5 seconds, etc.
  • processing logic of a server computing device receives a query from a mobile computing device.
  • the received query may include an identifier of a low power electronic device and information identifying a user of the mobile computing device.
  • the identifier may include two numerical values (e.g., a 2 byte major and a 2 byte minor).
  • the query may additionally include additional information such as a location of the mobile computing device, a time stamp, and so on.
  • processing logic determines an identity of the electronic device based on the identifier.
  • the identifier may include two numerical values that are
  • processing logic determines whether the received identifier is a default identifier.
  • the identifier may be a default identifier, which may indicate that the electronic device is new. If the identifier is a default identifier, the method proceeds to block 550. Otherwise the method continues to block 520.
  • processing logic determines an unused unique identifier and assigns the unique identifier to the low power electronic device. This may include determining a first numerical value and a second numerical value that can be concatenated to form the single larger value.
  • processing logic records a user of the mobile computing device as an owner of the device having the unique identifier.
  • processing logic instructs the mobile computing device to program the electronic device to have the unique identifier.
  • processing logic uses data from the query (e.g., the location, unique identifier, user account information, etc.) as an input into a rules engine to determine actions to perform. For example, processing logic may apply one or more rules, such as an authorization rule, a notification rule, etc.
  • processing logic may apply an authorization rule to determine whether the user of the mobile computing device has permission to access the electronic device.
  • processing logic may also apply a notification rule to determine whether a user should be notified of the query.
  • processing logic may apply an additional rule to determine whether any instructions are to be sent to the mobile computing device.
  • processing logic performs one or more actions based on an output from the rules engine. If the criteria of multiple rules are satisfied, then multiple different actions may be performed. For example, if a mobile computing device of a non-owner generated the query, then a first rule may cause a notification to be sent to the owner, and a second rule may cause a welcome message to be sent to the mobile computing device. In one embodiment, at block 540 processing logic sends a response to the mobile computing device with an indication of permissions.
  • processing logic may indicate whether the user of the mobile computing device has permission to access the low power electronic device, or if the user has permission to perform specific operations with regards to the low power electronic device (e.g., only has permission to send messages to the electronic device and display messages on the electronic device).
  • the response may also include additional instructions, such as instructions to display a message on the mobile computing device, or instructions for the mobile computing device to send an instruction to the electronic device
  • processing logic sends a notification to an owner of the electronic device.
  • the notification may include an identity of the user, a location of the mobile computing device and/or the electronic device, etc.
  • the location of the electronic device may be inferred based on the location of the mobile computing device and the known communication range of the low power radio signals broadcast by the low power electronic device in embodiments.
  • FIG. 6 depicts a block diagram of a computer system operating in accordance with one or more aspects of the present disclosure.
  • computer system 600 may correspond to low power electronic device 210, mobile computing device
  • Computer system 600 may be provided by a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a laptop computer, a tablet computer, a server computing device, a network router, switch or bridge, an electronic display device, or any device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device.
  • PC personal computer
  • PDA Personal Digital Assistant
  • STB set-top box
  • a cellular telephone a web appliance
  • laptop computer a laptop computer
  • tablet computer a tablet computer
  • server computing device a server computing device
  • network router switch or bridge
  • an electronic display device or any device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device.
  • the term "computer” shall include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods described herein.
  • the computer system 600 may include a processing device 602, a main (volatile) memory 604 (e.g., random access memory (RAM)), a static (non-volatile) memory 606 (e.g., read-only memory (ROM) or electrically-erasable programmable ROM (EEPROM)), and/or a data storage device 618, which may communicate with each other via a bus 608.
  • main (volatile) memory 604 e.g., random access memory (RAM)
  • static (non-volatile) memory 606 e.g., read-only memory (ROM) or electrically-erasable programmable ROM (EEPROM)
  • EEPROM electrically-erasable programmable ROM
  • terms such as “receiving”, “identifying”, “determining”, “transmitting”, “displaying”, or the like refer to actions and processes performed or implemented by a computer system that manipulates and transforms data represented as physical (electronic) quantities within the computer system registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage or display devices.
  • the terms “first,” “second,” “third,” “fourth,” etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.
  • Examples described herein also relate to an apparatus for performing the methods described herein.
  • This apparatus may be specially constructed for performing the methods described herein, or it may include a general purpose computer system selectively
  • Such a computer program may be stored in a computer-readable tangible storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, un dispositif informatique mobile qui manque d'une connexion réseau reçoit un signal radio à faible consommation d'énergie comprenant un identificateur unique affecté au dispositif électronique. Le dispositif informatique mobile envoie une interrogation à un dispositif informatique de serveur distant, l'interrogation comprenant l'identificateur unique et des informations identifiant un utilisateur du dispositif informatique mobile. Le dispositif informatique mobile reçoit une réponse en provenance du dispositif informatique de serveur distant, la réponse indiquant que l'utilisateur est autorisé à accéder au dispositif électronique. Le dispositif informatique mobile notifie à l'utilisateur une présence du dispositif électronique et établit une connexion sans fil avec le dispositif électronique.
EP16721341.2A 2015-03-26 2016-01-15 Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile Withdrawn EP3100225A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201561138944P 2015-03-26 2015-03-26
US14/789,648 US10009709B2 (en) 2015-03-26 2015-07-01 Electronic device with network access via mobile device proxy
PCT/US2016/013630 WO2016153584A1 (fr) 2015-03-26 2016-01-15 Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile

Publications (2)

Publication Number Publication Date
EP3100225A1 true EP3100225A1 (fr) 2016-12-07
EP3100225A4 EP3100225A4 (fr) 2017-08-30

Family

ID=57207985

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16721341.2A Withdrawn EP3100225A4 (fr) 2015-03-26 2016-01-15 Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile

Country Status (1)

Country Link
EP (1) EP3100225A4 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9609515B2 (en) * 2013-03-27 2017-03-28 Xerox Corporation System and method for verifying physical proximity to a network device
US20140324585A1 (en) * 2013-04-24 2014-10-30 Eric Mederos Apparatus, systems, and methods for product container programmable displays

Also Published As

Publication number Publication date
EP3100225A4 (fr) 2017-08-30

Similar Documents

Publication Publication Date Title
US10433138B2 (en) Electronic device with network access via mobile device proxy
US10528012B2 (en) Method and device for sending communication message
US9958841B2 (en) Method and device for remotely controlling household appliance, and computer readable storage medium
US9888342B2 (en) Communication method and system
US9699269B2 (en) Peripheral device detection with short-range communication
US8200868B1 (en) Peripheral device detection with short-range communication
CN111313500B (zh) 充电管理方法和装置、电子设备、计算机可读存储介质
US20190073178A1 (en) Flexible electronic display device
KR101927407B1 (ko) 메시지 송신 방법, 장치, 단말기, 라우터, 프로그램 및 기록매체
EP2659658B1 (fr) Détection de dispositif périphérique avec communication à courte distance
CN107786424B (zh) 音视频通信方法、终端及服务器
CN106792076B (zh) 一种进行信息展示的方法、装置和系统
KR20160100153A (ko) 장치 검색 방법 및 이를 지원하는 전자 장치
KR20160073242A (ko) 근거리 통신을 통해 스캔을 요청 또는 수행하는 전자 장치 및 그 동작 방법
EP4243349A1 (fr) Procédé d'acquisition d'un droit de commande d'un dispositif et système de communication
WO2019223601A1 (fr) Système de base de données, et procédé et appareil d'établissement associés
CN109728918B (zh) 虚拟物品发送方法、虚拟物品接收方法、装置及存储介质
EP3100225A1 (fr) Dispositif électronique ayant un accès à un réseau par l'intermédiaire d'un mandataire de dispositif mobile
US9622172B2 (en) Data transmission method and electronic device adapted to the method
KR20210080937A (ko) 전자 장치 및 전자 장치의 nan 기반의 통신 제어 방법
CN106294025B (zh) 一种终端软体的下载方法和装置
WO2015112315A1 (fr) Sélection d'un mode de communication
KR20160105031A (ko) 전자 장치의 동작 방법 및 전자 장치
WO2019014117A1 (fr) Systèmes et procédés de recommandation d'objets sur la base de données capturées
CN112689274B (zh) 短距离无线通信连接的提示方法、装置及按摩设备

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160519

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20170727

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 50/10 20120101ALI20170721BHEP

Ipc: H04W 4/02 20090101ALI20170721BHEP

Ipc: G06Q 30/02 20120101AFI20170721BHEP

Ipc: H04W 4/00 20090101ALI20170721BHEP

Ipc: H04W 8/00 20090101ALI20170721BHEP

Ipc: H04W 4/08 20090101ALI20170721BHEP

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MEDEA INC.

17Q First examination report despatched

Effective date: 20180319

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 8/00 20090101ALI20200303BHEP

Ipc: G06Q 30/02 20120101AFI20200303BHEP

Ipc: H04W 84/18 20090101ALI20200303BHEP

Ipc: H04W 4/80 20180101ALI20200303BHEP

Ipc: H04W 4/02 20180101ALI20200303BHEP

Ipc: H04W 4/00 20180101ALI20200303BHEP

Ipc: H04W 4/08 20090101ALI20200303BHEP

Ipc: G06Q 50/10 20120101ALI20200303BHEP

INTG Intention to grant announced

Effective date: 20200402

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20200813