Intelligent kitchen method and system simultaneously supporting cloud and offline pushing

Abstract

The invention relates to the technical field of intelligent kitchen systems, in particular to an intelligent kitchen method and system simultaneously supporting cloud and off-line pushing, and the method comprises the steps: when the system is initialized, a local KDS server automatically activates a UDP broadcast module, and periodically broadcasts a UDP data packet containing service basic information in a local area network; responding to a local order issued by the local POS terminal and / or a cloud order synchronized by the cloud KDS server; and the local KDS server performs preprocessing and merging according to the received local order and the cloud order, performs order splitting according to the demand of the client, integrates processed order data into an order queue corresponding to the client, performs data interaction with the client, pushes the order queue and updates and synchronizes the order state of the order. When the network is normal, data synchronization and pushing are achieved through the cloud, meanwhile, the system has the off-line processing capacity when the network is interrupted, continuous operation of the system and data integrity are ensured, and therefore the stability and efficiency of kitchen work are remarkably improved.

Description

Technical Field

[0001] The present invention relates to the technical field of smart kitchen systems, and in particular to a smart kitchen method and system that supports both cloud and offline push. Background Art

[0002] With the rapid development of the catering industry, smart kitchen systems have become an important tool for improving catering efficiency and service quality. At present, many catering companies are using smart kitchen systems to manage order processing, food preparation and delivery. These smart kitchen systems reduce the need for manual operations through automated processes, significantly speed up service and improve overall customer satisfaction.

[0003] Although smart kitchen systems bring many conveniences, existing technologies also have some limitations: ① Existing smart kitchen systems often rely on stable network connections to operate. Once the network has problems, the system cannot operate normally. This reliance on the network can easily lead to the inability to deliver order information to the kitchen in a timely manner when the network is unstable or interrupted, which greatly reduces the kitchen's operating efficiency and ultimately affects the customer experience waiting to pick up the food.

[0004] ② The existing smart kitchen system lacks effective offline processing capabilities and cannot continue to operate without a network connection, which can easily lead to problems such as data loss and order processing errors. Even if the network is quickly restored, errors in order flow may bring challenges to store operations and management.

[0005] This limitation of reliance on the Internet suggests the need to develop smart kitchen systems that can maintain basic functions even when offline, ensuring that kitchen operations can continue and service quality is not affected even when network connectivity is unavailable. Summary of the invention

[0006] In view of the above problems, the present invention proposes a smart kitchen method and system that supports both cloud and offline push. The system can synchronize and push data through the cloud when the network is normal, and has offline processing capabilities when the network is interrupted, ensuring the continuity of system operation and the integrity of data, thereby improving the stability and efficiency of kitchen operations. In addition, the automated design of the system ensures that no human intervention is required. The above invention object of the present invention is achieved through the following technical solutions: The present invention provides a smart kitchen method that supports both cloud and offline push, including: Step S1: When the system is initialized, the local KDS server automatically activates the UDP broadcast module and periodically broadcasts UDP data packets containing basic service information in the local area network; the UDP data packets are used by the client to automatically connect to the local KDS server for real-time data interaction; Step S2, responding to the local orders issued by the local POS terminal and / or the cloud orders synchronized by the cloud KDS server; wherein, when the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server; when the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronizes it to the local KDS server; the cloud order is the online order data stream; Step S3: The local KDS server pre-processes and merges the received local orders and cloud orders, splits the orders according to the client's needs, integrates the processed order data into the order queue corresponding to the client, interacts with the client through HTTP or Socket interface, pushes the order queue and updates the order status of the synchronized order.

[0007] Furthermore, in step S1, system initialization includes: When the local KDS server is started, the UDP broadcast module is automatically activated to periodically broadcast UDP packets in the LAN so that the client can find the UDP packets. The basic service information in the UDP packet is the service IP address, port number and unique identifier UUID of the local KDS server. After the client is started, it listens to the UDP broadcast in the local area network, captures and parses the basic service information in the UDP data packet, and initiates a request to the local KDS server to establish a connection based on the unique identifier; when the client initiates a connection request, the KDS server starts the connection pool management mechanism and creates a preset number of connections in advance to facilitate timely allocation when the client's request arrives.

