System And Methods For Card Exchange And User Interface Presentation

Abstract

The present disclosure relates to systems, methods and devices for the presentation of a user interface and exchange of card elements. In one embodiment, a method for exchange of card elements includes presenting a user interface including a first area with graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application. The method also includes presenting one or more card elements in the second area based on an entity selected in the third area, detecting a command input for exchange of a selected card element relative to the first area and the second area, and updating presentation of the user interface based on exchange of selected card elements.

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 Aug. 19, 2015 and assigned patent application Ser. No. 14/829,886; SYSTEM AND METHODS FOR CARD ELEMENT APPLICATION OPERATION filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,893; SYSTEM AND METHODS FOR CONTROL OF CARD ELEMENTS WITHIN AN APPLICATION USER INTERFACE filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,914; SYSTEM AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO DEVICES filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,923; SYSTEM AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO SPACES filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,930; SYSTEMS AND METHODS FOR CONNECT TO CONTROL filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,942; SYSTEMS AND METHODS FOR DEVICE TO DEVICE CONTROL filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,955; SYSTEM AND METHODS FOR SETTINGS CARDS filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,970; and SYSTEM AND METHODS FOR PRESENTATION OF A USER INTERFACE AND CARD ELEMENTS filed on Aug. 19, 2015 and assigned patent application Ser. No. 14/829,986, the disclosures of which are expressly incorporated by reference.

FIELD

[0003] The present disclosure relates to electronic devices and applications, and more particularly to methods and devices configured for exchange and communication for card elements and devices.

BACKGROUND

[0004] Technologies associated with network devices, and in particular personal devices, are implemented in various forms and accessible from many sources. Services for mobile communication can allow for portability of devices. While conventional systems allow for mobility, there are limitations on devices and device configurations. With respect to local networks, system components are also limited in many ways. Many conventional devices are not interoperable with other devices or network services. Connectivity of devices, or the lack connectivity, in conventional systems can be a major drawback. Many user devices must be configured to interact with one another. In many cases, conventional communication protocols and configurations do not allow for connectivity.

BRIEF SUMMARY OF THE EMBODIMENTS

[0005] Disclosed and claimed herein are systems, methods and devices for device configuration to exchange card elements. One embodiment is directed to a method for exchange of card elements by an application user interface including presenting, by a device, a user interface including a first area associated with the device, the first area including graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application. The method also includes presenting, by the device, one or more card elements in the second area based on an entity selected in the third area, and detecting, by the device, a command input for exchange of a selected card element relative to the first area of the user interface and the second area of the user interface. The method also includes updating, by the device, presentation of the user interface based on the exchange of the selected card element

[0006] In one embodiment, the first area, the second area, and the third area are non-overlapping portions of a display area of the device configured to provide a scrollable display of graphical elements.

[0007] In one embodiment, the graphical elements for card elements displayed in the user interface are associated with a card presentation format of the application.

[0008] In one embodiment, presenting one or more card elements in the second area includes detecting selection of an entity in the third area and determining card elements for the entity selected in the third area based on a profile associated with the entity selected in the third area.

[0009] In one embodiment, presenting one or more card elements in the first area and second area includes presentation of one or more rows of card elements associated with a card element arrangement, wherein the card element arrangement is configured to be scrolled in one of a vertical and horizontal direction.

[0010] In one embodiment, presenting one or more card elements includes identifying profile information for a selected entity to identify one or more card elements and determining card compatibility of card elements with the device.

[0011] In one embodiment, the command input relates to one or more of a touch command, gesture, fling and move of a card element.

[0012] In one embodiment, updating presentation of the user interface includes displaying a graphical element for an exchanged card in an area of the user interface in a display area associated with a card move.

[0013] In one embodiment, the method further includes determining that compatibility of a selected card element to a selected device conforms to at least one of capabilities of the device and card element constraints.

[0014] In one embodiment, the method further includes presenting, by the device, a graphical indicator identifying an exchange direction relative to the first area and second area a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface.

