CA2094657C - Communication system links different independent databases and provides automatic updating of corresponding records in the databases - Google Patents

Communication system links different independent databases and provides automatic updating of corresponding records in the databases

Info

Publication number
CA2094657C
CA2094657C CA002094657A CA2094657A CA2094657C CA 2094657 C CA2094657 C CA 2094657C CA 002094657 A CA002094657 A CA 002094657A CA 2094657 A CA2094657 A CA 2094657A CA 2094657 C CA2094657 C CA 2094657C
Authority
CA
Canada
Prior art keywords
record
database
records
node
nodes
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 - Fee Related
Application number
CA002094657A
Other languages
French (fr)
Other versions
CA2094657A1 (en
Inventor
Timothy Eldon Balgeman
Diane Myrl Clodi
Robert Webster Haddleton Jr.
John Roger North
Judith Ann Selby
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Corp
Original Assignee
American Telephone and Telegraph Co Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by American Telephone and Telegraph Co Inc filed Critical American Telephone and Telegraph Co Inc
Publication of CA2094657A1 publication Critical patent/CA2094657A1/en
Application granted granted Critical
Publication of CA2094657C publication Critical patent/CA2094657C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/258Data format conversion from or to a database
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99939Privileged access
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users

Abstract

A database interface and associated communication program are installed at each node in a communication network. The database interface provides a translation between different record formats held in the databases at each node and a standardized record format used to communicate records among the nodes. The communication program provides a facility for transmitting and receiving records in standardized record format among the nodes. The communication program automatically transmits records which have been modified at one node to all other nodes which contain corresponding records, thus maintaining current records at each node.

Description

2~946~7 COMMUNICATION SYSTEM LINKS DIFFERENT
INDEPENDENT DATABASES AND PROVIDES AUTOMATIC UPDATING
OF CORRESPONDING RECORDS IN THE DATABASES
Background of the Invention This invention relates to a communication system in which records are stored in independent databases and more specifically relates to communicating and updating corresponding records in the different independent databases. This invention is especially, but not exclusively, suited for intercompany database record sharing such as between an equipment manufacturer and its customer.
A variety of collllllunication networks exist which can transmit data files from an origination node (NODE O) to a destination node (NODE D). However, such a transrnission may not achieve the goal of transferring the desired information from NODE O to NODE D in a form readily usable at NODE D. As an example, assume that the information to be tr~nsmitte~l by NODE O is a record created in 15 NODE O's independent, local database. If the objective is to create a duplicate record in an independent, local database at NODE D, the received record can be directly entered in NODE D's ~t~b~ce assuming both NODE O and NODE D utilize the same database and the same field formats. If the ~l~t~b~ce at NODE D is not directly compatible with the record received from NODE O, a user at NODE D must 20 manually translate the received record into a record in the local database format. It is apparent that substantial inefficiencies exist where different database formats are utilized. If the databases utilized by NODE O and NODE D are controlled by independent companies, it is unlikely that each company will utilize the same database software. Even if the companies did utilize the same (l~t~b:~ce software, it 25 is even more unlikely that each will have created a substantially identical record format structures because of the different needs of each company.
It is possible to address this problem by utilizing a single database which can be accessed by a variety of users. Such a solution has the disadvantage that all of the users must agree to utilize the same format and agree to a common set 30 of rules regarding use and access of the database. It is difficult to achieve agreement among independent co-llpal-ies, or even different parts of the same company, because of their differing needs and objectives regarding database capabilities.Difficulties would still exist even if independent companies utilized the same database software and record format. Although the common structure of the 35 database records would enable records to be co,llmunicated over a conventional communication network and entered into another database, difficulties exist in maintaining duplicate records in different databases where the record can be updated by a user at any of the independent databases. Although it is possible to establish rules requiring that new and modified records be transmitted to others in the network, this places a substantial burden on each user in systems where it is 5 desirable to maintain duplicate records at different databases so that information can be locally accessed.
Thus, there exists a need for a communication system which provides flexibility by allowing individual nodes to utilize different databases and which automatically updates corresponding records at different databases with a minimum 10 of burden on the users.
SUMMARY OF THE INVENTION
It is an object of the present invention to provide an improved communication system which addresses the above needs.
In accordance with an embodiment of the present invention, a 15 database interface and an associated communication program are installed at each node in a communication network. The database interface provides a translation between the record format used at a database and a common standardized record format. Thus, the database interface provides an inbound and outbound translation of fields within a record in order to provide compatibility with varying databases 20 utilized at different nodes. The standardized format is used by the communication program to transmit record information to the other nodes in the system. The communication program provides a means for transmitting records and updates of records to the nodes in the network which need to maintain duplicate records. This communication capability is substantially automated to minimize user demands.
In accordance with one aspect of the present invention there is provided a communication system comprising: first and second nodes coupled to each other; first and second databases associated with said first and second nodes respectively, each store records, said first database storing said records in a first field format and said second database storing said records in a second field format which 30 is different from said first field format; means at said first and second nodes for transmitting records having standardized format to and receiving records having standardized format from the other of said first and second nodes, said standardized format being different from said first and second field formats; means at said first node for automatically translating a received standardized format record into said 35 first field format record for storage in said first database and for automatically --2a- F, ~ 5 7 translating a first field format record stored in said first database into standardized format record for transmission to said second node; means for independently identifying an originator and an owner of each record, said translating and transmitting means acting to translate and transmit a first record contained in said 5 first database associated with said first node to said second database associated with said second node based upon entry in said first record of an owner associated with said second database, wherein records in said first database that do not identify an owner are not transmitted to said second database; said identifying means permitting the identified owner of a duplicate record stored at the second database and 10 corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed owner-ship to be automatically transmitted to a database associated with the changed owner.
In accordance with another aspect of the present invention there is provided a method for handling records in a communications system which includesIS at least first and second nodes having first and second databases, respectively, said first database storing records in a first field format and said second database storing records in a second field format which is different from said first field format, said method comprising the steps of: transmitting records having a standardized format from said first node and receiving records having a standardized format at said first 20 node from said second node, said standardized format being different from said first and second field formats; automatically translating a standardized forrnat record received by said first node into said first field format record for storage in said first database and for automatically translating a first field format record stored in said first database into a standardized format record for transmission to said second node;
25 independently identifying an originator and an owner of each record, said translating and transmitting steps translating and transmitting a first record contained in said first database associated with said first node to said second database associated with said second node based upon entry in said first record of an owner associated with said second database, wherein records in said first database that do not identify an 30 owner are not transmitted to said second database; said identifying step permitting the identified owner of a duplicate record stored at the second database and corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed ownership to be automatically transmitted to a database associated with the changed 3 5 owner.

-2b-BRIEF DESCRIPTION OF THE DRAWING
FIG. I is a block diagram of a typical network which incorporates an embodiment of the present invention.
FIG. 2 is a block diagram of a typical node in the network of FIG. 1.
FIG. 3 is a diagram which illustrates the relationship between database interface software and communication software in accordance with the present invention.
FIG. 4 is a diagram which illustrates the mapping of a local database record into a standardized record format in accordance with the present invention.
FIG. 5 illustrates an embodiment of a communication directory and file structure in accordance with an embodiment of the present invention.

20~4~7 FIGS. 6 and 7 comprise a table that illustrates parameters utilized with each record in accordance with an embodiment of the present invention.
FIG. 8 is a flow diagram illustrating the transmission of a record from a node in accordance with an embodiment of the present invention.
S FIG. 9 is a flow diagram illustrating receipt of a record from another node in accordance with an embodiment of the present invention.
Detailed Description An exemplary application of the present invention follows in order to appreciate the advantages of the present invention. Assume that a provider of 10 teleco~ u~ications equipment is coupled via a co..-.--...lication system to a plurality of independent users of its e.luiylllent. A trouble ticket, i.e. a documented problem with a failure of user owned e~luipnle-lt, is entered by a user in an independent rlataba~e controlled by the user. If the trouble ticket relates to equipment supplied by the manufacturer a copy of the trouble ticket is forwarded l]tili7ing the database 15 interface and co""--ul-ication program in accordance with an embodiment of the present invention to a corresponding field support organi7ation of the e-luiylll~,nt provider. If this org~ni7ation is able to solve the problem, the duplicate ticket stored in a database of the support organi7~tion is modified indicating the solution or other relevant information relating to the problem and transmitted to the originating user.
20 If the organi7~tion is unable to solve the problem, it sends a copy of the ticket to a different org:lni7ation within the company with greater technical expertise and sends an update of the same ticket back to the user so that the user is apprised of the status of the trouble ticket. Assuming the higher level organi7ation solves or otherwise handles the problem, the higher level org~ni7~tion updates the trouble ticket and 25 sends a copy of the updated trouble ticket back to the field support organi7ation which in turn sends the update to the end user. ~suming the end user is satisfied with the solution to the problem indicated on the updated trouble ticket, the ticket is updated and closed by the user with copies of the update being sent to the fieldsupport organi7~tion and the higher level technical organi7ation. Each organi7ation 30 dealing with the trouble ticket is apprised of all updates to the trouble ticket by any involved party. However, each of the parties (nodes in the comlllunication system) are free to maintain an independent ~1~taba~e so that each can independently maintain statistics and otherwise utilize the information according to the needs of each. The illustrative embodiment of the present invention can be 35 incorporated in a network utilized for problem solving as explained above.
However, it will be a~yalen~ to those skilled in the art that the utility of the present invention is not limited to this application.
FIG. 1 illustrates a communication system in which a plurality of user nodes 10-20 are coupled to support nodes 22 and 24 which are in turn coupled to central support node 26. In the illustrative example, service providers at nodes 22 S and 24 are in a direct support level and have sufficient expertise to solve many of the problems posed by the users which they support. Technical experts at node 26 provide corporate support to users for problems which the service providers at the direct support nodes cannot solve. The direct support nodes are also connected to each other so that problem solving expertise can be shared at the direct support level.
10 A communication network 27 provides c(JIlllllunication channels among the nodes.
This embodiment of the present invention is especially well suited for utilization in the illustrative system, especially when the equipment and/or software supplied to users is complex. For example, users may encounter difficulties in configuring the equipment to properly interface with other peripheral equipment or 15 in customizing the operation of the equipment pursuant to a desired customer configuration. Help with such problems can normally be provided by the service providers at the support nodes. Another class of problems which users may encounter deal with failures or errors in the basic operation of the equipment. Some of these problems may be solved by personnel at the support nodes, but other 20 problems will require the greater technical expertise available from the technical experts at the central support node.
In the illustrative example, a user documents a new problem by entering applopliate information describing the equipment, nature of the problem, and other parameters utilizing the user's database. The user preferred format for storing 25 information in the local independent database is translated into a standardized record format by a rl~t~bace interface which is coupled to the local database. After the information is tr~nsl~ted into the standardized record format, a communication program in accordance with the present invention interfaces with the database interface and permits the standardized record to 'oe transmitted to a direct support 30 node. A d~t~ba~e interface at the support node translates the standardized record into the applv~liate format for the independent database m~int~ined by the support node.
The support node acknowledges receipt of the record to the user. Preferably, thedirect support node generates an electronic mail (e-mail) message to an assignedsupport person, advising of the receipt of a problem ticket. After the direct support 35 person considers the problem as documented by the user's record, the record will typically be updated by the assigned support person to contain additional 2094~7 information and may request additional information from the user relevant to theproblem. The record at the support node is updated in the support node database and communicated to the originating user in standardized format. The database interface at the user node translates the received update from standardized format to the record S format used at the user's local database. Thus, each node in the system which addresses a trouble ticket maintains an updated record regardless of the party making an update. Preferably, the person at the user node is notified by e-mail indicating that the record has been updated and thus, should be reviewed for possible additional action. Thus, the user and the assigned support person are each guaranteed of having 10 access to the latest updated illfolmation concerning the problem while allowing each to m~int~in an independent d~t~bace which can be tailored to meet the different needs of the user and the support provider.
FIG. 2 illustrates a typical node in a system in accordance with the present invention. The node includes a microprocessor (MPU) 28, and associated 15 memory including read-only nle.lluly (ROM) 30, random access memory (RAM) 32,and alternate memory storage 34 such as a disk or tape drive. Conventional inputand output devices associated with MPU 28 include a keyboard 36, a video displayterminal 38, and a comlllullication module 40 which enables comrnunications between MPU 28 and a collllllullication network 27. The node as shown in FIG. 2 20 can be used for any of the nodes as shown in FIG. 1. The commllnication network 27 may comprise either the public switched telephone network such as by modems or may comprise dedica~ed leased lines between the users and connected nodes.
FIG. 3 is a pictorial representation of the relationship among software in 25 accordance with the present invention. Local database software 46 receives input from the user and provides output to the user of stored records. The database interface 44 translates the relevant fields in a record stored in the local database 46 into corresponding fields in a standardized record format. Records retrieved viainterface 44 from the local d~t~b~ce are likewise tr~ncl~te~ for trancmicsiQn by30 communication program 48 to collllllunication network 27 in the standardized record format. The standardized record format allows individual nodes to maintain different local database soflwalc programs and define fields within records to meet the needs of the associated users of the node. The local database may consist ofconventionally available database software including flat file and relational types. In 35 order to minimi7e the overall communication network requirements in order to handle the transmission of records, each of the nodes preferably utilizes a UNIX(~

-6- 2094~
operating system which inherently contains communication support.
FIG. 4 graphically illustrates how the database interface 44 interfaces with the local d~t;~h~ce 46. The standardized record format 50 is defined and stored in database interface 44. It is related to a local database record format 52 utilized by 5 the local database 46. The standardized record format 50 includes fields A-N which define different information parameters which can be co.lllllunicated within thenetwork shown in FIG. 1. The local ~t:~b~ce record format 52 includes fields 1-99 which correspond to paldll~tel~ determined by the operator of the node for possible storage in local database 46. The lines 54 which interconnect one field in format 50 10 with one field in format 52 identify the translation or mapping which will occur when transferring records 52 stored in local database 46 to other nodes in the system.
Each of the fields in record format 50 are preferably supported by a corresponding field in record format 52. The standardized record format 50 which is transmitted between nodes allows the independent databases associated with each node to be 15 able to share information with other nodes without requiring manual re-entry of the information at another database because of dirrel~nt record and field structures.
In a preferred embodiment of the present invention, one of the fields in standardized record format 50 identifies if the record contains information which should be interpreted by another node as a trouble ticket, i.e. typically a request for 20 help by another node, and another field contains a description of the product or manufacturer of the product associated with the problem. Each node preferably maintains in memory an address map which identifies the support node to receive a copy of the record dependent upon the equipment manufacturer or product entered in the corresponding record field. Thus, a user as illustrated in FIG. 1 does not have to 25 provide an address of the direct support node associated with the problem since this addressing will be accomplished automatically merely by the user initiating the trouble ticket. Since the database interface 44 is coupled to the communication program 48 and monitors changes made to records in the local database, a person entering data in local database 46 need only change the ownership field in a trouble 30 ticket in order to initiate trancmicsion of the record to the appropriate supporting node. It is contemplated that the user can be coupled by the communication network to a variety of different support nodes which support different products.
FIG. S illustrates an exemplary directory structure, preferably associated with each node, in accordance with the present invention, in order to facilitate35 communications. Node directory 56 is the highest level directory which interacts with communication network 27 to receive communications from the network which 7 20~4G57 are addressed to the node and to transmit co~ nfications to another node in the network. Subdirectory BIN 58 contains the co-"""lllication program 60 in accordance with the present invention. The communication program 60 is explained, especially with regard to the flow diagram of FIGs. 8 and 9. Subdirectories 62, 64, 5 and 66 each have symmetrical file structures. Each of these subdirectories contains a structure in which one allocated subdil~cloly is maintained for each node in thesystem. Each record received by node directory 56 is placed under IN directory 62 and the subdirectory which corresponds to the node which tr~n~mittecl the record.
These files are periodically scanned by the database interface 44 to check for 10 received files. Received standardized records are tr~n~l~te~l utilizing the database interface 44 and then stored in the local database of the node. To transmit a record stored in the local database 46 of the node, the record is t~nsl~te~l by the database interface 44 and a copy of the standardized record placed in the corresponding subdirectory of the destination node under OUT directory 64. The colllmullication 15 program 60 periodically scans the files in the OUT subdirectories and transmits the records via node directory 56 to the destination node in communication network 27.
After the tr~n~mi~sion of the outbound record, a duplicate copy of the record isplaced in a corresponding subdirectory under HOLD directory 66; the tr~n~mitted record in the subdirectory under OUT directory 64 is deleted. If an 20 acknowledgement is not received from the destination node within a predetermined time, an attempt to retransmit the record is lepcated from the subdil~;loly under HOLD directory 66.
FIGs. 6 and 7 illustrate the status of p~alllete,~, associated with a record relative to nodes 12, 22, and 26 of FIG. 1 at time intervals T0, T1, T2, T3, and T4.
25 The state of the parameters shown in FIGs. 6 and 7 reflect states at the end of each interval. Time T0 corresponds to user node 12 creating a new record indicative of a problem. A unique ticket number which also identifies the originating node is assigned, i.e. UN 12-1487. User node 12 is also identified as the originator andowner of the trouble ticket; note the originator and owner rows in FIG. 6. The status 30 of the trouble ticket is "open". In the illustrative example the record was created and entered in the local database of node 12 without causing the record to be transmitted as a trouble ticket to direct support node 22. This indicates that records may be opened and potentially closed by the originating user if the user determines a solution or otherwise decides that a trouble ticket is not to be generated. Thus the 35 user's database can store records that are not trouble tickets.

-8- 209~7 Assuming that node 12 now wishes to colllmullicate the stored record as a trouble ticket for direct support node 22, a person at node 12 will load the stored information from the local (i~t~h~ce 46 into database interface 44 which includes the pararneters as shown. The owner is changed from node 12 to node 22. The 5 ownership parameter identifies the node from which help is sought. The ownership of a given ticket may change from time to time depending upon the node from which help is sought. User node 12 always remains the originator and the ticket number is never changed during the commllnication of records from node to node. This allows each trouble ticket to be assigned a sequential number by each node. At user 10 node 12, the record is placed in node 22 of the OUT directory 64 for trancmicsion to node 22 by the con~ unication program. Upon receiving the record at node 22, it is placed under IN directory 62 in the subdirectory corresponding to user node 12. It is then transferred to the local rl~t~h~ce 46 of node 22. Thus, following the successful completion of the tr~ncmiccion~ the identical record will exist at nodes 12 and 22.
In this example, a service provider at node 22 is unable to handle the problem associated with ticket UN 12-1487 and makes a determination that the ticket should be escalated to node 26 for additional help from the technical experts in problem solving. At node 22, the record is retrieved from the local database into the database interface and the ownership changed from node 22 to node 26. Node 22 20 transmits the record at time period T2 to node 26 in a similar manner explained as for the tr~ncmicsion from node 12 to node 22. In addition, node 22 transmits theupdated record to node 12 so that all nodes in the network will maintain identical data for each ticket. Each node in the network maintains an address table which identifies the node from which it received each trouble ticket and thus, permits a 25 daisy-chain addressing by which updated tickets are tr~ncmittçd to the nodes which contain corresponding stored records. Node 26 receives the record and stores it in its local database. Preferably, upon receipt of each ticket at each node, a corresponding e-mail message is gencldted to the person at the node associated with handling such tickets. Thus, at the end of time interval T2, nodes 12, 22, and 26 will each contain 30 an identical copy of the ticket in each's database.
After considering the substance of the problem indicated in the ticket, node 26 may make a determination of the cause of the problem and provide a solution. The docll"~f~ tion for the problem cause and the proposed solution will be included as updated information to the ticket during time interval T3 and the35 status changed by node 26 from "open" to "solved". Node 26 initiates an update tr~n~mission of the ticket to node 22 which in the daisy-chain manner retransmits the 2~94~57 g updated ticket back to the originating node 12. It will also be noted that at time interval T3 the owner is changed from node 26 to user node 12, indicating that further disposition of the problem ticket with the proposed solution rests with the user at node 12.
The user at node 12 considers the proposed solution and accepts the solution proposed. During time interval T4, the user at node 12 changes the status of the message from solved to closed and transmits the updated record to node 22 which in daisy-chain manner transmits the message to node 26. As illustrated in time T4, each of the nodes communicating relative to the illustrative trouble ticket 10 will contain an identical record which indicates the status of the ticket is closed thereby ending further problem solving consideration of the item by direct support providers at node 22 and the technical experts at central support node 26. The record can be m;~int~ined in the local ~l~t~ba~e of the respective nodes and utilized for other related problems should similar problems occur, the record can also be used for 15 statistical data purposes.
FIG. 8 is a flow diagram illustrating steps in the tr~n~mi~sion of a record to another node. Beginning at START 68, the record to be tr~n~mi~ed is loaded from the local database to the standard record format of the d~t~h~e interface 44 as indicated by step 70. It will be understood by those skilled in the art that the record 20 may also be directly entered by the user into the database interface as well as being retrieved from storage in the local database. In step 72 the user requests tr~n~mi~sion of the record to another node such as by changing the ownership of the record. The address of the destination node is determined in step 74. In a preferred embodiment of the present invention, the destination is dete~ ed from an 25 originating node based upon a stored table which correlates the address of the node which services the equipment identified by the trouble ticket. Alternatively, the user at the originating node can directly enter the address of the node from which help is sought. Next, a copy of the trouble ticket is placed in the destination node (DN) subdirectory under the OUT directory. In accordance with the col~llllunication 30 program, a predetermined time interval can be utilized in which to check for multiple records to be transmitted to the same destination. Step 78 represents that the record is held waiting for an OUT tr~n~mi~sion cycle to be started. At the end of the cycle, the record is sent to the destination node, as indic~ted in step 80 through commullication network 27. In step 82 a copy of the transmitted record is placed in 35 the destination node subdirectory under the HOLD directory. In decision step 84 a determination is made if an acknowledgement has been received from the destination 2~94~S7 node within a predetermined time. If NO, control transfers to the beginning of step 78 to initiate a retr~nsmicsion of the record. Upon a YES determination by step 84, the record stored in the destin~tion node subdirectory under HOLD is deleted since a retr~nsmi~sion will not be required. The tr~n~mi~sion step terminates 5 at END 88. Thus, in accordance with the tr~n~mission according to the present invention, a trouble ticket or record is tr~n~mittecl to another node in standardized record format based upon a corresponding local database record format.
FIG. 9 is a flow diagram illustrating steps in accordance with the present invention for receiving a record transmitted from another node. Beginning at 10 START 90, the general node directory 56 receives a record addressed for the subject node as indicated in step 92. In step 94 the received record is put under the N
directory in the SUbdil~C~OI,y of the node which tr~n~mitte~l the record. In step 96 the record is copied from the subdirectory under the IN directory to the database interface 44 as a standardized record format. In step 95 an acknowledgement is sent 15 to the node which tr~nsmitte~l the record acknowledging its successful receipt. In step 98 the database 46 is updated by the d~t~bace interface 44 tr~nsl~ting the standardized record format and storing the record in the local database 46. A
determination is made in step 102 of whether to transmit the record to another node.
This decision is based upon the destination contained with the record and the owner 20 of the record. For example, if an originating node identifies the owner as a node other than an interm~li~te node which receives the record, the intermediate node will recognize the need to transmit the record to the designated owner. Upon a YES
determination by step 102, control passes as indicated by transfer point "A" 104 back to step 74 as shown in FIG. 8. The transmission then continues as previously 25 explained with regard to FIG. 8. A NO determination by step 102 indicates that further tr~n~mission is not required and concludes the receipt of the record at END 106.
In accordance with the present invention, a user friendly communication system is provided in which all nodes in the system requiring access to a record30 m~int~in~ the record in a local database. Subsequent updates of the record by any node are automatically distributed to the other nodes by utilizing a standardized record format. Thus, the present invention provides an enhanced col~ unication system allowing independent d~t~ba~e flexibility while still providing the relevant nodes in the network with up-to-date records.

Although an embodiment of the present invention has been described and shown in the drawings, the scope of the invention is defined by the claims which follow.

Claims (14)

1. A communication system comprising:
first and second nodes coupled to each other;
first and second databases associated with said first and second nodes respectively, each store records, said first database storing said records in a first field format and said second database storing said records in a second field format which is different from said first field format;
means at said first and second nodes for transmitting records having standardized format to and receiving records having standardized format from theother of said first and second nodes, said standardized format being different from said first and second field formats;
means at said first node for automatically translating a received standardized format record into said first field format record for storage in said first database and for automatically translating a first field format record stored in said first database into standardized format record for transmission to said second node;
means for independently identifying an originator and an owner of each record, said translating and transmitting means acting to translate and transmit a first record contained in said first database associated with said first node to said second database associated with said second node based upon entry in said first record of an owner associated with said second database, wherein records in saidfirst database that do not identify an owner are not transmitted to said second database;
said identifying means permitting the identified owner of a duplicate record stored at the second database and corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed ownership to be automatically transmitted to a database associated with the changed owner.
2. The system according to claim 1, further comprising a plurality of other nodes in addition to said first and second nodes, said other nodes comprising:
a database;
means for transmitting standardized format records and receiving standardized format records; and means for automatically translating a received standardized format record into its field format record for storage in its database and for automatically translating a record stored in its database into a standardized format record for transmission to one of said first, second, and other nodes.
3. The system according to claim 1, further comprising means associated with said second node for automatically transmitting a copy of an updated first record based on the original record from said second database to the firstdatabase containing the corresponding original record, said first database storing said updated first record.
4. The system according to claim 1, further comprising means for labelling each record at its creation with a unique identification number which identifies all corresponding records in the communication system.
5. A first node for use in a communications system having a plurality of nodes, said first node comprising:
first database that stores records in a first field format;
means for transmitting records having standardized format to and receiving records having standardized format from one of said nodes, said standardized format being different from said first field format;
means for automatically translating a standardized format record into said first field format for storage in said first database and for automaticallytranslating a first field format record stored in said first database into a standardized format record for transmission to one of said nodes;
means for independently identifying an originator and an owner of each record, said translating and transmitting means acting to translate and transmit a first record contained in said first database associated with said first node to a second database associated with a second node based upon entry in said first record of an owner associated with said second database, wherein records in said first database that do not identify an owner are not transmitted to said second database;
said identifying means permitting the identified owner of a duplicate record stored at the second database and corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed ownership to be automatically transmitted to a database associated with the changed owner.
6. The node according to claim 5, further comprising means for automatically sending records stored in the first database that have been modified to other nodes which contain corresponding records thereby keeping corresponding records at other nodes updated.
7. The node according to claim 5, further comprising means for labelling each record at its creation with a unique identification number which always identifies all corresponding records in other nodes in the communication system.
8. A method for handling records in a communications system which includes at least first and second nodes having first and second databases, respectively, said first database storing records in a first field format and said second database storing records in a second field format which is different from said first field format, said method comprising the steps of:
transmitting records having a standardized format from said first node and receiving records having a standardized format at said first node from said second node, said standardized format being different from said first and secondfield formats;
automatically translating a standardized format record received by said first node into said first field format record for storage in said first database and for automatically translating a first field format record stored in said first database into a standardized format record for transmission to said second node;
independently identifying an originator and an owner of each record, said translating and transmitting steps translating and transmitting a first record contained in said first database associated with said first node to said second database associated with said second node based upon entry in said first record of an owner associated with said second database, wherein records in said first database that do not identify an owner are not transmitted to said second database;
said identifying step permitting the identified owner of a duplicate record stored at the second database and corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed ownership to be automatically transmitted to a database associated with the changed owner.
9. The method according to claim 8, further comprising the step of automatically updating records stored in databases of other nodes upon a corresponding record being modified at one node in the communication system.
10. The method according to claim 8, further comprising the step of labelling each record at its creation with a unique identification number which identifies all corresponding records in other databases in the communication system.
11. The method according to claim 8, wherein said identifying step permits the owner of a corresponding set of records to be changed by any node which stores one of the corresponding records thereby allowing the responsibility for acting on the record to be changed.
12. A method for handling records by a node in a communications system having other nodes, said method comprising the steps of:
storing records using a first field format in a first database;
transmitting records having a standardized format to and receiving records having a standardized format from said other nodes, said standardized format being different from said first field format;
automatically translating a standardized format record received from one of said other nodes into a first field format record and storing said translated record in said first database;
translating a first field format record stored in said first database into standardized format record and transmitting said standardized record to at least one of said other nodes;
independently identifying an originator and an owner of each record, said translating and transmitting steps translating and transmitting a first record contained in said first database associated with said first node to said second database associated with said second node based upon entry in said first record of an owner associated with said second database, wherein records in said first database that do not identify an owner are not transmitted to said second database;
said identifying step permitting the identified owner of a duplicate record stored at the second database and corresponding to said first record to be changed thereby changing responsibility for acting on the duplicate record and causing the duplicate record with changed ownership to be automatically transmitted to a database associated with the changed owner.
13. The method according to claim 12, further comprising the step of automatically sending records stored in the first database that have been modified by a user to other nodes which contain corresponding records thereby keeping corresponding records at other nodes updated.
14. The method according to claim 12, further comprising the step of labelling each record at its creation with a unique identification number which identifies all corresponding records in other nodes in the communication system.15. The method according to claim 12, wherein said identifying step permits the owner of a corresponding set of records to be changed by a node which stores one of the corresponding records thereby allowing the responsibility for acting on the record to be changed.
CA002094657A 1992-08-31 1993-06-22 Communication system links different independent databases and provides automatic updating of corresponding records in the databases Expired - Fee Related CA2094657C (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US937,814 1992-08-31
US07/937,814 US5446880A (en) 1992-08-31 1992-08-31 Database communication system that provides automatic format translation and transmission of records when the owner identified for the record is changed

Publications (2)

Publication Number Publication Date
CA2094657A1 CA2094657A1 (en) 1994-03-01
CA2094657C true CA2094657C (en) 1997-09-16

Family

ID=25470447

Family Applications (1)

Application Number Title Priority Date Filing Date
CA002094657A Expired - Fee Related CA2094657C (en) 1992-08-31 1993-06-22 Communication system links different independent databases and provides automatic updating of corresponding records in the databases

Country Status (4)

Country Link
US (1) US5446880A (en)
EP (1) EP0586157A2 (en)
JP (1) JPH06161860A (en)
CA (1) CA2094657C (en)

Families Citing this family (85)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE9300671D0 (en) * 1993-03-01 1993-03-01 Sven Nauckhoff WORK FLOW MANAGEMENT
JPH07319917A (en) * 1994-05-24 1995-12-08 Fuji Xerox Co Ltd Document data base managing device and document data base system
US5627997A (en) * 1994-06-07 1997-05-06 Microsoft Corporation Method and system for converting computer mail messages using an extensible set of conversion routines
US5557790A (en) * 1994-06-21 1996-09-17 International Business Machines Corp. Facility for the generic storage and management of multimedia objects
US5694596A (en) * 1995-05-25 1997-12-02 Kangaroo, Inc. On-line database updating network system and method
US5680611A (en) * 1995-09-29 1997-10-21 Electronic Data Systems Corporation Duplicate record detection
WO1997019415A2 (en) 1995-11-07 1997-05-29 Cadis, Inc. Search engine for remote object oriented database management system
AU729275B2 (en) * 1995-12-30 2001-02-01 Tmln Royalty, Llc Data retrieval method and apparatus with multiple source capability
US6631382B1 (en) 1996-01-02 2003-10-07 Timeline, Inc. Data retrieval method and apparatus with multiple source capability
US6625617B2 (en) 1996-01-02 2003-09-23 Timeline, Inc. Modularized data retrieval method and apparatus with multiple source capability
US6119130A (en) * 1996-03-28 2000-09-12 Oracle Corporation Method and apparatus for providing schema evolution without recompilation
US5768581A (en) * 1996-05-07 1998-06-16 Cochran; Nancy Pauline Apparatus and method for selecting records from a computer database by repeatedly displaying search terms from multiple list identifiers before either a list identifier or a search term is selected
US5884310A (en) * 1996-06-14 1999-03-16 Electronic Data Systems Corporation Distributed data integration method and system
US5832514A (en) * 1996-06-26 1998-11-03 Microsoft Corporation System and method for discovery based data recovery in a store and forward replication process
US5890163A (en) * 1996-09-26 1999-03-30 Compaq Computer Corp Sharing an electronic mail message with a party not named as a recipient of the message
GB9623472D0 (en) * 1996-11-12 1997-01-08 Int Computers Ltd Data transfer mechanism
US6457012B1 (en) * 1997-06-10 2002-09-24 Pitney Bowes Inc. Method and system of updating address records utilizing a clientserver interface
KR100575956B1 (en) * 1998-05-14 2006-08-30 삼성전자주식회사 Generation of Standardized Subscriber Information for Wireless Mobile Communication Service and Conversion into Specific Operator Information
US6560596B1 (en) * 1998-08-31 2003-05-06 Multilingual Domains Llc Multiscript database system and method
US6240169B1 (en) 1999-05-06 2001-05-29 Mediacom Telesystems, Inc. Communications protocol for least cost call routing system
US6947903B1 (en) * 1999-08-06 2005-09-20 Elcommerce.Com.Inc. Method and system for monitoring a supply-chain
JP4167359B2 (en) * 1999-09-30 2008-10-15 株式会社東芝 Data management system and data management method
US7069592B2 (en) 2000-04-26 2006-06-27 Ford Global Technologies, Llc Web-based document system
AU2001268167A1 (en) * 2000-06-02 2001-12-11 First To File, Inc. Computer-implemented method for securing intellectual property
US7225139B1 (en) * 2000-06-27 2007-05-29 Bellsouth Intellectual Property Corp Trouble tracking system and method
US20020065677A1 (en) * 2000-11-27 2002-05-30 First To File, Inc. Computer implemented method of managing information disclosure statements
US20020065675A1 (en) * 2000-11-27 2002-05-30 Grainger Jeffry J. Computer implemented method of managing information disclosure statements
US20020111824A1 (en) * 2000-11-27 2002-08-15 First To File, Inc. Method of defining workflow rules for managing intellectual property
US20020111953A1 (en) * 2000-11-27 2002-08-15 First To File, Inc. Docketing system
US20020072920A1 (en) * 2000-12-07 2002-06-13 Jeffry Grainger Computer implemented method of generating information disclosure statements
US20020065676A1 (en) * 2000-11-27 2002-05-30 First To File, Inc. Computer implemented method of generating information disclosure statements
US7024662B2 (en) 2001-03-14 2006-04-04 Microsoft Corporation Executing dynamically assigned functions while providing services
US20030061365A1 (en) * 2001-03-14 2003-03-27 Microsoft Corporation Service-to-service communication for network services
US7302634B2 (en) * 2001-03-14 2007-11-27 Microsoft Corporation Schema-based services for identity-based data access
US20030041065A1 (en) * 2001-03-14 2003-02-27 Mark Lucovsky Schema-based services for identity-based access to contacts data
US7171415B2 (en) 2001-05-04 2007-01-30 Sun Microsystems, Inc. Distributed information discovery through searching selected registered information providers
US7099871B2 (en) * 2001-05-04 2006-08-29 Sun Microsystems, Inc. System and method for distributed real-time search
US6950821B2 (en) 2001-05-04 2005-09-27 Sun Microsystems, Inc. System and method for resolving distributed network search queries to information providers
US6961723B2 (en) 2001-05-04 2005-11-01 Sun Microsystems, Inc. System and method for determining relevancy of query responses in a distributed network search mechanism
US6934702B2 (en) * 2001-05-04 2005-08-23 Sun Microsystems, Inc. Method and system of routing messages in a distributed search network
US7013303B2 (en) * 2001-05-04 2006-03-14 Sun Microsystems, Inc. System and method for multiple data sources to plug into a standardized interface for distributed deep search
US6792431B2 (en) * 2001-05-07 2004-09-14 Anadarko Petroleum Corporation Method, system, and product for data integration through a dynamic common model
US20030036462A1 (en) * 2001-08-20 2003-02-20 Sundaram Ravikumar Powered antithrombotic foot mobility device
US20040006594A1 (en) * 2001-11-27 2004-01-08 Ftf Technologies Inc. Data access control techniques using roles and permissions
US20040006564A1 (en) * 2002-06-28 2004-01-08 Lucovsky Mark H. Schema-based service for identity-based data access to category data
US9886309B2 (en) 2002-06-28 2018-02-06 Microsoft Technology Licensing, Llc Identity-based distributed computing for device resources
US7206788B2 (en) * 2002-07-30 2007-04-17 Microsoft Corporation Schema-based services for identity-based access to device data
US7856454B2 (en) 2002-12-20 2010-12-21 Siebel Systems, Inc. Data model for business relationships
US8538840B2 (en) * 2002-12-20 2013-09-17 Siebel Systems, Inc. Financial services data model
US8392298B2 (en) * 2003-03-04 2013-03-05 Siebel Systems, Inc. Invoice adjustment data object for a common data object format
US8473399B2 (en) * 2003-03-04 2013-06-25 Siebel Systems, Inc. Invoice data object for a common data object format
US7912932B2 (en) * 2003-03-24 2011-03-22 Siebel Systems, Inc. Service request common object
US20070208577A1 (en) * 2003-03-24 2007-09-06 Leon Maria T B Position common object
US9704120B2 (en) * 2003-03-24 2017-07-11 Oracle International Corporation Inventory balance common object
US7904340B2 (en) * 2003-03-24 2011-03-08 Siebel Systems, Inc. Methods and computer-readable medium for defining a product model
JP2006523353A (en) * 2003-03-24 2006-10-12 シーベル システムズ,インコーポレイティド Common common object
US8489470B2 (en) * 2003-03-24 2013-07-16 Siebel Systems, Inc. Inventory location common object
US8510179B2 (en) * 2003-03-24 2013-08-13 Siebel Systems, Inc. Inventory transaction common object
US20070226037A1 (en) * 2003-03-25 2007-09-27 Shailendra Garg Modeling of opportunity data
US8112296B2 (en) * 2004-05-21 2012-02-07 Siebel Systems, Inc. Modeling of job profile data
US7865390B2 (en) * 2004-05-21 2011-01-04 Siebel Systems, Inc. Modeling of employee performance result data
EP1866780A4 (en) 2005-03-30 2013-07-31 Welch Allyn Inc Communication of information between a plurality of network elements
US20060282470A1 (en) * 2005-06-10 2006-12-14 Hong-Lee Yu Determining compliance of a database architecture to an enterprise data standard
US9792351B2 (en) * 2005-06-10 2017-10-17 International Business Machines Corporation Tolerant and extensible discovery of relationships in data using structural information and data analysis
US7613711B2 (en) * 2005-06-14 2009-11-03 Microsoft Corporation Specification of a hierarchical authorization model for a DBMS—SQL language extensions
US20070019617A1 (en) * 2005-06-30 2007-01-25 Dell Products L.P. Method, system and apparatus for maintaining ownership of service calls within an organization
US20070038896A1 (en) * 2005-08-12 2007-02-15 International Business Machines Corporation Call-stack pattern matching for problem resolution within software
CA2665556A1 (en) * 2006-10-04 2008-04-17 Welch Allyn, Inc. Dynamic medical object information base
US8015223B1 (en) * 2008-05-19 2011-09-06 Sprint Communications Company L.P. System and method for the translation of telecommunications trouble tickets
CA2736150A1 (en) * 2008-10-22 2010-04-29 Intervet International B.V. Method of documenting animal treatment
WO2011011718A2 (en) 2009-07-24 2011-01-27 Welch Allyn, Inc. Configurable health-care equipment apparatus
USD635681S1 (en) 2010-07-22 2011-04-05 Welch Allyn, Inc. Patient-monitor housing
USD632397S1 (en) 2010-07-22 2011-02-08 Welch Allyn, Inc. Portions of a patient-monitor housing
USD671222S1 (en) 2010-07-22 2012-11-20 Welch Allyn, Inc. Module for a patient-monitor or the like
US9577892B2 (en) * 2013-04-06 2017-02-21 Citrix Systems, Inc. Systems and methods for providing monitoring in a cluster system
US11297139B2 (en) * 2015-05-29 2022-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for client side encoding in a data processing system
EP3639502A4 (en) * 2017-06-12 2020-11-25 Daniel Maurice Lerner Securitization of temporal digital communications with authentication and validation of user and access devices
US10154015B1 (en) * 2017-06-12 2018-12-11 Ironclad Encryption Corporation Executable coded cipher keys
US10171435B1 (en) * 2017-06-12 2019-01-01 Ironclad Encryption Corporation Devices that utilize random tokens which direct dynamic random access
WO2018231703A1 (en) * 2017-06-12 2018-12-20 Daniel Maurice Lerner Securitization of temporal digital communications via authentication and validation for wireless user and access devices
US10616192B2 (en) * 2017-06-12 2020-04-07 Daniel Maurice Lerner Devices that utilize random tokens which direct dynamic random access
US10536445B1 (en) * 2017-06-12 2020-01-14 Daniel Maurice Lerner Discrete blockchain and blockchain communications
US10645070B2 (en) * 2017-06-12 2020-05-05 Daniel Maurice Lerner Securitization of temporal digital communications via authentication and validation for wireless user and access devices
US10817506B2 (en) 2018-05-07 2020-10-27 Microsoft Technology Licensing, Llc Data service provisioning, metering, and load-balancing via service units
US11693726B2 (en) * 2020-07-14 2023-07-04 State Farm Mutual Automobile Insurance Company Error documentation assistance

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4135240A (en) * 1973-07-09 1979-01-16 Bell Telephone Laboratories, Incorporated Protection of data file contents
US4031512A (en) * 1975-05-29 1977-06-21 Burroughs Corporation Communications network for general purpose data communications in a heterogeneous environment
US4714995A (en) * 1985-09-13 1987-12-22 Trw Inc. Computer integration system
US4933846A (en) * 1987-04-24 1990-06-12 Network Systems Corporation Network communications adapter with dual interleaved memory banks servicing multiple processors
US5119465A (en) * 1989-06-19 1992-06-02 Digital Equipment Corporation System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure
US5276869A (en) * 1990-09-10 1994-01-04 International Business Machines Corporation System for selecting document recipients as determined by technical content of document and for electronically corroborating receipt of document
US5283887A (en) * 1990-12-19 1994-02-01 Bull Hn Information Systems Inc. Automatic document format conversion in an electronic mail system based upon user preference
US5329618A (en) * 1992-04-02 1994-07-12 Fibronics Ltd. Look-up table for a bridge in a data communications system
US5249231A (en) * 1992-05-04 1993-09-28 Motorola, Inc. Memory tagging for object reuse protection

Also Published As

Publication number Publication date
CA2094657A1 (en) 1994-03-01
EP0586157A2 (en) 1994-03-09
JPH06161860A (en) 1994-06-10
EP0586157A3 (en) 1994-04-20
US5446880A (en) 1995-08-29

Similar Documents

Publication Publication Date Title
CA2094657C (en) Communication system links different independent databases and provides automatic updating of corresponding records in the databases
US5559721A (en) Multi-media information transfer system
US5424724A (en) Method and apparatus for enhanced electronic mail distribution
US5625675A (en) Voice mail communication system
US5826034A (en) System and method for transmission of communication signals through different media
US5856978A (en) Message queuing distribution services for mail systems
CN100483386C (en) Information management system and method
EP0458717A2 (en) Method for automated transmission of failure of delivery message in a data processing system
GB2217067A (en) Intelligent network server
US5910179A (en) Method and system for transmitting data within a tree structure and receiving a confirmation or status therefor
JP2643664B2 (en) Facsimile mail delivery method
US6081588A (en) Method and apparatus for obtaining alternate delivery instructions for a fax document
GB2294566A (en) Low cost teleprocessing system
US5469498A (en) Post-delivery support system for private branch exchanges
US6882448B2 (en) Facsimile system, and facsimile terminal and format converter both for use in the system
US5999601A (en) Method and apparatus for distributed number qualification
JP3208115B2 (en) Facsimile communication network system and communication method
EP1109367A2 (en) An electronic mail synchronizing device
US20050108316A1 (en) Methods and systems for organizing related communications
JPS6126107B2 (en)
JP3913791B2 (en) Data processing system
Tuck Using ISDN for document delivery
EP0892354B1 (en) Efficient representation and transmission of objects with variants
AU659032B2 (en) Method for joining a plurality of networks and seceding therefrom
JPS6126105B2 (en)

Legal Events

Date Code Title Description
EEER Examination request
MKLA Lapsed