[0008] Further, in step S1, when the local KDS server is started, the UDP broadcast terminal is automatically activated, and the UDP data packets are periodically broadcast in the local area network, including: The UDP broadcast module dynamically adjusts the broadcast frequency according to the network status, and periodically broadcasts UDP packets in the LAN to facilitate the client to capture UDP packets; the broadcast frequency has an upper limit and automatically reduces the broadcast frequency to reduce the network burden after the client and the local KDS server establish a connection.

[0009] Furthermore, step S1 also includes: real-time monitoring of the connection status between the local KDS server and the client. When the connection is interrupted or abnormal, the client will listen to the UDP broadcast again to re-establish the connection.

[0010] Further, in step S1, the UDP data packet is used by the client to automatically connect to the local KDS server for real-time data interaction, including: The local KDS server sends the merged order queue to the client via HTTP request; After receiving the order queue, the client performs order operations on the order; The client returns the operation feedback to the local KDS server through the Socket interface to update the order status of the order; When the network status is stable, the local KDS server will synchronize the order status of the updated cloud order to the cloud KDS server.

[0011] Further, in step S2, responding to the local order issued by the local POS terminal includes: The local KDS server obtains the login token from the login module of the local POS terminal to ensure the secure transmission of local order data. The token is a security credential used to verify identity and authority. The timing for obtaining the token includes when the local KDS server is initialized, when the token expires, or when it is pulled at a scheduled time. The local KDS server receives local orders from the local POS. Before receiving the local order, the KDS server verifies the received token to determine the validity of the source. If the token is invalid, it refuses to process and returns an error message. If the token passes the verification, the local order is obtained.

[0012] Further, in step S2, responding to the cloud order synchronized by the cloud KDS server includes: The cloud-based KDS server receives all order data streams and caches the data; The cloud order is synchronized to the local KDS server through the cloud KDS order link. After the synchronization is successful, the cloud KDS server saves a copy of the cloud order in the cache until the local KDS server determines that the cloud order has been processed and clears it; The cloud KDS server monitors the cloud order synchronization process in real time. When it detects that the network status is interrupted or abnormal, it starts the retransmission mechanism to resynchronize the cloud orders.

[0013] Furthermore, in step S2, responding to the cloud order synchronized by the cloud KDS server also includes: When the network status is restored, the local KDS automatically synchronizes and updates the status of all unprocessed or unconfirmed orders, and ensures that the cloud order status is consistent with the order status in the cloud KDS server.

[0014] Further, in step S3, the local KDS server pre-processes and merges the received local orders and cloud orders and splits the orders according to the needs of the client, and integrates the processed order data into the order queue corresponding to the client, including: Receive order data from local orders and cloud orders, and deduplicate cloud orders to ensure the uniqueness of order data; Classify order data, differentiate them according to order source and priority, and split orders according to client needs; integrate the processed order data into a unified order queue, arrange the order queue in chronological order and push it to the corresponding client.

[0015] Based on the same inventive concept, the present invention provides a smart kitchen system that supports both cloud and offline push, which is characterized by comprising: The data initialization module is used when the system is initialized. The local KDS server automatically activates the UDP broadcast module and periodically broadcasts UDP data packets containing basic service information in the local area network. The UDP data packets are used by the client to automatically connect to the local KDS server for real-time data interaction. The data acquisition module is used to respond to local orders issued by the local POS terminal and / or cloud orders synchronized by the cloud KDS server. When the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server. When the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronized to the local KDS server. Cloud orders are online order data streams. The data processing module is used by the local KDS server to pre-process and merge the received local orders and cloud orders, split the orders according to the client's needs, integrate the processed order data into the order queue corresponding to the client, interact with the client through HTTP or Socket interface, push the order queue and update the order status of the synchronized order.

