Group ticket information generation method, system and device and electronic equipment

Abstract

The invention discloses a group ticket information generation method, system and device and electronic equipment, and relates to the technical field of information processing. The method comprises the steps that a rule file of group ticket information to be generated is acquired, and the rule file is used for representing a rule for generating the group ticket information; analyzing the rule file to obtain time scheduling information of the group ticket information to be generated, the time scheduling information being used for representing a time range of generating the group ticket information; based on the time scheduling information, determining the number of orders contained in the to-be-generated group ticket information; and generating group ticket information based on the order quantity. The technical problem of low group ticket information generation efficiency is solved.

Description

Technical Field

[0001] The present application relates to the field of information processing technology, and in particular to a method, system, device and electronic device for generating group ticket information. Background Art

[0002] Currently, when airlines sell group tickets, they require ticket sales agents to submit group ticket applications first. The airlines will review the group ticket applications according to specific rules, and after the review is passed, the airlines will allocate seats and feedback to the ticket sales agents, who will then make the payment and issue the tickets.

[0003] In the related art, airlines and ticket sales agents determine the group ticket information of the planned group through offline communication. The communication cost is high, it takes a lot of time, and the degree of automation is low, so there is a technical problem of low efficiency in generating group ticket information.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method, system, device and electronic device for generating group ticket information, so as to at least solve the technical problem of low efficiency in generating group ticket information.

[0006] According to one aspect of an embodiment of the present application, a method for generating group ticket information is provided. The method may include: obtaining a rule file of the group ticket information to be generated, wherein the rule file is used to represent the rule for generating the group ticket information; parsing the rule file to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; determining the number of orders included in the group ticket information to be generated based on the time scheduling information; and generating the group ticket information based on the number of orders.

[0007] Optionally, group ticket information is generated based on the order quantity, including: generating total group ticket information based on the order quantity; determining flight time information of the group ticket information to be generated in the total group ticket information based on the time scheduling information; and generating group ticket information based on the flight time information.

[0008] Optionally, generating group ticket information based on flight time information includes: calling a flight query system based on the flight time information and flight itinerary information in a rule file to determine flight information for which group ticket information is to be generated; generating group ticket information based on the flight information.

[0009] Optionally, after generating the group ticket information based on the flight information, the method further includes: determining price information matching the group ticket information based on an air fare publishing system; and publishing the group ticket information including the price information to the target object.

[0010] Optionally, publishing the group ticket information including the price information to the target object includes: based on the historical order data of the target object, publishing the group ticket information including the price information to the matching target object.

[0011] Optionally, the rule file is parsed to obtain the time scheduling information of the group ticket information to be generated, including: verifying the format of the rule file, and converting the verified rule file into a rule object, wherein the rule object at least includes the time scheduling information.

[0012] According to another aspect of the embodiment of the present application, a group ticket information publishing system is also provided. The system may include: a rule file acquisition component, used to obtain a rule file of the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; a rule file parsing component, used to parse the rule file to obtain the time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; an order information calculation component, used to determine the number of orders contained in the group ticket information to be generated based on the time scheduling information; and a group ticket information creation component, used to generate the group ticket information based on the order quantity.

[0013] Optionally, the system further includes: a price information determination component for determining price information matching the group ticket information based on the air fare publishing system; and a group ticket information publishing component for publishing the group ticket information including the price information to the target object.

[0014] According to another aspect of the embodiment of the present application, a device for generating group ticket information is also provided. The device may include: an acquisition unit, used to acquire a rule file of the group ticket information to be generated, wherein the rule file is used to represent the rule for generating the group ticket information; a parsing unit, used to parse the rule file to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; a determination unit, used to determine the number of orders included in the group ticket information to be generated based on the time scheduling information; and a generation unit, used to generate the group ticket information based on the number of orders.

[0015] According to another aspect of an embodiment of the present application, a non-volatile storage medium is also provided, including: the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute any method for generating group ticket information.

[0016] According to another aspect of an embodiment of the present invention, a processor is further provided, the processor being used to run a program, wherein the method for generating group ticket information in an embodiment of the present invention is executed when the program is run.

