SYSTEM AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO SPACES

FIELD

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 spaces.

BACKGROUND

Technologies associated with network devices, and in particular personal devices, are implemented in various forms and accessible from many sources. Services include mobile communication and 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. 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

Disclosed and claimed herein are systems, methods and devices for presentation of a user interface. One embodiment is directed to a method for assigning card elements of an application user interface to a space, the method includes presenting, by a 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 spaces. The method also includes detecting, by the device, 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 outputting, by the device, a communication 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.

In one embodiment, the user interface includes the graphical elements for the one or more spaces in one portion of the user interface and the graphical elements for the one or more card elements in a second portion of the user interface.

In one embodiment, 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.

In one embodiment, the user interface command includes selection and movement of a graphical element for the selected card from a first position in user interface to a second position associated with display of the selected space.

In one embodiment, the one or more spaces refer to physical locations.

In one embodiment, the one or more spaces include virtual locations.

In one embodiment, association of the card element includes transmission of card element metadata to the space.

In one embodiment, updating metadata includes storing a unique identifier of the space with the card element metadata.

In one embodiment, the method further includes determining that assignment of the selected card element to the selected space conforms to at least one of capabilities of the space and card element constraints.

In one embodiment, the user interface continues to display the selected card element in the user interface following assignment to the selected space.

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, 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 spaces. The controller is configured to 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 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.

Another embodiment is directed to a system including a server and a device configured to communicate with the server. The device is configured to present a user interface including graphical elements for one or more card elements, and the user interface is presented including graphical elements for one or more spaces. The device is configured to 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.

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

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:

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

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

FIGS. 2A-2B depict processes for assigning card elements of an application user interface to a space according to one or more embodiments;

FIG. 3 depicts a graphical representation of a user interface according to one or more embodiments;

FIG. 4A depicts a graphical representation of card interaction within a user interface according to one or more embodiments;

FIG. 4B depicts card interaction within the secondary user interface according to one or more embodiments;

FIG. 5 depicts card assignment to a particular space according to one or more embodiments;

FIG. 6 depicts a process for creating a card element according to one or more embodiments; and

FIG. 7 depicts a graphical representation of card configuration according to one or more embodiments.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS
Overview and Terminology

One aspect of the disclosure is to provide methods and devices for card interaction and assigning cards to spaces. In one embodiment, a mobile operating system/experience (MOX) application is provided for the method of card interaction and assigning cards. In another embodiment, a device is disclosed for facilitating card interaction and assigning cards. In another embodiment, a method is disclosed for creating the cards for use in the MOX application. Another embodiment is directed to hanging cards on an application entity. According to one embodiment, hanging a card on a device, or application entity, relates to an association of a card element with a particular application entity for a temporal or permanent association. Hanging a card on an entity, allows for other entities or users associated with the application to view and/or access the hanged card element.

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 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.

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 peer-to-peer 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.

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.

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 by way of an application (e.g., MOX application).

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., café, office, etc.). Spaces may also be assigned to virtual locations that do not have a corresponding physical location.

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.

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.

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.

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).

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.

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.

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.

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

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_1-n. According to another embodiment, device 105 may communicate and interoperate with one or more other devices, such as devices 120_1-nby way of a communication network 115.

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.

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.

According to one embodiment, devices 110₁, relate to one or more devices in close proximity to device 105. Device 105 may be configured to communicate wirelessly with the devices 110_1-nby way of the MOX application. Devices 110_1-nrelate to devices associated with a particular space and/or ecosystem. Accordingly, a user interface may identify and/or include graphical elements for devices 110_1-nand for card elements of devices 110_1-n. Devices 120_1-nrelate to devices which may be communicated with over communication network 115. Devices 120_1-nmay relate to devices in close proximity or distances from device 105. Devices 120_1-nmay relate to electronic devices. In some embodiments, devices 120_1-ninclude one or more servers.

Device 105 may run a MOX application, which may allow for detection of user input/touch commands for a graphical element. The MOX application may further allow for movement, of the graphical element, from one section of the display to another section of the display. The graphical elements associated with the MOX application may be card elements. The detection of user input/touch commands and movement (including exchanges, interactions, control, etc.) of graphical elements may be processed by the MOX application.

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.

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.).

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_1-nand devices 120_1-n.

