A hotel AI service control method and system based on check-in related information, a terminal, and a storage medium

Abstract

The application discloses a hotel AI service control method and system based on check-in associated information, a terminal and a storage medium. After a guest completes check-in, a background system generates a dynamic binding voucher based on a check-in record; a terminal device acquires the voucher and submits device identification, device authentication information and a voucher identification; and the background system establishes unified check-in associated information after verification. The terminal device initiates a hotel service request through a unified service portal within the validity period of the associated information, the background system performs permission verification and business routing based on the associated information, and calls a corresponding hotel business subsystem to execute the service; and the related permissions are uniformly recycled when check-out, loss, time limit expiration or revocation, thereby improving service control security and collaboration.

Description

Technical Field

[0001] This invention relates to the technical field of hotel digital services, and in particular to a hotel AI service control method, system, terminal and storage medium based on check-in related information. Background Technology

[0002] With the improvement of hotel informatization and intelligentization, more and more hotels are beginning to introduce digital services such as self-check-in, smart door locks, room equipment control, online ordering, room service, robot delivery, wake-up reminders, and self-check-out. Guests can initiate operations such as opening doors, adjusting air conditioning, controlling lights, scheduling wake-up calls, submitting service requests, or checking out through mobile phones, smartwatches, tablets, and wristbands, enabling hotel services to gradually shift from traditional front desk manual processing to online, terminal-based, and automated processes.

[0003] However, in existing hotel digital systems, check-in management systems, door lock systems, guest room control systems, catering systems, front desk service systems, delivery systems, robot systems, and wake-up service systems are typically built and interconnected separately. The interfaces, authentication methods, user identifiers, and room statuses between these subsystems are not entirely unified. Although guests can access functions such as unlocking doors, controlling room access, ordering food, calling services, and receiving reminders through different entry points, these functions are often simply aggregated into the terminal interface, lacking a stable and unified identity association information that is linked to the current check-in status in real time.

[0004] In the aforementioned distributed service model, different subsystems need to separately identify guest identities, room information, check-in times, and available permissions, which can easily lead to problems such as duplicate authentication, incorrect room associations, inaccurate service routing, and untimely status synchronization. For example, door lock permissions, room control permissions, dining privileges, room service permissions, and notification push permissions may be maintained by different systems. When guests change rooms, extend their stays, have multiple guests, have equipment replaced, or lose terminals, it is difficult for the systems to maintain consistency in a timely manner, thereby affecting the security and accuracy of service control.

[0005] Furthermore, existing terminal devices in hotel settings typically function primarily as collections of "function entry points" or "control buttons," failing to establish unified check-in association information that can be reused across multiple hotel business systems based on the guest's current check-in status. Especially in cases of check-out completion, check-in expiration, device loss, misbinding, or administrator revocation, door lock permissions, in-room device control permissions, and service access permissions often need to be revoked separately, easily leading to issues such as untimely permission revocation, residual old credentials, and abnormal requests continuing to be effective. Therefore, it is necessary to propose a hotel check-in association information binding and unified service control scheme based on terminal devices. This scheme would enable terminal devices to establish secure bindings with current check-in records, rooms, time periods, and permissions, and provide unified authentication, routing, orchestration, and deregistration for door locks, room control, room service, catering, reminders, and check-out services during the check-in period. Summary of the Invention

[0006] In view of this, it is necessary to provide a hotel AI service control method, system, terminal and storage medium based on check-in association information. This will at least solve the problems in the existing hotel digital service system, where there is no unified binding relationship between terminal devices and guest check-in information, room permissions and various hotel services, which leads to duplicate authentication in different subsystems, scattered service routing, inconsistent permission control and asynchronous permission revocation after check-out.

[0007] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides a hotel AI service control method based on check-in association information, comprising: After a guest completes check-in, the back-end system generates a dynamic binding credential based on the check-in record. The dynamic binding credential is associated with the check-in identifier, target space identifier, check-in time window, and service permission set corresponding to this check-in. The terminal device obtains the dynamic binding credential and submits the device identifier, device authentication information, and credential identifier corresponding to the dynamic binding credential to the backend system. The backend system verifies the dynamic binding credential and the device authentication information, and establishes unified check-in association information corresponding to this check-in after the verification is successful. The unified check-in association information includes at least check-in identifier, target space identifier, check-in time window, terminal device identifier, permission scope and status information. During the validity period of the unified check-in association information, the terminal device initiates a hotel service request through the unified service portal, and the hotel service request is associated with the unified check-in association information; The backend system performs permission verification and business routing on the hotel service request based on the unified check-in association information, and calls the hotel business subsystem corresponding to the hotel service request to execute the corresponding service; When the preset invalidation conditions are met, the backend system will invalidate the dynamic binding certificate based on the unified check-in association information, and uniformly reclaim the door lock permissions, in-room equipment control permissions and service call permissions associated with the unified check-in association information. The preset failure conditions include at least one of the following: check-out completed, terminal device reported lost, check-in time window expired, or administrator revocation.