[0015] Another embodiment is directed to a device including a display configured to present a user interface and a controller coupled to the display. The controller is configured to present a user interface including a first area associated with the device, the first area including graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application. The controller is also configured to present one or more card elements in the second area based on an entity selected in the third area, and detect a command input for exchange of a selected card element relative to the first area of the user interface and the second area of the user interface. The controller is also configured to update presentation of the user interface based on the exchange of the selected card element.

[0016] Other aspects, features, and techniques will be apparent to one skilled in the relevant art in view of the following detailed description of the embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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:

[0018] FIG. 1A depicts a graphical representation of a simplified system diagram according to one or more embodiments;

[0019] FIG. 1B depicts a graphical representation of system entities according to one or more embodiments;

[0020] FIG. 2 depicts a process for assigning card elements of an application user interface to a device according to one or more embodiments;

[0021] FIGS. 3A-3B depict a graphical representations of a user interface according to one or more embodiments;

[0022] FIGS. 4A-4D depict graphical representations of card exchange within a user interface according to one or more embodiments;

[0023] FIG. 5 depicts a process associated with exchanging card elements according to one or more embodiments; and

[0024] FIG. 6 depicts a simplified diagram of a device according to one or more embodiments.

DETAILED DESCRIPTION OF TILE EXEMPLARY EMBODIMENTS

Overview and Terminology

[0025] One aspect of the disclosure is to provide methods and devices for card interaction and exchange relative to devices. In one embodiment, a mobile operating system/experience (MOX) application is provided for presentation of an interface (e.g., user interface) configured for exchange of card elements. According to one embodiment, exchange of a card element can include one or more of sharing, lending, borrowing, and transmitting one or more card elements relative to entities of an application (e.g., MOX application). The user interface of an application (e.g., MOX application) can present one or more configurations for exchange of card elements.

[0026] On embodiment is directed to presentation and operation of a device associated with user interface presentation for exchange of card elements. The exchange presentation can include one or more display elements and one or more display regions. The arrangement and configuration of the display configuration can allow for graphic manipulation of display elements which can be detected and result in operation of an application and exchange of card elements.

[0027] One or more embodiments are directed to devices configured to present a display configuration associated with an application (e.g., MOX application) and allow for control and operation of the application. Based on detected input commands to the user interface the device may be configured to exchange one or more card elements.

[0028] As used herein, a card can relate to graphical elements displayed in a user interface, wherein each card element 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 and one or more types of capabilities. A card element may have a data structure associated with each card type, the 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 shared, 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.

[0029] 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.

[0030] 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 (e.g., 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.

[0031] 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. An ecosystem relates to collections of entities that are associated.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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).

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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

[0041] 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 and execution 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. System 100 may be configured to allow for control and communication by device 105 with one or more of devices 110.sub.1-n.

[0042] 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. The user interface may be configured to detect user commands of device 105 for assignment of cards to another device, such as devices 110.sub.1-n and/or 120.sub.1-n.

[0043] According to one embodiment, device 105 is configured to run an application (e.g., a MOX application) 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. The MOX application may run across multiple devices of system 100, including multiple device types and across multiple device operating platforms.

[0044] 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 via the user interface of the MOX application. 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.

[0045] Device 105 may run a MOX application that allows 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.). Movement of cards within the user interface call allow for assignment of a card to a device.

[0046] 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.

[0047] 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.).

[0048] 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.

[0049] Architectural aspects of the MOX application can include providing card configurations, providing a platform for operating with mobile device operating systems (OS), and underlying processes for card exchange functionality within the MOX application.

[0050] 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.

[0051] System 100 may include a server, wherein one or more of devices 120.sub.1-n may relate to servers. Device 105 may be configured to communicate with the server of system 100. 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.

[0052] 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. System 150 depicts an exemplary representation of entities that can make up ecosystem of the application with respect to device 155. Device 155 may relate to a representation of device 105 of FIG. 1A.

[0053] 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 to a device.

[0054] 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.

[0055] 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.4, 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.

[0056] 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.

[0057] FIG. 2 depicts a process for assigning card elements of an application user interface to a device according to one or more embodiments. FIG. 2 depicts process 200 for presentation of a user interface according to one or more embodiments. Process 200 may be employed for assigning card elements of an application user interface to a device or devices. Process 200 may be performed by a device such as device 105 of FIG. 1A. 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, graphical elements for one or more spaces, and graphical elements for one or more devices. In one embodiment, the user interface includes graphical elements for one or more devices 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 devices 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.