Architectural aspects of the MOX application can include card configuration, platform for operating with mobile device OS, and underlying processes for card exchange functionality.

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.

System 100 may include a server, such as one of devices 120_1-nand 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.

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.

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_1-n. According to one embodiment, each of spaces 165_1-nmay be associated with device 155 by user selection, location of device 155 and/or by system 150. A user interface of device 155 may display graphical elements associated with one or more of spaces 165_1-nbased on the location and/or operation of the device. Spaces 165_1-nmay be real or virtual locations. By way of example, spaces 165_1-nmay be assigned to one or more of a room, building, floor, home, office or other physical location (e.g., café, office, etc.). Spaces 165_1-nmay also be assigned to virtual locations that do not have a corresponding physical location. Each of spaces 165_1-nmay 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 more graphical elements for each space. In addition, device 155 may be configured to assign one or more cards with a space.

Card elements 156 may be 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. In a preferred embodiment, the front and back of the card, as well as all relevant resources such as color pallet, branding, and interactive components, are validated by the cloud.

Each of spaces 165_1-nmay 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₁, can include MOX and non-MOX enabled devices, users, etc. Spaces 175 associated with a space, such as space 165₁, 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₁, 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₁, 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. According to one embodiment, device 155 may be configured to detect an input command to a user interface for the application and assign a card to at least one space, such as spaces 165_1-n, and/or one or more devices, such as devices 180.

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.

FIGS. 2A-2B depict processes for assigning card elements of an application user interface to a space according to one or more embodiments. FIG. 2A depicts process 200 for presentation of a user interface according to one or more embodiments. Process 200 may be employed to for assigning card elements of an application user interface to a space. 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, 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.

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 space presented by the user interface. In certain embodiments, the user interface command includes selection and movement of a graphical element for the selected card from a first position in user interface to a second position associated with display of the selected space. The selected space may refer to physical or virtual locations.

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 space. Based on the association of the selected card with the selected space, metadata for the card element may be updated. Association may include transmission of card element metadata to the space. In one embodiment, updating metadata includes storing a unique identifier of the space with the card element metadata.

In one embodiment, assignment of the selected card element to the selected space may be based on a determination that the card element can be assigned to the space. For example, the application can determine whether the assignment conforms to at least one of capabilities of the space and card element constraints. The card application may determine that a card element cannot be assigned to a space 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 space. According to one embodiment, outputting a communication at block 215 includes hanging a card to a space by the application.

FIG. 2B depicts a process for operation of a device (e.g., device 105) according to one or more embodiments. Process 250 may be configured to run an application (e.g., a MOX application) to determine card elements for display at block 255. At block 260, the application presents a user interface with graphical card elements associated with a MOX application. At block 265, the application can detect assignment of a card to a space. Process 250 may continue with associate the card with the space at block 270. Process 250 may optionally include determining the capability matching of the card element and the space at block 270.

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.

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.

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.

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.

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.

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, and card presentation based on geolocation.

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.

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.

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 an entity list 325. The entity list 325 includes a listing of a plurality of devices or spaces, shown as 310₁, 310₂, 310_n, 330, 320₁, 320₂, and 320_n. In this embodiment, there is no limit to the number of entities in the entity list 325. Some of the entities 310₁, 310₂, 310_n, are connected directly with the user device 305. Some of the entities 320₁, 320₂, and 320_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.

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₁, 310₂, 310_n, 330, 320₁, 320₂, and 320_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.

FIG. 4A depicts a graphical representation of card interaction within a user interface according to one or more embodiments. The user interface is displayed on the user device 405A. The user interface presents a user row 433A and a device row 431A. The user interface also presents an entity list 425A. The entity list 425A includes a listing of a plurality of devices/spaces 410₁A, 410₂A, 410_nA, 430A, 420₁A, 420₂A, and 420_nA. In this embodiment, there is no limit to the number of entities in the entity list 425A. Some of the entities 410₁A, 410₂A, 410_nA, are connected directly with the user device 405A. Some of the entities 420₁A, 420₂A, and 420_nA, are connected to the user device 405A by a communication network. The communication network can be a local network or a more global network, such as the Internet.

The user has the ability to select any entity 410₁A, 410₂A, 410_nA, 430A, 420₁A, 420₂A, and 420_nA, and upon selection, the user's choice will become the selected entity 430A. Once the user has made a choice for the entity 430A, the device row 431A will automatically update such that the device row 431A displays the plurality of card elements associated with the selected entity 430A.

