System and method for object management

Abstract

A method for providing a game or test application can include causing a workspace to be displayed on an interface, the workspace including a plurality of field objects and a plurality of mechanical objects, wherein each of the mechanical objects is positioned within the field objects; causing a plurality of controllable objects to be displayed on the interface; receiving a command to move one of the controllable objects to a position that covers at least a portion of the plurality of field objects; converting the covered portion of the plurality of field objects into an active area; identifying mechanical objects contained within the active area; and responsive to identifying the mechanical objects contained within the active area, running a mechanical object behavior on the mechanical objects within the active area.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 972,755, filed February 11, 2020, the entire contents of which are incorporated herein by reference. Background Technology

[0003] The brains of multicellular eukaryotes (such as humans and other animals) utilize a cognitive process that matches information retrieved from stimuli with information retrieved from memory. Based on this cognition, humans (and to some extent animals) can engage in various games or puzzles that require memorizing a set of rules or pre-programmed actions.

[0004] In standard cognitive tests, users must choose answers from a list of options provided for a given question. In other types of tests, users can issue commands directly to objects (e.g., things displayed on an interface whose behavior is controlled by the user's movement or actions and the game's response to them), thereby changing the object's position, behavior, or properties. Users can also delete objects. Attached Figure Description

[0005] When considered in conjunction with the following figures, reference can be made to the detailed description of the disclosed subject matter to gain a more complete understanding of its various purposes, features, and advantages, wherein like reference numerals denote like elements.

[0006] Figure 1 This is a block diagram of an example system that can implement object management technology according to some embodiments of the present disclosure.

[0007] Figure 2 This is a system diagram with an example device that can implement object management technology according to some embodiments of this disclosure.

[0008] Figure 3 Some embodiments of the present disclosure are shown. Figures 1 to 2 Example input devices used in the system.

[0009] Figure 4 This is a flowchart illustrating an example process of object management according to some embodiments of this disclosure.

[0010] Figure 5A , Figure 6A and Figure 7A This is a flowchart illustrating examples of object behavior according to some embodiments of this disclosure. Figure 5 B Figure 6 B and Figure 7 B illustrates, according to some embodiments of the present disclosure, that can be... Figure 5A , Figure 6A and Figure 7A Example parameter table used.

[0011] Figure 8 Example interfaces displayed to a user according to some embodiments of this disclosure are shown.

[0012] Figure 9 Examples of controllable objects that can be controlled by a user to manipulate mechanical objects according to some embodiments of this disclosure are shown.

[0013] Figure 10 These are example controllable objects according to some embodiments of this disclosure.

[0014] Figure 11 These are example field objects according to some embodiments of this disclosure.

[0015] Figure 12 These are example active field objects according to some embodiments of this disclosure.

[0016] Figure 13 Examples of user-manipulated controllable objects according to some embodiments of this disclosure are shown.

[0017] Figure 14 A controllable object for an overlay field object according to some embodiments of the present disclosure is shown.

[0018] Figure 15 The following are some embodiments of the invention illustrated in this disclosure. Figure 13 The example active field object generated by the manipulation.

[0019] Figures 16 to 18 Example types of mechanical objects according to some embodiments of this disclosure are shown.

[0020] Figures 19 to 27 Examples of user-manipulated controllable objects according to some embodiments of this disclosure are shown.

[0021] Figures 28 to 38 Example behaviors of mechanical objects according to some embodiments of this disclosure are shown.

[0022] Figures 39 to 43 Additional example behaviors of mechanical objects according to some embodiments of this disclosure are shown.

[0023] Figures 44 to 51 Additional example behaviors of mechanical objects according to some embodiments of this disclosure are shown.

[0024] Figure 52 Example interfaces displayed to a user according to some embodiments of this disclosure are shown.

[0025] Figures 53 to 69Example controllable objects are shown according to some embodiments of this disclosure.

[0026] Figures 70 to 71 Example interfaces displayed to a user according to some embodiments of this disclosure are shown.

[0027] Figure 72 Another example interface displayed to a user according to some embodiments of this disclosure is shown.

[0028] Figures 73 to 82 Additional example controllable objects are shown according to some embodiments of this disclosure.

[0029] Figures 83 to 88 Additional example interfaces displayed to a user according to some embodiments of this disclosure are shown.

[0030] Figure 89 Example tasks or objectives that may be displayed to a user before the start of a session are shown according to some embodiments of this disclosure.

[0031] Figures 90 to 91 Example interfaces that can be displayed to the user when a session is completed, according to some embodiments of this disclosure, are shown.

[0032] Figures 92 to 107 An example of a failed session of a user playing an object management game according to some embodiments of this disclosure is shown.

[0033] Figures 108 to 124 Examples of successful sessions of users playing an object management game according to some embodiments of this disclosure are shown.

[0034] Figure 125 It is possible to implement the embodiments according to this disclosure. Figure 1 Example server devices used within the system.

[0035] Figure 126 It is possible to implement the embodiments according to this disclosure. Figure 1 Example computing devices used within the system.

[0036] The accompanying drawings are not necessarily drawn to scale, nor do they necessarily include all the components of the system. Instead, the focus is usually on illustrating the concepts, structures, and techniques that this document seeks to protect. Detailed Implementation

[0037] Embodiments of this disclosure relate to systems and methods that allow users to manage and manipulate various data objects via a user interface. The disclosed object management techniques can be used to assess and / or improve a user's memory, cognitive abilities, abstract and logical reasoning, sequential reasoning, and / or spatial abilities through user-selectable applications (e.g., neuropsychological tests). The application allows a user to remember pre-programmed behaviors via a display and apply them to objects to achieve a pre-specified goal. In some embodiments, the disclosed principles can provide a methodology in which a user can manipulate objects by making changes to an environment in a specific area on a display; the user can perform various manipulations to achieve the goal. Test results can be scored, and the test results can reflect the user's predictive ability to infer the effects of their manipulations. In some embodiments, the disclosed principles can be implemented as, but are not limited to, video games, computer-aided testing devices, personal memory tests, training devices, mathematical visualization devices, or simulation devices. In some embodiments, the game, test, or simulation application can run as an application on a mobile device (e.g., an iOS or Android application); in other embodiments, the application can run in a browser, and the processing can be performed by a remote server on a device running the browser.

[0038] Typically, the game or test application disclosed herein will involve a workspace displayed on a user interface, including field objects, controllable objects, and mechanical objects. Multiple field objects will be displayed to the user in a grid-like or similar manner (e.g., a rectangular grid, where each rectangle is a field object). Controllable objects can be controlled by the user (e.g., clicked and dragged) and can have various shapes or arrangements composed of the same regional units as field objects (e.g., similar to Tetris). For example, a controllable object can simply be a rectangle that the user can click and drag onto the grid of field objects to make it cover a specific field object. Within the grid of field objects in the workspace are mechanical objects, which can be represented by various icons contained within a specific field object (e.g., musical notes running through this disclosure, although this is not limiting). For example, an icon can be contained within a rectangle of the grid. Mechanical objects exhibit various behaviors based on user activation of the field object containing the mechanical object (e.g., moving horizontally, moving vertically, colliding with other mechanical objects, etc.). The user can "activate" or convert a field object into an active field object by moving a controllable object onto it.

[0039] The goal or task displayed to the user before the session begins can be defined as what the winning user needs to do with various mechanical objects in a grid of field objects. A limited number of controllable objects will be provided to the user, and the user must manipulate the mechanical objects by moving these controllable objects onto the grid. This activates the corresponding field objects and causes the mechanical objects to behave in certain predefined ways. There can be various types of mechanical objects. For example, a stationary mechanical object may not move, but might exhibit a certain behavior when another type of mechanical object collides with it. A horizontal mechanical object might only move horizontally when its corresponding field object is active. A vertical mechanical object might only move vertically when its corresponding field object is active. The user can memorize these predefined behavior patterns and use them to manipulate the mechanical objects to complete the task. If the user achieves the goal or task without exhausting the available controllable objects, the user wins. Otherwise, the user loses.

