System, Method, and Apparatus for an Interactive Container

Abstract

An interactive container creation method, apparatus and system. The method includes creating a list, deploying the list to at least one device, calibrating and identifying touch areas, identifying at least one of an asset and a shape to be defined as a touch area, identifying the x,y axis of each point for a predetermined number of points for each of the at least one of asset or shape, and creating a touch area based of the identified x,y axis.

Description

FIELD OF THE INVENTION

The disclosure relates to systems, apparatus and methods for creating and operating interactive containers. More specifically, this disclosure relates to creating and operating interactive containers that relate to any assets that are projected, printed, displayed, etc.

BACKGROUND OF THE INVENTION

It has become more common from assets of different origin or type to communicate and cause an activity based on such interaction. For example, it has become common for users to utilize their portable devices to control various products in their home and/or office made by different manufacturers. The selection of the assets and its interaction can be customizable and variable. Therefore, it is desirable to be able to simulate such interactions and to be able to customize it. In addition, some assets may be susceptible to tampering. Thus, it is beneficial to display an interactive image, printout, etc. of such assets. Therefore, there is a need for an improved system, apparatus and method for creating and operating interactive container(s).

SUMMARY OF THE INVENTION

Embodiments described herein relate to an interactive container creation method, apparatus and system. The method includes creating a list, deploying the list to at least one device, calibrating and identifying touch areas, identifying at least one of an asset and a shape to be defined as a touch area, identifying the x,y axis of each point for a predetermined number of points for each of the at least one of asset or shape, and creating a touch area based of the identified x,y axis.

BRIEF DESCRIPTION OF DRAWINGS

Reference will now be made to the following drawings:

FIG. 1 is an embodiment illustrating a flow diagram of a method for creating at least one interactive container;

FIG. 2 is an embodiment illustrating a flow diagram of a method for calibrating at least one interactive container;

FIG. 3 is a block diagram illustrating an embodiment of an apparatus of interactive containers;

FIG.4 is a block diagram illustrating an embodiment of an interactive system relating to at least one interactive container;

FIG. 5 is an embodiment illustrating a flow diagram of a method for refining touch recognition; and

FIG. 6A-C are diagrams depicting an embodiment of an interactive container.

DETAILED DESCRIPTION

In the descriptions that follow, like parts are marked throughout the specification and drawings with the same numerals, respectively. The drawing figures are not necessarily drawn to scale and certain figures may be shown in exaggerated or generalized form in the interest of clarity and conciseness.

It will be appreciated by those skilled in the art that aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or context including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Therefore, aspects of the present disclosure may be implemented entirely in hardware or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system” (including firmware, resident software, micro-code, etc.). Further, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.

Any combination of one or more computer readable media may be utilized. The computer readable media may be a computer readable signal medium, any type of memory or a computer readable storage medium. For example, a computer readable storage medium may be, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include, but are not limited to: a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. Thus, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Computer program code for carrying out operations utilizing a processor for aspects of the present disclosure may be written in any combination of one or more programming languages, markup languages, style sheets and JavaScript libraries, including but not limited to Windows Presentation Foundation (WPF), HTML/CSS, XAML, and JQuery, C, Basic, *Ada, Python, C++, C#, Pascal, *Arduino. Additionally, operations can be carried out using any variety of compiler available.

Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, processor, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, processor, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

FIG. 1 is an embodiment illustrating a flow diagram of a method 100 for creating at least one interactive container. The method 100 starts at step 102 and proceeds to step 104. At step 102, the method 100 creates a list. The list may contain images, assets, attributes, WISPSs, rules, menus, etc. A WISP in this application relates to a shell that defines the rules and the interaction between the assets and/or containers. In an embodiment, the creation of the list is performed at a remote location or on a cloud. In other embodiments, the creation of the list is performed on the same device operating the interaction between the assets, menus, and/or containers. In such embodiments, the deployment step would not be necessary.

