A conference room reservation method, device and equipment based on a message queue

Abstract

The application discloses a conference room reservation method and device based on a message queue, and equipment, the method comprises the following steps: receiving a conference room reservation request sent by a user terminal; querying the conference room state according to the conference room reservation request, generating a reservation record, and the reservation record containing a temporary door opening password; sending a control message to the message queue based on the reservation record, the control message being used for instructing the access control system and the conference equipment to execute an operation; receiving an execution result feedback returned by the message queue, the execution result feedback being generated by the message queue collecting the execution state of the access control system and the conference equipment; generating a user notification message based on the execution result feedback and the temporary door opening password, and sending the user notification message to the message queue so as to push the user notification message to the user terminal. The application can solve the problems that in the related art, the conference equipment and the access control are poor in linkage during the conference room reservation process, the execution state cannot be fed back in real time, information notification is inaccurate, and the system modules are high in coupling degree, thereby causing insufficient stability.

Description

Technical Field

[0001] This application relates to the field of conference room management technology, and in particular to a conference room booking method, apparatus and equipment based on message queues. Background Technology

[0002] As enterprises accelerate their digital transformation of office operations, meeting rooms, as a core collaborative resource, are evolving from traditional manual management to digital systems. Currently, mainstream meeting room booking technologies fall into three main categories: The first is basic digital management systems, built on a front-end / back-end separated architecture using technologies such as Spring Boot and Vue. These systems provide core functions like meeting room information display, online booking, and approval management, supporting filtering by capacity, equipment, and floor. Booking data is stored in MySQL, with some systems incorporating Redis caching to improve response speed. The second category consists of simple collaboration tools, including shared Excel spreadsheets and embedded modules in enterprise OA systems. These only fulfill basic booking record functions and rely on manual information synchronization. The third category is rudimentary intelligent systems, some of which integrate conflict detection and equipment status marking functions, supporting the generation of electronic vouchers for check-in, but lacking fully intelligent workflow integration.

[0003] In terms of technical architecture, existing systems mostly adopt a synchronous processing mode, with direct coupling and calls between various functional modules (reservation module, device management module, and notification module). Some systems have attempted to introduce message queues (such as RabbitMQ) to achieve simple notification pushes, but have not fully utilized their core advantages of asynchronous processing and decoupling. In terms of application scenarios, the core positioning of existing technologies is focused on the digitization of the reservation process and the visualization of resources, but intelligent decision-making and cross-terminal collaboration capabilities are still insufficient.

[0004] Although existing technologies have overcome the limitations of traditional manual management, there are still many drawbacks in practical applications, such as: 1. Frequent booking conflicts and inefficient resolution: Traditional systems rely on "first-come, first-served" rules or manual coordination, and conflict detection is limited to basic time period verification, lacking intelligent alternatives. Cross-departmental conflict handling is time-consuming; some systems lack conflict early warning mechanisms, causing users to find that the meeting room is occupied only after arriving on site.

[0005] 2. Insufficient multi-terminal adaptation and cumbersome operation: Most systems only support web-based booking, with poor mobile adaptation. The integration of mini-programs for frequently used office tools such as WeChat and DingTalk is lacking, requiring users to switch between multiple platforms, resulting in low booking efficiency.

[0006] 3. Poor integration between equipment and access control: The conference room access control, projector, video conferencing system and other equipment operate independently, requiring manual debugging or additional verification. Equipment failure status cannot be synchronized in real time, resulting in meeting delays. The access control is disconnected from the reservation system, requiring attendees to contact the administrator to open the door, resulting in a poor experience.

[0007] 4. Information delivery is untimely and incomplete: Meeting notices are mostly sent through a single channel, lacking a pre-meeting reminder mechanism, and the probability of participants missing the meeting is relatively high; the usage status of meeting rooms (current meeting, meeting about to start) is not displayed on-site, resulting in a common phenomenon of resource mismatch (crowded small meeting rooms and idle large meeting rooms).

[0008] 5. Insufficient system stability due to module coupling: Existing systems mostly adopt synchronous call architecture. If the notification service or device management module fails, the entire reservation system will crash, resulting in poor fault tolerance. Summary of the Invention

[0009] This application provides a message queue-based meeting room booking method, apparatus, and equipment to solve the problems in related technologies, such as poor linkage between meeting equipment and access control during the meeting room booking process, inaccurate information notifications due to the inability to provide real-time feedback on execution status, and insufficient stability due to high coupling of system modules.

[0010] In a first aspect, embodiments of this application provide a meeting room booking method based on a message queue, which includes: Receive meeting room reservation requests sent by user terminals; Based on the meeting room reservation request, query the meeting room status and generate a reservation record, which includes a temporary door opening password; Based on the reservation record, a control message is sent to the message queue, the control message being used to instruct the access control system and conference equipment to perform operations; The system receives execution result feedback returned by the message queue, which is generated by the message queue collecting the execution status of the access control system and the conference equipment. Based on the execution result feedback and the temporary door opening password, a user notification message is generated and sent to the message queue so that it can be pushed to the user terminal.

[0011] In conjunction with the first aspect, in one implementation, the step of querying the meeting room status based on the meeting room reservation request and generating a reservation record includes: Search for available meeting rooms that match the meeting room booking request; If the number of available meeting rooms is greater than zero, select the target meeting room from the available meeting rooms to generate the reservation record; If the number of available meeting rooms is zero, execute the conflict resolution process.

[0012] In conjunction with the first aspect, in one implementation, the step of selecting a target meeting room from the available meeting rooms to generate the reservation record includes: If the number of available meeting rooms is less than or equal to the preset recommended number, a list of recommended meeting rooms will be generated from all available meeting rooms and sent to the user terminal. If the number of available meeting rooms is greater than the preset recommended number, select the preset recommended number of available meeting rooms based on the scoring results to generate the recommended meeting room list, and send it to the user terminal; The system receives a selection instruction from the user terminal based on the recommended meeting room list, determines the target meeting room according to the selection instruction, and generates the reservation record.

