Structured display method, system, storage medium and electronic equipment for retirement and modification rules

Abstract

The application provides a method and system for structurally displaying a refund and change rule, a storage medium and an electronic device, and relates to the technical field of data processing. The refund and change rule is a refund and change rule of an air freight rate. The method comprises the following steps: receiving a request message, wherein the request message comprises freight rate information, the freight rate information is used for matching a corresponding refund and change rule; matching a corresponding data table set from a database according to the freight rate information in the request message, wherein the data table set stores the refund and change rule, and the data table set comprises at least two data tables; when each data table in the data table set has completed structural processing, assembling a response message to structurally display the data table set storing the refund and change rule; and when there is a data table that has not completed structural processing in the data table set, assembling an error message to indicate that there is no structural content of the refund and change rule. The scheme can structurally display the refund and change rule to improve the efficiency of air freight.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a structured display method, system, storage medium, and electronic device for refund and modification rules. Background Technology

[0002] Air transport, as a vital part of transportation, occupies a significant market share due to its speed and efficiency. It is one of the most important core elements of shipping freight rates and is crucial for maintaining shipping stability.

[0003] Fare refund and change policies are a crucial component of passenger ticketing services. The diversity of these policies is a significant factor contributing to the flexibility and variability of international airfares. In the current international fare landscape, to support automated fare calculations, most airlines use a unified data format for publishing, receiving, and processing fare data. Fare refund and change policies also follow this format. Within this format, fare refund and change policies are divided into two types: Category 16 and Category 31 / 33. Category 31 / 33 is highly formatted data, optimized for computer processing, and typically not presented to users. Category 16, on the other hand, contains a small amount of simply formatted refund and change policy data, accompanied by text describing the policies in natural English.

[0004] These refund and change policy texts, composed of natural English language, are difficult to translate accurately into local languages, such as Chinese. This is because these texts are less natural language and more highly simplified or technically terminological segments of airline ticketing, making direct machine translation prone to inaccuracies. Furthermore, as natural language, they lack standardized formats, resulting in variations in word choice across airlines and inconsistent phrasing and paragraphing. Consequently, current refund and change policies are difficult to present to passengers or ticketing staff, potentially leading to decreased operational efficiency. Therefore, a structured approach to displaying refund and change policies is needed to improve operational efficiency. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a structured display method, system, storage medium, and electronic device for cancellation and modification rules, which can display cancellation and modification rules in a structured manner to improve shipping efficiency.

[0006] Firstly, this application provides a structured display method for refund and change rules, wherein the refund and change rules are for airfares. The method includes: receiving a request message, the request message including fare information used to match the corresponding refund and change rules; matching a corresponding set of data tables from a database based on the fare information in the request message, the set of data tables storing the refund and change rules, the set of data tables including at least two data tables; when all data tables in the set have completed structured processing, assembling a response message to display the set of data tables storing the refund and change rules in a structured manner; when there are data tables in the set that have not completed structured processing, assembling an error message to indicate that there is currently no structured content for the refund and change rules.

[0007] The solution provided in this application allows users to provide query content related to fare information in a request message, which automatically and accurately finds and matches the corresponding refund and change rules. Because the language in the refund and change rules is highly reusable, the backend does not directly store the text information. Part of the refund and change rules are stored in a fixed formatted encoding in table R3C016, and part are stored in free text in table R3T996. In addition, there is some auxiliary data, such as table R3T994 storing travel / ticketing / booking date restrictions, table R3C014 storing travel date restrictions, table R3C015 storing ticketing and booking date restrictions, and table R3C019 storing discount information, etc. Therefore, this solution matches the corresponding set of data tables from the database based on the fare information in the request message. The refund and change rule text is generally assembled from multiple R3C016 tables. Since the database only stores various tables such as R3C016, the refund and change rule text is dynamically generated when the user makes a request. Therefore, it is not suitable to directly perform structured processing on the refund and change rule text; this solution uses R3C016 as the starting point for structured processing. Except for its reference R3T996, R3C016 contains only structured information, which can be saved for later assembly. R3T996, however, requires confirmation of whether structured processing has been completed. For each data table in the data set, such as R3C016 and R3T996, if all data tables have completed structured processing, a response message is assembled from these structured data tables and returned to the user to provide a structured display of the data set containing refund / modification rules. If any data table in the data set has not completed structured processing, an error message is assembled to indicate that there is currently no structured content with refund / modification rules. In summary, this solution can provide a structured display of refund / modification rules, facilitating user development, translation, content reorganization, and ultimately improving shipping efficiency.

