Hotel static information adaptive updating method, system, device and storage medium

Abstract

The present disclosure relates to the technical field of information management, and discloses a hotel static information adaptive updating method, system, device and storage medium. The method comprises: obtaining hotel static information original data from multiple suppliers; analyzing the original data, establishing a hotel information multi-dimensional unified data standard template and a mapping relationship between hotel information heterogeneous data formats and the unified data standard; according to the data standard template and the mapping relationship, performing standardized conversion processing on the original data, and persistently storing the hotel static information standard data formed after conversion into a local database; periodically updating, real-time updating, and data monitoring and error correction of the hotel static information standard data stored in the local database. The present disclosure realizes convenient, fast, accurate and economical maintenance and updating of hotel industry static information.

Description

Technical Field

[0001] This disclosure relates to the field of information management technology, specifically to a method, system, device, and storage medium for adaptive updating of hotel static information. Background Technology

[0002] The hotel distribution industry has a diverse range of suppliers, including hotel groups (OTAs, Online Travel Agencies), large wholesalers, and global distribution system (GDS) providers. Static hotel information is crucial for multi-supplier collaborations. Hotel distribution aggregation platforms need to accurately grasp this information to better promote and sell hotel products to guests, while also providing accurate and timely service information. Because the formats and standards of the static hotel information returned by different suppliers vary, aggregation platforms need to perform necessary standardization and integration operations to better provide hotel resources to partner distributors.

[0003] Due to varying sources, hotel-related information provided by suppliers may differ in data format and specifications. Therefore, effective data integration is necessary. This involves organizing, classifying, and formatting the data according to unified specifications and standards to improve accuracy, consistency, and usability. Data maintenance, management, and updates are also crucial for unified management and presentation. Common categories of static hotel information include: Basic hotel information (hotel name, unique identifier ID, star rating, brand name, opening date, and most recent renovation date); Geographical location information (detailed address, city, province, country, postal code, latitude and longitude coordinates); Contact information (telephone number, email address, official website); and Facilities and services information (room amenities such as air conditioning, TV, and free broadband), dining facilities, leisure facilities, and business facilities). For example, some suppliers use the Gaode coordinate system, while others use Google or Baidu coordinate systems. These different coordinate systems can lead to discrepancies in hotel location during static information updates, impacting customer experience. Therefore, a cost-effective and efficient real-time static information update mechanism is needed to address this issue.

[0004] In summary, how to provide an adaptive update mechanism for hotel static information based on multi-dimensional perception to accurately, efficiently, and economically support the updating and maintenance of hotel static information has become an urgent problem to be solved. Summary of the Invention

[0005] This disclosure provides a method, system, device, and storage medium for adaptive updating of hotel static information to solve the problems in the prior art.

[0006] According to one aspect of this disclosure, a method for adaptively updating hotel static information is provided, comprising: Obtain raw static data of hotels from multiple suppliers; Analyze the raw data to establish a unified data standard template for hotel information across multiple dimensions, as well as a mapping relationship between heterogeneous data formats of hotel information and the unified data standard; Based on the data standard template and mapping relationship, the original data is standardized and transformed, and the transformed hotel static information standard data is persistently stored in the local database. Regularly update and monitor / correct the standard data of hotel static information stored in the local database.

[0007] In one possible implementation, raw hotel static information data is obtained from multiple suppliers, including: The raw data is obtained by calling the application programming interface (API) provided by the supplier or by parsing the static information file provided by the supplier.

[0008] In one possible implementation, the raw data is analyzed to establish a unified data standard template for hotel information across multiple dimensions, as well as a mapping relationship between heterogeneous data formats of hotel information and the unified data standard, including: Based on the analysis of raw data on hotel static information from multiple suppliers, a standard set of fields and formats for describing hotel static information are defined, and a multi-dimensional unified data standard template is created. Establish a correspondence between the specific data format, encoding, or value used by the supplier and the standard fields, encoding, or value in the data standard template to form the mapping relationship.

[0009] In one possible implementation, the original data is standardized and transformed according to the data standard template and mapping relationship, including: Fill the supplier-specific field content from the original data into the corresponding standard field in the data standard template; Based on preset rules, specific values ​​in the original data are transformed, including coordinate system transformation and code transformation; The format of the original data values ​​is standardized to the format specified in the data standard template.

[0010] In one possible implementation, the coordinate system transformation includes: converting latitude and longitude information provided by different suppliers based on different coordinate systems into a preset standard coordinate system, and storing the transformed coordinates in the corresponding fields of the data standard template.

