TW490639B - A software component-container framework for dynamic deployment of business logic components in a distributed object environment - Google Patents

Abstract

This application pertains to multi-tiered, distributed computing systems and, more specifically, is directed to a component container middleware framework for dynamic deployment of business logic software components on a CORBA distributed object infrastructure. Each server container includes a configuration file which is read upon initializing the container. The container process loads software components as specified in the configuration file, and the configuration file includes information on names and locations of components creators, and defines relationships among components. The configuration file, expressed in XML syntax, makes it easy to deploy or update business logic components without exposing system source code, while maintaining a robust, scalable distributed system for demanding applications like supporting travel web sites.

Description

490639 Printed by the Consumer Property Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs A7 B7 V. Description of Invention (/) Related Applications This application is US Provisional Application Nos. 60 / 156,499 and 2000 filed on September 28, 1999 Continuation of application No. 60 / 184,945 filed on February 25 and claims priority. The field of application This application relates to a multi-layer, distributed computer system, and more particularly to a component synthesizer intermediary software architecture for the dynamic configuration of business logic software components on a CORBA distributed object structure. The online travel of the present invention is one of the largest single e-commerce types today. The first generation of travel websites, roughly built between 1994 and 1996, are full of pictures and photos describing travel destinations and packages. These must be basic online manuals or "instructions" and lack interaction. Websites are difficult to maintain and consist of static content. Online reservations started around the second generation of travel websites around 1996. Many airline websites and virtual travel agencies have introduced booking services for aircraft, hotels, and car rental. This is the first time that an individual has access to information in advance through a travel agency only. A trend of interest develops, but profitability remains elusive due to the cost of access reservation systems such as Apollo and SABRE, high maintenance costs, and commission ceilings. As a result, the number of "viewers" maintained a high ratio to the number of "bookers". The third-generation tourism website displayed today is different from the original one in that it offers a high degree of humanity. Modern travel websites present dynamic content based on information volunteered by millions of users. The webpage is dynamically displayed on the member 槪 3 This paper size is applicable to the Chinese National Standard (CNS) A4 specification (210 X 297 mm) (Please read the precautions on the back before filling this page) 0 ϋ β ϋ ϋ in ϋ I n I ϋ n «ϋ II ϋ n · ϋ« ϋ ϋ · ϋ ί ί ϋ I ϋ ϋ n ϋ-^ 1 II ϋ _ 490639 ______B7___ 5. Information of the invention ()). Such conditions can include domestic airports, reserved seats, general destinations, status of membership grants, etc. For computer programmers and builders designing such systems, supporting all such interactivity and the load imposed by thousands of simultaneous users is a challenge. The present invention refers to a "intermediary software" architecture, that is, software located between a website and a computer reservation system such as SABRE. Such a system must be robust, scalable, and reliable. In particular, such a system should provide its users with, for example, the ability to integrate with travel website systems, quickly modify its own business logic software, and quickly and easily launch new business logic objects. If you can separate functional modules and develop simple and flexible components to introduce such functional modules to the reservation system, system integrators will be able to provide customers with a more powerful and effective interface, reducing their development and maintenance costs. . The common objects defined by the Object Management Group (OMG) require an intermediary architecture, CORBA, which is a protocol definition used to communicate between systems of different origins. CORBA allows systems to communicate using different hardware, operating systems, and programming languages. CORBA allows interaction between those systems that are defined in a platform-independent manner, giving the system a well-defined set of interfaces. Therefore, CORBA provides a distributed computer architecture. The invention is best implemented on a CORBA platform. Traditionally, a CORBA server, for example, a simple, executable program, contains all the different components that a user or customer may need. Executables are often difficult to code and compile. A copy of the compiled executable is provided to each server in the system. Therefore, to update the software or introduce new components, the 4 paper sizes are applicable to the Chinese National Standard (CNS) A4 specification (210 X 297 mm) (Please read the precautions on the back before filling this page); 0 Ministry of Economic Affairs Wisdom Printed by the Property Agency Staff Consumer Cooperative