The user device 405A allows for the user to send a selected card element 435A from the user row 433A to the entity 431A. The user does this through a tactile motion 436A. The tactile motion 436A can be one continuous swipe, flick, fling, or similar gesture. Alternatively, the tactile motion 436A can be a plurality of tapping motions.

According to one embodiment, tactile motion 436A relates to assignment of a card from user row 433A to device row 431A which may be associated with a particular space. Accordingly, the application can detect user interaction within a user interface presented by device 405A to assign a card to a space and/or hang a card to a space.

FIG. 4B depicts card interaction within the secondary user interface according to one or more embodiments. The secondary user interface is displayed on the secondary user device 405B. The secondary user interface presents a user row 433B and a device row 431B. The secondary user interface also presents an entity list 425B. The entity list 425B includes a listing of a plurality of entities 410₁B, 410₂B, 410_nB, 430B, 420₁B, 420₂B, and 420_nB. In this embodiment, there is no limit to the number of entities listed in the entity list 425B. Some of the entities 410₁B, 410₂B, 410_nB, are connected directly with the secondary user device 405B. Some of the entities 420₁B, 420₂B, and 420_nB, are connected to the secondary user device 405B by a communication network. The communication network can be a local network or a more global network, such as the Internet.

The secondary user has the ability to select any entity 410₁B, 410₂B, 410_nB, 430B, 420₁B, 420₂B, and 420_nB, and upon selection, the secondary user's choice will become the selected third-party device 430B. Once the user has made a choice for the selected third-party device 430B, the device row 431B will automatically update such that the device row 431B displays the plurality of device card elements associated with the selected third-party device 430B.

The secondary user device 405B allows for the secondary user to receive a selected card element 435B from the device row 431B to the user row 433B. The user does this through a tactile motion 436B. The tactile motion 436B can be one continuous swipe, flick, fling, or similar gesture. Alternatively, the tactile motion 436B can be a plurality of tapping motions.

Referring to FIGS. 4A and 4B, and as previously discussed, a user on a user device 405A can send a selected card element 435A from the user row 433A to the device row 431A. The device row 431A displays the device card elements associated with the selected third-party device 430A. By sending the selected card element 435A to the device row 431A, the selected card element 435A becomes associated with the selected third-party device 430A. When a secondary user on a secondary user device 405B chooses a selected third-party device 430B from the entity list 425B, that secondary user is able to see all the device card elements associated with the selected third-party device 430A. These device card elements are displayed on the device row 431B of the secondary user device 405B.

Therefore, if a user has sent a selected card element 435A to the device row 431A of a selected third-party device 430A, and the secondary user has selected the same third-party device 430B, such that 430A and 430B are the same third-party device, the secondary user is able to send the selected card element 435B from the device row 431B to the user row 433B, (where 435A and 435B are the same selected card element), such that the secondary user is able to view the selected card element 435A/435B on the user row 433B of the secondary user device 405B.

FIG. 5 depicts card assignment to a particular space according to one or more embodiments. The user interface is displayed on a user device 505. The user interface has a selected third-party device 530. There are also a plurality of other third-party devices 510₁, 510₂, 510_n, 520₁, 520₂, and 520_n. In this embodiment, there is no limit to the number of devices that can be connected with the user device 505. Some of the devices, 510₁, 510₂, 510_n, can be connected directly with the user device 505. Some of the devices, 520₁, 520₂, and 520_n, can be connected to the user device 505 by a communication network 515. The communication network can be a local network or a more global network, such as the Internet.

In an embodiment, the selected third-party device 530 is a location 530a. The location 530a selected by the user device 505 can be a virtual space. Alternatively, the location 530a selected by the user device 505 can be a physical location. In one embodiment, the location 530a selected by the user device 505 is Times Square, New York City.

In an embodiment, the user device 505 and subsequent entity list, from which the selected third-party device 530 can be chosen, is continually updated based on the geophysical location of the user device 505. In this embodiment, it is possible that a user would not be able to select the location 530a of Times Square if the user device 505 is not within the geophysical boundaries of Times Square. Likewise, the third-party devices 510₁, 510₂, 510_n, 520₁, 520₂, and 520_n, which may also have the ability to select a third-party device 530 as a location 530a would not be permitted to select the location 530a unless the third-party devices 510₁, 510₂, 510_n, 520₁, 520₂, and 520_n, were within the geophysical boundaries of the location 530a.

