KR20150016099A - Contract number allocation for travel industry transactions - Google Patents

Abstract

The present invention relates to a method, system and computer program product for delimiting subcategories and associated contract number ranges within a standard issuance context category for a travel product. The stochastic allocation module includes a stock index table having a plurality of stock indexes and at least one number range respectively associated with the issuance context. In response to the traveler purchasing the travel product, the publishing platform sends an allocation request to the STOCK allocation module. In response to receiving the allocation request, the ST allocation module identifies a STOCK index that matches the issuing context of the pending transaction. The matching stock index is used to identify the range of numbers corresponding to the issuance context. The available number is selected from the identified range of contract numbers and is used to define the contract number. This contract number is returned to the issuing platform.

Description

CONTRACT NUMBER ALLOCATION FOR TRAVEL INDUSTRY TRANSACTIONS FOR TRAVEL INDUSTRY TRANSACTIONS

The present invention relates generally to computer and computer software, and more particularly to a method, system, and computer program product for assigning a contract number from a range of contract numbers based on an issuance context of the contract. Product.

In the travel industry, travelers generally purchase travel products, such as travel to airline or rail transport companies, by purchasing tickets. A ticket is a document issued by a transportation company, travel agency or other authorized seller who confirms that the traveler has purchased goods or services from the transportation company. In the case of an airline, the ticket can confirm that the traveler has purchased a seat for one or more flights scheduled to travel from the origin to the destination. This seat may be for a specific time or may be exchanged for a later time period at the discretion of the traveler. In either case, the ticket is generally used to obtain a boarding pass from the shipping company prior to departure. The most common types of tickets are known as electronic tickets or "e-tickets", but tickets that can be exchanged for travel products can also be issued as coupons. A ticket issued with a coupon is generally referred to as a "paper ticket". A travel ticket provided through a rail transport company may be referred to as a travel card or a transit pass. In either case, the ticket confirms that there is a contract between the transportation company and the traveler indicating the carrier's commitment to provide the traveler with the right to transport in exchange for the money paid by the traveler.

Travelers can purchase many types of tickets. For example, some types of tickets are valid only for flights provided by a particular airline for which the ticket was purchased. However, an airline can endorse this type of ticket and accept it from another airline. Tickets may only be exchanged for certain flights, or tickets may be "open" tickets that allow travel on any flight between the origin and destination listed on the ticket. Some types of tickets may be refundable, while others may not be refundable. Tickets may specify that travelers are given additional services, such as meals or access to the airport lounges. Thus, many types of tickets are on the market, where each type has a different set of restrictions and / or gives different products to the traveler. As expected, the traveler generally has fewer restrictions or pays a higher fare (fare) to tickets that provide additional services. Thus, travelers who wish to accommodate a greater number of restrictions, including acceptable travel dates, the ability to transit to other flights, or the ability to refund a ticket, generally have more flexibility or a higher level of Tickets can be purchased for less than travelers who require service.

In order to identify a ticket in various computer systems associated with billing and passenger processing, the contract number is assigned in a portion of the process issuing the ticket. When a ticket is issued in the airline transportation industry, a unique contract number can be generated by the computer and assigned to the ticket. This contract number may include a form code that includes two or three numbers in the contract number. Each form code may be associated with one of a plurality of standard categories of shipping products defined by the International Air Transport Association (IATA). A "stock provider" number that identifies a valid shipping company may be further included in the contract number. Thus, the contract number of a ticket issued to an air travel may consist of an airline code and a form code followed by a serial number and, in some cases, a check digit. The form code thereby provides a plurality of contract number ranges that define the standard category of airline tickets. The contract number issued under this standard range allows the airline and / or Billing and Settlement Plan (BSP) system to determine whether a ticket is one of the standard categories. However, since this standard category is an industry standard category defined by IATA, this standard category is the same for each transport company. Transport companies are limited to the standard category category defined by IATA, limiting the ability of each airline to define additional categories of tickets that address specific needs.

Thus, while limiting the contract to include a specific set of product characteristics unique to this transport company, the contractor can be limited and assigned to limit the range of contract numbers that remain compatible with existing industry standards There is a need for an improved system, method and computer program product.

In one embodiment of the invention, a method is provided for configuring a contract number in a database. The database includes a plurality of sets of contract numbers, wherein each set of contract numbers corresponds to one of a plurality of stock providers and includes a plurality of standard category number ranges. The method includes defining a first subcategory number range corresponding to a first issuance context within a standard category number range for a contract number set corresponding to a stock provider. The method further includes the step of defining, for this set of contract numbers, a second subcategory number range corresponding to a second issuance context within a standard category number range. A first contract issued for a stock provider having a first contract number that includes a first number from a first subcategory number range is identifiable as having a first issue context based on a first contract number. Further, the second contract issued to the stock provider having the second contract number including the second number from the second sub-category number range is identifiable as having the second issue context based on the second contract number.