One: ° J »ϋ ϋ nn I l · ϋ II m-I--I—-SI- — —----n:--11 n I i I!!:--I 490639 A7 _____________ B7 V. Description of the Invention (3) The code must be modified or recompiled, and then the new executable file is distributed via an appropriate server. This is a time-consuming and expensive process. "Plug and play" is the required form of solution that allows integrators to quickly and easily introduce new components to a distributed system without compromising system scalability and performance. Summary of the Invention One general aspect of the present invention relates to a multi-layer, distributed computer system, and more particularly to a component synthesizer intermediary software architecture that dynamically configures business logic software components in a CORBA distributed object structure. The present invention describes by way of example, but not limitation, such a system for realizing tourism planning and booking 'to show its remarkable characteristics. This system allows consumers to use a web browser and connect via the Internet to investigate options that include flight departures (also like hotel rooms, car rentals, etc.) and to actually register their unique reservations, such as , Buy tickets online. This booking engine is built on top of a unique CORBA architecture. The "intermediary software" architecture is the basic component of the flexibility, scalability, and supervisory capabilities of this travel system. These same services can be performed by programmers and can coexist with existing systems for new businesses in the travel system or even individual applications Therefore, in practical application, the present invention allows a system integrator to easily develop new business rules or logic to a strong, flexible, or new system without having to rebuild the system or even access the resource code of the existing system. Scalable distributed system. The architecture of the present invention is based on a component synthesizer (container) model. The architecture includes a standard "synthesizer" that can contain components. The synthesizer 5 paper standards are applicable to Chinese national standards (CNS ) A4 size (210 X 297 mm) (Please read the notes on the back before filling out this page) ·· Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs ·-II — — — — — — — — — — — — — — — — — — — — — — 490639 A7 B7 V. Description of the Invention (Medium) It is best to be a general CORBA server, which is based on The structure file can load one or more components. When the synthesizer is started, the synthesizer automatically reads the structure file and loads the components listed in the structure file. The component is obtained from the architecture base class. Program The designer added to the synthesizer's structure file (explained later) to achieve the desired function in the composition object and load the result object into the synthesizer. This component is executed in a shared database mode, so the synthesis The synthesizer can load these components at runtime without recompiling or linking to a general server synthesizer. Figure 2 describes how the synthesizer and components are installed together, which will be explained in more detail below. General Servo The synthesizer provides multiple sets of services to the components it contains. These services alleviate many of the burdens that arise from processing the details required for load balancing, monitoring procedures, architecture, login, and threading to create objects. Description services that can be provided by the general server and component base classes include the following: • Read XML structure files • Load components based on this structure file • Establish links between components listed in the structure file • Set according to the characteristics of the components of the structure file • Three different threading modules for the component • Announcements and consumption items • Login • Allows the supervision of components and synthesizers Management functions • Collection and announcement statistics of components 6 (Please read the notes on the back before filling out this page) Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs I-· ϋ -1 n ϋ n .1 ϋ ^ OJ · ϋ ϋ -ϋ H ϋ ϋ n I ϋ -ϋ I ϋ III ϋ nn ϋ This paper size applies to China National Standard (CNS) A4 (210 X 297 mm) 490639 A7 B7 V. Description of the invention (t) • Component library • Transaction In addition, the new architecture enables higher-level services built on top of general server and component models. These higher-level services can include, for example, a transaction service coordinated especially for load balancing, and a file server for storing, querying, and persisting XML files for status management. In this way, the new architecture allows programmers to focus on building the business logic of components without having to worry about the myriad details required to build robust and scalable systems. A general server synthesizer implements many of these services for any component, that is, it does not include special properties in the component, but only inherits from the architectural base class. The invention can thus be described as an organized intermediary software architecture, including a client-level interface, a synthesizer process to support one or more business objects or components, and a resource interface, such as an interface to an existing computer reservation system. The synthesizer process has access to a structure file and can read XML to organize the synthesizer process at execution time to include specific components in the structure file. This processing can include internal components to load the logic synthesizer, as well as good external component references. The structure file is preferably implemented in XML, and the component itself is not limited to execution types other than a CORBA compatible interface. Generic servers also allow components to retrieve information from the structure file through the interface of the component base class. This makes it easy for programmers to store parameters or other information in XML structures and to modify those parameters without changing any code. The process of reading and parsing XML consists of a general server synthesizer and 7 paper sizes that are applicable to China National Standard (CNS) A4 (210 X 297 mm) ------------ · (Please (Please read the notes on the back before filling in this page) ------- Order * -------- I · Printed by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs 490639

Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs. 5. Description of invention (6) The base types of components are all processed, so programmers need not worry about file format or analysis. The invention therefore enables the integrator to join a new business logic and develop into a distributed system without slowing down the process' without modifying and recompiling the source code, and without copying the recompiled source code to each server Device. In fact, an integrator or other authorized user can add or modify features without source code. Other objects and advantages of the present invention will become apparent through the following detailed description of the preferred embodiment with reference to the accompanying drawings. Brief Description of the Drawings Figure 1 is a high-level block diagram showing a multi-level, distributed computer system for connecting end users to back-end resources such as a computerized reservation system via a network to implement strong and flexible Scalable, high-performance system. Figure 2 is a conceptual diagram of a general synthesizer according to the present invention for loading software components based on structural files. Figure 3 is a conceptual diagram describing the structural files between the connected components. Figures 4A and 4B—an example of a structure file that is implemented in XML, is processed by city code. Figures 5A to 5C describe software processing, each of which executes a general synthesizer with a corresponding structure file. Figure 6 is a simplified diagram illustrating the operation of a multi-level, distributed computer system supporting a travel planning and booking website. Fig. 7A illustrates a part of the XML structure file corresponding to the synthesizer of Fig. 5B. 8 This paper size applies to China National Standard (CNS) A4 (210 X 297 mm) (Please read the precautions on the back before filling this page) I 1_1 ϋ · ϋ n ϋ · ϋ 1-1 1 ** Line 丨-490639 9 A7 B7? Year (month ΊP. I would like to ask the commission to print the employee's cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs. 5. Description of the invention () The pseudo-codes listed in the implementation. Figure 8A-B is written in XML An example of the requested shift schedule is shown in Figure 9. Figures A--9B are examples of response schedules expressed in XML. Figures 10A-B are illustrations of city code lookup processing (synthesizer) structure files. Figure 11 Figure 12A to Figure 12C illustrate the XML data, an individual DOM-level module of the XML data, and the corresponding node form; Figure 13A To FIG. 13B, an interface definition for a file server object is proposed. Component symbol description 1, 2, 3: Component 102: Server 104: Internet 106: End user 108: Application server 112: XML file Library 114: Architecture Object 116: Business Object 120: Database Inventory Layer 1 22: Customer profile database 126: CRS (Computer Reservation System) interface 9 (Please read the precautions on the back before filling out this page) · ____ Yi-kou, · n 1_1 ϋ n -ϋ i ft ϋ 1 · ϋ n « ϋ n «ϋ nnnn I n ϋ i_l 1 I n This paper size applies to Chinese National Standard (CNS) A4 (210 X 297 public love) 490639 A7 B7 Printed by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs 130: Computer reservation system 500: Synthesizers 502, 504: Component 506: Business logic component 510: Synthesizer processing 512: Amadeus interface factory 514: Interface object 516: Filter integration component 520: Document server components 522 and 524: Object (or "document") 600: Customer Packaging Interface 602: Call 604: Travel Plan Controller Factory Component 606: Travel Plan Controller Instance 610: Call 612: Document Factory 614: Document Object 620: Call 622: Call 624: Amadeus Interface factory 626: Interface object 627: Flight request information 640: Computer reservation system 650: Kosher meal business logic (please read the precautions on the back before filling this page) Order-丨 This paper size applies to China Standard (CNS) A4 (210 X 297 mm) 490639 Printed by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs A7 _____B7 _ V. Description of the Invention (1) 652: Structure File 654: Call 662: Call 664: City Code Viewing Component 666: Look-up table 670: Customer package 672: Filter component 674: Update file. Detailed description of the embodiment. Figure 1 describes a two-tier e-commerce architecture that uses COBRA to provide a distributed mechanism. At the top level, an HTTP server is coupled to the Internet 104 to provide access to multiple end users 106 running a standard web browser, such as IE or Navigator. Behind the web server 102 is an application server, such as the BroadVision application server 108. The application server interacts with business logic and framework "intermediary software providers" through a customer packaging layer provided by an intermediary software vendor. This customer packaging layer can be implemented in the conditions of airplane travel, hotel reservations and car rental, for example by using Java description language and providing methods suitable for the application. This customer package does not implement business logic. Business logic is implemented through the Java description language at the architecture (intermediary software) layer and the user interface layer. Second, the middle layer implements the business logic and intermediary software architecture of the present invention. This layer includes an XML document storage 112, a structure object 14, a business object 116, and various interfaces for interfacing with a computer reservation system and / or an inventory source. By way of description, Figure 1 shows a database inventory layer 12 for the purpose of (please read the notes on the back before filling out this page) — — — — — — — Line 丨 · 11 490639 A7 V. Description of the invention (connection The customer depicts the database 122, and it further displays a CRS (Computer Reservation System) interface 126 to interface to a computer reservation system 130. The drawing is greatly simplified, for example, various architecture objects u4 and business objects 116 may include Establish a factory with multiple instances of relative objects, and these various objects will be distributed to most applications through multiple servers. As mentioned above, the main subject of the present invention is to implement an intermediary software architecture without touching the system Source code, which greatly simplifies the development of business objects 116. The business logic that drives the site includes things such as ticket booking rules or restrictions on specific travel. Business logic components are sufficient to implement pricing, discounts, seat allocation and other strategies. Later In the example described, a Jewish meal item is confirmed to be obtained when a Jewish meal is requested. In a practical implementation, this CRS interface 126 is similar to management 1, 0 The sequence of simultaneous connection to a CRS host such as the SABRE system. Figure 2 depicts the general server synthesizer according to the present invention as mentioned above in the summary. The components are obtained from the architecture base class. The programmer (Or a travel website integrator) to achieve the desired function in the component object 'and load the result object into the synthesizer by adding the result object to the structure file 202 of the synthesizer in Figure 2. The component is implemented as a shared database, Therefore, the synthesizer 204 can be loaded at runtime without recompilation or link-general server synthesizer. The structure file is expressed in XML syntax to explain which components the general server will load, and how to connect to it When the basic server starts together, one of the first things to do is to find the basic file with the name on the server's command line. In the preferred embodiment + separate processing for each server The structure file is the same as the individual wood paper standard applicable to China National Standard (CNS) A4 (210 X 297 mm) (Please read the precautions on the back before filling in this ) Ministry of Economic Affairs Intellectual Property Office employees consumer cooperatives printed

ϋ IH-aJ · nnnnn I ϋ II I- nnnnn 1 1 ϋ I n II ϋ ϋ nnn III n I 490639 A7 B7 Printed by the Consumers ’Cooperative of Intellectual Property Bureau of the Ministry of Economic Affairs Shared structure file. This makes it easy to place common components. For example, each server can use a specific shared object reference in a shared file of information. In addition, the structure file can describe the connections between components that implement a specific architecture-defined interface. The connection can include components (internal components) located in the same server process, components in other general server processes, and even objects (external components) in other processes that are not implemented within the architecture. Its objects Any CORBA object that can be entered as a string into the structure file can be linked-even if the object is written in another language supported by CORBA. Figure 3 illustrates the connection between two specific components in the structure file. In this case, component 1 requires a confirmation service, and its confirmation interface is provided by the structure file with a link to component 2 It is implemented and located in another server defined by the component 2 object reference listed in the structure file. The threading strategy general server also supports three different threading modules to process the objects it contains Requirement. Single 1. Separate thread. This is the simplest model. For general servers, every request issued by any object included in this server processing is processed in series. The incoming requests are stored in In the queue, and each request is completed before the next request is processed. Note that this module is applicable to all components included in server processing, so only one request of any component in server processing is processed at a time. 2. Separate each request. The general server synthesizer also supports a module, each input request is processed by a separate split. Each new 13 paper standards are applicable to China National Standard (CNS) A4 specifications (210 X 297 mm) (Please read the notes on the back before filling out this page) · ____ Order --- Line 丨 490639 Printed clothing A7 B7 by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs ____ 5 Description of the Invention) seeking a cause partial thread is created to handle the request, and starts executing the thread minutes until the request is completed. Then the thread terminates. The maximum number of threads can be set with specific parameters in the XML structure file. If this maximum number is reached, the new request is blocked until at least one prior request is completed and its division is terminated. 3. Partition library. In this model, the generic server starts several specific threads in the structure file at startup. When entering a request, if there is no disjunction, the request waits in the queue until a disjunction is available. The threading model used is specified by the structure file. However, it can also change at execution time. The general server also checks the threading safety attributes of each component it loads. If any of the components it loads are non-threading safe, the server forces it to be a separate threading model. In addition, general server synthesizers deal with thread maintenance issues, such as dealing with broken or hanged threads, and reporting statistics on thread usage. Figures 4A and 4B illustrate a structure file, in which case the server is considered a city code lookup server. This provides the ability for the application server to look up the city code, which is obtained through the customer packaging layer of Figure 1. So if an end user of a travel website enters a city name that is not unique (Portland, Oregon / Portland, Maine) or uses an airport abbreviation (PDX) or misspells the city name, the application server can request a city code lookup to get a Or multiple valid replacements. Referring to Figure 4A, a part of the file lists the attributes of the synthesizer, such as the time over, the splitting strategy, and the maximum number of simultaneous splitting ("maximum splitting"). Part I > 14 This paper size applies to China National Standard (CNS) A4 (210 x 297 public love) (Please read the precautions on the back before filling this page) * 1 = mouth, · 111111 line 丨 · 490639 A7 B7 V. Description of the Invention (ρ)) The internal software components are listed in this section. In this case, start with the component name "City Code Lookup". For each internal component, the structure file indicates a creator's name and location, relationship (not related in this example), and attributes. In the presently preferred embodiment, a component can have three forms of attributes: simplicity, architecture, and order. In this example, the attributes of all the bars are in simple form. The city code checking structure file is continued in Figure 4B. The next component starts with the component name "City Code Restricted Access". Once again, provide the name of the creator and the location of the creator, a database. It doesn't matter in this example, and various attributes are listed again. Therefore, when the city code lookup server or synthesizer processes the initialization, it will read the structure file, establish the recorded general attributes, and then it will load (create) the example of the city code lookup and city code restriction lookup components. This simple form attribute, and the corresponding frame, provide the tools to go around these components. This makes it possible to integrate changes around a given business logic component by simply editing the XML structure file. This structure file also simply defines the order of calling components according to the order of the components in the structure file. This allows new business logic (a new component) to be simply inserted into the corresponding point in the component table in the structure file by inserting the correct point in the existing process. As explained later, a structure file can define relationships or "connections" between components, for example, defining services that components use for other components. From "sequentially, a new component to the correct position in the structure file table to define the relationship with other components, a new logical component can be installed into the entire system without changing any existing source code. In other words, 'above the The component synthesizer architecture of the present invention presents a high-level abstract, but it is still compatible with 15 paper sizes in accordance with the Chinese National Standard (CNS) A4 specification (210 X 297 mm) (please read the precautions on the back before filling this page) Printed by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs

1-1 0, I «^ 1 1 a ^ i 1§ ϋ I n 11 n I —_B1 ϋ ·· I n_i am 11 MmMMe In tmmmme I · ϋ nn ϋ · nn I Printed by the Consumers’ Cooperative of Intellectual Property Bureau of the Ministry of Economic Affairs 490639 A7 _ B7 V. Description of the invention (/ min) The COBRA architecture is compatible. Figure 5A is a simple example of the synthesizer processing Cl and the corresponding structure file, structure (C1). The synthesizer 500 includes a travel plan control component 502, a Kosher meal component 504, and any other business logic components. "XX" 506. Figure 5B depicts the second synthesizer process 510, which includes the previously mentioned components 502 and 504, and introduces a new component, the Amadeus interface factory 512. The interface factory creates interface objects as needed. Described by the interface object 514. The interface factory components are added to the synthesizer by listing in the corresponding structure file, structure (C2) ". This structure file is simplified for the purpose of description, and will be contained in more detail in actual applications as shown in Figures 4A-B. Figure 5C depicts another synthesizer process C3, in this case a file server synthesizer. The synthesizer includes two components, called a file server component 520 and a filter integration component 516, as listed in the corresponding structure file "Config. (C3)". The document server creates individual documents as needed, such as objects (or "documents") 522 and 524. In the travel website application, a document will be created by each end-user "trip" processed by the website application server. The application server maintains the workshop status information and calls the document server (document factory) to generate a new document. Conversely, it can be noted that the document synthesizer discards the existing document when the corresponding trip ends. Individual document objects store user / trip information, such as a flight journal, in XML format as described later. Figure 6 describes the operation of the software system described above. Refer to Figure 6. At the beginning of the customer itinerary on the travel planning website, the application server (see Figure 1), using the customer packaging interface 600, make a call to 602 to the synthesizer C2 16 This paper size applies to China National Standard (CNS) A4 Specifications (210 X 297 mm) ---------------------- Order · -------- 1AW-1 (Please read the note on the back first Please fill in this page again for matters) 490639 A7 B7 printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs V. The travel plan controller factory component 6O4 shown in the description of the invention (d). A requirement for the factory to set up a travel plan controller instance 606 is inevitable. The object 606 will implement the travel plan processing for a specific itinerary. The customer package 600 is also used as a call 610 to the document factory 612, in this case at a document server synthesizer C3. The document factory 612 creates document objects. In this example, the document object 614 is used to store information about the current trip. The corresponding travel plan controller 606 communicates with the file 614 via the channel 616. Suppose the end user in the current itinerary requests flight information, etc., between a given location on a given date. The flight request information is written to the itinerary file 614 in XML syntax via call 620. The travel plan controller (TPC) 606 makes a call 622 to the Amadeus interface factory 624 to request an interface to the CRS. The factory 624 creates (or specifies from the database) an interface object 626 as required, making it available to the TPC. The interface 626 uses a query language explained later, reads flight request information 627 from a file 614, and establishes a flight plan request in a suitable form, describing the flight plan request to the computer reservation system 640. The interface receives a flight plan response and writes the information to a file 614 in XML syntax. The customer package 600 can read the updated document through another call, provide the document to the application server, and then provide the flight information to the web server (see Figure 1). Note that the client packaging layer provides an interface to the application server document to access the XML data. We then assume that the end user chooses her journey from the offered flights. The selected flight information is written to the itinerary document 614 through the customer package described. Before the end of the trip, various business logic components can be adjusted to 17 national standards (CNS) A4 (210 X 297 mm) in this paper size (please read the precautions on the back before filling this page) • ---- ---— tr --------- ^ Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economy 490639 A7 B7 V. Description of Invention (α) Call to correct and / or confirm the appropriate travel plan information. Other components can be called by the travel planning controller of the itinerary (606), and they interact with the data stored in relative file 614 by Jianghan. Multiple components can be implemented to provide various business logic, as mentioned above, such as pricing, seat allocation, discount specials, mileage accumulation, loans and even food requirements. We describe the above characteristics in the manner of Jewish meal business logic 650. The Kosher meal component is shown configured in the synthesizer C2, and a corresponding structure file 652 appears. The Kosher meal component determines whether Kosher meals are available on the flight request by the end user. For example, if a kosher meal is required, the travel plan controller makes a call 654 to a kosher meal component 650. The work of component 650 determines whether Kosher meals are available on flight request. Two requirements must be met: first, the take-off program must be able to provide Kosher meals, and second, the minimum number of days in advance to provide Kosher meals is necessary. The minimum number of days required to be notified in advance will be transmitted to the Jewish meal component via structure file C2 at the execution time, which will be explained later. In response to call 654, the kosher meal assembly 650 makes an inquiry 660 to document 614. That is to determine two pieces of information for each flight segment, namely the departure date and the departure city code. The Kosher meal 650 then makes a call 662 to the city code lookup component 664 to determine if the designated departure city is able to provide Kosher meals. We assume that this information is accessible to the city code, as it is based on information on all commercial airports in the world. If Kosher meals are available in the designated departure city, and if previous notifications are met, expressed as the number of days from booking (or today) to the departure date, Jewish component 650 will amend document 614 to specify that Kosher meals are available The flight segment was awarded 18 ^ sheets in accordance with Chinese National Standard (CNS) A4 specifications (210 X 297 public love) (Please read the precautions on the back before filling this page) ·· ___