[0058] According to one embodiment, the user interface presented at block 205 is configured for exchange of card elements. The user interface presented at block 205 may include elements of the user interface depicted in FIGS. 3A-3B and 4A-4D.

[0059] At block 210, an interface command is detected. The detected interface command may be to associate a selected card element presented by the user interface with a selected device presented by the user interface. In certain embodiments, the user interface command includes selection (e.g., tap, tactile, other, etc.) and movement of a graphical element for the selected card from a first position (e.g., the displayed position) in user interface to a second position associated with display of the selected device. The selected device may refer to physical or virtual locations. Interface commands detect at block 210 may be associated with one or more areas or elements of an exchange view of the user interface including but not limited to elements or display areas depicted in FIGS. 3A-3B and 4A-4D.

[0060] At block 215, the application outputs a communication based on the detected interface command. According to one embodiment, outputting a communication includes the association of the selected card element with the selected device. Based on the association of the selected card with the selected device, metadata for the card element may be updated. Association may include transmission of card element metadata to the device. In one embodiment, updating metadata includes storing a unique identifier of the device with the card element metadata.

[0061] In one embodiment, assignment of the selected card element to the selected device may be based on a determination that the card element can be assigned to the device. For example, the application can determine whether the assignment conforms to at least one of capabilities of the device and card element constraints. The card application may determine that a card element cannot be assigned to a device and in response may display one or more elements to indicate that the assignment cannot be made. Following the output communication at block 215, user interface can continue to display the selected card element in the user interface following assignment to the selected device.

[0062] In one embodiment, process allows for exchange of data associated with the card to be provided to a device. The MOX application may be configured to allow for the data to be usable by one or other MOX devices. In this fashion, conventional methods of electronically sending that require end user addresses (e.g., email) are not required. Similarly, assignment does not require configuration, downloading, decompressing, other steps for the card to be useable once assigned. Rather, card assignment allows for the card element to appear within the user interface when the device to which the card is assigned is selected. In addition, one or more properties of the card element may be usable by the device to which the card is assigned.

[0063] FIGS. 3A-3B depict graphical representations of a user interface according to one or more embodiments. The user interface 300 may be displayed on a user device 305. The user device 305 can be a cellular phone, an electronic tablet, an c-reader, a laptop computer, or any other device with control capabilities and a connection to a communication network. The user interface 300 is presented including graphical elements for one or more card elements including graphical elements for one or more spaces. Features of user interface 300 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 and other devices. 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.

[0064] In one embodiment, user interface 300 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.

[0065] In one embodiment, MOX may provide card interact on 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.

[0066] 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 application, pulling a card off of a device, appearance of card transition.

[0067] 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.

[0068] In one embodiment, MOX may provide card interaction including Assigning cards to Space/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.

[0069] 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.

[0070] 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.

[0071] In FIG. 3A, user interface 300 of the user device 305 has a number of individual features, such as a user row 333 (e.g., first display area) and a device row 331. (e.g., second display area). The user interface also presents an entity list 325 (e.g., third display area). The entity list includes a listing of a plurality of devices or spaces, shown as 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 entities in the entity list 325. Some of the entities 310.sub.1, 310.sub.2, 310.sub.n, are connected directly with the user device 305. Some of the entities 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.

[0072] 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 entity 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.

[0073] According to one embodiment, user interface 300 is presented including graphical elements 334 for one or more card elements in a first portion (e.g., row 333) and graphical elements for one or more devices 310.sub.1-n and 320.sub.1-n. User inputs (e.g., contact, touch, selection, etc.) may be detected by device 305 as a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface 300. FIG. 3A depicts a selected card 336 in a first portion of the user interface. In certain embodiments, the user selection may be a tap, hold and drag to a second portion of the user interface, such as device row 331. The second portion of the user interface may also relate to a tap, hold, and drag to a device (e.g., one or more devices 310.sub.1-n and 320.sub.1-n). Following the assignment of the card to a device, user interface 300 may update the presentation format.