[0008] In a further embodiment, the unified check-in association information also includes one or more of the following: guest identifier or desensitized value of guest identifier, role level, service scope, request priority, room status summary, and association information version number; The associated information version number is used to refresh, verify invalidity, or perform idempotent verification of the unified check-in associated information when there is a renewal of stay, room change, loss of terminal device, change of permissions, or revocation of binding.

[0009] In a further embodiment, the dynamic binding credential includes one or more of the following: credential identifier, check-in identifier, target space identifier, valid time range, permission template identifier, binding method identifier, device binding quantity limit, random verification value, and server signature information; The binding method identifier is used to instruct the terminal device to obtain the dynamic binding credential through scanning, near-field sensing, or manual confirmation. The random verification value and server signature information are used to perform anti-replay verification and integrity verification on the dynamic binding credential.

[0010] In a further embodiment, after the dynamic binding credential and the device authentication information are verified, the backend system issues a set of permission tokens to the terminal device. The set of permission tokens includes one or more of the following: a service control token for online service invocation, a door lock permission credential for door lock verification, device capability description data for in-room device control, and a session key or instruction signature parameter for instruction security verification.

[0011] In a further embodiment, when the hotel service request is a room equipment control request, the backend system determines the equipment capability model corresponding to the target space based on the unified check-in association information, and converts the unified control command issued by the terminal device into a protocol command that can be recognized by the guest room control gateway before sending it to the corresponding room equipment. The device capability model includes one or more of the following: device type, device instance identifier, operable actions, parameter range, scene mode mapping, and exception reporting code.

[0012] In a further embodiment, when the hotel service request is a check-out request, the backend system first queries one or more of the following: bill status, deposit status, incomplete service status, delivery status, and delayed check-out status. After the check-out settlement conditions are met, the back-end system generates a check-out confirmation and sequentially performs one or more of the following actions: freezing new requests, invalidating door lock permissions, invalidating in-room device control permissions, invalidating service call permissions, clearing local bound credentials, and updating room status.

[0013] In a second aspect, the present invention provides a hotel AI service control system based on check-in association information, comprising: The binding management module is used to generate a dynamic binding certificate based on the check-in record after the guest completes check-in. The dynamic binding certificate is associated with the check-in identifier, target space identifier, check-in time window and service permission set corresponding to this check-in, and is used to receive binding requests submitted by terminal devices. The device authentication module is used to verify the device identifier and device authentication information in the binding request; The association information management module is used to establish unified check-in association information corresponding to this check-in after the dynamic binding credential and the device authentication information are verified. The unified check-in association information includes at least check-in identifier, target space identifier, check-in time window, terminal device identifier, permission scope and status information. A unified service gateway is used to receive hotel service requests initiated by terminal devices within the validity period of the unified check-in association information, and to perform permission verification and service routing on the hotel service requests based on the unified check-in association information. The service orchestration module is used to call the corresponding hotel business subsystem to execute the corresponding service based on the business routing result; The permission cancellation module is used to invalidate the dynamic binding certificate when the preset invalidation conditions are met, and to uniformly reclaim the door lock permissions, in-room equipment control permissions and service call permissions associated with this check-in based on the unified check-in association information. The hotel business subsystem includes at least one or more of the following: door lock system, guest room control system, guest room service system, catering system, reminder service system, or check-out processing system.