· I I I I I I I —I— I —II 490639 Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs A7 B7 V. Description of Invention (丨 q). Obtaining the Jewish meal can be achieved with a lookup table 666, but it would be better to use the city lookup component so that airport information is collected in one place. The travel plan controller 606 can provide updated information to the customer package 670. An illustrative embodiment of a kosher meal assembly is provided in FIG. 77C. This component uses the query language described below to access the data stored in the trip document object. Of course, many user trips can be processed at the same time. The application server, packaged by the customer, will request the travel plan controller and corresponding documents from the document factory as needed. BL205 only confirms another business logic component in the figure. Another component, described in the synthesizer C3, is a filter component 672 called "filter integration". The component architecture includes what is commonly referred to as a filter. This is used to modify a file on which the system works. It is necessary to check the document and delete specific information. In this case, the filter integration has the task of removing the flight from the document integration airline, which appears in the flight plan response data. To add any new filter, the program designer can get it from the base filter category, simply write one, and add it to the filter bar in the structure file. To illustrate, we show the filter integration of update file 674. Figure VIIA describes the C2 structure in more detail. The structure file is displayed in XML syntax, starting with the server name and server attributes. Then line up the three internal components, travel plan control, kosher meals, and the Amadeus interface factory, as mentioned above. For each component name, the structure name includes the creator name and the creator's database location. It also includes attributes and relationships with other components, as appropriate. For Kosher meal components, the creator name 19 This paper size applies Chinese National Standard (CNS) A4 specifications (210 X 297 public love) (Please read the precautions on the back before filling this page). · 5 ^ 1 1 1_ «ϋ · An · I— n in II— ϋ_ι · * 1 n aMemm i §mm§ HI Words 490639 Printed by the Consumers ’Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs A7 B7 V. Description of invention (丨 f) Character and creator database The locations are listed. 3 There is an attribute that is displayed in a simple form, called "notify in advance" and the parameter 値 is 5, indicating that the Jewish meal needs to be informed in the first five days. A synthesizer handles reading the structure file and provides attribute information to the Jewish component as a parameter at runtime. In this way, previous notification requirements can be easily changed by simply editing the XML structure file. The archive also shows that the component Jewish meal has a relationship in which it uses the city code to look up the component. Figure 8 shows an example of flight plan requirements. The various components required by the flight plan are extracted in the following table: Table 1 · The flight plan request method components are listed: Component: Flight plan Description: Contains all information to perform flight acquisition and flight plan requirements and displays the results. Attributes: None Sub-components: Requirement-The following, 1 or more, as needed Component: Requirement Description: Contains all information to perform flight acquisition and flight planning requirements. Attribute: Identification code-unique confirmation element · required flight segment-below, 1 or more, category of service as required-below, exactly 1, as needed passenger form: below, 1 or more, valid as needed Airliner: The following, 0 or 1, optional components: Request Flight Segment Description: Contains all information requested by a flight. (Please read the notes on the back before filling this page) -------- J Ding · -------- 丨 20 490639 Printed by A7, Consumer Cooperatives, Intellectual Property Bureau, Ministry of Economic Affairs Description of the invention (7) Attribute: identification code-unique confirmation secondary element: takeoff-below, exactly 1, arrive as needed-below, exactly 1, include transit cities as required-below, 0 or 1, optional element: takeoff description : Take-off point description. Attributes: Date-Departure Date Time-Departure Time Secondary Element: City-Travel Plan XML, exactly 1, as needed Element: Arrival Description: Arrival city. Attribute: No secondary element: City_Tourism Plan XML, exactly 1, as needed Element: Include transit cities Description: The list of cities that require transit, the flight selection must include a stopover city Attribute: No secondary element: City-Tourism Plan XML, exactly 1, as needed Component: Category description of the service Requirement: Cabin required attributes for all segments: Code-required cabin code for the passenger component: No component: Valid passenger description: Restrictions for passenger aircraft. The return flight is acceptable for this paper. Applicable to China National Standard (CNS) A4 (210 X 297 mm) (Please read the precautions on the back before filling this page)