An apparatus is provided in another embodiment of the present invention. The apparatus includes a processor, and a memory including instructions. The instructions, when executed by the processor, are configured to cause the device to define a first subcategory number range within a standard category number range. The first subcategory range is limited to the contract number set and corresponds to the first issue context. Instruction causes the processor to further define the second subcategory number range within the standard category number range. The second subcategory range is limited to the contract number set and corresponds to the second issue context. A first contract issued for a stock provider with a first contract number that includes a first number from a first subcategory number range is identifiable as having a first issuance context based on a first contract number. Further, the second contract issued to the stock provider having the second contract number including the second number from the second sub-category number range is identifiable as having the second issue context based on the second contract number.

In yet another embodiment of the present invention, a computer program product is provided. The computer program product includes a non-transitory computer readable storage medium for storing instructions. The instructions, when executed by the processor, are configured to cause the processor to define a first subcategory number range within a standard category number range. The first subcategory range is limited to the contract number set and corresponds to the first issue context. Instruction causes the processor to define a second subcategory number range within the standard category number range. The second subcategory range is limited to the contract number set and corresponds to the second issue context. A first contract issued for a stock provider with a first contract number that includes a first number from a first subcategory number range is identifiable as having a first issuance context based on a first contract number. Further, the second contract issued to the stock provider having the second contract number including the second number from the second sub-category number range is identifiable as having the second issue context based on the second contract number.

In yet another embodiment of the present invention, a method of assigning a contract number from a database of contract numbers is provided. The method includes receiving, in a computer, an allocation request from a publishing platform, wherein the allocation request is for a contract issued to a stock provider and includes an issuance context. The method further includes the step of determining, at the computer, a stock index matching the issuance context. The method delimits a contract number comprising a number from a first subcategory number range associated with a stock index in a database and sends the contract number to a publishing platform. The first subcategory number range defines a portion of a standard category number range stored in a database capable of storing a plurality of standard category number ranges. The standard category number range includes a first subcategory number range and a second subcategory number range, wherein each first and second subcategory number range is associated with a stock provider.

In another embodiment of the present invention, another apparatus is provided. The apparatus includes a processor, and a memory including instructions. The instructions, when executed by the processor, are configured to cause the device to receive an allocation request from a publishing platform. The allocation request may be for a contract issued against a stoker provider and includes an issuance context. The instructions may cause the processor to further perform operations to determine a stock index matching the issuance context and to define a contract number. The contract number may include a number from a first subcategory number range associated with the stock index in the database and may be transmitted to the issuance platform. The first subcategory number range may define a portion of the standard category number range stored in the database. The standard category number range may further include a first subcategory number range and a second subcategory number range, wherein each first and second subcategory number range is associated with a stock provider. The first standard category number range may be one of a plurality of standard category number ranges stored in the database.

Another computer program product is provided in another embodiment of the present invention. The computer program product includes a non-transitory computer readable storage medium for storing instructions. The instructions, when executed by the processor, are configured to cause the processor to receive an allocation request from the issuing platform. The allocation request may be for a contract issued against a stoker provider and includes an issuance context. The instructions may cause the processor to further perform operations to determine a stock index matching the issuance context and to define a contract number. The contract number may include a number from a first subcategory number range associated with the stock index in the database and may be transmitted to the issuance platform. The first subcategory number range may define a portion of the standard category number range stored in the database. The standard category number range may further include a first subcategory number range and a second subcategory number range, wherein each first and second subcategory number range is associated with a stock provider. The first standard category number range may be one of a plurality of standard category number ranges stored in the database.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and, together with the brief description of the invention given above and the detailed description of the invention given below, It serves to explain.
1 is a schematic diagram illustrating an exemplary operating environment including a plurality of computer systems communicating over a network.
Figure 2 is a schematic diagram illustrating the exemplary computer system of Figure 1;
3 is a schematic diagram showing an exemplary contract number showing the structure of a contract number;
Figure 4 is a schematic diagram showing a plurality of standard categories and associated subcategories, with each standard category and subcategory being associated with a range of contract numbers.
5 is a schematic diagram showing a contract number assignment system including a stock allocation module having a stock index table and a stock database.
6 is a schematic diagram of an exemplary portion of the stock index table of FIG.
FIG. 7 is a schematic diagram of an exemplary portion of the stock database of FIG. 5;
Figure 8 is a flow chart illustrating a process for assigning a contract number to a pending transaction.
9 is a schematic diagram of an exemplary portion of a stock database with four stock index entries.
10 is a diagram showing a table showing parameter matching between the stock index of FIG. 9 and the issuing context of a pending transaction; FIG.
11 is a flow chart illustrating a process of defining a new stock index in the stock index table and associating the stock index with the contract number range in the stock database of FIG.