[0016] Compared with the prior art, the present invention has at least one of the following beneficial effects: The present invention realizes data synchronization and push through the cloud when the network is normal, and has offline processing capabilities when the network is interrupted, ensuring the continuous operation of the system and the integrity of the data, thereby significantly improving the stability and efficiency of kitchen operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A flowchart of the steps of the smart kitchen method of the present invention that supports both cloud and offline push; Figure 2 This is an architecture diagram of the smart kitchen system of the present invention that supports both cloud and offline push; Figure 3 This is an activity diagram of the smart kitchen system of the present invention that supports both cloud and offline push. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0019] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present invention refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0020] First embodiment In the context of the rapid development of the catering industry, smart kitchen systems have played an important role in improving catering efficiency and service quality. However, the existing smart kitchen system is overly dependent on stable network connections, and this design exposes significant deficiencies when the network is unstable or interrupted. For example, when the network is interrupted, the system cannot process and push order data to the kitchen display device in a timely manner, resulting in inaccurate understanding of the order to be processed by the kitchen staff, which in turn delays the preparation and delivery of meals, seriously affecting the customer experience. This problem is particularly evident during peak hours and cannot effectively meet the needs of catering services. In addition, the existing system lacks offline processing capabilities, resulting in the system being unable to operate normally in an environment without a network, further increasing dependence on the network and causing risks such as data loss and order processing errors.

[0021] Therefore, the inventor proposed a smart kitchen method that supports both cloud and offline push based on thinking. A cloud KDS order link is added to the local KDS server to connect to the cloud KDS server, effectively integrating local orders and cloud orders to achieve unified requests and operations on the client. At the same time, UDP broadcast technology is used for LAN service discovery to ensure that the client can automatically and reliably discover and connect to the address of the local KDS server, thereby achieving efficient matching connection. The specific implementation method is as follows: The present invention provides a smart kitchen method that supports both cloud and offline push, and aims to provide a smart kitchen method and system that can support both cloud and offline push, ensuring that the kitchen can continue to operate even in the event of a network failure, including: Step S1: When the system is initialized, the local KDS server automatically activates the UDP broadcast module and periodically broadcasts UDP data packets containing basic service information in the local area network; the UDP data packets are used by the client to automatically connect to the local KDS server for real-time data interaction; Step S2, responding to the local orders issued by the local POS terminal and / or the cloud orders synchronized by the cloud KDS server; wherein, when the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server; when the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronizes it to the local KDS server; the cloud order is the online order data stream; Step S3: The local KDS server pre-processes and merges the received local orders and cloud orders, splits the orders according to the client's needs, integrates the processed order data into the order queue corresponding to the client, interacts with the client through HTTP or Socket interface, pushes the order queue and updates the order status of the synchronized order.

[0022] Furthermore, in step S1, system initialization includes: When the local KDS server is started, the UDP broadcast module is automatically activated to periodically broadcast UDP packets in the LAN so that the client can find the UDP packets. The basic service information in the UDP packet is the service IP address, port number and unique identifier UUID of the local KDS server. After the client is started, it listens to the UDP broadcast in the local area network, captures and parses the basic service information in the UDP data packet, and initiates a request to the local KDS server to establish a connection based on the unique identifier; when the client initiates a connection request, the KDS server starts the connection pool management mechanism and creates a preset number of connections in advance to facilitate timely allocation when the client's request arrives.

[0023] Further, in step S1, when the local KDS server is started, the UDP broadcast terminal is automatically activated, and the UDP data packets are periodically broadcast in the local area network, including: The UDP broadcast module dynamically adjusts the broadcast frequency according to the network status, and periodically broadcasts UDP packets in the LAN to facilitate the client to capture UDP packets; the broadcast frequency has an upper limit and automatically reduces the broadcast frequency to reduce the network burden after the client and the local KDS server establish a connection.