[0017] According to another aspect of an embodiment of the present application, there is also provided an electronic device, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement any method for generating group ticket information.

[0018] According to another aspect of the embodiment of the present application, a computer program product is also provided. The computer program product may include a computer program, wherein the computer program is configured to execute any of the above-mentioned methods for generating group ticket information when running.

[0019] According to another aspect of the embodiment of the present application, a computer program product is also provided. The computer program product may include a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and the computer program is configured to execute any of the above-mentioned group ticket information generation methods when running.

[0020] According to another aspect of the embodiment of the present application, a computer program is further provided, which is configured to execute any of the above-mentioned methods for generating group ticket information when running.

[0021] In an embodiment of the present application, a rule file of the group ticket information to be generated is obtained, wherein the rule file is used to represent the rules for generating the group ticket information; the rule file is parsed to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, the number of orders included in the group ticket information to be generated is determined; based on the number of orders, the group ticket information is generated, thereby achieving the technical effect of improving the efficiency of generating the group ticket information, and further solving the technical problem of low efficiency in generating the group ticket information. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 is a flow chart of a method for generating group ticket information according to an embodiment of the present application;

[0024] Figure 2 It is a schematic diagram of a civil aviation group ticket generation device based on file import according to an embodiment of the present application;

[0025] Figure 3 It is a flow chart of a method for generating civil aviation group tickets based on file import according to an embodiment of the present application;

[0026] Figure 4 It is a structural schematic diagram of a system for generating group ticket information according to an embodiment of the present application;

[0027] Figure 5 It is a structural schematic diagram of a device for generating group ticket information according to an embodiment of the present application;

[0028] Figure 6 is a schematic block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] According to an embodiment of the present application, a method embodiment of a method for generating group ticket information is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0032] Figure 1 is a flow chart of a method for generating group ticket information according to an embodiment of the present application. Figure 1 As shown, the method may include the following steps:

[0033] Step S102, obtaining a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information.

[0034] In the technical solution provided in the above step S102, a rule file of the group ticket information to be generated can be obtained. The group ticket information to be generated can be the order information of the travel group (planned group) to be generated. The rule file can be used to represent the rules for generating the group ticket information, and the rule file can be uploaded by the manager of the business department of the airline (business department administrator).

[0035] Optionally, after the sales department administrator uploads the rule file, the rule file uploaded by the sales department administrator can be obtained, and the rule file can be used to represent the rules for generating group ticket information.

[0036] Step S104, parsing the rule file to obtain time scheduling information for generating the group ticket information, wherein the time scheduling information is used to indicate the time range for generating the group ticket information.

[0037] In the technical solution provided in the above step S104, after obtaining the rule file of the group ticket information to be generated, the rule file can be parsed to obtain the time scheduling information of the group ticket information to be generated. The time scheduling information can be used to indicate the time range for generating the group ticket information, and the time scheduling information can at least include information such as the start date (start time), the end date (end time), the exclusion time, the departure cycle, and the number of weeks between groups.

[0038] Optionally, after obtaining the rule file, the rule file can be parsed, the format of the rule file can be checked for legality, the rule file can be converted into a rule object, and the rule object can be stored in memory. After parsing the rule file to obtain the rule object, time scheduling information such as the start date, end date, departure period, and team interval weeks in the rule object can be obtained.

[0039] Step S106, based on the time scheduling information, determine the number of orders included in the group ticket information to be generated.

[0040] In the technical solution provided in the above step S106, after parsing the rule file to obtain the time scheduling information of the group ticket information to be generated, the number of orders included in the group ticket information to be generated can be determined based on the obtained time scheduling information.

[0041] Optionally, after obtaining the time scheduling information such as the start date, end date, departure period, team interval weeks, etc. in the rule object, the number of planned group orders that can be generated this time (ie, the order quantity) can be calculated and synchronized to the airline.

[0042] Step S108, generating group ticket information based on the order quantity.