1: mouth Y · ϋ 11 — ^ 1 II — ^ 1 · ϋ ^^ 1 I «ϋ n —ϋ 8— I— ni in II —ϋ · ϋ in i ii n flu n an Hi nmn I 490639 A7 ______B7 V. Description of the invention (yD) Attribute: No secondary element: Airliner-Travel Plan XML, exactly 1, as needed Element: Passenger form Description: Number of passengers required-Total number of all passenger forms will be used in the request Attribute: Number- Number of passengers in this form Secondary element: No element: Number selection description: Maximum number of return flight options Attribute: 値 -Number of passengers in this form Secondary element: No element · f / l class selection description: This element includes the use of The number of flights attributed to the plan or information that the user wants to get: 値-Number of flights Secondary element: None The example in Figure 8 shows practically all elements that may be included in the flight acquisition search, although not all of them Required, as indicated in the table. All information in the flight plan request and flight plan is stored in the corresponding itinerary file, as mentioned above. Figures IXA-IXB describe the response to a flight plan. The response begins with a corresponding flight plan request confirmation. The response has a confirmation number and includes two options (flights), choosing confirmation numbers 1 and 2. Figures 10A-B form the rows of the city code query server structure file. The 22 paper sizes are in accordance with Chinese National Standard (CNS) A4 (210 X 297 mm) (Please read the precautions on the back before filling out this page.)