[0014] In a further embodiment: the system also includes a reminder event engine, which is used to send reminder information to the corresponding bound terminal device based on events such as dining benefits, takeout arrival, wake-up call reservation, delivery completion, or room service status change, combined with the target space identifier, terminal device identifier, role level, service status, and trigger time window in the unified check-in association information, and to route subsequent operations initiated by the terminal device in response to the reminder information to the corresponding hotel business subsystem. In a third aspect, the present invention provides a terminal device, including a processor, a memory, a communication module, and a computer program stored in the memory and executable by the processor; When the computer program is executed by the processor, the terminal device performs the following steps: Obtain the dynamic binding credential generated by the backend system based on the guest check-in record; Submit the device identifier, device authentication information, and the credential identifier corresponding to the dynamically bound credential to the backend system in order to request the establishment of unified check-in association information corresponding to this check-in; After the unified check-in association information is established, the session state and / or permission token associated with the unified check-in association information are saved; During the validity period of the unified check-in association information, a hotel service request is initiated to the backend system through the unified service portal, and the hotel service request is associated with the unified check-in association information; Receive service execution results, status synchronization information, or permission expiration information returned by the backend system; Upon receiving permission expiration information or detecting that the locally bound credentials have expired, clear or invalidate the locally stored binding information, session state, and / or permission tokens.

[0015] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, a method for binding and unifying service control of hotel check-in association information based on a terminal device is implemented.

[0016] Compared with the prior art, the present invention has the following advantages: Through a closed-loop design of "check-in record - dynamic binding credentials - unified check-in association information - unified service control - check-out permission revocation," terminal devices can form a secure binding relationship with the guest's current check-in status, target space, check-in time window, and permission scope. The backend system uses unified check-in association information to perform unified authentication and business routing for requests such as door locks, in-room equipment control, room service, catering, reminders, and check-out. This reduces the risks of duplicate authentication, inconsistent status, and incorrect room routing caused by multiple subsystems of the existing hotel system separately identifying guests, rooms, and permissions, and improves the consistency and accuracy of cross-system service calls.

[0017] Meanwhile, this application enhances the security and timeliness of terminal device binding and service invocation through dynamic binding credentials, device authentication information, random verification values, server signature information, and permission token sets. The backend system can combine check-in time windows, role levels, service scope, room status summaries, and associated information version numbers to provide fine-grained control over different terminal devices, guest roles, and service requests, avoiding issues such as misbinding, unauthorized control, and the continued effectiveness of old permissions. In in-room device control scenarios, unified control commands can be converted into protocol commands recognizable by the guest room control gateway based on the device capability model, improving the compatibility and scalability of room control services.

[0018] Furthermore, in cases such as check-out completion, terminal device loss reporting, check-in time window expiration, or administrator revocation, this application can invalidate dynamically bound credentials based on unified check-in association information, and uniformly reclaim door lock permissions, in-room device control permissions, and service call permissions. This avoids the problems of delayed revocation, residual permissions, and abnormal requests continuing to take effect caused by separate cancellations of each system in the prior art, thereby improving the security, collaboration, response efficiency, and operation and maintenance management convenience of the hotel's digital service system.

[0019] To make the above and other objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] in: Figure 1 This is a schematic diagram of the overall system architecture of the present invention; Figure 2 A flowchart is established for the dynamic binding certificate and unified check-in association information of this invention; Figure 3 This is a schematic diagram of the data structure for the unified check-in association information of the present invention; Figure 4 This is a flowchart illustrating the unified service control and business routing process of the present invention. Figure 5 This is a schematic diagram of the in-room equipment control and equipment capability model conversion of the present invention.

[0021] Label Explanation: 10. Terminal equipment; 20. Back-end system; 30. Hotel back-end / PMS check-in management system; 40. Mobile relay terminal; 50. Door lock system; 60. Guest room control system; 601. Guest room control gateway; 70. Guest room service system; 80. Catering system; 90. Reminder service system; 100. Check-out processing system; 201. Binding management module; 202. Device authentication module; 203. Related Information Management Module; 204. Unified Service Gateway; 205. Service Orchestration Module; 206. Permission Cancellation Module; 207. Reminder Event Engine; 208. Unified Check-in Related Information; 209. Dynamic Binding Credentials; 210. Permission Token Set; 211. Device Capability Model; 212. Room Control Orchestration Module. Detailed Implementation

[0022] To make the technical problems, solutions, and beneficial effects of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of the invention.

[0023] like Figure 1 As shown, this embodiment provides a method, system, terminal, and storage medium for binding and unifying hotel check-in information based on a terminal device 10. The terminal device 10 can be a smartwatch, smart bracelet, mobile phone, tablet computer, or other user-side device with communication capabilities, preferably a smartwatch that is easy for guests to carry and operate instantly. The backend system 20 can include a hotel backend and a hotel middle platform. The hotel backend can be connected to the hotel check-in management system to obtain guest check-in records; the hotel middle platform is used to perform device binding, device authentication, associated information management, permission verification, service routing, business orchestration, reminder event triggering, and permission cancellation. Hotel business subsystems can include a door lock system 50, a guest room control system 60, a guest room service system 70, a catering system 80, a reminder service system 90, a check-out processing system 100, a front desk system, a delivery system, or a robot system, etc.