[0074] FIG. 3B depicts a selected card 336 in a portion of the user interface following card assignment to a device according to an exemplary embodiment. According to one embodiment, selected card element may be assigned to another device, and thus, the application will present a graphical element for the selected card element 336 in row 331. In certain embodiments, assignment of a card element to a device copies the card element to the device, such that a graphical element, such as 337, is still provided in row 333 of the user interface. In other embodiments, assignment of for the selected card element 336 will transfer the selected card element to the device for which graphical elements in row 331 are presented. In such a case, user interface will present graphical element 337 in row 333 which relates to a different card element from selected card element 336. Device 305 may output a communication including an association of the selected card element 336 with the selected device, wherein the association of the selected card with the selected device includes updating metadata for the card element.

[0075] FIGS. 4A-4D depict a graphical representation of card interactions within a user interface according to one or more embodiments. FIGS. 4A-4B depict a push command relative to an exchange presentation of a user interface for an application of device 405. The user interface is displayed on the user device 405. The user interface presents a user row 433 (e.g., first display area) and a device row 431 (e.g., second display area). The user interface also presents an entity list 425 (e.g., third display area). The entity list includes a listing of a plurality of devices/spaces 410.sub.1-n, 430, 420.sub.1-n. In this embodiment, there is no limit to the number of entities in the entity list 425. Some of the entities 410.sub.1-n, are connected directly with the user device 405. Some of the entities 420.sub.1-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.

[0076] The user has the ability to select any entity 410.sub.1, 410.sub.2, 410.sub.n, 430, and 420.sub.1-n, and upon selection, the user's choice will become the selected entity 430. Once the user has made a choice for the entity 430, the device row 431 will automatically update such that the device row 431 displays the plurality of card elements associated with the selected entity 430.

[0077] The user device 405 is configured to allow for a user to exchange a selected card element 435 from the user row 433 to the entity area 431. The user does this through a control command 436 detected by the user interface of user device 405. The control command 436 can be one continuous swipe, flick, fling, or similar gesture. In one embodiment, control command 436 relates to at least one of a touch, drag, fling and tactile command within the user interface. Alternatively, the control command 436 can be a plurality of tapping motions.

[0078] According to one embodiment, FIG. 4A depicts control command 436 as a push command. In one embodiment, user interface command 436 is push command to push the selected card 435 from the display area (user row 433) associated with the device 405 to a display area of the user interface associated with a second device (e.g., entity area 431). The push command can associate a new instance of card 435 with a second device or entity for a period of time. According to one embodiment, when control command 436 is detected by a controller of device 405, the user interface presented by device 405 can present graphical element 437. Graphical element 437 is a graphical indicator identifying an exchange direction relative to the first area and second area a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface. By way of example and relative to control command 436, graphical element 437 is presented indicating a direction from the display area (user row 433) associated with the device 405 to a display area of the user interface associated with a second device (e.g., entity area 431). In that fashion, an exchange configuration is provided by device 405. In one embodiment, graphical element 437 is presented during detection of control command 436. According to another embodiment, graphical element 437 may be presented when compatibility of a card element, such as card element 435 and selected entity 430 are compatible.

[0079] FIG. 4B depicts card element 435 moving from display area (user row 433) associated with the device 405 to a display area of the user interface associated with a second device (e.g., entity area 431). Once the card element is moved or detected as being in or substantially within a display area of the user interface associated with a second device (e.g., entity area 431), the user interface may display card element 435 as a copy and/or move of the card element in entity area 431. In addition the user interface application can associated the moved/exchanged card with the device and/or entity associated with entity area 431.

[0080] FIGS. 4C-4D depict a pull command relative to an exchange presentation of a user interface for an application of device 405. According to one embodiment, FIG. 4C depicts a control command as pull command for card element 450 in one embodiment, user interface command 455 is pull command to pull the selected card 450 from a display area of the user interface associated with a selected device/entity (e.g., entity area 431) to the display area (user row 433) associated with the device 405. The pull command can associate a new instance of card 450 for device 405 for a period of time.