[0043] In the technical solution provided in the above step S108, after determining the number of orders included in the group ticket information to be generated based on the time scheduling information, the group ticket information can be generated based on the determined number of orders. The group ticket information can also be called a planned group small order, a planned group order, or a system group small order.

[0044] Optionally, after calculating the number of orders expected to be generated by this rule file based on the time scheduling information such as the start time, end time, exclusion time, departure cycle, etc. in the rule object, a large group order (planned group order, group ticket total information) can be generated based on the generated number of orders. The large group order includes basic order information such as the specific number of people in each order, itinerary information, and contact information. Further, based on the large group order, a small group order (i.e., group ticket information) can be generated.

[0045] In an embodiment of the present application, a rule file of the group ticket information to be generated is obtained, wherein the rule file is used to represent the rules for generating the group ticket information; the rule file is parsed to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, the number of orders included in the group ticket information to be generated is determined; based on the number of orders, the group ticket information is generated, thereby achieving the technical effect of improving the efficiency of generating the group ticket information, and further solving the technical problem of low efficiency in generating the group ticket information.

[0046] The above embodiments of the present application are further described below.

[0047] In some embodiments of the present application, step S108, generating group ticket information based on the order quantity, includes: generating total group ticket information based on the order quantity; determining flight time information for the group ticket information to be generated in the total group ticket information based on the time scheduling information; generating group ticket information based on the flight time information.

[0048] In this embodiment, after determining the number of orders included in the group ticket information to be generated based on the time scheduling information, the total group ticket information can be generated based on the generated number of orders. Further based on the time scheduling information, the flight time information of the group ticket information to be generated in the total group ticket information can be determined. After generating the flight time information of the group ticket information to be generated, the group ticket information can be generated based on the generated flight time information. Among them, the total group ticket information can also be divided into a large group order and a planned group large order. The flight time information can be the flight departure date of the planned group sub-order (planned group small order).

[0049] Optionally, based on the number of planned group orders (order quantity), a planned group big order can be generated, and the generated planned group big order can be saved to the database. The planned group big order information can include the big order number, the number of sub-orders, basic order information, etc. Further, based on the time scheduling information such as the start date, the end date, the departure cycle, and the number of weeks between teams, the flight departure date (flight time information) of each sub-order of the planned group can be calculated. After the flight time information of the group ticket information to be generated is generated, the group ticket information can be generated based on the generated flight time information.

[0050] In some embodiments of the present application, group ticket information is generated based on flight time information, including: based on the flight time information and the flight itinerary information in the rule file, calling a flight query system to determine the flight information for the group ticket information to be generated; generating group ticket information based on the flight information.

[0051] In this embodiment, after determining the flight time information of the group ticket information to be generated in the group ticket total information based on the time scheduling information, the flight query system can be called based on the generated flight time information and the flight itinerary information in the rule file to determine the flight information of the group ticket information to be generated. Further based on the generated flight information, the group ticket information can be generated. Among them, the flight itinerary information can be the itinerary and flight number information in the rule file. The flight query system can be a flight query system of an airline. The flight information may include information such as flight number, cabin, departure time, arrival time, terminal, etc.

[0052] Optionally, after calculating the flight departure date of the planned group order based on time scheduling information such as the start date, end date, departure cycle, and team interval weeks, the airline's flight query system can be called in combination with the itinerary and flight number information in the rule file to obtain flight information including flight number, cabin class, departure time, arrival time, terminal, etc.

[0053] Optionally, based on the flight information returned by the flight query system, the airline's reservation system can be called and a thread pool can be started to generate passenger name records (PNRs) in batches. After the PNRs are successfully generated, a planned group order corresponding to each PNR can be generated in batches, and the corresponding information of the planned group order and the PNR can be saved in a database.

[0054] This embodiment connects to the airline's flight query system to query flight information such as flight departure time, arrival time, terminal, etc., and based on the received flight information, calls the airline's ticket sales system to generate a planned group small order.

[0055] In some embodiments of the present application, after generating group ticket information based on flight information, the method further includes: determining price information matching the group ticket information based on an airline fare publishing system; and publishing the group ticket information including the price information to the target object.