[0040] Figure 92 An example of interface 10 is shown, which can be displayed on a user device, such as a laptop or smartphone. Interface 10 may include a grid of field objects 17; the grid of objects 17 includes multiple field objects A1-A4, B1-B4, C1-C4, and D1-D4. Some of the field objects include different types of mechanical objects 41-43. Interface 10 may also include one or more controllable objects 100-102; the user can move the controllable object and place it on the grid of field objects 17 so that it is aligned with some of the field objects. For example, manipulation can be performed by clicking and dragging with a cursor, via a touchscreen, or by issuing keyboard commands. Once a controllable object is placed on a field object, the field object covered by the controllable object becomes the active field object. If the active field object contains mechanical objects (e.g., 41, 42, or 43), the mechanical objects will behave in some way depending on the type of mechanical object; see reference. Figures 5 to 7 The different behaviors and types of mechanical objects are discussed. For example, if mechanical objects 41, 42, and 43 reside within an active field object, they may behave differently. Pre-programmed behavior can also define what happens when a collision occurs with another mechanical object. The user can then manipulate mechanical objects 41-43 within the field object grid 17 using the various controllable objects 100-102 provided to them to achieve a predefined goal or task displayed to the user before the session begins, such as... Figure 89 The task defined in [the document / framework].

[0041] Figure 1This is a block diagram of an example system that can implement object management techniques according to some embodiments of this disclosure. The system may include a user interaction system 1000, which includes a display 11 and a user input device 12. The display 11 may display various interfaces associated with the disclosed principles, such as objectives / tasks for testing and games, and relevant interfaces for user participation in testing or games, such as available controllable objects, mechanical objects, and field object grids. The user input device 12 may include a device such as a mouse or a touchscreen. The system may also include a controller 13 that can control various interactions and components to be displayed on the display 11. The controller 13 may access a database 14 and a memory device 15. The memory device 15 may include various software and / or computer-readable code for configuring a computing device to implement the disclosed object manipulation techniques. In some embodiments, the memory device 15 may include one or more CD-ROMs, hard disks, or programmable memory devices.

[0042] Figure 2 This is a system diagram of an example apparatus that can implement object management technology according to some embodiments of the present disclosure. The system may include a server 16 communicatively connected to computer 20 and mobile device 21 via the Internet. In some embodiments, the server may utilize one or more of HTML documents, DHTML, XML, RSS, Java, streaming software, etc. In some embodiments, computer 20 may include various computing devices such as personal computers, computer-aided testing equipment, connected televisions, game consoles, entertainment machines, digital media players, etc. In some embodiments, mobile device 21 may include various devices such as PDAs, calculators, handheld computers, portable media players, handheld electronic game devices, mobile phones, tablets, GPS receivers, etc.

[0043] In some embodiments, the Internet may also include other types of communication and / or network systems, such as one or more wide area networks (WANs), metropolitan area networks (MANs), local area networks (LANs), personal area networks (PANs), or any combination of these networks. The system may also include combinations of one or more types of networks, such as the Internet, intranets, Ethernet, twisted-pair, coaxial cable, fiber optic, cellular, satellite, IEEE 801.11, terrestrial, and / or other types of wired or wireless networks, or may use standard communication technologies and / or protocols.

[0044] Figure 3 Some embodiments of the present disclosure are shown. Figures 1 to 2Examples of input devices used in the system. For example, computer 20 may connect to and receive input from at least one of wearable computing device 30, game controller 31, mouse 32, remote control 33, keyboard 34, and trackpad 35. In some embodiments, wearable computing device 30 may include devices such as virtual reality headsets, optical head-mounted displays, smartwatches, etc.

[0045] Figure 4 This is a flowchart illustrating an example process of object management according to some embodiments of this disclosure. Figure 4 The process can describe how users interact with the object management system (e.g., Figure 1 and Figure 2 And participate in tests or games. In some embodiments, Figure 4 The process can be referred to as a game or test “session” as described herein. The session begins at box S101. In some embodiments, initiating a session may further include server 16 displaying a task statement on mobile device 21. At box S102, mobile device 21 may display a workspace (e.g., a field object grid) and one or more controllable objects that the user can use for the session. At box S103, server 16 determines whether the user has moved a controllable object to the field object grid. If the user has not moved a controllable object, the process returns to box S102, and server 16 continues to display the field object grid and the available controllable objects for the user. If the user has moved a controllable object to the field object grid, the process proceeds to S104.

[0046] In box S104, server 16 determines whether a user command has been received to convert a necessary field object (e.g., a field object covered by a moved controllable object) into an active field object. If no user command has been received, processing returns to box S102, and server 16 continues to display the field object grid and the available controllable objects available to the user. If a user command has been received, processing continues to box S105. In box S105, server 16 changes the necessary field object into an active field object. In box S106, server 16 performs mechanical object actions on any mechanical objects now within the active field object. In some embodiments, this may include various actions such as combining, moving, or removing mechanical objects; see reference... Figures 5 to 7Additional details regarding the behavior of the mechanical objects are described. After the mechanical object behavior is executed by server 16, processing can proceed to box S107. In box S107, server 16 determines if there are any remaining controllable objects available for the user to place. For example, five mechanical objects may have initially been offered to the user; server 16 will determine if any of these five controllable objects have not yet been placed. If server 16 determines that there are still controllable objects available to play with, processing returns to box S102, and server 16 continues to display the field object grid and the available controllable objects for the user. If server 16 determines that there are no more controllable objects to play with (e.g., the user cannot move and can no longer manipulate the mechanical objects in the field object grid), processing continues to box S108, and the game session ends.

[0047] Figures 5 to 7 This is a flowchart illustrating examples of object behavior according to some embodiments of this disclosure. As described above, there can be various types of mechanical objects that manifest themselves in different ways. Mechanical object types can include stationary mechanical objects, horizontal mechanical objects, and vertical mechanical objects, and can be identified by object categories. As described herein, the "CLR" class corresponds to stationary mechanical objects, the "CLD" class corresponds to horizontal mechanical objects, and the "CLC" class corresponds to vertical mechanical objects. Furthermore, each type of mechanical object has an associated parameter table. For example, Figure 5 B shows the parameter table 841 for the stationary mechanical object (CLR). The only parameter is "Active", and the only parameter value is 0. Figure 6 B shows parameter table 842 for the horizontal mechanical object (CLD). This parameter can be "false" or "active". When the parameter is active, the parameter value is 0. When the parameter is false, the parameter value is also false, and the horizontal mechanical object disappears from the display. Figure 7 B shows the parameter table 843 for the Vertical Mechanical Object (CLC). This parameter can be false, level 1, level 2, etc. The relevant parameter value is false (the vertical mechanical object disappears) or displays the corresponding number. Note that object behavior does not necessarily include collisions, and... Figures 5 to 7 The behavior is not restrictive. In some embodiments, object behavior including movement (e.g., horizontal, vertical, tilting, or any combination thereof) may not include collision. For example, after a mechanical object moves within an active field area and enters the same field object as another mechanical object, there may be no collision behavior, and the two mechanical objects may coexist in the same field object. In some embodiments, this "non-collision" characteristic may be pre-programmed for other types of mechanical objects, such as non-collision objects.

[0048] Specifically, Figure 5AA flowchart illustrating the object behavior of a stationary mechanical object is provided. In block S201, server 16 determines the category of the mechanical object, and if the category is CLR, the stationary mechanical object is locked in its current position (i.e., the current field object it resides in). In block S202, in response to the field object becoming the active field object, server 16 begins to execute the mechanical object behavior, such as... Figure 4 As shown. In box S203, server 16 determines whether the stationary mechanical object is within the active field object. If the stationary mechanical object is not within the active field object, the process returns to box S201, and server 16 continues to lock the stationary mechanical object at its current position. If the stationary mechanical object is within the active field object, the process proceeds to box S204. In box S204, server 16 determines whether the stationary mechanical object has collided with another mechanical object. Collisions can occur with any other type of mechanical object, and a collision can be the result of any mechanical object's movement. For example, a horizontal mechanical object may have moved horizontally and collided with the stationary mechanical object. If server 16 determines that there is no collision, the process returns to box S201, and server 16 continues to lock the stationary mechanical object at its current position. If server 16 determines that a collision exists, the process proceeds to box S205.

[0049] In box S205, server 16 can analyze the object category of the mechanical object that collides with the fixed mechanical object. If server 16 determines that the colliding mechanical object is not of class CLD (not a horizontal mechanical object), processing returns to box S201, and server 16 continues to lock the fixed mechanical object at its current position. If server 16 determines that the colliding mechanical object is of class CLD, processing proceeds to box S206. In box S206, server 16 changes the object category of the horizontal mechanical object to "dummy" (see...). Figure 6 B), which causes the horizontal mechanical object to disappear and no longer be displayed to the user. Then, the process returns to box S201, and server 16 continues to lock the stationary mechanical object in its current position.