[0081] Graphical element 456 is presented indicating a direction from a display area of the user interface associated with a second device (e.g., entity area 431) to the display area (user row 433) associated with the device 405. In that fashion, an exchange configuration is provided by device 405. In one embodiment, graphical element 456 is presented during detection of control command 455. According to another embodiment, graphical element 456 may be presented when compatibility of a card element, such as card element 450 and device 405 are compatible.

[0082] FIG. 4D depicts card element 450 moving from a display area of the user interface associated with a second device (e.g., entity area 431) to display area (user row 433) associated with the device 405. Once the card element is moved or detected as being in or substantially within a display area (user row 433) associated with the device 405, the user interface may display card element 450 as a copy and/or move of the card element in the display area user row 433. In addition the user interface application can associated the moved/exchanged card with the device and/or entity associated with entity area 431.

[0083] According to one embodiment, exchange of card elements, such as card element 435 or card element 450 allows for exchange or transmission of card elements relative to one or more entities of a MOX application. In that fashion, features of the MOX application can be leveraged to allow for greater connectivity and simplified exchange of via a user interface. Moreover, exchange within a MOX application can allow for exchange of card elements and/or card element content based on commands detected relative to display areas, such as user row 433 and entity area 431 without requiring the use of a traditional message (e.g., email, etc.), message addressing, and/or transmission of all content. Exchange as discussed herein may relate to exchanged based on card elements within an application configured to operate with card elements.

[0084] FIG. 5 depicts a process associated with exchanging card elements according to one or more embodiments. Process 500 may be performed by the one or more devices supporting the MOX application, such as a MOX application residing (e.g., executed by) one or more end user devices and one or more servers. Process 500 is associated with operations executed by a device and performed by an application, such as a MOX application, run by the device for displaying the user interface and interaction with one or more other devices. Determinations at block 505 and 510 may be performed by the device or a MOX application to pre-determine capabilities of devices, cards and user interface actions.

[0085] Process 500 may be initiated by presenting a user interface at block 505. Presentation of a user interface (e.g., user interface 300) can allow for navigation and/or browsing of card elements. In one embodiment, presentation of the user interface allows for exchange of card elements by an application user interface (e.g., MOX user interface). According to one embodiment, presentation at block 505 includes presenting a user interface including a first area associated with the device, the first area including graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application.

[0086] In one embodiment, the first area (e.g., user row 433), the second area (e.g., device row 431), and the third area (e.g., entity list 425) are non-overlapping portions of a display area of the device configured to provide a scrollable display of graphical elements. In one embodiment, presenting one or more card elements in the second area (e.g., device row 431) includes detecting selection of an entity in the third area (e.g., entity list 425) and determining card elements for the entity selected in the third area based on a profile associated with the entity selected in the third area. According to another embodiment, presenting one or more card elements in the first area (e.g., user row 433) and second area (e.g., device row 431) includes presentation of one or more rows of card elements associated with a card element arrangement, wherein the card element arrangement is configured to be scrolled in one of a vertical and horizontal direction. By way of example, one or more rows or cards may be displayed to allow for scrolling in vertical, horizontal or other modes to allow for presentation of card elements in fixed display sets or a sequence of revolving card elements. In that fashion, one or more card elements in the first area and second area are presented as one or more rows of card elements associated with a card element arrangement, wherein the card element arrangement is configured to be scrolled in one of a vertical and horizontal direction. At block 505, presenting card elements includes identifying profile information for a selected entity to identify one or more card elements and determining card compatibility of card elements with the device.

[0087] At block 505, graphical elements for card elements displayed in the user interface are associated with a card presentation format of the application. For example, each card element may be associated with a card chrome specifying at least one of a summary view, detailed view, card characteristics, etc.

[0088] According to one embodiment, the presentation of a user interface at block 505 is a display configuration/arrangement for exchange of card elements. In one embodiment, a device and application (e.g., MOX application) may allow for navigation and/or browsing of card elements based on the user interface presented at block 505. The application is configured to detect user inputs/operations of the interface and present card elements based on detected inputs and/or interactions with a user. In one embodiment, presenting a user interface at block 505 includes queuing display elements, such as card to allow for the user interface to quickly display entities, devices and card elements accessible to the device.