[0013] In conjunction with the first aspect, in one implementation, selecting the preset recommended number of idle meeting rooms based on the scoring results includes: The idle meeting rooms are scored based on at least one of the following: equipment matching degree, historical preference, and meeting room utilization rate; The idle meeting rooms are sorted according to the rating results, and the number of idle meeting rooms with the highest ratings are selected according to the preset recommendation.

[0014] In conjunction with the first aspect, in one implementation, the execution of the conflict handling process includes: An alternative meeting room plan is generated and sent to the user terminal. The alternative meeting room plan includes information on available meeting rooms of the same size and time period during the same time period, as well as information on available time periods of meeting rooms that conflict with the meeting room booking request in similar time periods. Upon receiving a solution confirmation instruction from the user terminal, if the solution confirmation instruction indicates that the alternative meeting room solution is not accepted, a priority arbitration process is executed.

[0015] In conjunction with the first aspect, in one implementation, the execution priority arbitration process includes: Compare the priority identifier of the meeting room booking request with the priority identifier of the existing booking record corresponding to the conflicting meeting room; If the priority identifier of the meeting room booking request is higher than the priority identifier of the existing booking record, the conflicting meeting room is assigned to the meeting room booking request, the status of the existing booking record is updated to canceled, and the booking record is generated.

[0016] In conjunction with the first aspect, in one embodiment, the method further includes: if the priority identifier of the meeting room booking request is not higher than the priority identifier of the existing booking record, generating a conflict notification message, the conflict notification message including alternative meeting room options; And / or, the method further includes: generating an original booking cancellation notification and sending it to the message queue so as to push it to the user terminal corresponding to the existing booking record.

[0017] In conjunction with the first aspect, in one implementation, the execution result feedback includes at least one of an access control authorization success status and a conference equipment startup ready status; the step of generating a user notification message based on the execution result feedback and the temporary door opening password includes: if the execution result feedback indicates that the access control authorization success status is successful and the conference equipment startup ready status is ready, generating a success notification message containing the temporary door opening password; if the execution result feedback indicates that the access control authorization success status is failed or the conference equipment startup ready status is failed, generating a maintenance alarm message and sending it to the management terminal; And / or, the method further includes: updating the conference device status cache in the database and the effective status of the temporary door opening password based on the execution result feedback; And / or, receiving the meeting room booking request sent by the user terminal includes: receiving the original request from different office collaboration platforms, mapping the user identifiers of different platforms to a unified user identifier, and generating the meeting room booking request; And / or, the control message includes a device startup time, which is a preset duration prior to the meeting start time; And / or, the control message is also used to instruct the electronic display screen to display meeting information, and the execution result feedback also includes the display update status of the electronic display screen; And / or, the user notification message is pushed to the user terminal via at least one of the following channels: SMS, instant messaging application, or email; And / or, the temporary door opening password includes a valid time period, which begins with a first preset duration before the meeting start time and ends with a second preset duration after the meeting end time; And / or, generating user notification messages includes: generating reminder notification messages containing the temporary door opening password at multiple preset time points before the start of the meeting; And / or, the meeting room booking request includes the meeting time slot, meeting topic, number of participants, priority identifier, and equipment requirement tag; And / or, sending control messages to the message queue based on the reservation record includes: publishing a message instructing the access control system to perform an operation to a first topic; and publishing a message instructing the conferencing equipment to perform an operation to a second topic; And / or, the method further includes: sending a resource release message to the message queue after the meeting end time has elapsed, so that the access control system and the meeting equipment can return to their initial state.

[0018] Secondly, embodiments of this application provide a meeting room reservation device based on a message queue, comprising: The request receiving module is used to receive meeting room reservation requests sent by user terminals; The record generation module is used to query the meeting room status based on the meeting room reservation request and generate a reservation record, which includes a temporary door opening password. The message sending module is used to send control messages to the message queue based on the reservation record. The control messages are used to instruct the access control system and the conference equipment to perform operations. The feedback receiving module is used to receive the execution result feedback returned by the message queue. The execution result feedback is generated by the message queue collecting the execution status of the access control system and the conference equipment. The notification generation module is used to generate a user notification message based on the execution result feedback and the temporary door opening password, and send it to the message queue so as to push it to the user terminal.

[0019] Thirdly, embodiments of this application provide a message queue-based meeting room booking device, including a processor, a memory, and a message queue-based meeting room booking program stored in the memory and executable by the processor, wherein when the message queue-based meeting room booking program is executed by the processor, it implements the steps of the message queue-based meeting room booking method as described in any of the preceding claims.

[0020] The beneficial effects of the technical solution provided in this application include: This application provides a meeting room reservation method, apparatus, and device based on a message queue. By sending control messages to the message queue based on reservation records, the asynchronous transmission mechanism of the message queue isolates the reservation processing logic from the distribution of operation instructions for the access control system and meeting equipment, avoiding synchronous calls that block the main process. It also receives execution result feedback collected by the message queue, constructs trigger conditions for the generation of device execution status and user notification messages, generates user notification messages based on execution result feedback and temporary door opening passwords, and sends them to the message queue for push to the user terminal. This achieves dynamic dependence of notification content on the actual execution status of the device and decoupling of communication between the reservation module and the device management module, reducing the impact of single-module failures on the overall system, ensuring the reliability of information transmission, and solving problems such as poor linkage between meeting equipment and access control, inaccurate information notifications due to the inability to provide real-time feedback on execution status, and insufficient stability due to high system module coupling. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating an embodiment of the meeting room booking method based on message queues in this application; Figure 2 This is a schematic diagram of the functional modules of an embodiment of the message queue-based meeting room reservation device of this application; Figure 3 This is a schematic diagram of the hardware structure of a meeting room reservation device based on a message queue, as described in the embodiments of this application. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] In a first aspect, embodiments of this application provide a meeting room booking method based on message queues.

[0025] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the meeting room booking method based on message queues according to this application. Figure 1 As shown, the meeting room booking method based on message queues includes: S101: Receives a meeting room reservation request sent by a user terminal.