[0024] like Figure 2 As shown, after a guest completes check-in, the hotel back-end / PMS check-in management system 30 generates a dynamic binding credential 209 corresponding to this check-in based on the check-in record. This check-in record typically includes the check-in order, room number, check-in start and end times, guest information, room status, and available service rights. The dynamic binding credential 209 is not a regular fixed QR code or static room code, but a temporary credential associated with this check-in, linked to the check-in identifier, target space identifier, check-in time window, and service permission set. The terminal device 10 can obtain the dynamic binding credential 209 through scanning, NFC near-field sensing, Bluetooth near-field sensing, front desk confirmation, or in-room pairing identification, and submits the device identifier, device authentication information, and credential identifier to the back-end system 20. The back-end system 20 verifies the authenticity, validity period, binding count, device legality, and credential integrity of the dynamic binding credential 209. After successful verification, it establishes unified check-in association information 208 corresponding to this check-in.

[0025] like Figure 3 As shown, the unified check-in association information 208 is used to uniformly represent "which check-in, which target space, which terminal device 10, what check-in time window, what permission range, and the current status". In a preferred embodiment, the unified check-in association information 208 may include the following fields: hotelId H23001 Hotel-side configuration Distinguish between hotel or park area stayId ST202504010001 Check-in records Unique identifier for one stay guestRef GUEST_HASH_xxx Guest identity anonymization value Provides cross-system identification of guests without exposing their plaintext identities. roomId 1808 Check-in management system or room control system Binding rooms, routing room control and services stayWindow 2025-04-01 14:00 to 2025-04-03 12:00 Check-in records Limit the validity period of permissions deviceId WATCH_A1B2C3 Terminal device information Identify the terminal that initiated the request. roleLevel Main Guest / Secondary Guest / Temporary Visitor Binding strategy Subdivided executable permissions serviceScope Door locks, room control, room service, food and beverage, reminders, check-out Permission template Limited access to services priority Normal / Emergency Service Request Attributes Used for unified routing and queuing roomStateDigest Currently occupied, do not disturb, energy saving, awaiting cleaning Room status system As a prerequisite for control ctxVersion v17 Related Information Management Module Used for refresh, undo, and idempotency verification. Through the unified check-in association information 208 mentioned above, each hotel business subsystem does not need to establish completely independent guest identification logic and room association logic. Instead, the backend system 20 determines whether the terminal device 10 has been bound, whether the request is within the check-in validity period, whether the target room matches, whether the current role has the corresponding permissions, and whether the room status allows the execution of the corresponding service based on the same set of association information fields. Especially in cases of extended stay, room change, loss of terminal device 10, permission change, or binding revocation, the backend system 20 can refresh, invalidate, or perform idempotent checks on the old association information through the association information version number to prevent old permissions from continuing to be effective.

[0026] Combination Figure 2 As shown, the dynamic binding credential 209 can be generated by the backend system 20 according to a preset security policy and can be provided to the terminal device 10 in the form of a QR code, NFC tag, near-field broadcast data, or manual confirmation code. The dynamic binding credential 209 may include the following fields: credentialId Binding credential identifier Unique value Easy to index and undo stayId / roomId Check-in sign and target room Signature protection Preventing room ownership from being altered validFrom / validTo Effective and Expiration Time Signature protection Limited time limit permProfileId Permission Template Number Signature protection For loading service range bindMode QR code scanning / scanning / manual confirmation Signature protection Indicates binding method deviceLimit Maximum number of bound devices Signature protection Supports multiple guests nonce Random check value Randomly generated Anti-replay serverSign Server digital signature or message authentication code Integrity verification Provide the middle platform to verify the authenticity of the credentials During the binding process, after obtaining the dynamic binding credential 209, the terminal device 10 can submit the credentialId, deviceId, device authentication information, timestamp, random number, and signature value to the backend system 20. The device authentication information can be a device certificate, security chip proof, terminal public key, system authorization information, or login status information of the bound application. During verification, the backend system 20 can determine whether the dynamic binding credential 209 is within a valid time frame, whether it matches the check-in record, whether it exceeds the allowed number of bound devices, whether the random verification value has been used, whether the server signature information is correct, and whether the device authentication information meets the hotel's security policy. This process reduces the risks of forged credentials, duplicate binding, accidental binding across rooms, or unauthorized device service access.