-OT n n ϋ H ϋ i n I I n n I ϋ -n n ϋ n ϋ n n n n n n n ϋ ϋ I I I 490639 A7 B7 V. Description of the invention (yj) file includes general attributes (can be used to the entire synthesizer) and internal components. Each of the internal components "city code lookup" and "city code restricted lookup" has multiple attributes. Also, these attributes are passed to the component as parameters at execution time. Fig. 11 A-Eleven B. Describe the structure of the travel plan controller synthesizer. The structure file includes a tour controller factory in one of the forms discussed above. File component This file component is a component that contains XML files internally. Its external interface provides customers with the ability to set and release specific parts of files at a predetermined time. The XML file is preferably stored internally using a C ++ DOM implementation. However, most document users will not need to process XML or DOM directly, because most of the reading and writing of document information can be done using nodes and node attribute structures, using node identifiers or an XQL query to confirm a node Or a group of nodes. Note that the itinerary data is stored in the document object in XML format. Figure 12A illustrates a hierarchical combination of tags in XML format. Figure 12B is a description of the DOM module. The tag has three structures, and each node has a corresponding node identification number. The present invention implements a node tandem concept with its query language. This is a list of tags and the corresponding point of identification. A * node identification code is the only internal confirmation 'file processing used to identify individual nodes. The user of the file will not try to determine the node ID on it, but will only use the 値 that has been obtained from the file instance. They operate through operations similar to those obtained by querying the node. If a call to a node is successful, then the responding node can believe that it has the correct node identification code, and their attributes or attributes can be modified. These 23 paper standards are applicable to the Chinese National Standard (CNS) A4 specification (210 X 297 public). Li) one " one ^ '(Please read the notes on the back before filling in this page) 丨 · Line 丨 · Printed by the Intellectual Property Bureau Employee Consumer Cooperative of the Ministry of Economic Affairs 490639 A7 B7 V. Description of the invention (~ y >) The node ID update is transmitted back to the file, and the change will be made where appropriate in the file. However, if one of these node IDs is released, the file stores a file, and a new file is created from the same file 'The node ID will no longer be valid. Query language A query is a string of characters that conforms to a defined query language. In the preferred embodiment of the present invention, a query language suitable for accessing file content is a subset of XQL (XML query language), which is an extension of XSL (Extensible Stylistic Language). More information in these languages is publicly available. Next is a table containing examples of query commands supported by the component, and what they do: / Confirm the root node. / Confirm the current file node. / / Confirm the parent node code of the current file node Select all code nodes that are children of the current file node " Code Select Now File_All Code Nodes of Sons of Nodes Touch Select All Code Nodes of Sons of Root Nodes to Find All City Code Sons of Current Files and Select All Their Code Node Sons / Cities / Codes to Find Root All city code children of the node, and select all their code node children 丨 丨 Perform a recursive download at the root node (but not included). // Perform a recursive download at the current file (but not included) Start // code selection code node anywhere in the file // code selection now code node anywhere in the file 24 This paper size applies to China National Standard (CNS) A4 specifications (210 X 297 public love) (Please read first Note on the back, please fill in this page) -------- Order · -------- Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economy 490639 Α7 Β7 V. Invention Explanation θ ') city / * find all city code sons of the current file and select all their code node sons * / city select all city grandsons / cities of the current file // find all city code nodes of the son of the root node, And in each (but not including) perform a recursive download to start the city " code search, find all the city code nodes of the son of the current file, and select all their code nodes son // city horse to find all the City code, and select all their code node son cities / @ confirm to find all city code sons of the current file, and select only the attribute city from each @@ * find all city code sons of the current file, and select only from each Attribute (excluding node name and 节点) City [@OK] Select all city code nodes of the son of the current file and have a confirmation attribute City [Code] Select all city code nodes of the son of the current file and have At least their own one-node son node city [@ confirmed = ”my city] select all the sons of the current file City code node, and its confirmation attribute is "My City" The present invention violates the standard XQL supported by symbol files, including the addition of the! Operator as a // performance modification. The XQL definition // operator is on a specific node. Recursive download begins. Therefore, // will indicate that a recursive download begins, but does not include the current file node. This is obvious in our use of XQL, because a common XQL query will look for a specific Nodes and select them and their descendants. For example, you may want to select all urban paper sizes anywhere in the file to apply Chinese National Standard (CNS) A4 specifications (210 X 297 mm) (Please read the precautions on the back before (Fill in this page). · ____ Printed by the Consumer Cooperative of the Intellectual Property Bureau of the Ministry of Economic Affairs τ I n ^^ 1 * 1 ^ ϋ— ϋ— mtmmMm I ϋ m ϋ— II 11 · ϋ flu Ha 11 m · ϋ — ϋ m —ϋ nm ϋ ϋ II > ϋ · ϋ flu-490639 A7 Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs ___B7____ V. Invention Description (^) City nodes and their descendants. With the sentence along with XQL, you can write the query // city, which will select all the city nodes anywhere in the file ’but will not select their descendants. You will also write " City // 'which will find all city nodes anywhere in the file' and select their descendants' but not the city node itself. Therefore, you will have to ask at least twice to select urban nodes and their descendants, whether a potentially expensive process is done over the internet, and will respond to the chaotic results once. Our solution allows an! Operator to follow // directly to include the starting node with the effect of //. This will allow the following queries: Find all city code nodes that are the children of the root node, and perform a recursive download at each (and including) start. Find all the city code nodes of the sons of the current document, find their code descendants, and perform a recursive download on each (and including) to begin. Select all code nodes in the current file or anywhere below the current file (very slight difference). Find all city code nodes that are the sons of the current file and select all their code descendants. In this case,! It is useless because it will modify the effect of // to check each city node to see if it is a yard node, which is obviously never true. Find all city codes in the file and select all their code node sons. Again, here! Is useless, because it will modify the role of // to check each city node to see if the root node is a city node. It will never be true because the root node is a file and not XML 26 National Standard (CNS) A4 (210 X 297 mm) / City / /! City / / Code / /! • / /! Code City // / Code / /! City / Code J · (please first (Read the notes on the back and fill out this page)