[0008] Secondly, this application also provides a structured display system for refund and modification rules, the system comprising: an entry service module, a refund and modification rule query module, and a processing module; wherein,

[0009] The entry service module is used to receive request messages, which include fare information and are used to match the corresponding refund and modification rules.

[0010] The refund and modification rule query module is used to match the corresponding data table set from the database based on the fare information in the request message. The data table set stores the refund and modification rules and includes at least two data tables.

[0011] The processing module is used to assemble a response message when all data tables in the data table set have completed the structured processing, so as to display the data table set storing the refund and modification rules in a structured manner; when there are data tables in the data table set that have not completed the structured processing, it assembles an error message, which is used to indicate that there is currently no structured content for the refund and modification rules.

[0012] This system allows for a structured presentation of refund and cancellation rules, making it easier for users to develop solutions, translate them, reorganize content, and ultimately improve shipping efficiency.

[0013] Thirdly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a structured display method for refund and modification rules.

[0014] Fourthly, this application also provides an electronic device for running a program, and a structured display method for executing refund and modification rules during program execution. Attached Figure Description

[0015] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0016] Figure 1 A flowchart illustrating a structured display method for refund and modification rules provided in this application embodiment;

[0017] Figure 2 A flowchart illustrating another structured representation method for refund and modification rules provided in this application embodiment;

[0018] Figure 3 An architecture diagram of a structured display system for refund and modification rules provided in this application embodiment;

[0019] Figure 4 A schematic diagram of a structured display system for refund and modification rules provided in an embodiment of this application;

[0020] Figure 5 A schematic diagram of another structured display system for refund and modification rules provided in this application embodiment;

[0021] Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0023] To enable those skilled in the art to better understand the present application, the application scenarios of the present application are described below.

[0024] Fare refund and change policies are an important part of civil aviation ticketing services. The diversity of these policies is a key factor contributing to the flexibility of international airfares. For example, for the same itinerary and flight, the price of a ticket that can be changed and one that cannot will differ significantly. Furthermore, fare refund and change policies are not limited to simple scenarios like refunds and changes are possible. Adding factors such as booking / ticketing / travel dates, departure / departure dates, cabin class, and the availability of child discounts makes the policies quite complex.

[0025] The display of fare refund and change policies is maintained throughout the long process of ticket purchase, travel, and ticket refund / change. At multiple points in time, passengers, ticket sales staff, and the automatic fare calculation system all need to view the fare refund and change policies.

[0026] In the current international airfare market, to support automated fare calculation, most airlines use a unified data format for publishing, receiving, and processing fare data in their fare calculation systems. Fare refund and change rules also follow this format. Within this format, fare refund and change rules are divided into two types: Category 16 and Category 31 / 33. Category 31 / 33 is highly formatted data, designed for computer processing, and is typically not presented to users. Category 16, on the other hand, contains a small amount of simply formatted refund and change rule data, accompanied by a text description in natural English.

[0027] These refund and change policy texts, composed of natural English language, are difficult to translate accurately into local languages ​​such as Chinese. This is because these texts are less natural language and more highly simplified or technically terminological fragments of airline ticketing. Direct machine translation easily fails to convey the intended meaning. Furthermore, as they are natural language, there are no fixed standards, so different airlines use different terms, and there are no universal rules for phrasing and paragraphing. It is also quite difficult for a ticketing system to break them down, format them, and then recombine them for display.

[0028] To enable users to better utilize fare refund and change rules data, a solution is needed to structure and display Category 16 content, and provide it to users through an interface to facilitate development on this basis, making it easier to translate and reorganize content.

[0029] To address the above issues, embodiments of this application provide a structured display method, system, storage medium, and electronic device for refund and modification rules. This structured display facilitates user development, translation, and content reorganization, thereby improving shipping efficiency.

[0030] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0031] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0032] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0033] This application provides an embodiment, which will be described in detail below with reference to the accompanying drawings.