[0026] Users can send meeting room booking requests via smartphones, tablets, or office computers. The booking request includes the meeting time slot, meeting topic, number of participants, equipment requirement tags, and priority identifier. The priority identifier is used to compare with other booking records in the subsequent conflict resolution process to determine resource allocation authority.

[0027] For example, when a user clicks to book through a WeChat mini-program, the user's terminal generates a meeting room booking request. This request includes the meeting topic "Project Review Meeting," the number of attendees (10), the meeting time slot (October 27, 2023, 14:00-15:00), the equipment requirement tag "Projector," and the priority identifier "Level 2 - Department Meeting." After receiving the request, the server parses the above parameters for subsequent processing.

[0028] S102: Query the meeting room status according to the meeting room reservation request, generate a reservation record, and the reservation record includes a temporary door opening password.

[0029] It should be noted that the reservation record in this embodiment is a structured data object stored in the server database, used to uniquely identify a meeting room reservation. In addition to the temporary door opening password, the reservation record also includes: reservation identifier, user identifier, meeting room identifier, meeting start time, meeting end time, priority identifier, and reservation status.

[0030] It should be noted that the server maintains meeting room resources and stores all meeting room reservation records. For any given time period, if a corresponding reservation record exists in the database, the meeting room is considered occupied, forming an existing reservation record; otherwise, it is considered idle and marked as an unoccupied meeting room. When a new reservation record is generated, the server writes it to the database, updating the meeting room's occupancy status so that it becomes an existing reservation record in subsequent queries. This embodiment ensures the accuracy of meeting room status queries through centralized storage and real-time updates of reservation records, provides a data foundation for conflict detection, avoids duplicate reservations caused by status synchronization delays, and improves the consistency of resource management.

[0031] The priority identifier is stored in association with the reservation record for comparison with the priority identifier of existing reservation records in subsequent steps. The temporary access password is stored in association with the reservation identifier for verification by the access control system within a valid time period before the meeting start time. The user identifier is used to associate with the user terminal that initiated the reservation. The meeting room identifier is used to associate with a specific physical meeting room resource. The reservation status indicates whether the current reservation is confirmed, canceled, or completed. Through this data structure, the server can bind access control permissions, device control commands, and specific reservation behaviors, ensuring that control messages sent based on the reservation record in subsequent steps accurately target the specific meeting room and time period.

[0032] For example, the server queries the database and confirms that meeting room 301 is available from 14:00 to 15:00 on October 27, 2023, and generates a reservation record. This reservation record includes the reservation identifier "B20231027001", user identifier "U1001", meeting room identifier "301", meeting start time "14:00", meeting end time "15:00", priority identifier "Level 2 - Department Meeting", reservation status "Confirmed", and a randomly generated temporary door access password "889900".

[0033] S103: Send a control message to the message queue based on the reservation record. The control message is used to instruct the access control system and conference equipment to perform operations.

[0034] The conference equipment includes projectors, video conferencing systems, etc.

[0035] For example, the server publishes a control message containing the temporary door opening password "889900" and the device startup command to the "Device_Control" topic in the message queue. The message queue routes this message to the access control system and the projector control system, instructing them to perform door opening authorization and device warm-up operations 10 minutes before the meeting starts, without the server directly calling the hardware interface.

[0036] S104: Receive the execution result feedback returned by the message queue, the execution result feedback being generated by the message queue collecting the execution status of the access control system and the conference equipment.

[0037] For example, the access control system returns an "authorization successful" status, the projector returns a "ready" status, and the message queue collects these execution statuses to generate execution result feedback. The server subscribes to the "Feedback" topic of the message queue, receives the feedback, and thus knows whether the access control system and conference equipment have completed the preparation work as instructed, rather than waiting blindly.

[0038] S105: Generate a user notification message based on the execution result feedback and the temporary door opening password, and send it to the message queue so as to push it to the user terminal.

[0039] For example, if the execution result indicates that the device is ready, the server generates a user notification message containing a temporary door access code "889900" and the location of the meeting room, and sends it to the "Notify" notification subject in the message queue. The message queue then sends the notification to the user's terminal via SMS or app push notifications, ensuring that the user only receives the door access code when the device is available, thus avoiding invalid notifications.

[0040] In this embodiment, control messages are sent to the message queue based on reservation records. The asynchronous transmission mechanism of the message queue isolates the reservation processing logic from the operation instructions of the access control system and conference equipment, avoiding synchronous calls from blocking the main process. The execution result feedback collected by the message queue is received, and the trigger conditions for the generation of device execution status and user notification messages are constructed. User notification messages are generated based on the execution result feedback and temporary door opening password and sent to the message queue for push to the user terminal. This realizes the dynamic dependence of the notification content on the actual execution status of the device and the decoupling of communication between the reservation module and the device management module. It reduces the impact of a single module failure on the overall system, ensures the reliability of information transmission, and solves the problems of poor linkage between conference equipment and access control, inaccurate information notification due to the inability to provide real-time feedback on execution status, and insufficient stability due to high coupling of system modules.

[0041] Furthermore, in one embodiment, the step of querying the meeting room status based on the meeting room reservation request and generating a reservation record includes: S201: Query available meeting rooms that match the meeting room booking request.

[0042] For example, the server parses a meeting room booking request and finds that the desired time slot is 14:00-15:00, the number of attendees is 10, and the equipment requirement is a projector. The server then compares these conditions with all meeting room booking records in the database and filters out meeting rooms that are not booked within that time slot, have a capacity of more than 10 people, and are equipped with a projector.

[0043] S202: If the number of available meeting rooms is greater than zero, select a target meeting room from the available meeting rooms to generate the reservation record; if the number of available meeting rooms is zero, execute the conflict handling process.