[0050] Figure 6A This is a flowchart illustrating the object behavior of a horizontal mechanical object. In block S301, server 16 determines the category of the mechanical object as CLD, and the parameter value is set to active. In block S302, server 16 begins executing the mechanical object behavior in response to the field object becoming the active field object, such as... Figure 4As shown. In block S304, server 16 determines whether the horizontal mechanical object is located within the active field object. If the horizontal mechanical object is not located within the active field object, the process proceeds to block S303, and server 16 locks the horizontal mechanical object at its current position. If the horizontal mechanical object is located within the active field object, the process proceeds to block S305. In block S305, server 16 moves the horizontal mechanical object horizontally within the active field object. Horizontal movement can be performed in various ways. For example, if three consecutive horizontal field objects become active, and one of the field objects contains the horizontal mechanical object, the horizontal mechanical object will move horizontally back and forth between the three consecutive active field objects. In other embodiments, horizontal movement can be performed from left to right once until the mechanical object reaches the end of the active field area, from right to left until the mechanical object reaches the end of the active field area, a single round trip from right to left, a single round trip from left to right, or multiple round trips in either direction. In some embodiments, the behavior of a mechanical object may also include both horizontal and vertical movement, similar to the L-shaped movement pattern of a knight in chess, or diagonal movement.

[0051] In box S306, server 16 determines whether the horizontal mechanical object collides with another mechanical object. If server 16 determines that no collision occurs, the process returns to box S301 and repeats; in other words, as long as no collision occurs, the horizontal mechanical object continues to move back and forth in the relevant active field. If server 16 determines that a collision occurs, the process proceeds to box S307. In box S307, server 16 can analyze the object category of the mechanical object that collided with the horizontal mechanical object. If server 16 determines that the colliding mechanical object is not a CLC class (not a vertical mechanical object), the process returns to box S301 and repeats. If server 16 determines that the colliding mechanical object is a CLC class (e.g., a vertical mechanical object), the process proceeds to box S308. In box S308, server 16 obtains the corresponding parameter value from the vertical mechanical object, which can be used for calculations in various applications (see “Alternative Embodiments”). In box S309, server 16 changes the parameter of the vertical mechanical object to spurious, and the vertical mechanical object disappears from the user's display. From here, processing can return to box S301.

[0052] Figure 7A This is a flowchart illustrating the object behavior of a vertical mechanical object. In block S401, server 16 determines that the mechanical object's category is CFC and that the parameter value is at level 1, although level 1 is not required. In block S402, server 16 begins running the mechanical object behavior in response to the field object becoming the active field object, such as... Figure 4As shown. In block S404, the server determines whether the vertical mechanical object is located within the active field object. If the vertical mechanical object is not located within the active field object, the process proceeds to block S403, and the server 16 locks the vertical mechanical object at its current position. If the vertical mechanical object is located within the active field object, the process proceeds to block S405. In block S405, the server 16 causes the vertical mechanical object to move vertically within the active field object. The vertical movement can be performed in various forms. For example, if three consecutive vertical field objects become active, and one of the field objects contains the vertical mechanical object, the vertical mechanical object will move vertically until it reaches the last of the three consecutive active field objects. In other embodiments, the vertical movement can be a single top-to-bottom movement until the mechanical object reaches the end of the active field area, a bottom-to-top movement until the mechanical object reaches the end of the active field area, a single round trip from top to bottom, a single round trip from bottom to top, or multiple round trips in either direction. In some embodiments, the behavior of a mechanical object may also include both horizontal and vertical movement, similar to the L-shaped movement pattern of a knight in chess, or diagonal movement.

[0053] In box S406, the server determines whether the vertical mechanical object collides with another mechanical object. If the server 16 determines that there is no collision, the process returns to box S401 and repeats; in other words, the vertical mechanical object is locked in its current position. If the server 16 determines that a collision exists, the process proceeds to box S407. In box S407, the server 16 can analyze the object category of the mechanical object that collided with the vertical mechanical object. If the server 16 determines that the colliding mechanical object is not a CLC class (not a vertical mechanical object), the process returns to box S401 and repeats. If the server 16 determines that the colliding mechanical object is a CLC class (e.g., a vertical mechanical object), the process proceeds to box S408. In box S408, the server 16 changes the parameter from the vertical mechanical object above to spoof, causing it to disappear from the user's display. In box S409, the server 16 changes the parameter from the vertical mechanical object below to the sum of the values ​​of the two colliding mechanical objects. From here, the process can return to box S401.

[0054] Figure 8An example interface 10 displayed to a user according to some embodiments of the present disclosure is shown. Interface 10 can be displayed on various platforms, such as computer 20 or mobile device 21. Interface 10 includes a controllable object 100 and a field object grid 17. The field object grid 17 may include a rectangular pattern 200 of field objects (also referred to herein as "field object 200"), although this is not a limiting example and other arrangements are possible. Furthermore, the controllable object 100 may include a surrounding selectable area 90. The user can manipulate the controllable object 100 by clicking anywhere within the selectable area 90 and dragging the controllable object 100 onto the rectangular pattern 200.

[0055] Figure 9 Examples of controllable objects that a user can control and manipulate according to some embodiments of this disclosure are shown. When a user begins a test or game, he / she attempts to achieve a pre-specified goal or task; this task must be completed under certain constraints to provide a challenge. In the context of this disclosure, constraints can be defined by a set of controllable objects provided to the user for a specific session. For example, Figure 9 "Set A" is a possible set; five controllable objects 100, all with the same shape, will be provided to the user: the same shape as the field object. In another example, the user could be provided with... Figure 9 The “set B” includes various configurations of controllable objects 100-102, both of which are controllable objects 100.

[0056] Figure 10 This is an example of a controllable object 100 according to some embodiments of the present disclosure. For visual differentiation within this disclosure, the controllable object 100 may include a pattern 50. However, in practical applications of the disclosed principles, the controllable object may have any visual appearance when displayed. Figure 11 This is an example field object 200 according to some embodiments of the present disclosure. Also for visual distinction in the present disclosure, field object 200 may include a pattern 60, although it is not required to have such a blank pattern, and may have any visual appearance when displayed. Figure 12 This is an example active field object 300 according to some embodiments of the present disclosure. Again, for visual distinction in this disclosure, the active field object 300 may include a pattern 70, although this is not required and any visual appearance is possible during display.

[0057] Figure 13 Examples of user-manipulated controllable objects 100 according to some embodiments of the present disclosure are shown. For example, a user can manipulate (e.g., click and drag) controllable object 100 until corner 1 is aligned with corner 1a of field object 200. Figure 14The result of a controllable object 100 overriding a field object 200 according to some embodiments of this disclosure is shown. This may be referred to herein as an overridden field object 201, which also has pattern 50. In response to user confirmation of a change to the active field object, the overridden field object 201 can be converted back into the active field object. Figure 15 The following are some embodiments of the invention illustrated in this disclosure. Figure 13 The manipulation produces an example active field object 300. Active field object 300 now has pattern 70.

[0058] Figures 16 to 18 Example types of mechanical objects according to some embodiments of this disclosure are shown. In the context of this disclosure, Figures 16 to 18 The visual appearance of mechanical objects is used to visually distinguish them from other objects; however, this appearance of mechanical objects is neither necessary nor limiting. Rather, the use of different appearances is merely exemplary, and many possible icons or images can be used for their placement. Figure 16 The stationary mechanical object 41 (CLR class) is shown; Figure 17 A horizontal mechanical object 42 (CLD class) is shown; Figure 18 Vertical mechanical object 43 (CLC class) is shown.