[0011] In one possible implementation, the standardization transformation of the original data based on the data standard template and mapping relationship further includes: When conflicting data is detected, it is processed according to a preset conflict resolution strategy; the conflicting data includes at least: multiple records from the same supplier with different hotel codes but the same hotel name.

[0012] In one possible implementation, the hotel's static information standard data stored in a local database is updated periodically, updated in real time, and monitored and corrected, including: The hotel's static information from suppliers will be fully updated according to the preset cycle. When the supplier's static hotel information changes, the data is received and updated through a data synchronization mechanism; Monitor the accuracy and integrity of stored data, and trigger error correction processes when errors or anomalies are detected.

[0013] According to one aspect of this disclosure, a hotel static information adaptive update system is provided, comprising: The acquisition unit is used to acquire raw data of hotel static information from multiple suppliers; A unit is established to analyze the raw data, establish a unified data standard template for hotel information across multiple dimensions, and establish a mapping relationship between heterogeneous data formats of hotel information and the unified data standard. The conversion unit is used to perform standardized conversion processing on the original data according to the data standard template and mapping relationship, and persistently store the converted hotel static information standard data in the local database. The update unit is used to periodically update and in real-time update the standard static information data of hotels stored in the local database, as well as monitor and correct the data.

[0014] According to one aspect of this disclosure, an electronic device is provided, comprising: Processor and memory; The memory is used to store computer programs, and the processor calls the computer programs stored in the memory to execute the hotel static information adaptive update method described above.

[0015] According to one aspect of this disclosure, a computer-readable storage medium is provided, wherein a computer program is stored therein, which, when executed by a processor, enables the processor to perform the hotel static information adaptive update method described in any of the preceding claims.

[0016] This disclosure offers the following advantages: It provides an adaptive update mechanism for supplier hotel static information based on multi-dimensional perception, aiming to achieve convenient, fast, accurate, and cost-effective maintenance and updating of static information in the hotel industry. This method and mechanism have the following significant advantages: Efficient Storage and Retrieval: A standardized template for hotel static information was created using multi-vendor, multi-dimensional standards. This unifies hotel static information data from multiple vendors and standardizes key feature data, ensuring data standardization and uniformity across the platform. A two-tier storage structure utilizing a database and Redis cache ensures convenient storage and retrieval. This design supports high-concurrency, high-performance queries, significantly improving query speed.

[0017] Accuracy and Real-Time Guarantee: This method is based on large-scale data updates from upstream suppliers and will be continuously maintained and updated. This ensures the accuracy of hotel information and provides a reliable information basis for the hotel industry. Combined with message notification technology, real-time data updates and synchronization are achieved, ensuring the up-to-dateness and timeliness of hotel static information.

[0018] Economic practicality: This method allows for standardized and formatted updates of static information across all supplier resource access points, reducing the cost of information standardization and making it more economical. It also possesses integration capabilities with other systems, enabling easy expansion to other industries or fields, thus offering broad application prospects.

[0019] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features and advantages of this application will become apparent from the accompanying drawings. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not intended to limit this disclosure. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0021] Figure 1 This is a flowchart of an exemplary embodiment of a hotel static information adaptive update method; Figure 2 This is a flowchart illustrating an exemplary embodiment of a hotel static information adaptive update method based on multi-dimensional perception. Figure 3 This is a block diagram of a hotel static information adaptive update system according to an exemplary embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment of the present invention. Detailed Implementation

[0022] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of these specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0023] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware units or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0024] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all steps. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0025] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in a sequence other than those illustrated or described herein.

[0026] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or device that includes a series of steps or sub-modules is not necessarily limited to those steps or sub-modules that are explicitly listed, but may include other steps or sub-modules that are not explicitly listed or that are inherent to such process, method, product, or device.

[0027] Figure 1 This is a flowchart of an exemplary embodiment of a hotel static information adaptive update method, such as... Figure 1 As shown, an exemplary embodiment of this disclosure provides a method for adaptively updating hotel static information, including: Obtain raw static data of hotels from multiple suppliers; Analyze the raw data to establish a unified data standard template for hotel information across multiple dimensions, as well as a mapping relationship between heterogeneous data formats of hotel information and the unified data standard; Based on the data standard template and mapping relationship, the original data is standardized and transformed, and the transformed hotel static information standard data is persistently stored in the local database. Regularly update and monitor / correct the standard data of hotel static information stored in the local database.