The device row associated with the selected third-party device 530 of a location 530a can also dynamically update, based on the user device's 505 geophysical location with respect to the location 530a boundaries. In an embodiment, any user card elements added to the device row of a selected third-party device 530 associated with a location 530a will be deleted when the user device 505 leaves the boundaries of the location 530a. In another embodiment, any user card elements added to the device row of a selected third-party device 530 will remain on the device row indefinitely, regardless of the user device's 505 position within the boundaries of the location 530a. In another embodiment, user card elements added to the device row of a selected third-party device 530 can be deleted after a certain period of time has lapsed.

FIG. 6 depicts a process for creating a card element according to one or more embodiments. Process 600 can create card element 637. Once the card element 637 is created, it is displayed on the user interface of the user device 605. A JSON metadata profile 610 is created. The JSON metadata profile 610 including information such as device profile, device uid, device class, device manufacturer, device model, device default name, device friendly name, zone uid, capabilities url, and mox version. A chrome 620 is created. The chrome 620 is the visual depiction of the card element 637 including color, style, layout, and theme. A unique identifier 630 is created. The unique identifier 630 being used so that every card element created is distinct. A transaction log 640 is created. The transaction log 640 being used to record all movements of a selected card between a user device 605 and any plurality of third-party devices. A user input 650 is created. The user input 650 includes any information that is added to the card element by the user device 605. The user input 650 can include passive information or dynamic functional commands. The user input 650 can also include any information that is modified by the user device 605. All of these created parameters: the JSON metadata profile 610, the chrome 620, the unique identifier 630, the transaction log 640, and the user input 650, are then stored on the card element 637.

In one embodiment, the card element 637 can only be modified when it is created, such that once the card element 637 is created, no user device 605 can modify the card element 637.

In another embodiment, the card element 637 can be modified by a user device 605 or any third-party device, such that any of the devices can add text comments to the card element 637. These text comments are stored on the card element 637 and are viewable by either the user device 605 or any of the plurality of third-party devices.

FIG. 7 depicts a graphical representation of card configuration according to one or more embodiments. Card element 700 may be a MOX card element. 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. Card element 700 may include several layers to allow for the card element to function and be used within an application where layers of the card have a different function. FIG. 7 depicts an exemplary representation of card element 700 as may be displayed. By way of example card element 700 may be displayed as graphical element 705 which includes image 710 and description 715. Image 710 may be specified by a user of the application or generated by the application. Image 710 may be employed to identify the card element. Description 715 may be user specified or similarly defined by the application. Description 715 may provide a name, type, and/or brief description of the card element 700 in text.

Presentation of card element 700 as graphical element 705 may employ interface layer 720 to define the graphical elements (e.g., image 710, description 715, etc.). Interface layer 720 may provide the user interface graphical elements that enables presentation but also reduce the amount of data to be processed (as opposed to the entire card) in order to present graphical elements for display of card element 700. HTML layer 725 can provide one or more web-based protocols or formatting. JavaScript layer 730 can include web-based elements can include but are not limited to CSS, JavaScript, and HTML5. Metadata layer 735 (e.g., JSON) can relate to metadata associated with the card that may define the card type, card content, card functionality, etc. According to one embodiment one or more layers of card element 700 may be pre-loaded for interoperation with a user interface of an application. It should be appreciated that card element 700 may include one or more additional or different layers.

According to one embodiment, presentation of card element 700 can introduce color into modular layout. Layout of the card element 700 may also be configured with a color pattern associated with cultural perspectives. According to another embodiment, the outer border of card element 700 may be presented to visually differentiate offerings and/or allude to potential movement of card element 700. Border edges of card element 700 can also manage the amount of information presented and include a contextual menu within the card footprint.

Card element 700 may be presented as a summary view and/or a detailed view. The summary view can include content associated with pre-loading of a protocol stack and interface layer 720. Summary view can include a brief description of content associated with the card element 700. In another embodiment, preloaded protocol stack can be used for displaying content associated with card element 700 for a detailed view within the application. A detailed view of card element 700, for example, can include a discussion of a card type, such as a web card, which is not displayed in the summary view. However, access to the detailed view of the card element may result in display of the discussion in at least a portion of the display of the card element as a detailed view. Web card functions may include one or more of generating a web card, embedding a web card from broadcasts to a MOX display, and commenting features.