At step 106, the method 100 deploys at least one list to a device that is operating the interaction between the assets, menus, and/or containers. In one embodiment, the deployment may occur on several devices that may or may not be at the same location. The device(s) may be at the same location as the container being operated. In one embodiment, the axis location, i.e. x, y, x, location of the assets may be incorporated into the list at the list creation time or it may be determined on the device controlling the interaction, i.e., a device located at the same location as the container. The device controlling the interaction may learn the location of the assets, it may display the assets, or it may scan for characteristics to learn their location. In one embodiment, a list may already exist and only changes, omissions and/or additions are deployed, rather than the entire list. Furthermore, the deployment may be initiated/conducted manually or it may be automatic.

At step 108, the method 100 calibrates assets subjects in the container and/or identifies the touch areas. During the calibration process, the method 100 may perform projection mapping for every container to ensure that the display matches the physical space. In one embodiment, the method 100 uses image training during calibration to detect a known image, item, logo, etc.

In other embodiments, a person manually calibrates the system by shifting from point to point identifying the touch area and triggering a new touch area when the current touch area is done and another touch area exists and needs to be identified by the system. Whereas, during an automatic calibration, the system automatically identifies a predetermined number of points per touch area relating to assets and/or shapes. In another embodiment, a calibration stream is cropped to where only areas of interest are calibrated. Only calibrating areas of interest results in a more accurate and more efficient calibration. The calibration process is better described in FIG. 2. Method 100 ends at step 110.

FIG. 2 is an embodiment illustrating a flow diagram of a method 200 for calibrating at least one interactive container. Method 200 starts at step 202 and proceeds to step 204, wherein the method 202 detects an asset or shape displayed that needs to be defined as a touch area. At step 206, the method 200 identifies a predetermined number of points relating to the asset or shape where each point is defined by its x, y axis. At step 208, the method 200 determines if there are more assets or shapes to be identified as touch areas. If there are more assets or shapes to be identified as touch areas, the method 200 returns to step 204. Otherwise, the method 200 ends at step 210.

For example, a projector displays a pre-determined shape over a touch area not identified yet. Using a camera, the method identifies the x, y axis for each point in a pre-determined number of points relating to the asset or displayed shape. Once the axis is identified, the method 200 proceeds to the next asset or shape in the container. The method 200 may perform such function on a single container or multiple containers. The method 200 may utilize asset identification, display recognition, shape recognition, light, exposure, contrast, RGB difference, infrared, etc. to determine the areas that need to be identified as touch areas. When all touch areas are identified, the camera and/or method are capable of identifying the touch areas and identify the corresponding rule, menu, activity etc. relating to the touch area.

FIG. 3 is a block diagram illustrating an embodiment of an apparatus 300 of interactive containers. In this embodiment, the apparatus 300 has two containers 302A and 302B, where container 302 A has two menus/attributes 304A and 304B. Container 302B has a single menu/attributes 304C. Each of the menu/attribute's 304A, 304B and 304C has a WISP/Rules 306A, 306B and 306C, respectively. Each of the WISP/Rules 306A, 306B and 306C has assets 308A, 308B and 308C, respectively.

A single interactive apparatus 300 may include any number of containers that may or may not communicate and/or interact. As such, in one embodiment, interacting with one container may cause a change in another container. Containers create an interactive experience using the menus/attributes and WISP/rules relating to assets. The menu/attributes are options at an instance, which may be a default instance or options that come about due to an interaction or touch on or around a menu item or attribute presented. A container may contain any number of menus/attributes 306, which may interact or stand alone. Attributes may be audio, video, image, change in display, etc. WISP/rules are the interactive active mask over a touch area that triggers a menu or attribute due to a pre-determined activity. Assets may be pre-determined object or person, printouts of objects, displayed items, images, video, an identified object or person, and the like.