[0024] Furthermore, step S1 also includes: real-time monitoring of the connection status between the local KDS server and the client. When the connection is interrupted or abnormal, the client will listen to the UDP broadcast again to re-establish the connection.

[0025] Further, in step S1, the UDP data packet is used by the client to automatically connect to the local KDS server for real-time data interaction, including: The local KDS server sends the merged order queue to the client via HTTP request; After receiving the order queue, the client performs order operations on the order; The client returns the operation feedback to the local KDS server through the Socket interface to update the order status of the order; When the network status is stable, the local KDS server will synchronize the order status of the updated cloud order to the cloud KDS server.

[0026] Further, in step S2, responding to the local order issued by the local POS terminal includes: The local KDS server obtains the login token from the login module of the local POS terminal to ensure the secure transmission of local order data. The token is a security credential used to verify identity and authority. The timing for obtaining the token includes when the local KDS server is initialized, when the token expires, or when it is pulled at a scheduled time. The local KDS server receives local orders from the local POS. Before receiving the local order, the KDS server verifies the received token to determine the validity of the source. If the token is invalid, it refuses to process and returns an error message. If the token passes the verification, the local order is obtained.

[0027] Further, in step S2, responding to the cloud order synchronized by the cloud KDS server includes: The cloud-based KDS server receives all order data streams and caches the data; The cloud order is synchronized to the local KDS server through the cloud KDS order link. After the synchronization is successful, the cloud KDS server saves a copy of the cloud order in the cache until the local KDS server determines that the cloud order has been processed and clears it; The cloud KDS server monitors the cloud order synchronization process in real time. When it detects that the network status is interrupted or abnormal, it starts the retransmission mechanism to resynchronize the cloud orders.

[0028] Furthermore, in step S2, responding to the cloud order synchronized by the cloud KDS server also includes: When the network status is restored, the local KDS automatically synchronizes and updates the status of all unprocessed or unconfirmed orders, and ensures that the cloud order status is consistent with the order status in the cloud KDS server.

[0029] Further, in step S3, the local KDS server pre-processes and merges the received local orders and cloud orders and splits the orders according to the needs of the client, and integrates the processed order data into the order queue corresponding to the client, including: Receive order data from local orders and cloud orders, and deduplicate cloud orders to ensure the uniqueness of order data; Classify order data, differentiate them according to order source and priority, and split orders according to client needs; integrate the processed order data into a unified order queue, arrange the order queue in chronological order and push it to the corresponding client.

[0030] Second embodiment Based on the same inventive concept, the present invention provides a smart kitchen system that supports both cloud and offline push, which is characterized by comprising: The data initialization module is used when the system is initialized. The local KDS server automatically activates the UDP broadcast module and periodically broadcasts UDP data packets containing basic service information in the local area network. The UDP data packets are used by the client to automatically connect to the local KDS server for real-time data interaction. The data acquisition module is used to respond to local orders issued by the local POS terminal and / or cloud orders synchronized by the cloud KDS server. When the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server. When the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronized to the local KDS server. Cloud orders are online order data streams. The data processing module is used by the local KDS server to pre-process and merge the received local orders and cloud orders, split the orders according to the client's needs, integrate the processed order data into the order queue corresponding to the client, interact with the client through HTTP or Socket interface, push the order queue and update the order status of the synchronized order.

[0031] Third embodiment In order to enable those skilled in the art to more clearly understand the technical features of this solution and its practical application, the third embodiment will elaborate on the implementation method and advantages of the present invention in a specific environment. This embodiment aims to demonstrate the operation process of the smart kitchen system under normal network and network interruption conditions through specific cases, as well as how to effectively integrate local and cloud order information to improve the efficiency and stability of kitchen operations. In addition, this embodiment will also explore the performance of the system in practical applications to provide relevant technical personnel with a more intuitive understanding and reference.

