JP2016505912A - Content storage apparatus and method - Google Patents

Abstract

A first user content request is received from the first visualization and a second user content request is received from the second visualization. The first user content request and the second user content request are analyzed. Based on the analysis, access to a set of common functions is provided for the first user content request and the second user content request. The state information is shared between the first visualization and the second visualization. [Selection] Figure 1

Description

  The subject matter disclosed herein relates to organizing and storing content within an application.

  Mobile application, or “app” development, remains a relatively unskilled technical field. More specifically, platforms are changing and changing very frequently. The platform's volatility also means that the applications supported by the platform are volatile as well.

  Most Internet websites have their own apps that do nothing but mirror the website. In many situations, multiple separate apps are deployed, and each app performs only a few functions. Therefore, these approaches often waste system resources.

  For mobile applications, a promising approach is the creation of individual applications for individual parts of functionality. However, this also wastes system resources.

  There are also specialists in specific fields, who often have a complete understanding of the field. As a result, these domain experts can provide knowledge of the domain and existing context-dependent information as well as new content that utilizes context from the domain. Unfortunately, these domain experts spend unnecessary time learning, building, compiling, and deploying the entire application. Furthermore, even if the applications are from the same creator, most applications do not provide interoperability for other applications.

  Unfortunately, these shortcomings are rarely a problem in conventional systems, resulting in user penalties and dissatisfaction with these conventional approaches.

US Patent Application Publication No. 2012/260161

  An approach for content storage within a mobile or web application is provided. More specifically, many embodiments described herein provide a single wrapper application that includes a content container having a device interface, context sharing, and interoperability interface.

  In one approach for content storage within a mobile or web application, the container encapsulates the entire content. “Encapsulation” means that all program logic, visualization components, and functionality needed to support visualization are in the application hosting the container. This approach also allows server-side components to provide the necessary functionality for the content, but the visualization and background application level logic or functionality resides in the application itself (eg, an application on a mobile device).

  These approaches also support dynamic hosting of content, which allows visualization components and logic to reside on the server or outside the application somewhere in the cloud computing environment. In this case, the availability of new content is discovered via queries by existing server-side functions, and the required content components can be streamed and loaded into the application container when needed.

  In some approaches, the container provides the general features required for the content as well as the navigability within the application. In other approaches, the container provides the necessary mechanism to contain any type of desired content.

  Content storage can be provided within a mobile or web application, and can provide the ability to distribute and demonstrate a single primary application. In addition, the approach allows the user to decide whether to protect the content by providing custom content and making it accessible only from specific computer systems. In addition, various applications, content, and visualization can share information such as state information.

  In many of these embodiments, a first user content request is received from a first visualization and a second user content request is received from a second visualization. The first user content request and the second user content request are analyzed. Based on the analysis, access to a set of common functions is provided for the first user content request and the second user content request. State information is also shared between the first visualization and the second visualization.

  In another aspect, a selected one of the set of common functions includes setting the size of the graphic display icon. The selected one of the set of common functions further includes a graphic display icon in the user content status bar.

  In yet another aspect, the selected one of the set of common functions includes security related functions. In another aspect, the selected one of the set of common functions includes logging on to the server.

  In yet another embodiment, the state information includes dynamic information about the object or asset. In some other embodiments, the first visualization includes a web page.

  In other of these embodiments, an apparatus for interfacing user content to actions includes an interface and a controller. The interface has inputs and outputs and is configured to receive a first user content request from a first visualization and a second user content request from a second visualization as input.

  The controller is coupled to the interface. The controller is configured to analyze the first user content request and the second user content request. The controller is configured to provide access to a set of common functions for the first user content request and the second user content request based on the analysis. The controller is configured to share state information between the first visualization and the second visualization at the output.

  For a fuller understanding of the present disclosure, reference is made to the following detailed description and accompanying drawings.