[0034] See Figure 1 The figure is a flowchart of a structured display method for refund and modification rules provided in an embodiment of this application.

[0035] This method is used to present the refund and change rules for air freight in a structured way, that is, to present the refund and change rules using a fixed logical expression. The method includes the following steps:

[0036] S101: Receive a request message, which includes fare information. The fare information is used to match the corresponding refund and change rules.

[0037] The fare information may include the airline's two-letter code for the fare's origin, destination, tariff code, rule number, fare basis code (FBC), one-way / round-trip attribute, route map number, footnote number, fare type, travel date, ticket date, seller information, passenger type code, data source, and one or more other optional information. The optional information is used to assist in fare queries and make the matched refund and change rules more accurate.

[0038] S102: Based on the fare information in the request message, match the corresponding data table set from the database. The data table set stores the refund and modification rules and includes at least two data tables.

[0039] Because the language used in fare refund and change rules is highly reusable, the backend does not directly store text information. Part of the refund and change rules are stored in table R3C016 with a fixed formatted encoding, and part are stored in table R3T996 as free text. In addition, there is some auxiliary data, such as table R3T994 storing travel / ticketing / booking date restrictions, table R3C014 storing travel date restrictions, table R3C015 storing ticketing and booking date restrictions, and table R3C019 storing discount information, etc.

[0040] A typical refund / modification rule text is assembled from multiple R3C016 tables. Except for the R3T996 table it references, all other R3C016 tables contain structured information. It needs to be determined whether the R3T996 table referenced by the R3C016 table has undergone structured processing.

[0041] S103: When all data tables in the data table set have completed the structured processing, a response message is assembled. When there are data tables in the data table set that have not completed the structured processing, an error message is assembled.

[0042] The response message is a response to the request message and is used to provide a structured display of the data table set containing the refund and modification rules.

[0043] Error messages are used to indicate that there are currently no refund or modification rules for structured content.

[0044] Since the database typically only stores tables such as R3C016, and the refund / modification rule text is dynamically generated upon user request, it is not suitable to directly perform structured processing on the refund / modification rule text. In this embodiment, structured processing is performed starting from R3C016. Except for its referenced R3T996, all other information in R3C016 is structured information and only needs to be saved for later assembly. R3T996, however, needs to determine whether structured processing has been completed. For each data table included in the data table set, such as R3C016 and R3T996, once all data tables have completed structured processing, the structured data tables are assembled into a response message and returned to the user.

[0045] When there are data tables in the data table set that have not completed the structured processing, that is, when there are R3T996 that have not completed the formatting process, an error message is assembled.

[0046] In summary, the method provided in this application embodiment can present refund and change rules in a structured manner, making it easier for users to develop on this basis, facilitating translation, content reorganization, and ultimately improving shipping efficiency.

[0047] The following section will explain the specific implementation method.

[0048] The database in this embodiment includes at least two types of data tables: a first type of data table and a second type of data table. The first type of data table references the second type of data table, and the first type of data table has undergone structured processing. For example, the first type of data table could be table R3C016, which, except for its referenced table R3T996, contains all structured information. Alternatively, the first type of data table could be table R3C019, which provides discount information, and its content is also entirely structured information.

[0049] See Figure 2 The figure is a flowchart of another structured display method for refund and modification rules provided in an embodiment of this application.

[0050] The method provided in this application includes the following steps:

[0051] S201: Receive a request message, which includes freight rate information.

[0052] The fare information is used to match the corresponding refund and change rules.

[0053] S202: Determine the corresponding Category I data tables for freight rate information.

[0054] The first type of data tables in this application embodiment are tables R3C016 and R3C019. Except for the referenced table R3T996, table R3C016 contains structured information that does not require manual processing; it simply needs to be saved for later assembly. Table R3C019 provides discount information, and its content is also entirely structured information.

[0055] S203: Query the second-class data tables referenced by each first-class data table from the database, so that the first-class data tables and the second-class data tables form a data table set.

[0056] First, try querying the database for an existing table, R3C016. If it exists, then further query the database for the table R3T996 referenced by R3C016.

[0057] Each first-class data table may reference one or more second-class data tables. The specific number of references is not limited in the embodiments of this application.

[0058] Each R3C016 table can reference one or more R3T996 tables.