[0056] In this embodiment, after the group ticket information is generated based on the flight information, the price information matching the group ticket information can be determined based on the air fare publishing system, and the group ticket information including the price information can be further published to the target object. The target object can be an airline ticket sales agent (can be referred to as an agent), which is only an example here and does not specifically limit the type of the target object. The air fare publishing system can be an airline's fare publishing system.

[0057] Optionally, according to the number of people in the planned group order, the airline's fare publishing system is connected to select a suitable price, and the price information is saved in the generated planned group order. The planned group order containing the price information can be further published to the airline's ticket sales agent.

[0058] Optionally, the revenue staff of the airline can manage the planned group large orders and the planned group small orders. The revenue staff can manually enter the order price information according to the flight cabin information in each planned group small order, or query the airline's freight rate publishing system to batch import the price information of the planned group small orders. Further, the revenue staff can query the airline's flight plan information according to the flight number in each planned group small order, and complete the host's seat allocation and confirmation according to the actual passenger load factor of the flight. Finally, the planned group small order containing the price information is released to the airline's ticket sales agent.

[0059] In some embodiments of the present application, group ticket information including price information is published to a target object, including: based on historical order data of the target object, publishing the group ticket information including price information to a matching target object.

[0060] In this embodiment, after determining the price information matching the group ticket information based on the air fare publishing system, the group ticket information including the price information can be published to the matching target object based on the historical order data of the target object. The historical order data can be the historical sales data or historical sales order data of the target object.

[0061] Optionally, according to the generated planned group small order and the historical sales data of the airline ticket sales agent, a suitable planned group small order is allocated to the airline ticket sales agent. After receiving the planned group small order, the airline ticket sales agent can receive the group passengers and perform subsequent payment and ticketing operations.

[0062] Optionally, the business department administrator can query the historical sales order data of the agents under the business department for the planned group small orders with confirmed seats, compare the actual number of tickets issued by the agents on this flight recently with the number of orders that have been allocated but not yet issued by the agents, allocate the planned group small orders to specific agents as needed, and notify the agents in time by sending emails or offline methods to avoid wasted seats. After receiving the planned group small order data allocated by the business department, the agent can receive the passenger and make payment and ticketing operations.

[0063] In some embodiments of the present application, step S104, parsing the rule file to obtain the time scheduling information of the group ticket information to be generated, includes: verifying the format of the rule file, and converting the verified rule file into a rule object, wherein the rule object at least includes the time scheduling information.

[0064] In this embodiment, the format of the rule file can be checked for legality, the rule file can be converted into a rule object, and the rule object can be stored in memory. After parsing the rule file to obtain the rule object, time scheduling information such as the start date, end date, departure period, and team interval weeks in the rule object can be obtained.

[0065] In order to facilitate those skilled in the art to better understand the technical solution of the present application, a specific embodiment is now described.

[0066] With the development of tourism, tour groups are becoming more and more popular. When airlines sell group tickets, agents are required to submit group ticket applications first. Airlines review group ticket applications according to specific rules. After the airlines review and assign seats, they will feedback to the agents, who will then make payment and issue tickets. Since tour groups usually have the same departure and arrival places, different departure dates, and certain planning characteristics, the ticket sales of tour groups also need to be planned, so this tour group can be called a planned group.

[0067] In the related technologies, the traditional ticketing method cannot meet the sales needs of airlines, and there is currently no automated method to provide group ticket sales. In actual business scenarios, airlines and agents communicate offline to determine the information related to the group ticket order. The communication cost is high, it takes a lot of time, and the degree of automation is low, resulting in a technical problem of low efficiency in generating group ticket information.

[0068] In order to solve the above problems, the present application proposes a method and device for generating a planned group based on file import. In this method, airline users can create group ticket orders in advance according to historical sales data by setting popular routes or destinations within a period of time, and assign them to agents through the method of publishing agents. The agents directly accept passengers and pay for tickets, thereby achieving the technical effect of improving the efficiency of generating group ticket information, and then solving the technical problem of low efficiency in generating group ticket information.

