A wireless recording system for infant and toddler care events and a multi-format interactive recording method

The wireless recording system for infant and toddler care events via Bluetooth Low Energy broadcasting solves the problems of high cost, complex deployment, privacy concerns, and insufficient full-scene coverage in existing technologies. It achieves low-cost, full-scene coverage, sharing by multiple caregivers, and privacy-protected recording of care events, and the button battery can be used for a long time.

CN123123834APending Publication Date: 2026-11-17CHONGQING MECAMEI TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611280565.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing methods for recording infant and toddler care have problems such as high cost, complex deployment, privacy concerns, insufficient coverage across all scenarios, and risk of location tracking leakage, and cannot meet the needs of multiple caregivers to share records.

Method used

The wireless recording system for infant and toddler care events using low-power Bluetooth broadcasting includes an event recording button, a host gateway, and a server. It enables network configuration-free operation, one-click recording, reliable transmission, cloud-based attribution authentication, and automatic archiving. It supports multi-format interactive recording and encodes the type and semantics of care events through an event type field, with the server generating care records.

Benefits of technology

It achieves low-cost, full-scenario coverage, multi-caregiver sharing, and privacy protection in nursing event recording. The button requires no network configuration or connection, the button battery can be used for a long time, and the server-side fault-tolerant closed-loop mechanism ensures that records are not lost and prevents the device from being tracked.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123834A_ABST
    Figure CN123123834A_ABST
Patent Text Reader

Abstract

This invention discloses a wireless recording system and multi-mode interactive recording method for infant care events. The system includes a Bluetooth broadcast event recording button powered by a button battery and a Bluetooth-to-wireless gateway powered by AC power. The button broadcasts care events in plaintext event frames. The event type field simultaneously encodes the event category and semantics (instantaneous / time period / measurement / left / right breastfeeding). The serial number is persistently stored for the gateway to deduplicate. Attribution authentication is completed in the cloud: application scanning and binding, and a whitelist is distributed from the cloud. The server implements a fault-tolerant closed loop for start and end frame pairing, timeout by category threshold and heartbeat keep-alive, isolated frame estimation, and cancellation rollback. The button provides four interaction modes: single-button timing, double-button instantaneous, double-button breastfeeding timing, and knob measurement. It supports pre-filling of the last feeding amount, silent submission on the confirmation page, and can adopt a privacy protection mode that hides the identity during normal times and exposes the identifier during pairing. This invention realizes one-click blind operation recording of infant care without network configuration, in all scenarios, and shared by multiple users.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of infant and toddler care assistive devices and Internet of Things communication technology, specifically to an infant and toddler care event wireless recording system based on low-power Bluetooth broadcasting, a multi-form interactive recording method, and an inter-device communication frame protocol, applicable to recording care scenarios such as feeding, sleeping, diaper changing, bathing, swimming, and playing. Background Technology

[0002] Daily care records for infants and toddlers (feeding times and amounts, sleep schedules, diaper changes, bathing, etc.) are crucial for newborn care, especially during the breastfeeding period when precise control of feeding intervals and amounts is essential. Care is typically shared by multiple caregivers, including parents, grandparents, and a postpartum nanny, and these caregivers need to share care records in real time.

[0003] There are three main types of existing nursing record-keeping methods. The first is manual recording via a mobile application: this requires unlocking the phone, opening the application, and navigating through multiple menus, making it difficult to operate blindly with one hand at night, and recording actions can interrupt the care process. The second type is smart bottles or wearable sensor solutions: these rely on specific bottles or wearable devices and cannot cover all scenarios such as breastfeeding, sleep, and diaper changing; the cost of cleaning and maintaining these devices is also high. The third type is visual or physiological sensor monitoring solutions: these are costly, complex to deploy, and raise privacy concerns.

[0004] On the other hand, although the low-power Bluetooth wireless switch in the smart home field has the form of "button battery button + Bluetooth gateway", its binding authentication adopts the local pairing mode, and the event semantics are control commands for smart home devices. It does not have the ownership management, start and end frame pairing, duration and capacity calculation capabilities required for nursing record scenarios.