[0028] This embodiment provides an adaptive update mechanism for hotel static information based on multi-dimensional perception, which is applied to a hotel aggregation platform and can accurately, efficiently, and economically support the updating and maintenance of hotel static information.

[0029] Specifically, raw data on hotel static information is obtained from multiple suppliers, including: The raw data is obtained by calling the application programming interface (API) provided by the supplier or by parsing the static information file provided by the supplier.

[0030] This embodiment discloses the data collection steps, specifically: obtaining raw data from suppliers; due to the numerous categories of suppliers, in order to standardize and manage the data, static hotel information from multiple suppliers is collected. This information may include basic hotel information (such as hotel name, address, contact information, etc.), room information (such as room type, number of beds, room facilities, etc.), and other relevant information (such as hotel rating, surrounding facilities, etc.). The collected static hotel information from multiple suppliers is then analyzed to facilitate the creation of a standardized template in the next step.

[0031] Specifically, the raw data is analyzed to establish a unified data standard template for hotel information across multiple dimensions, as well as a mapping relationship between heterogeneous data formats and the unified data standard for hotel information, including: Based on the analysis of raw data on hotel static information from multiple suppliers, a standard set of fields and formats for describing hotel static information are defined, and a multi-dimensional unified data standard template is created. Establish a correspondence between the specific data format, encoding, or value used by the supplier and the standard fields, encoding, or value in the data standard template to form the mapping relationship.

[0032] Specifically, based on the data standard template and mapping relationship, the original data undergoes standardization transformation processing, including: Fill the supplier-specific field content from the original data into the corresponding standard field in the data standard template; Based on preset rules, specific values ​​in the original data are transformed, including coordinate system transformation and code transformation; The format of the original data values ​​is standardized to the format specified in the data standard template.

[0033] Specifically, the coordinate system conversion includes: converting latitude and longitude information provided by different suppliers based on different coordinate systems into a preset standard coordinate system, and storing the converted coordinates in the corresponding fields of the data standard template.

[0034] This embodiment discloses the data standardization and mapping steps: establishing a unified standard based on multi-dimensional data, creating data mapping relationships, and persistently storing and caching them; Data Standardization: Analyze the multi-supplier hotel static information data collected in the previous step to create a template for original supplier hotel static information based on multi-dimensional standards. This helps improve data consistency, accuracy, and manageability, facilitating data integration and analysis. Select key fields or combinations of fields that can uniquely identify each supplier and hotel, such as supplier code, supplier-specific hotel code, etc. These are used to record the correspondence between hotel information from different suppliers and the unified identifier. Define the hotel static information content that needs to be standardized, commonly including: Basic information: hotel name, address, telephone, email, opening date, star rating, etc. Geographic information: latitude and longitude, city, region, etc. Room facilities (e.g., air conditioning, TV, free Wi-Fi, etc.). Supplier information: supplier code, supplier name, etc. Create a standardized template for supplier hotel static information based on the unique identifier to record the original supplier hotel static information data.

[0035] Keyword Mapping Template: Due to the diverse categories of supplier sources, we have created keyword mapping data for multiple suppliers to ensure unified and standardized data management. This guarantees the uniqueness and accuracy of the data. Keyword mapping data includes: supplier country code, supplier city code, province, and latitude and longitude coordinates. A unique identifier is established based on the supplier code, country code, or city code, creating standardized mapping relationships for the platform. This mapping data is persistently stored. As the amount of resource data continues to increase, the supplier-specific mapping data will be continuously supplemented and improved during actual operation.

[0036] Due to the large volume of data, we use a Redis (RemoteDictionaryServer) caching mechanism to improve efficiency. Redis is an open-source, single-core, in-memory key-value database where data is stored in memory, not on disk. Redis caching is suitable for scenarios with frequent read operations, such as read-heavy, write-light, low-frequency data updates, and dispersed data access hotspots. By storing frequently accessed data in Redis, we can reduce the number of database accesses, thereby improving application performance and responsiveness. Redis caching is a highly efficient and flexible in-memory storage system suitable for various scenarios requiring optimized read operations.

[0037] Specifically, the standardization transformation of the original data based on the data standard template and mapping relationship further includes: When conflicting data is detected, it is processed according to a preset conflict resolution strategy; the conflicting data includes at least: multiple records from the same supplier with different hotel codes but the same hotel name.