[0027] After successful verification, the backend system 20 issues a set of permission tokens 210 to the terminal device 10. This set of permission tokens 210 may include a service control token for online service invocation, a door lock permission credential for door lock verification, device capability description data for controlling in-room devices, and a session key or instruction signature parameter for instruction security verification. The service control token is primarily used by the terminal device 10 to initiate requests for room service, catering service, reminder service, and check-out through a unified service portal; the door lock permission credential can be used for online unlocking or short-term offline unlocking verification; the device capability description data allows the terminal device 10 to understand the controllable device capabilities of the current room, such as lighting, air conditioning, curtains, fresh air system, and scene modes; the session key or instruction signature parameter ensures the integrity and legality of control instructions during transmission and execution.

[0028] like Figure 4 As shown, within the validity period of the unified check-in association information 208, terminal device 10 initiates a hotel service request through the unified service portal. The hotel service request can be a lock unlock request, an in-room device control request, a room service request, a catering service request, a reminder setting request, a food delivery request, or a check-out request, etc. Each service request is associated with the unified check-in association information 208. After receiving the request, the backend system 20 first performs permission verification based on the unified check-in association information 208, and then performs business routing and service orchestration according to the request type. For example, the backend system 20 can determine whether the stayId and roomId match, whether the deviceId belongs to a bound device, whether the current time is within the stayWindow, whether the roleLevel allows the execution of the service, whether the serviceScope includes the service type, whether roomStateDigest allows the corresponding operation, and determine whether the current association information is a valid version based on ctxVersion.

[0029] In one embodiment, different service types can be routed as follows: door Open door / temporary authorization Door lock system or door lock controller Token valid, door matched, time window valid roomControl Lighting / Air Conditioning / Curtains / Scene Control Guest room control system or room control gateway Room matching, control permissions, room status permission housekeeping Cleaning / Supply / Delivery Guest room service system Service hours, Do Not Disturb status, priority dining Breakfast, ordering food, and extra food requests Catering System Rights, meal segments, room association delivery Food delivery reminders / delivery options Front-end system or robot system Room order association, guest online status wakeUp Wake-up settings / modify / cancel Reminder service system or wake-up service system Time window, mute preference, role permissions checkout Check-out request / confirmation Check-out processing system and permission cancellation module Bills, deposits, and status of unfinished services Through the unified service routing method described above, terminal device 10 does not need to connect to the door lock system 50, room control system, catering system 80, and guest room service system 70 separately. Instead, it submits requests through the unified service entry point of the backend system 20. The backend system 20 then calls the corresponding hotel business subsystem based on the unified check-in association information 208 and service type, thereby reducing the situation of repeated authentication and repeated identification of guests, rooms, and permissions by multiple subsystems and improving the consistency of service scheduling.

[0030] like Figure 5As shown, for in-room device control requests, the backend system 20 determines the device capability model 211 corresponding to the target space based on the unified check-in association information 208. The device capability model 211 may include device type, device instance identifier, operable actions, parameter range, scene mode mapping, and exception reporting code. For example, the device type may include lights, air conditioning, curtains, fresh air system, television, or smart scene panel; operable actions may include turning on / off, adjusting brightness, adjusting temperature, switching modes, or executing scenes; parameter range may limit the air conditioning temperature range, light brightness range, or curtain opening / closing percentage. The unified control command issued by the terminal device 10 is converted by the backend system 20 into a protocol command recognizable by the guest room control gateway 601 before being sent to the corresponding in-room device. The protocol command may be an MQTT message, gateway API request, Modbus control command, or hotel private protocol message, etc. If the room is in a Do Not Disturb, energy-saving, maintenance, unoccupied, or cleaning state, the backend system 20 can restrict or refuse to execute the corresponding device control request based on the room status summary.

[0031] Combination Figure 4 As shown, for door lock control requests, the system can adopt an online verification-based approach with short-term credentials as a fallback. In online mode, terminal device 10 initiates a door opening request through a unified service entry point. The backend system 20 verifies the request based on the service control token, door lock access credentials, and unified check-in association information 208, and issues door opening authorization to the door lock system 50 or the door lock controller. If the door lock system 50 supports near-line or offline verification, terminal device 10 can hold a short-term door lock access credential. The door lock or door lock controller verifies the credential signature, validity period window, and revocation version number according to preset verification parameters, and executes door opening after successful verification. This method balances door opening continuity under network fluctuations and door lock access security.