[0069] Figure 2 is a schematic diagram of a civil aviation group ticket generation device based on file import according to an embodiment of the present application, such as Figure 2 As shown, the automatic generation of planned groups can be achieved through the imported rule file. The civil aviation group ticket generation device based on file import can include: a file parsing component 201, a basic information calculation component 202, an order creation component 203, a price publishing component 204, an information publishing component 205 and an information receiving component 206.

[0070] The file parsing component 201 accepts the file uploaded by the user (airline administrator), verifies the legality of the file format, converts it into a rule object, and stores it in the memory. The basic information calculation component 202 calculates the number of orders expected to be generated by this file based on the formatted rule object generated by the file parsing component 201, the start time, end time, exclusion time, departure cycle and other information in the file, and generates a large order for a series of groups. The large order for a series of groups includes basic order information such as the specific number of people, itinerary information, and contact information in each order. The order creation component 203 receives the result of the basic information calculation component 202, and connects to the airline's flight query system to query the flight departure time, arrival time, terminal and other information. Based on the received flight information, the airline's ticket sales system (airline ticket system) is called to generate a small order for the planned group.

[0071] The price publishing component 204 connects to the airline's fare publishing system according to the itinerary number information in the planned group small order generated by the order creation component 203, selects a suitable price, and saves the price information in the planned group order generated by the order creation component. The information publishing component 205 allocates a suitable planned group small order to the airline's ticket sales agent (agent) according to the planned group small order generated by the order creation component 203 and the historical sales data of the airline's ticket sales agent. The information receiving component 206 refers to the airline's ticket sales agent receiving the planned group order issued by the information publishing component 205, receiving the group passengers, and performing subsequent payment and ticketing operations.

[0072] In this embodiment, the rule file is a prerequisite for generating a planning group. The format of the rule file includes a table (EXCEL), plain text (TXT), etc. The field information contained in the rule file includes but is not limited to the field information in Table 1.

[0073] Table 1 Field information contained in the rule file

[0074]

[0075] Figure 3 is a flow chart of a method for generating civil aviation group tickets based on file import according to an embodiment of the present application, such as Figure 3 As shown, the process of the civil aviation group ticket generation method based on file import may at least include the following steps:

[0076] Step S301, parsing the rule file.

[0077] In the above steps, the business department administrator uploads the file, parses the rule file uploaded by the airline business department manager, verifies the legality of the file format, converts it into a rule object, and stores it in the memory.

[0078] Step S302, calculating the number of PNRs to be generated.

[0079] In the above steps, the number of planned group orders that can be generated this time is calculated based on the start date, end date, departure period, team interval weeks and other information in the rule object, and synchronized to the airline.

[0080] Step S303: persisting system group rule information.

[0081] In the above steps, a large order for the planned group is generated and saved in the database. The large order information includes the large order number / the number of sub-orders / basic order information, etc. Based on the start date, end date, departure cycle, number of weeks between groups, etc., the flight departure date of each sub-order of the planned group is calculated. Combined with the itinerary and flight number information in the file, the airline's flight query system is called to obtain flight information including flight number, cabin, departure and arrival time, terminal, etc.

[0082] Step S304, calling the thread pool to initiate a batch creation PNR event.

[0083] In the above steps, according to the flight information returned by the flight query system, the airline's reservation system is called, and the thread pool is started to generate PNRs in batches.

[0084] Step S305, create an order.

[0085] In the above steps, after the PNR is successfully generated, the planned group small orders corresponding to each PNR are generated in batches, and the corresponding information of the small orders and PNRs is saved in the database.

[0086] Step S306, managing orders.

[0087] In the above steps, the airline revenue personnel can manage the large and small orders of the planned group in step 5.

[0088] Step S307, confirm the price information.

[0089] In the above steps, the revenue personnel first manually enter the order price information according to the flight space information in each small order, or query the airline's freight rate publishing system to batch import the price information of the series group small orders.

[0090] Step S308, confirm the black screen seat status.