In one embodiment, a weighted average may be used. In such an embodiment, a new object/asset is added to a container. The weighted average method adds the object/asset incrementally over time where the accounting of the new item increases in percentile in relation to the whole picture over time. Such a method insures that the item is truly added, allows of real-time reaction to change in a container, and allows for a realistic change over time.

FIG. 4 is a block diagram illustrating an embodiment of an interactive system 400 relating to at least one interactive container. In this embodiment, the system 400 includes a processor 402, memory/storage medium 404, a calibrator 406, a touch detector 408, a touch listener 410, an analytics module 412 and an I/O 414. The memory 404 include deployed data 404A, touch area data 404B, analytics data 404C and the likes.

Even though all these items are shown to be in the same system 400, yet, they may be distributed in multiple systems that may or may not be in the same location. In one embodiment, a cloud may communicate with the systems 400 to deploy items from remote locations, such as, the deployed data 404A.

The touch detector 408 detects touch and its related information, which includes identifying coordinate related to a touch area. In one embodiment, the touch detector 408 may distinguish between a hover and a touch, where the distinction relates to the z axis of the touch. If the hand or object is closer to the object or further from a camera or system then it is a touch. If the hand or object is further from the object or closer to a camera or system then it is hover. In one embodiment, the touch detector may identify different types of touch based on thresholds, such as time, proximity, color of the object doing the touch, based on a sequence of touches, etc. The touch detection 408 may refine the recognition of a touch by performing the method of FIG. 5, which will be described herein below. In another embodiment, the touch detector may crop areas to where only areas of interest are detected, resulting in a touch detection that is more accurate and more efficient.

The touch listener 410 reads the coordinates determined by the touch detector and determines if the touch occurred in a touch area identified during calibration. The touch listener 410 determines the type of reaction or no reaction to take place based on the deployed data, the location of the touch and sometime the type of touch. In some cases, the touch listener 410 may facilitate a zoom in/out or a drag based on the determination of the type of touch. Touch listener may determine that there are no persons and/or no touch for a predetermined time or sense a person walk away and initiate a default display or a predetermined activity.

The analytics module 412 is designed to collect data and/or measure characteristics related to a predetermined object, person, movement, lack of movement, etc. for example, the analytics module 412 may identify a person, follow a path of a person, follow selections of a person, duration of a touch, lack of touch, list a person's activity, determine gender, personal characteristics, traffic, dwell time, etc.

FIG. 5 is an embodiment illustrating a flow diagram of a method 500 for refining touch recognition. The method 500 starts at step 502 and proceeds to step 504. At step 504 the method 500 creates a baseline depth area using multi-frames from a depth camera. At step 506, the method 500 creates a moving average of a real-time area from the depth camera. At step 508, the method 500 determines the difference between the baseline and the moving average. At step 510, the method 500 determines if the difference is less than a pre-determined threshold. If it is less, then the method 500 proceeds to step 512 and looks at the surrounding pixels to determine if the event is a touch or noise. If the surrounding pixels have the same z-axis depth, the event is a touch, and the method 500 proceeds to step 514. In one embodiment, the radius of the surrounding pixels changes based on the depth of the camera. If the difference is greater than the threshold, then determine that the event is a touch, at step 514. If the surrounding pixels have different z-axis, then the method 500 proceeds to step 516. At step 516, the method 500 determines that the event is not a touch. From steps 514 and 516, the method 500 proceeds to step 518 where it ends.

FIG. 6A-C are diagrams depicting an embodiment of an interactive container. In FIG.6A, a container is shown that displays a car engine with its mechanics and electronics. In FIG. 6B, a touch is detected activating a touch area. In FIG. 6C, the touch results in the display of information related to the touch area. In other embodiments, such a touch may result in an engine sound, a menu display, a video activation etc.

It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept. It is understood, therefore, that this disclosure is not limited to the particular embodiments herein, but it is intended to cover modifications within the spirit and scope of the present disclosure as defined by the appended claims.

Claims