[0005] In addition, low-power Bluetooth devices using fixed broadcast addresses are at risk of being scanned and tracked by third parties when broadcasting for a long time, and there is a risk of location tracking leakage when applied to infant and toddler scenarios; moreover, different care events have different requirements for interaction forms - timing events only need the start and end times, feeding events also need to record milliliters, diaper changing is an instantaneous event, and breastfeeding needs to distinguish between the left and right sides - a single button form cannot cover all scenarios.

[0006] Therefore, there is a need for a low-cost, button-operated, network-free infant care event recording solution that covers all scenarios, can be shared by multiple caregivers, and has privacy protection capabilities. Summary of the Invention

[0007] To address the shortcomings of existing technologies, the present invention aims to provide a wireless recording system for infant and toddler care events and a multi-form interactive recording method. The event recording button requires no network configuration or connection, enabling one-click recording, reliable transmission, cloud-based authentication, and automatic archiving. The host gateway is automatically connected to the network after being configured once by the mobile terminal.

[0008] To achieve the above objectives, the present invention adopts the following system technical solution: a wireless recording system for infant and toddler care events, comprising at least one event recording button, a host gateway, and a server. The event recording button is battery-powered and transmits plaintext event frames via Bluetooth Low Energy in a broadcast manner. Each event frame includes at least a device identification field, an event type field, and a serial number field. The event type field encodes the type and semantics of the care event. The host gateway is powered by AC mains and includes a Bluetooth receiving module and a wireless network communication module. It scans and parses the event frames, deduplicates them according to the device identification and serial number, and then forwards them to the server. The server maintains the attribution relationship between the event recording button and the user account and generates care records based on the event semantics represented by the event type field.

[0009] Furthermore, the event semantics include at least instantaneous events, time-segment events, and metering events: instantaneous events generate a complete record from a single frame; time-segment events generate a record containing duration by pairing a start frame with an end frame; and metering events carry a capacity value field in the end frame.

[0010] Furthermore, the event type field also includes breastfeeding side time period events, which encode whether breastfeeding is done with the left or right breast. The server generates left and right breastfeeding duration records according to left and right sides respectively, and calculates the cumulative duration of one side and the total duration.

[0011] Furthermore, the server performs cloud authentication and binding: it receives binding requests from event log buttons discovered by the mobile terminal, establishes the ownership relationship between the buttons and user accounts, and sends a whitelist containing the device identifiers of the bound buttons to the host gateway; the host gateway or the server discards event frames from buttons not on the whitelist.

[0012] Furthermore, the event recording button is normally in a deep sleep state. The button switch is connected to the real-time clock domain pin of the main control chip. The button level directly wakes up the main control chip, and the wake-up is considered a valid button event. The event progress status and serial number of the button are persisted in non-volatile memory. After power failure and restart, the short window broadcast and periodic heartbeat during the event progress period are automatically restored.

[0013] Furthermore, after the event recording button is pressed, it continuously broadcasts a status frame in a preset short window while the serial number remains unchanged; during the period event, it is periodically woken up by a real-time clock timer and broadcasts a heartbeat frame with the serial number incremented by one; the host gateway maintains a serial number status table indexed by device identifier, removes duplicate frames with the same serial number, and forwards the heartbeat frame to the server.

[0014] Furthermore, the server performs fault-tolerant closure for time-segment events: based on the most recent received time of the start frame or heartbeat frame, if no new frame is received beyond the threshold configured according to the event type, the record is automatically closed and a timeout attribute is marked; when a start frame of the same type as the ongoing event is received during the time-segment event, it is regarded as a heartbeat keep-alive frame and the most recent received time is updated; when a start frame of another time-segment event of the same button is received, the ongoing event is closed with the start time of the new event as the end time; when only an end frame is received, the start time is back-estimated according to the preset default duration; when a cancellation event is received, the corresponding unclosed ongoing record is deleted.

[0015] Furthermore, the event recording button broadcasts using a randomly rotating Bluetooth broadcast address during normal operation. The broadcast payload carries a temporary identifier in encrypted or hash form of the device identifier, but not the plaintext real device identifier. The temporary identifier is parsed by the host gateway or server for whitelist matching and attribution. When entering pairing mode, it broadcasts in a recognizable manner and provides the device identifier to the mobile terminal via Bluetooth Low Energy connection service for cloud binding.