[0059] S204: Determine whether all data tables in the data table set have been structured.

[0060] If yes, proceed to S205; otherwise, proceed to S206.

[0061] In some embodiments, if at least one second-type data table in the data table set has not undergone structured processing, it is determined that the data table set contains data tables that have not undergone structured processing. That is, if table R3T996 has not undergone structured processing, it is determined that the data table set contains data tables that have not undergone structured processing.

[0062] S205: Assemble a response message to provide a structured display of the data table set containing refund and modification rules.

[0063] S206: Assemble an error message to indicate that there are currently no refund or modification rules.

[0064] S207: Perform manual structuring on the second type of data tables that have not yet undergone structuring.

[0065] That is, the processing personnel perform structuring on the unstructured R3T996 table.

[0066] S208: Verify the authenticity of the second type of data table after artificial structuring.

[0067] In some embodiments, authenticity verification is used to verify whether the data in the second type of data table after manual structuring is authentic and reliable, and whether it has been tampered with.

[0068] S209: When the verification passes, the second type of data table, which has been manually structured, will be stored in the database.

[0069] The second type of data, after undergoing structured processing, is marked as structured in the database. It can then be displayed in a structured manner the next time it is referenced by the R3C016 table. In other words, although the structured display failed this time, after one iteration, the next structured display of the R3T996 table will succeed. The user only needs to send the request message again.

[0070] In one possible implementation, when a second type of data table referenced by a first type of data table is missing in the database, the method further includes the following steps:

[0071] Based on at least one of the freight rate information or the specified time range in the request message, obtain the missing second-type data table; perform manual structuring on the obtained missing second-type data table; verify the authenticity of the manually structuring missing second-type data table; when the verification passes, store the manually structuring missing second-type data table in the database.

[0072] In other words, if the R3T996 table, which is referenced by the R3C016 table, is not stored in the database, the missing R3T996 table is retrieved through a query. This R3T996 table is then manually structured. Once its authenticity is verified, it is stored in the database. The next time the R3C016 table references it, a structured display can be performed. In other words, although the structured display fails this time, after one iteration, the structured display of the R3T996 table will succeed the next time. The user only needs to send a request message again.

[0073] In one possible implementation, the method further includes the following steps:

[0074] The first type of data table stored in the database is updated according to a preset cycle; if the second type of data table referenced by the newly stored first type of data table is found to be missing in the database, the missing second type of data table is retrieved; the retrieved missing second type of data table is manually structured; the authenticity of the manually structured missing second type of data table is verified; when the verification is successful, the manually structured missing second type of data table is stored in the database.

[0075] By automatically updating the database according to a preset cycle, the number of first-type data tables not stored in the database and the number of second-type data tables that have not undergone structured processing can be reduced. This increases the success rate of structured processing of refund and modification rules, reduces the number of required request messages, and thus improves shipping efficiency.

[0076] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0077] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0078] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0079] The following explains how the structured display system for refund and modification rules is implemented.

[0080] See Figure 3 This figure is an architecture diagram of a structured display system for refund and modification rules provided in an embodiment of this application.

[0081] The structured display system 10 for the refund and modification rules shown in the diagram mainly includes an external interface layer 11, a business processing layer 21, and a data access object (DAO) layer 31.

[0082] Among them, the external interface layer 11 includes entry service, exit service and refund / modification rule query service;

[0083] Business Processing Layer 21: Includes refund and change rule processing service, data query service, task file receiving service, task file sending service, and polling new fare refund and change rule data service.

[0084] It can also be used in conjunction with external systems: Manual splitting system for refund and modification rules 20.

[0085] The following section will first describe the external interface layer 11.

[0086] The entry service of the external interface layer 11 provides a request interface: StructuredTranslateRuleText_RQ.

[0087] The entry service of the external interface layer 11 provides a response interface: StructuredTranslateRuleText_RS.

[0088] The system requires that the request for the entry service include information related to fares, and it can automatically and accurately find and match the corresponding refund and change rules.

[0089] Please refer to the table below for the specific information required in the request.

[0090] Table 1: Information Required for Entry Service Requests