[0032] As shown in Figure 3, in the smart kitchen system, when the customer places an order and completes the payment on the cloud or local POS terminal, the order data will be stored in the local KDS server. Analyze the order information, send the entire order to the assembly station, split the order, and assign the corresponding sub-orders to the corresponding production screens A and B. Then, the system will perform single-item or whole-order operations on each sub-order and the entire order. When all dishes are completed, the relevant sub-orders will be marked as completed and fed back to the local KDS server. Once all sub-orders are marked as completed and the integrity of the entire order is confirmed, the system will enter the meal delivery stage. After the meal is delivered, the local KDS server will confirm the completion of the meal pickup and update the order status to ensure the integrity and accuracy of the entire order processing process. Specifically, if Figure 2 As shown, this system mainly includes three parts: POS-Native, which represents the local POS terminal, processes local orders, i.e. offline orders; KDS-Native, which represents the local KDS server, is used to obtain local orders and cloud orders obtained by the cloud KDS server; the client mainly includes the KDS client and the smart screen client.

[0033] The interaction process between the three parts is as follows: ① Login interaction between the local KDS server and the local POS terminal: The local KDS server obtains the login token from the local POS login module to ensure the secure transmission of data. The timing of obtaining the token includes when the local KDS server is initialized, when the token expires, and when it is pulled at a scheduled time.

[0034] ② Local order processing between local KDS server and local POS: After the order is successfully placed in the local POS service, the order information is sent to the local KDS server service for order splitting and processing; the local KDS server service finally sends the processed order information to the client.

[0035] ③ Communication interaction between local KDS server and local POS terminal: The local KDS server service communicates with the client through the socket module in the local POS service.

[0036] ④ The local KDS server adds a cloud KDS order link, which enables the local KDS server to merge cloud orders and offline orders for unified requests and operations by the client. The specific technical details of the cloud KDS order link are as follows: In traditional smart kitchen systems, KDS (Kitchen Display System) usually only processes local orders or only processes online orders, that is, orders sent to the corresponding KDS server through the local POS terminal or the cloud. In this mode, order data is only transmitted directly between local systems or online systems, lacking the processing ability to effectively combine local and cloud orders. As a result, when the network connection is unstable or interrupted, the system cannot effectively integrate order information from different channels, affecting the kitchen's operating efficiency.

[0037] Therefore, in view of this problem, the present invention proposes an improved solution for the cloud KDS order link, so that the local KDS server can effectively integrate cloud and offline orders and realize unified requests and operations of the client. The specific steps are as follows: Integrate the cloud KDS order link in the local KDS server, so that it can obtain and synchronize cloud order data from the cloud KDS server. The cloud KDS order link is responsible for monitoring and receiving order information from the cloud and merging it into the local order queue.

[0038] When the local KDS server receives order data from the cloud KDS server, it first classifies the cloud orders. The classification criteria include the source of the order (local or cloud), and the priority of the order. For the same order, the latest data is processed first, and duplicate order information is deduplicated to ensure the uniqueness and accuracy of the order data.

[0039] After completing the order data merging, the local KDS server consolidates all orders into a unified order queue. This queue is arranged in chronological order, ensuring that kitchen staff can clearly view and process all pending orders.

[0040] The unified order queue will be updated in real time on the client, providing the latest order processing status to ensure smooth kitchen operations.

[0041] The client interacts with the local KDS server through HTTP and Socket interfaces to obtain the merged order queue and perform operations (such as confirming orders, marking orders completed, etc.). The local KDS server synchronizes the client's operation feedback to the cloud KDS service to ensure real-time updates of cloud order status. At the same time, when the network is restored, the local KDS server synchronizes all order operation records during the offline period to the cloud to ensure consistency between the cloud and local system data.

[0042] This technical solution achieves seamless integration of cloud and local orders by introducing cloud links, enabling the smart kitchen system to operate effectively under different network connection states. This not only improves the stability and availability of the system, but also significantly improves the operational efficiency of the kitchen.

[0043] ⑤The local KDS server needs to distinguish the data sources to ensure that offline orders only maintain the offline POS communication link, and cloud orders only maintain the cloud service communication link.

