CLIAMS:We claim:
1. A web browser for providing customized interface for web interactions, the web browser configured to:
store instructions for each web-page for which customized interface is desired to be provided; and
display customized interface based on the instruction specific to a web-page displayed by the web browser.
2. The web browser of claim 1 further configured to:
verify whether the web-page satisfies pre-configured criteria set forth in the instruction specific to the web-page; and
display the customized interface upon the web-page satisfying the pre-configured criteria.
3. The web browser of claim 1 further configured to:
verify whether the web-page satisfies pre-configured criteria set forth in the instruction specific to the web-page; and
send error log if the web-page does not satisfy at least one of one or more of the pre-configured criteria.
4. The web browser of claim 1 further configured to:
store information corresponding to a plurality of entities, wherein the stored information corresponding to an entity among the plurality of entities relates to the relationship between web-pages of the entity; and
send an error log upon detecting a change in the relationship.
5. The web browser of claim 1 further configured to:
store information corresponding to a plurality of entities, wherein the stored information corresponding to an entity among the plurality of entities relates to the relationship between web-pages of the entity;
detect a change in relationship;
attempt to correlate a web-page to be or being displayed by the web browser with one of expected web-page(s) of the entity based on the stored instructions; and
display customized interface upon successful correlation.
6. The web browser of claim 1 further configured to:
store information corresponding to a plurality of entities, wherein the stored information corresponding to an entity among the plurality of entities relates to communication methodologies adopted by the entity;
identify communication received from the entity by a terminal on which the web browser is executed based on the communication methodologies adopted by the entity;
fetch relevant data from the received communication based on the communication methodologies adopted by the entity; and
auto fill a field configured to receive the relevant data.
7. The web browser of claim 6, wherein the communication is received as one or more of email and Short Messaging Service, and the relevant data is a one-time password.
8. The web browser of claim 1, wherein an action performed using the customized interface results in performance of a plurality of action on one or more web-pages.
9. The web browser of claim 1, wherein the customized interface displays an enlarged view of a location on the web-page.
10. The web browser of claim 1, wherein the customized interface displays a location on the web-page by auto scrolling through the web-page.
11. The web browser of claim 1, wherein the customized interface is provided as an overlay over the web-page.
12. The web browser of claim 1, wherein the customized interface is configured to receive input.
13. The web browser of claim 1, wherein:
at least one web-page associated with an entity enables authentication; and
at least one web-page among the remaining web-page(s) associated with the entity is accessible upon successful authentication.
14. The web browser of claim 1, wherein:
multiple web-pages are associated with an entity among a plurality of entities;
each of the entities are associated with multiple web-pages;
at least one web-page associated with its respective entity enables authentication; and
at least one web-page among the remaining web-page(s) associated with the respective entity is accessible upon successful authentication.
15. The web browser of claim 1, wherein the customized interface comprises a keypad for entering a password, wherein the keypad is operable to show or hide password within the keypad. ,TagSPECI:The following specification particularly describes the invention and the manner in which it is to be performed.

BACKGROUND
Field
[0001] The subject matter in general relates to web browser. More particularly, but not exclusively, the subject matter relates to web browser for providing customized interface for web interactions.
Discussion of related field
[0002] A web browser is a software application that enables users to access a wide variety of information resources on the World Wide Web. Conventionally, web browsers were accessed using desktop computers, laptops and notebook computers. With the advent of smart phones, tablets and other handheld touch screen devices, users have the convenience of accessing a wide variety of information on the go, although they face inconvenience while browsing through the page, navigating across different pages and selecting options within a page, among others due to sensitivity of the touch screen and limited screen size.
[0003] To facilitate web interaction on mobile devices, browsers on these devices attempt to provide altered web-page layouts. These interfaces or layouts are generic in nature, wherein the browser applies same rule for all the web-pages by reading the HTML code of the web-page and display interface according to the HTML code of the web-page. However, it has been observed that such generic interfaces may not provide a time-efficient solution for navigating through the web-page, which may require carrying out multiple gestures to find field of interest on the web-page. During the process of carrying out such gestures to locate the field of interest, there exists possibility of selecting a field that is not particularly of interest unintentionally due to sensitivity of the touch screen and limited screen size.
[0004] Further, the browsers rely on tags provided to input fields on a web-page to invoke a digital keypad that enables a user to provide input. However, it has been observed that some of the input fields may not be appropriately tagged, thereby requiring the user to switch between keypads displaying numeric, alphabetic and special characters, thereby adversely affecting user experience.
[0005] It has also been observed that users experience inconvenience when the input field in a web-page that requires entering a one-time password, which may be sent to the user via SMS. In such use cases, typically the user will have to access the SMS, locate the one-time password in the SMS, remember the one-time password and enter the one-time password in the input field.
[0006] In light of the foregoing discussion, there may be a need for a technique to improve web interactions while using a browser on a mobile device.