Embodiments of the present invention may be implemented by a processing and database system, such as Global Distribution System (GDS), to provide a flexible method of assigning a contract number based on one or more sets of parameters that define the issuing context of the contract. Airlines, railroads and other stellar providers may issue contracts with contract numbers encoded with information related to the issuance parameters of the contract. These issuance parameters include the type of stock provider, the identity of the stoker provider, the type of contract being issued, the type of contract media, the type of user (e.g., a travel agency, a Central Ticketing Office, an Airline Ticketing Office, The contract issuance point and / or the nature of the contract (e.g., domestic or international). With this encoded information, the billing system can use a revenue accounting method that differentiates the contract type based on the contract number within a pre-defined number range. To this end, the stoker provider may configure the system to allocate a predefined range of contract numbers within the range of existing standard category numbers, such as those assigned by the International Air Transport Association (IATA). This predefined range may be indexed by different combinations of issue parameters. With this feature, for example, different contract number ranges can be assigned to domestic and international air tickets issued for a particular airline in a particular country. According to an embodiment of the present invention, the stoker provider can define a contract and / or a ticket subcategory having an issuance context parameter that satisfies a specific requirement of the stoker provider. This contract subcategory may be recognized by the computing system based solely on the range of numbers from the issued contract to reduce the need for database queries or other processing steps in determining the issuance parameters of the contract.

Referring now to Figure 1, an operating environment 10 in accordance with an embodiment of the present invention includes a Global Distribution System (GDS) 12 that communicates over a network 20, one or more airline systems 14, System 16 and a Billing and Settlement Plan (BSP) system 18. The airline system 14 may be used by the airline system 14 to provide the GDS 12, the travel agent system 16 and / or the BSP system 18 with airline tickets and other travel products, And a CRS (Computer Reservation System). The network 20 may include one or more private and / or public networks (e.g., the Internet) capable of exchanging data between systems.

The GDS 12 may be configured to provide communications between the airline system 14 and the travel agent system 16 so that travel agents can book reservations to the airline system 14 via the GDS 12. To this end, the GDS 12 may maintain a link with the airline system 14 via the network 20. Through these links, the GDS 12 can route reservation requests from the travel agent system 16 to the airline system 14. The travel agent system 16 can book flights to a number of airlines via a single connection with the GDS 12.

The BSP system 18 may function as an intermediary between the airline and the travel agent systems 14, 16. To this end, the BSP system 18 may include a revenue accounting module 82 (FIG. 5) that manages the flow of data and funds between the airline system 14 and the travel agent system 16. The BSP system 18 may provide a single point of connection for the airline system 14 and the travel agent system 16 so that all payment information passes through the BSP system 18. There may be one BSP responsible for handling all settlement and settlement for a particular country or group of countries. The ticketing process may involve the travel agency reporting the sale of the ticket to the corresponding BSP in the airline name. In the United States, Airline Reporting Corporation (ARC) typically provides this service. In either case, the BSP can act as a business process outsourcer (BPO) that provides a clearing house that clears the accounts between travel agents, transportation carriers, active airlines, or any other transaction parties. The appropriate airline can thereby collect fees to provide airline seats through the BSP. The BSP may issue a ticket to the traveler, thereby acting as a stoker provider.

Airline tickets purchased through one of the airline system 14, the travel agent system 16 and / or the BSP system 18 may entail booking, pricing and ticketing flights. Booking a flight may include checking airline inventory for availability of the flight. This check may include sending a booking request from the validity system 14, 16, 18 to the GDS 12 that may query the airline system 14 for flight availability. If there is a seat available for the requested flight, the flight can be booked and the carrier airline inventory will be reduced to reflect the booking. As part of the bookkeeping process, a contract number providing a number that uniquely identifies the transaction may be issued and assigned to the ticket.

2, in the operating environment 10, the GDS 12, the airline system 14, the travel agent system 16, and the BSP system 18 may communicate with one or more computer devices or systems, for example, an exemplary computer system (22). The computer system 22 may include a processor 24, a memory 26, a mass storage memory device 28, an input / output (I / O) interface 30 and a user interface 32.

The processor 24 may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, electric field programmable gate array, programmable logic device, state machine, logic circuit, analog circuit, Or any other device that manipulates the signal (analog or digital) based on an operating command stored in the memory. The memory 26 may be a read only memory (ROM), a random access memory (RAM), a volatile memory, a non-volatile memory, a static random access memory (SRAM), a dynamic random access memory But may include a single memory device or a plurality of memory devices, including, but not limited to, any other device capable of storing information. The mass storage memory device 28 may include a data storage device, e.g., a hard drive, an optical drive, a tape drive, a non-volatile solid state device, or any other device capable of storing information. The database 36 may reside in the mass storage memory device 28 and may be used to collect and organize the data used by the various systems and modules described herein.

The processor 24 may operate under the control of an operating system 38 resident in the memory 26. The operating system 38 manages computer resources to include instructions executed by the processor 24 in computer program code embodied in one or more computer software applications, such as applications 40 residing in memory 26 . In an alternative embodiment, the processor 24 may execute the application 40 directly, in which case the operating system 38 may be omitted. One or more data structures 42 may reside in memory 26 and may be used by processor 24, operating system 38 and / or application 40 to store or manipulate data.

The I / O interface 30 may provide a machine interface that operatively connects the processor 24 to other devices and systems, such as the network 20. The application 40 may operate in cooperation with the network 20 by communicating via the I / O interface 30 to provide various features, functions, and / or modules, including embodiments of the invention. The application 40 may further comprise program code that is executed by one or more external resources (not shown), or that relies on functions and / or signals provided by other systems or network components external to the computer system 22 can do. In fact, hardware and software configurations are nearly endless, so those of ordinary skill in the art will appreciate that embodiments of the present invention may include applications located outside of computer system 22, (Hardware and software) that is distributed among computers, other external resources, or served through a network 20, such as a cloud computing service.

The user interface 32 may be operably connected to the processor 24 of the computer system 22 in a known manner in which the user interacts directly with the computer system 22. [ The user interface 32 may include video and / or alphanumeric displays, touch screens, speakers, and any other suitable audio, visual and / or tactile indicators that may provide information to the user. User interface 32 may be an input device such as an alphanumeric keyboard, pointing device, keypad, push button, control knob, microphone, etc., which may receive commands or may be input from a user and transmit input to processor 24. [ And a control unit.

Referring now to FIG. 3, contract number 50 may include a code that includes a stock provider code 52, a form code 54, and a serial number 56. The code may include any number of alphabetic characters, any number of numeric characters, or a combination of alphabetic and numeric characters. In an exemplary embodiment specific to the airline industry, the contract number 50 includes a three-digit stock supplier code 52 (also referred to as an airline code), a two- or three-digit form code 54, Digit serial number 56, which may be a 13-digit code. The form code 54 may be one of a plurality of form codes 54 defined by the IATA in which each form code 54 corresponds to the standard category of the issuance context for that contract.

FIG. 4 shows an exemplary set 60 of a contract number 50 that may be associated with a particular stock provider. The set 60 of contract numbers 50 may include a plurality of standard categories 62. Each standard category 62 may be associated with a number range 64 defined by a corresponding form code 54. In accordance with an embodiment of the present invention, one or more of the standard categories 62 may be further divided into a plurality of subcategories 66 each associated with a corresponding subcategory number range 68. By way of example, the form code "AA" corresponding to the standard category J may be a number (e.g., 24) that defines an issuance context that includes a parameter indicating that the contract is for an electronic ticket or & have. The issuance context may include additional parameters indicating that the contract is for a ticket electronically issued by the airline defined by the stellar provider code 52. [ Similarly, the form code BB corresponding to the standard category (K) includes a parameter indicating that the contract is for a ticket electronically issued by the travel agent, and includes a number (for example, 22 ). The form code (CC) corresponding to the standard category (D) includes a parameter indicating that the contract is for an electronic miscellaneous document (EMD) issued by the airline, and includes a number (for example, 82 ). The form code DDD may be a number (e.g., 457) corresponding to a standard category G that defines the issuing context of the contract, including a parameter indicating that the contract is for an EMD issued by a travel agent. Other standard categories defined by the IATA are category (H) indicating that the contract is in the form of a paper ticket; A category N indicating that the contract is for an MCO (Miscellaneous Charges Order); And category X indicating that the contract is for excess cargo (XSB).

The subcategory 66 may be defined to specify additional issue context parameters within the standard category 62. The subcategory may be defined by the stoker provider (e.g., an airline) such that the subcategory 66 is specified to the stock provider defined by the stock provider code 52. This subcategory 66 may include additional publishing context parameters such as the issuance point (e.g. France), the type of agreement (e.g., ticket, EMD, MCO, XSB, etc.) Electronic, or paper), a user type (e.g., a travel agency, an airline ticketing office or a central ticketing office), a stakeholder type (e.g., an airline, a railroad transport company), a stark provider identity (e.g., Air France) / RTI > and / or any other suitable issue context parameters. For example, the subcategory (J ₁ ) may include a contract with an issuance context that includes a parameter indicating that the contract is for a ticket electronically issued by an airline with a retail store in France. In contrast, subcategory J ₂ may include an agreement with an issuance context that includes a parameter indicating that the contract is for a ticket electronically issued by an airline that includes only segments provided by a valid shipping company.

Thus, the airline system 14, BSP system 18, or other appropriate system may determine additional characteristics of the travel product beyond being conveyed by the form code 54 based only on the subcategory number range of the contract number. The subcategory number range feature allows the ticket processing system to determine additional travel product characteristics without having to ask the database. Embodiments of the present invention may reduce processing time and resource requirements compared to conventional systems having a contract number set 60 without sub-categories 66. [ By subcategory 66 within the standard category 62, the subcategory number range 68 is a tool that assigns the contract number to a lower granularity than may be possible in the standard category 62 only, To the stoker provider. The subcategory number range feature allows the stellar provider to customize a set 60 of contract numbers 50. This customization can deliver issuance context parameters that address the specific needs of the stoker provider while maintaining compatibility with legacy, non-featured ticket processing systems.

Embodiments of the present invention may provide a flexible system by which a stock provider can select publish context parameters to distinguish within a standard category. The subcategory 66 may be defined for an issuance context that is specific to that stakeholder. With this feature, the stoker provider can assign a specific number range to a transaction corresponding to a particular issuance context without worrying that other stoker providers will format the contract number. Since the subcategory 66 is independently limited from the stock provider code 52, the same subcategory number range can be assigned to different issuance contexts by different stock providers. By way of example, an EMD issued by an airline with a stark provider code of '132' may limit the contract number in the number range 132-82-13000000 to 132-82-13999999 to identify the contract for excess baggage service have. At the same time, another airline with a stark provider code of 456 can use this same subcategory number range (82-13000000 to 82-13999999) to identify the contract for the EMD and add the payable seat characteristics to the ticket.

Referring now to FIG. 5, the contract number assignment system 70 may include a stock allocation module 72 and a reporting module 74. The stall assignment module 72 and the reporting module 74 may be provided by the GDS 12 as shown or may be provided independently of the GDS 12. In either case, the stock allocation module 72 may communicate with the issuance platform 80 and the reporting module 74. The stock allocation module 72 may include a stock index table 76 and a stock database 78 that cooperatively operate to provide a contract number that matches the issuing context of the contract for which the contract number is being requested. The publishing platform 80 may be part of an airline system 14, a travel agent system 16, a BPS system 18, or any other system that issues contracts for travel products. The reporting module 74 may communicate with a revenue accounting module 82 that may be provided by the BSP system 18. The reporting module 74 may be configured to receive the contract number and issuance context data from the stock allocation module 72. The reporting module 74 may configure this data in a suitable format and provide the data to the revenue accounting module 82. In this manner, the BSP system 18 may identify the contract issued by the issuance platform 80 based on the assigned contract number provided by the stow allocation module 72. [

The stock allocation module 72 can manage a plurality of contract numbers for each of a plurality of stock providers. To this end, the stowage allocation module 72 may be configured to store, for example, a stark database of a given stalk provider (e.g., an airline) by adding, deleting or displaying different agreement numbers corresponding to different types of documents that may be issued by the stalk provider (78). The stall assignment module 72 may configure a set 60 of contract numbers 50 of a given stoker provider according to a parameter list that includes the issuance context of that contract.

Referring now to FIG. 6, a table 90 illustrates an exemplary portion of a stock index table 76 in accordance with an embodiment of the present invention. The table 90 may include a column for each of a plurality of parameters collectively defining an issuance context for each of a plurality of stark issuing context subcategories. Thus, in the table 90, each stock may have an issuance context defined by a row of the table 90. The parameters defining the issuance context include a user type parameter 92, a issuance point parameter 93, a stock provider type parameter 94, a stock provider parameter 95, a contract type parameter 96, a contract media parameter 97, And may include, but is not limited to, a property parameter 98 of the contract. The user type parameter 92 may define the entity performing the transaction. The object may be an airline ticketing office or a central ticketing office, a travel agent, or any other seller of travel products. The issuing point parameter 93 may define the location of the point of sale. That is, the issuing point may be the location of the system user who performed the transaction that caused the issuance of the contract. The stakeholder type parameter 94 may define the type of entity that issued or distributed the contract. Exemplary stoker provider types include, but are not limited to, airlines, BSPs, railroad companies, or airline reporting companies. The stakeholder parameter (95) can identify the specific mechanism that distributes the contract. The contract type parameter 96 may identify whether the transaction is for a ticket, or for some other product, such as EMD, MCO or XSB. The contract media parameter 97 can identify whether the contract is in an electronic, paper or virtual form. The contract property parameter 98 may include an identifier that allows the stock index table 76 to identify the type of contract handled by the issuance platform 80, for example, the type of contract for domestic or international flights . The stark index 100 may include a specific combination of parameters 92-98 to define the issuance context. Thus, the issuance context of the contract in the stock database 78 can be identified by the stock index 100.

The staked index table 76 enables to define and index the stoker provider contract based on the issuance context parameters 92-98. The STOCK INDEX TABLE 76 allows the contract limitation to be separated from the contract number range storage and handling. By way of example, a single STOCK index 100 may be defined for each existing 7-uplet that defines the issuance context for an agreement in the air travel industry. A separate subcategory 66 of the issuance context may be defined in a final 1: 1 relationship between each 7-ascet and its corresponding stock index 100 in the stock index table 76. In one embodiment of the present invention, the stock index table 76 may be managed so that the contract number conforms to an Automated Baggage Rule (ABR) issued by the IATA.

Referring now to FIG. 7, a table 110 illustrates an exemplary portion of a stock database 78 in accordance with one embodiment of the present invention. The table 110 may include columns for a stock provider parameter 95, a stock index 100, an office ID parameter 112, a contract number range 114, and a contract description field 116. Within the contract number range 114, each column entry can define a contract number range. The contract number can be assigned from this range to a contract having an issuance context corresponding to the stock index 100. Tables 90 and 110 in FIGS. 6 and 7 are shown as having a particular number of rows and columns, each of which is shown as hosting a particular issue context, parameter, contract number range, etc., Embodiments of the present invention are not limited to the illustrated table configurations. Thus, those of ordinary skill in the art will appreciate that embodiments of the present invention include a stock index table 76 and a stock database 78 having different numbers of rows, columns, parameters, and / or number ranges You can understand that you can.

Referring now to FIG. 8, a flow diagram illustrates an exemplary process 120 for assigning a contract number from a stock database 78. In response to indicating that the traveler wishes to execute a transaction (e.g., to book a flight), the publishing platform 80 may send an allocation request 122 to the stock allocation module 72. In response to receiving the allocation request 122, the stock allocation module 72 may send the query 124 to the stock index table 76. The query 124 may include a context issue parameter for the transaction. In response to receiving the query 124, the stock index table 76 may attempt to identify the stock index 100 that matches the issuance context of the transaction. In response to identifying the stock index 100 having a parameter that matches the issuance context of the transaction, the stock index table 76 includes a response 126 including the stock index 100 To the stochastic allocation module 72.

In response to receiving the response 126, the stock allocation module 72 sends a query 128 to the stock database 78 requesting the available contract number from the contract number range 114 matching the stock index 100, As shown in Fig. In response to receiving the query 128, the stark database 78 may identify the next available contract number from the contract number range 114 corresponding to the stock index 100 and / or the office ID 112 have. The stark database may mark the identified contract number as assigned and send a response 130 containing the identified contract number to the stow allocation module 72. In response to receiving the contract number from the stock database 78, the stock allocation module 72 may transmit the allocation response 132 to the issuance platform 80. [ The publishing platform 80 may complete the transaction by issuing a contract with the received contract number.

If the staked index table 76 can not identify the staked index 100 having parameters that provide an exact match with the issuing context of the pending transaction, then the staked allocation module 72 may determine that the staked index 100 Can be determined. The stochastic allocation module 72 can determine the stochastic index 100 that performs the best matching based on the number of matching parameters and the relative weight assigned to each matching parameter. In one embodiment of the invention, the relative weights of each parameter in the stock index table 76 may be assigned a value based on a scale where each weight is a power of two. That is, each parameter can be associated with a number of binary numbers, and the weight of the parameter corresponds to the numerical value of the number. Each parameter may be provided with a unique power of two, and the top parameter has a maximum weight.

To determine the best matching stochastic index 100, the stochastic allocation module 72 may select a stochastic index 100 having a maximum parameter number that matches the issuance context parameter of the pending transaction. If two or more of the stock indexes 100 have this matching parameter number, the stock allocation module 72 may calculate the sum of the weights of the matching parameters for the combined tied index 100. The stock index 100 having the maximum sum may be selected to be the best matching stock index 100 and returned to the issuance platform 80.

Referring now to Figures 9 and 10, an exemplary stock index table 140 includes parameter weights for each of the seven parameters as follows: (1) airline parameter weight = 2 ¹⁰ ; (2) Stack provider parameter weight = 2 ⁹ ; (3) contract type parameter weight = 2 ⁸ ; (4) contract media parameter weight = 2 ⁷ ; (5) User type parameter weight = 2 ⁶ ; (6) Issuing point parameter weight = 2 ⁵ ; And (7) contract property parameter weight = 2 ⁴ . The exemplary allocation request 122 includes the following context issuance parameters: (1) stoker provider type = airline; (2) Stack provider = 057; (3) Contract type = ticket; (4) Contracted media = electronic; (5) user type = none; (6) Issuing point = FR; And (7) nature of the contract = domestic. Since the exemplary allocation request 122 does not exactly match any of the stock indexes 100 in the table 140, the stock allocation module 72 can determine the best matching for the request.

The weighted matching for each of the stock indexes in the exemplary allocation request 122 is illustrated by the table 150 shown in FIG. To determine the best match, the stall assignment module 72 first determines how many of the parameters in each staked index 100 match the parameters of the issue context for the pending transaction. In this example, each of the stock indexes I1, I2, and I3 has six matching parameters, and the stock index I4 has five matching parameters. The stock allocation module 72 calculates the following weighted sum: I1 = 11111100000 (BIN) = 2016 (DEC); I2 = 11111010000 (BIN) = 2000 (DEC); And a staked index (I1-I3) that produces I3 = 11101110000 (BIN) = 1904 (DEC). Thus, in this exemplary case, the best match to the received query may be the stock index I1, which may be returned to the issuance platform 80.

Referring now to FIG. 11, a flow diagram illustrates an exemplary process 160 for defining a new stock index 100 in a stock index table 76. Defining the new STOCK index 100 may be initiated by entering system commands into the GDS 12 via a user terminal (not shown). The command may include all issuance context parameters associated with the transaction for which the staked index 100 is requested, and a corresponding number range to be associated with the staked index. As an example of a cryptographic command that can generate this association,

> DSLA / CT-TKT / CM-E / SPT-AIR / SP-176 / 1000000000-1099999999.

The command may generate a stock index request 162 requesting to generate a stock index 100 with contract type = ticket, contracted media = electronic, stock provider type = airline, and stock provider = '176' have. This limited stock index 100 may further be associated with the number range 1000000000-1099999999.

In response to receiving the staked index request 162, the staked allocation module 72 may send the request 164 to the staked index table 76. In response to receiving the request 164, the staked index table 76 may determine whether the issuance context parameter in the request 164 exactly matches the parameters of the existing staked index 100. The stock allocation module 72 can search for an existing stock index 100 if the stock index 100 that matches the entered issuance context parameter exactly is already defined in the stock index table 76. [ The STOCK allocation module 72 adds a new STOCK INDEX to the table and updates the new STOCK INDEX 100 with the new STOCK index 100. If the new STOCK index 100 is not yet defined in the STOCK INDEXTABLE table 76, ) With the issue context parameters in request (164). The staked index table 76 may provide the staked index 100 (in some cases, previously existing or newly defined) to the staked allocation module 72 in response 166.

In response to receiving the response 166, the stall assignment module 72 sends a command 168 to the stock database 78, including a stock range (e.g., 1000000000-1099999999) and an associated stock index 100 Can be transmitted. In response to receiving the command 168, the stark database 78 may add a table entry that associates the inputted number range (e.g., 1000000000-1099999999) with the stalk index 100. [

The program code embodying any of the embodiments of the invention described herein may be distributed individually or collectively to a number of different types of program products. In particular, the program code may be distributed using a computer-readable medium and a communication medium, which may include a computer-readable storage medium. A computer-readable storage medium, which is essentially non-volatile, includes volatile and nonvolatile, nonvolatile, nonvolatile, nonvolatile, nonvolatile, nonvolatile, nonvolatile, And removable and non-removable tangible media. The computer readable storage medium may be any of a variety of storage devices including but not limited to RAM, ROM, erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory or other solid state memory technology, CD-ROM), or magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information that can be read by a computer. The communication medium may embody computer readable instructions, data structures, or other program modules. By way of example, and not limitation, communication media may include wired media, e.g., wired networks or direct-wired connections, and wireless media such as acoustic, RF, infrared and other wireless media. Any combination of the above may also be included within the scope of computer readable media.

The methods described herein may be implemented by computer program instructions supplied to a processor of any type of computer to produce a machine having a processor executing instructions and implementing the functions / operations specified herein. The computer program instructions may be stored on a computer readable medium that can cause the computer to function in a particular manner. To this end, the computer program instructions may be loaded into a computer to perform a series of operational steps to create a computer-implemented process in which the executed instructions provide a process for implementing the functions / operations specified herein.

Further, the program code described herein may be identified based on an application or software component that implements the program code in a particular embodiment of the invention. It is understood, however, that the term " any specific program " below is used for convenience only and that the invention is not limited to use with any particular application identified and / or dictated by the term. It is further understood that the various features, applications, and devices described herein may be used alone or in any combination. Furthermore, there are a variety of ways in which a computer program can consist of routines, procedures, methods, modules, objects, etc., and in which program functions reside within a common computing system (e.g., operating system, library, API, It is to be understood that the present invention is not limited to the specific configurations and assignments of the program functions described herein, as the manner in which they can be assigned to the software layer and / or over one or more hardware platforms is generally never ending.

Although the embodiments of the present invention have been illustrated by explaining a number of examples, these embodiments are described in considerable detail, but applicants are not intended to limit or limit the appended claims to such details. Additional advantages and modifications will readily occur to those of ordinary skill in the art. The invention is not limited to the specific details, representative methods, and examples shown and described in the broader aspects. Accordingly, the present invention may be devised without departing from the spirit and scope of the inventor's general inventive concept.

Claims (21)

Claims 1. A method for configuring a contract number in a database, the database comprising a plurality of sets of contract numbers, each set of contract numbers corresponding to one of a plurality of stock providers and comprising a plurality of standard category number ranges,
Defining, for a first set of contract numbers corresponding to a first stock provider, a first subcategory number range corresponding to a first issue context within a first standard category number range; And
And for the first set of contract numbers, defining a second subcategory number range corresponding to a second issuance context within the first standard category number range,
Wherein a first contract issued to the first stock provider and having a first contract number including a first number from the first subcategory number range is provided to the first stock provider based on the first contract number A second contract issued to the first stock provider and having a second contract number including a second number from the second sub-category number range is identified by the second contract number, 2 < / RTI > issuance context in the database. The method according to claim 1,
A third subcategory number corresponding to a third issuance context different from any of the first and second issuance contexts within the first standard category number range for the second set of contract numbers corresponding to the second stellar provider, Further comprising the step of defining a range,
The third contract having a third contract number issued to the second stock provider and including a third number from the third sub-category number range, the third contract having the third issuance context based on the third contract number Wherein the contract number is identifiable to be included in the database. 3. The method of claim 2,
Wherein the third subcategory number range overlaps with one or more of the first and second subcategory number ranges. The method according to claim 1,
Further comprising the step of qualifying the first contract number by attaching an airline code corresponding to the first stock provider to the first number from the first subcategory number range, How to configure numbers. The method according to claim 1,
Wherein the first issuance context is defined by parameters selected from the group consisting of a user type, a contract type, a contract medium, a nature of a contract, a stark provider type, a stark provider identity and a issuing point. . A non-transient computer readable storage medium,
The non-transient computer readable storage medium storing instructions that when executed by a processor cause the processor to:
Defining, for a first set of contract numbers corresponding to a first stellar provider, a first subcategory number range corresponding to a first issue context within a first standard category number range; And
Performing an operation of limiting the second subcategory number range corresponding to the second issuance context within the first standard category number range for the first set of the contract number,
Wherein the first contract having a first contract number issued to the first stock provider and including a first number from the first subcategory number range is configured to assign the first issuance context based on the first contract number And can be identified as having,
The second contract having a second contract number issued to the first stock provider and including a second number from the second subcategory number range is configured to include the second issuance context based on the second contract number Wherein the computer readable medium is identifiable as having a computer readable medium. As an apparatus,
A processor; And
And a memory containing instructions,
Wherein the instructions, when executed by the processor, cause the device to:
Defining, for a first set of contract numbers corresponding to a first stellar provider, a first subcategory number range corresponding to a first issue context within a first standard category number range; And
Performing an operation of limiting the second subcategory number range corresponding to the second issuance context within the first standard category number range for the first set of the contract number,
Wherein the first contract having a first contract number issued to the first stock provider and including a first number from the first subcategory number range is configured to assign the first issuance context based on the first contract number And can be identified as having,
The second contract having a second contract number issued to the first stock provider and including a second number from the second subcategory number range is configured to include the second issuance context based on the second contract number Wherein the device is identifiable to be equipped. 8. The method of claim 7,
Wherein the instructions, when executed by the processor, cause the device to:
A third subcategory number corresponding to a third issuance context different from any of the first and second issuance contexts within the first standard category number range for the second set of contract numbers corresponding to the second stellar provider, Thereby further performing an operation of limiting the range,
The third contract having a third contract number issued to the second stock provider and including a third number from the third sub-category number range, the third contract having the third issuance context based on the third contract number Wherein the device is identifiable to be equipped. 9. The method of claim 8,
Wherein the third subcategory number range overlaps with at least one of the first and second subcategory number ranges. 8. The method of claim 7,
Wherein the instructions, when executed by the processor, cause the device to:
Further comprising an operation of limiting the first contract number by attaching an airline code corresponding to the first stock provider to the first number from the first subcategory number range, . 8. The method of claim 7,
Wherein the first issuance context is defined by a parameter selected from the group consisting of a user type, a contract type, a contract medium, a nature of a contract, a stoker provider type, a stark provider identity and a issuing point. A method for assigning a contract number from a database containing a contract number,
Receiving, at the computer, a first allocation request from a publishing platform, the first allocation request being for a first contract issued to a first stock provider and comprising a first issuing context;
Determining, at the computer, a first stock index matching the first issuance context;
Defining a first contract number in the database that includes a first number from a first subcategory number range associated with the first stock index; And
Sending the first contract number to the publishing platform,
Wherein the first subcategory number range defines a portion of a first standard category number range stored in the database, the first standard category number range includes the first subcategory number range and the second subcategory number range, Wherein the first and second subcategory number ranges are each associated with the first stock provider and the first standard category number range is one of a plurality of standard category number ranges stored in the database. How to. 13. The method of claim 12,
Receiving, at the computer, a second allocation request from the publishing platform, the second allocation request being for a second contract issued to a second stoker provider and comprising a second issuing context; step;
Determining, at the computer, a second stock index matching the second issuance context;
Defining a second contract number in the database that includes a second number from a third subcategory number range associated with the second stock index; And
And sending the second contract number to the publishing platform,
The third subcategory number range being stored in the database and defining a second portion of the first standard category number range associated with the second stock provider. 14. The method of claim 13,
And the third subcategory number range overlaps with at least one of the first and second subcategory number ranges. 13. The method of claim 12,
Wherein the first stock index is associated with the first subcategory number range in the stock index table and the second stock index is associated with the second subcategory number range in the stock index table. How to. 13. The method of claim 12,
Wherein the step of defining the first contract number comprises attaching the airline code to the first number. 13. The method of claim 12,
Wherein the first issuance context is defined by a parameter selected from the group consisting of a user type, a contract type, a contract medium, a nature of a contract, a stoker provider type, a stark provider identity and a contract issuance point. 13. The method of claim 12,
Wherein the first stock index is one of a plurality of stock indexes, and the step of determining a first stock index matching the first issuance context comprises:
Determining, for each of the plurality of stock indexes of the plurality of stock indexes, the number of parameters of the first issuance context matching the corresponding parameter of the stock index;
Selecting the STACK index having a maximum number of parameters matching the matching STACK index; And
Selecting a stock index having a highest weighted sum of matching parameters in the matching stock index, in response to the two or more stock index having the same number of matching parameters as the matching index; Way. 19. The method of claim 18,
Wherein each parameter is weighted based on a power of two. As an apparatus,
A processor; And
And a memory containing instructions,
Wherein the instructions, when executed by the processor, cause the device to:
Receiving a first allocation request from a publishing platform, the first allocation request being for a first contract issued to a first stock provider and comprising a first publishing context;
Determining a first stock index that matches the first issuance context;
Defining a first contract number in the database that includes a first number from a first subcategory number range associated with the first stock index; And
To transmit the first contract number to the publishing platform,
Wherein the first subcategory number range defines a portion of a first standard category number range stored in the database, the first standard category number range includes the first subcategory number range and the second subcategory number range, Wherein the first and second subcategory number ranges are each associated with the first stock provider and the first standard category number range is one of a plurality of standard category number ranges stored in the database. A non-transient computer readable storage medium,
The non-transient computer readable storage medium storing instructions that when executed by a processor cause the processor to:
Receiving a first allocation request from a publishing platform, the first allocation request being for a first contract issued to a first stock provider and comprising a first publishing context;
Determining a first stock index that matches the first issuance context;
Defining a first contract number in the database that includes a first number from a first subcategory number range associated with the first stock index; And
To transmit the first contract number to the publishing platform,
Wherein the first subcategory number range defines a portion of a first standard category number range stored in the database, the first standard category number range includes the first subcategory number range and the second subcategory number range, Wherein the first and second subcategory number ranges are each associated with the first stock provider and the first standard category number range is one of a plurality of standard category number ranges stored in the database. Readable storage medium.

Images