[0032] For reminder services, the reminders in this embodiment are not simply push notifications, but are triggered and routed by the reminder event engine 207 in conjunction with unified check-in association information 208. The reminder event engine 207 can send reminder information to the corresponding bound terminal device 10 based on events such as dining benefits, takeout arrival, wake-up call reservation, delivery completion, or room service status change, combined with the target space identifier, terminal device 10 identifier, role level, service status, and trigger time window. For example, when the dining system 80 identifies that a guest has breakfast benefits and is currently in the breakfast period, the reminder event engine 207 can send a breakfast reminder to the bound terminal device 10; when the front-end system or delivery system receives a takeout arrival event, the back-end system 20 retrieves valid unified check-in association information 208 based on the roomId and sends a takeout pickup or robot delivery selection reminder to the corresponding terminal device 10; when a guest sets a wake-up time, the reminder event engine 207 can send vibration, ringtone, or linked light reminders to the terminal device 10 within the corresponding time window. Subsequent operations initiated by terminal device 10 in response to reminder messages, such as "remind later", "deliver food to room", "robot delivery", and "cancel wake-up call", are still routed by the backend system 20 to the corresponding business subsystem based on the unified check-in association information 208.

[0033] Combination Figure 3 As shown, in scenarios involving multiple guests or multiple terminal devices 10, the same guest information can be associated with multiple terminal devices 10. The backend system 20 can configure different permission ranges for different terminal devices 10 based on the device binding limit and role level. For example, the primary guest terminal can have door lock permissions, all room control permissions, room service request permissions, catering service permissions, reminder setting permissions, and check-out request permissions; the secondary guest terminal can have door lock permissions, some room control permissions, and reminder receiving permissions; and the temporary visitor terminal can be limited to only having temporary door opening or some service permissions within a short time window. By combining role level and service scope settings, fine-grained permission control can be achieved in multi-guest scenarios, preventing all terminal devices 10 from obtaining the exact same permissions.

[0034] When a guest extends their stay, changes rooms, changes permissions, reports a lost device, or cancels a binding, the backend system 20 refreshes or invalidates the unified check-in association information 208 using the association information version number. For example, when a guest changes rooms, the backend system 20 can generate a new roomId and ctxVersion, and invalidate the old room's door lock permissions and room control permissions; when a guest reports a lost terminal device 10, the backend system 20 adds the corresponding deviceId to the cancellation list, refreshes the unified check-in association information 208 version number, and synchronizes the cancellation status with the door lock system 50, the guest room control system 60, and the unified service gateway 204 to prevent the lost device from continuing to use the old permissions; when an administrator cancels a binding, the backend system 20 can directly invalidate the corresponding dynamic binding credential 209 and permission token set 210.

[0035] Combination Figure 4 As shown, when terminal device 10 initiates a check-out request, the backend system 20 does not directly delete permissions. Instead, it first determines the corresponding bill, deposit, unfinished services, delivery status, and delayed check-out status based on the unified check-in association information 208. If the bill is not settled, the deposit is abnormal, or there are still unfinished room services or delivery tasks, the backend system 20 can return an error message, transfer the request to manual processing, or guide the guest to complete supplementary confirmation. If the check-out settlement conditions are met, the backend system 20 generates a check-out confirmation and sequentially or according to a preset strategy executes new request freezing, door lock permission invalidation, in-room device control permission invalidation, service call permission invalidation, local binding credential clearing, and room status update. After receiving permission invalidation information, terminal device 10 clears or invalidates locally stored binding information, session status, and permission tokens to prevent the old terminal from continuing to initiate door lock, room control, or service requests after check-out.

[0036] In a specific system implementation, the system may include a binding management module 201, a device authentication module 202, an association information management module 203, a unified service gateway 204, a service orchestration module 205, a permission deregistration module 206, and a reminder event engine 207. The binding management module 201 generates a dynamic binding credential 209 after a guest completes check-in and receives binding requests from terminal devices 10; the device authentication module 202 verifies device identifiers and device authentication information; the association information management module 203 establishes, refreshes, and revokes unified check-in association information 208; the unified service gateway 204 receives hotel service requests initiated by terminal devices 10 and performs permission verification and business routing; the service orchestration module 205 calls the corresponding hotel business subsystems according to different service types; the permission deregistration module 206 uniformly revoks relevant permissions under conditions such as check-out completion, terminal device 10 being reported lost, check-in time window expiring, or administrator revocation; and the reminder event engine 207 sends reminder information to the corresponding bound terminal devices 10 based on hotel business events and routes subsequent operations to the corresponding subsystems.