According to one embodiment, card element 700 may be imported to an application. By way of example, elements displayed or presented in a native application can include MOX as a selection from a drop down menu so that elements/documents can be added to MOX. Following the selection, a template is selected, information is received regarding a description of the card element, privacy, tag, expiration, location (map) and comments and representative photo for creation of the card element 700 in one exemplary embodiment.

According to one embodiment, card element 700 may be configured as a card container configured to retain the metadata associated with a card. By way of example, card element 700 may contain the UUID values needed to track owner, creator, sender, instance, and card master. This metadata is associated with the card and validated by the cloud publishing services.

Card element 700 may be configured in a plurality of configurations to provide a plurality of card types. In addition to the card types discussed herein, card element 700 may be a combination of one or more card types discussed herein. Alternatively, and/or in combination, a card may be presented as a fusion of two cards together. By way of example, the fusion may relate to presentation of card element 700 with a portion of the display features relating to a first card, and a portion of the display features relating to a second card.

In one embodiment, card element 700 may be configured as a shortcut card configured to launch an application that is external to MOX application. By way of example, the MOX application may be ran on a device which presents a MOX user interface. The device executing the MOX application may include a native application (e.g., operating system, platform, etc.). Selection of a shortcut card element from the MOX user interface can prompt/initiate execution or startup of an application resident on the device or to be executed by the native application. In that fashion, the MOX application can interoperate, and/or at least initiate other programs from the MOX user interface.