1 is a block diagram of a container based system according to various embodiments of the invention. FIG. FIG. 6 includes a flowchart of an example of operating a container based system in accordance with various embodiments of the invention. FIG. 5 includes a flowchart of another example of operating a container based system in accordance with various embodiments of the invention. FIG. 6 includes a flowchart illustrating the operation of a container according to various embodiments of the invention. FIG. 6 includes a block diagram of an apparatus for providing information sharing during access and visualization of common functions according to various embodiments of the present invention.

  Those skilled in the art will appreciate that elements in the drawings are illustrated for simplicity and clarity. It is further understood that although specific operations and / or steps may be described or illustrated in a specific order of appearance, those skilled in the art will understand that specificity for a sequence is not actually necessary. I want. The terms and expressions used herein have their usual meanings that are consistent with the terms and expressions for each corresponding area of research and research, except where specific meanings are set forth herein. Will understand.

  A single wrapper application is provided that includes a content container having a device interface, context sharing, and interoperability interface. The approach provided herein removes or substantially reduces unnecessary processing and frees up domain experts to provide content that operates or is supported by the container. Interoperability is easily made possible by containers that allow new content to interoperate with existing content, and existing content to interoperate with content that was not yet implemented at the time of its creation. .

  In one embodiment, a system is provided that includes a single container, which serves to encapsulate all content. The container provides some general features that the content needs, such as access to device, session and hardware information, and common context dependent information such as user, application and system context information. The container further provides access to providing a complete set of navigability within the application, as well as the availability of context-based custom and dynamic actions. Finally, the container provides all the mechanisms necessary to contain any type of desired content to provide additional visualization and / or functionality to the application. Content is any one or more visualization components combined with both background functionality, as well as server-side components necessary to provide an extension to either existing content or additional distinct content including.

  From these perspectives, the container provides access to common functions, enables sharing of information and context, and includes the components called content, providing the functions necessary to host, execute, and display To act as a top-level master mechanism.

  Static hosting of content is accomplished by including all program logic, visualization components, and functionality within the application that hosts the container itself. Even with this approach, server-side components can provide the necessary functionality for the content, but the visualization and background application-level logic resides in the application itself (eg, an application that resides on a mobile device).

  In addition, a dynamic host of content is provided, allowing visualization components and logic to exist outside of an application anywhere in the server or cloud computing environment. The availability of new content is discovered via queries by existing server-side functions, and the required content components are streamed and loaded into the application container when needed.

  If all content is hosted (encapsulated) in a container, this creates a common access point where context sensitive information can be stored and shared. Furthermore, the data flow can be controlled and shared through provision of a specific access mechanism program. In mobile applications, if both network traffic, i.e. frequency and size, is a concern, the container notifies the content as the controller of the network request when it needs to update or refresh the data, time range and data Important characteristics that affect the size of the data search, such as the set size and maximum size, can be controlled.

  The common program flow and shared context can be used through a shared navigation context. If the set of context-sensitive information has been modified by a given content, switching to other content causes the container to provide this updated set of context information to the newly loaded content, and so on A common program flow and ease of use can be ensured.

  In addition, providing a high level container provides an ideal location for managing specific implementations of functions such as dynamic actions. These dynamic actions can also be realized by some other root-level singleton object if this container does not exist. However, if the container exists and all content already has access and understanding of the container, the concept of action system can be easily incorporated here. This is true for any future function or concept that may span the entire system or multiple separate content or functions.

  The approaches described herein provide content within the domain of expertise by substantially reducing (or eliminating) the time and effort required by a domain expert to compose the content. Enable. Another advantage described herein is the ability to demonstrate a single main application in a distributed manner. Specific content available within the application can be added at various times and even licensed individually. Customers will not have to worry about deciding which apps to load. Instead, they will load a single application and navigate to the content of interest.

  Yet another advantage of this approach relates to advanced container functionality that attempts to allow dynamic streaming or loading of content from a server or cloud based environment. A customer or system integrator can decide to protect by providing custom content and making it accessible only from a particular customer server of a particular integrator cloud solution only.

  An example of the container 102 will now be described with reference to FIG. The container 102 includes an action module 104, an error logging module 106, a parameter passing module 108, a parameter 110, an authentication module 112, and a data update module 114.

  Container 102 is located within a single application, which may itself be located on a mobile device such as a mobile phone, personal computer, pager, or personal digital assistant. Other examples of mobile devices are possible. The container 102 provides access to common functions, enables sharing of information and context between content (visualization), and includes a component called content (or visualization) that hosts, executes, and displays It is a common system level component that acts as a top-level master mechanism to provide the necessary functions for the.

  The action module 104 receives the user's content 115 and processes the information. Various types of functions are supported. In one example, action module 104 receives content or a request from content and determines an icon 116 that is placed in the action bar of content 115. The content 115 is, for example, visualization of information presented to the user displayed on a graphic display. The content 115 can be a single content, but can also be divided into a plurality of content. In this example, the action module 104 determines the type of icon to display, sets the icon size correctly, and returns the icon to the content. When there are a plurality of contents, information (for example, status information) can be shared between the plurality of contents.

  The error logging module 106 receives the content and logs errors related to the content 115. The parameter passing module 108 can receive various parameters 110 and pass them between the content 115 and the server 124 (via the authentication module 112, the interface 120, and the network 122).

  Parameters can be configured, initialized, or updated, and this information is passed to content 115 if the content is a piece of content, or individual if content 115 includes multiple pieces. Content (fragment). The parameter 110 is a value that can be associated with the content 115. Examples of parameters include logged in user, server name, permissions / claims.

  The authentication module 112 authenticates access between the content 115 and the server 124. In these respects, it demonstrates that content can access the server 124 and use any known security protocol to achieve this result.

  The data update module 114 enables data update between the content 115 and the server 124. An example of the data update is new information from the server 124 used to update the content 115.

  It should be understood that the content 115 need not know the detailed operation of the modules within the container 102. Thus, users can change content, add content, and share information without having to worry about all the execution details within a single application that can reside, for example, on a mobile device.

  The container is coupled to interface 120. The interface 120 is any combination of programmed software or hardware that enables communication between the network 122 and the container 102. Interface 120 is coupled to network 122. The network 122 is any network, such as the Internet, a cellular phone network, a data network, or any combination of these networks. Network 122 is coupled to server 124. Server 124 is any combination of software or hardware programmed to provide server or server-side functionality, as is known to those skilled in the art.

  Generally speaking, the container 102 has access to common context-dependent information (via the modules described above) and content such as device, session, and hardware information, and user, application, and system context information. Provides the functions that are required by The container 102 further provides access to providing a complete set of navigability within the application, as well as the availability of custom and dynamic actions based on context. Finally, the container 102 provides all the mechanisms necessary to contain any type of content 115 that is desired to provide additional visualization and / or functionality to the application. In these respects, content 115 is necessary to provide one or more visualization components combined with both background functionality, as well as extensions to either existing content or additional distinct content. Contains server-side components.

  Static hosting of content 115 by container 102 is accomplished by including all program logic, visualization components, and functionality within the application hosting container 102. Even with this approach, any server-side component (eg, server 124) can provide the necessary functionality for content 115, but the visualization and background application-level logic resides in the application in which container 102 resides.

  The dynamic hosting of content by the container 102 allows visualization components and logic to exist outside of an application somewhere in the server 124 or cloud computing environment (eg, network 122). The availability of new content is discovered via queries by existing server-side functions, and the required content components are streamed and loaded into the container 102 when needed.

  If all content is hosted in the container 102, this creates a common access point where context sensitive information is stored and can be shared between different content. Furthermore, programs and data flows can be controlled and shared through the provision of specific access mechanisms. In mobile applications, if network traffic, i.e. both frequency and size, is an issue, the container 102, as a controller for network requests, notifies the content 115 when data needs to be updated or refreshed, and the time range And important properties that affect the size of the data search, such as data set size and maximum size.

  Common program flows and shared contexts can also be used through shared navigation contexts. If the set of context sensitive information is modified by content 115, switching to other content causes content 115 to provide this updated set of context information to the newly loaded content, and thus common Ensure program flow and ease of use.

  Here, with reference to FIG. 2, an example of the transfer and reception of context information between the container 220 and the hosted content 222 will be described. In this case, the container 220 communicates with the content 222. The content 222 may be a visualization (eg, a web page) that can be presented to the user on any type of display.

  In step 202, a predetermined set of parameters is sent to or initialized by container 220. These parameters are a set of parameters provided by the container and are available for all hosted content and are provided on demand. In step 204, a “parameter change” message is sent from the container 220 to the content 222. In step 206, some or all of the application context parameters are requested by content 222 and transmitted by container 220. In step 208, a response is sent that includes the requested (modified) parameters.

  Referring now to FIG. 3, a scenario in which multiple visual fragments (contents) are hosted and parameters modified by one of the fragments will be described. In this case, the container 320 is in communication with the first visual fragment 322 and the second visual fragment 324. Fragments 332 and 334 may be any type of visualization (eg, part of a web page) that can be presented to the user on any type of display.

  In this case, the container 330 sends a “parameter change” event message and both fragments 332 and 334 respond to this event. In this case, the fragment that changed the parameter also responds to the event. Alternatively, this fragment may simply ignore the event.

  In step 302, the first hosted content changes the parameters. In step 304, a “parameter change” message sends that a parameter change event has occurred. This is sent from container 330 to both fragments 332 and 334.

  In step 306, a message is sent from the first fragment 332 to fetch the application content or all context parameters by the first fragment 332. In step 308, the requested information is sent to the first fragment 332.

  In step 310, a request is made by the second fragment 334 to fetch the application content or all context parameters. In step 312, the requested information is sent to the second fragment 334.

  Various types of information can also be shared. For example, in step 314, status information is sent from the first fragment 332 to the container 330. In step 316, this status information is sent to the second fragment 334.

  Now referring to FIG. 4, an example of an approach that allows content to share a common function is described. In step 402, a first user content request is received from a first visualization (or fragment) and a second user content request is received from a second visualization (or fragment). Visualization, in one embodiment, is a separate piece of content that can be displayed together (or need not be displayed together). The first user content request and the second user content request are analyzed at step 404. The analysis determines the nature of the required requirements and actions.

  In step 406, based on the analysis, access to a set of common functions is provided for the first user content request and the second user content request. A common set of functions is in the container, and the detailed functions of these actions are not seen by different content. Thus, both visualizations have access to these functions. In addition, new visualizations are created, and these visualizations have access to and use this common functionality. In step 408, state information is shared between the first visualization and the second visualization. This state information may include dynamic information. In some examples, the state information may include current context (selected asset), key performance indicator (KPI), and alarm information (eg, state, severity, or source) of interest. Other examples of status information are possible.

  Referring now to FIG. 5, one embodiment of an apparatus that provides common functionality and allows visualization fragments to share information will be described. The apparatus 500 includes an interface 502 and a controller 504. Interface 502 has an input 506 and an output 508 and is configured to receive a first user content request 510 from a first visualization and a second user content request 512 from a second visualization at input 506.

  It will be appreciated that apparatus 500 may be implemented as a combination of hardware and software. The apparatus 500 may be a part of an application, for example, an application that resides in a mobile device such as a mobile phone or a personal computer. Alternatively, the device 500 may have its function divided into different physical locations.

  Controller 504 is coupled to interface 502. The controller 504 is configured to analyze the first user content request 510 and the second user content request 512. The controller 504 is configured to provide access to the set of common functions 514 for the first user content request and the second user content request based on the analysis. The controller 504 is configured to share state information 516 between the first visualization and the second visualization at output 508.

  While preferred embodiments of the invention have been described herein, it includes the best mode known to the inventors for carrying out the invention. It should be understood that the illustrated embodiments are exemplary and should not be construed as limiting the scope of the invention.