[0091] In the above steps, the revenue staff then queries the airline's flight schedule information based on the flight number in each small order, and completes the host's seat allocation and confirmation based on the actual occupancy rate of the flight.

[0092] Step S309, publish the order.

[0093] In the above steps, the business department administrator will query the historical sales order data of the agents under the business department for the small orders with confirmed seats, compare the actual number of tickets issued by the agents on this flight recently and the number of orders that have been allocated but not yet completed by the agents, allocate the series group small orders to specific agents as needed, and notify the agents in time by sending emails or offline methods to avoid wasted seats.

[0094] Step S310, receiving passengers.

[0095] Step S311, payment and ticket issuance.

[0096] In the above steps, after the agent receives the planned group small order data assigned by the sales department, he can receive the passengers and perform payment and ticketing operations.

[0097] The method for generating group ticket information in this embodiment is planned, more in line with the needs of airlines, and is flexible and scalable for airline management. Airline managers can create planned groups according to actual needs and publish them to agents as needed.

[0098] This embodiment is based on the rule file. The airline administrator creates a planned group order and publishes the planned group by assigning agents, which facilitates the airline to flexibly formulate flight plans, improve flight occupancy rates, and increase airline revenues.

[0099] In an embodiment of the present application, a rule file of the group ticket information to be generated is obtained, wherein the rule file is used to represent the rules for generating the group ticket information; the rule file is parsed to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, the number of orders included in the group ticket information to be generated is determined; based on the number of orders, the group ticket information is generated, thereby achieving the technical effect of improving the efficiency of generating the group ticket information, and further solving the technical problem of low efficiency in generating the group ticket information.

[0100] The embodiment of the present application also provides a system for generating group ticket information. Figure 4 is a structural diagram of a system for generating group ticket information according to an embodiment of the present application, such as Figure 4 As shown, the group ticket information generation system 400 may include: a rule file acquisition component 402 , a rule file parsing component 404 , an order information calculation component 406 and a group ticket information creation component 408 .

[0101] The rule file acquisition component 402 is used to acquire the rule file of the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information.

[0102] The rule file parsing component 404 is used to parse the rule file to obtain the time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to indicate the time range for generating the group ticket information.

[0103] Optionally, the rule file parsing component may be a file parsing component that accepts files uploaded by users (airline administrators), performs a validity check on the file format, and converts the file into a rule object and stores it in memory.

[0104] The order information calculation component 406 is used to determine the number of orders included in the group ticket information to be generated based on the time scheduling information.

[0105] Optionally, the order information calculation component can be a basic information calculation component. The basic information calculation component calculates the number of orders expected to be generated by this file based on the formatting rule object generated by the file parsing component and the start time, end time, exclusion time, departure period and other information in the file, and generates a large order for a series of groups. The large order for a series of groups includes basic order information such as the specific number of people in each order, itinerary information, contact information, etc.

[0106] The group ticket information creation component 408 is used to generate group ticket information based on the order quantity.

[0107] Optionally, the group ticket information creation component can be an order creation component. The order creation component receives the results of the basic information calculation component and connects to the airline's flight query system to query flight departure time, arrival time, terminal and other information. Based on the received flight information, the airline's ticket sales system (airline ticket system) is called to generate a small order for the planned group.

[0108] Optionally, the system further includes: a price information determination component for determining price information matching the group ticket information based on the air fare publishing system; and a group ticket information publishing component for publishing the group ticket information including the price information to the target object.

[0109] Optionally, the price information determination component can be a price publishing component, which connects to the airline's fare publishing system based on the itinerary number information in the planned group order generated by the order creation component, selects a suitable price, and saves the price information in the planned group order generated by the order creation component.

[0110] The group ticket information publishing component may be an information publishing component that allocates appropriate planned group small orders to airline ticket sales agents (agents) based on the planned group small orders generated by the order creation component and the historical sales data of the airline ticket sales agents.

[0111] In the system, a rule file of the group ticket information to be generated is obtained by a rule file acquisition component 402, wherein the rule file is used to indicate the rules for generating the group ticket information. The rule file is parsed by a rule file parsing component 404 to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to indicate the time range for generating the group ticket information. The order information calculation component 406 determines the number of orders included in the group ticket information to be generated based on the time scheduling information. The group ticket information creation component 408 generates the group ticket information based on the number of orders.