[0044] For example, assuming there are 5 meeting rooms that meet the requirements and are not occupied, these 5 meeting rooms are marked as available meeting rooms, forming an available meeting room list. A meeting room is selected from these 5 available meeting rooms as the target meeting room to generate the reservation record, which includes a temporary access password. If the available meeting room list is empty, meaning all eligible meeting rooms have been booked, the server determines that there is a resource conflict and executes a conflict resolution process, such as pushing alternative solutions to the user or initiating priority arbitration, to resolve the issue of not being able to book directly and ensure that the user's request is responded to.

[0045] Furthermore, in one embodiment, the step of selecting the target meeting room from the available meeting rooms to generate the reservation record includes: S301: If the number of idle meeting rooms is less than or equal to the preset recommended number, generate a recommended meeting room list from all the idle meeting rooms and send it to the user terminal; if the number of idle meeting rooms is greater than the preset recommended number, select the preset recommended number of idle meeting rooms according to the scoring results to generate the recommended meeting room list and send it to the user terminal.

[0046] The preset recommended number can be set according to actual needs.

[0047] For example, the preset number of recommendations is set to 5. If 3 available meeting rooms are selected, the server generates a list of recommended meeting rooms with all information for these 3 rooms and sends it to the user's terminal for selection. If 10 available meeting rooms are selected, the server selects the 5 highest-scoring meeting rooms based on the rating results and generates a list of recommended meeting rooms, which is then sent to the user's terminal. This avoids an excessively long list that makes it difficult for users to choose, while ensuring the quality of the recommendations.

[0048] S302: Receive the selection instruction returned by the user terminal based on the recommended meeting room list, determine the target meeting room according to the selection instruction, and generate the reservation record.

[0049] For example, after viewing the list of recommended meeting rooms on their user terminal, a user clicks on one of the meeting rooms to confirm a reservation. The user terminal generates a selection command and sends it to the server. The server receives this selection command, designates the user-selected meeting room as the target meeting room, and generates a reservation record including a temporary door access code based on the meeting time slot. This process gives the final decision-making power to the user, ensuring that the reservation result meets the user's expectations and reducing the problem of decreased satisfaction caused by automatic allocation by the system.

[0050] In this embodiment, a list of recommended meeting rooms is generated based on the comparison between the number of available meeting rooms and the preset recommended number. The target meeting room is then determined by combining the selection instructions returned by the user terminal. This achieves the synergy between intelligent system filtering and user self-decision-making, avoids selection difficulties caused by overload of candidate information, ensures the accuracy of reservation record generation, and improves reservation efficiency and user satisfaction.

[0051] Further, in one embodiment, selecting the preset recommended number of idle meeting rooms based on the scoring results includes: S401: The idle meeting room is scored based on at least one of equipment matching degree, historical preference degree and meeting room utilization rate.

[0052] As an example, device compatibility score The following formula can be used for calculation:

[0053] in, This indicates the total number of meeting equipment requirement tags in the meeting room booking request. This score indicates the number of meeting equipment items in the available meeting rooms that match the meeting equipment requirement tag in the meeting room booking request. The score reflects the percentage of meeting equipment requirements met; a higher score indicates a more complete match.

[0054] For example, if a user requests "projector" and "video conferencing", then =2, if a meeting room only has a "projector", then =1, =50.

[0055] Historical preference rating The following formula can be used for calculation:

[0056] in, This indicates the number of times the available meeting room has been booked by the current user within a preset historical period. This represents the number of times the meeting room has been booked most frequently by the current user within the preset historical period. This formula is used for normalization to ensure the score is between 0 and 100. The preset historical period can be set according to actual needs.

[0057] For example, the preset historical period is the past 3 months. The following statistics are compiled based on the current user's booking history within this period: 5 bookings for meeting room 301, 10 bookings for meeting room 302, and 2 bookings for meeting room 303. When calculating the historical preference score for meeting room 301... The number of reservations for meeting room 301 was 5. The maximum number of bookings across all meeting rooms, 10 (from meeting room 302), is used as the base score in the formula, resulting in a score of 50. When calculating the historical preference score for meeting room 302... For 10 times, The score remains at 10 times, with a total score of 100. When calculating the historical preference score for Conference Room 303, For 2 times, The number of bookings remains at 10, with a score of 20. This calculation normalizes the number of bookings for different meeting rooms to a standard score of 0-100, eliminating the impact of differences in the total frequency of user bookings.

[0058] In addition, historical preference rating The calculation can also be performed using the following formula:

[0059] This represents the total number of times all meeting rooms have been booked by the current user within the preset historical period. For example, still using the above example of booking meeting room 301 5 times, meeting room 302 10 times, and meeting room 303 2 times, in this case... =17.

[0060] Meeting room utilization rate score The following formula can be used for calculation:

[0061] in, This indicates the occupancy rate of the idle meeting rooms during a preset statistical period, with a value ranging from 0 to 1. The lower the occupancy rate, the higher the score for this item, in order to encourage the balanced use of resources. The preset statistical period can be set according to actual needs.

[0062] The time slot occupancy rate is defined as the ratio of the booked time to the total open time of the idle meeting room within a preset statistical period. For example, if a meeting room is open for a total of 40 hours per week and 20 hours have been booked, then... =0.5.

[0063] The overall score is obtained by combining all the scores. :

[0064] in, + + =1, , , The preset weighting coefficients can be set according to actual needs, for example... =0.4, =0.3, =0.3.

[0065] The server calculates a comprehensive score by weighting the three scores, quantifying the recommendation priority of each idle meeting room, and providing a data foundation for subsequent ranking.

[0066] S402: Sort the idle meeting rooms according to the rating results, and select the number of idle meeting rooms with the highest ratings according to the preset recommendation.

[0067] For example, the default number of recommendations is 5. The server sorts 10 available meeting rooms from highest to lowest based on their overall rating, and selects the top 5 to generate a recommended meeting room list. If meeting room 301 has the highest rating, it is placed at the top of the list. This list is sent to the user's terminal to ensure that the user sees the most suitable meeting room first, reducing the user's filtering time, improving the booking experience, and balancing the load on meeting room resources.

