Abstract: Embodiments of the present disclosure, relate to automatic switch of screen layouts. According to an embodiment of the present disclosure, a method for automated switch of screen layouts comprises acquiring object information for each screen layout, processing acquired object information as per user requirements, storing processed object information in a data storage array, evaluating suitability of each screen layout for display and displaying and automatically switching screen layouts as per evaluation and stored object information.
FORM-2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENTS RULES, 2003
(As Amended)
COMPLETE SPECIFICATION (See section 10; rule 13)
“AUTOMATIC SWITCH OF SCREEN LAYOUTS”
TATA TELESERVICES LTD, a corporation organized and existing under the laws of the India, of A, E & F Blocks, Voltas Premises, T.B. Kadam Marg, Chinchpokli, Mumbai – 400033 India.
The following specification particularly describes the invention and the manner in which it is to be performed :
AUTOMATIC SWITCH OF SCREEN LAYOUTS
Field of the Disclosure: -
The present disclosure relates to automatic switch of screen layouts and more particularly, but not limited to, automatic switch of screen layouts on video walls.
Background: -
There are several display options currently available, which are capable of displaying higher capacity of information. Popular displays are such as video walls and huge LED screens, which display specific information on screen layouts where the specific information relates to the industry they are being used in. For e.g. in a Network Operation Center (NOC), a video wall is used to display various network related information, performance statistics, maps, real time major and critical events in the form of Dashboards which helps engineers in the NOC take quick actions in case of emergency situations and therefore, results in easier monitoring.
However, there are several limitations associated with aforementioned displays such as restricted space for multiple display, therefore only limited information is visible and only one screen layout is visible at all times.
Conventionally known art offers a solution to such limitations, wherein screen layouts are switched and displayed. However, such switch of screen layouts requires a server for each screen layout and corresponding hardware. So, if we have three screen layouts to be displayed, we require three servers and their respective peripherals for such switching to take place. Additional hardware as required makes implementation of conventional art costly and cumbersome, owing to the greater amount of equipment involved.
Further, there is a time delay between display of each screen layout in conventional art. In addition, there is no check regarding the suitability of display of a screen layout. Even if a screen layout is not suitable for display, it is displayed by the conventional art, which results in an undesired blank screen on the video wall.
Summary: -
Embodiments of the present disclosure refer to automatic switch of screen layouts and specifically, but not limited to, in a video wall. An embodiment of the present disclosure teaches a method for automated switch of screen layouts comprising acquiring object information for each screen layout, processing acquired object information as per user requirements, storing processed object information in a data storage array, evaluating suitability of each screen layout for display and displaying and automatically switching screen layouts as per evaluation and stored object information. In accordance with an embodiment of the disclosure, a data storage array is an array list. According to yet another embodiment, the object information is such as handler content of an application running on a screen layout.
According to an embodiment of the disclosure, processing acquired object information as per user requirements comprises specifying display time of each screen layout and prioritizing each screen layout.
According to yet another embodiment of the disclosure, displaying and automatically switching screen layouts comprises automatically skipping display of a screen layout, which is not suitable for display. Not suitable for display is such as the application running on screen layout is hung and the application running on screen layout is refreshing.
An embodiment of the present disclosure teaches a system for automated switch of screen layouts comprising an acquisition unit, a processor coupled to the acquisition unit, a data storage array coupled to the processor, an evaluation unit coupled to the data storage array and at least one display interface coupled to the evaluation unit. The acquisition unit is configured to acquire object information for each screen layout where the object information is such as handler content of an application running on a screen layout.
According to an embodiment of the disclosure, the processor is configured to process the acquired object information as per user requirements such as display time of each screen layout and priority of each screen layout.
According to yet another embodiment of the present disclosure, the data storage array is an array list configured to store the processed object information. In another embodiment, the evaluation unit is configured to evaluate suitability of a screen layout for display. In another embodiment, the display interface is configured to display and automatically switch screen layouts as per output of the evaluation unit and stored object information. The display interface is configured to automatically skip display of a screen layout, which is not suitable for display wherein not suitable for display is such as application running on screen layout is hung, and application running on screen layout is refreshing.
Yet another embodiment refers to a video wall system comprising an acquisition unit, a processor coupled to the acquisition unit, a data storage array coupled to the processor, an evaluation unit coupled to the data storage array and at least one display interface coupled to the evaluation unit.
Brief Description of drawings: -
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in
which the reference number first appears. The same numbers are used
throughout the drawings to reference like features and components.
Figure 1 illustrates a flow diagram representation of a method for automatic
switch of screen layouts according to an embodiment of the present disclosure.
Figure 2 illustrates a block diagram representation of a system for automatic
switch of screen layouts according to an embodiment of the present disclosure.
Figure 3 illustrates a block diagram representation of a system for automatic
switch of screen layouts according to an example of the embodiment of the present disclosure.
Detailed description: -
The following discussion provides a brief, general description of a suitable
computing environment in which various embodiments of the present disclosure
can be implemented. The aspects and embodiments are described in the general
context of computer executable mechanisms such as routines executed by a
general purpose computer e.g. a server or personal computer. The embodiments
described herein can be practiced with other system configurations, including
Internet applications, hand held devices, multi-processor systems,
microprocessor based or programmable consumer electronics, network PCs, mini computers, mainframe computers and the like. The embodiments can be embodied in a special purpose computer or data processor that is specifically programmed configured or constructed to perform one or more of the computer executable mechanisms explained in detail below.
Exemplary embodiments now will be described with reference to the accompanying drawings. The disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey its scope to those skilled in the art. The terminology used in the detailed description of the particular exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting. In the drawings, like numbers refer to like elements.
The specification may refer to “an”, “one” or “some” embodiment(s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.
As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations and arrangements of one or more of the associated listed items.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The figures depict a simplified structure only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown. The connections shown are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the structure may also comprise other functions and structures. It should be appreciated that the functions, structures, elements and the protocols used in communication are irrelevant to the present disclosure. Therefore, they need not be discussed in more detail here.
Also, all logical units described and depicted in the figures include the software and/or hardware components required for the unit to function. Further, each unit may comprise within itself one or more components which are implicitly understood. These components may be operatively coupled to each other and be configured to communicate with each other to perform the function of the said unit.
Embodiment of a method for automatic switch of screen layouts according to the present disclosure is described in Figure 1. The method is illustrated as a collection of blocks in a logical flow graph, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. The order in which the process is described is not intended to be
construed as a limitation, and any number of the described blocks can be combined in different orders to implement the process, or an alternate process.
‘Screen layout/s’ refers to the screen, window and page displaying the application running on a computer, server, processor. However, a person skilled in the art would appreciate that the present disclosure is not limited only to the above mentioned definition.
Figure 1 illustrates a method for automatic switch of screen layouts in accordance with an embodiment of the present disclosure. Object information for each screen layout is acquired 101 and processed as per user requirements 102. Object information according to an example of the embodiment refers to handler content of an application in the DLL (Dynamic Link Library), where the application is being displayed on the screen layout. User requirements according to an example of the embodiment refer to specifying display time of each screen layout and prioritizing each screen layout by the user himself. The processed object information is then stored in a data storage array 103 where according to an example of the embodiment, the data storage array is an array list. When a screen layout is to be displayed, its suitability for display is first evaluated 104 and then the screen layouts are displayed and automatically switched as per evaluation and stored object information 105.
According to an embodiment of the disclosure, displaying and automatically switching screen layouts comprises automatically skipping display of a screen layout which is not suitable for display. In an example of the embodiment, not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
Figure 2 teaches a system for automatic switch of screen layouts according to an embodiment of the present disclosure. The system comprises an acquisition unit
201, a processor 202 coupled to the acquisition unit, a data storage array 203 coupled to the processor, and evaluation unit 204 coupled to the data storage array and a display interface 205 coupled to the evaluation unit.
The acquisition unit 201 is configured to acquire object information for each screen layout. According to an example of the embodiment, the object information is handler content of an application in the DLL (Dynamic Link Library), where the application is being displayed on the screen layout. According to an embodiment, the processor 202 is configured to process the acquired object information as per user requirements such as display time of each screen layout and priority of each screen layout. The processed object information is then stored in the data storage array 203 where according to an example of the embodiment, the data storage array is an array list. The evaluation unit 204 is configured to evaluate suitability of a screen layout for display. Upon evaluation, the evaluation unit retrieves the object information of the screen layout from the data storage array 203 and forwards it along with its evaluation to the display interface 205. The display interface 205 is configured to display and automatically switch screen layouts as per output of the evaluation unit and stored object information. According to an embodiment of the disclosure, the display interface 205 is configured to automatically skip display of a screen layout, which is not suitable for display. As an example, not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
For e.g. if a screen layout is for an application which is refreshing, the display interface would skip that screen layout altogether instead of displaying a blank screen and move to the next screen layout.
Example of an Embodiment
Figure 3 illustrates a system for automatic switch of screen layouts according to an example of the embodiment of the present disclosure. The example pertains to a video wall, which is used to display information. The system comprises a server 301, which comprises the applications being run and displayed on screen layouts. For better illustrations, according to another example, the applications running on the server 301 are a Flash presentation, a PDF document and Internet explorer. The acquisition unit 302, is configured to acquire the object information of each screen layout wherein the applications are running. According to an example, the object information is handler content of each an application in the DLL (Dynamic Link Library). Therefore, the acquisition unit acquires handler content for Flash, PDF as well as the Internet explorer.
The acquired handler content is then processed by a processor 303 wherein the processor comprises a timer 303a. A user is equipped to program the timer according to his preference and the object information is accordingly processed and stored in an array list 304. According to yet another example, the user specifies through the timer that all screen layouts are to be displayed for 2 minutes each. Accordingly, the Flash presentation, the PDF document and the Internet explorer are displayed for 2 minutes each and automatically switched to the next screen layout.
When an application runs, the screen layout is to be displayed on the display interface which according to the example is a video wall 305. However, the screen layouts are first evaluated for their suitability for display by an evaluation unit 304. Upon evaluation, the evaluation unit 304 retrieves the object information of the screen layout from the array list 303 and forwards it along with its evaluation to the video wall 305.
The video wall 305 is configured to display and automatically switch screen layouts as per output of the evaluation unit and stored object information.
According to an embodiment of the disclosure, the video wall 305 is configured to automatically skip display of a screen layout, which is not suitable for display. As an example, not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
Therefore, according to the example, Flash presentation is first displayed on the video wall 305, after 2 minutes, the screen layout automatically switches and the PDF document is displayed. After another 2 minutes, the screen layout automatically switches and the internet explorer is displayed. If the internet explorer is refreshing when it is to be displayed, the evaluation unit identifies its status and accordingly the video wall automatically skips the internet explorer screen layout and automatically switches to the Flash presentation.
According to another example of the embodiment, during processing of the handler content, the user also specifies priority of each screen layout displaying an application along with setting the timer for 2 minutes. PDF document gets the highest priority, then Internet Explorer and then the Flash presentation. Then during display of screen layouts on the video wall 305, the PDF document is displayed first, after 2 minutes, automatically the Internet Explorer is displayed and after another 2 minutes, the screen layout automatically switches to the Flash presentation.
A person skilled in the art would appreciate that the examples of applications taken are only for illustrations and descriptive purposes. The present disclosure, is not limited to the same.
As per the embodiments and examples of the embodiments described above, the present disclosure requires only one server for display of screen layouts as opposed to the conventional art where each screen layout requires a separate server for each application. Accordingly, the present disclosure ensures lower
cost and lesser hardware requirement for the execution of display of screen layouts.
Further, owing to storage of object information in the data storage array and its consequent retrieval during display of the screen layouts, time delay involved in automatic switching of screen layouts is considerably lowered. In addition, due to the automatic skip of screen layouts not suitable for display, the present disclosure offers seamless and efficient switching of screen layouts.
Embodiments of the present disclosure are applicable to, but not limited, to all genres of industry which involve display of information such as TV studios, museums, art galleries, clubs, theme parks, corporate displays, NOC network operation centers, military command centers, security monitoring centers etc. The embodiments are also applicable to huge LED screens which are another popular display used.
As will be appreciated by one of skill in the art, the present invention may be embodied as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a "circuit" or "module." Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.
Furthermore, the present invention was described in part above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention.
It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and schematic diagrams of Figures 1-3 illustrate the architecture, functionality, and operations of some embodiments of methods, systems, and computer program products for centralized and controlled printing and administration. In this regard, each block may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in
other implementations, the function(s) noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending on the functionality involved.
In the drawings and specification, there have been disclosed exemplary embodiments of the invention. Although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention being defined by the following claims
We claim: -
1. A method for automated switch of screen layouts comprising: -
a. acquiring object information for each screen layout;
b. processing acquired object information as per user requirements;
c. storing processed object information in a data storage array;
d. evaluating suitability of each screen layout for display; and
e. displaying and automatically switching screen layouts as per
evaluation and stored object information.
2. A method as claimed in claim 1 wherein processing acquired object
information as per user requirements comprises: -
a. specifying display time of each screen layout; and
b. prioritizing each screen layout.
3. A method as claimed in claim 1 wherein displaying and automatically switching screen layouts comprises automatically skipping display of a screen layout which is not suitable for display.
4. A method as claimed in claim 3 wherein not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
5. A method as claimed in claim 1 wherein the data storage array is an array list.
6. A method as claimed in claim 1 wherein the object information is such as handler content of an application running on a screen layout.
7. A system for automated switch of screen layouts comprising: -
a. an acquisition unit;
b. a processor coupled to the acquisition unit;
c. a data storage array coupled to the processor;
d. an evaluation unit coupled to the data storage array; and
e. at least one display interface coupled to the evaluation unit.
8. A system as claimed in claim 7 wherein the acquisition unit is configured to acquire object information for each screen layout.
9. A system as claimed in claim 7 wherein object information is such as handler content of an application running on a screen layout.
10. A system as claimed in claim 7 wherein the processor is configured to process the acquired object information as per user requirements such as display time of each screen layout and priority of each screen layout.
11. A system as claimed in claim 7 wherein the data storage array is an array list configured to store the processed object information.
12. A system as claimed in claim 7 wherein the evaluation unit is configured to evaluate suitability of a screen layout for display.
13. A system as claimed in claim 7 wherein the display interface is configured to display and automatically switch screen layouts as per output of the evaluation unit and stored object information.
14. A system as claimed in claim 7 wherein the display interface is configured to automatically skip display of a screen layout which is not suitable for display.
15. A system as claimed in claim 14 wherein not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
16. A video wall system comprising: -
a. an acquisition unit;
b. a processor coupled to the acquisition unit;
c. a data storage array coupled to the processor;
d. an evaluation unit coupled to the data storage array; and
e. at least one display interface coupled to the evaluation unit.
17. A video wall system as claimed in claim 16 wherein the acquisition unit is configured to acquire object information for each screen layout.
18. A video wall system as claimed in claim 16 wherein object information is such as handler content of an application running on a screen layout.
19. A video wall system as claimed in claim 16 wherein the processor is configured to process the acquired object information as per user requirements such as display time of each screen layout and priority of each screen layout.
20. A video wall system as claimed in claim 16 wherein the data storage array is an array list configured to store the processed object information.
21. A video wall system as claimed in claim 16 wherein the evaluation unit is configured to evaluate suitability of a screen layout for display.
22. A video wall system as claimed in claim 16 wherein the display interface is configured to display and automatically switch screen layouts as per output of the evaluation unit and stored object information.
23. A video wall system as claimed in claim 16 wherein the display interface is configured to automatically skip display of a screen layout which is not suitable for display.
24. A video wall system as claimed in claim 23 wherein not suitable for display is such as application running on screen layout is hung and application running on screen layout is refreshing.
| # | Name | Date |
|---|---|---|
| 1 | 1262-MUM-2010- FORM 1 (16-04-2010).pdf | 2010-04-16 |
| 2 | 1262-MUM-2010- CORRESPONDENCE (22-04-2010).pdf | 2010-04-22 |
| 3 | Form-3.pdf | 2018-08-10 |
| 4 | Form-18(Online).pdf | 2018-08-10 |
| 5 | Form-1.pdf | 2018-08-10 |
| 6 | ABSTRACT 1.jpg | 2018-08-10 |
| 7 | 1262-MUM-2010-POWER OF ATTORNEY(19-7-2010).pdf | 2018-08-10 |
| 8 | 1262-MUM-2010-FORM 1(19-7-2010).pdf | 2018-08-10 |
| 9 | 1262-MUM-2010-CORRESPONDENCE(19-7-2010).pdf | 2018-08-10 |
| 10 | 1262-MUM-2010-FER.pdf | 2019-01-23 |
| 11 | 1262-MUM-2010-AbandonedLetter.pdf | 2020-01-30 |
| 12 | 1262-MUM-2010- ACKNOWLEDGEMENT RECEIPT.pdf | 2022-12-07 |
| 1 | Search_11-01-2019.pdf |