Multiple interface scripting language

• US 6,658,646 B1
• Filed: 09/29/1999
• Issued: 12/02/2003
• Est. Priority Date: 09/29/1999
• Status: Expired due to Term

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Hernandez, III, Gaspar
• Primary Examiner(s): Morse, Gregory
• Assistant Examiner(s): Vo, Ted T.
• Application Number:
  US09/407,890
• Time in Patent Office: 1,525 Days
• Field of Search: 717/141, 717/114-117, 717/142-143
• US Class Current: 717/115
• CPC Class Codes: G06F 9/45512 Command shells

Abstract

For a large system having an associated monitoring system with one or more user interfaces that each requires a large amount of direct user interaction, a scripting language especially well suited to write a script (that generates liaison interface between the user and the existing user interfaces) is provided. The liaison interface requires much less direct user interaction by taking the place of the user in the extensive direct interaction required by the existing user interfaces. Such a scripting language that includes an integration construct data structure that permits commands of discrete interfaces to be integrated in a single script that is to be executed by a machine. Also provided are scripts according to the scripting language, that include at least two of the integration construct data structures.

Claims

1. A computer-readable medium having embodied thereon a script of machine-executable statements to be executed by a machine connected to a system, said system having at least a first interface for interacting with a user, said computer-readable-medium-embodied script causing said machine to generate a second interface for interacting differently with said user than said first interface, said first interface having a first set of commands and a corresponding first syntax, said second interface having a second set of commands and a corresponding second syntax, respectively, the second set being different than the first set and the second syntax being different than the first syntax,

said computer-readable-medium-embodied script comprising:

a sequence of executable statements in which at least two of the executable statements are integration constructs, each of said integration constructs including

a first field, readable by said machine, to identify for said machine and so cause said machine to correspondingly engage one of said first interface and said second interface; and

a second field, readable by said machine, to identify for said machine at least a command from the first or second command set, respectively, for the interface identified in said first field and so correspondingly cause said machine to submit the identified command to the respective engaged interface.

2. The computer-readable-medium-embodied script of claim 1, wherein said first field of said integration construct is separated from said second field by an alphanumeric symbol.

3. The computer-readable-medium embodied script of claim 2, wherein said alphanumeric symbol is a colon.

4. The computer-readable-medium-embodied script of claim 1, wherein said first interface also includes a set of parameters that can be passed with said first set of commands, respectively, and said second field includes at least one parameter corresponding to said command contained therein.

5. The computer-readable-medium-embodied script of claim 1, wherein said system is a wireless communication network and said first interface is one of the TIpdunix (TI) interface and the Status Display Page (SDP) interface.

6. The computer-readable-medium-embodied script of claim 5, wherein said system comprises a third interface having a third set of commands and a corresponding third syntax, said first is said TI Interface and said third interface is said SDP interface.

7. The computer-readable-medium-embodied script of claim 1, wherein said second interface is the Wireless Application Manager (WAM) interface.

8. The computer-readable-medium-embodied script of claim 1, wherein said sequence of executable statements further includes at least one IF-THEN-ELSE decisional construct.

9. The computer-readable-medium-embodied script of claim 1, wherein said first field of said integration construct is a header for said second field.

10. An integration construct data structure readable by a machine, said machine operating upon commands from at least a first interface and a second interface, the first domain having a first command set and a corresponding first syntax, the second domain having a second command set and a corresponding second syntax, the second set being different than the first set and the second syntax being different than the first syntax, said integration construct associating a command with an interface where said command is valid, said integration construct comprising:

a first data object, readable by said machine, to identify for said machine at least a command to be executed; and

a second data object, readable by said machine and linked to said first data object, to identify for said machine one of said first interface and said second interface as the interface in which the identified command of said first data object is valid, contents of the first and second data object causing said machine to correspondingly engage the identified interface and submit the identified command to the engaged interface.

11. The integration construct data structure of claim 10, wherein said first data object also identifies a parameter to be operated upon by said command in said first data object.

12. The integration construct data structure of claim 10, wherein said second data object is linked to said first data object by an alphanumeric symbol.

13. The integration construct data structure of claim 12, wherein the alphanumeric symbol is a colon.

14. The integration construct data structure of claim 10, wherein the first interface is a first user interface to a system and the second interface is a second user interface to the same system, the second interface providing different interaction with the user than the first interface.

15. The integration construct data structure of claim 14, wherein said system is a wireless communication network and said first interface is one of the TInpdunix (TI) interface and the Status Display Page (SDP) interface.

16. The integration construct data structure of claim 14, wherein said second interface is the Wireless Application Manager (WAM) interface.

17. A method of parsing an executable statement, said executable statement being readable by a machine, said machine operating upon commands for use with one of at least a first interface and a second interface, said first interface having a first command set and a corresponding first syntax, said second interface having a second command set and a corresponding second command set, the first set being different than the second set and the first syntax being different than the second syntax, said method comprising:

examining said executable statement to identify one of at least said first interface and said second interface as the interface for which a command embedded in said executable statement is to be parsed;

examining said executable statement to identify at least said command; and

parsing the identified command according to the respective command set, and the respective syntax, of the identified interface.

18. The method of claim 17, further comprising examining said executable statement to identify a parameter to be operated upon by said command.

19. The method of claim 17, wherein the first interface is a first user interface to a system and the second interface is a second user interface to the same system, the second interface providing different interaction with the user than the first interface.

20. The method of claim 19, wherein said system is a wireless communication network and said first interface is one of the TInpdunix (TI) interface and the Status Display Page (SDP) interface.

21. The method of claim 19, wherein said second interface is the Wireless Application Manager (WAM) interface.

22. The method of claim 19, wherein the executable statement includes an integration construct, the integration construct including

a first field, readable by said machine, to identify for said machine and so cause said machine to correspondingly engage one of said first interface and said second interface, and

a second field, readable by said machine, to identify for said machine at least a command from the first or second command set, respectively, for the interface identified in said first field and so correspondingly cause said machine to submit the identified command to the respective engaged interface.

23. The method of claim 22, wherein said first field of said integration construct is separated from said second field by an alphanumeric symbol.

24. The method of claim 23, wherein said alphanumeric symbol is a colon.

25. The method of claim 22, wherein said first interface also includes a set of parameters that can be passed with said first set of commands, respectively, and said second field includes at least one parameter corresponding to said command contained therein.

26. The method of claim 22, wherein said first field of said integration construct is a header for said second field.