[0091] Name Meaning Carrier Two-character code of the airline to which the change rule belongs Origin Origin of the rate Destination Destination of the rate RuleTariff Tariff number of the rate Rule Rule number of the rate Fbc Fare basis code of the rate, fare basis, which can be understood as the name of the rate Owrt One-way or round-trip attribute of the rate Routing Routing number of the rate Ftnt Footnote number of the rate FareType Type of the rate TravelDate Travel date of the rate TicketingDate Ticketing date of the rate Seller Seller information of the rate PTC Passenger type code of the rate Source Data source of the rate Other non-mandatory information Auxiliary query rate, make the matched change rule result more accurate

[0092] The field structure of the export service response is shown in the table below:

[0093] Table 2: Field Structure Table of Export Structure Response

[0094] Cat16 Fixed field, represents chapter 16 of the rate rule Refund / Change / Noshow Refund / Change / Noshow classification ChargeApplication Refund application scenario, i.e. before departure / after departure TimingApplication Timing requirement of the refund Permission Whether to allow refund Rbd Cabin to which the refund clause applies Location Geographical information (origin-destination) to which the refund clause applies Io Outbound-return condition to which the refund clause applies FareBasis Fare basis to which the refund clause applies FareType Fare type to which the refund clause applies TravelDate Travel origin date to which the refund clause applies TicketingDate Ticketing date to which the refund clause applies ReservationDate Reservation date to which the refund clause applies ChargePortion Segment condition to which the refund clause applies Charges Handling fee to which the refund clause applies Administration Administration fee to which the refund clause applies Discount Handling fee discount to which the refund clause applies OtherInfo Other unstructured information

[0095] Please refer to the relevant instructions for the entry service. Users only need to provide fare information, and the system will automatically match the refund and change rules. The refund and change rule query service provides a function to query refund and change rules, accurately matching the fare refund and change rules from the fare database based on the fare information.

[0096] Because the language used in fare refund and change rules is highly reusable, the backend does not directly store the text information. Part of the refund and change rules are stored in table R3C016 with a fixed formatted encoding, and part are stored in table R3T996 as free text. In addition, there is some auxiliary data, such as table R3T994 storing travel / ticketing / booking date restrictions, table R3C014 storing travel date restrictions, table R3C015 storing ticketing and booking date restrictions, and table R3C019 storing discount information, etc.

[0097] The refund and change rule query service will automatically retrieve the original English text of the refund and change rules involved in the request and the corresponding R3C016 number, and pass on the subsequent refund and change rule processing service.

[0098] The information provided to the business processing layer 21 by the refund and modification rule query service includes form number R3C016 and form number R3C019.

[0099] A refund / modification rule text is assembled from multiple R3C016 tables. The international freight rate calculation engine's database only stores various tables such as R3C016, while the refund / modification rule text is dynamically generated upon user request. Therefore, it is not suitable to directly perform structured processing on the refund / modification rule text. Thus, this system uses R3C016 as the starting point for structured processing.

[0100] Apart from R3T996, which it references, R3C016 is entirely structured information and requires no manual processing; it simply needs to be saved for later assembly. Only the R3C016 table number is being transmitted here.

[0101] The R3C019 form provides discount information, and its content is all structured information. Here, the R3C019 form number is transmitted.

[0102] The business processing layer 21 is responsible for processing the content passed in from the external interface layer 11, structuring the content and / or translating the content and passing it back to the external interface layer 11.

[0103] The business processing layer 21 generates task files from unstructured content and sends them to the manual refund / modification rule splitting system 20 for structured splitting. The business processing layer 21 also stores the structured data in the database for future retrieval. Since a purely request-driven approach results in a low probability of hitting content in the database and always suffers from delays in manual processing, the business processing layer 21 also has a periodic polling mechanism to autonomously detect newly added refund / modification rule content in the fare data and send it to manual processing as early as possible.

[0104] The following provides a detailed description of each service in the business processing layer 21.

[0105] The following section explains the refund and modification policy.

[0106] For requests that require structured processing, first attempt to query the existing R3C016 table in the database. If it exists, then further query the database to see if the R3T996 table referenced by that table has completed the structured processing.

[0107] If R3T996 has completed the structured processing, it queries the database for auxiliary tables such as R3T994, R3C014, R3C015, and R3C019 (if not found, it calls the data query service to query), and assembles the response message to pass it to the upper layer.