[0089] At block 510, process 500 includes detecting user interface inputs. In one embodiment, the user interface input at block 510 is a command input for exchange of a selected card element relative to the first area of the user interface and the second area of the user interface. In one embodiment, a command input at block 510 relates to one or more of a touch command, gesture, fling and move of a card element.

[0090] At block 515, the device can present card elements. Presentation at block 515 can also include one or more card elements in the second area based on an entity selected in the third area. Card elements presented at block 515 may be independent of and/or directly related to user interface inputs detected at block 510,

[0091] Process 500 may include analyzing user interface inputs and presented card elements to determine whether to exchange elements at decision block 520. When detected commands and card presentation does not require exchange (e.g., "NO" path out of decision block 520), process 500 can update the user interface presentation at block 525. Updating the user interface presentation can include scrolling and/or modification of card elements and/or entities in one or more display areas of the user interface.

[0092] In certain embodiments, process 500 includes determining an exchange at decision block 520 (e.g., "YES" path out of decision block 520) based on an interface command detected at block 510. By way of example, the interface command may be a fling from one area of the user interface to a second area of the user interface. In one embodiment, based on a determination to exchange an element, such as a card, process 500 exchanges a card element at block 540. Process 500 can then update the user interface presentation at block 525. Updating presentation of the user interface at block 525 includes displaying a graphical element for an exchanged card in an area of the user interface in a display area associated with a card move,

[0093] In certain embodiments, process 500 may optionally include displaying an exchange indicator at block 530 and determining capability at block 535 after determining an exchange at decision block 520 (e.g., "YES" path out of decision block 520). Displaying an exchange indicator at block 530 may include display of one or more elements in the user interface to indicate one or more of an exchange direction, compatibility or incompatibility. In one embodiment, the indicator identifies an exchange direction relative to the first area and second area a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface. FIGS. 4A-4D depict the indicator 436 as a triangular shaped graphical element which can overlay or transparently be displayed in a continuous and/or pulsed manner before, during and/or after a user interface input.

[0094] Determining compatibility at block 535 can include determining capabilities of a device that may be accessible or presented by a graphical element in the user interface. Determining compatibility at block 535 can include determining compatibility of a card element with a device or entity. According to one embodiment, cards may be exchanged between entities or devices based on a capability matching of the card and the selected entity or device. By way of example, the card type, or functionality, may allow for interoperation with one or more device functions. By way of further example, a device including display or media operations may be assigned a card associated with the display or media operations. In a similar fashion, a device configured for control (e.g., lighting, home automation, etc.) can be assigned a card directed to settings for the device, including display or media operations may be assigned a card associated with the display or media operations. The device capability may be based on a profile generated for the device within the MOX application. In certain embodiments, device profiles may be similar for similar types of devices. Determining compatibility at block 535 may include processing stored information for entities and/or devices accessible to the user interface. Alternatively, or in combination, determining device capability at block 535 may include requesting device capability via the MOX application.

[0095] Blocks 520 and 535 of process 500 may be performed simultaneously, concurrently, and/or independently. Process 500 includes updating, by the device, presentation of the user interface based on the exchange of the selected card element at block 525,

[0096] FIG. 6 depicts a simplified diagram of a device according to one or more embodiments. Device 600 may relate to one or more devices for providing an application, such as a MOX application. According to another embodiment, device 600 may relate to one or more devices configured to run a MOX core. In one embodiment, device 600 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 600 may be devices, such as a set-top box, configured to output content to a display device. According to another embodiment, device 600 may be devices without a display. As shown in FIG. 6, device 600 includes controller 605, graphical user interface 610, communications unit 615 and memory 620.

[0097] Controller 605 may be configured to execute code stored in memory 620 for operation of device 600 including presentation of a graphical user interface. Controller 605 may include a processor and/or one or more processing elements. In one embodiment controller 605 may he include one or more of hardware, software, firmware and/or processing components in general. According to one embodiment, controller 605 may be configured to perform one or more processes described herein. Graphical user interface 610 may be configured to receive one or more commands via an input/output (I/O) interface 625 which may include one or more inputs or terminals to receive user commands. When device 600 relates to a TV, I/O interface 625 may receive one or more remote control commands.

[0098] Controller 605 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. Controller 600 may be configured for exchange of card elements within an application user interface presented by device 600.