[0016] This invention also provides a method for wirelessly recording infant and toddler care events, comprising: after an event recording button detects a key press event, it sends a plaintext event frame via Bluetooth Low Energy broadcast, the event frame containing a device identifier, event type, and serial number; a host gateway scans and parses the event frame, removes duplicates according to the device identifier and serial number, and forwards it to the server via a wireless network; the server verifies the attribution of the event recording button, and generates a care record according to the event semantics represented by the event type: instantaneous events are directly recorded; time-period events are recorded by pairing the start frame and end frame; and metered events are recorded by extracting the capacity value from the end frame.

[0017] This invention also provides four multi-mode interactive recording methods corresponding to the four button types: a single-button timing recording method, applied to a single button, where a short press switches the start and end states of a time period event, and short window broadcasts are performed after the start and end are switched. During the event, periodic heartbeat broadcasts are performed at heartbeat intervals, and the scene semantics of the time period event are assigned by the application or server; an instantaneous recording method, applied to a dual-button button, where a short press of either button generates a complete record without the need for an end frame; a breastfeeding timing recording method, applied to a dual-button button, where the left and right breasts independently maintain the breastfeeding time period event state, supporting alternating breastfeeding from both sides; and a metering recording method, applied to an event recording button that includes a button, a rotary encoder, and a display screen, where a short press starts recording, the rotary encoder adjusts the metering value and displays it on the screen, and a short press ends recording with the capacity value. The metering value is pre-filled with the actual capacity value of the previous record by default, and the confirmation page after completion supports silent automatic submission; in all the above methods, the button can be connected to the real-time clock domain pin of the main control chip to achieve deep sleep wake-up.

[0018] Compared with the prior art, the beneficial effects of the present invention are as follows: (1) The button is free from network configuration, connection and local key, and can be used immediately after pasting, and the recording is completed with one click; (2) The multi-form button covers the semantics of all nursing events such as timing, measurement, instantaneous, left and right side feeding; (3) The records are centrally stored in the cloud and shared in real time by multiple caregivers; (4) The low power consumption design of deep sleep plus button wake-up plus state persistence enables the button battery to support long-term use; (5) The server fault tolerance closure mechanism ensures that the records are not lost when wireless frames are dropped, and the timeout threshold and heartbeat keep-alive mechanism configured according to the event type support the recording of any long-term events such as sleep and play; (6) The two-stage design of random broadcast address and pairing period exposure mark avoids the device being tracked. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments are briefly introduced below.

[0020] Figure 1 The system overall architecture diagram provided for embodiments of the present invention; Figure 2 This is a schematic diagram of the broadcast frame format; Figure 3 Encoding event types represents intent; Figure 4 Bind a sequence diagram to cloud authentication; Figure 5 This is a closed-loop flowchart for server-side events. Figure 6 A low-power state machine transition diagram for the button; Figure 7 Flowchart for gateway scan deduplication; Figure 8 A schematic diagram of the layout of four button types; Figure 9 This is the flow diagram for a single-key timing state machine. Figure 10 Schematic diagram of a dual-key feed-timed independent state machine for left and right sides; Figure 11This is the flow diagram of a knob-type metering state machine; Figure 12 This is a schematic diagram of a three-state screen layout for a knob-type metering system. Detailed Implementation

[0021] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0022] See Figure 1 The wireless recording system for infant care events provided in this embodiment includes an event recording button 100, a host gateway 200, a server 300, and a mobile terminal application 400. The event recording button 100 can be one or more, powered by a button battery, and has no WiFi function, only low-power Bluetooth communication capability. It broadcasts plaintext event frames without establishing a connection or requiring network configuration. It can be attached to any location such as a wall, bedside table, or crib via a back adhesive layer. The host gateway 200 is powered by AC mains and integrates a Bluetooth receiver module and a WiFi communication module. It continuously and passively scans Bluetooth broadcasts, parses event frames conforming to a preset frame format, removes duplicates according to device identifier and serial number, and then transmits the data to the server 300 via the MQTT protocol. The host gateway 200 itself completes a one-time WiFi network configuration via the mobile terminal application: either by issuing wireless network credentials via a BluFi-type Bluetooth network configuration protocol, or by issuing wireless network credentials via the HTTP interface of the gateway's temporary hotspot. The network configuration credentials are persistently stored in non-volatile memory, and the device automatically connects to the network upon power-up without needing to be reconfigured. The server-side 300 maintains the button ownership, event closure, and record generation logic; the mobile terminal application 400 displays nursing records and statistical information for multiple caregivers to share and view.