[0108] If R3T996 fails to complete the structured processing, it will assemble an error message (informing the user that there is currently no structured content) and pass it to the next layer.

[0109] If R3T996 is not found, the data query service is invoked to search for R3T996. Once found, the task file sending service is notified to generate a task file for R3T996 and send it to the manual splitting system for refund and modification rules for processing. An error message is then assembled (informing the user that there is currently no structured content) and sent to the next layer of traditional processing.

[0110] The following describes the data query service.

[0111] Unlike the refund and cancellation policy query service, this data query service does not contain complex business logic; it only retrieves and returns results from raw data. The data query service includes the following two types of queries:

[0112] 1. Query table records by table name and table number. For example, query the record with table number 12345678 in table R3C016.

[0113] 2. Query newly added tables in the international freight rate calculation system database based on a specified time range. For example, query the list of newly added table numbers for R3C016 within a specified time period.

[0114] The following describes the task file receiving service.

[0115] Receives a structured file from the manual splitting system for refund and modification rules. Calls the data query service to verify the authenticity of R3T996 in the file. Stores it in the corresponding R3T996 field in the system library and marks the R3T996 as structured.

[0116] The following describes the task file sending service.

[0117] The task file sending service receives notifications from the refund and change rule processing service and the polling new fare refund and change rule data service, generates an R3T996 task file, and sends it to the refund and change rule manual splitting system for processing.

[0118] The following describes the data service for polling new fare refund and change rules.

[0119] The system polls the new fare refund and change rule data service to automatically and periodically call the data query service to check if any new R3C016 tables have been added to the international fare calculation system database. If detected, it retrieves a list of newly added R3C016 table numbers and adds these tables to the system database. It then checks whether the R3T996 tables they reference are already in the system database (new R3C016 tables may reuse older R3T996 tables). If not, it calls the data query service to search for R3T996. Once found, it notifies the task file sending service to generate a task file for that R3T996 and send it to the manual refund and change rule splitting system for processing.

[0120] The following describes DAO layer 31.

[0121] DAO layer 31 is the database access object layer. The database is EDB, also known as Exchange, used to persistently store data such as R3C016. DAO layer 31 uses Redis as a cache. When the upper layer queries data, it first queries Redis; if the data is not found, it then queries EDB. Simultaneously, EDB data is periodically synchronized to Redis via the syndbCache (syndb cache) service.

[0122] The `syncdb` command is a simple way to synchronize data to a database. The `syncdb` command checks the database and creates the table if it doesn't exist. It's important to note that the `syncdb` command does not synchronize data modifications or deletions to the database; if you modify or delete data and then try to commit it to the database, `syncdb` will not perform any processing.

[0123] The manual splitting system 20 for refund and modification rules is an external system used to receive task files sent by system 10 in real time, and assign them to processing personnel for structured splitting. After structuring, a file is generated according to the agreed format and sent back to system 10.

[0124] To enable those skilled in the art to better understand the technical solution of this application, the following describes the process by which the above system implements the structured breakdown of international freight rate refund and change rules, using a scenario as an example.

[0125] Scenario 1: R3C016 already exists in the database, and the referenced R3T996 have already undergone structured processing.

[0126] The user sends a StructuredTranslateRuleText_RQ to system 10, with the target language being Simplified Chinese, declaring that structured data is required.

[0127] Since the entry service of the external interface layer 11 provides a request interface, the external interface layer 11 receives the request, calls the refund and modification rule query service to obtain multiple R3C016, and passes this information to the business processing layer 21.

[0128] The database includes these R3C016s, and the R3T996s they reference have also been structured and stored in the database.

[0129] The business processing layer 21 assembles the structured content into a response message and passes it to the external interface layer 11.

[0130] The external interface layer 11 encapsulates the response message into StructuredTranslateRuleText_RS and returns it to the user through the response interface provided by the exit service of the external interface layer 11.

[0131] Scenario 2: R3C016 exists but does not exist in the database.

[0132] The user sends a StructuredTranslateRuleText_RQ to this system, with Simplified Chinese as the target language.

[0133] The external interface layer 11 receives the request message, calls the refund and modification rule query service to obtain the Rule Text and multiple R3C016, and passes this information to the business processing layer 21.

[0134] The business processing layer 21 discovered that one of the R3C016 entries was not in the database.