[0037] The terminal device 10 may include a processor, memory, a communication module, and a computer program. The communication module may support cellular networks, Wi-Fi, Bluetooth, NFC, or other near-field communication methods. When the terminal device 10 has independent network connectivity, it can communicate directly with the backend system 20; when the terminal device 10 does not have independent network connectivity, it can forward binding requests, service requests, and control results to the backend system 20 through a mobile relay terminal 40. In the mobile relay mode, the mobile phone only serves as a communication channel, and the final binding object is still the terminal device 10 itself. The binding request still includes the device identifier and device authentication information of the terminal device 10 to avoid mistaking the mobile phone for the final authorized terminal.

[0038] When the computer program stored in the memory is executed by the processor, the terminal device 10 can obtain the dynamic binding credential 209, submit the device identifier, device authentication information, and credential identifier, save the session state and permission token associated with the unified check-in association information 208, initiate hotel service requests associated with the unified check-in association information 208 within the validity period of the unified check-in association information 208, receive service execution results, status synchronization information, or permission expiration information, and clear the local binding information, session state, and permission token when the permission expires. Accordingly, when the computer program stored in the computer-readable storage medium is executed by the processor, the above-described hotel check-in association information binding and unified service control method based on the terminal device 10 can be implemented.

[0039] Through the above implementation methods, this application can establish unified check-in association information 208 based on the current check-in status of guests, incorporating terminal devices 10, target spaces, check-in time windows, permission ranges, and room status into the same control logic, and performing unified authentication, routing, orchestration, and deregistration for hotel services such as door locks, room control, room service, catering, reminders, and check-out. Compared with the existing method of decentralized authentication, routing, and deregistration in various subsystems, this application can reduce duplicate authentication and inconsistent status issues, reduce the risks of incorrect room routing, misbinding, unauthorized control, and residual old permissions, and improve the security, collaboration, and operation and maintenance efficiency of the hotel digital service system.

[0040] The present invention has been described above by way of example with reference to the accompanying drawings. Obviously, the specific implementation of the present invention is not limited to the above-described manner. Any non-substantial improvements made using the inventive concept and technical solution of the present invention, or the direct application of the inventive concept and technical solution of the present invention to other occasions without modification, are all within the protection scope of the present invention.

Claims

1. A hotel AI service control method based on check-in association information, characterized in that, include: After a guest completes check-in, the back-end system generates a dynamic binding credential based on the check-in record. The dynamic binding credential is associated with the check-in identifier, target space identifier, check-in time window, and service permission set corresponding to this check-in. The terminal device obtains the dynamic binding credential and submits the device identifier, device authentication information, and credential identifier corresponding to the dynamic binding credential to the backend system. The backend system verifies the dynamic binding credential and the device authentication information, and establishes unified check-in association information corresponding to this check-in after the verification is successful. The unified check-in association information includes at least check-in identifier, target space identifier, check-in time window, terminal device identifier, permission scope and status information. During the validity period of the unified check-in association information, the terminal device initiates a hotel service request through the unified service portal, and the hotel service request is associated with the unified check-in association information; The backend system performs permission verification and business routing on the hotel service request based on the unified check-in association information, and calls the hotel business subsystem corresponding to the hotel service request to execute the corresponding service; When the preset invalidation conditions are met, the backend system will invalidate the dynamic binding certificate based on the unified check-in association information, and uniformly reclaim the door lock permissions, in-room equipment control permissions and service call permissions associated with the unified check-in association information. The preset failure conditions include at least one of the following: check-out completed, terminal device reported lost, check-in time window expired, or administrator revocation.

2. The hotel AI service control method based on check-in association information according to claim 1, characterized in that: The unified check-in association information also includes one or more of the following: guest identifier or desensitized value of guest identifier, role level, service scope, request priority, room status summary and association information version number; The associated information version number is used to refresh, verify invalidity, or perform idempotent verification of the unified check-in associated information when there is a renewal of stay, room change, loss of terminal device, change of permissions, or revocation of binding.