[0059] Figures 19 to 27 Examples of user-manipulated controllable objects according to some embodiments of this disclosure are shown. Figure 19 A controllable object 100 with pattern 50 is shown, which is dragged to cover a complete field object 210 with pattern 60 (e.g., a field object containing mechanical objects, such as stationary mechanical object 41), such that corner 1 is aligned with corner 1a. Figure 20 The overridden full field object 211 is shown, which can be converted into an active field object in response to user confirmation. In some embodiments, the conversion into an active field object may also occur automatically. Figure 21 The complete active field object 310 is shown, which contains the stationary mechanical object 41 and now has a pattern 70. Figures 22 to 24 It shows the relationship with Figures 19 to 21 The same process is described, but in which the horizontal mechanical object 42 is within the complete field object 220. The complete field object 220 is changed to an overriding complete field object 221, and then, once activated by the user, it is changed to a fully active field object 320, which contains the horizontal mechanical object 42 and now has the pattern 70. Figures 25 to 27 It also shows with Figures 19 to 21 and Figures 22 to 24The process is the same as described in the previous section, but with a vertical mechanical object 43 within the complete field object 230. The complete field object 230 is changed to an overriding complete field object 231, and then, once activated, is changed to a fully active field object 330, which contains the vertical mechanical object 43 and now has a pattern 70.

[0060] Figures 28 to 38 Example behaviors of mechanical objects according to some embodiments of this disclosure are shown. For example, Figure 28 A grid of field objects with multiple field objects is shown, such as field object 200 with pattern 60. Figure 29 Another field object grid with multiple field objects is shown, such as field object 200 with pattern 60 and full field object 210 containing stationary mechanical object 41. Figure 30 It shows Figure 29 The field object grid and the process of user manipulation of a controllable object 100 with pattern 50 to cover the field object 200. Figure 31 The overridden field object 201 is shown. Figure 32 and Figure 33 An active field object 300 with pattern 70 is shown.

[0061] Figure 34 This demonstrates the user manipulating the second controllable object 100 to... Figure 33 The process of aligning it with the C2 complete field object containing the fixed mechanical object 41 in the workspace. Figure 35 The diagram shows the overlaid full field object 211 adjacent to the active field object 300. Once activated, the full field object 211 becomes the active field object, as shown below. Figure 36 As shown, it illustrates the adjacent active field frames that form the active field region 311 containing the stationary mechanical object 41.

[0062] Figure 37 This demonstrates how the user manipulates the third controllable object 100. Figure 36 The process of aligning it with the C3 field object in the workspace. Figure 38 The new active field region 313 is shown, in which field objects B2, C2, and C3 have all been converted into active field objects with pattern 70. Additionally, because the only mechanical object contained within the active field region 313 is a stationary mechanical object, the stationary mechanical object 41 does not move (see...). Figure 5 ).

[0063] Figures 39 to 43 Additional example behaviors of mechanical objects according to some embodiments of this disclosure are shown. For example, Figure 39A grid of field objects is shown, such as an active field object 300 with pattern 70 and a complete field object 220 with pattern 60 containing a horizontal mechanical object 42. Figure 40 This demonstrates how the user manipulates the controllable object 100. Figure 39 The process of making controllable object 100 cover the entire field object 220 and be adjacent to active field object 300 on the field object grid. Figure 41 A covered field object 221 with pattern 50 containing a horizontal mechanical object 42 is shown. Figure 42 The diagram shows a field object grid when the covered full field object 221 is activated (e.g., by a user or automatically by a server) and becomes an active field object 321 with pattern 70 containing the horizontal mechanical object 42 at position 2.

[0064] like Figure 6A As described in block S305, when the horizontal mechanical object 42 is located within the active field area, it will move horizontally through the active field objects within that area. Figure 43 The process of horizontal mechanical object 42 moving horizontally from position 2 (C2) to position 3 (B2) in active field object 321 is shown.

[0065] Figures 44 to 51 Additional example behaviors of mechanical objects according to some embodiments of this disclosure are shown. For example, Figure 44 A grid of field objects is shown, including an active field object 300 and a complete field object 230 with a pattern 60 containing a vertical mechanical object 43. Figure 45 This demonstrates how the user manipulates the controllable object 100. Figure 44 The process of making controllable object 100 cover the entire field object 230 and be adjacent to active field object 300 on the field object grid. Figure 46 A covered field object 231 with pattern 50 is shown, containing a vertical mechanical object 43. Figure 47 The diagram illustrates a field object grid once the fully covered field object 231 is activated (e.g., by a user or automatically by a server) and becomes an active field object 331 with pattern 70 containing vertical mechanical objects 43.

[0066] Figure 48 This shows the user manipulating the attached controllable object 100. Figure 47 The process of making the field object on the grid cover the field object at C3 and be located below the active field object 331. Figure 49 The overridden field object at C3 is shown. Figure 50The diagram shows the field object grid once the covered field object at C3 is activated and becomes the active field area 333 with pattern 70. The vertical mechanical object 43 is located at position 4 (C2). (As shown...) Figure 7A As described in S405, when the vertical mechanical object 43 is within the active field area, it will move vertically through the various active field objects within that area. Figure 51 The process of vertical mechanical object 43 being moved vertically from position 4 (C2) within the active field area 333 to position 5 (C3) is shown.

[0067] Figure 52 An example interface 10 displayed to a user according to some embodiments of the present disclosure is shown. The interface 10, which can be displayed on a mobile device 21, includes a controllable object 100 with a pattern 50 that can be moved by a user via a selectable area 90. Furthermore, the interface 10 may include a field object 200 with a pattern 60 and a complete field object 220 with a pattern 60 that includes a horizontal mechanical object 42.

[0068] Figures 53 to 69 Example controllable objects according to some embodiments of the present disclosure are shown, each of which has a pattern 50 or patterns 50a-g. In the context of this disclosure, controllable objects provided to a user to complete a game or test can be of various shapes. This allows for controllable level difficulty and greater flexibility in game design. While not exhaustive, potential controllable objects utilizing rectangular field objects in a system may include controllable object 100 aligned with a field object. Figure 53 ), and the controllable object 102 aligned with the two field objects ( Figure 54 ), and controllable object 103 aligned with the three field objects. Figure 55 ), and various controllable objects 104-106 aligned with the four field objects. Figures 56-58 ), and controllable object 107 aligned with the five field objects ( Figure 59 ).

[0069] In other embodiments, the disclosed principles may utilize field objects in a grid that are less elongated and more square-like. For example, see... Figures 60 to 69 Controllable objects 110-119 are shown in the document. Although their shapes and patterns differ, users can control these controllable objects in the same way as the previously described types.

[0070] Figures 70 to 71 Example interfaces displayed to a user according to some embodiments of this disclosure are shown. For example, Figures 70 to 71The interface may include a grid of field objects 400 having multiple square field objects 400, which may also be described singularly herein as square field objects 400. The interface also includes a complete field object 430 containing a vertical mechanical object 43, a complete field object 420 containing a horizontal mechanical object 42, and a complete field object 410 containing a stationary mechanical object 41, as well as a controllable object 111 having a selectable area 90. Figure 71 This is shown after the user has placed two controllable objects 111 onto the field object grid. Figure 70 The interface creates an active field object 502 and an active field object 532 containing a vertical mechanical object 43, each of which has a pattern 70.

[0071] Figure 72 Another example interface 10 displayed to a user on a mobile device 21 according to some embodiments of the present disclosure is shown. Interface 10 may include a plurality of controllable objects 110, 111 and 114 that can be placed by a user on a plurality of field objects 400 having a pattern 60 (including a complete field object 420 containing a horizontal mechanical object 42).

[0072] Figures 73 to 82 Additional example controllable objects according to some embodiments of this disclosure are shown. As described above, in the context of this disclosure, the shape and / or pattern of the controllable object is not limited to any particular shape (e.g., rectangle, square, or other quadrilateral). For example, in some embodiments, the controllable object and associated field object may be triangular. Figures 73 to 82 Controllable objects 120-129 of patterns 50a-e can be provided to the user and used in the disclosed game or test application. In some embodiments, such as in Figure 81 and Figure 82 In this context, controllable objects 128 or 129 may also include invisible controllable objects 80, which are displayed on the user's monitor but whose mechanical behavior is disabled.