[0068] In this embodiment, by scoring and ranking idle meeting rooms from multiple dimensions, a quantitative assessment of resources is achieved. Based on the scoring results, a preset number of idle meeting rooms are selected for recommendation, avoiding the problem of low matching caused by random recommendations, ensuring the quality of the recommended meeting room list, and improving user booking efficiency and meeting room resource utilization.

[0069] Furthermore, in one embodiment, the execution of the conflict handling process includes: S501: Generate an alternative meeting room plan and send it to the user terminal. The alternative meeting room plan includes information on available meeting rooms of the same specifications within the same time period and information on available time slots of meeting rooms that conflict with the meeting room booking request within a similar time period.

[0070] For example, the server detects a conflict between the user's requested meeting room 301 and the scheduled time slot of 14:00-15:00. The server then searches for available meeting rooms of the same specifications with projectors during the same time slot, such as meeting room 302. Simultaneously, it finds that meeting room 301 is available during either 13:00-14:00 or 15:00-16:00. The server integrates the information from meeting room 302 and the availability information from meeting room 301 into an alternative meeting room plan and sends it to the user's terminal. This provides the user with multiple options for changing rooms or times, avoiding direct conflicts that could lead to booking failures.

[0071] S502: Receive the solution confirmation instruction returned by the user terminal. If the solution confirmation instruction indicates that the alternative meeting room solution is not accepted, execute the priority arbitration process.

[0072] For example, after viewing alternative meeting room options on their user terminal, if a user agrees to change the meeting room or time slot, they can select the desired option and click "Confirm".

[0073] If the user is not satisfied with the room or time change options, they can click the "Dissatisfied" button. The user's terminal generates a confirmation instruction indicating that the option is not accepted and sends it to the server. Upon receiving the confirmation instruction, the server parses the user's intention to refuse and then triggers a priority arbitration process.

[0074] In this embodiment, by generating alternative meeting room options that include information on changing rooms or times, and executing a priority arbitration process when the user does not accept the alternative, a tiered approach to conflict resolution is achieved. This avoids resource disruption caused by direct arbitration, ensures resource availability for high-priority meetings, solves the problem of frequent and inefficient booking conflicts, and improves meeting room resource scheduling efficiency and user satisfaction.

[0075] Furthermore, in one embodiment, the execution priority arbitration process includes: S601: Compare the priority identifier of the meeting room reservation request with the priority identifier of the existing reservation record corresponding to the conflicting meeting room.

[0076] For example, the server extracts the priority identifier "Level 2 - Department Meeting" from the meeting room booking request and queries the existing booking record for the conflicting meeting room, which has a priority identifier "Level 1 - Regular Meeting". The server compares the two values ​​and confirms that Level 2 is higher than Level 1. If both are Level 1, it is determined that they are not higher. This step, by quantifying the priority identifier, provides a clear basis for determining whether to perform preemption, avoiding the subjectivity of manual coordination and ensuring the certainty of the arbitration logic.

[0077] S602: If the priority identifier of the meeting room booking request is higher than the priority identifier of the existing booking record, the conflicting meeting room is assigned to the meeting room booking request, the status of the existing booking record is updated to canceled, and the booking record is generated; if the priority identifier of the meeting room booking request is not higher than the priority identifier of the existing booking record, a conflict notification message is generated, and the conflict notification message includes alternative meeting room options.

[0078] For example, if the priority indicator is higher than an existing record, the server assigns the conflicting meeting room to the current request, generates a booking record, updates the status of the existing booking record to canceled, and triggers a notification to the original user. If the priority indicator is not higher than an existing record, the server generates a conflict alert message, which includes the previously generated alternative meeting room options, and sends it to the user's terminal. This step enables automated resource reallocation based on priority or guides users to choose alternatives, ensuring high-priority meeting resources while also considering the backup needs of low-priority users.

[0079] In this embodiment, by comparing priority identifiers and performing conflict room allocation or generating conflict alert messages based on the comparison results, automated arbitration and dynamic adjustment of meeting resources are achieved. This avoids the time-consuming drawbacks of traditional manual coordination, ensures resource acquisition for high-priority meetings, solves the problem of frequent and inefficient booking conflicts, and improves the efficiency of meeting room resource scheduling and the level of system automation.

[0080] Furthermore, in one embodiment, the method further includes: generating an original booking cancellation notification and sending it to the message queue so as to push it to the user terminal corresponding to the existing booking record.

[0081] For example, if priority arbitration updates the status of an existing booking record to "cancelled," the server generates the original booking cancellation notification and sends it to the message queue. The message queue uses the user identifier associated with the existing booking record to locate the user's terminal and pushes the notification. This ensures the original user is promptly informed of the change, preventing them from arriving at the meeting room on time only to find it unusable, thus improving the user experience.

[0082] In this embodiment, an asynchronous notification of cancellation is achieved by generating the original booking cancellation notification and sending it to a message queue. The message queue's reliable delivery mechanism then pushes the notification to the user's terminal. This ensures that users with original bookings are promptly informed of meeting changes, avoids resource waste, and improves system service reliability and user satisfaction.

[0083] Further, in one embodiment, the execution result feedback includes at least one of the access control authorization success status and the conference equipment startup ready status; the step of generating a user notification message based on the execution result feedback and the temporary door opening password includes: if the execution result feedback indicates that the access control authorization success status is successful and the conference equipment startup ready status is ready, generating a success notification message containing the temporary door opening password; if the execution result feedback indicates that the access control authorization success status is failed or the conference equipment startup ready status is failed, generating a maintenance alarm message and sending it to the management terminal.

[0084] This embodiment dynamically generates messages based on execution result feedback, ensuring that the notification content reflects the actual status of the equipment, avoiding the inability of users to enter due to equipment failure, and improving system reliability and user meeting experience.

[0085] Furthermore, in one embodiment, the method further includes: updating the conference device status cache in the database and the validity status of the temporary door opening password based on the execution result feedback. Specifically, the conference device status cache is updated to a cache database such as a Redis database, and the reservation record is updated to a relational database such as a MySQL database.

