CA2080797C - Method of operating a computer program using data base schema and related language dictionaries - Google Patents
Method of operating a computer program using data base schema and related language dictionariesInfo
- Publication number
- CA2080797C CA2080797C CA002080797A CA2080797A CA2080797C CA 2080797 C CA2080797 C CA 2080797C CA 002080797 A CA002080797 A CA 002080797A CA 2080797 A CA2080797 A CA 2080797A CA 2080797 C CA2080797 C CA 2080797C
- Authority
- CA
- Canada
- Prior art keywords
- database
- data
- loading
- schema
- language
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
Abstract
A method of operating a computer program comprised of encoding a description of each view and field of a database into a database schema loading the database schema onto a switching platform during commissioning thereof preparing language dictionaries storing phrases representing all legal data values within the database, including view and field names loading said dictionaries onto the switching platform each time the switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform, and using a standard database program language as an interpreter of the meta-data within the database schema.
Description
-FIELD OF THE INVENTION
This invention relates to computers, and particularly to a method of operating a computer program.
BACKGROUND TO THE INVENTION
S A standard database command (or manipulation) language is TL1, which has been standardized by BellCore for public switching platforms (systems) and network equipment. This language is based on the CCITT Z.300 series recommendations for man-machine language.
Classical implementation methods would involve creating a lexical analyzer using the lex software available on virtually all UNIX platforms. Then a Yacc parser supplemented by custom code is created to handle the semantic processing.
Unfortunately, these methods essentially hardcode the field names and associated values such that any variation in the syntax or semantics of a particular database view of field require a new software build. In typical systems where several different databases and/or languages are used by the same software this leads to a proliferation of software builds and significant inflexibility.
Because of these problems, independent languages and multiple schema capability are typically not available on-switching machine or on-switching platform because of these problems.
SUMMARY OF THE INVENTION
From software release to software release, in accordance with this invention no software maintenance work is required at all within the TL1 language software. Instead, a database schema and related language dictionaries are loaded into the system with the new software load and the existing TLl language code runs from this new data. An immense amount of custom coding is avoided.
Because the database schema and language dictionaries exist in a highly encoded form, they can be interpreted by other database language processors and/or applications to provide access to the switching system's data. For example, an off-board form-based customer data entry can paint a TLl compatible interface into windows on a personal computer, allowing a simplified switch programming mechanism. This package also survives from software load to software load with only a change in database schema and language dictionary files.
In accordance with an embodiment of the invention, a method of operating a computer program is comprised of encoding a description of each view and field of a database into a database schema; loading the database schema onto a switching platform during commissioning thereof; preparing language dictionaries storing phrases representing all legal data values within the database, including view and field names; loading the dictionaries onto the switching platform; each time the switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform; using a standard database program language as an interpreter of the meta-data within the database schema, wherein the steps of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data, the setup of loading includes loading of the encoded description other than actual data, and the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
In yet another embodiment, a method of operating a computer program is comprised of encoding a description of each view and field of a database into a database schema; loading the database schema onto a switching platform during initial operation thereof; preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names; loading the dictionaries onto the switching platform; each time the switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform; using a standard database program language as an interpreter of meta-data within the database schema, for every standard database program language command, retrieving from the RAM each bit of data about each field within the database command, the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data and the step of loading including loading of the encoded description other than actual data, and the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
BRIEF INTRODUCTION TO THE DRAWINGS
A better understanding of the invention will be obtained by reference to the description below in conjunction with the following drawings, in which:
.
2b Figure 1 illustrates in a flow diagram the functionality of a second process step used in the invention.
Figure 2 illustrates in a flow diagram the functionality of a third process step used in the nventlon .
Figure 3 illustrates in a flow diagram the functionality of fourth and fifth process steps used in the invention.
Figure 4 illustrates in a flow diagram the functionality of a sixth process step used in the invention.
.~
This invention relates to computers, and particularly to a method of operating a computer program.
BACKGROUND TO THE INVENTION
S A standard database command (or manipulation) language is TL1, which has been standardized by BellCore for public switching platforms (systems) and network equipment. This language is based on the CCITT Z.300 series recommendations for man-machine language.
Classical implementation methods would involve creating a lexical analyzer using the lex software available on virtually all UNIX platforms. Then a Yacc parser supplemented by custom code is created to handle the semantic processing.
Unfortunately, these methods essentially hardcode the field names and associated values such that any variation in the syntax or semantics of a particular database view of field require a new software build. In typical systems where several different databases and/or languages are used by the same software this leads to a proliferation of software builds and significant inflexibility.
Because of these problems, independent languages and multiple schema capability are typically not available on-switching machine or on-switching platform because of these problems.
SUMMARY OF THE INVENTION
From software release to software release, in accordance with this invention no software maintenance work is required at all within the TL1 language software. Instead, a database schema and related language dictionaries are loaded into the system with the new software load and the existing TLl language code runs from this new data. An immense amount of custom coding is avoided.
Because the database schema and language dictionaries exist in a highly encoded form, they can be interpreted by other database language processors and/or applications to provide access to the switching system's data. For example, an off-board form-based customer data entry can paint a TLl compatible interface into windows on a personal computer, allowing a simplified switch programming mechanism. This package also survives from software load to software load with only a change in database schema and language dictionary files.
In accordance with an embodiment of the invention, a method of operating a computer program is comprised of encoding a description of each view and field of a database into a database schema; loading the database schema onto a switching platform during commissioning thereof; preparing language dictionaries storing phrases representing all legal data values within the database, including view and field names; loading the dictionaries onto the switching platform; each time the switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform; using a standard database program language as an interpreter of the meta-data within the database schema, wherein the steps of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data, the setup of loading includes loading of the encoded description other than actual data, and the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
In yet another embodiment, a method of operating a computer program is comprised of encoding a description of each view and field of a database into a database schema; loading the database schema onto a switching platform during initial operation thereof; preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names; loading the dictionaries onto the switching platform; each time the switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform; using a standard database program language as an interpreter of meta-data within the database schema, for every standard database program language command, retrieving from the RAM each bit of data about each field within the database command, the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data and the step of loading including loading of the encoded description other than actual data, and the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
BRIEF INTRODUCTION TO THE DRAWINGS
A better understanding of the invention will be obtained by reference to the description below in conjunction with the following drawings, in which:
.
2b Figure 1 illustrates in a flow diagram the functionality of a second process step used in the invention.
Figure 2 illustrates in a flow diagram the functionality of a third process step used in the nventlon .
Figure 3 illustrates in a flow diagram the functionality of fourth and fifth process steps used in the invention.
Figure 4 illustrates in a flow diagram the functionality of a sixth process step used in the invention.
.~
2~8Q797 DETAILED DESCRIPTION OF THE INVENTION
A description of each view and field is encoded into a database schema and is loaded onto the switching platform during commissioning thereof. As well, language dictionaries storing phrases representing all legal data values (including view and field names) within the database are built off-line and then are loaded onto the switching platform.
Each time the system is rebooted, the schema and related language dictionaries are loaded into switching system RAM. After this, the TL1 language runs as an interpreter of the data (or more accurately, meta-data) within the database schema.
For every TL1 command, the system retrieves from the schema RAM area each bit of data about each field within the database command.
A typical database command utilizes the following steps during processing:
1. Parse command syntax and build a parse tree describing the location of all data blocks, field names, and field values. No checking of identifier validity or field content validity is done at this time.
2. Verify, from the schema and language dictionaries that the TL1 command and view identifier are a valid combination.
A description of each view and field is encoded into a database schema and is loaded onto the switching platform during commissioning thereof. As well, language dictionaries storing phrases representing all legal data values (including view and field names) within the database are built off-line and then are loaded onto the switching platform.
Each time the system is rebooted, the schema and related language dictionaries are loaded into switching system RAM. After this, the TL1 language runs as an interpreter of the data (or more accurately, meta-data) within the database schema.
For every TL1 command, the system retrieves from the schema RAM area each bit of data about each field within the database command.
A typical database command utilizes the following steps during processing:
1. Parse command syntax and build a parse tree describing the location of all data blocks, field names, and field values. No checking of identifier validity or field content validity is done at this time.
2. Verify, from the schema and language dictionaries that the TL1 command and view identifier are a valid combination.
3. Verify, from the schema dn language dictionaries, that the field value within the access identifier block has valid syntax and semantics; i.e. if the command is enter, verify that this key field does not already exist within the database. If necessary, store the retrieved database tuple in system RAM for later use.
4. Scan across the data block and perform these steps for each field that has been entered:
a) Verify, from the schema and language dictionaries, that the field name exists.
4 2~80797 b) Verify, from the schema and language dictionaries, that the field data is of the correct type and holds a legal value for that field.
c) Insert, using size and position data from the schema, the data value in binary form into the database tuple.
a) Verify, from the schema and language dictionaries, that the field name exists.
4 2~80797 b) Verify, from the schema and language dictionaries, that the field data is of the correct type and holds a legal value for that field.
c) Insert, using size and position data from the schema, the data value in binary form into the database tuple.
5. Scan across the data block and perform these steps for each field that has not been entered:
a) Verify, from the schema, that the field is optional, i.e. need not be filled.
b) For edit commands do nothing more. For enter commands, extract the default value from the database schema and stuff it into the database tuple in binary form.
a) Verify, from the schema, that the field is optional, i.e. need not be filled.
b) For edit commands do nothing more. For enter commands, extract the default value from the database schema and stuff it into the database tuple in binary form.
6. Execute the particular TL1 command. For example, enter and edit commands require writing the tuple into the system database RAM at this time.
To access a different database, a different set of schema and language dictionary files is simply loaded into RAM, and the pointers are changed.
A specific example will be given with reference to the drawings and tables shown below.
An example of a command is:
"enter-system config::1-2-2:::programmed card==single party line" (quotations do not form part of the command).
Table 1 illustrates the information units, after the first step described above. Table 2 illustrates the parameters after the second step. The token numbers relate to Table 1.
The tables are shown at the end of this disclosure, as Appendix A.
Command and Block information is as follows, after the first step. Parm~i relate to Table 2.
command: token 1 view identifier: token 3 blocks: 5 20$0797 target id block: null access id block: null correlation tag block: null access id block: 1 parm, first is parm 1 correlation tag block: null general block: null data block: 1 parm, first is parm 2 Figure 1 illustrates in a flow diagram the functionality of the second process step described above.
Figure 2 illustrates in a flow diagram the functionality of the third process step described above.
Figure 3 illustrates in a flow diagram the functionality of the fourth and fifth process steps described above.
Figure 4 illustrates in a flow diagram the functionality of the sixth process step described above.
It should be noted that Tables 1 and 2 are used extensively from RAM, as is the command line.
A variation of data driven TL1 can be used as a communications pipe between the switching platform and the off-board data entry platform and will be equally immune from database changes.
To access a different database, a different set of schema and language dictionary files is simply loaded into RAM, and the pointers are changed.
A specific example will be given with reference to the drawings and tables shown below.
An example of a command is:
"enter-system config::1-2-2:::programmed card==single party line" (quotations do not form part of the command).
Table 1 illustrates the information units, after the first step described above. Table 2 illustrates the parameters after the second step. The token numbers relate to Table 1.
The tables are shown at the end of this disclosure, as Appendix A.
Command and Block information is as follows, after the first step. Parm~i relate to Table 2.
command: token 1 view identifier: token 3 blocks: 5 20$0797 target id block: null access id block: null correlation tag block: null access id block: 1 parm, first is parm 1 correlation tag block: null general block: null data block: 1 parm, first is parm 2 Figure 1 illustrates in a flow diagram the functionality of the second process step described above.
Figure 2 illustrates in a flow diagram the functionality of the third process step described above.
Figure 3 illustrates in a flow diagram the functionality of the fourth and fifth process steps described above.
Figure 4 illustrates in a flow diagram the functionality of the sixth process step described above.
It should be noted that Tables 1 and 2 are used extensively from RAM, as is the command line.
A variation of data driven TL1 can be used as a communications pipe between the switching platform and the off-board data entry platform and will be equally immune from database changes.
Claims (2)
1. A method performed by computer of operating a computer program, comprising the steps of:
(a) encoding a description of each view and field of a database into a database schema;
(b) loading the database schema onto a switching platform during initial operation thereof;
(c) preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names;
(d) loading said dictionaries onto the switching platform;
(e) each time said switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform;
(f) using a standard database program language as an interpreter of meta-data within the database schema, (g) wherein the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data, (h) the step of loading includes loading of the encoded description other than actual data, and (i) the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
(a) encoding a description of each view and field of a database into a database schema;
(b) loading the database schema onto a switching platform during initial operation thereof;
(c) preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names;
(d) loading said dictionaries onto the switching platform;
(e) each time said switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform;
(f) using a standard database program language as an interpreter of meta-data within the database schema, (g) wherein the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data, (h) the step of loading includes loading of the encoded description other than actual data, and (i) the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
2. A method performed by computer of operating a computer program, comprising the steps of:
(a) encoding a description of each view and field of a database into a database schema;
(b) loading the database schema onto a switching platform during initial operation thereof;
(c) preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names;
(d) loading said dictionaries onto the switching platform;
(e) each time said switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform;
(f) using a standard database program language as an interpreter of meta-data within the database schema, (g) for every standard database program language command, retrieving from said RAM each bit of data about each field within the database command, (h) the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data and the step of loading including loading of the encoded description other than actual data, and (i) the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
(a) encoding a description of each view and field of a database into a database schema;
(b) loading the database schema onto a switching platform during initial operation thereof;
(c) preparing language dictionaries storing phrases representing all expected data values within the database, including view and field names;
(d) loading said dictionaries onto the switching platform;
(e) each time said switching platform is rebooted, loading the schema and related language dictionaries into a RAM used by a processor of the switching platform;
(f) using a standard database program language as an interpreter of meta-data within the database schema, (g) for every standard database program language command, retrieving from said RAM each bit of data about each field within the database command, (h) the step of encoding a description of each view and field of a data base into a database schema includes encoding a description other than actual data and the step of loading including loading of the encoded description other than actual data, and (i) the step of preparing language dictionaries includes preparing a database of specifications of data and information processing resources storing all phrases representing all expected data values within the data base, and the meta-data is program description data which is interpreted by the standard database program language.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002080797A CA2080797C (en) | 1992-10-16 | 1992-10-16 | Method of operating a computer program using data base schema and related language dictionaries |
| US07/962,330 US5659738A (en) | 1992-10-16 | 1992-10-16 | Method of operating a computer program using database schema and related language dictionaries |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002080797A CA2080797C (en) | 1992-10-16 | 1992-10-16 | Method of operating a computer program using data base schema and related language dictionaries |
| US07/962,330 US5659738A (en) | 1992-10-16 | 1992-10-16 | Method of operating a computer program using database schema and related language dictionaries |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2080797A1 CA2080797A1 (en) | 1994-04-17 |
| CA2080797C true CA2080797C (en) | 1999-02-02 |
Family
ID=25675597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002080797A Expired - Lifetime CA2080797C (en) | 1992-10-16 | 1992-10-16 | Method of operating a computer program using data base schema and related language dictionaries |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US5659738A (en) |
| CA (1) | CA2080797C (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6268850B1 (en) | 1997-12-22 | 2001-07-31 | Sun Microsystems, Inc. | User interface for the specification of lock groups |
| US6175837B1 (en) * | 1998-06-29 | 2001-01-16 | Sun Microsystems, Inc. | Object-relational mapping toll that processes views |
| US6360223B1 (en) | 1997-12-22 | 2002-03-19 | Sun Microsystems, Inc. | Rule-based approach to object-relational mapping strategies |
| US7281003B2 (en) * | 1998-10-05 | 2007-10-09 | Oracle International Corporation | Database fine-grained access control |
| US6330555B1 (en) * | 1999-02-19 | 2001-12-11 | Nortel Networks Limited | Method and apparatus for enabling a view of data across a database |
| US6591275B1 (en) | 2000-06-02 | 2003-07-08 | Sun Microsystems, Inc. | Object-relational mapping for tables without primary keys |
| US6915305B2 (en) | 2001-08-15 | 2005-07-05 | International Business Machines Corporation | Restructuring view maintenance system and method |
| EP1296252B1 (en) * | 2001-09-21 | 2007-08-01 | Koninklijke KPN N.V. | Computer system, data communication network, computer program and data carrier, all for filtering a received message comprising mark-up language content |
| US7310647B2 (en) * | 2003-12-24 | 2007-12-18 | Oracle International Corporation | Column masking of tables |
| US8825702B2 (en) | 2004-02-24 | 2014-09-02 | Oracle International Corporation | Sending control information with database statement |
| US10318752B2 (en) * | 2006-05-26 | 2019-06-11 | Oracle International Corporation | Techniques for efficient access control in a database system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4774661A (en) * | 1985-11-19 | 1988-09-27 | American Telephone And Telegraph Company, At&T Information Systems | Database management system with active data dictionary |
| US4841433A (en) * | 1986-11-26 | 1989-06-20 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method and apparatus for accessing data from data attribute tables |
| US5274802A (en) * | 1991-02-22 | 1993-12-28 | Gte Mobilnet Incorporated | Method for restoring lost databases by comparing existing database and generic database, and generating cellular switch commands to update the generic database |
| SG45328A1 (en) * | 1991-11-27 | 1998-01-16 | Ericsson Telefon Ab L M | Software structure for telecommunication switching systems |
| US5418957A (en) * | 1992-03-09 | 1995-05-23 | Narayan; Rom | Network data dictionary |
-
1992
- 1992-10-16 CA CA002080797A patent/CA2080797C/en not_active Expired - Lifetime
- 1992-10-16 US US07/962,330 patent/US5659738A/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| US5659738A (en) | 1997-08-19 |
| CA2080797A1 (en) | 1994-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6158031A (en) | Automated code generating translator for testing telecommunication system devices and method | |
| CA2080797C (en) | Method of operating a computer program using data base schema and related language dictionaries | |
| US6636877B1 (en) | Method for analyzing the quality of telecommunications switch command tables | |
| CN112540923B (en) | Interface parameter checking and converting method, device, equipment and storage medium | |
| US5021943A (en) | Content independent rule based options negotiations method | |
| EP0669066B1 (en) | Equipment management system | |
| US5941978A (en) | Method for comparing attribute values of controllable object expressions in a network element | |
| US6003035A (en) | Method and apparatus for building a telecommunications network database | |
| CN1526104B (en) | Parsing structured data | |
| US6678370B1 (en) | Data extraction process | |
| AU679637B2 (en) | Interface device and method | |
| US8001242B2 (en) | Method for redirection of host data access to multiple non-host file systems or data stores | |
| CA2172221A1 (en) | Method and apparatus for managing relationships among objects in a distributed object environment | |
| US6829620B2 (en) | Table-level unicode handling in a database engine | |
| US20100185937A1 (en) | Methods and apparatus for creating markup language documents | |
| US6356886B1 (en) | Apparatus and method for communicating with a knowledge base | |
| AU2004318284B2 (en) | ASN.1 protocol processor and method for ASN.1 protocol processing | |
| CN100421110C (en) | Search method of dictionary data | |
| US6668053B1 (en) | Process for generating recent change commands for various stored program telephone switches | |
| US20060294127A1 (en) | Tagging based schema to enable processing of multilingual text data | |
| EP0678817A1 (en) | Data capture in a communication network configuration system | |
| CA2437008A1 (en) | Method and apparatus for data migration between databases | |
| EP0344083A2 (en) | Explicit specification of valid compound document data stream structure and content | |
| CN115687292B (en) | Verifiable database upgrading method irrelevant to database technology | |
| CN112346672B (en) | Log dyeing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry | ||
| MKEX | Expiry |
Effective date: 20121016 |