[0135] The business processing layer 21 calls the data query service to query the R3C016 and stores the queried R3C016 into the database.

[0136] The business processing layer 21 discovered that the R3T996 referenced by R3C016 was not in the database.

[0137] The business processing layer 21 calls the data query service to query the R3T996, and stores the queried R3T996 into the database and marks it as unstructured.

[0138] The business processing layer 21 notifies the task file sending service to send the R3T996 generated task file to the manual splitting system for refund and modification rules 20 for processing.

[0139] The business processing layer 21 assembles an error message (prompting the user that there is no structured content) and passes it to the external interface layer 11.

[0140] The external interface layer encapsulates the 11 response message into a StructuredTranslateRuleText_RS and returns it to the user.

[0141] Based on the architecture of the structured display system for refund and modification rules provided above, this application embodiment also provides a structured display system for refund and modification rules, which will be described in detail below with reference to the accompanying drawings.

[0142] See Figure 4 The figure is a schematic diagram of a structured display system for refund and modification rules provided in an embodiment of this application.

[0143] The structured display system for refund and modification rules provided in this application includes an entry service module 401, a refund and modification rule query module 402, and a processing module 403.

[0144] The entry service module 401 is used to receive request messages, which include fare information. This fare information is used to match the corresponding refund and change rules. The entry service module 401 is used to implement... Figure 3 The entry service in the middle.

[0145] The refund / modification rule query module 402 is used to match the corresponding data table set from the database based on the fare information in the request message. The data table set stores refund / modification rules and includes at least two data tables. The refund / modification rule query module 402 is used to implement... Figure 3 The service provides access to the refund and modification rules.

[0146] Processing module 403 is used to assemble a response message when all data tables in the data table set have completed structured processing, to provide a structured display of the data table set containing refund / modification rules; when there are data tables in the data table set that have not completed structured processing, it assembles an error message to indicate that there is currently no structured content with refund / modification rules. Processing module 403 is used to implement... Figure 3 Services in the application processing layer.

[0147] The implementation method of this system is explained in detail below.

[0148] See Figure 5 The figure is a schematic diagram of a structured display system for refund and modification rules provided in an embodiment of this application.

[0149] In some embodiments, the structured display system for the refund and modification rules further includes: a DAO module 404 for implementing the functions of the DAO layer 31, and an export service module 405 for implementing export services.

[0150] Furthermore, in some embodiments, the processing module 403 specifically includes: a refund and change rule processing submodule 4031 for implementing refund and change rule processing service, a data query submodule 4032 for implementing data query service, a task file receiving module 4033 for implementing task file receiving service, a polling submodule 4034 for implementing polling new fare refund and change rule data service, and a task file sending submodule 4035 for implementing task file sending service. The functions of the above submodules can be found in the descriptions in the above embodiments and will not be repeated here.

[0151] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the structured display method for the cancellation and modification rules described above.

[0152] In the context of this disclosure, a computer-readable storage medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0153] This application also provides an electronic device, which will be described in detail below with reference to the accompanying drawings.

[0154] See Figure 6 This figure is a schematic diagram of an electronic device provided in an embodiment of this application.

[0155] The illustrated electronic device 600 may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0156] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 606 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0157] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, etc.; storage devices 606 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0158] When the program stored on the electronic device is run, it is used to implement the structured display method of refund and modification rules described in the above embodiments. This method can display the refund and modification rules in a structured manner, making it easier for users to develop on this basis, making it easier to translate, easier to reorganize content, and thus easier to improve shipping efficiency.