[0086] For example, if the execution result indicates successful access authorization, the server updates the device status cache in the database to "ready" and marks the temporary access password as "valid." If the feedback indicates failure, the device status cache is updated to "faulty," and the password status is marked as "invalid." Synchronously updating the conference device status cache and password validity status ensures consistency between system records and the actual physical device status, preventing users from being unable to open doors despite possessing valid passwords, thus improving the accuracy of system data and the reliability of access control.

[0087] Furthermore, in one embodiment, receiving the meeting room booking request sent by the user terminal includes: receiving original requests from different office collaboration platforms, mapping the user identifiers of different platforms to a unified user identifier, and generating the meeting room booking request.

[0088] For example, the server receives raw requests from office collaboration platforms such as web-based management platforms, mobile apps (iOS / Android), WeChat mini-programs, and DingTalk mini-programs. Upon initial registration or login, the server requires the user to verify their mobile phone number. The server maintains a user identifier mapping table, which stores the correspondence between platform type, platform user identifier, verification mobile phone number, and unified user identifier.

[0089] Specifically, when the system detects that the original WeChat request carries the user identifier "wx_openid_12345" and the verified mobile number is "13800000000", it generates a unified user identifier "U1001" and stores the association. When a subsequent DingTalk request is received carrying the user identifier "ding_user_67890" and the verified mobile number is also "13800000000", the server queries the mapping table and identifies that the mobile number is associated with the unified user identifier "U1001", thus mapping "ding_user_67890" to "U1001". This embodiment establishes multi-platform account associations using mobile phone numbers as a common unique identifier, eliminating differences in account systems across different office collaboration platforms, ensuring the accuracy of user identification, avoiding duplicate registrations on different platforms, and improving multi-terminal adaptability and booking efficiency.

[0090] Data is synchronized in real time across all user terminals, allowing users to complete reservations, view meeting room status, and receive notifications and reminders through any user terminal.

[0091] Furthermore, in one embodiment, the control message includes a device startup time, which is a preset duration preceding the meeting start time. The preset duration can be set according to actual needs.

[0092] For example, if the meeting starts at 14:00 and the preset duration is 10 minutes, the server will include the device startup time of 13:50 in the control message. Upon receiving this message, the meeting devices will automatically start at 13:50. This embodiment, by starting the meeting devices in advance with a preset time, ensures that the devices are ready when the user arrives, avoiding debugging delays after the meeting starts. It also prevents energy waste caused by premature device startup, improving meeting preparation efficiency and the level of intelligence in meeting device management.

[0093] Furthermore, in one embodiment, the control message is also used to instruct the electronic display screen to display conference information, and the execution result feedback also includes the display update status of the electronic display screen.

[0094] For example, an electronic display screen can be deployed at the entrance of a conference room. The server sends conference information, including it in a control message, to a message queue, which then forwards it to the electronic display screen at the conference room entrance. After updating its content, the electronic display screen returns an update status to the message queue. The server receives this status confirmation information and displays the information synchronously. This embodiment achieves on-site visualization of the conference room status through electronic display screen display and status feedback. Participants can intuitively confirm the situation, avoid accidental entry, and improve resource utilization and transparency.

[0095] The meeting information can include the current meeting topic, number of participants, end time, as well as the reservation information and start time of the next meeting, making the resource status transparent.

[0096] Furthermore, in one embodiment, the user notification message is pushed to the user terminal via at least one of the following channels: SMS, instant messaging applications (such as WeChat Work, DingTalk, etc.), or email.

[0097] Furthermore, in one embodiment, the temporary door opening password includes a valid time period, which begins with a first preset duration before the meeting start time and ends with a second preset duration after the meeting end time. The first and second preset durations can be set according to actual needs.

[0098] For example, the meeting starts at 14:00 and ends at 15:00, with a first preset duration of 10 minutes and a second preset duration of 10 minutes. The temporary access code is valid from 13:50 to 15:10. This embodiment ensures that the password is only valid within a specific time before and after the meeting by setting a valid time period, avoiding the security risks caused by long-term password validity, while reserving a buffer time to facilitate user access, thus improving the security and flexibility of access control.

[0099] Furthermore, in one embodiment, generating user notification messages includes: generating reminder notification messages containing the temporary door opening password at multiple preset time points before the meeting begins. The preset time points can be set according to actual needs.

[0100] For example, preset time points are 24 hours, 1 hour, and 15 minutes before the meeting starts. The server generates reminder notification messages containing temporary access codes and pushes them to the user's terminal at these three time points. This embodiment ensures that participants receive meeting information in a timely manner through multi-time-point reminders, avoiding absences or lateness due to forgetfulness, improving meeting attendance and user experience, and enhancing the reliability of the notification service.

[0101] Furthermore, in one embodiment, sending control messages to the message queue based on the reservation record includes: publishing a message instructing the access control system to perform an operation to a first topic; and publishing a message instructing the conferencing equipment to perform an operation to a second topic.

[0102] For example, the first topic is access control, and the second topic is device control. The server issues an open door command to the first topic and a projector start command to the second topic. This embodiment distributes different types of control messages through different topics, achieving independent processing and decoupling between the access control system and the conference equipment. This avoids congestion in a single topic affecting the execution of other commands, improving the processing efficiency of the message queue and the stability of system operation.

[0103] Furthermore, in one embodiment, the method further includes: sending a resource release message to the message queue after the meeting end time has elapsed, so that the access control system and the meeting equipment can return to their initial state.

[0104] For example, when the meeting ends at 15:00, the server sends a resource release message to the message queue. Upon receiving this message, the access control system and conference equipment shut down or clear temporary permissions, restoring to their initial state. This embodiment achieves automatic resource reclamation and reset after the meeting ends by automatically sending resource release messages. This avoids energy waste caused by prolonged idle operation of equipment, ensures that the conference room is quickly ready for the next meeting, and improves resource utilization.

[0105] Secondly, embodiments of this application also provide a meeting room reservation device based on a message queue.

