JP2003532129A - How to customize and render selected data fields - Google Patents

Abstract

(57) Abstract Data elements selected and identified by signatures extracted from mathematical regular expressions of data are of interest to queryers by a system adapted to access elements through reference by signature. A method is provided that can be rendered via a suitable language translator. This language translator of interest may include a text-to-speech translator, a stored audible representation mapped to its elements, and a simplified text representation programmed to match the HTML representation. As another feature of the invention, the method includes identifying the selected element, customizing the selected element for rendering appropriate to the intended context, and selecting and customizing the key appropriate language translator. It further includes further specification of the elements.

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD OF THE INVENTION

The present invention relates to rendering customized data in different formats, including audible and limited visual formats. The invention particularly relates to rendering of Hypertext Markup Language (HTML) data in another format other than its source format, such as an audio or visual format.

[0002]

[Prior art]

Currently, a great deal of valuable information is available in HTML format.
However, HTML is primarily designed for access in a particular visual context, i.e. by a type of graphical user interface designed for use by a web browser.

[0003]

[Problems to be Solved by the Invention]

There is a need to be able to access HTML data by another interface and reader. The invention described herein relates to an important feature of that need.

[0004]

[Means for Solving the Problems]

According to the present invention, in a computer network system, a data element selected and identified by a signature extracted from a mathematical regular representation of the data is queried by a system adapted to access the element by reference by the signature. A method is provided that can be rendered via a suitable language translator of interest to the. The language translator of interest may include a text-to-speech translator, a stored audible representation mapped to the element, and a simplified text representation programmed to match HTML. As another feature of the invention, the method identifies the selected element, customizes the selected element for rendering appropriate to the intended context, and selects and customizes by an appropriate suitable language translator. It further includes further specification of the element.

In the present invention, it is important to recognize that HTML pages can be represented by regular expressions. It is also recognized that the present invention only requires the element to be selected, the actual value of the element need not be selected, thus allowing the value to be dynamically updated and rendered with the current value. It is an important thing to be done.

[0006]

DETAILED DESCRIPTION OF THE INVENTION

The invention will be better appreciated by reference to the following detailed description and the accompanying drawings. FIG. 1 illustrates a system 10 with a main runtime component and associated components.
A block diagram of 1 is shown. The web page 11 is retrieved from the host web server 12 into a translator 20, which then retrieves the corresponding target language document 21 from the shared persistent store 14, a so-called WML page 23.
And a runtime object 24 is generated. Used by the run-time environment through the run-time engine to extract real-time data from an HTML page because the designer 13 has previously selected some data from the HTML or source language page 11 called "components" 17 A unique signature is automatically generated. The runtime engine 22 interfaces with a telephone server or other rendering server 26, and a user 28 accesses the real-time information requested by the host web server in the format provided by the rendering server 26. At run time, the runtime translator 20 acts like a browser to the host web server 12 as it downloads HTML pages from that site. In a particular embodiment, the translator 20 also retrieves from the shared persistent store 14 a target language script called AML generated for this purpose. For each web page, the corresponding AML script tells the translator how to create the runtime object 24. These runtime objects 24 are provided to the runtime engine 22, which in turn interfaces with the caller. The run-time engine 22 reads the text and prompts the user 28 by telephone or other interface device using text-to-speech or text-to-decrease text technology. Whenever the caller 28 utters, this engine 22 translates the caller's response into text using either voice recognition technology or text-on-nine (herein called T9). To do. The translator 20 can then return the response data from the caller to the host web server 12 for submission, after which the host web server 12 interprets the request and responds to it.

The script encodes the inter-page flow and may be configured to include the URL of the web page so that the translator can request the appropriate web page. In operation, the host web server 12 seems to be connected to it's normal web browser.

In addition to creating the runtime object 24, the runtime translator 20
Can also generate WML files for third party applications that use such files. Callers to audio-enabled sites accessed from the portal can also use the customized applet.

