EP0671694A1 - System zum Integrieren des Wissens mehrerer Rechnergrafiksysteme - Google Patents

System zum Integrieren des Wissens mehrerer Rechnergrafiksysteme Download PDF

Info

Publication number
EP0671694A1
EP0671694A1 EP95301288A EP95301288A EP0671694A1 EP 0671694 A1 EP0671694 A1 EP 0671694A1 EP 95301288 A EP95301288 A EP 95301288A EP 95301288 A EP95301288 A EP 95301288A EP 0671694 A1 EP0671694 A1 EP 0671694A1
Authority
EP
European Patent Office
Prior art keywords
knowledge
information
computer system
request
primary
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.)
Withdrawn
Application number
EP95301288A
Other languages
English (en)
French (fr)
Inventor
Robert J. Fechter
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
AT&T Corp
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 AT&T Corp filed Critical AT&T Corp
Publication of EP0671694A1 publication Critical patent/EP0671694A1/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
    • G08G1/0969—Systems involving transmission of navigation instructions to the vehicle having a display in the form of a map

Definitions

  • This invention relates generally to computer graphics systems. More particularly, this invention relates to integrating information contained in a plurality of independent computer graphics systems.
  • a computer system defined as a primary system
  • secondary systems because these secondary computer systems offer the ability to perform tasks that the primary system does not have the ability to perform and which are needed in conjunction with the tasks performed by the primary system.
  • This multi-system operation generally requires the user to exit or suspend operation of the primary system, enter the secondary system, perform the desired task, exit the secondary system, reenter or resume operation of the primary system, and attempt to correlate the knowledge of the secondary system with the knowledge of the primary system.
  • the first secondary system can identify the best route from one point to another, and the second secondary system can identify the location of detours or closed roads.
  • a user of the primary system who wanted to find the best route between two points would need to exit the primary system and enter the first secondary system to identify the best route.
  • the user would then need to correlate the best route information obtained from the first secondary system with the map in the primary system.
  • the user would need to exit the primary system and enter the second secondary system for the information. Again, the user would then need to correlate the detour information with the map from the primary system and the best route information from the first secondary system.
  • the correlation of information from independent systems can become a difficult task.
  • the present invention is a system that integrates the knowledge domains of two or more computer graphics systems.
  • the knowledge domain of a system is defined to be the set of knowledge, information, or intelligence that the system knows how to process or operate on.
  • This invention enables multiple graphical computer systems that were independently developed and that deal with different knowledge domains to interact and effectively integrate their knowledge domains.
  • This invention enables the user of a primary computer graphics system to extend its knowledge domain to include the knowledge domain of other secondary computer graphics systems thereby increasing the utility of the primary computer system to the user.
  • Knowledge from the secondary computer systems can be displayed, queried, and have other operations performed on it from inside the primary system.
  • Knowledge domains may be integrated through knowledge domain integrators, which act as integrative intermediaries controlling and managing the flow of knowledge between systems.
  • the knowledge domain integrator allows knowledge from secondary systems to be displayed and managed through the user interface of the primary system thereby integrating the knowledge of multiple systems in one display.
  • This invention enables secondary systems to be invoked from inside the primary system (i.e. without exiting or suspending operation of the primary system), perform a desired task in the secondary system, and have the results of that task (e.g. request for the display of information) passed back to the primary system and displayed and manipulated on the screen of the primary system.
  • the secondary system is used through the user interface of the primary system with the knowledge of both systems integrated on the screen of the primary system.
  • Fig. 1 shows a schematic of the components of a computer system which can be used in accordance with the present invention.
  • Fig. 2 is a block diagram of the high level architecture of two computer systems in accordance with the present invention.
  • Fig. 3 shows a flow diagram of the functioning of the knowledge domain integrator of a primary system according to the present invention.
  • Fig. 4 shows a flow diagram of the functioning of the Retrieve function of the knowledge domain integrator.
  • Fig. 5 shows a flow diagram of the functioning of the Display function of the knowledge domain integrator.
  • Fig. 6 shows a flow diagram of the functioning of the Query function of the knowledge domain integrator.
  • Fig. 7 shows a flow diagram of the functioning of the Modify function of the knowledge domain integrator.
  • Fig. 8 shows a flow diagram of the functioning of the List function of the knowledge domain integrator.
  • Fig. 9 shows a flow diagram of the functioning of the Set Options function of the knowledge domain integrator.
  • Fig. 10 shows a flow diagram of the functioning of the knowledge domain integrator of a secondary system according to the present invention.
  • Fig. 11 is a block diagram of the high level architecture of three computer systems in accordance with the present invention.
  • Fig. 12 shows a map display in accordance with an example illustrative of the present invention.
  • Fig. 13 shows the map display of Fig. 11 with graphics which were obtained from secondary systems superimposed on the display.
  • Fig. 1 shows a computer system 100 which comprises a display monitor 101 for the display of graphical and textual information, a keyboard 102 for textual entry of information, a mouse 107 for the entry of graphical data, a computer processor 105, a memory 103 for the storage of data items, a printer 104 to produce hard copy output, and an external storage device 106 for the storage of data.
  • the computer processor 105 is connected to the memory 103, the display monitor 101, the keyboard 102, the mouse 107, the printer 104 and the external storage device 106.
  • Other graphical entry devices, such as a light pen can be substituted for the mouse 107.
  • the general purpose computer 100 may suitably be any one of the types which are well known in the art such as a mainframe computer, a minicomputer, a workstation, or a personal computer.
  • the computer processor contains program code to implement the invention.
  • FIG. 2 shows a block diagram of the high level architecture of two computer systems in accordance with the present invention.
  • a primary system (PS) 110 is shown comprising a primary system knowledge domain integrator 114 and a knowledge domain 116.
  • the knowledge domain 116 represents the primary system's set of knowledge, information, intelligence and algorithms that the primary system 110 operates on.
  • the knowledge domain integrator 114 manages the flow of information between systems, and will be discussed in more detail below.
  • a secondary system 120 also comprises a knowledge domain integrator 124 and a knowledge domain 126.
  • the primary system 110 is connected to the secondary system 120 by communications network 140 to allow the primary system 110 to request and receive information from the secondary system 120.
  • the communication between the primary system 110 and the secondary system 120 is controlled by the knowledge domain integrators 114, 124.
  • the communication method may be of any type such that the primary system 110 and secondary system 120 can exchange information. Such communication methods include, without limitation, network links and shared memory. These methods could be readily implemented by one skilled in the art of data communications.
  • a user of the primary system 110 may request knowledge from secondary system 120 by sending a request for knowledge to the secondary system 120 over the communication network 140.
  • the secondary system 120 processes the request and passes back the knowledge in a set of one or more knowledge packets to the primary system 110 over the communications network 140.
  • a knowledge packet is a collection of graphical and/or textual information or knowledge.
  • a knowledge packet consists of knowledge packet atomics which are more elemental units of knowledge that are aggregated into a knowledge packet. This in effect gives a flexible hierarchical representation of knowledge as knowledge packet atomics grouped into knowledge packets which could be further grouped into other knowledge packets and so on.
  • a knowledge packet has a set of attributes which may include an identifier, type, description, source, date retrieved, date last modified, and contents of the data packet (i.e. information requested by a request).
  • Each system 110 and 120 has the ability to store, display, and generally manage graphics.
  • graphics refers to graphics and text in that text is just one type of graphics.
  • the technique of graphical superimposition is used to positionally associate graphics for related knowledge packets using a common coordinate system.
  • the primary system 110 and secondary system 120 must have common graphical representations or ones that can be cross mapped. If the primary system 110 and secondary system 120 have different coordinate systems and geometric representations, the knowledge domain integrators convert between them. This conversion is discussed below in conjunction with Fig. 4, and in particular step 302.
  • the primary system 110 must have the ability to transmit a request to and receive a response from the secondary system 120.
  • the secondary system 120 must have the ability to receive a request from the primary system 110, generate a response to the request, and transmit the response to the primary system 110.
  • Fig. 3 shows a flow diagram of the functioning of the knowledge domain integrator 114 of the primary system 110.
  • the functioning of the knowledge domain integrator 124 of the secondary system 120 is discussed below in conjunction with Fig. 10.
  • the knowledge domain integrator 114 is invoked from the primary system 110 in step 200.
  • the user selects a function in step 201.
  • the knowledge domain integrator 114 determines in step 202 if the user selected the Retrieve function, and if so, then it calls the retrieve function in step 203 (Fig. 4).
  • the knowledge domain integrator 114 determines in step 204 if the user selected the Display function, and if so, then it calls the Display function in step 205 (Fig. 5).
  • the knowledge domain integrator 114 determines in step 206 if the user selected the Query function, and if so, then it calls the Query function in step 207 (Fig. 6).
  • the knowledge domain integrator 114 determines in step 208 if the user selected the Modify function, and if so, then it calls the Modify function in step 209 (Fig. 7).
  • the knowledge domain integrator 114 determines in step 210 if the user selected the List function, and if so, then it calls the List function in step 211 (Fig. 8) .
  • the knowledge domain integrator 114 determines in step 212 if the user selected the Set Options function and if so, then it calls the Set Options function in step 213 (Fig. 9).
  • the knowledge domain integrator 114 determines in step 214 if the user selected Exit, and if so, then the knowledge domain integrator 114 is exited in step 215, else, go to step 201.
  • the retrieve function allows a user of the primary system 110 to request and retrieve information from the secondary system 120, and is described in conjunction with Figure 4.
  • the Retrieve function is entered in step 300.
  • a retrieve request is entered at step 301.
  • Such a request involves the identification of the secondary system 120 and the definition of secondary system retrieval parameters.
  • These retrieval parameters are passed to the secondary system 120 over communications network 140 as a request for knowledge, and the retrieval parameters define what knowledge is being requested and how the knowledge is to be communicated.
  • the retrieval parameters may define whether the information is returned by way of a file, shared memory, or some other communication method.
  • the retrieval parameters may also define the recipient(s) of the returned knowledge packet.
  • the request for knowledge could include a parameter which indicates that the knowledge packet returned from the secondary system 120 is to be sent to other systems, as well as, or instead of, the primary system 110.
  • the secondary system 120 processes the request for knowledge and creates a set of one or more knowledge packets which are passed to the primary system 110 and converted and stored by the primary system in step 302.
  • the secondary system 120 may define a line as: SEGMENT (X, Y), ( ⁇ X, ⁇ Y) where (X, Y) represents the X, Y coordinates of the starting point of the line, and the ending point coordinates are calculated as (X + ⁇ X , Y + ⁇ Y) .
  • ( ⁇ X, ⁇ Y) represents the ending point of the line relative to the starting point.
  • the primary system 110 may define a line as LINE (X1, Y1) , (X2, Y2) where (X1, Y1) is the absolute X, Y coordinates of the starting point of the line and X2, Y2 is the absolute X, Y coordinates of the ending point of the line.
  • the conversion in step 302 enables the primary system 110 to store the information received from the secondary system 120 in the primary system's native graphics format.
  • the conversion also enables the primary system 110 to display the information received from the secondary system 120 in the primary system's normal display mode.
  • the above example would require routine mapping techniques which could be readily implemented by one skilled in the art of computer graphics.
  • the secondary system's definition of SEGMENT (X, Y), ( ⁇ X, ⁇ Y) would be converted to the primary system's native format as LINE (X, Y), (X + ⁇ X, Y + ⁇ Y). Similar mappings may be required for other geometric constructs such as text, polygons, circles, etc. Coordinate system transformations may also be required. For example, dimensions may be represented differently in the two systems. Transformations such as miles to kilometers may be required. Such mappings and transformations could also be readily implemented by one skilled in the art of computer graphics.
  • the knowledge domain integrator 114 determines in step 303 if the display on retrieval option (options are discussed below in conjunction with Fig. 9) is set to yes, and if so, then it calls the Display function in step 304 (the Display function is discussed below in conjunction with Fig. 5).
  • the knowledge domain integrator 114 determines in step 305 if another retrieval request is desired, and if so, then it goes to step 301, otherwise it returns in step 306.
  • a list of one or more knowledge packets have been created which are stored within the primary system 110 and which can be operated on by the Display, Query, Modify, List, and Options capabilities described below.
  • the Display function is described in conjunction with Fig. 5.
  • the Display function is invoked at step 400.
  • a display request is entered at step 401.
  • the request may be to turn on or off the display of one or more knowledge packets which are stored in the primary system 110.
  • the knowledge packets which are stored in the primary system 110 are stored in the primary system's native graphics format.
  • the primary system has the ability to store and manage graphics. Part of this ability is to access each piece of graphics information individually. This ability is used to process the collection of stored KPs. Functions are implemented to control the display of the first, last, next, and previous KP in the requested list or among the entire domain of all KPs.
  • an entire list of KPs can be turned on or off in one request.
  • the display attributes, such as color, of the KP may be specified as well.
  • the knowledge domain integrator 114 determines in step 402 if the request is to display the first KP, and if so, then the first KP among the set requested is located and displayed in step 403. This displayed KP is defined as the current KP. All requests for a next or previous KP are made relative to the current KP. Each subsequently displayed KP becomes the current KP.
  • the knowledge domain integrator 114 determines in step 404 if the request is to display the next KP, and if so, it locates the next KP and displays it in step 405.
  • the knowledge domain integrator 114 determines in step 406 if the request is to display the last KP, and if so, it locates the last KP and displays it in step 407.
  • the knowledge domain integrator 114 determines in step 408 if the request is to display the previous KP, and if so, it locates and display the previous KP in step 409. If the first KP is the current KP then a request for the previous KP will result in a message that there is no previous KP.
  • the KP list could be implemented to wrap around from first to last and last to first. If this option were implemented, then a request for the next KP when the current KP is the last KP will result in the first KP. Similarly, a request for the previous KP when the current KP is the first KP will result in the last KP.
  • the knowledge domain integrator 114 determines in step 410 if the request is to display a list, and if so, it locates and displays each KP in the list in step 411.
  • the knowledge domain integrator 114 determine in step 412 if another display request is desired, and if so, then it goes to step 401, else it returns in step 413. If requested as an option (options are discussed below in conjunction with Fig. 9), as KPs are displayed graphically, a textual display may be created in a separate area of the display screen 101 that specifies each KP and its attributes.
  • the Query function is described in conjunction with Fig. 6.
  • the Query function is invoked at step 500.
  • the Query function enables the user of the knowledge domain integrator to point to a KP on the display screen 101 and request additional information. In this sense it represents a variation on the Retrieve function, which is used as part of the implementation of the Query function.
  • Query is easier and faster to use when additional information is required for an existing KP. By identifying the KP graphically and accessing its attributes in the primary system the request for additional information is made easier.
  • a query request is entered at step 502 by pointing to an existing KP on the display screen 101 using the mouse 107 or other suitable pointing device. The identified or pointed to KP is located in step 503.
  • the Retrieve function is called in step 504 with the specified KP as part of the parameters that are passed to the secondary system 120 as part of the request for additional information.
  • the response to the query will be constructed by appending the additional information to the original KP or a new KP will be created (see discussion of the secondary system knowledge domain integrator below, in conjunction with Fig. 10).
  • the knowledge domain integrator 114 determines in step 505 if another query is desired, and if so, then go to step 502, else return in step 506.
  • the Modify function is described in conjunction with Fig. 7.
  • the Modify function is invoked at step 600.
  • the Modify function allows the user to modify an existing KP shown on the display screen 101 using the graphical editing techniques described below.
  • a modify request is entered at step 601.
  • the knowledge domain integrator 114 determines in step 602 if move is requested, and if so, then any part or all of the graphics associated with a KP or group of KPs are moved in step 603.
  • the knowledge domain integrator 114 determines in step 604 if rotate is requested, and if so, then part or all of the graphics associated with a KP or group of KPs are located and rotated in step 605.
  • the knowledge domain integrator 114 determines in step 606 if delete is requested, and if so, then part or all of the graphics associated with a KP or group of KPs are located and deleted in step 607.
  • the knowledge domain integrator 114 determines in step 608 if change attribute is requested, and if so, then the attributes of part or all of the graphics associated with a KP or group of KPs are located and changed in step 609. This may include any graphical attributes (e.g. text height or line thickness).
  • the knowledge domain integrator 114 determines in step 610 if add is requested, and if so, a new KP is added or atomics are added to an existing KP in step 611.
  • An atomic may be any graphical object (circle, ellipse, line, polygon, text, etc).
  • the knowledge domain integrator 114 determines in step 612 if annotate is requested, and if so, then the KP textual attributes, such as description and type information, are annoted (added/edited) in step 613.
  • the knowledge domain integrator 114 determines in step 614 if another modify request is desired, and if so, then it goes to step 601, else it returns in step 615.
  • other well known graphical editing techniques could be implemented, such as cut and paste, and shrink and magnify.
  • the List function is described in conjunction with Fig. 8.
  • the List function is invoked at step 700.
  • the List function allows the user to perform various tasks on the list of KPs in the primary system 110.
  • a list request is entered at step 701.
  • the knowledge domain integrator 114 determines in step 702 if the request is list, and if so, then a list of all KPs is generated in step 703.
  • the knowledge domain integrator 114 determines in step 704 if the request is Report, and if so, then a customizable report of all KPs and their attributes (identification, type, description, source, date created, last date modified, etc.) is generated in step 705.
  • the report is customizable in that any subset of KP attributes can be requested to be included or excluded from the report.
  • the knowledge domain integrator 114 determines in step 706 if the request is Search, and if so, then a search of all the KPs is performed and a list and optionally a customizable report of the KPs matching the search conditions is generated in step 707. If the result of the search is one KP, then that KP becomes the current KP for Display function purposes. In the case of list, report, and search, the results can be sent to the display screen 101, printer 104, or external storage 106.
  • the knowledge domain integrator 114 determines in step 708 if another list request is desired, and if so, then it goes to step 701, else it returns in step 709.
  • the Set Options function is described in conjunction with Fig. 9.
  • the Set Options function is invoked at step 800.
  • An option request is entered at 801.
  • the knowledge domain integrator 114 determines in step 802 if the retrieval system options are selected, and if so, then the retrieval system options are set in step 803 for one or more secondary systems (e.g., default system identification and retrieval parameters). These options are defaults which may be overridden at the time a retrieve is requested.
  • the knowledge domain integrator 114 determines in step 804 if the display on retrieval option is requested, and if so, then the display on retrieval option is set on or off in step 805.
  • the knowledge domain integrator 114 determines in step 806 if the set default KP parameters is requested, and if so, then default KP parameters (e.g. id, type, description) are set in step 807.
  • the knowledge domain integrator 114 determines in step 808 if the report destination option is requested, and if so, then the report destination (e.g. screen 101, printer 104, external storage 106) is set in step 809.
  • the knowledge domain integrator 114 determines in step 810 if the textual display of KPs option is requested, and if so, then the KP textual display option is set on or off in step 811.
  • the knowledge domain integrator 114 determines in step 812 if another option request is desired, and if so, then it goes to step 801, else it returns in step 813.
  • the secondary system knowledge domain integrator 124 is discussed in conjunction with Fig. 10, which shows a flow diagram of the functioning of the secondary system knowledge domain integrator 124.
  • the secondary system knowledge domain integrator 124 is invoked from the secondary system 120 in step 1200.
  • the secondary system 120 receives a request for information in step 1201.
  • the requested information is located in the secondary system's knowledge domain 126 in step 1202.
  • the knowledge domain integrator 124 determines in step 1203 if the request was to append the requested information to an already existing knowledge packet. This would be an option if the primary system 110 requested the information from the secondary system 120 by using the Query function (discussed above in conjunction with Fig. 6).
  • Information specifying whether or not to append the requested information to an already existing KP would be passed as a retrieval parameter (discussed above in conjunction with Fig. 4). If the request was to append the information, then the requested information is appended to the existing KP, which was sent with the request for information, in step 1205. If there was not a request to append the requested information to an existing KP, then a new KP containing the requested information is created in step 1204. The KP containing the requested information is sent to the primary system 110 in step 1206 via communication network 140. The knowledge domain integrator 124 is exited in step 1207.
  • computer system 110 operates as only a primary system and computer system 120 operates as only a secondary system.
  • the primary system 110 could function as both a primary system by requesting information from other systems, and as a secondary system, by receiving requests for information from another system, processing those requests, and transmitting knowledge packets.
  • the secondary system 120 could function as both a secondary system by receiving requests for information from other systems, processing those requests, and transmitting knowledge packets, and as a primary system by requesting information from other systems.
  • Secondary system 920 comprises a knowledge domain integrator 924 and a knowledge domain 926.
  • the knowledge domain 926 of secondary system 920 contains information relating to the distances of routes between points and thus secondary system 920 is capable of determining the shortest distance route between two points.
  • Secondary system 930 also comprises a knowledge domain integrator 934 and a knowledge domain 936.
  • the knowledge domain 936 of secondary system 930 contains information relating to travel time, detours and accidents, and thus secondary system 930 is capable of determining estimated travel times and alternate faster routes.
  • Primary system 910 is connected to secondary system 920 by communications network 940 to allow the primary system knowledge domain integrator 914 to request and receive information from the secondary system knowledge domain integrator 924.
  • Primary system 910 is connected to secondary system 930 by communications network 945 to allow the primary system knowledge domain integrator 914 to request and receive information from secondary system knowledge domain integrator 934.
  • the invention will enable the user of the primary system 910 which displays maps to request the shortest route between two points from secondary system 920 without exiting the primary system 910.
  • the secondary system 920 will identify the shortest route, pass the route information back to the primary system 910 as a knowledge packet, and this information will be superimposed on the display screen 101 of the primary system 910.
  • the user can then request from secondary system 930 the estimated travel time and if there are any faster alternate routes, and that information may also be displayed on the screen 101 of the primary system 910.
  • three independently developed systems, 910, 920, 930 have their knowledge domains 916, 926, 936 integrated and presented to the user through the user interface of the primary system 910.
  • Fig. 12 shows an outline of a screen display 1002, within which there are various lines, 1005, 1006, 1007, 1008, 1009, 1010 representing roads on a map.
  • the user wants information on the shortest route between points A and B.
  • the shortest route between points A and B is the two line segment (X1,Y1) ⁇ (X2,Y2) ⁇ (X3,Y3).
  • secondary system 920 is capable is providing such information. The user would invoke the knowledge domain integrator 914 of primary system 910 in order to access the knowledge domain 926 of secondary system 920.
  • the user of the primary system 910 invokes the knowledge domain integrator 914, and enters a retrieve request.
  • the retrieve function is discussed above in conjunction with Fig. 4.
  • the primary system 910 passes a request 950 to secondary system 920 over communication network 940 requesting the shortest distance route from point A to point B.
  • Secondary system 920 invokes its knowledge domain integrator 924 (discussed above in conjunction with Fig. 10) and receives the request, locates the requested information and transmits a knowledge packet 952 over communication network 940.
  • the knowledge packet 952 contains two atomics 953 and 954 representing the two line segments which portray the shortest distance route between points A and B. As discussed above in conjunction with Fig.
  • the knowledge packet 952 passed back to primary system 910 may contain information expressed in a format which is not the native graphics format of the primary system 910. In this situation, the information must be converted to the format native to primary system 910. Once the information is converted into a format recognized by the primary system 910, the knowledge packet is stored in the primary system as shown at 955.
  • This information may then be displayed on the display screen 101 of the primary system 910 by using the Display function, discussed above in conjunction with Fig. 5.
  • the user of the primary system 910 would request that KP1 955 be displayed on the display screen 101 superimposed over the map shown in Fig. 12.
  • the result of the request is shown in Fig. 13.
  • Bold line 1102 represents the shortest route between points A and B as retrieved from secondary system 920 in KP1 952 and converted and stored in primary system 910 as KP1 955.
  • the user could then use the Query function, discussed in conjunction with Fig. 6, to request estimated travel time and alternate faster routes from secondary system 930.
  • the user would point to line 1102 on the computer screen 101, using for example the mouse 107 or other suitable pointing mechanism.
  • This line 1102 represents KP1 955 stored in primary system 910.
  • primary system 910 will send a request to secondary system 930, requesting estimated travel time between points A and B and alternate faster routes.
  • KP1 is sent to secondary system 930 as part of the request for information.
  • This request for knowledge is represented in Fig. 11 at 960.
  • Secondary system 930 will invoke its knowledge domain integrator 934 (discussed above in conjunction with Fig.
  • KP2 962 relates to route (X1,Y1) ⁇ (X2,Y2) ⁇ (X3,Y3) and contains two KP atomics 963 and 964. These KP atomics indicate that there is an accident along the route and that the travel time is 60 minutes.
  • KP3 970 relates to an alternate identified route (X1,Y1) ⁇ (X4,Y4) ⁇ (X3Y3) and contains three KP atomics 971, 972, 973.
  • KP atomics 971 and 972 specify the two line segments which represent the alternate route
  • KP atomic 973 specifies text related to the alternate route which indicates 30 minutes travel time.
  • secondary system 930 uses the same graphics format of primary system 910, there is no need to convert the graphics descriptions in the knowledge packets 962 and 970.
  • the knowledge packets 962 and 970 are stored in the primary system 910 as shown at 965 and 966 respectively.
  • the user of the primary system 910 could then invoke the Display function (discussed above in conjunction with Fig. 5) to display the knowledge packets 965 and 966.
  • the result would be as shown in Fig. 13 where an accident is identified at point X5Y5, the travel time of 60 minutes is displayed at 1104, and the dotted line alternate route 1106 between points A and B is displayed with the travel time shown as 30 minutes 1108.
  • three independently developed systems, 910, 920, 930 have their knowledge domains 916, 926, 936 integrated and presented to the user through the user interface of the primary system 910.
EP95301288A 1994-03-08 1995-02-28 System zum Integrieren des Wissens mehrerer Rechnergrafiksysteme Withdrawn EP0671694A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US20797794A 1994-03-08 1994-03-08
US207977 1994-03-08

Publications (1)

Publication Number Publication Date
EP0671694A1 true EP0671694A1 (de) 1995-09-13

Family

ID=22772742

Family Applications (1)

Application Number Title Priority Date Filing Date
EP95301288A Withdrawn EP0671694A1 (de) 1994-03-08 1995-02-28 System zum Integrieren des Wissens mehrerer Rechnergrafiksysteme

Country Status (2)

Country Link
EP (1) EP0671694A1 (de)
JP (1) JPH07302329A (de)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2187009A (en) * 1986-02-21 1987-08-26 Hitachi Ltd A knowledge-based system having a plurality of processors
EP0471442A2 (de) * 1990-08-14 1992-02-19 Digital Equipment Corporation Verfahren und Gerät zur Realisierung von Anbieterfunktionen in einer verteilten heterogenen Umgebung
WO1992004683A1 (en) * 1990-09-12 1992-03-19 Motorola, Inc. Land vehicle navigation apparatus with visual display

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2187009A (en) * 1986-02-21 1987-08-26 Hitachi Ltd A knowledge-based system having a plurality of processors
EP0471442A2 (de) * 1990-08-14 1992-02-19 Digital Equipment Corporation Verfahren und Gerät zur Realisierung von Anbieterfunktionen in einer verteilten heterogenen Umgebung
WO1992004683A1 (en) * 1990-09-12 1992-03-19 Motorola, Inc. Land vehicle navigation apparatus with visual display

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INOUE T ET AL: "In-vehicle information systems and semiconductor devices they employ", IEICE TRANSACTIONS ON ELECTRONICS, DEC. 1993, JAPAN, vol. E76-C, no. 12, ISSN 0916-8524, pages 1744 - 1755, XP000426736 *

Also Published As

Publication number Publication date
JPH07302329A (ja) 1995-11-14

Similar Documents

Publication Publication Date Title
US7043357B1 (en) Extensible navigation systems
US8195389B2 (en) System and method of wireless downloads of map and geographic based data to portable computing devices
US5904727A (en) Graphical fleet management methods
EP2463627B1 (de) Navigationssystem, welches Korridorkarten verwendet
US7272492B2 (en) Path planning for mine countermeasures
US6026384A (en) Cost zones
CA2583036C (en) Method and system for distribution of map content to mobile communication devices
US20040085318A1 (en) Graphics generation and integration
US20060058952A1 (en) System and method of wireless downloads of map and geographic based data to portable computing devices
US20060080031A1 (en) System and method of wireless downloads of map and geographic based data to portable computing devices
US20060058951A1 (en) System and method of wireless downloads of map and geographic based data to portable computing devices
US7023452B2 (en) Image generation system, image generating method, and storage medium storing image generation program
US20040210386A1 (en) System for communicating and associating information with a geographic location
EP1426876A1 (de) Geographisches Informations-System
CN105359189A (zh) 使用地图数据差别瓦片来迭代地向客户端设备提供地图数据
CN108731692A (zh) 用于提供地图数据的装置和方法及其系统
JP3437055B2 (ja) 地理情報提供システム
JP2003329474A (ja) 車載装置、情報端末装置及び車載情報システム
JPH08285613A (ja) 情報集中管理型ナビゲーションシステム
WO2004084437A1 (en) Navigation system using mobile device and method thereof
KR100650274B1 (ko) 이동 통신 단말기를 이용한 네비게이션 시스템 및 방법
JPH11271068A (ja) 地図情報表示装置、地図情報表示方法、及び記録媒体
EP0671694A1 (de) System zum Integrieren des Wissens mehrerer Rechnergrafiksysteme
JP6940897B1 (ja) 巡回支援システム、巡回支援方法、及び、巡回支援プログラム
WO2022161309A1 (zh) 基于电子地图的交互方法、装置、电子设备、计算机可读存储介质及计算机程序产品

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FR GB IT NL

17P Request for examination filed

Effective date: 19960229

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Withdrawal date: 19990701