[0106] In one embodiment, reference is made to Figure 2 , Figure 2 This is a functional module diagram of an embodiment of the meeting room reservation device based on message queues according to this application. Figure 2 As shown, the message queue-based meeting room booking device includes: The request receiving module is used to receive meeting room reservation requests sent by user terminals; The record generation module is used to query the meeting room status based on the meeting room reservation request and generate a reservation record, which includes a temporary door opening password. The message sending module is used to send control messages to the message queue based on the reservation record. The control messages are used to instruct the access control system and the conference equipment to perform operations. The feedback receiving module is used to receive the execution result feedback returned by the message queue. The execution result feedback is generated by the message queue collecting the execution status of the access control system and the conference equipment. The notification generation module is used to generate a user notification message based on the execution result feedback and the temporary door opening password, and send it to the message queue so as to push it to the user terminal.

[0107] Furthermore, in one embodiment, the record generation module queries the meeting room status according to the meeting room reservation request and generates a reservation record, including: querying available meeting rooms that meet the meeting room reservation request; if the number of available meeting rooms is greater than zero, selecting a target meeting room from the available meeting rooms to generate the reservation record; if the number of available meeting rooms is zero, executing a conflict handling process.

[0108] Furthermore, in one embodiment, the record generation module selects a target meeting room from the available meeting rooms to generate the reservation record, including: if the number of available meeting rooms is less than or equal to a preset recommended number, generating a recommended meeting room list from all available meeting rooms and sending it to the user terminal; if the number of available meeting rooms is greater than the preset recommended number, selecting the preset recommended number of available meeting rooms based on the rating results to generate the recommended meeting room list and sending it to the user terminal; receiving a selection instruction returned by the user terminal based on the recommended meeting room list, determining the target meeting room according to the selection instruction, and generating the reservation record.

[0109] Furthermore, in one embodiment, the record generation module selects the preset recommended number of idle meeting rooms based on the scoring results, including: scoring the idle meeting rooms based on at least one of equipment matching degree, historical preference degree, and meeting room utilization rate; sorting the idle meeting rooms according to the scoring results, and selecting the preset recommended number of idle meeting rooms with the highest scores.

[0110] Furthermore, in one embodiment, the record generation module executes a conflict handling process, including: generating an alternative meeting room plan and sending it to the user terminal, wherein the alternative meeting room plan includes information on available meeting rooms of the same specifications within the same time period and information on available time slots of meeting rooms that conflict with the meeting room booking request within a similar time period; receiving a plan confirmation instruction returned by the user terminal, and if the plan confirmation instruction indicates that the alternative meeting room plan is not accepted, executing a priority arbitration process.

[0111] Furthermore, in one embodiment, the record generation module executes a priority arbitration process, including: comparing the priority identifier of the meeting room booking request with the priority identifier of the existing booking record corresponding to the conflicting meeting room; if the priority identifier of the meeting room booking request is higher than the priority identifier of the existing booking record, assigning the conflicting meeting room to the meeting room booking request, updating the status of the existing booking record to canceled, and generating the booking record.

[0112] Furthermore, in one embodiment, the record generation module is also configured to generate a conflict notification message if the priority identifier of the meeting room booking request is not higher than the priority identifier of the existing booking record, the conflict notification message including alternative meeting room options.

[0113] Furthermore, in one embodiment, the record generation module is also used to generate the original booking cancellation notification and send it to the message queue so as to push it to the user terminal corresponding to the existing booking record.

[0114] Furthermore, in one embodiment, the notification generation module generates a user notification message based on the execution result feedback and the temporary door opening password, including: if the execution result feedback indicates that the access control authorization is successful and the conference device is ready, generating a success notification message containing the temporary door opening password; if the execution result feedback indicates that the access control authorization is unsuccessful or the conference device is unsuccessful, generating a maintenance alarm message and sending it to the management terminal.

[0115] Furthermore, in one embodiment, the meeting room reservation device based on the message queue further includes an update module, used to: update the meeting equipment status cache in the database and the effective status of the temporary door opening password according to the execution result feedback.

[0116] Furthermore, in one embodiment, the request receiving module receives a meeting room booking request sent by a user terminal, including: receiving original requests from different office collaboration platforms, mapping user identifiers from different platforms to a unified user identifier, and generating the meeting room booking request.

[0117] Furthermore, in one embodiment, the notification generation module generates user notification messages, including: generating reminder notification messages containing the temporary door opening password at multiple preset time points before the meeting begins.

[0118] Furthermore, in one embodiment, the message sending module sends control messages to the message queue based on the reservation record, including: publishing a message for instructing the access control system to perform an operation to a first topic; and publishing a message for instructing the conferencing equipment to perform an operation to a second topic.

[0119] Furthermore, in one embodiment, the message sending module is also configured to send a resource release message to the message queue after the meeting end time has elapsed, so that the access control system and the meeting equipment can return to their initial state.

[0120] The functions of each module in the above-mentioned message queue-based meeting room booking device correspond to the steps in the above-mentioned message queue-based meeting room booking method embodiment, and their functions and implementation processes will not be described in detail here.

[0121] Thirdly, this application provides a meeting room reservation device based on a message queue. The meeting room reservation device based on a message queue can be a personal computer (PC), a laptop, a server, or other device with data processing capabilities.

[0122] Reference Figure 3 , Figure 3 This is a schematic diagram of the hardware structure of a message queue-based meeting room reservation device involved in an embodiment of this application. In this embodiment, the message queue-based meeting room reservation device may include a processor, a memory, a communication interface, and a communication bus.

[0123] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0124] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting devices within the message queue-based meeting room reservation equipment, as well as interfaces used for interconnecting the message queue-based meeting room reservation equipment with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0125] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0126] The processor can be a general-purpose processor, which can call a message queue-based meeting room booking program stored in memory and execute the message queue-based meeting room booking method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the message queue-based meeting room booking program is called can be referred to in the various embodiments of the message queue-based meeting room booking method of this application, and will not be repeated here.