[0112] The embodiment of the present application also provides a device for generating group ticket information. It should be noted that the device for generating group ticket information of this embodiment can be used to execute the method for generating group ticket information of the embodiment of the present invention.

[0113] Figure 5 is a structural diagram of a device for generating group ticket information according to an embodiment of the present application, such as Figure 5 As shown, the group ticket information generating device 500 may include: an acquiring unit 502 , a parsing unit 504 , a determining unit 506 and a generating unit 508 .

[0114] The acquisition unit 502 is used to acquire a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rule for generating the group ticket information.

[0115] The parsing unit 504 is used to parse the rule file to obtain the time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to indicate the time range for generating the group ticket information.

[0116] The determination unit 506 is used to determine the number of orders included in the group ticket information to be generated based on the time scheduling information.

[0117] The generating unit 508 is used to generate group ticket information based on the order quantity.

[0118] Optionally, the generation unit 508 includes: a first generation module, used to generate group ticket total information based on the order quantity; a determination module, used to determine the flight time information of the group ticket information to be generated in the group ticket total information based on the time scheduling information; and a second generation module, used to generate group ticket information based on the flight time information.

[0119] Optionally, the second generation module includes: a determination submodule, which is used to call the flight query system based on the flight time information and the flight itinerary information in the rule file to determine the flight information for the group ticket information to be generated; and a generation submodule, which is used to generate the group ticket information based on the flight information.

[0120] Optionally, after generating group ticket information based on flight information, the device also includes: a first determination unit, used to determine price information matching the group ticket information based on an airline fare publishing system; and a publishing unit, used to publish the group ticket information containing price information to a target object.

[0121] Optionally, the publishing unit includes: a publishing module, which is used to publish the group ticket information including price information to the matching target object based on the historical order data of the target object.

[0122] Optionally, the parsing unit 504 includes: a parsing module, which is used to verify the format of the rule file and convert the verified rule file into a rule object, wherein the rule object at least includes time scheduling information.

[0123] In the device, the rule file of the group ticket information to be generated is obtained by the acquisition unit 502, wherein the rule file is used to indicate the rule for generating the group ticket information. The rule file is parsed by the parsing unit 504 to obtain the time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to indicate the time range for generating the group ticket information. The number of orders included in the group ticket information to be generated is determined by the determination unit 506 based on the time scheduling information. The group ticket information is generated by the generation unit 508 based on the number of orders.

[0124] According to another aspect of an embodiment of the present application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any method for generating group ticket information.

[0125] Specifically, the above storage medium is used to store program instructions for the following functions to implement the following functions:

[0126] Obtain a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; parse the rule file to obtain time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, determine the number of orders included in the group ticket information to be generated; and generate the group ticket information based on the number of orders.

[0127] Optionally, in this embodiment, the above-mentioned storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the above-mentioned contents. More specific examples of the above-mentioned storage medium may include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above-mentioned contents.

[0128] According to another aspect of an embodiment of the present invention, a processor is further provided, the processor being used to run a program, wherein the method for generating group ticket information in an embodiment of the present invention is executed when the program is run.

[0129] In an exemplary embodiment of the present application, a computer program product is also provided, including a computer program, which implements any of the above-mentioned methods for generating group ticket information when executed by a processor.

[0130] Optionally, the computer program may implement the following steps when executed by a processor:

[0131] Obtain a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; parse the rule file to obtain time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, determine the number of orders included in the group ticket information to be generated; and generate the group ticket information based on the number of orders.

[0132] In an exemplary embodiment of the present application, a computer program product is also provided, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and the computer program is configured to execute any of the above-mentioned methods for generating group ticket information when running.

[0133] Optionally, the computer program may implement the following steps when executed by a processor:

[0134] Obtain a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; parse the rule file to obtain time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, determine the number of orders included in the group ticket information to be generated; and generate the group ticket information based on the number of orders.

