U.S. patent application number 14/829970 was filed with the patent office on 2016-08-11 for system and methods for settings cards.
This patent application is currently assigned to JAMDEO CANADA LTD.. The applicant listed for this patent is Hisense Electric Co., Ltd., Hisense International Co., Ltd., Hisense USA CORP., Jamdeo Canada Ltd.. Invention is credited to Alexander DE PAZ, Sergii GRYSENKO, Mohammed Selim, Sanjiv SIRPAL, Salvador SOTO.
Application Number | 20160234075 14/829970 |
Document ID | / |
Family ID | 56565293 |
Filed Date | 2016-08-11 |
United States Patent
Application |
20160234075 |
Kind Code |
A1 |
SIRPAL; Sanjiv ; et
al. |
August 11, 2016 |
SYSTEM AND METHODS FOR SETTINGS CARDS
Abstract
The present disclosure relates to methods and devices for the
presentation, configuration and operation of an application,
including a user interface. In one embodiment, a method includes
allowing one or more card elements for a user interface of a device
to interact with other devices. Another embodiment is directed to a
device configured to provide a user interface and allow for user
interaction, including interaction with other devices. The device
includes one or more elements to present one or more card elements
for a user interface of the device. The device may include a
display and a controller configured to control presentation of a
card element for a user interface of a device, and control
operation of at least one of the device and the user interface
based on an operation associated with the card element.
Inventors: |
SIRPAL; Sanjiv; (Oakville,
CA) ; Selim; Mohammed; (Oakville, CA) ; DE
PAZ; Alexander; (Burlington, CA) ; SOTO;
Salvador; (Toronto, CA) ; GRYSENKO; Sergii;
(Burlington, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Jamdeo Canada Ltd.
Hisense Electric Co., Ltd.
Hisense USA CORP.
Hisense International Co., Ltd. |
Oakville
Qingdao
Suwanee
Qingdao |
GA |
CA
CN
US
CN |
|
|
Assignee: |
JAMDEO CANADA LTD.
Oakville
GA
HISENSE INTERNATIONAL CO., LTD.
Qingdao
HISENSE USA CORP.
Suwanee
HISENSE ELECTRIC CO., LTD.
Qingdao
|
Family ID: |
56565293 |
Appl. No.: |
14/829970 |
Filed: |
August 19, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
62113225 |
Feb 6, 2015 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G09G 2354/00 20130101;
G06F 3/04847 20130101; G06F 3/0485 20130101; H04L 12/2807 20130101;
G06F 3/0482 20130101; G06F 3/04842 20130101; G06F 3/0486 20130101;
H04L 51/046 20130101; H04N 21/4516 20130101; H04N 21/44227
20130101; H04N 21/812 20130101; G06F 3/04845 20130101; H04N 21/4882
20130101; H04L 41/12 20130101; G06F 3/04817 20130101; G06F 3/1454
20130101; G06F 3/017 20130101; H04N 21/4402 20130101; H04N 21/458
20130101; H04L 41/22 20130101; H04N 21/42653 20130101; H04L 67/303
20130101; H04N 21/4826 20130101; G06F 3/0481 20130101; H04L 41/0806
20130101; H04L 67/306 20130101; G06F 3/04883 20130101; G06F 3/1415
20130101; G09G 5/005 20130101 |
International
Class: |
H04L 12/24 20060101
H04L012/24; G06F 3/0484 20060101 G06F003/0484 |
Claims
1. A method for using a card, the method comprising: displaying, by
a first device, a user interface, wherein the user interface is
presented including graphical elements for one or more card
elements, and wherein the user interface is presented including
graphical elements for one or more devices; displaying, by the
first device, a graphical element for a card, based on a selection
of the card on the user interface; detecting, by the first device,
a control input, the control input being an input for the card; and
outputting, by the first device, a control command based on the
control input, wherein the control command is configured to control
the operation of one or more devices associated with the card.
2. The method of claim 1, wherein the card is a micro-application
configured to control one or more devices associated with the
card.
3. The method of claim 1, wherein the control command is configured
to control the operation of a display device.
4. The method of claim 1, wherein the control command is configured
to control a plurality of devices.
5. The method of claim 1, wherein the control command is
pre-configured to control a plurality of associated devices.
6. The method of claim 1, wherein the card is configured for
limited control functionality of devices associated with the
card.
7. The method of claim 1, wherein the card is configured to be
loaned to devices associated within a location of card devices.
8. The method of claim 1, wherein the card stores a favorite
profile for a device.
9. The method of claim 1, wherein the card stores a user profile
associated with access to devices based on preferred settings.
10. A device comprising: a display; and a controller coupled to the
display, wherein the controller is configured to control display of
a user interface, wherein the user interface is presented including
graphical elements for one or more card elements, and wherein the
user interface is presented including graphical elements for one or
more of a plurality of devices; control display of display a
graphical element for a card, based on a selection of the card on
the user interface; detect a control input, the control input being
an input for the card; and output a control command based on the
control input, wherein the control command is configured to control
the operation of the plurality of devices associated with the
card.
11. The device of claim 10, wherein the card is a micro-application
configured to control one or more devices associated with the
card.
12. The device of claim 10, wherein the control command is
configured to control the operation of a display device.
13. The device of claim 10, wherein the control command is
configured to control the plurality of devices.
14. The device of claim 10, wherein the control command is
pre-configured to control a plurality of associated devices.
15. The device of claim 10, wherein the card is configured for
limited control functionality of devices associated with the
card.
16. The device of claim 10, wherein the card is configured to be
loaned to devices associated within a location of card devices.
17. The device of claim 10, wherein the card stores a favorite
profile for a device.
18. The device of claim 10, wherein the card stores a user profile
associated with access to devices based on preferred settings.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional
Application No. 62/113,225 titled SYSTEM AND METHODS FOR AN
APPLICATION CONFIGURATION AND PRESENTATION filed on Feb. 6, 2015,
the content of which is expressly incorporated by reference in its
entirety.
[0002] This application is related to the concurrently filed
applications entitled: SYSTEM AND METHODS FOR APPLICATION USER
INTERFACE PRESENTATION AND CARD ELEMENTS filed on ______ and
assigned patent application Ser. No. ______; SYSTEM AND METHODS FOR
CARD ELEMENT APPLICATION OPERATION filed on ______ and assigned
patent application Ser. No. ______; SYSTEM AND METHODS FOR CARD
EXCHANGE AND USER INTERFACE PRESENTATION filed on ______ and
assigned patent application Ser. No. ______; SYSTEM AND METHODS FOR
CONTROL OF CARD ELEMENTS WITHIN AN APPLICATION USER INTERFACE filed
on ______ and assigned patent application Ser. No. ______; SYSTEM
AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO DEVICES
filed on ______ and assigned patent application Ser. No. ______;
SYSTEM AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO
SPACES filed on ______ and assigned patent application Ser. No.
______; SYSTEMS AND METHODS FOR CONNECT TO CONTROL filed on ______
and assigned patent application Ser. No. ______; SYSTEMS AND
METHODS FOR DEVICE TO DEVICE CONTROL filed on ______ and assigned
patent application Ser. No. ______; and SYSTEM AND METHODS FOR
PRESENTATION OF A USER INTERFACE AND CARD ELEMENTS filed on ______
and assigned patent application Ser. No. ______, the disclosures of
which are expressly incorporated by reference.
FIELD
[0003] The present disclosure relates to electronic devices and
applications, and more particularly to systems, methods and devices
configured for exchange, communication and control based on card
elements.
BACKGROUND
[0004] Technologies associated with network devices, and in
particular personal devices, are implemented in various forms and
accessible from many sources. Conventional systems are often
limited by there configurations. For example, conventional
communication protocols and configurations do not allow for devices
to connect. Conventional systems that do allow for connectivity are
typically platform dependent and usually require profile
designations or authentication for interaction. Device
configuration requiring a platform specific configuration prevents
interaction makes it difficult for a user to interact with other
users, interact with other users' devices, or interoperate
devices.
BRIEF SUMMARY OF THE EMBODIMENTS
[0005] Systems, methods and devices are disclosed for using a
settings card. In one embodiment, a method for using a settings
card includes displaying, by a user device, a user interface. The
user interface presented includes graphical elements for one or
more card elements. The user interface presented includes graphical
elements for one or more space. The method further includes
presenting, by the user device, a graphical element for a settings
card, based on a selection of the settings card on the user
interface. The method further includes detecting, by the user
device, a control input, the control input being an input for the
settings card. The method further includes outputting, by the user
device, a control command which is based on the control input. The
control command is configured to control the operation of one or
more third-party devices, which are associated with the settings
card.
[0006] In another embodiment, a device is configured to system for
using a settings card includes a user interface. The system further
includes a controller, configured to control the presentation of a
card element for the user interface. The system further includes a
communications network, linking the user device to a plurality of
third-party devices. The system further includes the user device
presenting a user row and a device row on a user interface. The
system further includes the user device presenting a device list on
the user interface, the device list representing a plurality of
third-party devices. The system further includes the user device
presenting a plurality of user card elements on the user row, such
that the user card elements are associated with a selected
third-party device, the selected third-party device being one of
the plurality of third-party devices on the device list. The system
further includes one of the plurality of device card elements being
a device settings card. The system further includes the user device
allowing a user to select the device settings card and send the
device settings card to the user row. The system thus providing the
user with access to the device settings card.
[0007] Other aspects, features, and techniques will be apparent to
one skilled in the relevant art in view of the following brief
description of the figures and detailed description of the
exemplary embodiments.
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The features, objects, and advantages of the present
disclosure will become more apparent from the detailed description
set forth below when taken in conjunction with the drawings in
which like reference characters identify correspondingly throughout
and wherein.
[0009] FIG. 1A depicts a graphical representation of a simplified
system diagram according to one or more embodiments;
[0010] FIG. 1B depicts a graphical representation of system
entities according to one or more embodiments;
[0011] FIGS. 2A-2B depict graphical representations of methods of
using a settings card according to one or more embodiments;
[0012] FIG. 3 depicts a graphical representation of a user
interface according to one or more embodiments;
[0013] FIGS. 4A-4B depict a graphical representation of card
interaction within the user interface according to one or more
embodiments;
[0014] FIG. 5 depicts a settings card on the user interface, being
used to control a display device according to one or more
embodiments;
[0015] FIG. 6 depicts a settings card on the user interface, being
used to control a plurality of devices according to one or more
embodiments; and
[0016] FIG. 7 depicts a simplified diagram of a device according to
one or more embodiments.
DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS
Overview and Terminology
[0017] One aspect of the disclosure is to provide a method and a
system for using a settings card. In one embodiment, a mobile
operating system/experience (MOX) application is provided for the
method of using a settings card to control devices. In another
embodiment, a system is disclosed for using a settings card to
control devices.
[0018] As used herein, a card can relate to graphical elements
displayed in a user interface, wherein the card elements can allow
for one or more of exchange, communication, control and/or
application accessibility. Card elements may be associated with one
or more types of cards or capabilities. A card element may have a
data structure associated with the each card providing metadata
that can allow an application and/or devices to utilize the card.
According to one embodiment, each card element can include a
graphical element that is represented by a device and/or can
include a data record stored by one or more servers or devices that
allow for the card to be shard, transmitted, loaned, exchanged,
associated, pulled and/or pushed to one or more devices and spaces.
Card elements may define capabilities of devices and/or spaces.
Card elements may be associated with devices or spaces that are
real or virtual. Card elements may be uniquely identified.
[0019] As used herein, a MOX application relates to an application
having particular core elements that allow for the application to
be executed across many different devices and devices types. The
application may be platform agnostic and thus, configurable on one
or more operating systems or platform types (e.g., linux, etc.).
The MOX application provides connectivity, control and/or
communication relative to one or more devices. The MOX application
can be operated based on communication with a network and/or
pear-to-pear communication among devices. The MOX application may
operate within a network or system that is an ecosystem or MOX
ecosystem. The MOX application may be deployed on one or more
devices, entities or spaces that make up a MOX ecosystem.
[0020] According to one embodiment, the MOX system is an
application that runs on a mobile device. According to another
embodiment, MOX provides a unique user interface with many
features. Features of the MOX application can be characterized as
user interface (user experience) features and architectural
features. The MOX system incorporates cards. Cards are displayed as
visual elements in the user interface that can be manipulated to
provide exchange of data, capabilities, and allow for device
control. Card elements may be configured as containers.
[0021] As used herein, an entity relates to elements that that are
recognized and that make up an ecosystem of the application. An
entity may relate to a device, space, and users of an
application.
[0022] An ecosystem relates to collections of entities that are
associated.
[0023] Spaces relate to real and virtual locations that are
recognized by the application. By way of example, a space may be
assigned to one or more of a room, building, floor, home, office or
other physical location (e.g., cafe, office, etc.). Spaces may also
be assigned to virtual locations that do not have a corresponding
physical location.
[0024] A device can relate to devices configured to execute and run
a MOX application. A device can also relate to non-MOX devices.
Devices may refer to real and virtual devices.
[0025] Architectural aspects of the MOX application relate to the
card configuration, platform for operating with mobile device OS,
and underlying processes for card exchange functionality.
[0026] One embodiment is directed to processes for presentation of
a user interface and a device configured to present a user
interface, such as MOX, with cards.
[0027] Another embodiment is directed to an application platform,
processes and devices for operating within a MOX platform. MOX may
provide a common UI for multiplatform devices, such as a single
unified way to control or know even though devices are not
connected. The MOX architecture may include one or more of the
following attributes: use of cards as containers, defined card
architecture, card based metadata (Json Metadata). MOX may allow
for spaces and provide a visual of all spaces based on connection.
MOX may include a prioritization algorithm based on proximity,
known/history, places with access, etc. MOX may allow for a search
of virtual spaces. MOX may be configured with a MOX stack and MOX
plugin, and security features. MOX may allow the same card to
provide different actions on different devices. May be configured
to publish card into any device (virtual or real).
[0028] MOX may operate based on independently defined APIs, which
are available via a RESTful interface (similar to the cloud
interface). The APIs may be defined by an OEM to support the
device.
[0029] In certain embodiments, a MOX card itself is an HTML object,
containing relevant resources related to color pallet, and
branding, as well as the interactive components. Both the front and
the back of the card are supplied by the device itself, and are
validated by the cloud.
[0030] As used herein, the terms "a" or "an" shall mean one or more
than one. The term "plurality" shall mean two or more than two. The
term "another" is defined as a second or more. The terms
"including" and/or "having" are open ended (e.g., comprising). The
term "or" as used herein is to be interpreted as inclusive or
meaning any one or any combination. Therefore, "A, B or C" means
"any of the following: A; B; C; A and B; A and C; B and C; A, B and
C". An exception to this definition will occur only when a
combination of elements, functions, steps or acts are in some way
inherently mutually exclusive.
[0031] Reference throughout this document to "one embodiment,"
"certain embodiments," "an embodiment," or similar term means that
a particular feature, structure, or characteristic described in
connection with the embodiment is included in at least one
embodiment. Thus, the appearances of such phrases in various places
throughout this specification are not necessarily all referring to
the same embodiment. Furthermore, the particular features,
structures, or characteristics may be combined in any suitable
manner on one or more embodiments without limitation.
Exemplary Embodiments
[0032] Embodiments are directed to settings card interaction within
a mobile operating system/experience application. By allowing a
settings card to control devices, a user is able to interact with
multiple devices from a common user interface. The systems, methods
and devices allow for advanced interoperability between connected
devices.
[0033] Referring now to the figures, FIG. 1A depicts a graphical
representation of a simplified system diagram according to one or
more embodiments. System 100 may be configured for presentation of
an application by device 105. By way of example, system 100
includes one or more devices that may be configured with similar
core elements to allow for an application to reside on one or more
devices for connectivity, communication, exchange and/or control
relative to the devices. Based on the application, device 105 may
communicate and interoperate with one or more other devices, such
as devices 110.sub.1-n. According to another embodiment, device 105
may communicate and interoperate with one or more other devices,
such as devices 120.sub.1-n by way of a communication network
115.
[0034] Device 105 may be configured to execute an application, such
as a MOX application providing one or more functions, including but
not limited to viewing of cards associated with the user device,
viewing other devices and cards associated with other devices,
exchange of cards between the user device-exchange may be based on
one or more of push/fling, pull and exchange of cards and
contextual presentation of cards.
[0035] According to one embodiment, device 105 is configured to run
an application, such as a MOX application, wherein the application
is configured to present a user interface. Device 105 includes
memory and hardware configured to store and execute and
application, such as a MOX application and to operate with one or
more card elements.
[0036] According to one embodiment, devices 110.sub.1-n relate to
one or more devices in close proximity to device 105. Device 105
may be configured to communicate wirelessly with the devices
110.sub.1-n by way of the MOX application. Devices 110.sub.1-n
relate to devices associated with a particular space and/or
ecosystem. Accordingly, a user interface may identify and/or
include graphical elements for devices 110.sub.1-n and for card
elements of devices 110.sub.1-n. Devices 120.sub.1-n relate to
devices which may be communicated with over communication network
115. Devices 120.sub.1-n may relate to devices in close proximity
or distances from device 105. Devices 120.sub.1-n may relate to
electronic devices. In some embodiments, devices 120.sub.1-n
include one or more servers.
[0037] Device 105 may run a MOX application may allow for detection
of user input/touch command of a graphical element and movement
from one section of the display to another section where the
graphical element is a card element, and how the system processes
the movement (exchange, interact, control, etc.).
[0038] The MOX application can allow for one or more of card
presentation, association of cards and entities (e.g., devices,
virtual devices), transition of card and/or entities with respect
to user actions or spaces, display of cards based on capability
matching, selection of which cards to display, user and device
avatars, a summary view and detailed view of card, and card
comments.
[0039] Device 105 may present/provide a user interface and MOX
application to allow for hanging cards on devices, controlling
devices using cards, borrowing services (e.g., Wi-Fi) using cards,
capability sharing (e.g., sharing control of a device), and one or
more features built around sharing cards. Device 105 may detect
user input/touch commands of a graphical element and movement from
one section of the display to another section where the graphical
element is a card element. The MOX application processes movement
of cards (exchange, interact, control, etc.).
[0040] Device 105 includes a display configured to present a user
interface and a controller coupled to the display. The controller
is configured to present a user interface. An exemplary
representation of a user interface is depicted in FIG. 3 according
to one or more embodiments. The user interface is presented
including graphical elements for one or more card elements,
graphical elements for one or more spaces and devices, such as
devices 110.sub.1-n and devices 120.sub.1-n.
[0041] Architectural aspects of the MOX application can include
card configuration, platform for operating with mobile device OS,
and underlying processes for card exchange functionality.
[0042] Device 105 may be a mobile device or tablet executing an
application, such as the MOX application executed by device 105.
Although FIG. 1 depicts one device 105, it should be appreciated
that system 100 and the application may allow for multiple devices
to communicate and interoperate.
[0043] System 100 may include a server, such as one of devices
120.sub.1-n and device 105 may be configured to communicate with
the server. The device is configured to present a user interface
including graphical elements for one or more card elements, detect
a user interface command to associate a selected card element
presented by the user interface with a selected space presented by
the user interface, and output a communication to the server
including an association of the selected card element with the
selected space, wherein the association of the selected card with
the selected space includes updating metadata for the card
element.
[0044] FIG. 1B depicts a graphical representation of system
entities according to one or more embodiments. According to one or
more embodiments, an application or electronic platform is provided
for communication, control and exchange based on one or more
associations. FIG. 1B depicts a graphical representation of
application entities for a MOX application system. A MOX system 150
can include a plurality of devices, such as device 155. Device 155
may relate to a representation of device 105 of FIG. 1A. System 150
depicts an exemplary representation of entities that can make up
ecosystem of the application with respect to device 155.
[0045] Each device in system 150 can be associated with one or more
ecosystems. Device 155 is associated with ecosystem 160. Within a
MOX system, each device may be associated with different
ecosystems. Ecosystems may be particular to a particular device or
user. Ecosystem includes a plurality of spaces 165.sub.1-n.
According to one embodiment, each of spaces 165.sub.1-n may be
associated with device 155 by user selection, location of device
155 and/or by system 150. A user interface of device 150 may
display graphical elements associated with one or more of spaces
165.sub.1-n based on the location and/or operation of the device.
Spaces 165.sub.1-n may be real or virtual locations. By way of
example, spaces 165.sub.1-n may be assigned to one or more of a
room, building, floor, home, office or other physical location
(e.g., cafe, office, etc.). Spaces 165.sub.1-n may also be assigned
to virtual locations that do not have a corresponding physical
location. Each of spaces 165.sub.1-n may be associated with one or
more devices, such as device 155 for a user. Based the selection of
a space or location of device 155, the user interface may present
one or graphical elements for each space. In addition, device 155
may be configured to assign one or more cards with a space.
[0046] Card elements 156 are HTML objects, containing relevant
resources related to color pallet, and branding, as well as the
interactive components. Both the front and the back of the card are
supplied by the device itself, and are validated by the cloud.
[0047] Each of spaces 165.sub.1-n may include and/or be associated
with a plurality of entities 170, spaces 175, devices 180, and
cards 185. Entities 170 associated with a space, such as space
165.sub.1, can include MOX and non-MOX enabled devices, users, etc.
Spaces 175 associated with a space, such as space 165.sub.1, can
include one or more spaces associated based on location, card
selection, user preferences/selections, etc. Devices 180 associated
with a space, such as space 165.sub.1, can include MOX and non-MOX
enabled devices, devices based on location, device assigned to a
space etc. Cards 185 associated with a space, such as space
165.sub.1, can include one or more card elements associated by a
user to a space, such as cards 156 or cards that may be available
while within a space.
[0048] Ecosystem 190 may be another ecosystem that is not assigned
to device 155. Device 155 may be configured to join or gain access
to ecosystem 190 using a MOX application.
[0049] Conventional controls for third-party devices do not provide
the cross-functionality which is disclosed herein. Often,
conventional controls require individual configuration for each and
every device. Alternatively, the disclosure herein allows for the
control of multiple third-party devices from a single user
interface. The number and types of third-party devices are
potentially limitless. Each individual third-party device can be
controlled, regardless of its type or location, by the single user
interface on a single user device. The user interface can also be
configured such that third-party devices have pre-set settings. The
user interface disclosed can allow for improved connectivity
between third-party devices and control of said devices. The user
interface disclosed can also eliminate individual control units
associated with third-party devices as being completely
unnecessary. Improved connectivity, configuration, and control are
just some of the improvements disclosed herein.
[0050] FIGS. 2A-2B depict graphical representations of the method
of using a settings card. FIG. 2A depicts process 200 for the use
of a settings card according to one or more embodiments. Process
200 may be performed by a device such as device 105 of FIG. 1A.
Process 200 is illustrated from the perspective of the device 105.
Process 200 may be configured to present a user interface at block
205. The user interface presented at block 205 may be associated
with a MOX application. The user interface may be presented at
block 205 including graphical elements for one or more card
elements, and graphical elements for one or more spaces. In one
embodiment, the user interface includes graphical elements for one
or more spaces in one portion of the user interface and the
graphical elements for one or more card elements in a second
portion of the user interface. For example, the spaces may be icons
or graphical elements presented in a top portion of the user
interface. Each card element includes graphical display elements in
the user interface configured to be manipulated within the user
interface to allow for at least one of exchange of data,
capabilities, and device control.
[0051] At block 210, a graphical element for a settings card is
displayed by the user device. The settings card displayed is
selected, by the user, from any one of a plurality of settings
cards as shown on the user interface.
[0052] At block 215, a control input for the settings card is
detected by the user device. The control input is specifically
associated with the settings card, such that each of the plurality
of settings cards has a distinct set of control inputs.
[0053] At block 220, a control command is output from the user
device. The control command is sent to a device. The control
command relates to the control input for a settings card,
previously detected at block 215. The control command is configured
to control the operation of one or more devices (e.g., MOX
devices).
[0054] FIG. 2B depicts process 250 for the use of a settings card
according to one or more embodiments. Process 250 may be performed
by a device such as device 105 of FIG. 1A. Process 250 is
illustrated from the perspective of an application (e.g., a MOX
application). In an alternate embodiment, the settings card itself
is a micro-application, running within the MOX application
itself.
[0055] At block 255, the application associated with a user device
receives a control input. The control input is specifically
associated with a settings card, such that each of the plurality of
settings cards has a distinct set of control inputs.
[0056] At block 260, the application associated with a user device
determines the control input's relationship to a device. Each
control input is specifically associated with a settings card, and
each settings card is specifically associated with at least one of
a plurality of devices. This being the case, the application
determines how the individual control input relates to the
device.
[0057] At block 265, the application associated with a user device
outputs a control command to the device. The control command output
process is sent over a communication link between the application,
run on the user device, and the device. The communication link can
be through a local network or a more global network, such as the
Internet.
[0058] FIG. 3 depicts a graphical representation of a user
interface according to one or more embodiments. The user interface
is displayed on a user device 305. The user device 305 can be a
cellular phone, an electronic tablet, an e-reader, a laptop
computer, or any other device with control capabilities and a
connection to a communication network. The user interface is
presented including graphical elements for one or more card
elements including graphical elements for one or more spaces. User
interface features allow for one or more of viewing of cards
associated with the user device, viewing other devices and cards
associated with other entities (e.g., other devices, spaces), and
exchange of cards between the user device. Exchange may be based on
one or more of push/fling, pull and exchange of cards. The user
interface also allows for contextual presentation of cards.
[0059] In one embodiment, the user interface may provide card
Interaction by way of an Exchange View. A MOX application may
provide processes and device for exchange of a card via a user
interface (MOX). User interface features and processes for showing
cards include a detailed view and summary view when selected,
capability matching, communication of device features, devices
indicating that services and capabilities are available, and
associating content with any device so that content appears to
reside on the device.
[0060] In one embodiment, MOX may provide card interaction
including a push operation. The push operation may include one or
more of a fling gesture of card, a profile card, settings card,
cards in general, etc., hanging a card, capabilities (network
access, temporary control of a device, guest features, etc.)
capability matching, appearance of card transition.
[0061] In one embodiment, MOX may provide card interaction
including a pull operation. The pull operation may include one or
more of pulling a device card, borrowing capabilities, capability
matching, pulling settings vs. pulling an app., pulling a card off
of a device, appearance of card transition.
[0062] In one embodiment, MOX may provide card interaction
including Assigning/associating cards to devices (virtual or
connected). The operation may include one or more of a device that
is connected or not is presented in the MOX UI and connection to
the device (whether virtual or actual) based on card, processes for
identification based on scanning, and searching for non-connected
and connected devices, associating devices (connected or not with
spaces), and creating a virtual equivalent.
[0063] In one embodiment, MOX may provide card interaction
including assigning cards to spaces or card hanging. The operation
may include one or more of processes and device where a card may be
assigned to a space, including acts for flinging, pushing or
hanging card to a space, presentation of the card on other devices,
presenting cards based on a space that a device is in, card
presentation based on geolocation.
[0064] One embodiment is directed to detection of user input/touch
command of a graphical element and movement from one section of the
display to another section where the graphical element is a card
element. The MOX application processes movement of cards (exchange,
interact, control, etc.). The application allows for description of
card presentation, description of cards and entities (e.g.,
devices, virtual devices) in user interface, transition of card
and/or entities with respect to user actions or spaces, display of
cards based on capability matching, selection of which cards to
display, user and device avatars, design summary view and detailed
view of card, and card comments.
[0065] User interface features allow the MOX application to provide
functions including hanging cards on devices, controlling devices
using cards, borrowing services (e.g., Wi-Fi) using cards,
capability sharing (e.g., sharing control of a device), and one or
more features built around sharing cards.
[0066] The user interface of the user device 305 has a number of
individual features, such as a user row 333 and a device row 331.
The user interface also presents a device list 325. The device list
includes a listing of a plurality of third-party devices 310.sub.1,
310.sub.2, 310.sub.n, 330, 320.sub.1, 320.sub.2, and 320.sub.n. In
this embodiment, there is no limit to the number of devices listed
in the device list 325. Some of the devices, 310.sub.1, 310.sub.2,
310.sub.n, are connected directly with the user device 305. Some of
the devices, 320.sub.1, 320.sub.2, and 320.sub.n, are connected to
the user device 305 by a communication network. The communication
network can be a local network or a more global network, such as
the Internet.
[0067] The user interface of the user device 305 also presents a
plurality of user card elements 334 which are stored on the user
row 333. These user card elements 334 are associated with the user
device 305. Likewise, the user interface of the user device 305
presents a plurality of device card elements 332 which are stored
on the device row 331. These device card elements 332 are
associated with a selected third-party device 330. The selected
third-party device is one of the plurality of third-party devices
which are listed on the device list 325. The user has the ability
to select any third-party device, 310.sub.1, 310.sub.2, 310.sub.n,
330, 320.sub.1, 320.sub.2, and 320.sub.n, and upon selection, the
user's choice will become the selected third-party device 330. Once
the user has made a choice for the selected third-party device 330,
the device row 331 will automatically update such that the device
row 331 displays the plurality of device card elements 332
associated with the selected third-party device 330.
[0068] FIG. 4A depicts card interaction within the user interface
for the user. The user interface is displayed on the user device
405. The user interface presents a user row 433 and a device row
431. The user interface also presents a device list 425. The device
list includes a listing of a plurality of third-party devices
410.sub.1, 410.sub.2, 410.sub.n, 430, 420.sub.1, 420.sub.2, and
420.sub.n. In this embodiment, there is no limit to the number of
devices listed in the device list 425. Some of the devices,
410.sub.1, 410.sub.2, 410.sub.n, are connected directly with the
user device 405. Some of the devices, 420.sub.1, 420.sub.2, and
420.sub.n, are connected to the user device 405 by a communication
network. The communication network can be a local network or a more
global network, such as the Internet.
[0069] The user has the ability to select any third-party device,
410.sub.1, 410.sub.2, 410.sub.n, 430, 420.sub.1, 420.sub.2, and
420.sub.n, and upon selection, the user's choice will become the
selected third-party device 430. Once the user has made a choice
for the selected third-party device 430, the device row 431 will
automatically update such that the device row 431 displays the
plurality of device card elements associated with the selected
third-party device 430. One of these device card elements in the
device row 431 is the settings card 435. The settings card is a
device card element that specifically controls the functional
settings of the selected third-party device 430 which is associated
with the settings card 435.
[0070] The user device 405 allows for the user to send the settings
card 435 from the device row 431 to the user row 433. The user does
this through a tactile motion. The tactile motion can be one
continuous swipe, flick, fling, or similar gesture. Alternatively,
the tactile motion can be a plurality of tapping motions.
[0071] Once the settings card 435 has been sent to the user row 433
of the user device 405, the user can access the settings card 435.
The user has the ability to control the settings of the selected
third-party device 430 through the settings card 435.
[0072] In an embodiment, when the settings card 435 is selected by
the user, the settings card 435 becomes overlayed on top of the
user interface. The settings card can be overlayed on top of device
card elements in the device row 431 and on top of user card
elements in the user row 433. When overlayed on top of the user
interface, the settings card 435 is shown to the user in an
enlarged or a magnified view, such that the user can easily read
the contents of the settings card 435.
[0073] FIG. 4B depicts card interaction within the user interface
for the user, according to a different embodiment. The user
interface is displayed on the user device 455. The user device 455
allows for the user to select a settings card 485. The user does
this through a tactile motion. The tactile motion can be one
continuous swipe, flick, fling, or similar gesture. Alternatively,
the tactile motion can be a plurality of tapping motions. When the
settings card 485 is selected by the user, the settings card 485
populates the entire user interface of the user device 455. The
settings card 485 is shown to the user in an enlarged or a
magnified view, by populating the entire user interface of the user
device 455, such that the user can easily read the contents of the
settings card 485.
[0074] Once the settings card 485 has been selected by the user,
the user can access the settings card 485. The user has the ability
to control the settings of the selected third-party device through
the settings card 485.
[0075] FIG. 5 depicts a settings card on the user interface, being
used to control a device. The settings card can be used to control
any number of devices, including devices associated with the
Internet of things. This could include home automation devices,
heating and cooling systems, lighting systems, media devices,
personal electronics, appliances, office devices, meeting room
devices, audio-visual devices, and public location devices.
[0076] In an embodiment shown, the user has already chosen a
selected third-party device 530 on the user device 505.
Furthermore, the user has already moved the settings card 535
associated with the selected third-party device 530 into the user
row. Therefore, the user has access to the settings card 535
through the user interface of the user device 505.
[0077] In one embodiment, the selected third-party device 530 is a
display device 510. The user is accessing the settings card 535
associated with the display device 510. Through this access, the
user can control the channel and volume on the display device 510
directly from the user device 505. In this embodiment, the settings
card 535 also has limitations. Namely, that only certain
functionalities of the display device 510: channel and volume, can
be controlled by the user device 505.
[0078] In a different embodiment, the settings card 535 has access
limitations, such that only certain user devices can access the
settings card 535 and thus control the selected third-party device
530. As one example, a husband and wife could allow their personal
user devices to have access to their display device 510 through the
settings card 535 while simultaneously restricting all other user
devices, such as their neighbors' user devices, from accessing
their display device 510 through the settings card 535.
[0079] In a different embodiment, the settings card 535 has timing
limitations, such that a user device 505 can only access the
settings card 535 to control the selected third-party device 530
during certain days or certain times of the day. In another
different embodiment, the settings card 535 has proximity
limitations, such that a user device 505 can only access the
settings card 535 to control the selected third-party device 530
when the user device 505 is within a predefined geophysical
boundary.
[0080] In a different embodiment, the settings card 535 associated
with the selected third-party device 530 stores a favorite's
profile of pre-set, preferred, settings for the third-party device
530. In an embodiment, the settings card 535 initially shows the
user the display device's 510 preferred settings: the channel set
at 23 and the volume set at 14. In a related embodiment, the
settings card 535 associated with the selected third-party device
530 stores a user profile, associated with the user device's 505
access to the third-party device 530, the user profile being a
record of the user's preferred settings.
[0081] While the embodiment shown in FIG. 5 relates to a selected
third-party device 530 on the user device 505, such that the user
has already moved the settings card 535 associated with the
selected third-party device 530 into the user row, there are
alternate ways to control a third-party device on the user device
505.
[0082] In an alternate embodiment, the user device 505 has a
settings card 535 pre-loaded onto the user device 505. The user
does not have to select a third-party device and subsequently move
the settings card for that third party device onto the user row.
Rather, the user device 505 has saved the settings card 535 for a
third-party device onto the user row. This being the case, the user
can access the settings card 535 for a third-party device
immediately, without having to select the third-party device from a
device list, move the settings card for a particular device from
the device row to the user row, and then access the settings card
535.
[0083] FIG. 6 depicts a settings card on the user interface, being
used to control a plurality of devices. In this embodiment, the
user has already chosen a selected third-party device 630 on the
user device 605. Furthermore, the user has already moved the
settings card 635 associated with the selected third-party device
630 into the user row. Therefore, the user has access to the
settings card 635 through the user interface of the user device
605.
[0084] In an embodiment, the selected third-party device 630 is a
linked network which is made up of a plurality of linked devices:
610.sub.1, 610.sub.2, and 610.sub.3, in separate locations. The
user is accessing the settings card 635 associated with the
plurality of linked devices 610.sub.1, 610.sub.2, and 610.sub.3.
Because multiple devices are associated with a single selected
third-party device 630, and thus a single settings card 635, the
multiple device can be controlled simultaneously, through a single
settings card 635 accessed by a single user device 605. Through
this access, the user can control all of the plurality of linked
devices 610.sub.1, 610.sub.2, and 610.sub.3 directly from the user
device 605. In this embodiment, the plurality of linked devices
610.sub.1, 610.sub.2, and 610.sub.3 associated with the settings
card 635 are not directly linked with the user device 605. Rather,
the user device 605 and the plurality of linked devices 610.sub.1,
610.sub.2, and 610.sub.3 are linked through a communication network
615. This communication network 615 can be a local network or a
more global network, such as the Internet.
[0085] FIG. 7 depicts a simplified diagram of a device according to
one or more embodiments. Device 700 may relate to one or more
devices for providing an application, such as a MOX application.
According to another embodiment, device 700 may relate to one or
more devices configured to run a MOX core. In one embodiment,
device 700 relates to a device including a display, such as a TV,
mobile device, or device having a display in general. According to
another embodiment, device 700 may be devices, such as a set-top
box, configured to output content to a display device. According to
another embodiment, device 700 may be devices without a display. As
shown in FIG. 7, device 700 includes controller 705, graphical user
interface 710, communications unit 715 and memory 720.
[0086] Controller 705 may be configured to execute code stored in
memory 720 for operation of device 700 including presentation of a
graphical user interface. Controller 705 may include a processor
and/or one or more processing elements. In one embodiment
controller 705 may be include one or more of hardware, software,
firmware and/or processing components in general. According to one
embodiment, controller 705 may be configured to perform one or more
processes described herein. Graphical user interface 710 may be
configured to receive one or more commands via an input/output
(I/O) interface 725 which may include one or more inputs or
terminals to receive user commands. When device 700 relates to a
TV, I/O interface 725 may receive one or more remote control
commands.
[0087] Controller 705 may be configured to run a MOX application,
the MOX application including one or more card elements, restful
APIs, a MOX core and a MOX configuration.
[0088] Communications unit 715 may be configured for wired and/or
wireless communication with one or more network elements, such as
servers. Memory 720 may include non-transitory RAM and/or ROM
memory for storing executable instructions, operating instructions
and content for display.
[0089] In an alternate embodiment, the plurality of linked devices
could be home automation devices, heating and cooling systems,
lighting systems, media devices, personal electronics, appliances,
office devices, meeting room devices, audio-visual devices, and
public location devices.
[0090] It will be appreciated that all of the disclosed methods and
procedures described herein can be implemented using one or more
computer programs or components. These components may be provided
as a series of computer instructions on any conventional
computer-readable medium, including RAM, ROM, flash memory,
magnetic or optical disks, optical memory, or other storage media.
The instructions may be configured to be executed by a processor,
which when executing the series of computer instructions performs
or facilitates the performance of all or part of the disclosed
methods and procedures.
[0091] It should be understood that various changes and
modifications to the example embodiments described herein will be
apparent to those skilled in the art. Such changes and
modifications can be made without departing from the spirit and
scope of the present subject matter and without diminishing its
intended advantages. It is therefore intended that such changes and
modifications be covered by the appended claims.
[0092] While this disclosure has been particularly shown and
described with references to exemplary embodiments thereof, it will
be understood by those skilled in the art that various changes in
form and details may be made therein without departing from the
scope of the claimed embodiments.
* * * * *