[0127] Those skilled in the art will understand that Figure 3 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0128] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0129] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0130] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0131] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0132] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0133] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0134] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A meeting room booking method based on message queues, characterized in that, include: Receive meeting room reservation requests sent by user terminals; Based on the meeting room reservation request, query the meeting room status and generate a reservation record, which includes a temporary door opening password; Based on the reservation record, a control message is sent to the message queue, the control message being used to instruct the access control system and conference equipment to perform operations; The system receives execution result feedback returned by the message queue, which is generated by the message queue collecting the execution status of the access control system and the conference equipment. Based on the execution result feedback and the temporary door opening password, a user notification message is generated and sent to the message queue so that it can be pushed to the user terminal.

2. The method according to claim 1, characterized in that, The step of querying the meeting room status based on the meeting room reservation request and generating a reservation record includes: Search for available meeting rooms that match the meeting room booking request; If the number of available meeting rooms is greater than zero, select the target meeting room from the available meeting rooms to generate the reservation record; If the number of available meeting rooms is zero, execute the conflict resolution process.

3. The method according to claim 2, characterized in that, The step of selecting a target meeting room from the available meeting rooms to generate the reservation record includes: If the number of available meeting rooms is less than or equal to the preset recommended number, a list of recommended meeting rooms will be generated from all available meeting rooms and sent to the user terminal. If the number of available meeting rooms is greater than the preset recommended number, select the preset recommended number of available meeting rooms based on the scoring results to generate the recommended meeting room list, and send it to the user terminal; The system receives a selection instruction from the user terminal based on the recommended meeting room list, determines the target meeting room according to the selection instruction, and generates the reservation record.

4. The method according to claim 3, characterized in that, The step of selecting the preset recommended number of idle meeting rooms based on the scoring results includes: The idle meeting rooms are scored based on at least one of the following: equipment matching degree, historical preference, and meeting room utilization rate; The idle meeting rooms are sorted according to the rating results, and the number of idle meeting rooms with the highest ratings are selected according to the preset recommendation.

5. The method according to claim 2, characterized in that, The conflict resolution process includes: An alternative meeting room plan is generated and sent to the user terminal. The alternative meeting room plan includes information on available meeting rooms of the same size and time period during the same time period, as well as information on available time periods of meeting rooms that conflict with the meeting room booking request in similar time periods. Upon receiving a solution confirmation instruction from the user terminal, if the solution confirmation instruction indicates that the alternative meeting room solution is not accepted, a priority arbitration process is executed.

6. The method according to claim 5, characterized in that, The execution priority arbitration process includes: Compare the priority identifier of the meeting room booking request with the priority identifier of the existing booking record corresponding to the conflicting meeting room; If the priority identifier of the meeting room booking request is higher than the priority identifier of the existing booking record, the conflicting meeting room is assigned to the meeting room booking request, the status of the existing booking record is updated to canceled, and the booking record is generated.

7. The method according to claim 6, characterized in that: The method further includes: if the priority identifier of the meeting room booking request is not higher than the priority identifier of the existing booking record, generating a conflict notification message, the conflict notification message containing alternative meeting room options; And / or, the method further includes: generating an original booking cancellation notification and sending it to the message queue so as to push it to the user terminal corresponding to the existing booking record.

8. The method according to claim 1, characterized in that: The execution result feedback includes at least one of the following: access control authorization success status and conference equipment startup ready status; the step of generating a user notification message based on the execution result feedback and the temporary door opening password includes: if the execution result feedback indicates that the access control authorization success status is successful and the conference equipment startup ready status is ready, generating a success notification message containing the temporary door opening password; if the execution result feedback indicates that the access control authorization success status is failed or the conference equipment startup ready status is failed, generating a maintenance alarm message and sending it to the management terminal; And / or, the method further includes: updating the conference device status cache in the database and the effective status of the temporary door opening password based on the execution result feedback; And / or, receiving the meeting room booking request sent by the user terminal includes: receiving the original request from different office collaboration platforms, mapping the user identifiers of different platforms to a unified user identifier, and generating the meeting room booking request; And / or, the control message includes a device startup time, which is a preset duration prior to the meeting start time; And / or, the control message is also used to instruct the electronic display screen to display meeting information, and the execution result feedback also includes the display update status of the electronic display screen; And / or, the user notification message is pushed to the user terminal via at least one of the following channels: SMS, instant messaging application, or email; And / or, the temporary door opening password includes a valid time period, which begins with a first preset duration before the meeting start time and ends with a second preset duration after the meeting end time; And / or, generating user notification messages includes: generating reminder notification messages containing the temporary door opening password at multiple preset time points before the start of the meeting; And / or, the meeting room booking request includes the meeting time slot, meeting topic, number of participants, priority identifier, and equipment requirement tag; And / or, sending control messages to the message queue based on the reservation record includes: publishing a message instructing the access control system to perform an operation to a first topic; and publishing a message instructing the conferencing equipment to perform an operation to a second topic; And / or, the method further includes: sending a resource release message to the message queue after the meeting end time has elapsed, so that the access control system and the meeting equipment can return to their initial state.

9. A meeting room reservation device based on a message queue, characterized in that, include: The request receiving module is used to receive meeting room reservation requests sent by user terminals; The record generation module is used to query the meeting room status based on the meeting room reservation request and generate a reservation record, which includes a temporary door opening password. The message sending module is used to send control messages to the message queue based on the reservation record. The control messages are used to instruct the access control system and the conference equipment to perform operations. The feedback receiving module is used to receive the execution result feedback returned by the message queue. The execution result feedback is generated by the message queue collecting the execution status of the access control system and the conference equipment. The notification generation module is used to generate a user notification message based on the execution result feedback and the temporary door opening password, and send it to the message queue so as to push it to the user terminal.

10. A meeting room reservation device based on a message queue, characterized in that, The system includes a processor, a memory, and a message queue-based meeting room booking program stored in the memory and executable by the processor, wherein when the message queue-based meeting room booking program is executed by the processor, it implements the steps of the message queue-based meeting room booking method as described in any one of claims 1 to 7.

Images