[0023] The hardware components of the event logging button 100 include a housing, a button battery, a main control circuit board, a button, and an indicator light; the metering version also includes a rotary encoder with a push-button switch and an OLED display. The signal line of the button switch is connected to the RTC domain pin of the main control chip. In deep sleep mode, the button level directly wakes up the main control chip, and waking up is considered a valid button event. A silicone sealing cap can be installed at the button opening on the front of the housing, and a double-sided adhesive layer or a Velcro layer can be installed on the back of the housing, or a magnetic attachment or hanging hole can be provided.

[0024] See Figure 2The event frame is a 16-byte plaintext frame, placed in the ManufacturerSpecific Data field of the Bluetooth Low Energy broadcast packet. The overall structure is: Flags field (02 01 06), Length field (0x13), Type field (0xFF), Manufacturer ID field (2 bytes, little-endian), and 16 bytes payload. The payload structure is: MAGIC field (2 bytes, values ​​0xFE, 0xED), DEVICE_ID field (6 bytes), EVENT field (1 byte), SEQ field (2 bytes, big-endian), DATA field (2 bytes), and RFU reserved field (3 bytes). DEVICE_ID is the device identifier; in this embodiment, it is the Bluetooth chip's factory MAC address, inherently unique and requiring no additional programming. EVENT is the event type encoding, simultaneously encoding the event category and semantics. SEQ is the action sequence number, incremented by one for each valid button press and persisted to the button's local non-volatile memory for gateway deduplication of retransmitted frames in continuous broadcasts. DATA is additional event data; the end frame of metering events carries the milliliter value in big-endian u16, while other events are set to zero.

[0025] See Figure 3 Event type encoding is semantically divided into four categories. **Segmented Events:** 0x01 and 0x02 represent the start and end of sleep, respectively; 0x03 and 0x04 represent the start and end of bathing, respectively; 0x05 and 0x06 represent the start and end of swimming, respectively; 0x07 and 0x08 represent the start and end of play, respectively. **Meaning Events:** 0x10 and 0x11 represent the start and end of bottle feeding, respectively; 0x13 and 0x14 represent the start and end of breastfeeding, respectively, with the DATA field of the end frame carrying the milliliters; 0x12 is the bottle feeding cancellation frame, and 0x15 is the breastfeeding cancellation frame. **Instantaneous Events:** 0x20 represents urination during diaper changing, and 0x21 represents defecation during diaper changing. **Breastfeeding Side Segmented Events:** 0x30 and 0x31 represent the start and end of breastfeeding on the left side, respectively; 0x32 and 0x33 represent the start and end of breastfeeding on the right side, respectively. The semantics of events are defined as follows: For instantaneous events, a single press generates a complete record without an end frame; for time-segment events, the start and end frames are paired by the server to form a record containing the duration; for metering events, the end frame carries the capacity value based on the time-segment event; for breastfeeding-side time-segment events, the left and right breast dimensions are carried based on the time-segment event, with the left and right sides being paired independently.

[0026] See Figure 4The button has no local key and no network configuration process; ownership authentication is all completed in the cloud. The host gateway is configured and bound once by the mobile terminal application: the application sends wireless network credentials and binding keys to the gateway via the BluFi-type Bluetooth configuration protocol or the HTTP interface of the gateway's temporary hotspot. The gateway persists the credentials in non-volatile memory and connects to the home network. Then, it logs into the server via MQTT. The server records the ownership relationship between the gateway and the home account. After that, the gateway automatically connects to the network upon power-up without repeated configuration. Button Binding Process: Step 1: The button comes with a device identifier at the factory. A long press enters pairing mode and broadcasts a connection. The mobile application connects and reads the device identifier, or it can be obtained directly from the broadcast address in the scan results. Step 2: After the application scans and discovers the button, it initiates a binding request to the server. The server verifies and records the ownership relationship between the button and the family account. Step 3: The server sends a whitelist to the family's gateway via MQTT. The whitelist contains a list of allowed button device identifiers. The gateway receives the whitelist and updates its local whitelist. Step 4: The gateway filters broadcast frames according to the local whitelist, or it may not filter them and directly transmit them, allowing the server to make the final ownership decision. The server confirms the ownership of the event before writing it into the record. This model allows for zero button configuration; changing families, transferring ownership, and expanding to multiple buttons can all be done in the cloud.