[0135] In an exemplary embodiment of the present application, a computer program is further provided. The computer program is configured to execute the steps in any of the above method embodiments when running.

[0136] Optionally, the computer program may implement the following steps when executed by a processor:

[0137] Obtain a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; parse the rule file to obtain time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to represent the time range for generating the group ticket information; based on the time scheduling information, determine the number of orders included in the group ticket information to be generated; and generate the group ticket information based on the number of orders.

[0138] According to an embodiment of the present application, an electronic device is provided, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned methods for generating group ticket information.

[0139] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0140] Figure 6600 is a schematic block diagram of an electronic device according to an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0141] like Figure 6 As shown, the device 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0142] A number of components in the device 600 are connected to the I / O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0143] The computing unit 601 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 601 performs the various methods and processes described above, such as the method for generating group ticket information. For example, in some embodiments, the method for generating group ticket information may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 600 via the ROM 602 and / or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the method for generating group ticket information described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method for generating group ticket information in any other appropriate manner (e.g., by means of firmware).

[0144] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0145] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0146] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0147] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0148] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0149] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0150] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0151] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0152] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0153] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0154] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0155] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0156] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for generating group ticket information, characterized in that: include: Obtain a rule file for the group ticket information to be generated, wherein the rule file is used to represent the rules for generating the group ticket information; Parsing the rule file to obtain time scheduling information for the group ticket information to be generated, wherein the time scheduling information is used to indicate a time range for generating the group ticket information; Based on the time scheduling information, determine the number of orders included in the group ticket information to be generated; Based on the order quantity, the group ticket information is generated.

2. The method according to claim 1, characterized in that Based on the order quantity, the group ticket information is generated, including: Based on the order quantity, generate group ticket total information; Based on the time scheduling information, determine the flight time information of the group ticket information to be generated in the group ticket total information; The group ticket information is generated based on the flight time information.

3. The method according to claim 2, characterized in that Based on the flight time information, the group ticket information is generated, including: Based on the flight time information and the flight itinerary information in the rule file, calling a flight query system to determine the flight information of the group ticket information to be generated; The group ticket information is generated based on the flight information.

4. The method according to claim 3, characterized in that After generating the group ticket information based on the flight information, the method further includes: Based on the air fare publishing system, determine the price information that matches the group ticket information; The group ticket information including the price information is published to the target object.

5. The method according to claim 4, characterized in that Publishing the group ticket information including the price information to the target object includes: Based on the historical order data of the target object, the group ticket information including the price information is published to the matching target object.

6. The method according to claim 1, characterized in that Parse the rule file to obtain the time scheduling information of the group ticket information to be generated, including: The format of the rule file is verified, and the rule file that passes the verification is converted into the rule object, wherein the rule object at least includes the time scheduling information.

7. A group ticket information publishing system, characterized in that: include: A rule file acquisition component is used to acquire a rule file for group ticket information to be generated, wherein the rule file is used to represent the rules for generating group ticket information; A rule file parsing component, used to parse the rule file to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to indicate a time range for generating the group ticket information; An order information calculation component, used to determine the number of orders included in the group ticket information to be generated based on the time scheduling information; The group ticket information creation component is used to generate the group ticket information based on the order quantity.

8. The system according to claim 7, characterized in that The system further comprises: A price information determination component, used to determine price information matching the group ticket information based on an air fare publishing system; The group ticket information publishing component is used to publish the group ticket information including the price information to the target object.

9. A device for generating group ticket information, characterized in that: include: An acquisition unit, used to acquire a rule file for group ticket information to be generated, wherein the rule file is used to represent a rule for generating the group ticket information; A parsing unit, used to parse the rule file to obtain time scheduling information of the group ticket information to be generated, wherein the time scheduling information is used to indicate a time range for generating the group ticket information; A determination unit, configured to determine the number of orders included in the group ticket information to be generated based on the time scheduling information; A generating unit is used to generate the group ticket information based on the order quantity.

10. An electronic device, characterized in that: The method comprises one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 6.

Images