EP3430826A1 - Wearable group communication device linking - Google Patents
Wearable group communication device linkingInfo
- Publication number
- EP3430826A1 EP3430826A1 EP17767641.8A EP17767641A EP3430826A1 EP 3430826 A1 EP3430826 A1 EP 3430826A1 EP 17767641 A EP17767641 A EP 17767641A EP 3430826 A1 EP3430826 A1 EP 3430826A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- end user
- user device
- optical symbol
- communication
- data
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
- H04W12/33—Security of mobile devices; Security of mobile applications using wearable devices, e.g. using a smartwatch or smart-glasses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
- H04W12/55—Secure pairing of devices involving three or more devices, e.g. group pairing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/71—Hardware identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/77—Graphical identity
-
- 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
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
Definitions
- aspects of the disclosure are related to communications and, in particular, to end user devices and applications for efficient communications.
- an endpoint device in a communication system can be an end user device that allows a user to communicate with other endpoint devices via one or more intermediate communication devices and a communication network or the like.
- a wearable end user device can be linked to an intermediate communication device (e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer) that in turn is connected to a communication network that permits a user of the end user device to communicate verbally or otherwise with other devices connected to the network.
- both the end user device and its associated intermediate communication device are portable devices
- external markings on the devices e.g., serial numbers, media access control (MAC) addresses, etc.
- MAC media access control
- linking an end user device with an intermediate communication device in a crowded area may be difficult because a list of available device identifiers presented to a user on an intermediate communication device might include numerous potential connections and thus be difficult to manage.
- Implementations of linking a wearable group communication device to another communication device utilize optical symbol sequence communication linking that can use lights, light-emitting diodes (LEDs), and/or other optical symbol sequence-generating and/or displaying devices that provide users with visually perceptible symbols on both an end user device and the display system of an associated intermediate communication device.
- a communication application on the intermediate communication device can be configured to collect optical symbol reference data (representing an optical symbol sequence) derived from identifying data transmitted from an associated end user device (e.g., an end user device to which a user wishes to link the intermediate communication device).
- the end user device displays the optical symbol sequence so that a user can match the displayed sequence by entering the same optical symbol sequence using a user interface on the intermediate communication device (e.g., as optical symbol input data).
- the communication application can compare the optical symbol reference data and the optical symbol input data and, if they match, can then enable and initiate a communication connection between the end user device and the intermediate communication device.
- the end user and intermediate communication devices can utilize Bluetooth low energy (one or more versions of which may be referred to as "Bluetooth LE,” “BLE,” and/or “Bluetooth Smart”) to exchange information during pre-connection data exchange between devices in at least a portion of the linking process.
- the intermediate communication device has a display system that pre -populates a user interface graphical depiction of an optical symbol sequence corresponding to the identifying data (i.e., optical symbol reference data) from the nearest end user device. The user can confirm that the pre-populated optical symbol sequence on the intermediate communication device display system matches the optical symbol sequence displayed on the end user device to enable the intermediate communication device to initiate a communication connection with the end user device.
- the intermediate communication device includes an optical data acquisition device that can generate optical symbol sequence image data captured from the end user device's displayed optical symbol sequence. Optical symbol input data can be derived from this image data and compared to the optical symbol reference data received from the end user device to determine the correct end user device.
- Figure 1 illustrates one or more exemplary systems configured to facilitate secure communications using optical symbol sequence communication linking of devices.
- Figure 2A is a top view of one or more end user devices configured to be part of optical symbol sequence communication linking of devices.
- Figure 2B is a side view of one or more end user devices configured to be part of optical symbol sequence communication linking of devices.
- Figure 3 illustrates one or more methods of operating a communication system.
- Figure 4 illustrates one or more implementations of an end user device and an intermediate communication device apparatus and one or more methods of operating a communication system.
- Figure 5 illustrates one or more methods of operating a communication system.
- Figure 6 illustrates one or more methods of operating a communication system
- Figure 7 illustrates a computing architecture to provide optical symbol sequence communication linking of devices including a wearable group communication end user device.
- Figure 8A illustrates an operational example in an implementation.
- Figure 8B illustrates an operational example in an implementation.
- Bluetooth low energy may expose private information or data, or may allow a connecting party to control one of the devices involved in such communications (e.g., a Bluetooth device). Security and other reasons thus make it advisable to identify and verify specific devices prior to connecting to such devices and/or exchanging sensitive and/or other data with such devices. It also is helpful for communication devices to be able to establish a connection without undue user inconvenience and difficulty, especially when a user is on the go or in an active communication and/or linking setting. Bluetooth low energy
- communication connections can be established using a BLE device's advertising function for device discovery, and subsequent communications between a searching device and a discovered device can establish a BLE connection between the correct pair of devices.
- devices implementing limited-range Bluetooth low energy connect by utilizing a discovery and connection process in which one or more Generic Access Profile (GAP) peripheral devices advertise their availability to a GAP central device.
- GAP Generic Access Profile
- the GAP central device can then request a connection with a specific GAP peripheral, after which the GAP central device becomes the BLE Generic Attribute Profile (GATT) client and the GAP peripheral device becomes the BLE GATT server.
- GATT Generic Attribute Profile
- the connected devices may then exchange messages and other data utilizing the BLE attribute protocol.
- optical symbol sequence (OSS) communication linking are used in a communication system that allows wearable group communication end user devices (e.g., two-way audio communication devices that include a speaker and a microphone) to communicate with one another via their respective intermediate
- an end user device can be any end user device that uses BLE or similar limited-range communication to connect each end user device to an associated (e.g., Bluetooth paired) intermediate communication device.
- an end user device can be any end user device that uses BLE or similar limited-range communication to connect each end user device to an associated (e.g., Bluetooth paired) intermediate communication device.
- GAP peripheral device that advertises its availability to establish a connection with its associated intermediate communication device (which can be
- the intermediate communication device may be the component that advertises its availability to connect to an end user device.
- Implementations of OSS communication linking disclosed and claimed herein provide apparatus and methods for facilitating linking an end user device with a
- implementations of OSS communication linking use optical symbols as a proxy for more complex device identifiers.
- Optical symbols include any optically perceptible symbols and may, in some implementations, include symbols whose color, brightness or other state is normally perceptible by a human user operating an end user device or the like.
- Optical symbol reference data received by an intermediate communication device is confirmed prior to commencing a communication connection between the devices. Confirmation of the optical symbol reference data can be achieved in various implementations.
- Optical symbol reference data can be derived from identifying data contained in availability information that is broadcast or otherwise transmitted by an end user device and received by an intermediate communication device. That is, an end user device can broadcast availability information regarding its availability for linking with other devices. Identifying data can be included as part of that availability information; the identifying data can be used to derive the optical symbol reference data.
- the intermediate communication device also obtains optical symbol input data (e.g., receiving inputs via a user interface, or obtained from image data acquired by the intermediate communication device) that can be compared to the optical symbol reference data.
- optical symbol input data e.g., receiving inputs via a user interface, or obtained from image data acquired by the intermediate communication device
- a user can confirm or reject the optical symbol reference data rather than separately inputting distinct optical symbol input data.
- Figure 1 illustrates one or more implementations of a communication system
- OSS optical symbol sequence
- System 100 includes exemplary communication node 104 (which includes endpoint end user device 110 and communication device 130 (e.g., an intermediate communication device that also may be referred to as a computing system)), exemplary communication node 106 (which includes endpoint end user device 160 and communication device 150 (e.g., another intermediate communication device that also may be referred to as a computing system)), and communication network 140 linking nodes 104, 106.
- exemplary communication node 104 which includes endpoint end user device 110 and communication device 130 (e.g., an intermediate communication device that also may be referred to as a computing system)
- exemplary communication node 106 which includes endpoint end user device 160 and communication device 150 (e.g., another intermediate communication device that also may be referred to as a computing system)
- communication network 140 linking nodes 104, 106.
- additional nodes, endpoint devices, end user devices and intermediate communication devices can be interconnected via communication network 140.
- intermediate communication device 130 can be a computing system (e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer) in communication node 104 that communicates with its associated end user device 110 over a limited-range communication link 142 (e.g., Bluetooth low energy), and further communicates outside node 104 using communication network 140 over one or more communication network links 144.
- a limited-range communication link 142 e.g., Bluetooth low energy
- ICD 150 also can be a computing system (e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer) in communication node 106 that also communicates with its associated end user device 160 using a limited-range communication link 142, and further communicates outside node 106 using communication network 140 over communication network link 144.
- a computing system e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer
- Limited-range links 142 can be used, as described in more detail herein, to perform linking of an end user device with its associated intermediate communication device using OSS communication linking.
- the communication link 144 that connects intermediate communication device 130 to communication network 140 can use one or more of Time Division Multiplexing (TDM), asynchronous transfer mode (ATM), IP, Ethernet, synchronous optical networking (SONET), hybrid fiber-coax (HFC), circuit-switched, communication signaling, wireless communications, or some other communication format, including improvements thereof.
- TDM Time Division Multiplexing
- ATM asynchronous transfer mode
- SONET synchronous optical networking
- HFC hybrid fiber-coax
- Link 144 connecting intermediate communication device 150 to network 140 can operate similarly.
- Communication links 144 each use metal, glass, optical, air, space, or some other material as the transport media and may each be a direct link, or can include intermediate networks, systems (including one or more management service systems), or devices, and can include a logical network link transported over multiple physical links.
- Each ICD 130, 150 may comprise a computing system capable of running a communication application and communicating with network 140 using the Internet or some other widespread communication network.
- Each of ICDs 130, 150 can include at least one user interface that allows a user to enter data and interact with communication application 135, 155, respectively.
- communication devices 130, 150 and the like can use an appropriate data transfer scheme.
- Communications network 140 can comprise a server system utilizing one or more computing devices capable of providing communication services to a plurality of communication nodes and their respective endpoint devices, such as end user devices 110, 160.
- End user devices 110, 160 may each comprise a speaker, microphone, processing system, communication interface, and a user interface to exchange communications with ICDs 130, 150, respectively, and thus with communications network 140 and other endpoint devices of various types.
- at least one EUD has an at least one OSS display capability (e.g., one or more lights and/or LEDs; a color sequence on a sticker, label or decal applied to the end user device; other display capabilities may also be implemented).
- the endpoint devices of network 140 include EUDs 110, 160, each of which can be a highly portable (e.g., wearable) communication device.
- EUD device 110 is shown in Figures 2A and 2B.
- Device 110 has a top cover 111 that can be generally circular in shape, as shown in Figure 2A, or can be any other shape.
- end user device 110 uses the generally circular shape to facilitate certain operations and to permit the positioning of certain functions and components, which also can be performed and implemented in alternative ways in other configurations.
- device 110 includes a generally cylindrical base 107 and a generally convex cover 111 (e.g., having a quasi-conical shape or a cup-like shape).
- Base 107 has an attachment mechanism 109 (e.g., a clip or clasp) mounted thereon to permit attachment of device 110 to clothing, a backpack or another personal item that facilitates audio communications (e.g., a conversation with another user) by a user while wearing device 110.
- Various functional components of EUD 110 can be situated around the periphery of base 107, as seen in Figures 2A and 2B.
- a master power switch 112 can turn device 110 on and off (as distinguished from turning on and off BLE advertising, as discussed herein).
- a speaker 114 is built in to base 107, as is a microphone 116, each of a type and size that again facilitates and enables conversation by a user wearing device 110 in some implementations.
- a volume control 118 permits adjustment of the sound level generated by speaker 114 (e.g., lowering sound level by depressing the "-" end of control 118 and increasing sound level by depressing the "+” end).
- Other components and/or features e.g., a micro and/or other Universal Serial Bus (USB) port, headphone jack, mute button or switch
- USB Universal Serial Bus
- Cover 111 can be made of plastic or any other suitable material and includes an
- OSS display 122 which in Figures 2A and 2B is a non-limiting exemplary LED array that includes individually addressable multi-color LEDs 122a, 122b, 122c, 122d, 122e.
- the optical symbol sequence displayed on end user device 110 can be a color sequence on a sticker, label or decal applied to the end user device 110.
- LED array 122 operates as described in various implementations of OSS communication linking discussed herein.
- Cover 111 is attached to base 107 in a manner that permits limited rotation of cover 111 relative to base 107, as referenced by arrow 124 in Figures 2 A and 2B.
- the master device power 112 is turned on.
- cover 111 is rotated clockwise relative to base 107 to initiate broadcast of availability information to inform certain other devices in the vicinity of end user device 110 of its availability for communications and to provide relevant identifying data and/or other information that can assist in enabling such communications (counterclockwise rotation of cover 111 can turn off availability broadcasting).
- rotation of cover 111 turns on BLE advertising in EUD 110, which then broadcasts its availability information in a manner that can be detected and received by other devices, including ICD 130.
- ICD 130 when ICD 130 scans for BLE devices to which it might connect, it can receive advertising packets broadcast by EUD 110.
- at least part of the payload data in the advertising packets includes identifying data such as a serial number, MAC address, and/or other alphanumeric characters, text, or the like that functions as an identifier of EUD 110.
- EUD 110 When activated to broadcast BLE advertising packets or the like, EUD 110 also can illuminate an optical symbol sequence (e.g., using array 122 to provide a sequence of colors). This optical symbol sequence can be displayed when BLE advertising is activated or in response to a prompting transmission from ICD 130.
- the identifying data contained and/or included in the availability information transmitted by EUD 110 and received by ICD 130 can be converted by communication application 135 into optical symbol reference data (e.g., a byte array, binary string or other data structure) that represents a reference optical symbol sequence.
- optical symbol reference data can be derived from the identifying data by applying an appropriate algorithm or data conversion process, or in any other way that yields a suitable data value, structure, size, etc. for use as optical symbol reference data.
- the light sequence that can be displayed on array 122 of device 110 may include multi-color lights or LEDs.
- each LED 122a, 122b, 122c, 122d, 122e can emit one of three colors (e.g., white, red or blue).
- a light or LED being "off also can constitute a color usable in an optical symbol sequence, as can a light or LED blinking (including blinking at different speeds, each of which can likewise constitute a color usable in an optical symbol sequence).
- Communication application 135 can display a graphical user interface (GUI) on ICD 130 (e.g., using a touchscreen or other display system on device 130).
- GUI graphical user interface
- Such a GUI can permit data entry or confirmation of verification data by a user (e.g., by "typing in” or “tapping in” a color sequence that matches the optical symbol sequence being displayed as a graphical depiction corresponding to optical symbol reference data on EUD 110) or by confirming a pre-populated optical symbol sequence being displayed on the user interface.
- User-entered verification data and OSS data on ICD 130 can be processed (e.g., converted into optical symbol input data), so that the optical symbol input data has a data structure that allows it to be compared to optical symbol reference data to determine whether or not they match (and thus whether the optical symbol sequence on EUD 110 matches the optical symbol sequence on the display system of ICD 130). If the user-input optical symbol input data and optical symbol reference data match, then ICD 130 can send a BLE connection request or other invitation to connect to EUD 110, which it can answer with a response, thus connecting EUD 110 and ICD 130.
- FIG. 3 a method 300 of linking an end user device and an intermediate communication device using OSS communication linking in a communication system is shown.
- Method 300 is described with reference to exemplary elements, apparatus, systems and other information from Figures 1, 2 A, 2B and 4.
- the description below references operations of Figure 3 parenthetically.
- an ICD 130 may comprise a computing system (e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer) configured to communicate over a communication network 140 and to communicate with an associated EUD 110.
- a computing system e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer
- EUD 110 an associated EUD 110.
- end user device identifying information such as a serial number, MAC address, and/or other alphanumeric characters, text, or the like that functions as an identifier
- implementations of OSS communication linking utilize one or more optical symbol sequences in conjunction with an application 135 on an associated intermediate
- an optical symbol sequence acts as a proxy for more detailed end user device identifying information.
- an EUD 110 initiates broadcast of its availability for connection (310). This can be done by broadcasting BLE advertising packets or the like (e.g., that contain identifying data from which optical symbol reference data can be derived), which are then received (315) by ICD 130 (e.g., if it is in BLE scanning mode).
- communication application 135 derives optical symbol reference data from received identifying data, for example by processing (e.g., by applying an algorithm or other processing technique) digital, numeric or alphanumeric identifying data to generate the optical symbol reference data, which represents a color sequence.
- the EUD 110 displays (320) an optical symbol sequence (e.g., an LED-illuminated color sequence) that is similarly based on that end user device's identifying data. Display of the optical symbol sequence can be initiated once BLE advertising commences or can be in response to a prompt (317) sent by ICD 130 after it has received availability information that includes end user device identifying data.
- ICD 130 also receives optical symbol input data (325), which can be a plurality of optical symbol selections received at a user interface (e.g., sequenced color selections entered by a user on a display system device such as a touchscreen). Optical symbol selections may also be received via image capturing or the like.
- the user interface can be implemented as a GUI in connection with communication application 135 so that a user is able to select colors (or other optical symbols) and their sequence and enter the selections, for example via a touchscreen, keypad, voice command and/or otherwise.
- an EUD 110 has an array of LEDs 122a, 122b, 122c, 122d, 122e with counterpart optical symbol input points 132a, 132b, 132c, 132d, 132e on the GUI 133 of a display system 131 of ICD 130.
- Each optical symbol input point 132a-e can comprise a selectable color image (e.g., a dot or circle).
- GUI 133 can be generated by communication application 135 as part of a device setup for EUD 110 and ICD 130.
- the optical symbol sequence of BLUE, WHITE, BLUE, RED, RED illuminated respectively on LEDs 122a, 122b, 122c, 122d, 122e of device 110 is reproduced after a user inputs the same color sequence on GUI 133.
- optical symbol input data from the user interface of ICD 130 matches (330) the optical symbol reference data obtained by ICD 130 from the identifying data of
- an ICD 130 may comprise a computing system (e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer) configured to communicate over a communication network 140 and to communicate with an associated EUD 110.
- a computing system e.g., a cellphone, smartphone, gaming device, tablet, laptop or other computer
- some implementations of OSS communication linking utilize one or more optical symbol sequences in conjunction with a communication application 135 on an ICD 130 to enable verification of a peripheral end user device and connection(s) between the correct devices.
- an optical symbol sequence again can act as a proxy for detailed end user device identifying information.
- an EUD 110 initiates broadcast of the end user device's availability for connection (510), which includes end user device data.
- end user device data comprising: end user device signal strength data (e.g., RSSI or Tx Power data); and end user device identifying data (e.g., a device serial number, binary string, MAC address, and/or other alphanumeric characters, text, or the like that functions as an identifier or the like from which optical symbol reference data can be derived).
- end user device signal strength data e.g., RSSI or Tx Power data
- end user device identifying data e.g., a device serial number, binary string, MAC address, and/or other alphanumeric characters, text, or the like that functions as an identifier or the like from which optical symbol reference data can be derived.
- Availability information broadcast by a set of end user devices in the same general vicinity i.e., one or more EUDs that are broadcasting end user device data
- ICD 130 e.g., if it is in BLE scanning mode.
- end user device signal strength data e.g., a received signal strength indication (RSSI) or other signal strength data
- RSSI received signal strength indication
- Tx Power transmit power data
- communication application 135 does not have to determine or estimate how far away any particular device(s) might be. Instead, application 135 can select the nearest BLE device (by ranking devices based on received signal strength data), process whatever identifying data is provided in that nearest device's advertising packets, and pre-populate the color optical symbol input points of communication application 135 accordingly (525).
- Each optical symbol input point can comprise a selectable color image (e.g., a dot or circle).
- EUD 110 displays (520) an optical symbol sequence (e.g., an LED-illuminated color sequence), which can be displayed once advertising commences or in response to a prompt (517) sent by ICD 130 after it has received optical symbol reference data.
- image capturing can be used to collect image data from which the optical symbol input data can be obtained and which a user can then merely confirm via a user interface or the like.
- ICD 130 processes the optical symbol reference data and pre-populates (525) the color code input points 132a, 132b, 132c, 132d, 132e on the GUI 133 as a graphical depiction of a sequence corresponding to the nearest BLE device's optical symbol reference data, as seen in Figure 4.
- the user need only confirm (530) the correct optical symbol sequence (e.g., by tapping
- CONNECT and establish a connection (535) or, if the pre-populated color sequence is incorrect, the user rejects the initial optical symbol reference data and optionally can either update the user interface inputs (540) to display the correct optical symbol sequence (e.g., by visually checking the display 122 on EUD 110) or can request (540) the identifying data for the second nearest (i.e., next-closest) BLE device, based on RSSI strength (e.g., by tapping "NEXT").
- RSSI strength e.g., by tapping "NEXT”
- FIG. 6 another method 600 of linking an end user device and an intermediate communication device using OSS communication linking in a communication system is shown in which image capture and/or image recognition is used.
- Method 600 is described with reference to exemplary elements, apparatus, systems and other information from Figures 1, 2A, 2B and 4. The description below references operations of Figure 6 parenthetically.
- OSS communication linking use one or more optical symbol sequences in conjunction with a communication application 135 on ICD 130 to enable verification of a peripheral end user device and connection(s) between the correct devices.
- an optical symbol sequence again can act as a proxy for detailed end user device identifying information.
- an end user device 110 initiates its broadcast of the end user device's availability for connection (610). This can be done by broadcasting BLE advertising packets or the like that contain availability information including device identifying data (e.g., a serial number, MAC address, and/or other alphanumeric characters, text, or the like that functions as an identifier or the like from which optical symbol reference data can be derived and that corresponds to the optical symbol sequence displayed by EUD 110).
- Availability information broadcast by EUD 110 is received (615) by ICD 130 (e.g., if it is in BLE scanning mode).
- EUD 110 displays (620) an optical symbol sequence (e.g., an LED-illuminated color sequence) that is similarly based on that device's identifying data.
- Display of the optical symbol sequence can be initiated once BLE advertising commences or can be in response to a prompt (617) sent by ICD 130 after it has received availability information that includes end user device identifying data.
- the computing system 130 also can include an optical data acquisition device 637 (e.g., a camera or other reader built in or otherwise coupled to system 130).
- Optical data acquisition device 637 can acquire optical symbol sequence image data (625) from an image of optical symbol sequence 122 being displayed on EUD 110 (e.g., communication application 135 can instruct a user to point the camera 637 at EUD 110 to acquire the optical symbol sequence image data).
- Communication application 135 can display (e.g., on a display system 131 of
- ICD 130 a replica of the optical symbol sequence displayed on EUD 110 by processing the optical symbol sequence image data to derive optical symbol input data.
- a user can confirm a match by using an input on GUI 133 (630), after which a connection is established (635) between EUD 110 and ICD 130.
- communication application 135 can perform the comparison (632) by comparing optical symbol reference data obtained from availability information broadcast by EUD 110 with the optical symbol reference data derived from the optical symbol sequence image data.
- Figure 7 illustrates a computing architecture 700 to implement the
- Computing architecture 700 is representative of a computing architecture that may be employed in an intermediate communication device such as ICDs
- Computing architecture 700 comprises network communication interface 701, limited-range communication interface 702, user interface 703, and processing system 704.
- Processing system 704 is communicatively linked to communication interfaces 701, 702 and user interface 703.
- Processing system 704 includes processing circuitry 705 and memory device 706 that stores operating software 707 (including communication application 735).
- Network communication interface 701 comprises components that communicate over network and related communication links (e.g., including those extending outside a communication node), such as network cards, ports, RF transceivers, processing circuitry and software, or some other communication devices.
- Network communication interface 701 may be configured to communicate over metallic, wireless, or optical links.
- Network communication interface 701 also may be configured to use TDM, IP, Ethernet, optical networking, wireless protocols, communication signaling, or some other
- Limited-range communication interface 702 comprises components that communicate using a limited-range channel (e.g., Bluetooth low energy).
- User interface 703 comprises components that permit user interaction with computing architecture 700.
- User interface 703 can include a touchscreen, keyboard, display screen, voice command apparatus, mouse, touch pad, and/or other user input/output apparatus.
- Processing circuitry 705 comprises microprocessor and other circuitry that retrieves and executes operating software 707 from memory device 706.
- Memory device 706 comprises a non-transitory storage medium, such as a disk drive, flash drive, data storage circuitry, or some other memory apparatus.
- Operating software 707 comprises computer programs, firmware, or some other form of machine-readable processing instructions.
- Operating software 707 may include any number of software modules to provide the communication operations described herein. Operating software 707 may further include an operating system, utilities, drivers, network interfaces, applications, or some other type of software. When executed by circuitry 705, operating software 707 directs processing system 704 to operate computing architecture 700 as described herein to provide one or more implementations of optical symbol sequence communication linking and other
- Display system 731 which may be the same or included in the user interface 703
- an optical data acquisition device 737 e.g., a camera or other reader built in or otherwise coupled to system 704 that enables acquisition of image data and the like.
- Display system 731 and optical data acquisition device 737 can be configured to operate as herein described in connection with one or more implementations of optical symbol sequence communication linking.
- each end user device can be implemented in a half- duplex type of operational mode. That is, a device in a communication node linked to a communication group or the like can transmit and receive, but cannot do both at the same time.
- a "push-to-talk" operational mode allows an end user to press a transmit toggle button or the like (e.g., by pushing and holding top cover 111 of device 110 as depicted by arrow 126 in Figure 2B) to initiate sending a voice communication to one or more users in the communication group. While the toggle is in its "transmit" position (e.g., with cover 111 depressed), the end user device is configured to collect audio data from the user (e.g., recording voice communications).
- the collected audio data can be held in the end user device or in a linked intermediate communication device (e.g., a smartphone, cellphone, gaming device, tablet, or laptop).
- a linked intermediate communication device e.g., a smartphone, cellphone, gaming device, tablet, or laptop.
- any collected audio data is transmitted to the one or more communication group members.
- the collected audio data can be transmitted using any appropriate transmission scheme.
- audio data collected by an end user device can be transmitted to its linked intermediate communication device via one of the Bluetooth modes.
- audio data collected by an intermediate communication device can be send over a broader network using any appropriate communication protocol or scheme.
- a communication node 804 includes an end user device 810 that has a microphone 816 configured to collect audio data from a human user. As illustrated in Figure 8A, the end user device 810 begins storing the collected audio data in a memory location 884. This audio data collection process continues until the a push-to-talk button on end user device 810 is released (i.e., the END signal in Figure 8A). Some additional processing 891 may be performed by end user device 810 before the collected audio data is transmitted at 842 to an intermediate communication device 830 that also is part of communication node 804. Again, some additional processing 835 may be performed by ICD 830 before it transmits at 844 the audio data to one or more additional communication group members via communication network 840.
- multiple members of a group can be collecting audio data, though while an EUD 810 or the like is collecting such audio data (i.e., while the push-to-talk button is in its transmit position) the ICD 830 and/or EUD 810 cannot play back audio data received from another user.
- the intermediate communication device 830 that stores the collected audio data before it is transmitted via network 840.
- the end user device 810 may process audio data collected from a user prior to transmission at 843 to the ICD 830 (e.g., the collected audio data may be encrypted, buffered to permit error correction, assembled into packets, etc.).
- the intermediate communication device 830 builds the audio data until the push-to-talk button on the EUD 810 is switched back to receive, at which point the ICD 830 can transmit the collected audio data to network 840 and thus to one or more communication group members or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Optical Communication System (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662310100P | 2016-03-18 | 2016-03-18 | |
PCT/US2017/022988 WO2017161285A1 (en) | 2016-03-18 | 2017-03-17 | Wearable group communication device linking |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3430826A1 true EP3430826A1 (en) | 2019-01-23 |
EP3430826A4 EP3430826A4 (en) | 2019-09-25 |
Family
ID=59851377
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17767641.8A Withdrawn EP3430826A4 (en) | 2016-03-18 | 2017-03-17 | Wearable group communication device linking |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP3430826A4 (en) |
CN (1) | CN109247075A (en) |
WO (1) | WO2017161285A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB201712566D0 (en) | 2017-08-04 | 2017-09-20 | Spd Swiss Prec Diagnostics Gmbh | Method and system for linking devices |
EP4111400A4 (en) * | 2020-02-28 | 2024-02-28 | Verifone Inc | Systems, methods and devices for bluetooth numeric comparison pairing |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7124953B2 (en) * | 2003-12-29 | 2006-10-24 | Nokia Corporation | Visual encoding of a content address to facilitate data transfer in digital devices |
US9088627B2 (en) * | 2005-09-29 | 2015-07-21 | Ipass Inc. | System and method for actively characterizing a network |
US20070083919A1 (en) * | 2005-10-11 | 2007-04-12 | Guy Heffez | Secure Image Protocol |
JP4303760B2 (en) * | 2007-02-16 | 2009-07-29 | 富士通株式会社 | AD conversion control device, optical receiving device, and optical receiving method |
US9357336B2 (en) * | 2012-12-03 | 2016-05-31 | Samsung Electronics Co., Ltd. | Information providing method and mobile terminal therefor |
US9270344B2 (en) * | 2013-02-01 | 2016-02-23 | Creating Revolutions, LLC | Combination process interaction |
US9537661B2 (en) * | 2014-02-28 | 2017-01-03 | Verizon Patent And Licensing Inc. | Password-less authentication service |
US9642173B2 (en) * | 2014-07-15 | 2017-05-02 | Paypal, Inc. | Systems and methods for reusing generic tokens using Bluetooth® low energy (BLE) beacons |
US10762189B2 (en) * | 2015-06-22 | 2020-09-01 | Blackberry Limited | Segment pattern entry based authentication |
US11481750B2 (en) * | 2015-06-30 | 2022-10-25 | Block, Inc. | Pairing a payment object reader with a point-of-sale terminal |
-
2017
- 2017-03-17 WO PCT/US2017/022988 patent/WO2017161285A1/en active Application Filing
- 2017-03-17 EP EP17767641.8A patent/EP3430826A4/en not_active Withdrawn
- 2017-03-17 CN CN201780030650.2A patent/CN109247075A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
EP3430826A4 (en) | 2019-09-25 |
CN109247075A (en) | 2019-01-18 |
WO2017161285A1 (en) | 2017-09-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10552655B2 (en) | Image-acquisition-based linking for wearable group communication device | |
US11653398B2 (en) | Bluetooth connection method and device | |
US6826387B1 (en) | Efficient service registration for legacy applications in a bluetooth environment | |
US7031660B2 (en) | Method for transferring a device identifier block on a second communication link separated from the BLUETOOTH link | |
US7974249B2 (en) | Virtual access point for configuration of a LAN | |
CN104811423B (en) | The sharing method and device of location information | |
EP3385896A1 (en) | System and method for transmitting/receiving data by using a mobile communication terminal in a zigbee pan | |
JPH07336370A (en) | Communication controller and communication controlling method | |
US20230039861A1 (en) | Projection Connection Control Method And Electronic Device | |
US11825531B2 (en) | Wireless cross pairing resolution on interconnected devices | |
KR20050114634A (en) | Method and device for identifying and pairing bluetooth devices | |
EP2941058A1 (en) | Near field communication method and device | |
EP3430826A1 (en) | Wearable group communication device linking | |
US8804608B1 (en) | Methods, apparatus, and systems for facilitating audio communications between disparate devices | |
CN106490751A (en) | There is the intelligent helmet and its remote control thereof of remote control | |
CN106102033A (en) | A kind of equipment communication means based on Android platform and device | |
US10630821B2 (en) | One-touch group communication device control | |
CN106210436A (en) | A kind of method simultaneously changing operating frequency by voice-grade channel control image transmitting transceiver | |
KR20190066174A (en) | Ptt terminal | |
US20110161822A1 (en) | Method and system for connection management and resource sharing | |
US20070258571A1 (en) | Conference System | |
CN117812547A (en) | Call transfer method and electronic equipment | |
KR20230069628A (en) | A mobile communication device capable of correcting the button recognition of an ear microphone and a method for correcting the button recognition using the same | |
CN115277923A (en) | Call method and electronic equipment | |
CN107566038A (en) | A kind of wireless router, Wireless Keyboard realize the method and system of equipment switching |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
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 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180913 |
|
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 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20190826 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 4/06 20090101ALN20190820BHEP Ipc: H04L 29/06 20060101ALI20190820BHEP Ipc: H04W 12/00 20090101ALI20190820BHEP Ipc: H04W 8/00 20090101ALI20190820BHEP Ipc: H04W 4/80 20180101AFI20190820BHEP Ipc: H04W 12/06 20090101ALI20190820BHEP Ipc: H04W 4/00 20180101ALI20190820BHEP Ipc: H04W 76/10 20180101ALI20190820BHEP |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ORION LABS |
|
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: 20211001 |