[0044] ⑥Push cloud order: When the local KDS server completes the operation of the cloud order, the order status is synchronized to the cloud service.

[0045] ⑦Pull cloud order: The cloud KDS server intercepts the data stream pushed online and sends it to the local KDS synchronously. The specific process details are as follows: In the smart kitchen system, the cloud KDS server is responsible for receiving and processing order information from different channels, such as payment orders, dine-in orders, take-out orders, and refund orders. These order data are usually transmitted to the local KDS server through cloud push. However, the existing order push method may cause data loss or processing delays due to network fluctuations or other factors. In order to ensure the integrity of order data and the reliability of processing, the present invention designs an interception and synchronization mechanism for cloud order data flow, and the specific implementation steps are as follows: 1. All order data streams received by the cloud KDS server include but are not limited to the following types of orders: Paid orders: Orders involving successful payment of food, including dine-in and takeaway orders.

[0046] Dine-in orders: Orders for consumption in restaurants, which may include order split information, special dish requests, etc.

[0047] Takeaway orders: Orders placed through food delivery platforms, involving delivery information and special customer requirements, etc.

[0048] Refund and Cancellation Menu: Orders that have been paid but need to be refunded or cancelled for various reasons.

[0049] These data streams are intercepted and cached in the cloud KDS server to ensure that no data is lost due to network problems during the push process.

[0050] 2. After completing the initial processing and caching of order data, the cloud KDS server will synchronously send the data to the local KDS server through a secure network protocol (such as HTTPS, WebSocket). Specifically, the client obtains the latest data from KDS-Native through a combination of local HTTP and socket push and pull.

[0051] During the data delivery process, the cloud KDS server will monitor the data transmission status in real time to ensure the integrity of the data packet and the stability of the transmission. In the event of a network interruption, the system will automatically enable the retransmission mechanism to ensure that the order data can be fully and accurately transmitted to the local KDS server.

[0052] After receiving the order data from the cloud, the local KDS server will first verify the data to ensure its accuracy and completeness. The data that passes the verification will be immediately added to the local order queue for further processing.

[0053] 3. In order to ensure reliable data transmission, the system has designed a redundant data storage mechanism. After each cloud order is successfully sent to the local KDS server, a copy will be retained in the cloud KDS server until the local KDS server confirms that the data has been processed.

[0054] After the local KDS server completes the order processing, it will feed back the processing results (such as order confirmation, order completion status) to the cloud KDS server. The cloud KDS server will clean up the corresponding order cache data only after confirming that the data is consistent. This process ensures that the order data will not be lost or processed repeatedly when the network fluctuates or is interrupted.

[0055] In addition, the system also supports automatic synchronization and updating of the status of all unprocessed or unconfirmed orders when the network is restored, ensuring that the data in the cloud and local systems are always consistent.

[0056] Therefore, this technical solution ensures the stability and reliability of the smart kitchen system in different network environments through the effective interception and reliable delivery mechanism of cloud order data flow, avoids order loss or processing errors caused by network problems, and thus improves the efficiency of kitchen operations and customer experience.

[0057] Finally, in the smart kitchen system, clients such as KDS clients and smart screen clients need to communicate with the KDS-Native service in real time to obtain the latest order data and kitchen operation status. In a complex network environment, how to quickly and accurately discover and connect to the local KDS server becomes the key to the stable operation of the system. In order to achieve this goal, the present invention uses UDP broadcast technology for LAN service discovery to ensure that the client can automatically and reliably discover and connect to the local KDS server. The specific implementation steps are as follows: 1. Initialization of UDP broadcast: When the local KDS server is started, the system automatically initializes the UDP broadcast module. This module packages the basic information of the service, such as the service IP address, port number, service identifier, etc., into a UDP data packet and broadcasts it periodically in the local area network.

[0058] The UDP datagram also contains a unique identifier for the service, such as a UUID, so that the client can accurately match and connect to the correct local KDS server. This mechanism is particularly suitable for environments where multiple local KDS server instances coexist, preventing the client from connecting to the wrong service.