[0027] See Figure 5 To address scenarios where frame drops may occur in wireless broadcasting, the server implements a fault-tolerant closure strategy: Normal closure: Upon receiving the end frame of a time period or metering event, it pairs it with the ongoing start frame according to the device identifier, generating a record containing start and end times; Timeout closure: Based on the most recent reception time of the start frame or heartbeat frame, if no new frame is received within a threshold configured according to the event type, the record is automatically closed and a timeout attribute is marked. In this embodiment, the thresholds are 12 hours for sleep, 1 hour for bathing, 2 hours for swimming, 4 hours for playing, and 1 hour for feeding. Each threshold can be adjusted in the mobile terminal application, and the record can be modified within the application. Positive; Heartbeat Keep-alive: During the event, the button periodically broadcasts heartbeat frames. When the server receives a heartbeat frame or a start code frame of the same type, it updates the most recent received time of the event. As long as heartbeat frames are continuously received, the event will not time out and close, thus supporting recording of any length of time; Event Handover Closure: When the start frame of another event of the same time period is received during the event of a time period, the event in progress will be closed with the start time of the new event as the end time; End Frame Isolation: When only an end frame is received, the start time is back-estimated according to the preset default duration and the estimated attribute is marked; Cancel Rollback: After receiving a cancel event, the in-process record of the button that has not been closed is deleted.

[0028] See Figure 6The button employs the following low-power state machine: During deep sleep, the main controller is directly woken up by the button level on the RTC domain pin; waking up is considered a valid button press. Button events are determined by debouncing and long / short press settings. In this embodiment, the debouncing threshold is 30 milliseconds, and the long press threshold is 10 seconds for entering pairing mode. For knob-type metering devices, the long press to cancel the feeding state is 3 seconds. After a button press, a preset short window continuously broadcasts a status frame to ensure gateway reception. In this embodiment, the window is 3 seconds long with a 500-millisecond interval, and the sequence number remains unchanged. If the event is still in progress after the short window ends, the device returns to deep sleep and enters a periodic heartbeat. The main controller is woken up by a real-time clock timer at heartbeat intervals. After broadcasting a heartbeat frame with a sequence number incremented by one, it immediately returns to deep sleep. In this embodiment, the heartbeat interval is 5 minutes for button-type mode and 30 seconds for metering mode. The average current introduced by the heartbeat is in the microamp range, and its impact on button battery life is negligible. The end frame is broadcast for a preset short duration before returning to deep sleep, which is 3 seconds in this embodiment. The event status and sequence number are persisted in non-volatile memory and automatically resume short-window broadcasting and periodic heartbeats after power failure and restart. If there is no operation for more than a preset time, it automatically enters deep sleep, which is 10 seconds in this embodiment. In another alternative embodiment, the periodic heartbeat can be omitted. In this case, the button returns to deep sleep immediately after the short-window broadcast ends, and the timeout threshold mentioned by the server is calculated based on the start frame reception time.

[0029] See Figure 7 The host gateway uses a low duty cycle passive scanning method to receive button broadcasts: a scanning interval of 160 milliseconds, a scanning window of 60 milliseconds, and a duty cycle of approximately 30%, balancing power consumption, heat generation, and reception reliability; it parses the broadcast AD structure, matches the vendor ID and frame length, and then verifies the frame header MAGIC; it maintains a status table indexed by device identifier, which records the most recent serial number and in-process status of each button, deduplicates retransmitted frames with the same serial number, and only the first valid frame is uploaded; valid events are uploaded via MQTT, and topics are organized by home and device dimensions.