5JI n n I ϋ n ϋ ϋ I I n H ϋ n 1 n n I n ϋ I ϋ n I n n I I n i I n I 490639 A7 ______B7 V. Description of the node. When using a query, documentation is now an important concept. If the query starts with '/', it starts at the root, which is the base of the file tree. However, if it does not start with V ', it starts with the current file. In other technologies, the file is now similar to an indicator or cursor, representing a specific location in the file. Once the file is now set, it will remain until it is changed neatly or until the file is destroyed. This allows queries to be used only at specific locations of the file 'if needed. Some operations that are performed by a query, such as setting a current file by a query and adding a node to a query, can only perform their functions when a query specifies a single node in the file. In other operations, for example, nodes are obtained from a query, and a query can specify and select multiple nodes. A simple example of using these forms of inquiry is described in the Jewish meal of the examples of Figures 7B-C. It will be apparent to those skilled in the art that the details of the embodiments of the present invention described above can be changed in many ways without violating their basic principles. The scope of the invention will therefore only be determined by the scope of the following patent applications. (Please read the precautions on the back before filling this page) ·· Order. 丨 Line 丨-Printed by the Employees ’Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs 27 This paper size applies to China National Standard (CNS) A4 (210 X 297 Mm)

Claims (1)

8 8 8 8 ABCD 490639 6. Scope of patent application 1. A multi-layer, distributed object architecture, which includes: (a) — customer packaging layer for interacting with customers; (b) — intermediary software layer, including A synthesizer process to have one or more business logic objects; and (c) a resource interface layer to connect to and interface with a computer reservation system, (d) a synthesizer process with access to at least one structure file , Used to organize the synthesizer at execution time, and load one or more specific components in the synthesizer structure file. 2. The structure according to item 1 of the patent application scope, wherein the structure file includes the identification of at least one external component. 3. The architecture according to item 1 of the patent application scope, wherein the structure file includes at least one attribute processed by the synthesizer. 4. The architecture according to item 3 of the scope of patent application, wherein the synthesizer properties include the selection of a predetermined threading strategy. 5. The architecture according to item 1 of the scope of patent application, wherein the structure file includes, for a specific component, at least one attribute confirmation is used to transmit to the component as a parameter at execution time. 6. According to the intermediary software architecture of item 5 of the scope of patent application, the component attributes include a selection parameter and a selection parameter 値, which is used to transmit the selection parameter 値 to the internal component, and edit 値 in the corresponding structure file. 7. The structure according to item 1 of the scope of patent application, wherein the structure file is formed by XML syntax. 8. According to the structure of the first patent application scope, the structure file is (please read the precautions on the back before filling this page). Order printed by the Intellectual Property Bureau Staff Consumer Cooperatives of the Ministry of Economic Affairs. ) A4 specification (210 X 297 mm) 490639 A8 B8 C8 D8 6. The scope of patent application is realized by text file. 9. The structure according to item 1 of the scope of patent application, wherein the structure file is enclosed as a software object. 10. The structure according to item 1 of the scope of patent application, wherein the structure file includes confirmation of at least one relationship between a specific component, the component and another component. (Please read the precautions on the back before filling out this page), ‘Printed by the Consumer Cooperatives of the Intellectual Property Bureau of the Ministry of Economic Affairs This paper size is applicable to China National Standards (CNS) Α4 specification (210 × 297 mm)