In one embodiment, card element 700 may be configured as a content card. A content card may represent a document or file in the version of a card. As such, selection of the content card may launch presentation of the document. A content card can present a preview of the content with the card display format as well as include the entire data (e.g., PDF's, image, contacts, etc.). One type of content card may be an image card for image files, wherein the summary view provides a preview of one or more image files. When the content card relates to a file type, for example, a spreadsheet file, the presentation of the card element in the summary view may include an image of the particular file itself or a representation of the file type. One type of content card may be a web card. A web card can be created with an item of interest, such as an interest card, and can include image data in the summary view, and a brief description of the item. In a detailed view, the web card can include content (e.g., image of a webpage, etc.) and additional information associated with the item of interest. As an interest card, the web card can be viewed and account for the number of times viewed, shared, etc. The MOX can track number of check-ins, last time a card was viewed, and provide metrics for card access in the display of the card element, such as a detailed view.

In one embodiment, card element 700 may be configured as an interactive card to provide functionality with purpose built light interactions. By way of example, a list card may be an interactive card. The list card may be a listing of items (e.g., shopping, to-do list, checklist, etc.) which may be incorporated into a card element. The shopping list card can include a graphic list in the summary view and an intractable list in the detailed view. The list card function may include one or more of processes, systems and devices for providing, hanging and updating a list card. The list format is retained across devices and more than just text can be shared.

A widget card can provide a unique functionality that is purpose built for more intensive features such as control of a device (e.g., thermostat, TV, media player, etc.) with interactive controls based on or tailored to the particular device for control. By way of example, card element 700 may be a settings card including settings for a particular device that can be controlled using the user interface to control a device. The settings card may be associated with capabilities of a device. For example, a card may be associated with picture settings for a TV, media downloaded for the TV, a remote control for the TV, etc. The settings card operation may include one or more of processes, systems and devices for using a settings card. Settings cards may be applied to a display device, internet of things (IoT) devices, and may be profiled based on preferences.

In another embodiment, card element 700 may be a now playing card, associated with media, music or video including the name of the media playing and additional information to be displayed with a card. The now playing card may be presented during playback of media and may be removed from the display once playback has stopped. In another embodiment, card element 700 may be configured as a door bell card that allows for selection of the card to alert another user of MOX that is associated with the card.

In one embodiment, card element 700 may be configured as a gaming card. Gamification of card elements, such as a “you're it” card, card can be sent to “tag” a user. The tag functionally may display to a user in the user interface that they have been tagged and include a message from the sender. Gamification can include a point system based on access to the MOX application wherein points are collected and tallied by the MOX application based on usage. The points may be used for purchases, such as other cards, and/or for rewards. In one embodiment, MOX may provide a social feed card. The operation may include one or more of processes, systems and devices for presenting portions of a social media account within a MOX user interface.

In one embodiment, card element 700 may be configured as a challenge card. The challenge card can include a description of the challenge, and may include a timer. Based on access to the card, a user can accept the challenge to complete.

In one embodiment, card element 700 may be configured for payment and/or transactions. Card elements may be configured for payment, rewards clubs, banking, transit costs, etc. The payment card operation may include one or more of processes, systems and devices for providing payments via card and associating a card with payment, identity, etc.

In one embodiment, card element 700 may be a single use card. Single use cards may include one or more of processes, systems and devices for exchanging a singe use card. Single use cards may include formatting of card to provide a single use and use with card purchasing (e.g., gift cards, stationary, etc.).

In one embodiment, card element 700 may be configured to provide mirror control. The operation may include one or more of processes for providing mirror image of MOX interface onto another device, embedding a card from broadcasts to MOX display and interacting with a store.

In one embodiment, card element 700 may be configured as a novelty card. A novelty card may be an image card, such as a trading card. The novelty cards can be associated with sports paraphernalia. Novelty cards can be created for family members. Novelty card may be a sports card with an image and text associated with the individual or subject of the image. As such, card element 700 may used to encapsulate a picture, sports team, year, number and images or video. Novelty cards or other cards can be personalized with graphical elements or stickers associated with points of interest, such as organizations, professional sports teams, etc. The badge may be a card associated with connections to a particular item of interest.

In one embodiment, card element 700 may be configured as a warranty card. The warranty card may be created to provide warranty information for a device. The warranty card may be a particular format, such as pdf. A summary view of the warranty card can provide image of the product, a name, and card type. A detailed viewed can provide device particulars such as product model, size, capabilities, warranty terms, file information and comments.

In one embodiment, card element 700 may be video link card to provide notice of chat available. A video link card may be sent in MOX to allow or initiate connection, such as video feed or chat, between two or more devices.

In one embodiment, card element 700 may be personal tracker card for tracking locations of a user. The tracking card can include map displays to show locations of the user, places the user has visited, and the location of one or more other entities in MOX. Regarding goal tracking, such as health tracking, can be tied to a wearable device to track activity, calories burned, distance or other goals. The user interface can present a graphic, in either the card summary or detailed view, providing a display of progress toward a goal, the current level, the goal amount and performance metrics in general.

In one embodiment, card element 700 may be a greetings card. Card element 700 may relate to a one time use or single instance card which can be created or purchased as greetings cards (e.g., birthday, sympathy, congratulatory, etc.). Similarly, card element 700 may be a goodness card that includes a message than can be sent to deliver positive messages/goodwill. The goodness card may be tracked to see how may user open, send, received, etc. By tracking the goodness card, the user interface can present a map or graphic illustrating the reach of the goodness card. Card element 700 may be a birthday card, graphic message including name of recipient, etc. In certain embodiments, card element 700 may be associated with a greetings card pack, or collection of multiple card elements.

In one embodiment, card element 700 may be configured to provide connectivity to a device or network, such as WI-FI, home network access. The card can include credentials for access to the network in residential or public spaces.

In one embodiment, card element 700 may be contact card. The contact card can include an image for the contact, contact information, company name, etc. Card element 700 may be used as digital note passing including a user photograph and message, and a description of the note. As such, card element 700 can be used for chatting, sending a questions and conversations. Text messages of card element 700 can include a quotation, author of the quote, and source information associated with the note. In one embodiment, card element 700 may be schedule card including an image or text message for task to be completed and the due date for the task. Card element 700 may include location information including an address and map data associated with the location.

According to another embodiment, card element 700 may be a social card associated with one or more social media applications. The social card can relate to a micro-application for providing a social media account or accounts within the MOX user interface. In other embodiments, card element 700 can encapsulate a function or features of a social media account such as a message, image, status, etc.

In one embodiment, card element 700 may include advertisements incorporated into presentation of a card, such as a coupon or product placement.

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.

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

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.

SYSTEM AND METHODS FOR CARD INTERACTION AND ASSIGNING CARDS TO SPACES

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Provisional Applications (1)