3. The hotel AI service control method based on check-in association information according to claim 1, characterized in that: The dynamic binding credential includes one or more of the following: credential identifier, check-in identifier, target space identifier, valid time range, permission template identifier, binding method identifier, device binding quantity limit, random verification value, and server signature information; The binding method identifier is used to instruct the terminal device to obtain the dynamic binding credential through scanning, near-field sensing, or manual confirmation. The random verification value and server signature information are used to perform anti-replay verification and integrity verification on the dynamic binding credential.

4. The hotel AI service control method based on check-in association information according to claim 1, characterized in that: After the dynamic binding credential and the device authentication information are verified, the backend system issues a set of permission tokens to the terminal device. The set of permission tokens includes one or more of the following: a service control token for online service invocation, a door lock permission credential for door lock verification, device capability description data for in-room device control, and a session key or instruction signature parameter for instruction security verification.

5. The hotel AI service control method based on check-in association information according to claim 1, characterized in that: When the hotel service request is a room equipment control request, the backend system determines the equipment capability model corresponding to the target space based on the unified check-in association information, and converts the unified control command issued by the terminal device into a protocol command that can be recognized by the guest room control gateway before sending it to the corresponding room equipment. The device capability model includes one or more of the following: device type, device instance identifier, operable actions, parameter range, scene mode mapping, and exception reporting code.

6. The hotel AI service control method based on check-in association information according to claim 1, characterized in that: When the hotel service request is a check-out request, the backend system first queries one or more of the following: bill status, deposit status, incomplete service status, delivery status, and delayed check-out status. After the check-out settlement conditions are met, the back-end system generates a check-out confirmation and sequentially performs one or more of the following actions: freezing new requests, invalidating door lock permissions, invalidating in-room device control permissions, invalidating service call permissions, clearing local bound credentials, and updating room status.

7. A hotel AI service control system based on check-in association information, characterized in that, include: The binding management module is used to generate a dynamic binding certificate based on the check-in record after the guest completes check-in. The dynamic binding certificate is associated with the check-in identifier, target space identifier, check-in time window and service permission set corresponding to this check-in, and is used to receive binding requests submitted by terminal devices. The device authentication module is used to verify the device identifier and device authentication information in the binding request; The association information management module is used to establish unified check-in association information corresponding to this check-in after the dynamic binding credential and the device authentication information are verified. The unified check-in association information includes at least check-in identifier, target space identifier, check-in time window, terminal device identifier, permission scope and status information. A unified service gateway is used to receive hotel service requests initiated by terminal devices within the validity period of the unified check-in association information, and to perform permission verification and service routing on the hotel service requests based on the unified check-in association information. The service orchestration module is used to call the corresponding hotel business subsystem to execute the corresponding service based on the business routing result; The permission cancellation module is used to invalidate the dynamic binding certificate when the preset invalidation conditions are met, and to uniformly reclaim the door lock permissions, in-room equipment control permissions and service call permissions associated with this check-in based on the unified check-in association information. The hotel business subsystem includes at least one or more of the following: door lock system, guest room control system, guest room service system, catering system, reminder service system, or check-out processing system.

8. A hotel AI service control system based on check-in association information according to claim 7, characterized in that: The system also includes a reminder event engine, which is used to send reminder information to the corresponding bound terminal device based on events such as dining benefits, takeout arrival, wake-up call reservation, delivery completion, or room service status change, combined with the target space identifier, terminal device identifier, role level, service status, and trigger time window in the unified check-in association information, and to route the subsequent operations initiated by the terminal device in response to the reminder information to the corresponding hotel business subsystem.

9. A terminal device, characterized in that, Includes a processor, a memory, a communication module, and a computer program stored in the memory and executable by the processor; When the computer program is executed by the processor, the terminal device performs the following steps: Obtain the dynamic binding credential generated by the backend system based on the guest check-in record; Submit the device identifier, device authentication information, and the credential identifier corresponding to the dynamically bound credential to the backend system in order to request the establishment of unified check-in association information corresponding to this check-in; After the unified check-in association information is established, the session state and / or permission token associated with the unified check-in association information are saved; During the validity period of the unified check-in association information, a hotel service request is initiated to the backend system through the unified service portal, and the hotel service request is associated with the unified check-in association information; Receive service execution results, status synchronization information, or permission expiration information returned by the backend system; Upon receiving a permission expiration message or detecting an expiration of locally bound credentials, clear or invalidate the locally stored binding information, session state, and / or permission tokens.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the hotel check-in association information binding and unified service control method based on terminal devices as described in claim 1.

Images