1. An interactive container creation method for creating an interactive experience, comprising: creating a list;deploying the list to at least one device;calibrating and identifying touch areas;identifying at least one of an asset and a shape to be defined as a touch area;identifying the x,y axis of each point for a predetermined number of points for each of the at least one of asset or shape; andcreating a touch area based of the identified x,y axis.

2. The interactive container creation method of claim 1, further comprising at least one of: retrieving a baseline depth area utilizing multiple depth frames;retrieving moving average of a real-time area;determining the difference between the baseline depth and moving average;comparing the difference to a threshold and determining if the area is a touch area based on the comparison.

3. The interactive container creation method of claim 2, wherein the method utilizes at least one of a depth camera, a weighted average to add items into the container over time, an interactive container that at least one of communicates and causes change in another container.

4. The interactive container creation method of claim 3, wherein the radius of the surrounding pixels changes based on the depth of the camera.

5. The interactive container creation method of claim 1, wherein the list comprises at least one of an image, an asset, an attribute, a wisp, a rule, a menu, axis location and any combination thereof, wherein an attribute may be at least one of audio, video, image, display, or combination thereof, and wherein an asset is at least one of an object, a person, printout of an object or person, a displayed item, an image, a video, an identified item or person, or a combination thereof.

6. The interactive container creation method of claim 1, wherein the list is deployed from a remote location.

7. The interactive container creation method of claim 1, wherein the list is deployed from a remote location via at least one of a network, a wireless network, and a cloud network.

8. The interactive container creation method of claim 1, wherein the list is the list is created on a machine utilizing the list to where the deployment step is not needed.

9. The interactive container creation method of claim 1, wherein the list is deployed simultaneously on several devices in the same or in different locations.

10. The interactive container creation method of claim 1, wherein the list is deployed from a remote location.

11. The interactive container creation method of claim 1 further comprising a calibration method, wherein the calibration method comprises: identifying an item to be defined as a touch area, wherein the item is one of an asset, a display, a shape, light, exposure, contrast, RGB difference, infrared, or a combination thereof;identifying coordinates of predetermined number of points related to the item; andIdentifying the area within the predetermined points as a touch area.

12. The interactive container creation method of claim 11, wherein the calibration method utilizes a camera to identify the coordinates.

13. The interactive container creation method of claim 11, wherein the calibration method is performed on a single container or multiple containers at the same time.

14. The interactive container creation method of claim 11, wherein the calibration method is one of automatic or manual.

15. The interactive container creation method of claim 11, wherein the calibration method further comprises identifying one of a rule, a menu, a display, and an activity related to the identified touch area.

16. The interactive container creation method of claim 11 further comprising at least one of: training an image to detect at least one of a known image, asset, logo, item or combination thereof;cropping calibration stream to calibrate only areas of interest.

17. An interactive container creation system for creating an interactive experience, comprising: a processor;a storage medium comprising at least one of deployed data and touch area data;a touch detector of generating the touch area data;a touch listener for determining an activity related to a touch area;at least one input/output device for at least one of receiving input to the interactive container system or to cause an action related to the interactive container system.

18. The interactive container creation system of claim 17 further comprising an analytics module related for generating analytics data.

19. The interactive container creation system of claim 17, wherein the interactive container system is distributed over multiple systems.

20. The interactive container creation system of claim 17, wherein the touch detector distinguishes between a touch and a hover.

21. The interactive container creation system of claim 17, wherein the touch detector crops areas to detect only areas of interest.

22. The interactive container creation system of claim 17, wherein the touch listener facilitates a zoom in or out function based on the type of touch.

23. The interactive container creation system of claim 17, wherein the touch listener facilitates a drag function based on the type of touch.

24. The interactive container creation system of claim 17, wherein the touch listener determines that no touch has occurred and cause an action as a result.

25. The interactive container creation system of claim 17, wherein the analytics module collects analytics data related to at least one of a person, characteristics, movement, lack of movement, shopping habits, dwell time, gender, traffic, duration of an activity and a combination thereof.