[0038] This embodiment describes the data integration and storage steps: integrating data according to standardized templates and mapping relationships and persistently storing it; By establishing API connections with various supplier hotel systems, direct connection programs are created for each supplier. These programs automatically retrieve static hotel information (including hotel name, phone number, address, country, city, latitude and longitude) using a scheduled API mechanism. The raw supplier data is then standardized and integrated into a unified data structure based on the multi-dimensional unified data standard template and mapping relationships established in the previous step, and persistently stored in a local database. Persistent storage processing includes: creating a static hotel information table for supplier hotel data and storing this information in the database (the significance of this standardized static information lies in its future use for other functions, such as user location-based hotel searches; this will not be elaborated upon here). For suppliers that do not support API interfaces, they can provide corresponding static hotel information files in file formats (such as CSV, XML, or JSON). The platform can parse and update the data according to the different file formats provided by different suppliers.

[0039] During the integration process, data conflicts may need to be addressed. For example, there may be multiple records for hotels with different hotel codes but the same hotel name from the same supplier. In such cases, it is necessary to confirm with the supplier whether the hotel is accurate to resolve the conflict, or to handle the conflict separately according to the different rules of each supplier.

[0040] The raw data, along with examples of formatting and mapping, are shown in Table 1: Table 1 shows the original data and examples of formatting and mapping.

[0041] Specifically, the hotel's static information standard data stored in the local database is updated regularly and in real time, and data is monitored and corrected, including: The hotel's static information from suppliers will be fully updated according to the preset cycle. When the supplier's static hotel information changes, the data is received and updated through a data synchronization mechanism; Monitor the accuracy and integrity of stored data, and trigger error correction processes when errors or anomalies are detected.

[0042] This embodiment describes the data update and maintenance steps: real-time updates and periodic updates, as well as data monitoring and error correction; Scheduled Updates: A fixed time interval (e.g., daily, weekly) is set for a comprehensive update of the supplier's hotel static information to ensure timeliness and accuracy. Real-time Updates: A real-time data synchronization mechanism is established with the supplier, ensuring that updated data is promptly pushed to the platform when hotel information changes. Data Monitoring and Error Correction: A data monitoring system is established to regularly check the completeness and accuracy of the data. Upon discovering errors or abnormal data, timely communication with the supplier and hotel is conducted for verification and correction.

[0043] Example The following is combined with Figure 2 This embodiment introduces a specification update method based on multi-supplier personalized feature extraction, which is implemented through step ad.

[0044] a. Data collection: Obtain raw data from suppliers.

[0045] Collecting static hotel information from multiple suppliers and standardizing the data collection of hotel information from these suppliers helps to integrate and manage information provided by different suppliers. The following are the specific operational steps and key points: Define the scope of information collection: This includes basic hotel information (such as name, address, telephone number, email address), room details (room type, number, facilities), hotel rating (hotel class, hotel group, etc.), services (dining, conference facilities, entertainment facilities, etc.), and other information (opening date, last renovation date), etc. Obtain raw static hotel information data from suppliers through the Application Program Interface (API), and analyze the obtained supplier hotel static information. For suppliers that do not support API access to obtain hotel static information, the supplier's hotel static information can be obtained by parsing the hotel static information file. Examples of raw data styles are shown in Table 2. Table 2 Original Data Style Sheet

[0046] b. Data standardization and mapping: Establish a unified standard based on multi-dimensional data, create data mapping relationships, and persist and cache the data.

[0047] Supplier hotel information standardization refers to organizing and standardizing hotel information provided by different suppliers according to unified specifications and formats to improve the accuracy, consistency, and usability of the information. The following are some key standardization contents and methods: Define common field names and meanings to ensure that data from different vendors can be accurately mapped to standard fields. For example, the "Hotel Name" field corresponds to the official name of the hotel in the data from all vendors.

[0048] Establish a data dictionary: Create a unified, standardized data dictionary for multiple vendors, detailing the meaning, data type, value range, and whether each field is required.

[0049] Examples of data field styles are shown in Table 3: Table 3 Data Field Style Table

[0050]

[0051]

[0052]

[0053] For fields that may differ, corresponding conversion rules should be established. For example, different suppliers use different latitude and longitude systems; some use the Gaode coordinate system, while others use the Google coordinate system. Therefore, a standard coordinate system conversion rule can be established to use a unified coordinate system and convert the suppliers' non-standard coordinate systems into the standard coordinate system. Here, we use the Gaode coordinate system as the standardized coordinate system.

[0054] Examples of coordinate system transformations are shown in Table 4: Table 4. Examples of Coordinate System Transformation