102 Container 104 Action module 106 Error logging module 108 Parameter passing module 110 Parameter 112 Authentication module 114 Data update module 115 Content 116 Icon 120 Interface 122 Network 124 Server 202 Step 204 Step 206 Step 208 Step 220 Container 222 Content 302 Step 304 Step 306 Step 308 Step 310 Step 312 Step 314 Step 316 Step 320 Container 322 First Visual Fragment 324 Second Visual Fragment 330 Container 332 First Fragment 334 Second Fragment 402 Step 404 Step 406 Step 408 Step 500 Device 502 Interface 04 controller 506 inputs 508 outputs 510 the first user content request 512 the second user content request 514 common function 516 status information

Claims (14)

A method of interfacing user content (115, 222) with an action,
Receiving a first user content request (510) from a first visualization and receiving a second user content request (512) from a second visualization;
Analyzing the first user content request (510) and the second user content request (512);
Providing access to a set of common functions (514) for the first user content request (510) and the second user content request (512) based on the analyzing step;
Sharing state information (516) between the first visualization and the second visualization.   The method of claim 1, wherein a selected one of the set of common functions (514) includes setting a size of a graphic display icon (116).   The method of claim 2, wherein the selected one of the set of common functions (514) further comprises placing the graphic display icon (116) in a status bar.   The method of claim 1, wherein the selected one of the set of common functions (514) includes security-related functions.   The method of claim 1, wherein the selected one of the set of common functions (514) comprises logging on to a server (124).   The method of claim 1, wherein the state information (516) comprises dynamic information about an object or asset.   The method of claim 1, wherein the first visualization comprises a web page. A device that interfaces user content (115, 222) to an action,
An interface (120, 502) having an input and an output to receive as input a first user content request (510) from a first visualization and a second user content request (512) from a second visualization. Interfaces (120, 502) configured to
A controller, wherein the controller is coupled to the interface (120, 502), wherein the controller analyzes the first user content request (510) and the second user content request (512). The controller is further configured to set a common function (514) for the first user content request (510) and the second user content request (512) based on the analysis. Wherein the controller is configured to share status information (516) between the first visualization and the second visualization at an output.   The apparatus of claim 8, wherein a selected one of the set of common functions (514) includes setting a size of a graphic display icon (116).   The apparatus of claim 9, wherein the selected one of the set of common functions (514) further comprises placing the graphic display icon (116) in a status bar.   The apparatus of claim 8, wherein the selected one of the set of common functions (514) includes security-related functions.   The apparatus of claim 8, wherein the selected one of the set of common functions (514) includes logging on to a server (124) via the output.   The apparatus of claim 8, wherein the state information (516) includes dynamic information about an object or asset.   The apparatus of claim 8, wherein the first visualization comprises a web page.