Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
  • G06F13/38—Information transfer, e.g. on bus
  • G06F13/40—Bus structure
  • G06F13/4063—Device-to-bus coupling
  • G06F13/4068—Electrical coupling
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/54—Interprogram communication
• • 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
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup

Definitions

• aspects of the present disclosure relate, generally, to wireless docking and, more particularly, to providing alternate visualization on a device via wireless docking.
• Wireless communication systems can provide wireless communication between multiple devices. Devices may wirelessly connect to each other using various technologies.
• a first device e.g., a smartphone
• a second device e.g., a desktop computer
• Existing systems may merely replicate the user experience of the first device (e.g., an AndroidTM operating system-based user experience) on the second device (e.g., the desktop computer), even if the second device (e.g., the desktop computer) customarily provides a different user experience (e.g., a WindowsTM operating system-based user experience).
• AndroidTM operating system-based user experience) on the second device may be undesirable for the user. Instead, the user may prefer the user experience to which they are accustomed for the second device (e.g., a WindowsTM operating system-based user experience on their desktop computer). Accordingly, enhancements associated with providing an alternate visualization may improve the user experience.
• a first device that establishes a wireless docking session with a second device.
• the first device may determine whether a profile of the second device matches a profile stored in the first device. When such a match exists, the first device may export data to the second device in a format associated with the profile of the second device. When such a match does not exist, the first device may provide an error message or export data to the second device in a format associated with a profile of the first device.
• the profile may indicate an operating system, a peripheral component, a display size, a display resolution, a touch screen-capability, a font type, a user setting, a power source or availability, a hardware component, or a software module. Additional aspects, embodiments, and features are also provided herein.
• the disclosure provides a method that includes establishing a wireless docking session with a second device, determining whether a profile of the second device matches one of a plurality of profiles stored in the first device, and exporting data to the second device in a format associated with the profile of the second device when the profile of the second device matches one of the plurality of profiles stored in the first device.
• the disclosure provides an apparatus including a transceiver, a memory, and at least one processor communicatively coupled to the transceiver and the memory.
• the at least one processor may be configured to establish a wireless docking session with a device, determine whether a profile of the device matches one of a plurality of profiles stored in the apparatus, and export data to the device in a format associated with the profile of the device when the profile of the device matches one of the plurality of profiles stored in the apparatus.
• the disclosure provides another apparatus including means for establishing a wireless docking session with a device, means for determining whether a profile of the device matches one of a plurality of profiles stored in the apparatus, and means for exporting data to the device in a format associated with the profile of the device when the profile of the device matches one of the plurality of profiles stored in the apparatus.
• the disclosure provides a computer-readable storage medium including code for establishing a wireless docking session with a second device, determining whether a profile of the second device matches one of a plurality of profiles stored in the first device, and exporting data to the second device in a format associated with the profile of the second device when the profile of the second device matches one of the plurality of profiles stored in the first device.
• FIG. 1 is a diagram illustrating an example of a hardware implementation of a master device.
• FIGS. 2-4 are diagrams illustrating examples of user interfaces of various profiles of the master device.
• FIGS. 5-7 are diagrams illustrating examples of user interfaces of various profiles of a slave device.
• FIGS. 8-9 are diagrams illustrating examples of various profiles of the master device and the slave device.
• FIGS. 10-1 1 are diagrams illustrating examples of proximities of the slave device relative to the master device.
• FIG. 12 is a diagram illustrating an example of various items displayed on the master device and the slave device.
• FIG. 13-14 are diagrams illustrating examples of various methods and/or processes.
• FIG. 1 is a diagram 100 illustrating an example of a hardware implementation of the master device 101 in accordance with various aspects of the present disclosure.
• the master device 101 may be any apparatus configured to communicate with another apparatus.
• the master device 101 may be a cellular telephone, a smartphone, user equipment, a tablet computer, a laptop computer, a personal digital assistant (PDA), a gaming device, an e-reader, and/or any other apparatus configured to communicate with another apparatus.
• PDA personal digital assistant
• the master device 101 may include a user interface 1 12.
• the user interface 112 may be configured to receive one or more inputs from a user of the master device 101.
• the user interface 112 may also be configured to display information (e.g., text and/or images) to the user of the master device 101.
• the user interface 1 12 may exchange data to and/or from the processing system 101 via the bus interface 108.
• the master device 101 may also include a transceiver 110.
• the transceiver 110 may be configured to receive data and/or transmit data in communication with another apparatus.
• the transceiver 1 10 provides a means for communicating with another apparatus via a wired or wireless transmission medium.
• the transceiver 1 10 may provide the means for establishing a wireless docking session with another apparatus and/or device, such as the slave device 102.
• the transceiver 1 10 may be configured to perform such communications using various types of technologies. One of ordinary skill in the art will understand that many types of technologies to perform such communication may be used without deviating from the scope of the present disclosure.
• the master device 101 may also include a memory 1 14, one or more processors
• the bus interface 108 may provide an interface between a bus 103 and the transceiver 1 10.
• the memory 1 14, the one or more processors 104, the computer-readable medium 106, and the bus interface 108 may be connected together via the bus 103.
• the processor 104 may be communicatively coupled to the transceiver 110 and/or the memory 1 14.
• the processor 104 may include a profile determination circuit 120.
• the profile determination circuit 120 may include various hardware components and/or software modules that can perform various functions and/or enable various aspects associated with the profile of the master device 101.
• the profile of the master device 101 may refer to the set of parameters and/or functions that characterize the operability and/or user experience of the master device 101.
• the profile of the master device 101 may include information related to the operating system of the master device 101, one or more peripheral components of the master device 101, a display size of one or more displays of the master device 101, a display resolution of one or more displays of the master device 101, a touch screen-capability of the master device 101, one or more font types of the master device 101, one or more user settings of the master device 101, an extended display identification data (EDID) of the master device 101, the power source/availability of the master device 101, one or more hardware components of the master device 101, and/or one or more software modules of the master device 101. Additional description pertaining to the profile of the master device 101 is provided throughout this disclosure.
• the profile determination circuit 120 provides the means for determining whether a profile of another device (e.g., the slave device 102) matches one of a plurality of profiles stored in the master device 101.
• the processor 104 may also include a data exportation circuit 121.
• the data exportation circuit 121 may include various hardware components and/or software modules that can perform various functions and/or enable various aspects associated with exporting data from the master device 101.
• the data may be exported to another device (e.g., the slave device 102).
• the profile of the slave device 102 matches one of the plurality of profiles stored in the master device 101.
• the data exportation circuit 121 provides the means for exporting data to the slave device 102 in a format associated with the profile of the slave device 102.
• the profile of the slave device 102 does not match one of the plurality of profiles stored in the master device 101.
• the data exportation circuit 121 provides the means for exporting data to the slave device 102 in a format associated with a default profile of the master device 101.
• the processor 104 may also include a notification circuit 122.
• the notification circuit 122 may include various hardware components and/or software modules that can perform various functions and/or enable various aspects associated with providing notifications to the master device 101 and/or the slave device 102.
• the notification circuit 122 provides the means for providing an error message on the master device 101 and/or the slave device 102.
• the error message may indicate that none of the profiles stored in the master device 101 matches any of the profiles of the slave device 102.
• the slave device 102 is within a proximity range of the master device 101.
• the proximity range may be a particular distance relative to the location of the master device 101.
• the notification circuit 122 provides the means for providing a notification for display on the slave device 102.
• such notifications may include various alerts, such as 'low-battery' alerts. Because the slave device 102 is within the proximity range of the master device 101, notifications displayed on the slave device 102 are more likely to be viewed by the user.
• the slave device 102 is beyond the proximity range of the master device 101.
• the master device 101 e.g., a smartphone
• the slave device 102 may be moved by the user out of a room having the slave device 102 (e.g., a desktop computer).
• the notification circuit 122 provides the means for providing various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the master device 101. Because the user (together with the master device 101) has moved beyond the proximity range of the master device 101, notifications displayed on the slave device 102 are less likely to be viewed by the user, and notifications displayed on the master device 101 are more likely to be viewed by the user.
• the processor 104 may also include an attribute adjustment circuit 123.
• the attribute adjustment circuit 123 may include various hardware components and/or software modules that can perform various functions and/or enable various aspects associated with adjusting an attribute of the data for export to the slave device 102.
• the attributes of the data may be adjusted based on bandwidth availability.
• the attributes adjustment circuit 123 provides the means for adjusting the attribute of the data for export to the slave device 102 based on bandwidth availability. Attributes that may be adjusted include a file size, a refresh rate, a display resolution, a bit rate, a quality parameter, and/or a domain. Such attributes may be adjusted such that the exported data occupies relatively less bandwidth when bandwidth availability is relatively low. Conversely, such attributes may be adjusted such that the exported data occupies relatively more bandwidth when bandwidth availability is relatively high.
• processor 104 of the master device 101.
• various circuits have been described above, one of ordinary skill in the art will understand that the processor 104 may also include various other circuits 124 that are in addition and/or alternative(s) to circuits 120, 121, 122, 123. Such other circuits 124 may provide the means for performing any one or more of the functions, methods, processes, features and/or aspects described herein.
• the computer-readable medium 106 may include various instructions.
• the instructions may include computer-executable code configured to perform various functions and/or enable various aspects described herein.
• the computer-executable code may be executed by various hardware components (e.g., the processor 104) of the master device 101.
• the instructions may be a part of various software programs and/or software modules.
• the computer-readable medium 106 may include profile determination instructions 140.
• the profile determination instructions 140 may include computer- executable code configured for performing various functions and/or enable various aspects associated with the profile of the master device 101.
• the profile of the master device 101 may refer to the set of parameters and/or functions that characterize the operability and/or user experience of the master device 101.
• the profile of the master device 101 may include information related to the operating system of the master device 101, one or more peripheral components of the master device 101, a display size of one or more displays of the master device 101, a display resolution of one or more displays of the master device 101, a touch screen-capability of the master device 101, one or more font types of the master device 101, one or more user settings of the master device 101, an EDID of the master device 101, the power source/availability of the master device 101, one or more hardware components of the master device 101, and/or one or more software modules of the master device 101. Additional description pertaining to the profile of the master device 101 is provided throughout this disclosure.
• the profile determination instructions 140 may include computer-executable code configured for determining whether a profile of another device (e.g., the slave device 102) matches one of a plurality of profiles stored in the master device 101.
• the computer-readable medium 106 may also include data exportation instructions 141.
• the data exportation instructions 141 may include computer- executable code configured for performing various functions and/or enable various aspects associated with exporting data from the master device 101.
• the data may be exported to another device (e.g., the slave device 102).
• the profile of the slave device 102 matches one of the plurality of profiles stored in the master device 101.
• the data exportation instructions 141 may include computer-executable code configured for exporting data to the slave device 102 in a format associated with the profile of the slave device 102.
• the profile of the slave device 102 does not match one of the plurality of profiles stored in the master device 101.
• the data exportation instructions 141 may include computer-executable code configured for exporting data to the slave device 102 in a format associated with a default profile of the master device 101.
• the computer-readable medium 106 may also include notification instructions
• the notification instructions 142 may include computer-executable code configured for performing various functions and/or enable various aspects associated with providing notifications to the master device 101 and/or the slave device 102.
• the notification instructions 142 may include computer executable code configured for providing an error message on the master device 101 and/or the slave device 102.
• the error message may indicate that none of the profiles stored in the master device 101 match any of the profiles of the slave device 102.
• the slave device 102 is within a proximity range of the master device 101.
• the proximity range may be a particular distance relative to the location of the master device 101.
• the notification instructions 142 include computer-executable code configured for providing a notification for display on the slave device 102.
• such notifications may include various alerts, such as 'low-battery' alerts. Because the slave device 102 is within the proximity range of the master device 101, notifications displayed on the slave device 102 are more likely to be viewed by the user.
• the slave device 102 is beyond the proximity range of the master device 101.
• the master device 101 e.g., a smartphone
• the slave device 102 may be moved by the user out of a room having the slave device 102 (e.g., a desktop computer).
• the notification instructions 142 include computer-executable code configured for providing various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the master device 101. Because the user (together with the master device 101) has moved beyond the proximity range of the master device 101, notifications displayed on the slave device 102 are less likely to be viewed by the user, and notifications displayed on the master device 101 are more likely to be viewed by the user.
• the computer-readable medium 106 may also include attribute adjustment instructions 143.
• the attribute adjustment instructions 143 include computer-executable code configured for performing various functions and/or enable various aspects associated with adjusting an attribute of the data for export to the slave device 102.
• the attributes of the data may be adjusted based on bandwidth availability.
• the attributes adjustment instructions 143 include computer- executable code configured for adjusting the attribute of the data for export to the slave device 102 based on bandwidth availability. Attributes that may be adjusted include a file size, a refresh rate, a display resolution, a bit rate, a quality parameter, and/or a domain. Such attributes may be adjusted such that the exported data occupies relatively less bandwidth when bandwidth availability is relatively low. Conversely, such attributes may be adjusted such that the exported data occupies relatively more bandwidth when bandwidth availability is relatively high.
• the computer-readable medium 106 may also include various other instructions 144 that are in addition and/or alternative(s) to instructions 140, 141, 142, 143.
• Such other instructions 144 may include computer-executable code configured for performing any one or more of the functions, methods, processes, features and/or aspects described herein.
• the memory 1 14 may include various memory modules.
• the memory modules may be configured to store, and have read therefrom, various values and/or information by the processor 104, or any of its circuits 120, 121, 122, 123, 124.
• the memory modules may also be configured to store, and have read therefrom, various values and/or information upon execution of the computer-executable code included in the computer-readable medium 106, or any of its instructions 140, 141, 142, 143, 144.
• the memory 1 14 may include profile information 130.
• the profile information may include data pertaining to the set of parameters and/or functions that characterize the operability and/or user experience of the master device 101.
• the profile information 130 may also include data related to the operating system of the master device 101, one or more peripheral components of the master device 101, a display size of one or more displays of the master device 101, a display resolution of one or more displays of the master device 101, a touch screen-capability of the master device 101, one or more font types of the master device 101, one or more user settings of the master device 101, an EDID of the master device 101, the power source/availability of the master device 101, one or more hardware components of the master device 101, and/or one or more software modules of the master device 101.
• the memory 1 14 may also include various types of data that may be exported to the slave device 102.
• a non-limiting example of such data is application data 131.
• the application data 131 may be generated by an application running in the master device 101.
• the application data 131 may be exported from the master device 101 to the slave device 102 in accordance to various configurations described herein.
• application data 131 is provided as a non- limiting example, one of ordinary skill in the art will understand that additional and/or alternative types of data may be stored in the memory and exported from the master device 101 to the slave device 102 without deviating from the scope of the present disclosure.
• the memory 1 14 may also include various other memory modules 132.
• the other memory modules 132 may be configured for storing information therein, and reading information therefrom, with respect to any of the features, functions, methods, processes, and/or aspects described herein.
• the master device 101 may include alternative and/or additional elements without deviating from the scope of the present disclosure.
• an element, or any portion of an element, or any combination of elements may be implemented with a processing system 101 that includes one or more processors 104.
• Examples of the one or more processors 104 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
• the processing system 101 may be implemented with a bus architecture, represented generally by the bus 103 and bus interface 108.
• the bus 103 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 101 and the overall design constraints.
• the bus 103 may link together various circuits including the one or more processors 104, the memory 114, and the computer-readable media 106.
• the bus 103 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art.
• the one or more processors 104 may be responsible for managing the bus 103 and general processing, including the execution of software stored on the computer- readable medium 106.
• the software when executed by the one or more processors 104, causes the processing system 101 to perform the various functions described below for any one or more apparatuses.
• the computer-readable medium 106 may also be used for storing data that is manipulated by the one or more processors 104 when executing software.
• Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
• the software may reside on the computer-readable medium 106.
• the computer-readable medium 106 may be a non-transitory computer-readable medium.
• a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
• a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
• an optical disk e.g., a compact disc (CD) or a digital versatile disc (DVD)
• a smart card e.g., a flash memory device (e.g.
• the computer-readable medium 106 may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer.
• the computer-readable medium 106 may reside in the processing system 101, external to the processing system 101, or distributed across multiple entities including the processing system 101.
• the computer-readable medium 106 may be embodied in a computer program product.
• a computer program product may include a computer-readable medium in packaging materials.
• FIGS. 2- ⁇ are diagrams 200, 300, 400 illustrating examples of user interfaces
• the master device 101 may include one or more profiles. As described above, the profile may refer to the set of parameters and/or functions that characterize the operability and/or user experience of the master device 101.
• the profile of the master device 101 may include a particular operating system-based user experience.
• FIG. 2 illustrates an example of a user interface 204 of a profile that provides an iOSTM operating system-based user experience for the user of the master device 101.
• FIG. 3 illustrates an example of a user interface 304 of a profile that provides a WindowsTM operating system-based user experience for the user of the master device 101.
• FIG. 4 illustrates an example of a user interface 404 of a profile that provides an AndroidTM operating system-based user experience for the user of the master device 101.
• FIGS. 2- ⁇ illustrate non- limiting examples of various operating system-based user experiences that may be a part of the profile of the master device 101.
• the profile of the master device 101 does not necessarily need to include features associated with an operating system.
• the profile includes the parameters and/or functions that characterize the operability and/or user experience of the master device 101.
• the profile of the master device 101 may include information related to one or more peripheral components of the master device 101, a display size of one or more displays of the master device 101, a display resolution of one or more displays of the master device 101, a touch screen-capability of the master device 101, one or more font types of the master device 101, one or more user settings of the master device 101, an EDID of the master device 101, the power source/availability of the master device 101, one or more hardware components of the master device 101, and/or one or more software modules of the master device 101.
• FIGS. 5-7 are diagrams 500, 600, 700 illustrating examples of user interfaces
• the slave device 102 may include one or more profiles.
• the profile includes the parameters and/or functions that characterize the operability and/or user experience of the slave device 102.
• the profile of the slave device 102 may include a particular operating system-based user experience.
• FIG. 5 illustrates an example of a user interface 504 of a profile that provides an iOSTM operating system-based user experience for the user of the slave device 102.
• FIG. 6 illustrates an example of a user interface 604 of a profile that provides a WindowsTM operating system-based user experience for the user of the slave device 102.
• FIG. 7 illustrates an example of a user interface 704 of a profile that provides an AndroidTM operating system-based user experience for the user of the slave device 102.
• FIGS. 5-7 illustrate non- limiting examples of various operating system-based user experiences that may be a part of the profile of the slave device 102.
• the profile of the slave device 102 does not necessarily need to include features associated with an operating system.
• the profile includes the parameters and/or functions that characterize the operability and/or user experience of the slave device 102.
• the profile of slave device 102 may include information related to one or more peripheral components of the slave device 102, a display size of one or more displays of the slave device 102, a display resolution of one or more displays of the slave device 102, a touch screen- capability of the slave device 102, one or more font types of the slave device 102, one or more user settings of the slave device 102, an EDID of the slave device 102, the power source/availability of the slave device 102, one or more hardware components of the slave device 102, and/or one or more software modules of the slave device 102.
• FIGS. 8-9 are diagrams 800, 900 illustrating examples of various profiles of the master device 101 and the slave device 102.
• the master device 101 and the slave device 102 may be connected wirelessly together via a wireless docking system.
• a wireless docking system may provide seamless connectivity, enabling two or more devices to connect together without needing wires, a docking connector, a personal identification number (PIN) code, elaborate pairing process per peripheral, or other similar steps.
• Peripherals associated with the slave device 102 may act as a group. Many different types of peripherals may be supported, including bridging of legacy peripherals. Existing application sessions/connections may be left intact.
• the master device 101 and the slave device 102 may receive and/or transmit various types of information.
• the master device 102 may transmit a probe request to the slave device 102.
• the slave device 102 may transmit a response message.
• Such exchanges of information may allow the master device 101 to discover the slave device 102.
• the master device 101 and the slave device 102 may also engage in various authentication/association exchanges.
• the master device 101 and the slave device 102 may also engage in a handshake procedure as well as a channel establishment process.
• every feature described in the above non-limiting example is not necessarily required and that alternative and/or additional steps may be implemented without deviating from the scope of the present disclosure.
• the master device 101 may determine the profile of the slave device 102 and compare the profile of the slave device 102 with a look-up table stored in the master device 101 (e.g., a look-up table stored in the profile information 130). Such a comparison may reveal whether the profile of the slave device 102 matches any of the profiles stored in the master device 101.
• FIG. 8 is a diagram 800 illustrating an example wherein at least one of the profiles stored in the master device 101 matches a profile of the slave device 102. Matching may existing when at least one of the parameters and/or functions that characterize the operability and/or user experience of a first device (e.g., the master device 101) is the same as or similar to at least one of the parameters and/or functions that characterize the operability and/or user experience of a second device (e.g., the slave device 102).
• the example provided in FIG. 8 depicts three profiles (e.g., Profile A 802, Profile B 804, Profile C 806).
• Profile A 802, Profile B 804, Profile C 806 e.g., Profile A 802, Profile B 804, Profile C 806
• Profile A 802 of the master device 101 may include the parameters and/or functions that characterize an iOSTM operating system-based user experience. Accordingly, the master device 101 may be capable of providing the user interface 204.
• Profile B 804 of the master device 101 may include the parameters and/or functions that characterize a WindowsTM operating system-based user experience. Accordingly, the master device 101 may be capable of providing the user interface 304.
• Profile C 806 of the master device 101 may include the parameters and/or functions that characterize an AndroidTM operating system-based user experience. Accordingly, the master device 101 may be capable of providing the user interface 404.
• the slave device 102 has Profile B 808, which matches at least one of the profiles (e.g., Profile B 804) stored in the master device 101.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format associated with the profile of the slave device 102.
• Exporting may be performed via wireless transmission over one of various wireless communication interfaces (e.g., a WLAN interface and/or a BluetoothTM interface).
• Exporting may also include an encryption process, wherein the data to be exported is encrypted prior to wireless transmission from the master device 101 to the slave device 102.
• a format of the data may refer to the configuration and/or formatting of the data.
• Data may be successfully processed by the slave device 102 when the data is formatted in a manner that enables that the slave device 102 to process the data by its processing system. If the data is not formatted in such a manner, the data may be incompatible with the slave device 102.
• Profile B 804, 808 includes the parameters and/or functions that characterize a WindowsTM operating system-based user experience.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format that provides a WindowsTM operating system-based user experience.
• the slave device 102 provides a visualization that corresponds to a WindowsTM operating system.
• the slave device 102 displays the user interface 604.
• FIG. 9 is a diagram illustrating an example wherein none of the profiles stored in the master device 101 matches the profile of the slave device 102.
• the slave device 102 has Profile D 908.
• Profile D 908 is not included as any of the profiles (e.g., Profile A 802, Profile B 804, Profile C 806) stored in the master device 101.
• the master device 201 may provide an error message 910.
• the error message 910 may be a visual message provided for display on a display component of the master device 101 and/or a display component of the slave device 102. For example, as illustrated in FIG. 9, the error message 910 may appear on a portion of the user interface 504 of the slave device 201.
• An error message may, alternatively or additionally, be an auditory message provided for playing on the master device 101 and/or the slave device 102.
• Alternative forms of providing an error message may be implemented without deviating from the scope of the present disclosure.
• the master device 101 may export data to the slave device 102 in a format associated with a default profile of the master device 101.
• a default profile of the master device 101 may be a profile that is preferred by the user. For instance, the user may set Profile A 802 as the default profile because the user prefers the user interface of that profile over the user interface of other profiles.
• a default profile of the master device 101 may be a profile that is set by the manufacturer of the master device. For instance, the manufacturer may set Profile A 802 as the default profile because the master device 101 is configured to operate more efficiently using that profile relative to other profiles.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in the format of the default profile of the master device 101 (e.g., Profile A 802). Because Profile A 802 includes the parameters and/or functions that characterize an iOSTM operating system-based user experience, the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format that provides an iOSTM operating system-based user experience. As such, the slave device 102 provides a visualization that corresponds to an iOSTM operating system.
• FIGS. 10-1 1 are diagrams 1000, 1100 illustrating examples of proximities of the slave device 102 relative to the master device 101.
• the master device 101 may have a proximity range 1002.
• the proximity range may be a distance (e.g., measured in units of feet or meters).
• the proximity range 1002 may be preselected by the user of the slave device 102.
• the proximity range 1002 may be preset by the manufacturer of the master device 101.
• Various techniques may be used to determine the proximity range 1002.
• the proximity range 1002 may be determined using the received signal strength of a signal (e.g., a pilot signal) from another device (e.g., the slave device 102). As another example, the proximity range 1002 may be determined using calculations of 'round-trip time' of a signal originating from the master device 101. Additional or alternative techniques for determining the proximity range 1002 are known to one of ordinary skill in the art and may be used without deviating from the scope of the present disclosure. Given the capability of the master device 101 and the slave device 102 to communicate wirelessly with each other, these devices may be moved closer / farther apart relative to each other during normal use.
• a signal e.g., a pilot signal
• the proximity range 1002 may be determined using calculations of 'round-trip time' of a signal originating from the master device 101. Additional or alternative techniques for determining the proximity range 1002 are known to one of ordinary skill in the art and may be used without deviating from the scope of the present disclosure. Given the capability of the master device 101 and the slave device 102 to
• FIG. 10 is a diagram 1000 illustrating an example wherein the slave device 102 is within the proximity range 1002 of the master device 101.
• the master device 101 e.g., a smartphone
• the slave device e.g., a desktop computer
• the master device 101 may provide various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the slave device 102. Because the slave device 102 is within the proximity range 1002 of the master device 101, notifications displayed on the slave device 102 are more likely to be viewed by the user.
• FIG. 11 is a diagram 1100 illustrating an example wherein the slave device 102 is beyond the proximity range 1002 of the master device 101.
• the master device 101 e.g., the smartphone
• the slave device 102 may be moved by the user out of the room having the slave device 102 (e.g., the desktop computer).
• the master device 101 may provide various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the master device 101. Because the user has moved (together with the master device 101) beyond the proximity range 1002 of the master device 101, notifications displayed on the slave device 102 are less likely to be viewed by the user, and notifications displayed on the master device 101 are more likely to be viewed by the user.
• FIG. 12 is a diagram 1200 illustrating an example of various items displayed on the master device 101 and the slave device 102.
• FIG. 12 illustrates a smartphone as the master device 101 and a desktop computer as the slave device 102.
• the master device 101 may include a display 1204 (e.g., the user interface 1 12) configured for displaying various information to the user.
• the display 1204 may display one or more icons corresponding to various applications.
• One or more applications may be running at the same time.
• One or more of the launched applications may be running in the foreground.
• One or more of the launched applications may be running in the background.
• four applications e.g., applications 1212, 1214, 1216, 1218
• FIG. 12 For the sake of simplicity and illustration, four applications (e.g., applications 1212, 1214, 1216, 1218) are illustrated in FIG. 12.
• applications 1212, 1214 are running in the foreground and that applications 1216, 1218 are running in the background.
• the profile of the slave device 102 is included in the plurality of profiles stored in the master device 101.
• the master device 101 e.g., the smartphone
• the slave device 102 e.g., the desktop computer
• a format associated with the profile of the slave device 102 e.g., the desktop computer's WindowsTM operating system
• an indication e.g., an icon
• an indication for every launched application (e.g., applications 1212, 1214, 1216, 1218) is displayed in a task bar 1210 of the slave device 102.
• one or more applications running in the foreground e.g., applications 1212, 1214
• an application running in the foreground e.g., applications 1212, 1214
• the master device 101 may adjust one or more attributes of the data for export to the slave device 102 based on bandwidth availability.
• an attribute may include a file size, a refresh rate, a display resolution, a bit rate, a quality parameter, and/or a domain.
• Alternative attributes of data are readily apparent to one of ordinary skill in the art and may adjusted based on bandwidth availability without deviating from the scope of the present disclosure.
• the master device 101 may increase the resolution of an item displayed on the slave device 102 when bandwidth availability is high, and the master device 101 may decrease the resolution of the item displayed on the slave device 102 when bandwidth availability is low.
• the master device 101 may increase the refresh rate of an item displayed on the slave device 102 when bandwidth availability is high, and the master device 101 may decrease the refresh rate of the item displayed on the slave device 102 when bandwidth availability is low.
• two different types of applications may be transmitted across different domain types.
• a productivity-type application e.g., a word processing application or spreadsheet application
• other types of applications may be transmitted over a pixel domain.
• the master device 101 may turn off the display 1204 of the master device 101 after exporting the data to the slave device 102. By turning off the display 1204 of the master device 101, the master device 101 may conserve power. However, turning off the display 1204 of the master device 101 is not a requirement. In some other configurations, the master device 101 may keep the display 1204 of the master device 101 turned on and use that display 1204 as an extended display of the slave device 102.
• the slave device 102 may display a website differently than the display of that website on the master device 101.
• the master device 101 may display the website according to a first a uniform resource locator (URL) (e.g., a URL configured for display on a mobile device, such as "rn.exampleURL.com”), and the slave device may display the website according to a second URL (e.g., a URL configured for display on a non-mobile device, such as "exampleURL.com”).
• URL uniform resource locator
• the master device 101 may export the data in a format that complies with a government regulation.
• the slave device 102 may be a device inside of an automobile.
• the master device 101 may export data to the slave device 102 in a format that complies with automotive safety standards. Some automotive safety standards may require speech-to-text and/or text-to- speech capabilities for such devices. Accordingly, the master device 101 may export data to the slave device 102 in a format that accommodates for the speech-to-text and/or text-to-speech capabilities of the slave device 102.
• FIG. 13 is a first diagram 1300 illustrating an example of various methods and/or processes.
• the methods and/or processes described with reference to FIG. 13 may be performed by any device.
• the first device may be the master device 101, as described in greater detail above.
• the first device may establish a wireless docking session with a second device (e.g., slave device 102).
• the first device may determine whether a profile of the second device matches one a plurality of profiles stored in the first device.
• the second device may be the slave device 102, as described in greater detail above.
• the first device provides an error message.
• the slave device 102 has Profile D 908.
• Profile D 908 is not included as any one of the profiles (e.g., Profile A 802, Profile B 804, Profile C 806) stored in the master device 101.
• the master device 201 may provide an error message 910.
• the error message 910 may be a visual message provided for display on a display component of the master device 101 and/or a display component of the slave device 102.
• an error message may be an auditory message provided for playing on the master device 101 and/or the slave device 102.
• Other forms of providing an error message may be used without deviating from the scope of the present disclosure.
• the first device may export data to the second device in a format associated with the profile of the second device.
• the slave device 102 has Profile B 808.
• the master device 101 includes Profile B 804. Accordingly, a profile (e.g., Profile B 808) of the slave device 102 matches one of the profiles (e.g., Profile B 804) stored in the master device 101.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format associated with the profile of the slave device 102.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format that provides a WindowsTM operating system-based user experience. Accordingly, the slave device 102 provides a visualization that corresponds to a WindowsTM operating system (i.e., user interface 604).
• a WindowsTM operating system i.e., user interface 604
• the first device may determine whether the second device is within a proximity range of the first device.
• the master device 101 may determine whether the slave device 102 is within the proximity range 1002 of the master device 101.
• the proximity range may be a distance (e.g., measured in units of feet or meters).
• the proximity range 1002 may be preselected by the user of the slave device 102.
• the proximity range 1002 may be preset by the manufacturer of the master device 101. Various techniques may be used to determine the proximity range 1002, as described in greater detail above.
• the first device may provide a notification for display on the second device.
• the master device 101 e.g., a smartphone
• the slave device 102 e.g., a desktop computer
• the master device 101 may provide various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the slave device 102. Because the slave device 102 is within the proximity range 1002 of the master device 101, notifications displayed on the slave device 102 are more likely to be viewed by the user.
• the first device may provide the notification for display on the first device.
• the slave device 102 is beyond the proximity range 1002 of the master device 101.
• the master device 101 e.g., the smartphone
• the slave device 102 may be moved by the user out of the room having the slave device 102 (e.g., the desktop computer).
• the master device 101 may provide various notifications (e.g., alerts, such as 'low-battery' alerts) for display on the master device 101. Because the user has moved (together with the master device 101) beyond the proximity range 1002 of the master device, notifications displayed on the slave device 102 are less likely to be viewed by the user, and notifications displayed on the master device 101 are more likely to be viewed by the user.
• FIG. 14 is a second diagram 1400 illustrating an example of various methods and/or processes.
• the methods and/or processes described with reference to FIG. 14 may be performed by any device.
• the first device may be the master device 101, as described in greater detail above.
• the first device may establish a wireless docking session with a second device (e.g., slave device 102).
• the first device may determine whether a profile of the second device matches one a plurality of profiles stored in the first device.
• the second device may be the slave device 102, as described in greater detail above.
• the first device may export data to the second device in a format associated with a default profile of the first device.
• the master device 101 may export data to the slave device 102 in a format associated with the default profile of the master device 101.
• the default profile for the master device 101 is Profile A 802.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in the format of the default profile of the master device 101 (e.g., Profile A 802). Because Profile A 802 includes the parameters and/or functions that characterize an iOSTM operating system-based user experience, the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format that provides an iOSTM operating system-based user experience. Accordingly, the slave device 102 provides a visualization corresponding to an iOSTM operating system (i.e., user interface 504).
• an iOSTM operating system i.e., user interface 504
• the first device may export data to the second device in a format associated with the profile of the second device.
• the slave device 102 has Profile B 808.
• the master device 101 includes Profile B 804. Accordingly, a profile (e.g., Profile B 808) of the slave device 102 matches one of the profiles (e.g., Profile B 804) stored in the master device 101.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format associated with the profile of the slave device 102.
• the master device 101 may export data to the slave device 102 (e.g., during the wireless docking session) in a format that provides a WindowsTM operating system-based user experience. Accordingly, the slave device 102 provides a visualization that corresponds to a WindowsTM operating system (i.e., user interface 604).
• a WindowsTM operating system i.e., user interface 604
• the first device may adjust an attribute of the data for export to the second device based on bandwidth availability.
• an attribute may include a file size, a refresh rate, a display resolution, a bit rate, a quality parameter, and/or a domain.
• Alternative attributes of data are readily apparent to one of ordinary skill in the art and may adjusted based on bandwidth availability without deviating from the scope of the present disclosure.
• the master device 101 may increase the resolution of an item displayed on the slave device 102 when bandwidth availability is high, and the master device 101 may decrease the resolution of the item displayed on the slave device 102 when bandwidth availability is low.
• the master device 101 may increase the refresh rate of an item displayed on the slave device 102 when bandwidth availability is high, and the master device 101 may decrease the refresh rate of the item displayed on the slave device 102 when bandwidth availability is low.
• FIGS. 13-14 are provided for illustrative purposes and are not intended to limit the scope of the present disclosure.
• the methods and/or processes described with reference to FIGS. 13-14 may be performed in sequences different from those illustrated therein without deviating from the scope of the present disclosure. Additionally, some or all of the methods and/or processes described with reference to FIGS. 13-14 may be performed individually and/or together without deviating from the scope of the present disclosure.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Networks & Wireless Communication (AREA)
• Software Systems (AREA)
• Signal Processing (AREA)
• Computer Hardware Design (AREA)
• Telephone Function (AREA)
• User Interface Of Digital Computer (AREA)
• Information Transfer Between Computers (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (3)

Applications Claiming Priority (4)

Publications (1)

Family

ID=54870912

Family Applications (1)

Country Status (5)

Families Citing this family (6)

Citations (3)

Family Cites Families (10)

• 2014
  • 2014-12-22 US US14/579,059 patent/US20150373483A1/en not_active Abandoned
• 2015
  • 2015-06-18 WO PCT/US2015/036505 patent/WO2015200100A1/en not_active Ceased
  • 2015-06-18 EP EP15739376.0A patent/EP3158450A1/en not_active Withdrawn
  • 2015-06-18 CN CN201580033467.9A patent/CN106462531A/zh active Pending
  • 2015-06-18 JP JP2016574389A patent/JP2017522805A/ja active Pending

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events