[0030] See Figure 8 The event logging button offers four modes. See also Figure 9Form 1 is a single-button timing type, suitable for sleep, bathing, swimming, and play scenarios: the button contains only one button and one status indicator light; in standby deep sleep mode, a short press of the button switches the event state and receives immediate LED feedback, with a feedback duration of 150 milliseconds in this embodiment; when switching from not in progress to in progress, the sequence number is incremented and persisted, a scene start frame is sent, a short window broadcasts for 3 seconds, then returns to deep sleep and is woken up by a real-time clock every 5 minutes to broadcast a heartbeat frame, with the indicator light lighting up for 200 milliseconds when the heartbeat wakes it up; when switching from in progress to end, an end frame is sent, broadcasting for 3 seconds to ensure delivery, after which the indicator light turns off and returns to deep sleep; a long press for more than 10 seconds enters pairing mode, and automatically exits after 120 seconds; upon first power-on, it automatically enters pairing mode and waits for binding. The same hardware distinguishes scenes through event encoding, or the application can assign scene semantics to the button.

[0031] See Figure 8 The second type is a dual-button instantaneous event type, suitable for diaper changing scenarios: the button has two independent buttons, corresponding to urination and defecation events respectively; a short press of either button sends the corresponding instantaneous event frame, incrementing the sequence number by one, without needing an end frame; the server receives the instantaneous event frame and directly generates a complete record; the two button events do not affect each other and can be recorded quickly and continuously. As an alternative implementation method, a single-button double-click can be used to switch the event type followed by a single-button confirmation.

[0032] See Figure 10 Form 3 is a dual-button breastfeeding timing type, suitable for breastfeeding scenarios: the button has two independent buttons, corresponding to the left and right breasts respectively; each side maintains an independent time period event state machine, when a button on a side is pressed briefly and there is no ongoing event on that side, a start frame for that side is sent, and when the button on the same side is pressed briefly again, an end frame for that side is sent; the left and right sides are independent of each other, allowing both sides to be in the ongoing state at the same time to adapt to alternating breastfeeding scenarios; the server is paired with the left and right sides according to the device identifier, generates a breastfeeding duration record including the left and right side dimensions, and calculates the duration of a single side and the total duration; the side in progress is distinguished and indicated by the corresponding indicator light.

[0033] See Figure 11 and Figure 12Form 4 is a knob-type metering device suitable for bottle feeding and breast pumping scenarios: the button includes a rotary encoder with a press switch and an OLED display. The battery is a high-capacity button battery; this embodiment uses a CR2450 or CR2477. The interactive state machine includes three states: standby, feeding, and confirmation page. In standby mode: a short press of the knob records the start time and sends a start frame, entering the feeding state; rotating the knob without pressing it only lights up the screen to enter preview mode, displaying the time interval since the last feeding and the volume of milliliters fed in the last feeding, without generating any recording frames; after 8 seconds of inactivity, the screen automatically turns off and returns to deep sleep; a long press for 10 seconds enters pairing mode. During feeding: The screen displays the start time, feeding duration, and current milliliter volume; rotating the knob adjusts the milliliter volume in fixed increments, with each increment in this embodiment being 5 milliliters, ranging from 0 to 500 milliliters; the default milliliter volume is the last actual feeding volume, which is persistently stored in non-volatile memory for pre-filling; the screen lights up after operation, automatically turns off after 8 seconds of inactivity to save power, and lights up again upon rotating the knob again; a short press of the knob sends an end frame carrying the current milliliter volume, entering the confirmation page; a long press for 3 seconds cancels the current record, sending a cancellation frame, and the server deletes any unclosed records; during feeding, a heartbeat frame with a broadcast sequence number incremented by one is awakened at fixed intervals, with an interval of 30 seconds in this embodiment. In the confirmation page state: The screen displays a summary of the milliliter volume, duration, and end time; rotating the knob temporarily adjusts the milliliter volume, and a short press confirms and saves; if no operation exceeds a preset window, it automatically confirms and saves, turns off the screen, and returns to deep sleep; in this embodiment, the window is set to 10 seconds to adapt to nighttime scenarios where the user falls asleep immediately after feeding, without requiring a second confirmation action. Bottle feeding and breast pumping share the same hardware and interaction process, only the event type encoding is different. The event type can be assigned to the button by the application.