[0159] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0160] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on its differences from other embodiments. The device embodiments described above are merely illustrative, and the units and modules described as separate components may or may not be physically separate. Furthermore, some or all of the units and modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0161] The above description is only a specific embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A structured display method for refund and modification rules, characterized in that, The aforementioned refund and change rules are the refund and change rules for air freight fares, and the method includes: The system receives a request message, which includes fare information used to match corresponding refund and change rules. The fare information includes at least one of the following: the airline code to which the refund and change rule belongs, the origin of the fare, the destination of the fare, the customs duty code of the fare, the rule number of the fare, the basic code of the fare, the one-way / round-trip attribute of the fare, the route map number of the fare, the footnote number of the fare, the type of fare, the travel date of the fare, the ticketing date of the fare, the seller information of the fare, the passenger type code of the fare, the data source of the fare, and other non-essential information used to assist in querying fares. Based on the fare information in the request message, a corresponding set of data tables is matched from the database, and the set of data tables stores the refund and modification rules; When all data tables in the data table set have completed the structured processing, a response message is assembled to display the data table set storing the refund / modification rules in a structured manner; when there are data tables in the data table set that have not completed the structured processing, an error message is assembled to indicate that there is currently no structured content for the refund / modification rules. The database includes at least two types of data tables: a first type of data table and a second type of data table; the first type of data table references the second type of data table, and the first type of data table has undergone structured processing; the step of matching the corresponding set of data tables from the database based on the fare information in the request message specifically includes: Determine each of the first type of data tables corresponding to the freight rate information; The database is queried to find the second type of data table referenced by each of the first type of data tables, so that each of the first type of data tables and each of the second type of data tables forms the data table set.

2. The method according to claim 1, characterized in that, When there are data tables in the data table set that have not undergone complete structured processing, an error message is assembled, specifically including: When at least one of the second type of data tables in the data table set has not completed the structured processing, it is determined that there is a data table in the data table set that has not completed the structured processing, and the error message is assembled.

3. The method according to claim 2, characterized in that, After the error message is generated through assembly, the method further includes: Manual structuring is performed on the second type of data tables that have not yet undergone structuring.

4. The method according to claim 3, characterized in that, After manually structuring the second type of data table that has not undergone complete structuring, the method further includes: The authenticity of the second type of data table after the artificial structuring process is verified; When the verification is successful, the second type of data table after manual structuring is stored in the database.

5. The method according to claim 1, characterized in that, When a second type of data table referenced by the first type of data table is missing in the database, the method further includes: Based on at least one of the freight rate information or the specified time range in the request message, obtain the missing second type of data table; The missing second type of data table obtained is manually structured; Verify the authenticity of the missing second-type data table after artificial structuring; When the verification is successful, the missing second type of data table, after being manually structured, is stored in the database.

6. The method according to claim 1, characterized in that, The method further includes: The first type of data table stored in the database is updated according to a preset period; If a newly stored first-class data table is found to be missing in the database, the missing second-class data table is retrieved. The missing second type of data table obtained is manually structured; Verify the authenticity of the missing second-type data table after artificial structuring; When the verification is successful, the missing second type of data table, after being manually structured, is stored in the database.

7. A structured display system for refund and modification rules, characterized in that, The system includes: an entry service module, a refund / modification rule query module, and a processing module; wherein... The entry service module is used to receive request messages, which include fare information. The fare information is used to match the corresponding refund and change rules. The fare information includes at least one of the following: the two-letter code of the airline to which the refund and change rule belongs, the origin of the fare, the destination of the fare, the customs duty code of the fare, the rule number of the fare, the basic code of the fare, the one-way round-trip attribute of the fare, the route map number of the fare, the footnote number of the fare, the type of fare, the travel date of the fare, the ticketing date of the fare, the seller information of the fare, the passenger type code of the fare, the data source of the fare, and other non-essential information. The non-essential information is used to assist in querying fares. The refund and modification rule query module is used to match the corresponding data table set from the database based on the fare information in the request message, and the data table set stores the refund and modification rules; The processing module is used to assemble a response message when all data tables in the data table set have completed the structured processing, so as to display the data table set storing the refund and modification rules in a structured manner; when there are data tables in the data table set that have not completed the structured processing, it assembles an error message, which is used to indicate that there is currently no structured content for the refund and modification rules. The database includes at least two types of data tables: a first type of data table and a second type of data table; the first type of data table references the second type of data table, and the first type of data table has been structured; the refund and modification rule query module is used to determine each of the first type of data tables corresponding to the fare information; and to query the second type of data tables referenced by each of the first type of data tables from the database, so that each of the first type of data tables and each of the second type of data tables forms the data table set.

8. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the structured presentation method of the refund and modification rules as described in any one of claims 1 to 6.

9. An electronic device, characterized in that, The electronic device is used to run a program, wherein the program executes the structured display method of the refund and modification rules as described in any one of claims 1 to 6.

Images