[0073] Figures 83 to 88 An additional example interface 10 is shown on a mobile device 21 displayed to a user according to some embodiments of the present disclosure. Figure 83 The display incorporates a triangular theme and includes controllable objects 120, 122, and 129 based on triangular patterns, as well as selectable areas 91-93. The display also includes multiple field objects 600, a complete field object 620 with horizontal mechanical objects 42 and patterns 60, and an active field area 700.

[0074] Figure 84A display 11 is shown including rectangular controllable objects that can be manipulated by a user via selectable areas 91-96. The field object grid includes multiple field objects 200 with pattern 60, a complete field object 220 with a first horizontal mechanical object 42, an active field object 300 with pattern 70, an active field area 317 containing a stationary mechanical object 41, and an active field area 336 containing a second horizontal mechanical object 42 and a vertical mechanical object 43. Based on... Figures 5 to 7 As described in the text, the second horizontal mechanical object 42 in the active field area can move horizontally, and the vertical mechanical object 43 can move vertically.

[0075] Figure 85 and Figure 86 Other examples of possible displays utilizing the disclosed principles are shown. For example, Figure 85 A mobile device 21 is shown with controllable objects with patterns 50 and 50a-b and selectable areas 90, which a user can use to manipulate the controllable objects onto multiple field objects 200 with patterns 60. Figure 86 An embodiment of this disclosure is shown, wherein the available controllable objects and associated selectable regions 91 and 92 are displayed to the right of, rather than below, a plurality of field objects 200. Figure 87 Another possible embodiment is shown where a grid of field objects and available controllable objects are displayed to a user on device 21; controllable objects 100-102 and corresponding selectable areas 91-93 can be displayed on top of multiple field objects 200. Figure 88 Another possible embodiment is shown, displaying controllable objects 100-102 and multiple field objects 200, including an information screen 40. In some embodiments, the information screen 40 may include a task screen 801, a failure screen 802, a success screen 803, clues, test progress, user scores, answers, test results, real-time simulation results, etc.

[0076] Figure 89 Example tasks or objectives that may be displayed to a user before the start of a session are illustrated according to some embodiments of this disclosure. Interface 10 may include a task screen 801 that provides details about what the user needs to accomplish to successfully “win” a game or test. Task screen 801 may include mechanical objects that the user must attempt to obtain by manipulating various controllable objects, and the required quantity of each. For example, the user must obtain vertical mechanical objects 812 (quantity 811), horizontal mechanical objects 814 (quantity 813), and stationary mechanical objects 816 (quantity 815) with a level two state (quantity 811). In some embodiments, the number of eighth notes within hexagonal icons may reflect the “level” state of the mechanical objects.

[0077] Figures 90 to 91 Example interfaces that may be displayed to a user upon completion of a session, according to some embodiments of this disclosure, are shown. If a user is participating in a game or test application as described herein and fails to complete a pre-assigned task (e.g., exhausting all initially assigned controllable objects before meeting the task requirements), a failure screen 802 may be displayed to the user. Figure 90 Similarly, if the user does achieve the task requirements before exhausting the allocated controllable objects, a success screen 803 can be displayed to the user. Figure 91 ).

[0078] Figures 92 to 107 Examples of failed sessions of a user playing an object management game according to some embodiments of this disclosure are shown. For illustrative purposes and not as a limiting example, users can attempt to implement... Figure 89 The task is displayed on task screen 801. Figure 92 The diagram shows interface 10 displayed to the user at the start of a session, after task screen 801 has already been shown. Interface 10 includes a field object grid 17 and five mechanical objects: a first vertical mechanical object 43 (D1), a second vertical mechanical object 43 (B2), a horizontal mechanical object 42 (A3), a third vertical mechanical object 43 (B4), and a stationary mechanical object 41 (D4). Interface 10 also indicates to the user that controllable objects 100-102 can be manipulated via selectable areas 91-93 respectively. Furthermore, interface 10 specifies the available quantity of each corresponding controllable object via digital displays 821-823.

[0079] Figure 93 The process of a user moving a controllable object 102 (e.g., via a click and drag process) onto a field object grid 17 is shown, such that it covers the field objects at B2, A3, and B3. Figure 94 The result of placing the controllable object 102 is shown, which converts the field objects at B2, A3, and B3, containing the second vertical mechanical object 43 and the horizontal mechanical object 42, into active field objects. For example... Figures 5 to 7 The server controlling the behavior and operations of the game or test will cause the relevant mechanical objects within the active field area to move. For example... Figure 95 As shown, the second vertical mechanical object 43 moves vertically between B2 and B3 (box S405), while the horizontal mechanical object 42 moves horizontally between A3 and B3 (box S305). Figure 96The collision result between the second vertical mechanical object 43 and the horizontal mechanical object 42 is shown (boxes S306-S309). Because the horizontal mechanical object 42 (CLD) collides with the vertical mechanical object 43 (CLC), the horizontal mechanical object 42 obtains the corresponding value (1) from the vertical mechanical object 43, and the server changes the parameter of the vertical mechanical object 43 to "false," causing it to disappear from the display. There is no effect on the first vertical mechanical object 43, the third vertical mechanical object 43, or the stationary mechanical object 41, as these are not in the valid field. Furthermore, Figures 94 to 96 Controllable object 102 will no longer be displayed as something that can be manipulated.

[0080] Figure 97 The process of a user moving a controllable object 100 onto a field object grid 17 so that it covers the field object at B4 is illustrated. Figure 98 The result of placing the controllable object 100 is shown, which converts the field object at B4 into an active field object and expands the active field area. Figure 99 The process is shown where a user moves controllable object 101 onto field object grid 17 so that it covers the field objects at C3 and D3. Figure 100 The result of placing controllable object 101 is shown, which converts the field objects at C3 and D3 into active field objects. Similarly, a server controlling the behavior and actions of the game or test will cause the associated mechanical objects within the active field area to move. Figure 101 As shown, the horizontal mechanical object 42 moves horizontally along the third row (A3-D3). Additionally, Figure 100 and Figure 101 The interface 10 no longer displays the controllable object 101 as something that can be manipulated.

[0081] Figure 102 The process is shown where a user moves another controllable object 100 onto the field object grid 17 so that it covers the field object at D1. Figure 103 The result of placing controllable object 100 is shown, which converts the field object at D1 into an active field object. Additionally, the count of available controllable object 100 is decremented by one. Figure 104 The process is shown where the user moves the third and last controllable object 100 onto the field object grid 17 so that it covers the field object at D2. Figure 105 The result of placing controllable object 100 is shown, which converts the field object at D2 into an active field object. As a result, the server controlling the behavior and actions of the game or test will cause the associated mechanical objects within the active field area to move. Figure 106 As shown, the first vertical mechanical object 43 moves vertically along the fourth column (D1-D3). Figure 107The collision result between the first vertical mechanical object 43 and the horizontal mechanical object 42 is shown (boxes S306-S309). Again, because the horizontal mechanical object 42 (CLD) collides with the vertical mechanical object 43 (CLC), the horizontal mechanical object 42 obtains the corresponding value (1) from the vertical mechanical object 43, and the server changes the parameter of the vertical mechanical object 43 to "false", causing it to disappear from the display. Furthermore, because the user has no remaining controllable objects to manipulate (e.g., selectable areas 91-93 are blank) and has one stationary mechanical object, one horizontal mechanical object, and one level one vertical mechanical object (unlike the one stationary mechanical object, one horizontal mechanical object, and one level two vertical mechanical object specified as in task screen 801), the user has failed the task, and a failure screen can be displayed to the user.

[0082] Figures 108 to 124 Examples of successful user sessions playing an object management game according to some embodiments of this disclosure are shown. Again, this is for illustrative purposes and not as a limiting example; users can attempt to implement... Figure 89 The task is displayed on task screen 801. Figure 108 This illustrates a user moving a controllable object 101 (e.g., via a click and drag process) to a field object grid 17 (e.g., with...). Figure 92 The process of making the same field object on the grid 17 (displayed in the image) cover the field objects at A3 and B3. Figure 109 The result of placing the controllable object 101 is shown, which converts the field objects at A3 and B3, containing the horizontal mechanical object 42, into active field objects. For example... Figures 5 to 7 The server controlling the behavior and operations of the game or test will cause the relevant mechanical objects within the active field area to move. For example... Figure 110 As shown, the horizontal mechanical object 42 moves within the active field area 351.