An important feature of run-time behavior is the translation process. The conversion process will be described below. [A. Transformations This section describes how the various components from the previous section are rendered. [A. 1 Transformation: Morphology] The transformation for the sample morphology is shown below. Each input element in this form appears as a "STEP". The step element has a prompt element that informs the user of the nature of this input and an input element that collects the input from the user. Figure 2
Is a flowchart of the sample conversion disclosed herein.

[0010]

[Equation 1]

[Equation 2]

Attributes define the transition from a given step. For example, referring to FIG.
In the first step F1 which is the logon step, the prompt is given to the user.
The transition to step F2 is made by requesting a digit account number and receiving it at the utterance input. In the logon step, the name attribute of the input element, the SignonAccountNumber (SignonAccountNumber), is a "global" variable, which can later be accessed as $ amlvar (SignonAccountNumber). At step F2, the prompt requires a password and a transition is made to step F3 by receiving the input. Step F3 is a list of options that allows the user to select one of the memory options. After selecting an option, the user is taken to the next step F4. The parameter attribute identifies the parameter that needs to be sent to the action URL, and finally the prompt feeds back to the user what has been done. Given the destination URL, the designer and the runtime system can determine the next AML page needed to continue browsing, the flow element defines the transition to the next step.

The recognition grammar specifies the name for the variable it places a value in, eg, X, and the step has a variable name (Startanchor) corresponding to the input. In some cases, these may not be the same, for example if the grammar is shared between many different input steps, they are all coded with different variable names. In that case, the RENAME element will help define the mapping of recognition variable names to step variable names. If the grammar assigns many variables, then one rename element needs to be specified for each of the variables. For example, in the following code segment, all variables are assigned by grammar and they are remapped to variable names used in another example code below:

[Equation 3]

For some reason, an error condition occurs when what the user says is not understood by the (speech) recognition engine. If the onError attribute is not specified, it is processed in the default way: the prompt is repeated several times until recognition is correct. The user may choose to replace the default behavior with his or her own error steps. In the example below, the error step is defined by the user as a global step. The steps define actions in case of various errors. The step is global, i.e. it can be accessed from another subsequent AML page.

[0014]

[Equation 4]

[Equation 5]

[A. 2 Transformation: Table] The table can be read in a number of ways. This section describes two possible methods. One way is to read one row of the table at a time and ask the user if he wants to go further. Another way is
The goal is to read all rows of the table at one time and allow the user to interrupt at any time.

[A. 2.1. One Row at a Time] After a user logs on to the system, he or she can use the browser to transition to a page with a table of headline news for a particular stock symbol, for example. The selected cells of this table are of particular interest. They can specify date, time and headline news respectively. Each row of the table is a news headline for a stock symbol. Below is the corresponding AML page for such an example. It includes both identification and conversion parts. The identification portion contains the rows of the table that make up the loop of iterations and the cells 1, 3 and 5 selected as an example from the HTML page. There is only one step, headline, in this page. It has prompt and input elements. The input element for this step is in a loop element looping over the component specified by the component attribute. Another prompt is associated with the input element and this prompt is spoken for each iteration of the loop. The prompt associated with the loop in this example is specified with respect to an array variable such as $ amlvar (Headlines [index] .date) called the date variable for the current line.

The following attributes have a number of implicit meanings for option tags: (1) next = “# goto”: Indicates that the next step is a step named goto (2) next = ” return ”: Return to the calling step (3) else: next is, for example, next =“ $ amlvar (c.continue) ”or next =
If specified as something else, such as http://www.amazon.com/select/select.cgi, the next step is traversing the anchor element.

The “next” attribute for the option following the prompt in each iteration is 2
One possible value: (i) a reserved word continue indicating that the system will proceed to the next iteration of the loop, and (ii) a transition to the system-specified URL if the user says "yes". $ Amlvar (Headli
nes [index] .news.url). Subsequent flow elements define the AML pages needed to continue browsing. The following is AML code with embedded audible prompts:

[Equation 6]

[A. 2.2 All Rows at One Time] All rows can be read one after the other and the user can be prompted at the end of the reading. It can be enhanced to add support for barge-in, i.e. to allow the user to interrupt the playing of the list.

[0020]

[Equation 7]

Interrupts allow users to listen to the news and say yes if they wish to hear the detailed news. This minimizes the number of things the user has to say.

[A. 3 Transformation: Variable Looping Element] Consider the following transformations for an example of variable looping for another sample. The stage after component identification is not much different from the table rendering in the previous example.

[0023]

[Equation 8]

[A. 4 Transformation: Another Structure] In the previous iterative structure example, each row had the same structure and the selected cells provided the required input. This section is an example of a different row structure.

Example 1 The following table can be rendered with different prompts for different cases in the table as follows.

[0026]

[Table 1]

[Equation 9]

[Equation 10]

Example 2 The following AML code renders a trade history table. There are two loops, one for the stock symbols and the other for each symbol's trading history.

[0028]

[Equation 11]

[Equation 12]

[B. Flow: Identify URL / Form Action] A transition from one HTML page to another HTML page can be done for the URL or form action element. They also define traversals between corresponding audio page specifications according to the invention. Therefore, it is possible to do a mapping called "flow" which defines the destination URL and the destination voice element. The source URL and source page information are also stored for simplicity and perhaps for easy searching. UR
L can have a static part and a dynamic part. In operation, the structural attribute to the component specification that identifies the variable URL is reused.

In the GUI part, the conversion of HTML pages into audio “programs” takes place at two levels. At the first level, individual HTML pages are converted into corresponding audio pages. At the second level, all audio pages are displayed and the user is given the URL / in the corresponding HTML component.
It is allowed to specify transitions between various audio pages using formal action methods. For each URL transition, an audio element is specified, which is "urls
-> audioid ”mapping is maintained internally, where audioid is an audio page identifier.

URL transitions are identified using flow elements. The flow element identifies the url and its corresponding dialog. Consider the href statement in the following HTML page:

[Equation 13]

If the user can traverse this URL (destination address), the corresponding flow specification is:

[Equation 14]

Similarly, when the formal component in the Amazon homepage example is selected, the action method is implicitly selected for traversal. Therefore,
For that, it is necessary to specify the flow element. Formal elements start, for example:

[Equation 15]

When the format is submitted, the destination URL is: http://www.amazon.com/exec/obidos/generic-quicksearch-query/002-0363237-
It is 2566852. This is the static part: http://www.amazon.com/exec/obidos/gene
It has ric-quicksearch-query / and variable part: 002-0363237-2566852.
The variable part is amazon. It is the session id assigned to the new session coming into the com page. Therefore, the flow component for this page can be defined as follows:

[Equation 16]

The caller / voice user can navigate between different audio steps using the navigation commands: back, forward, stop, continue and refresh. Transitions are defined between transition steps and marked steps. The back and forward commands respectively move the caller back to or from the next transition step. Stop ends the current rendering or background execution of the session. To continue, the work is started from where it was stopped. Play (refresh) plays the HTML page currently being investigated for the session. Thus, in AML language code such as the following, a headline step can be marked as a transition step using an attribute transition (which is "false" by default):

[Equation 17] Not all steps are transitional. Thus, a form may be converted into multiple steps internally and the user can always be forced to transition to the first step of the form.

[C. AML (DTD specification)] [C. 1 Entire Document] The following is a specification for the audio language AML. Other languages may be generated according to this syntax example, modified to work on the intended medium, or otherwise subject to specified constraints. Therefore, this specification is merely an example and is not limiting.

[0037]

[Equation 18]

[Formula 19]

[Equation 20]

[Equation 21]

[Equation 22]

[Equation 23] The invention has been described with reference to particular embodiments. One of ordinary skill in the art will recognize other embodiments. Therefore, the invention is not to be limited except as set forth in the appended claims.

[Brief description of drawings]

FIG. 1 is a block diagram of a system in accordance with the present invention in which a runtime engine uses elements identified by a suitable representation tool to retrieve information from an HTML page in accordance with the present invention.

[Fig. 2]   6 is a flowchart of sample conversion according to the present invention.

─────────────────────────────────────────────────── ─── Continued front page    (81) Designated countries EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, I T, LU, MC, NL, PT, SE), OA (BF, BJ , CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, K E, LS, MW, MZ, SD, SL, SZ, TZ, UG , ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, CA, CH, C N, CR, CU, CZ, DE, DK, DM, EE, ES , FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, KP, K R, KZ, LC, LK, LR, LS, LT, LU, LV , MA, MD, MG, MK, MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, S I, SK, SL, TJ, TM, TR, TT, TZ, UA , UG, UZ, VN, YU, ZA, ZW (72) Inventor Mohindra, Rajiev             California, United States             94552 Castro Valley, Beacon Hi             Le drive 4950 (72) Inventor Sinha, Amitaboo             California, United States             94022 Los Altos, Number 10, Da             Brew Edith 226 (72) Inventor Kurosapari, Prasad             California, United States             95129 San Jose, Craig Drive               1027 (72) Inventor Mc, Ronald             California, United States             95120 San Jose, Greystone Me             Dow Circle 6484 (72) Inventor Bittal, Chassis             California, United States             95051 Santa Clara, Uren Aveni             View 920 F-term (reference) 5D045 AA07 AA20

Claims (33)

[Claims] 1. A two-dimensional data which is a part of a mathematical regular expression in a computer network system having a storage means for source data and a means for identifying the source data is expressed in an audible or visible form, and The representation is a signature derived from an analysis of mathematical regular elements. In the rendering method, the signature is retrieved from the storage means in response to a question from the user, and the current element of interest when specified by the signature. A rendering method of retrieving a value of s from a source, converting the current value to an output by a preselected language translator, and providing the output to a user. 2. The method of claim 1, wherein the preselected language translator is a text-to-speech translator. 3. The method of claim 1, wherein the preselected language translator is a set of stored audible representations mapped to preselected values for each of the elements. 4. The method of claim 1, wherein the preselected language translator comprises a simplified textual representation engine mapped to preselected values for each of the elements. 5. A means for receiving source language information identifying a web element from a host web server; a means for receiving a mathematical regular expression identifying at least one web element identified by the source language information; and a source language. Means for generating target language information using the information and the mathematical regular expression to enable the runtime engine to provide the identified web element. 6. The system of claim 5, wherein the source language information comprises HTML data. 7. The target language information includes HTML data.
The system described. 8. The system of claim 5, wherein the target language information comprises run-time objects. 9. The system of claim 5, wherein the identified web element includes flow control information. 10. The system of claim 5, wherein the identified web element includes a list of options. 11. The system of claim 5, wherein the identified web element comprises a table. 12. The system of claim 5, wherein the identified web element includes a request for logon information. 13. The system of claim 5, wherein the runtime engine comprises a text-to-speech engine. 14. The system of claim 5, wherein the translator includes a text-to-speech engine. 15. The system of claim 5, wherein the translator includes an audible representation that is mapped to a preselected value for the identified web element. 16. The system of claim 5, wherein the translator includes a simplified textual representation mapped to preselected values for the identified web element. 17. Receiving source language information identifying a web element from a host web server and receiving a mathematical regular expression identifying at least one web element identified by the source language information, the source language information and the mathematical expression. A method of generating target language information from a canonical expression to enable the runtime engine to provide the identified web element. 18. Receiving source language information identifying a web element from a host web server and receiving a mathematical regular expression identifying at least one web element identified by the source language information, the source language information and the mathematical expression. A computer readable storage medium storing program code for causing a computer to take steps to generate target language information from a canonical representation to enable a runtime engine to provide an identified web element. 19. Receiving HTML page information from a host web server, retrieving a target language script from persistent storage, converting the HTML page information according to the target language script, and generating the converted HTML page information. , A method of providing converted HTML page information to a user by a rendering device. 20. The method of claim 19, wherein the converting comprises extracting dynamically updated data from HTML page information. 21. The method of claim 19, wherein the converted HTML page information is provided audibly. 22. The method of claim 19, wherein the transformed HTML page information includes run-time objects. 23. The method of claim 19, wherein said providing comprises interactively providing a prompt element to a user and receiving an input element from a user. 24. The method of claim 19, wherein the rendering device is a telephone. 25. The method of claim 19, wherein the HTML page information is a web page. 26. The method of claim 19, further comprising identifying the HTML page information selected for conversion. 27. In a method for a user to interactively access web page information, receiving web page information from a host web server and converting the web page information into a currently rendered dialog, the dialog being rendered. Receiving a transition of the currently represented page from the user, including the represented page that can be given to the user via the device, and representing the transition page by mapping it to the web page information target and the corresponding transition step. The dialog element corresponding to the web page information target in the transition step that defines the specified navigation element and receives the user's navigation command, and the interaction that occurs when the received navigation command of the user corresponds to the displayed element. Access method. 28. The method of claim 27, wherein the transition page is provided to the user shortly before receiving the transition of the rendered page. 29. The method of claim 27, wherein the navigation commands include backward commands that provide previous dialogs. 30. The navigation command of claim 27, wherein the navigation command includes a backward command in which the user adopts the backward direction for the next transition step and a forward command in which the user adopts the forward direction for the next transition step. Method. 31. The navigation commands include a stop command that terminates execution of the corresponding current rendering device, and a continue command that initiates execution of the corresponding rendering device from a state in which such execution is suspended. The method of claim 27. 32. Navigation commands are currently inspected HTML
28. The method of claim 27, including a refresh command to refresh the page. 33. The method of claim 27, wherein the rendered page comprises an audio page and the rendered element is an audio element.