[0034] In another alternative embodiment, to prevent the fixed broadcast address from being scanned and tracked by third parties, the button broadcasts using a randomly rotating Bluetooth broadcast address during normal operation. The broadcast payload carries a temporary identifier obtained by encrypting or hashing the device identifier, but does not carry the plaintext real device identifier. After binding is completed, the server sends the corresponding parsing key or verification table to the home gateway. The gateway parses the temporary identifier to obtain the device identifier and then performs whitelist matching and attribution determination. Third parties cannot directly read the real identifier from the broadcast, nor can they track the device via the fixed address. When binding is required, the user long-presses the button to enter pairing mode. The button broadcasts and exposes the connectable GATT service in a recognizable manner. The mobile terminal application connects and reads the device identifier to initiate cloud binding. This two-stage model achieves the goal of hiding the identity during normal operation and exposing the identity only during pairing, maintaining the button's no-network-configuration experience while preventing long-term tracking of infants' personal devices.

[0035] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention. For example: event type coding can be extended to other nursing scenarios; the button main control chip can be an ESP32 series, nRF52 series, or other chips with low-power Bluetooth and deep sleep wake-up capabilities; the wireless network communication module of the host gateway can use cellular networks in addition to WiFi; the capacity measurement unit can use other capacity units in addition to milliliters; the number of buttons in the four forms, the display specifications, and the battery model can all be adjusted as needed.

Claims

1. A wireless recording system for infant care events, characterized by, include: At least one event logging button, battery powered, broadcasts plaintext event frames via Bluetooth Low Energy. The event frame includes at least a device identifier field, an event type field, and a serial number field. The event type field encodes the type and semantics of the nursing event. The host gateway, powered by mains electricity, includes a Bluetooth receiving module and a wireless network communication module, used to scan and parse the event frames, and forward them to the server after deduplication according to the device identifier and serial number. The server-side component is used to maintain the attribution relationship between the event logging button and the user account, and to generate nursing records based on the event semantics represented by the event type field.

2. The system of claim 1, wherein, The event semantics include at least instantaneous events, time-period events, and metering events; wherein instantaneous events are generated as complete records from a single frame; time-period events are generated as records containing duration by pairing start and end frames; and metering events carry a capacity value field in the end frame.

3. The system according to claim 1, characterized in that, The event type field also includes breastfeeding side time period events, which encode whether breastfeeding is done with the left or right breast. The server generates left and right breastfeeding duration records according to left and right sides respectively, and calculates the cumulative duration of one side and the total duration.

4. The system according to claim 1, characterized in that, The server performs cloud authentication and binding: it receives binding requests from event log buttons discovered by the mobile terminal, establishes the ownership relationship between the buttons and the user account, and sends a whitelist containing the device identifiers of the bound buttons to the host gateway; the host gateway or the server discards event frames of buttons that are not on the whitelist.

5. The system according to claim 1, characterized in that, The event recording button is normally in a deep sleep state. The button switch is connected to the real-time clock domain pin of the main control chip. The button level directly wakes up the main control chip, and the wake-up is considered a valid button event. The event status and serial number of the button are persisted in non-volatile memory. After power failure and restart, the short window broadcast and periodic heartbeat during the event are automatically restored.

6. The system according to claim 1, characterized in that, After the event recording button is pressed, it continuously broadcasts a status frame in a preset short window while the serial number remains unchanged; during the period event, it is periodically woken up by a real-time clock timer and broadcasts a heartbeat frame with the serial number incremented by one; the host gateway maintains a serial number status table indexed by device identifier, removes duplicate frames with the same serial number, and forwards the heartbeat frame to the server.

7. The system according to claim 1 or 6, characterized in that, The server performs fault-tolerant closure for time-period events: based on the most recent reception time of the start frame or heartbeat frame, if no new frame is received beyond the threshold configured according to the event type, the record is automatically closed and a timeout attribute is marked; when a start frame of the same type as the ongoing event is received during the time-period event, it is regarded as a heartbeat keep-alive frame and the most recent reception time is updated. When the start frame of another event for the same button is received, the ongoing event will be closed with the start time of the new event as the end time; when only the end frame is received, the start time will be estimated back according to the preset default duration; when a cancellation event is received, the corresponding unclosed ongoing record will be deleted.