[0055] The supplier hotel city-country code mapping associates the city and country of a hotel with specific codes to facilitate data storage, transmission, and processing. Based on the original supplier data, the country and city codes vary across different suppliers' static hotel information. To enable users to quickly and accurately locate hotels and pinpoint their geographical location using the platform system, the platform calculates and maps hotels based on various factors and weights during hotel management and integration. Differences in country and city codes can cause deviations in the hotel mapping calculation. To address this issue, a mapping relationship based on supplier codes, city codes, and country codes has been created.

[0056] Develop a mapping program: Use a programming language (such as Java) to write a program that automatically transforms data according to mapping rules. For example, use Java's dictionary structure to store mapping relationships to achieve fast data transformation. Persistently store the mapped data and cache it.

[0057] Examples of the mapping relationship between country code and city code are shown in Table 5: Table 5. Example of mapping relationship between national code and city code

[0058] c. Data integration and storage: Integrate data based on standardized templates and mapping relationships and store it persistently.

[0059] In step c, based on the standard data model and the mapping relationship between the supplier hotels' countries and cities, the static information of the supplier hotels is integrated. It is determined which field in the standard model each supplier field corresponds to. For data that needs transformation or processing (such as latitude and longitude conversion, city and country mapping), it is explicitly stored in the data.

[0060] d. Data updates and maintenance: real-time and periodic updates, as well as data monitoring and error correction.

[0061] Regular Updates: Establish a regular update mechanism, such as conducting a comprehensive review and update of the hotel's static information daily or weekly. The review should include basic hotel information (e.g., hotel name, address, contact information), room information (e.g., room type, facilities, prices), and hotel facilities and services information (e.g., dining facilities, leisure and entertainment facilities, services offered). Different suppliers have different update cycles; therefore, the update frequency and cycle should be customized based on the supplier's actual situation and volume.

[0062] Real-time updates: When significant changes occur to hotel information, such as renovations, additions or cancellations of facilities and services, or changes in hotel brand, the supplier should immediately transmit the changes to the relevant departments or systems and update the information as soon as possible. Simultaneously, any errors or inaccuracies in guest feedback or complaints should be promptly verified and updated in real time.

[0063] Data monitoring and error correction: In supplier hotel data management, data monitoring and error correction are key steps to ensure data quality. The following are specific implementation methods: Establish a monitoring indicator system: 1. Accuracy indicator: Check the degree of matching between key information such as city / country code, hotel name, and address and the actual situation, and calculate the proportion of accurate records to total records. 2. Completeness indicator: Assess whether information such as hotel star rating, latitude and longitude, hotel facilities, and services is complete, and count the number and proportion of records with missing values.

[0064] Employ automated monitoring tools: Use data monitoring software or written scripts to periodically and automatically scan hotel data in the database. These tools can quickly detect abnormal data and generate detailed reports according to set rules and indicators. For example, by writing SQL (Structured Query Language) scripts, data records with city and country codes that do not conform to the standard format or do not match the actual location of the hotel can be retrieved.

[0065] Set up a real-time monitoring mechanism: Configure real-time monitoring for changes in critical data, such as hotel status and renovation dates. Immediately issue alerts to relevant personnel when abnormal data changes occur. For example, if the hotel closes, the system automatically sends notifications to suppliers and data administrators to facilitate timely verification.

[0066] Data error correction (error classification and analysis): Classify errors detected by monitoring, such as data entry errors, system integration errors, and untimely data updates. Analyze the causes of each error type to implement targeted solutions. Regularly communicate with suppliers regarding data quality and jointly explore methods and measures to optimize data management.

[0067] Figure 3 This is a block diagram of a hotel static information adaptive update system according to an exemplary embodiment of the present invention, such as... Figure 3 As shown, an exemplary embodiment of this disclosure provides a hotel static information adaptive update system, including: The acquisition unit is used to acquire raw data of hotel static information from multiple suppliers; A unit is established to analyze the raw data, establish a unified data standard template for hotel information across multiple dimensions, and establish a mapping relationship between heterogeneous data formats of hotel information and the unified data standard. The conversion unit is used to perform standardized conversion processing on the original data according to the data standard template and mapping relationship, and persistently store the converted hotel static information standard data in the local database. The update unit is used to periodically update and in real-time update the standard static information data of hotels stored in the local database, as well as monitor and correct the data.