[0083] Figure 111 The process is shown whereby a user moves controllable object 102 onto field object grid 17 so that it covers field objects at D2, C3, and D3. Figure 112 The result of placing the controllable object 102 is shown, which transforms the field objects at D2, C3, and D3 into active field objects and forms a larger active field area 352. Figure 113 This shows that after the active field area extends horizontally, the horizontal mechanical object 42 continues to move horizontally to D3.

[0084] Figure 114 The process is illustrated in which a user moves a controllable object 100 onto a field object grid 17 such that it covers the field object at B2 containing the second vertical mechanical object 43. Figure 115The result of a user placing a controllable object 100 is shown, which transforms the field object at B2 into an active field object, forming a larger active field area 353. Because the second vertical mechanical object 43 is now within the active field object area 353, the server controlling the behavior and operations of the game or test will move it vertically downwards to B3, as shown. Figure 116 As shown.

[0085] Figure 117 The process is illustrated in which a user moves another controllable object 100 onto the field object grid 17 such that it covers the field object at B4 containing the third vertical mechanical object 43. Figure 118 The diagram illustrates the result of a user placing a controllable object 100, which transforms the field object at B4 into an active field object, forming a larger active field area 354. Because the active field area 354 is now a vertical path extending downwards from the second vertical mechanical object 43, it continues to move downwards as a result of instructions from the server, such as... Figure 119 As shown.

[0086] Figure 120 It shows Figure 119 The collision result between the second and third vertical mechanical objects caused by the downward movement of the second vertical mechanical object 43. (For example...) Figure 7 As shown in boxes S406-S409, if two vertical mechanical objects collide, the server changes the parameter of the vertical mechanical object colliding above to "false," causing it to disappear from the user's display. The server also changes the parameter value of the vertical mechanical object colliding below to the sum of the two mechanical objects, which is 2 in this case. Because the value of vertical mechanical object 43 is now 2, the server changes the display to include two eighth notes in the hexagonal icon.

[0087] Figure 121 The process is illustrated in which the user moves the final controllable object 100 onto the field object grid 17 so that it covers the field object at D1 containing the first vertical mechanical object 43. Figure 122 The diagram illustrates the result of a user placing a controllable object 100, which transforms the field object at D1 into an active field object, forming a larger active field region 355. Because the active field region 354 now provides a downward vertical path for the first vertical mechanical object 43, it continues to move downwards as a result of instructions from the server, such as... Figure 123 As shown.

[0088] Figure 124 The collision result of the first vertical mechanical object 43 and the horizontal mechanical object 43 at point D3 is shown. Figure 6As shown in boxes S306-S309, due to the collision between the horizontal mechanical object 42 (CLD) and the vertical mechanical object 43 (CLC), the horizontal mechanical object 42 obtains the corresponding value (1) from the vertical mechanical object 43, and the server changes the parameter of the vertical mechanical object 43 to "false", which makes it disappear from the display. Figure 124 Interface 10 now displays stationary mechanical object 41, horizontal mechanical object 42, and vertical mechanical object 44 in level two state, which is consistent with... Figure 89 The task initially specified in task screen 801 matches. Therefore, the user has completed the task and "passed" the game or test.

[0089] Alternative embodiments

[0090] In some embodiments, the concept of winning or losing may not apply, such as when the disclosed principles are used as training devices, mathematical visualization devices, or simulation devices.

[0091] Regarding training equipment (e.g., brain training equipment in hospitals, job skills screening in the workplace, etc.), doctors (or recruiters or other similar positions) can give patients (or job seekers) time to learn the behavior of a mechanical object. Once the test begins, the doctor / recruiter can analyze the patient / applicant's ability to use the machine, their modifications to the machine's behavior, the test progress, and the time spent. In such embodiments, "success" or "failure" may be more subjective, and the outcome can vary based on observed memory abilities, creativity, spatial awareness, personal experience, and analytical abilities or personality traits of the patient / applicant. Results can be observed, and performance evaluation reports can be printed.

[0092] Regarding mathematical visualization devices, after displaying the task screen, a real-time information screen can be displayed (e.g., Figure 88 Information screen 40). The simulation device utilizing the principles of this disclosure allows a user to manipulate mechanical objects as controllable objects to create computational geometry. The user can move the position of the mechanical object through other mechanisms. The server can calculate the received values ​​and convert them into color, area, and / or position as computational geometry. The server then displays the result as a visual image or animation on information screen 40. Embodiments of this disclosure enable users with mathematical and / or design knowledge to create computational geometry results through predictable scenarios of mechanical object manipulation. However, this can be applied to ordinary users without specialized knowledge and can allow them to create intentional or unintentional geometry. These embodiments can be applied to creativity training or creativity assessment.

[0093] Regarding the simulation equipment, the disclosed principles can be used to predict the behavior of production processes, such as raw material mixing, scheduling sequence, part assembly sequence, and timetable. Embodiments of this disclosure can provide a user interface for simulation to predict movements and sequences in injection, extrusion, 3D printing, or part assembly facilities, in situations where the final product frequently changes based on limited raw material composition or properties, or in on-demand production. For example, this application can run as a plug-in or be provided via API to CAD software, BIM design software, production software, or quality control software.

[0094] Figure 125 It is possible Figure 1 A schematic diagram of an example server device 12500 used in system 1000. Server device 12500 can implement the various features and processes described herein. Server device 12500 can be implemented on any electronic device running software applications derived from compiled instructions, including but not limited to personal computers, servers, smartphones, media players, tablet computers, game consoles, email devices, etc. In some embodiments, server device 12500 may include one or more processors 12502, volatile memory 12504, non-volatile memory 12506, and one or more peripheral devices 12508. These components may be interconnected via one or more computer buses 12510.

[0095] Processor 12502 may use any known processor technology, including but not limited to graphics processors and multi-core processors. As an example, a suitable processor for executing instructions may include general-purpose and special-purpose microprocessors, as well as a single processor or one of multiple processors or cores of any kind of computer. Bus 12510 may be any known internal or external bus technology, including but not limited to ISA, EISA, PCI, PCI Express, USB, Serial ATA, or FireWire. Volatile memory 12504 may include, for example, SDRAM. Processor 12502 may receive instructions and data from read-only memory or random access memory, or both. The basic elements of a computer may include a processor for executing instructions and one or more memories for storing instructions and data.

[0096] The non-volatile memory 12506 may include, for example, semiconductor storage devices such as EPROM, EEPROM, and flash memory devices; disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The non-volatile memory 12506 may store various computer instructions, including operating system instructions 12512, communication instructions 12514, application instructions 12516, and application data 12517. The operating system instructions 12512 may include instructions for implementing an operating system (e.g., Mac). The operating system can be multi-user, multi-processor, multi-tasking, multi-threaded, real-time, etc. Communication instructions 12514 may include network communication instructions, such as software for implementing communication protocols such as TCP / IP, HTTP, Ethernet, and telephony. According to the systems and methods disclosed herein, application instructions 12516 may include instructions for performing various processes to provide an application for playing a game or similar test. Application data 12517 may include data corresponding to the aforementioned processes.

[0097] Peripheral device 12508 may be included within or operatively coupled to server device 12500 to communicate with server device 12500. Peripheral device 12508 may include, for example, a network subsystem 12518, an input controller 12520, and a disk controller 12522. Network subsystem 12518 may include Ethernet, for example, a WiFi adapter. Input controller 12520 may be any known input device technology, including but not limited to a keyboard (including a virtual keyboard), a mouse, a trackball, a touchpad, or a display. Disk controller 12522 may include one or more mass storage devices for storing data files; such devices include disks, such as internal hard drives and removable disks; magneto-optical disks; and optical disks.