8. The system according to claim 1, characterized in that, The event recording button broadcasts using a randomly rotating Bluetooth broadcast address during normal operation. The broadcast payload carries a temporary identifier in encrypted or hash form of the device identifier but not the plaintext real device identifier. The temporary identifier is parsed by the host gateway or server for whitelist matching and attribution. When entering pairing mode, it broadcasts in a recognizable manner and provides a device identifier to the mobile terminal via Bluetooth Low Energy connection service for cloud binding to be completed.

9. A method for wirelessly recording infant and toddler care events, characterized in that, include: After the event logging button detects a key press event, it sends a plaintext event frame via Bluetooth Low Energy broadcast. The event frame includes the device identifier, event type, and serial number. The host gateway scans and parses the event frames, removes duplicates by device identifier and serial number, and forwards them to the server via the wireless network. After the server verifies the attribution of the event logging button, it generates nursing records based on the event semantics represented by the event type: instantaneous events generate records directly; time-segmented events pair the start frame and end frame to generate records containing the duration. The metering event extracts the capacity value from the end frame and writes it to the record.

10. A method for recording metered nursing events, applied to an event recording button comprising a button, a rotary encoder, and a display screen, characterized in that, include: When a short press event is detected in standby mode, the start time is recorded and a start frame is sent via Bluetooth Low Energy broadcast. When a rotation event of the rotary encoder is detected, the metering value is adjusted by a preset step and displayed in real time on the display screen. The default value of the metering value is taken from the actual capacity value recorded last time. When a short press event is detected again, the end time is recorded and an end frame carrying the measured value is sent. After sending the end frame, the system enters the confirmation page state, allowing rotation to correct the measurement value and a short press to confirm. If there is no operation for more than a preset time window, the system will automatically confirm and save the data and enter deep sleep. The server generates a nursing record containing duration and capacity values ​​based on the pairing of the start frame and the end frame.

11. The method according to claim 10, characterized in that, When a rotation event is detected in standby mode, the display screen is lit up to show the most recent recorded information and time interval, without sending any recording frames; when a long press is detected during measurement and exceeds the preset duration, a cancellation frame is sent, and the server deletes the in-process record of the button that is not closed; during measurement, a heartbeat frame with the broadcast sequence number incremented by one is woken up at fixed intervals.

12. A method for recording breastfeeding timed nursing events, applied to an event recording button including a first button and a second button, characterized in that, include: The first button and the second button correspond to breastfeeding from the left breast and breastfeeding from the right breast, respectively, with each side having its own independent time period event status maintenance; When a button on a side is pressed briefly and there is no ongoing event on that side, a start frame for that side is sent; when the button on that side is pressed briefly again, an end frame for that side is sent. Both sides are allowed to be in progress simultaneously; The server pairs the start frame and end frame with the device identifier and the left and right sides respectively, and generates a duration record containing the left and right side dimensions.

13. A button-type nursing event recording method, applied to an event recording button including at least one button, each button corresponding to a nursing event type, characterized in that: When the nursing event corresponding to the button is a momentary event, a short press of the button will send a momentary event frame carrying the corresponding event type, and the server will directly generate a complete record based on a single frame; When the nursing event corresponding to the button is a time-limited event, a short press of the button switches the event status: from not in progress to in progress, a start frame is sent and continuously broadcast in a preset short window, and during the in progress, a heartbeat frame with a sequence number incremented by one is periodically broadcast at heartbeat intervals; from in progress to end, an end frame is sent and continuously broadcast for a preset short duration before entering deep sleep. The same button can be encoded with different event types to represent different nursing scenarios, or the server can assign scenario semantics to the button.

14. The method according to claim 13, characterized in that, The instantaneous event types include diaper changing urination events and diaper changing defecation events; the time-based event scenarios include sleeping, bathing, swimming, and playing.

15. The method according to any one of claims 9 to 14, characterized in that, The button is connected to the real-time clock domain pin of the main control chip. The button level in deep sleep directly wakes up the main control chip, and the button is considered a valid button once it is woken up. The event status and sequence number are persisted in non-volatile memory and are automatically restored after power failure and restart.