[0068] Figure 4 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment of this invention. Figure 4 As shown, corresponding to the above-described adaptive update method for hotel static information, this disclosure also provides an electronic device. Since the embodiment of this device is similar to the above-described method embodiment, the description is relatively simple; relevant details can be found in the description of the above-described method embodiment section. The device described below is merely illustrative. This device may include: a processor 1, a memory 2, a communication bus (i.e., the aforementioned device bus), and a lookup engine. The processor 1 and memory 2 communicate with each other via the communication bus and communicate with external systems via a communication interface. The processor 1 can call logical instructions in the memory 2 to execute the adaptive update method for hotel static information.

[0069] Furthermore, the logical instructions in the aforementioned memory 2 can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as memory chips, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0070] On the other hand, this disclosure also provides a processor-readable storage medium storing a computer program 3, which, when executed by a processor 1, is implemented to perform the hotel static information adaptive update method provided in the above embodiments.

[0071] The processor-readable storage medium can be any available medium or data storage device that the processor 1 can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0072] The above are merely preferred embodiments of this disclosure. The scope of protection of this disclosure is not limited to the above embodiments. All technical solutions falling within the scope of this disclosure are protected. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of this disclosure should be considered within the scope of protection of this disclosure.

Claims

1. A method for adaptively updating static hotel information, characterized in that, include: Obtain raw static data of hotels from multiple suppliers; Analyze the raw data to establish a unified data standard template for hotel information across multiple dimensions, as well as a mapping relationship between heterogeneous data formats of hotel information and the unified data standard; Based on the data standard template and mapping relationship, the original data is standardized and transformed, and the transformed hotel static information standard data is persistently stored in the local database. Regularly update and monitor / correct the standard data of hotel static information stored in the local database.

2. The hotel static information adaptive update method according to claim 1, characterized in that, Obtain raw hotel static information data from multiple suppliers, including: The raw data is obtained by calling the application programming interface (API) provided by the supplier or by parsing the static information file provided by the supplier.

3. The hotel static information adaptive update method according to claim 1, characterized in that, Analyze the raw data to establish a unified data standard template for hotel information across multiple dimensions, and to establish a mapping relationship between heterogeneous data formats of hotel information and the unified data standard, including: Based on the analysis of raw data on hotel static information from multiple suppliers, a standard set of fields and formats for describing hotel static information are defined, and a multi-dimensional unified data standard template is created. Establish a correspondence between the specific data format, encoding, or value used by the supplier and the standard fields, encoding, or value in the data standard template to form the mapping relationship.

4. The hotel static information adaptive update method according to claim 1, characterized in that, Based on the data standard template and mapping relationship, the original data undergoes standardization transformation processing, including: Fill the supplier-specific field content from the original data into the corresponding standard field in the data standard template; Based on preset rules, specific values ​​in the original data are transformed, including coordinate system transformation and code transformation; The format of the original data values ​​is standardized to the format specified in the data standard template.

5. The method according to claim 4, characterized in that, The coordinate system conversion includes: converting latitude and longitude information provided by different suppliers based on different coordinate systems into a preset standard coordinate system, and storing the converted coordinates in the corresponding fields of the data standard template.

6. The method according to claim 1, characterized in that, Based on the data standard template and mapping relationship, the original data is standardized and transformed, which also includes: When conflicting data is detected, it is processed according to a preset conflict resolution strategy; the conflicting data includes at least: multiple records from the same supplier with different hotel codes but the same hotel name.

7. The hotel static information adaptive update method according to claim 1, characterized in that, Regularly update and monitor / correct the standard static information data of hotels stored in the local database, including: The hotel's static information from suppliers will be fully updated according to the preset cycle. When the supplier's static hotel information changes, the data is received and updated through a data synchronization mechanism; Monitor the accuracy and integrity of stored data, and trigger error correction processes when errors or anomalies are detected.

8. A hotel static information adaptive update system, characterized in that, include: The acquisition unit is used to acquire raw data of hotel static information from multiple suppliers; A unit is established to analyze the raw data, establish a unified data standard template for hotel information across multiple dimensions, and establish a mapping relationship between heterogeneous data formats of hotel information and the unified data standard. The conversion unit is used to perform standardized conversion processing on the original data according to the data standard template and mapping relationship, and persistently store the converted hotel static information standard data in the local database. The update unit is used to periodically update and in real-time update the standard static information data of hotels stored in the local database, as well as monitor and correct the data.

9. An electronic device, characterized in that, include: Processor and memory; The memory is used to store computer programs, and the processor calls the computer programs stored in the memory to execute the hotel static information adaptive update method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, enables the processor to perform the hotel static information adaptive update method according to any one of claims 1 to 7.

Images