[0098] Figure 126 The embodiments of this disclosure can be used for Figure 1 The system 1000 includes an example computing device 12600. In some embodiments, device 12600 may be any of devices 20-21. The illustrative user device 12600 may include a memory interface 12602, one or more data processors, a graphics processor, a central processing unit 12604 and / or a security processing unit 12605, and a peripheral device subsystem 12606. The memory interface 12602, one or more central processing units 12604 and / or security processing unit 12605 and / or peripheral device subsystem 12606 may be separate components or may be integrated into one or more integrated circuits. The various components in user device 12600 may be connected via one or more communication buses or signal lines.

[0099] Sensors, devices, and subsystems can be coupled to peripheral subsystem 12606 to enable a variety of functions. For example, motion sensor 12610, light sensor 12612, and proximity sensor 12614 can be coupled to peripheral subsystem 12606 to facilitate orientation, illumination, and proximity functions. Other sensors 12616 can also be coupled to peripheral subsystem 12606, such as Global Navigation Satellite System (GNSS) (e.g., GPS receiver), temperature sensors, biosensors, magnetometers, or other sensing devices to facilitate related functions.

[0100] The camera subsystem 12620 and optical sensor 12622, such as a charge-coupled device (CCD) or complementary metal-oxide-semiconductor (CMOS) optical sensor, can be used to facilitate camera functions such as recording photos and video clips. The camera subsystem 12620 and optical sensor 12622 can be used to collect user images used during user authentication, for example, by performing facial recognition analysis.

[0101] Communication functions can be facilitated by one or more wired and / or wireless communication subsystems 12624, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. For example, Bluetooth (e.g., Bluetooth Low Energy (BTLE)) and / or WiFi communication described herein can be handled by the wireless communication subsystem 12624. The specific design and implementation of the communication subsystem 12624 may depend on the communication network on which the user equipment 12600 is intended to operate. For example, the user equipment 12600 may include networks designed to operate on GSM networks, GPRS networks, EDGE networks, WiFi or WiMax networks, and Bluetooth. TM A communication subsystem 12624 operates on a network. For example, the wireless communication subsystem 12624 may include a managed protocol that enables the device 12600 to be configured as a base station for other wireless devices and / or to provide WiFi services.

[0102] The audio subsystem 12626 can be connected to the speaker 12628 and microphone 12630 to facilitate voice-enabled functions such as speaker recognition, voice copying, digital recording, and telephone functions. For example, the audio subsystem 12626 can be configured to facilitate the processing of voice commands, voice printing, and voice authentication.

[0103] I / O subsystem 12640 may include touch surface controller 12642 and / or other input controller 12644. Touch surface controller 12642 may be coupled to touch surface 12646. Touch surface 12646 and touch surface controller 12642 may use, for example, any of a variety of touch sensitivity technologies to detect contact and its movement or interruption, including but not limited to capacitive, resistive, infrared and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more contact points with touch surface 12646.

[0104] Other input controllers 12644 can be coupled to other input / control devices 12648, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or indicating devices such as pointers. One or more buttons (not shown) may include up / down buttons for volume control of the speaker 12628 and / or microphone 12630.

[0105] In some implementations, pressing the button for a first duration can unlock the touch surface 12646; and pressing the button for a second duration longer than the first duration can turn the power on or off the user device 12600. Pressing the button for a third duration can activate a voice control or voice command module, which allows the user to speak commands into the microphone 12630 to have the device execute the spoken commands. The user can customize the function of one or more of the buttons. The touch surface 12646 can also be used, for example, to implement virtual or soft buttons and / or a keyboard.

[0106] In some embodiments, user device 12600 may display recorded audio and / or video files, such as MP3, AAC, and MPEG files. In some embodiments, user device 12600 may include MP3 player functionality, such as an iPod. TM Therefore, user equipment 12600 may include an iPod-compatible 36-pin connector and / or an 8-pin connector. Other input / output and control devices may also be used.

[0107] Memory interface 12602 can be coupled to memory 12650. Memory 12650 may include high-speed random access memory and / or non-volatile memory, such as one or more disk storage devices, one or more optical storage devices, and / or flash memory (e.g., NAND, NOR). Memory 12650 may store operating system 12652, such as Darwin, RTXC, LINUX, UNIX, OS X, Windows, or an embedded operating system such as VxWorks.

[0108] Operating system 12652 may include instructions for handling basic system services and for performing hardware-related tasks. In some embodiments, operating system 12652 may be a kernel (e.g., a UNIX kernel). In some embodiments, operating system 12652 may include instructions for performing voice authentication.

[0109] The memory 12650 may also store communication instructions 12654 to facilitate communication with one or more additional devices, one or more computers, and / or one or more servers. The memory 12650 may include graphical user interface instructions 12656 for graphical user interface processing; sensor processing instructions 12658 for sensor-related processing and functions; telephone instructions 12660 for telephone-related processes and functions; electronic messaging instructions 12662 for electronic messaging-related processes and functions; web browsing instructions 12664 for web browsing-related processes and functions; media processing instructions 12666 for media processing-related functions and processes; GNSS / navigation instructions 12668 for GNSS and navigation-related processes and instructions; and / or camera instructions 12670 for camera-related processes and functions.

[0110] Memory 12650 can store application (or "app") instructions and data 12672, such as those described above. Figures 1 to 124 The memory 12650 may also store additional software instructions 12674 for various other software applications located at appropriate locations on the device 12600.

[0111] Note that using musical icons (e.g., eighth notes, quarter notes, and half notes) to distinguish different types of mechanical objects is not a limitation; various visual icons, graphics, or images may also be used.

[0112] In some embodiments, the server may also be configured to deliver data and data visualization tools to users via a secure request-based application programming interface (API). For example, a user (e.g., a network or utility administrator) may wish to conduct an in-depth examination of measurements. The server may provide a range of data analysis and presentation capabilities via a secure web portal. For example, the server may provide asset defect signature identification, asset failure risk estimation, pattern recognition, data visualization, and a web map-based user interface. In some embodiments, the server may generate an alert if signal analysis of a defective HF signal indicates that it has exceeded a certain threshold.

[0113] The features described can be implemented in one or more computer programs, which can be executable on a programmable system. The programmable system includes at least one programmable processor, at least one input device, and at least one output device. The at least one programmable processor is coupled to receive data and instructions from a data storage system and to transmit data and instructions to the data storage system. A computer program is a set of instructions that can be used directly or indirectly in a computer to perform a specific activity or produce a specific result. A computer program can be written in any form of programming language (e.g., Objective-C, Java), including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0114] Suitable processors for executing instructions may include, for example, general-purpose and special-purpose microprocessors, as well as a single processor or one of multiple processors or cores of any type of computer. Typically, the processor may receive instructions and data from read-only memory or random access memory, or both. The basic elements of a computer may include a processor for executing instructions and one or more memories for storing instructions and data. Typically, a computer may also include one or more mass storage devices for storing data files, or be operatively coupled to and in communication with one or more mass storage devices for storing data files; such devices include disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Memory devices suitable for tangibly containing computer program instructions and data may include all forms of non-volatile memory, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented or incorporated into ASICs (Application-Specific Integrated Circuits).

[0115] To provide interaction with the user, the features described can be implemented on a computer having a display device for displaying information to the user, such as an LED or LCD monitor, and a keyboard and a pointing device such as a mouse or trackball through which the user can provide input to the computer.

[0116] The features described can be implemented in a computer system that includes back-end components, such as data servers, or middleware components, such as application servers or internet servers, or front-end components, such as client computers with graphical user interfaces or internet browsers, or any combination thereof. The components of the system can be connected via digital data communication of any form or medium, such as a communication network. Examples of communication networks include, for example, telephone networks, LANs, WANs, and computer networks that form the Internet.

[0117] Computer systems can include clients and servers. Clients and servers can typically be geographically separated and can interact via a network. The client-server relationship can be established by computer programs running on their respective computers and having a client-server relationship with each other.

[0118] One or more features or steps of the disclosed embodiments can be implemented using the API. The API can define one or more parameters passed between the calling application and other software code (e.g., operating system, library routines, functions) that provides services, provides data, or performs operations or calculations.