SUMMARY
[0007] In an embodiment a web browser is provided. The web browser provides customized interface for web interactions. The web browser may be configured to store instructions for each web-page for which customized interface is desired to be provided, and display customized interface based on the instruction specific to a web-page displayed by the web browser.

BRIEF DESCRIPTION OF DRAWINGS
[0008] Embodiments are illustrated by way of example and not limitation in the Figures of the accompanying drawings, in which like references indicate similar elements and in which:
[0009] FIG. 1A illustrates a web browser 100 displaying a customized interface 102 for entering User ID and Password;
[0010] FIG. 1B illustrates an example prior-art interface 103 of the same web-page displayed in FIG. 1A by a conventional web browser;
[0011] FIG.2 is an exemplary block diagram of the web browser 100 for providing customized interface for web interactions;
[0012] FIGs. 3A and 3B illustrate customized interfaces provided for a login page of a website;
[0013] FIG. 4 illustrates customized interface for selecting two-factor authentication option in a webpage of a website;
[0014] FIG. 5 is a flowchart of an exemplary method for providing customized interface for web interactions;
[0015] FIG. 6 is a flowchart of an exemplary method followed upon encountering an unexpected web-page; and
[0016] FIG. 7 is a flowchart of an exemplary method for auto processing of OTP.

DETAILED DESCRIPTION
[0017] A browser configured to enable customized interface for web interactions is provided. The browser stores specific instructions for each web-page for which customized interface is desired to be provided. The browser further checks whether the web-page to be or being displayed satisfies pre-configured criteria as set forth in the instructions specific to that web-page. Upon the pre-configured criteria being satisfied, the browser displays customized interface for the web-page. In case one or more pre-configured criteria are not satisfied, the browser generates error report and submits error report to a server. Further, in case one or more pre-configured criteria are not satisfied, the browser may display a generic interface and refrain from displaying customized interface as per the instructions specific to the web-page.
[0018] Further, the browser stores information corresponding to relationship between web-pages of a website. Error report is generated and submitted to the server when a change in relationship between web-pages is identified.
[0019] Furthermore, the browser stores information corresponding to communication methodologies adopted by websites to communicate "one-time password". Based on the communication methodologies, the browser fetches relevant data automatically from communication sent by the website to the terminal which is being used to access the website. The fetched relevant data will be automatically filled in its relevant input field.
[0020] The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments, which may be herein also referred to as “examples” are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical, and design changes can be made without departing from the scope of the claims. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined by the appended claims and their equivalents.
[0021] In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.
[0022] Referring to the figures, and more particularly to FIG. 1A, a web browser 100 is displaying a customized interface 102 for web interaction. In the customized interface 102, the “User ID” and “Password” fields are prominently displayed, the cursor is in the “User ID” field, which is the first input filed in the displayed web-page. The web browser 100 provides such customized interface 102 using the instructions stored by it specific to that web-page. On the other hand FIG. 1B illustrates an example prior-art interface 103 of the same web-page displayed by a conventional web browser. In the prior-art interface 103, the user may have to use a gesture to zoom into the “User ID” field and then begin to enter his user ID.
[0023] Referring to FIG.2, a block diagram of the web browser 100 for providing customized interface for web interactions is exemplified. The web browser 100 may include a rule engine 104, which may include a rules database 106, an execution module 110, an error reporting module 112 and a customized interface (UI/UX) database 114. The web browser may communicate with a server 116 at a remote location.
[0024] The rules database 106 may include rules corresponding to a plurality of entities or websites, which may have multiple web-pages. The rules database 106 may include instruction 120 for each web-page of a website/entity among the multiple web-pages of the website to which customized interface may be desired to be provided. The instruction 120 for a web-page may include pre-configured criteria for the web-page. The criteria, for example, may be to verify whether a web-page being loaded on the web browser 100 has an expected URL. Another example may be to verify whether a web-page being loaded on the web browser 100 has an expected Document Object Model (DOM). Another example may be to verify whether a web-page being loaded on the web browser 100 has expected field(s).
[0025] Further, the instruction 120 corresponding to a web-page may include instruction to display a customized interface upon the web-page satisfying the pre-configured criteria.
[0026] Furthermore, the instruction 120 corresponding to a web-page may include instruction to display generic interface provided by the terminal upon not satisfying the pre-configured criteria. The instructions 120 may be specific to each web-page.
[0027] Further, the rules database 106 may include information corresponding to relationship between the multiple web-pages 122 of a website. The stored information may include sequence of web-pages of the website, and in addition may include information corresponding to nature of exchange of data between web-pages, among others that facilitates transaction. Further, the rules database 106 may store information to send an error log upon detecting a change in the relationship. At least one or more of the web-pages (ex: login page) associated with an entity/website may enable authentication. At least one web-page among the remaining web-page(s) associated with the respective entity may be accessible upon successful authentication.
[0028] The rules database 106 may be configured to store information corresponding to a plurality of entities/websites, wherein the stored information corresponding to an entity among the plurality of entities relates to communication methodologies 124 adopted by the entity. Every website may have its own communication methodologies to communicate (outside of the website) with the user accessing the website. The rules database106 may be further configured to store instructions to identify communication received from the entity by a terminal on which the web browser 100 may be executed, based on the communication methodologies 124 adopted by the entity. The communication may be received as one or more of email and Short Messaging Service. The communication sent by the websites may include voice message, image, or any other methodologies of transmission of authentication data. Information corresponding to communication methodologies adapted by each of the websites may be stored, and can include type of communication, format of communication and identity of communication sender, among others.
[0029] Furthermore, the rules database 106 may be configured to receive updates from the server 116. The updates may include information about relationship between web-pages, communication methodologies, pre-configured criteria for web-pages and instructions for web-pages, among others.
[0030] The execution module 110 may be configured to execute the instruction 120 specific to a web-page when the web-page is accessed by the web browser 100. Upon satisfying pre-configured criteria as set forth in the instruction 120, the execution module 110 may be configured to display a customized interface as per the instruction 120 specific to that web-page.
[0031] In case the execution module 110 identifies that one or more pre-configured criteria as set forth in the instruction 120 for the web-page are not satisfied, the execution module 110 may generate an error log, and facilitate sending of the error log to the server 116.
[0032] The execution module 110 further identifies whether the sequence of navigation from one web-page to another is as per the relationship between web-pages 122. In case the execution module 110 identifies a change in sequence, then the execution module 110 may generate an error log, and facilitate sending of the error log to the server 116.
[0033] In an embodiment, the execution module 110 upon encountering a web-page that it was not expecting based on the relationship between web-pages 122, attempt is made to correlate the web-page to be or being displayed by the web browser 100 with one of remaining expected web-page(s) of the entity based on the stored information/instructions 120, 122. In case execution module 110 is successful in correlating the web-page to an expected web-page, the execution module 110 enables display of customized interface as per the instruction specific to the correlated web-page.
[0034] The error reporting module 112 is configured to receive error log from the execution module 110. The error reporting module 112 may be configured to send error log to the server 116. The error report/log may include one or more of changes in URL and/or the DOM of the web-page, information corresponding to the pre-configured criteria not being met, format of the communication (OTP sent by the website being accessed) that was not recognized by the browser 100 due to lack or mismatch of information about the format of the communication, and change in relationship between web-pages that may have occurred due to addition of a web-page, deletion of a web-page or change in sequence of navigation.
[0035] The customized interface database 114 may be configured to store media or interfaces for the multiple web-pages of the plurality of websites. Based on the instruction 120 specific to the web-page being accessed, the execution module 110 may fetch media/items/objects from the customized interface database 114 and display as overlaid interface on the web browser 100.
[0036] The specific instructions 120 for a web-page for providing customized interface may include one or more of auto-scrolling through the web-page to display the field of interest of the web-page being accessed, enlarging the displayed field of interest or location of the web-page being accessed and displaying media/items/objects. The customized interface (media/items/objects) may be configured to display as an overlay over the web-page being displayed. The customized interface may further be configured to receive input.
[0037] The server 116 receives error log/report from the error reporting module 112 of the web browsers 100. The error logs at the server 116 may be accessed to develop updates to address reported errors. The server 116 can communicate the updates to the web browsers 100.
[0038] The server 116, on receiving error report of a web-page may send instruction to web browsers 100 to disable providing of customized interface to that/those web-page(s) for which error report was generated. Providing of customized interface may be disabled across multiple web browsers 100 for such web-pages until an update is provided for that/those web-page(s) for which error report was generated.
[0039] Referring to FIG. 5, an exemplary method for providing customized interface for web interactions is provided. A user wishing to carry out financial transaction using a touch-screen terminal using the web browser 100 may request a login page of a banking website. At step 502, the rule engine 104 of the web browser 100 verifies whether the web-page (login page of a banking website) satisfies pre-configured criteria set forth in instruction specific to the web-page. The pre-configured criteria may include matching of the URL of the web-page with an expected URL and matching of the DOM of the web-page with an expected DOM. If one or more pre-configured criteria is not satisfied (step 504), then at step 508, the execution module 110 may generate error report/log for the web-page that didn’t satisfy one or more pre-configured criteria. The error report may be communicated to the server 116. The generated error report may include non-sensitive information such as for example one or more of, URL, DOM of the current web-page and information about the criteria that was not satisfied, among others. Additionally, upon non-satisfaction of one or more criteria, the web browser 100 may execute instructions to be carried out when the web-page doesn’t satisfy pre-configured criteria set forth. The instructions may include disabling customized interface and displaying generic interface provided by the terminal on which web browser 100 is executed (step 510). Example of one such generic interface for a login page is illustrated in FIG. 1B.
[0040] On the other hand, if the pre-configured criteria specific to the web-page is/are satisfied (step 504), then at step 506, a customized interface for the web-page is provided on the web browser 100 as per the instructions specific to the web-page. Further, the above described process is carried out for any web-page that is subsequently requested (steps 512, 514) by the web browser 100. On the other hand, the operation of the web browser 100 may be terminated or the user may navigate to a website for which the web browser 100 does not have instructions specific to the website, in which case the next logic step is carried out (step 514).
[0041] The customized interface, for example, can include providing an enlarged view of an area of interest on the web-page, as illustrated in FIG. 1A, automatically (in other words, automatically zooming without a user input to zoom).
[0042] The customized interface, for example, can include auto-scrolling to a location on the web-page (in other words, automatically scrolling without a user input to scroll).
[0043] The customized interface, for example, can include providing an interface as an overlay over the web-page. The interface can be an input interface, such as, a variety of keypad and selection interface, among others.
[0044] The execution module 110 may fetch media/items from the customized interface database 114 as per the instructions specific to the web-page and display as an overlaid customized interface in the web browser 100.
[0045] Referring to FIG. 3A, a customized interface 302 is illustrated. The customized interface 302 is provided for a login page of a website, wherein the login page is configured to receive a User ID and password. The execution module 110 applies instructions specific to the login page and provides the customized interface 302. The customized interface 302 may display a location (User ID and password fields) on the web-page by auto scrolling through the login page. Further, the User ID box and password box are auto zoomed to provide a better view of the boxes. A keypad is overlaid over the login page. The credentials of the user ID input field of the login page may include only numbers, therefore the keypad 304 provided may include numeric keypad. Other convenient features such as “next” button to navigate from the user ID input field to the password input field and clear button, among others are provided.
[0046] The user, upon selecting the “next” button, is provided by a different keypad as illustrated in FIG. 3B. The password field of the login page may include combination of uppercase and lowercase alphabets, numerical characters and special characters. Therefore the customized interface/keypad 306 provided may include uppercase and lowercase alphabets, numerical characters and special characters keypad. Other convenient features such as show password button, previous button, next button, clear button and approve button, among others are provided. The keypad may be operable to show or hide password within the keypad. For example, the show password button, upon selection, results in showing of the password during input or subsequent to input. This facilitates the user to check whether the credentials entered in the password field are correct or incorrect before submitting the entered credentials. The approve button may be selected to submit the user ID and the password, instead of the user scrolling through the web-page to find the submit button on the web-page.
[0047] Referring to FIG. 6, at step 602, the web browser 100 may receive request for a web-page of a website. At step 604, the rule engine 104 of the web browser 100 verifies whether the requested web-page is as per the relationship between web-pages 122 of the website. The verification may include matching sequence of the requested web-page with an expected sequence of web-pages of the website. If the relationship is not satisfied (step 606), then at step 608, the execution module 110 may generate error report/log for the requested web-page that didn’t satisfy the relationship between web-pages 122 of the website. The error report may be communicated to the server 116. The generated error report may include non-sensitive information such as for example, one or more of, URL, DOM of the requested web-page and information about the relationship that was not satisfied, among others. Further at step 610, upon non-satisfaction of the relationship, the web browser 100 may attempt to correlate the requested web-page with one of remaining web-pages of the website for which specific instructions are present. If the correlation is unsuccessful (step 612), then the web browser 100 may generate error report/log reporting such unsuccessful correlation. The error report may be communicated to the server 116. At step 616, upon unsuccessful correlation, the web browser may continue providing generic interface for the requested web-page due to lack of specific instructions for the requested web-page.
[0048] On the other hand, if the requested web-page is as per the relationship between web-pages 122 of the website (step 606), then at step 614, the web browser 100 follows the instructions specific to the requested web-page (refer to FIG. 5). Likewise, if the requested web-page successfully correlates with one of the remaining web-pages of the website (step 612), then at step 614, the web browser 100 follows the instructions specific to the requested web-page (refer to FIG. 5).
[0049] Referring to FIG. 4, the web browser 100 provides customized interface to select an option for “two-factor” authentication, which may include “Password” and “One Time Password”. Referring to FIG. 7, at step 702, customized interface is provided by the web browser 100 to select an option which may lead to communication of One Time Password (OTP).
[0050] The customized interface, for example, can include providing an enlarged view of an area of interest (option to select “two-factor” authentication type) on the web-page, as illustrated in FIG. 4, automatically (in other words, automatically zooming without a user input to zoom).
[0051] The customized interface, for example, can include auto-scrolling to a location (option to select “two-factor” authentication type) on the web-page (in other words, automatically scrolling without a user input to scroll).
[0052] The customized interface, for example, can include providing an interface (option to select “two-factor” authentication type) as an overlay over the web-page. The interface can be an input interface for selection, such as, a “password” and “OTP”, among others. As seen in the illustration, apart from the website providing options as radio buttons for selection, the customized interface, as an overlay provides two buttons (password and OTP) for selection, which makes selection of an option more convenient.
[0053] At step 704, customized interface may receive the selected option (for example, request for OTP) and communicate request for OTP to the web-page of the website to generate an OTP. At step 706, the browser 100 may refer to the rule database 106 to identify the communication methodologies 124 adopted by the website for said selection to communicate OTP to users.
[0054] At step 708, the web browser 100 may verify whether the terminal being used to access the web browser 100 has received any communication as per one or more alternatives present in the communication methodologies 124 adopted by the website. The communication may be received as one or more of email and Short Messaging Service. The communication sent by the website may include text, voice message, image, or any other methodologies of transmission of authentication data. The web browser 100 may verify whether terminal has received any communication based on one or more identities (sender ID) of the communication sender. If the communication is not received in the terminal (step 710), then at step 712, the browser 100 may allow the user of the terminal to take action. The action taken by the user of the terminal, for example, can include requesting the web-page to send OTP once again. The action taken by the user of the terminal, for example, can include accessing the OTP after receiving OTP in a device other than the terminal used to execute the browser 100. The action taken by the user of the terminal, for example, can include accessing OTP manually from the communication that was received in the terminal, wherein identity of communication sender that sent the communication was not recognized by the browser 100 due to lack or mismatch of information about the communication methodologies 124 adopted by the website. The execution module 110 may generate an error report/log. The reported error may be communicated to the server 116.
[0055] If the communication is received in the terminal (step 710), then at step 714, the web browser 100 may verify whether the received communication is as per a format among one or more formats present in the communication methodologies 124 of the website. If the communication received is not as per the recognizable format (step 716), then at step 712, the browser may allow the user of the terminal to take action. The action taken by the user of the terminal, for example, includes opening the received communication in the terminal manually, input of OTP in the web browser 100 of the terminal and submitting of the entered OTP. The execution module 110 may generate an error report/log. The reported error may be communicated to the server 116. The reported error may include the format of the communication that was not recognized by the browser 100 due to lack or mismatch of information about the format of the communication (sensitive data may not be included in the error report).
[0056] On the other hand, if the communication received in the terminal is as per the recognizable format (step 716), then the web browser 100 automatically fetches relevant data from the received communication (step 718). The fetched relevant data may be OTP. Subsequent to fetching OTP, the browser 100 may auto fill the obtained OTP (step 720).
[0057] The web browser 100 may be configured such that an action performed using the customized interface results in performance of a plurality of action on one or more web-pages. For example, conventionally, once a user selects (action number 1) the OTP option, the user is directed to a next page where the user selects a button (action number 2) instructing the website to generate OTP. On the other hand, in the web browser 100 selection of the OTP option by the user also results in instruction automatically provided to the website to generate the OTP.
[0058] It shall be noted that the processes described above is described as sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, or some steps may be performed simultaneously.
[0059] Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the system and method described herein. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
[0060] Many alterations and modifications of the present invention will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. It is to be understood that the description above contains many specifications; these should not be construed as limiting the scope of the invention but as merely providing illustrations of some of the personally preferred embodiments of this invention. Thus the scope of the invention should be determined by the appended claims and their legal equivalents rather than by the examples given.