[0099] Communications unit 615 may be configured for wired and/or wireless communication with one or more network elements, such as servers. Memory 620 may include non-transitory RAM and/or ROM memory for storing executable instructions, operating instructions and content for display.

[0100] 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.

[0101] Although several features and embodiments are discussed relative to a MOX application, it should be appreciated that principles and teachings of the disclosure are not limited to MOX applications.

[0102] 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.

[0103] 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.

Claims

1. A method for exchange of card elements by an application user interface, the method comprising: presenting, by a device, a user interface including a first area associated with the device, the first area including graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application; presenting, by the device, one or more card elements in the second area based on an entity selected in the third area; detecting, by the device, a command input for exchange of a selected card element relative to the first area of the user interface and the second area of the user interface; and updating, by the device, presentation of the user interface based on the exchange of the selected card element.

2. The method of claim 1, wherein the first area, the second area, and the third area are non-overlapping portions of a display area of the device configured to provide a scrollable display of graphical elements.

3. The method of claim 1, wherein the graphical elements for card elements displayed in the user interface are associated with a card presentation format of the application.

4. The method of claim 1, wherein presenting one or more card elements in the second area includes detecting selection of an entity in the third area and determining card elements for the entity selected in the third area based on a profile associated with the entity selected in the third area.

5. The method of claim 1, wherein presenting one or more card elements in the first area and second area includes presentation of one or more rows of card elements associated with a card element arrangement, wherein the card element arrangement is configured to be scrolled in one of a vertical and horizontal direction.

6. The method of claim 1, wherein presenting one or more card elements includes identifying profile information for a selected entity to identify one or more card elements and determining card compatibility of card elements with the device.

7. The method of claim 1, wherein the command input relates to one or more of a touch command, gesture, fling and move of a card element.

8. The method of claim 1, wherein updating presentation of the user interface includes displaying a graphical element for an exchanged card in an area of the user interface in a display area associated with a card move.

9. The method of claim 1, further comprising determining that compatibility of a selected card element to a selected device conforms to at least one of capabilities of the device and card element constraints.

10. The method of claim 1, further comprising presenting, by the device, a graphical indicator identifying an exchange direction relative to the first area and second area a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface.

11. A device comprising: a display configured to present a user interface; and a controller coupled to the display wherein the controller is configured to present a user interface including a first area associated with the device, the first area including graphical elements for one or more card elements associated with the device, a second area to display graphical elements for one or more card elements associated with a selected entity device, and a third area including graphical elements for one or more entities accessible to the device by way of the application; present one or more card elements in the second area based on an entity selected in the third area; detect a command input for exchange of a selected card element relative to the first area of the user interface and the second area of the user interface; and update presentation of the user interface based on the exchange of the selected card element.

12. The device of claim 11, wherein the first area, the second area, and the third area are non-overlapping portions of a display area of the device configured to provide a scrollable display of graphical elements.

13. The device of claim 11, wherein the graphical elements for card elements displayed in the user interface are associated with a card presentation format of the application.

14. The device of claim 11, wherein presenting one or more card elements in the second area includes detecting selection of an entity in the third area and determining card elements for the entity selected in the third area based on a profile associated with the entity selected in the third area.

15. The device of claim 11, wherein presenting one or more card elements in the first area and second area includes presentation of one or more rows of card elements associated with a card element arrangement, wherein the card element arrangement is configured to be scrolled in one of a vertical and horizontal direction.

16. The device of claim 11, wherein presenting one or more card elements includes identifying profile information for a selected entity to identify one or more card elements and determining card compatibility of card elements with the device.

17. The device of claim 11, wherein the command input relates to one or more of a touch command, gesture, fling and move of a card element.

18. The device of claim 11, wherein updating presentation of the user interface includes displaying a graphical element for an exchanged card in an area of the user interface in a display area associated with a card move.

19. The device of claim 11, further comprising determining that compatibility of a selected card element to a selected device conforms to at least one of capabilities of the device and card element constraints.

20. The device of claim 11, further comprising presenting, by the device, a graphic indicator identifying an exchange direction relative to the first area and second area a user interface command to associate a selected card element presented by the user interface with a selected device presented by the user interface.