[0119] An API can be implemented as one or more calls in program code, which send or receive one or more parameters through a parameter list or other structure according to the calling conventions defined in the API specification file. Parameters can be constants, keywords, data structures, objects, object classes, variables, data types, pointers, arrays, lists, or other calls. API calls and parameters can be implemented in any programming language. Programming languages ​​can define the vocabulary and calling conventions that programmers use to access the functionality that supports the API.

[0120] In some implementations, API calls can report to the application the capabilities of the device running the application, such as input capabilities, output capabilities, processing capabilities, power capabilities, and communication capabilities.

[0121] Although various embodiments have been described above, it should be understood that these embodiments are presented by way of example and not limitation. It will be apparent to those skilled in the art that various changes in form and detail can be made without departing from the spirit and scope of this disclosure. Indeed, after reading the above description, those skilled in the art will understand how alternative embodiments can be implemented. For example, other steps may be provided, or steps may be removed from the described process, and other components may be added to or removed from the described system. Therefore, other implementations are also within the scope of the following claims.

[0122] It should be understood that the disclosed subject matter is not limited to the structural details and component arrangements set forth in the following description or shown in the accompanying drawings. The disclosed subject matter can have other embodiments and can be practiced and performed in various ways. Furthermore, it should be understood that the wording and terminology used herein are for descriptive purposes and should not be considered restrictive. Therefore, those skilled in the art will understand that the concepts on which this disclosure is based can readily be used as the basis for designing other structures, methods, and systems for achieving several purposes of the disclosed subject matter. Therefore, it is important that the claims be considered to include such equivalent constructions, provided they do not depart from the spirit and scope of the disclosed subject matter.

[0123] Furthermore, it should be understood that any accompanying drawings highlighting features and advantages are for illustrative purposes only. Each of the disclosed methods and systems is flexible and configurable enough that they can be utilized in ways other than those shown.

[0124] Although the term "at least one" may be frequently used in the specification, claims and drawings, the terms "a," "an," "the," "the," etc., also mean "at least one" or "the at least one" in the specification, claims and drawings.

[0125] Finally, the applicant intends that, pursuant to 35 USC112(f), only claims that include the terms "apparatus" or "step" should be interpreted. Claims that do not explicitly include the phrases "apparatus" or "step" should not be interpreted under 35 USC112(f).

[0126] Although the disclosed subject matter has been described and illustrated in the foregoing illustrative embodiments, it should be understood that this disclosure is by way of example only, and various changes may be made to the implementation details of the disclosed subject matter without departing from the spirit and scope of the disclosed subject matter.

Claims

1. A method for providing a game or test application, the method comprising: Display the workspace on the interface. The workspace includes a field object grid, which includes multiple field objects and one or more machine objects, wherein the one or more machine objects are positioned within one or more field objects in the field object grid. Display the controllable object in a selectable area outside the field object grid on the interface, where the user selects the controllable object; Receive a command to move the controllable object from the selectable area to a position that covers at least a portion of the field object grid, wherein the shape of the controllable object is the same as at least a portion of the field object grid to enable coverage; Convert at least a portion of the field object grid that is covered by the controllable object into an active area; Identify mechanical objects contained within the active area; The mechanical object behavior is executed on the mechanical object within the activity area; as well as Achievement is received in response to running mechanical object behavior on the mechanical object within the active area.

2. The method of claim 1, wherein the method includes indicating a number of user-manipulable objects associated with each of a plurality of controllable objects.

3. The method of claim 1, wherein performing the mechanical object behavior includes moving the mechanical object horizontally within the active area.

4. The method according to claim 3, wherein the mechanical object is a first mechanical object, and the method further comprises: Detect the collision between the first mechanical object and the second mechanical object; It is determined that the second mechanical object moved vertically before the collision; as well as In response to the detection of the collision, the second mechanical object is removed from the interface.

5. The method according to claim 3, wherein the mechanical object is a first mechanical object, and the method further comprises: Detect the collision between the first mechanical object and the second mechanical object; It was determined that the second mechanical object had not moved prior to the collision; as well as In response to the detection of the collision, the first mechanical object is removed from the interface.

6. The method of claim 1, wherein performing the mechanical object behavior includes moving the mechanical object within the active area vertically within the active area.

7. The method according to claim 6, wherein the mechanical object is a first mechanical object, and the method further comprises: Detect the collision between the first mechanical object and the second mechanical object; In response to the detection of the collision, the first mechanical object is removed from the interface; as well as The value associated with the second mechanical object is adjusted based on the value associated with the first mechanical object.

8. The method of claim 7, wherein the method includes displaying an indicator on the interface based on a value associated with the second mechanical object.

9. A system for providing a game or testing application, the system comprising: User devices, including user interfaces; as well as A server communicatively connected to the user equipment, the server including a processor and a non-transitory computer-readable storage device storing computer-executable instructions that cause the processor to perform processing as follows: Display the task on the interface; The workspace is displayed on the user interface. The workspace includes a grid of field objects, which includes a plurality of field objects and one or more machine objects, wherein the one or more machine objects are positioned within one or more field objects in the field object grid. Display the controllable object in a selectable area outside the field object grid on the user interface, where the user selects the controllable object; The user equipment receives a command to move the controllable object from the selectable area to a position that covers at least a portion of the field object grid, wherein the shape of the controllable object is the same as at least a portion of the field object grid to enable coverage; Convert at least a portion of the field object grid that is covered by the controllable object into an active area; Identify mechanical objects contained within the active area; execute mechanical object behaviors on the mechanical objects within the active area; as well as Achievement is received in response to running mechanical object behavior on the mechanical object within the active area.

10. The system of claim 9, wherein the server is configured to display an indicator on the user interface, the indicator describing a number of user-manipulable objects associated with each of a plurality of controllable objects.

11. The system of claim 9, wherein performing the mechanical object behavior includes moving the mechanical object horizontally within the active area.

12. The system of claim 11, wherein the mechanical object is a first mechanical object, and wherein the server is configured to: Detect the collision between the first mechanical object and the second mechanical object; Determine that the second mechanical object moved vertically prior to the collision; and In response to the detection of the collision, the second mechanical object is removed from the user interface.

13. The system of claim 11, wherein the mechanical object is a first mechanical object, and wherein the server is configured to: Detect the collision between the first mechanical object and the second mechanical object; It was determined that the second mechanical object had not moved prior to the collision; and In response to the detection of the collision, the first mechanical object is removed from the user interface.

14. The system of claim 9, wherein performing the mechanical object behavior includes moving the mechanical object within the active area vertically within the active area.

15. The system of claim 14, wherein the mechanical object is a first mechanical object, and wherein the server is configured to: Detect the collision between the first mechanical object and the second mechanical object; In response to detecting the collision, the first mechanical object is removed from the user interface; and The value associated with the second mechanical object is adjusted based on the value associated with the first mechanical object.

16. The system of claim 15, wherein the server is configured to display an indicator on the user interface based on a value associated with the second mechanical object.

17. A method for providing a game or test application, the method comprising: Receive instructions from the server to display the task objective on the monitor; The system receives instructions from the server to display a workspace on a user interface. The workspace includes a grid of field objects, which includes a plurality of field objects and one or more machine objects, wherein the one or more machine objects are positioned within one or more field objects in the field object grid. Receive instructions from the server to display controllable objects in a selectable area outside the field object grid on the user interface; The user receives an instruction to move the controllable object from the selectable area to a position that covers at least a portion of the field object grid, wherein the shape of the controllable object is the same as at least a portion of the field object grid to enable coverage; The instruction is transmitted to the server; Receive from the server an instruction to convert at least a portion of the field object grid covered by the controllable object into an active area; Identify mechanical objects contained within the active area; as well as The server receives instructions to perform mechanical object behaviors on the mechanical object within the active area, wherein the mechanical object behaviors include at least one of the following: The mechanical object within the active area is moved vertically; or the mechanical object within the active area is moved horizontally. as well as Achievement is received in response to running mechanical object behavior on the mechanical object within the active area.

18. The method of claim 17, wherein the method comprises: Detect collisions between two or more mechanical objects; In response to the detection of the collision, an indication of the collision is transmitted to the server; Receive adjustments to the value associated with one of the two or more mechanical objects; as well as The adjustment is displayed on the user interface.

Images