[0059] 2. Client service discovery and connection: When the client starts, it will first listen to the UDP data packets in the LAN and wait for the broadcast information from the local KDS server. Once the client receives the data packet, it will parse the service information and automatically try to establish a connection with the local KDS server.

[0060] To ensure that the client can quickly discover and connect to the local KDS server, the client's listening operation is executed immediately after startup. After discovering and connecting to the service, the service information is cached for direct use in subsequent operations, reducing the delay in service discovery.

[0061] 3. Reliability and stability of broadcasting: Due to its connectionless nature, UDP broadcast may cause broadcast packet loss in the case of network congestion or interference. In order to improve the reliability of broadcast, the system has designed a redundant broadcast mechanism. The KDS-Native service will broadcast service information multiple times within a period of time and dynamically adjust the broadcast frequency according to the network status to ensure that the client receives the broadcast packet in the shortest time.

[0062] At the same time, in order to prevent broadcast storms from burdening the network, the system sets an upper limit on the frequency of broadcast transmission, and automatically reduces the broadcast frequency after the client successfully connects to the service to reduce the impact on the network.

[0063] 4. Service coordination in a multi-client environment: In a multi-client environment, multiple clients may try to connect to the same KDS-Native service at the same time. To ensure the stability of the connection and the efficient use of the service, the system has designed a connection pool management mechanism. When the KDS-Native service receives connection requests from multiple clients, it will reasonably allocate and manage the connections to avoid resource competition and connection conflicts.

[0064] The connection status between the client and the KDS-Native service is monitored in real time by the system. If the connection is interrupted or abnormal, the client will automatically re-initiate the service discovery process and re-establish the connection to ensure the continuity of order data and job status.

[0065] This technical solution realizes the automatic discovery and connection of KDS-Native services in the local area network through UDP broadcast, ensuring that the client can quickly and accurately connect to the required service instance when starting. At the same time, through the redundant broadcast mechanism and connection management, the reliability of service discovery and the utilization efficiency of network resources are improved, ensuring the stable operation of the smart kitchen system in a complex network environment.

[0066] The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should also be regarded as the protection scope of the present invention.

[0067] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. A smart kitchen method that supports both cloud and offline push, characterized in that: include, Step S1: When the system is initialized, the local KDS server automatically activates the UDP broadcast module and periodically broadcasts a UDP data packet containing basic service information in the local area network; the UDP data packet is used for the client to automatically connect to the local KDS server for real-time data interaction; Step S2, responding to the local orders issued by the local POS terminal and / or the cloud orders synchronized by the cloud KDS server; wherein, when the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server; when the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronizes to the local KDS server; the cloud order is the online order data stream; Step S3: The local KDS server pre-processes and merges the received local orders and cloud orders, splits the orders according to the needs of the client, integrates the processed order data into the order queue corresponding to the client, interacts with the client through HTTP or Socket interface, pushes the order queue and updates the order status of the synchronized order.

2. The smart kitchen method according to claim 1, characterized in that: In step S1, system initialization includes: When the local KDS server is started, the UDP broadcast module is automatically activated to periodically broadcast the UDP data packet in the local area network so that the client can find the UDP data packet; the basic service information in the UDP data packet is the service IP address, port number and unique identifier UUID of the local KDS server; After the client is started, it listens to the UDP broadcast in the local area network, captures and parses the basic service information in the UDP data packet, and initiates a request to the local KDS server to establish a connection according to the unique identifier; wherein, when the client initiates the request for connection, the KDS server starts the connection pool management mechanism and pre-creates a preset number of connections to facilitate timely allocation when the client's request arrives.

3. The smart kitchen method according to claim 2, characterized in that: In step S1, when the local KDS server is started, the UDP broadcast terminal is automatically activated, and the UDP data packet is periodically broadcasted in the local area network, including: The UDP broadcast module dynamically adjusts the broadcast frequency according to the network status, and periodically broadcasts the UDP data packets in the local area network to facilitate the client to capture the UDP data packets; the broadcast frequency has a frequency upper limit and after the client and the local KDS server establish a connection, the broadcast frequency is automatically reduced to reduce the network burden.

4. The smart kitchen method according to claim 2, characterized in that: Step S1 also includes: real-time monitoring of the connection status between the local KDS server and the client. When the connection is interrupted or abnormal, the client will listen to the UDP broadcast again to re-establish the connection.

5. The smart kitchen method according to claim 1, characterized in that: In step S1, the UDP data packet is used by the client to automatically connect to the local KDS server for real-time data interaction, including: The local KDS server sends the merged order queue to the client via an HTTP request; After receiving the order queue, the client performs an order operation on the order; The client returns the operation feedback to the local KDS server through the Socket interface to update the order status of the order; When the network status is stable, the local KDS server synchronizes the updated order status of the cloud order to the cloud KDS server.

6. The smart kitchen method according to claim 1, characterized in that: In step S2, responding to the local order issued by the local POS terminal includes: The local KDS server obtains a login token from the login module of the local POS terminal to ensure the secure transmission of the local order data; wherein the token is a security credential used to verify identity and authority, and the timing for obtaining the token includes when the local KDS server is initialized, when the token expires, or when it is pulled at a scheduled time; The local KDS server receives the local order from the local POS terminal; before receiving the local order, the KDS server verifies the received token to determine the validity of the source, and when the token is invalid, refuses to process and returns an error message; when the token passes the verification, the local order is obtained.

7. The smart kitchen method according to claim 1, characterized in that: In step S2, the cloud order synchronized in response to the cloud KDS server includes: The cloud KDS server receives all the order data streams and caches the data; The cloud order is synchronized to the local KDS server through the cloud KDS order link. After the synchronization is successful, the cloud KDS server saves a copy of the cloud order in the cache until the local KDS server determines that the cloud order has been processed and clears it; The cloud KDS server monitors the cloud order synchronization process in real time, and when it detects that the network status is interrupted or abnormal, it starts the retransmission mechanism to resynchronize the cloud order.

8. The smart kitchen method according to claim 7, characterized in that: In step S2, the cloud order synchronized in response to the cloud KDS server also includes: When the network status is restored, the local KDS automatically synchronizes and updates the status of all unprocessed or unconfirmed orders, and ensures that the cloud order status is consistent with the order status in the cloud KDS server.

9. The smart kitchen method according to claim 1, characterized in that: In step S3, the local KDS server performs pre-processing and merging according to the received local order and the cloud order and splits the order according to the needs of the client, and integrates the processed order data into the order queue corresponding to the client, including: Receiving order data of the local order and the cloud order, and performing deduplication processing on the cloud order to ensure the uniqueness of the order data; The order data is classified, differentiated according to order source and priority, and the orders are split according to the needs of the client; the processed order data is integrated into a unified order queue, and the order queue is arranged in chronological order and pushed to the corresponding client.

10. A smart kitchen system that supports both cloud and offline push, characterized in that: include: Data initialization module, used for system initialization, the local KDS server automatically activates the UDP broadcast module, and periodically broadcasts UDP data packets containing basic service information in the local area network; the UDP data packets are used by the client to automatically connect to the local KDS server for real-time data interaction The data acquisition module is used to respond to the local orders issued by the local POS terminal and / or the cloud orders synchronized by the cloud KDS server; wherein, when the network status is stable, the cloud KDS server intercepts, caches and synchronously sends all online order data streams to the local KDS server; when the network status is unstable or interrupted, the cloud KDS server continues to cache the order data stream until the network status is restored and then synchronized to the local KDS server; the cloud order is the online order data stream; The data processing module is used for the local KDS server to pre-process and merge the received local orders and cloud orders, split the orders according to the needs of the client, integrate the processed order data into the order queue corresponding to the client, interact with the client through HTTP or Socket interface, push the order queue and update the order status of the synchronized order.

Images