A method for displaying a result of a ball hitting and a system therefor

Abstract

The present application relates to a kind of ball hitting result display control method and system thereof.The method includes: receiving the full volume ball hitting result data output by ball hitting monitoring device;Integrity and validity check is carried out on full volume ball hitting result data;When full volume ball hitting result data meets the data conditions of integrity and validity, unified ball hitting data model of fitting wearable display device is generated by analyzing full volume ball hitting result data, and ball hitting data ready event is generated;Based on ball hitting data ready event, ball hitting data model and display control instruction are issued to wearable display device, to drive wearable display device to display current ball hitting result based on ball hitting data model;If full volume ball hitting result data does not meet the data conditions of integrity and validity, then do not use current abnormal full volume ball hitting result data to refresh the original effective ball hitting result on wearable display device, and do not carry out storage statistical operation.The present application can improve the accuracy and reliability of ball hitting result display.

Description

Technical Field

[0001] This invention relates to the field of golf auxiliary equipment technology, and in particular to a method and system for displaying and controlling the result of a shot. Background Technology

[0002] Existing golf launch monitor devices from various brands can collect various raw measurement parameters during the golf shot, such as Carry (landing distance), Total (total distance), Ball Speed ​​(ball speed), Club Speed ​​(club head speed), Launch Angle (launch angle), and Spin (spin speed), and display them through mobile phones, tablets, external displays, or wearable devices.

[0003] In real-world scenarios where wearable display devices such as AR (Augmented Reality Glasses) are used, the timing of display, data integrity, and handling of abnormal data become even more critical. In related technologies, existing golf shot result display control schemes typically focus on whether data can be displayed, usually using the first data packet or a standard ShotDetected event as the refresh criterion. This is prone to problems such as prematurely refreshing incompletely parsed data, missing fields, or overwriting erroneous results, ultimately leading to poor accuracy and reliability in displaying the user's shot results. Summary of the Invention

[0004] This invention provides a method and system for displaying and controlling the results of a golf shot, in order to solve the problem of poor accuracy and reliability in the display and control schemes for golf shot results.

[0005] This invention discloses a method for displaying and controlling the result of a shot, comprising:

[0006] Receive all ball-hitting result data output by the ball-hitting monitoring equipment; The completeness and validity of the full set of shot results data are verified. Once the full set of shot results data meets the data conditions for completeness and validity, the full set of shot results data is parsed to generate a unified shot data model adapted to wearable display devices, and a shot data ready event is generated. Based on the ball-hitting data ready event, the ball-hitting data model and display control command are sent to the wearable display device to drive the wearable display device to display the current ball-hitting result based on the ball-hitting data model; If the full-volume shot result data does not meet the data conditions for completeness and validity, the original valid shot results on the wearable display device will not be refreshed using the current abnormal full-volume shot result data, and no retention or statistical operation will be performed on the current abnormal full-volume shot result data.

[0007] Optionally, the full set of shot results data includes a shot result field, and the step of parsing the full set of shot results data to generate a unified shot data model specifically includes the following steps: According to the preset field mapping rules, the byte order of each field of the full ball hitting result data is parsed to extract the original ball hitting parameter values. Based on the pre-configured unit system, the extracted raw hitting parameter values ​​are converted to the corresponding units. The converted values ​​of various hitting parameters are encapsulated according to a preset standardized field structure to generate a unified hitting data model that is compatible with wearable display devices.

[0008] Optionally, the integrity verification of the full set of shot result data specifically includes the following steps: Determine whether the overall byte length of the full ball-hitting result data matches the preset standard length; If the overall byte length of the full ball-hitting result data matches the preset standard length, then the full ball-hitting result data is determined to meet the data integrity requirements.

[0009] Optionally, the full set of shot result data includes a status identifier field, and the validity verification of the full set of shot result data specifically includes the following steps: After determining that the full range of shot results data meets the data integrity conditions, the status identifier field at a preset position within the full range of shot results data is read, and the full range of shot results data is identified as valid shot data in combination with preset status code rules. If the total number of shot results data is valid shot data, then the total number of shot results data is determined to meet the data conditions for validity.

[0010] Optionally, the preset status code rules include a first preset status code, a second preset status code, and a third preset status code. The step of combining the preset status code rules to identify whether the total number of shot results data belongs to valid shot data specifically includes the following steps: If the status identifier field at a preset position in the full-volume hit result data matches the first preset status code, then the full-volume hit result data is determined to be valid hit data. If the status identifier field at a preset position in the full shot result data matches the second preset status code, then the current shot is determined to be a miss or a blank shot. If the status identifier field at a preset position within the full ball-hitting result data matches the third preset status code, then it is determined that the current ball-hitting distance exceeds the upper limit. If the status identifier field at a preset position in the full ball-hitting result data fails to match the first preset status code, the second preset status code, and the third preset status code, a data reception error message will be displayed.

[0011] Optionally, the ball-hitting result display control method further includes the following steps: When the current shot is determined to be a miss or a missed shot, or when the current shot distance exceeds the limit, the wearable display device is controlled to execute the corresponding abnormal prompt.

[0012] Optionally, the ball-hitting result display control method further includes the following steps: If the full hit result data does not meet the data integrity condition, the full hit result data output by the hit monitoring device will be actively reread, or the hit monitoring device will be actively requested to output the full hit result data. If the maximum number of retries is reached and the complete data of the shot is still not obtained, the data transmission of the shot is deemed to have failed, and a data reception error message is displayed.

[0013] Optionally, the ball-hitting result display control method further includes the following steps: When multiple push reports from the ball-hitting monitoring device are received within a preset time window, the content of each push report is compared. If the comparison content of multiple push-reported data is completely identical, it is determined to be duplicate data, and only one push-reported data is selected as the full ball hitting result data; If the comparison content of multiple push reports is different from each other, and each push report data satisfies the data conditions of completeness and validity, then they are recorded as different valid full-volume ball-hitting result data.

[0014] Optionally, the ball-hitting result display control method further includes the following steps: The system controls the wearable display device to provide a main results display page, a parameter details page, and a data statistics page, and drives the wearable display device to respond to page switching operation commands, switching between the main results display page, the parameter details page, and the data statistics page. Once the ball-hitting data is ready event is generated, the wearable display device is controlled to automatically switch and reset the current display page to the main results display page.

[0015] The present invention also discloses a ball-hitting result display and control system, comprising: Shot monitoring equipment is used to collect various raw measurement parameters during the golf shot process and output full shot result data; A mobile terminal is communicatively connected to the ball-hitting monitoring device, and the mobile terminal is used to execute the ball-hitting result display control method as described in any of the above. A wearable display device is communicatively connected to the mobile terminal. The wearable display device is used to receive the ball-hitting data model and display control commands, and to display the ball-hitting result based on the ball-hitting data model.

[0016] The beneficial effects of the shot result display control method provided in this embodiment of the invention are as follows: After receiving the full shot result data output by the shot monitoring device, this embodiment of the invention first performs a dual verification of the completeness and validity of the received full shot result data. Only after verification that the data meets the data conditions is a unified shot data model adapted to the wearable display device constructed, and a shot data ready event is triggered before being pushed to the wearable display device for display. For full shot result data with abnormal verification, the original valid shot result of the wearable display device is maintained, and no data retention and statistical operation is performed, preventing abnormal full shot result data from overwriting the correct screen and polluting local statistics and backend records, thereby improving the accuracy and reliability of shot result display on the wearable display device. At the same time, the wearable display device does not need to parse the original full shot result data of different shot monitoring devices, but only needs to receive the unified adapted shot data model and display the current shot result, reducing the original protocol parsing burden of the wearable display device. Attached Figure Description

[0017] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. In the accompanying drawings: Figure 1 This is a flowchart illustrating the ball-hitting result display control method according to an embodiment of the present invention; Figure 2 This is a flowchart illustrating an embodiment of the present invention for generating a unified hitting data model by analyzing all hitting result data. Figure 3 This is a structural block diagram of the ball-hitting result display and control system according to an embodiment of the present invention.

[0018] The labels for the attached figures are as follows: 10. Ball-hitting monitoring equipment; 20. Mobile terminal; 30. Wearable display device. Detailed Implementation

[0019] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0020] This invention provides a method for displaying and controlling the result of a shot, such as... Figure 1 and Figure 3 As shown, the shot result display control method includes: S101, Receive the full ball-hitting result data output by the ball-hitting monitoring device 10; S102. Verify the completeness and validity of all ball-hitting results data; S103. After all the ball-hitting results data meet the data conditions of completeness and validity, parse all the ball-hitting results data to generate a unified ball-hitting data model adapted to wearable display devices, and generate a ball-hitting data ready event. S104. Based on the ball-hitting data ready event, send the ball-hitting data model and display control command to the wearable display device to drive the wearable display device to display the current ball-hitting result based on the ball-hitting data model; S105. If the full-volume hitting result data does not meet the data conditions for completeness and validity, the original valid hitting results on the wearable display device will not be refreshed using the current abnormal full-volume hitting result data, and the current abnormal full-volume hitting result data will not be retained for statistical operation.

[0021] In this embodiment of the invention, after receiving the full set of hitting result data output by the hitting monitoring device 10, the full set of hitting result data is first subjected to dual verification of integrity and validity. Only after verification that the data meets the data conditions is a unified hitting data model adapted to the wearable display device constructed, and a hitting data ready event is triggered before being pushed to the wearable display device 30 for display. For full set of hitting result data with abnormal verification, the original valid hitting result of the wearable display device is maintained, and no data retention and statistical operation is performed, preventing abnormal full set of hitting result data from overwriting the correct screen and polluting local statistics and backend records, thereby improving the accuracy and reliability of the hitting result display of the wearable display device 30. At the same time, the wearable display device 30 does not need to parse the original full set of hitting result data from different hitting monitoring devices 10, but only needs to receive the unified adapted hitting data model and display the current hitting result, reducing the original protocol parsing burden of the wearable display device 30.

[0022] In step S101, in a specific implementation scenario, at a golf driving range or course, the shot monitoring device 10, such as a radar tracking device or an optical tracking device, collects complete data on each of the player's shots in real time. After the player completes a swing, the shot monitoring device 10 collects and generates full shot result data, including shot result fields such as clubhead speed, path, distance, and height. The mobile terminal 20 can receive the full shot result data output by the shot monitoring device 10 via wired or wireless communication. Wireless communication methods include at least one of Bluetooth, WiFi, or other wireless communication methods. Wired communication methods can be USB, Ethernet, etc.

[0023] In step S102, in a specific implementation scenario, after receiving the full set of shot results data, an integrity check is performed to confirm that the data packet length is complete and that no packet loss has occurred. Simultaneously, a validity check is performed to determine whether physical parameters such as ball speed, flight distance, and spin rate are within reasonable ranges, and whether the parameters conform to aerodynamic logic consistency. By performing integrity and validity checks on the full set of shot results, abnormal full set of shot results data can be intercepted before the data enters the subsequent parsing stage, preventing the wearable display device 30 from displaying abnormal full set of shot results.

[0024] In step S103, in a specific implementation scenario, after all the ball-hitting result data passes both integrity and validity checks, the valid full-volume ball-hitting result data is parsed, key ball-hitting result fields are extracted, and a standardized ball-hitting data model is constructed. This ball-hitting data model is adapted to the display capabilities of the wearable display device. Subsequently, a ball-hitting data ready event is generated to trigger the subsequent display control process. The ball-hitting data model adapted to the wearable display device achieves decoupling between the ball-hitting monitoring device 10 and the wearable display device 30. The wearable display device 30 does not need to parse the original protocols of different brands of ball-hitting monitoring devices 10; it only receives and parses the unified ball-hitting data model.

[0025] In step S104, in a specific implementation scenario, in response to the ball-hitting data ready event, the ball-hitting data model and corresponding display control commands are sent to the wearable display device according to the type and communication protocol of the wearable display device. This drives the wearable display device to display the ball-hitting result in the ball-hitting data model, achieving visual feedback of the ball-hitting result. The wearable display device 30 can be AR glasses, smartwatches, etc. For example, it can drive AR glasses to overlay and display the ball speed, distance, directional deviation, and other ball-hitting results in the player's field of vision, or drive smartwatches to display simplified data on the watch face, achieving real-time visual feedback of the ball-hitting result.

[0026] The above-mentioned use of the ball-hitting data readiness event as the basis for display control of the wearable display device 30, rather than using the first data packet or ordinary ball-hitting detection event as the direct refresh basis, means that the data pushed to the wearable display device 30 is already verified, structurally complete, and uniformly standardized data, which makes the display refresh timing precisely aligned with the data availability status, thereby improving display accuracy and reliability.

[0027] In step S105, the retention statistics operation includes updating the number of shots, average value, and maximum value, writing to the business history record, uploading to the backend, and saving the current abnormal full shot result data. If the full shot result data fails the integrity or validity check, the current full shot data is determined to be abnormal data. This abnormal data will not be pushed to the wearable display device to avoid overwriting the original valid shot results. This ensures that the player's field of vision continues to display the most recent valid shot result. The above retention statistics operation will not be performed, and the abnormal data will be excluded from the shot statistics database to avoid contaminating the player's historical shot trend analysis and level assessment.

[0028] like Figures 1 to 3 As shown, in an optional embodiment of this application, the total number of shot results data includes a shot result field. Parsing the total number of shot results data to generate a unified shot data model specifically includes the following steps: S201. Parse the byte order of each hit result field of the full hit result data according to the preset field mapping rules, and extract the original hit parameter values. S202. Based on the pre-configured unit system, perform corresponding unit conversion processing on the extracted raw hitting parameter values; S203. The converted values ​​of various hitting parameters are encapsulated according to a preset standardized field structure to generate a unified hitting data model that is compatible with wearable display devices.

[0029] In step S201, the binary encoding methods of each shot result field (such as ball speed, clubhead speed, spin axis angle, etc.) in the full shot result data output by different brands of ball monitoring devices 10 are different. By parsing the received full shot result data field by field according to the preset field mapping rules, the field identifier, data length and byte arrangement order are identified, thereby accurately extracting the original shot parameter values.

[0030] Preset field mapping rules can be obtained through local or backend configuration, and then mapped to a unified shot data model according to the preset field mapping rules of different shot monitoring devices 10. In one embodiment, the shot monitoring device 10 outputs full shot result data using the 0xFF86 Full Data protocol, and the preset field mapping rules configured on the mobile terminal 20 parse the full shot result data. In another optional embodiment, the shot monitoring device 10 can output full shot result data through SDK callbacks, JSON data, key-value pairs, or other communication protocols. The mobile terminal 20 converts original fields such as carryDistance, ball_speed, club_velocity, spin_rpm, and shot_status into unified field identifiers based on the preset field mapping rules to form a shot data model.

[0031] In step S202, the raw ball-hitting parameter values ​​extracted from ball-hitting monitoring devices 10 of different brands may use different unit formats. For example, the ball speed field may be output in meters per second (m / s), miles per hour (mph), or kilometers per hour (km / h), the distance field may be output in meters (m) or yards, and the height unit may be output in feet (ft) and meters (m). The mobile terminal 20 performs corresponding unit conversion processing on various raw ball-hitting parameter values ​​according to the pre-configured target unit format. For example, the distance unit can be switched between yards and meters, the speed unit can be switched between mph, km / h, and m / s, and the height unit can be switched between ft and m, thereby converting the raw ball-hitting result fields into a unified ball-hitting data model.

[0032] In step S203, the converted original hitting parameters, such as ball speed, launch angle, sidespin, backspin, flight distance, and landing point deviation, are encapsulated according to a preset standardized field structure to generate a hitting data model. The hitting data model includes status, carry, smash, clubSpeed, ballSpeed, attackAngle, launchAngle, apex, flyTime, spin, totalDistance, and rollDistance, where status represents the status code; carry represents the landing point distance, in units of... yard; smash indicates shot efficiency; clubSpeed ​​indicates clubhead speed in mph; ballSpeed ​​indicates ball speed in mph; attackAngle indicates shot angle; launchAngle indicates launch angle in degrees; apex indicates the apex of the shot in feet; flyTime indicates flight time in seconds; spin indicates spin speed in rpm; totalDistance indicates the total distance formed by the ball's flight distance and roll distance in yards; rollDistance indicates the roll distance in yards.

[0033] The shot data model is adapted to the display capabilities of the wearable display device 30. The wearable display device 30 can extract the fields to be displayed from the shot data model and display the current shot result in response to display control commands. For example, various raw shot parameter values ​​are encapsulated in JSON format to form the shot data model.

[0034] Through the above steps, the heterogeneous full-volume hitting result data output by different brands of hitting monitoring devices 10 can be uniformly parsed by the mobile terminal 20, with byte order parsing, unit conversion, and standardized encapsulation, and converted into a unified hitting data model adapted to wearable display devices. This hitting data model carries various raw hitting parameter values ​​with a standardized field structure. Therefore, the wearable display device does not need to identify and parse the proprietary data protocols and heterogeneous formats of different brands of hitting monitoring devices 10; it only needs to interface with the hitting data model and display control commands issued by the mobile terminal 20 and present the hitting results, thereby significantly reducing the adaptation development cost and computing resource consumption of the wearable display device.

[0035] In an optional embodiment of this application, the integrity verification of all shot result data specifically includes the following steps: Determine whether the overall byte length of the full ball-hitting result data matches the preset standard length; If the total byte length of the full ball-hitting result data matches the preset standard length, then the full ball-hitting result data is determined to meet the data integrity requirements.

[0036] Specifically, after receiving the full hit result data transmitted by the hit monitoring device 10, the device first reads the total byte length of the full hit result data and compares it with a preset standard length, which is calculated based on the data frame length specified in the current protocol version. For example, the hit monitoring device 10 outputs the full hit result data through the Bluetooth Full Data feature value, which can be UUID 0xFF86. The total length of the complete full hit result data frame is 45 bytes, ranging from Byte0 to Byte44. Byte0 is the status field, and Bytes 1 to Byte44 are 11 32-bit floating-point hit result fields. The byte length of the received full hit result data is compared with 45 bytes. If the byte length of the full hit result data matches 45 bytes, the full hit result data is deemed to meet the data integrity requirements; otherwise, the full hit result data is considered abnormal data, and no hit data ready event is generated. In this way, it is possible to identify data truncation or padding anomalies caused by network packet loss, transmission interruption or equipment failure in a short time without having to continue parsing subsequent field details, thereby significantly reducing unnecessary computational overhead and improving system throughput performance.

[0037] Furthermore, the full set of shot results data includes a status identifier field. The validity of the full set of shot results data is validated, specifically through the following steps: After determining that the full range of shot results data meets the data integrity conditions, the status identifier field at a preset position within the full range of shot results data is read, and the full range of shot results data is identified as valid shot data in combination with the preset status code rules. If all the shot data is considered valid, then the total shot data is deemed to meet the data validity criteria.

[0038] Specifically, after determining that the complete set of shot results data meets the integrity requirements, a status identifier field is read from a preset location within the complete set of shot results data. This status identifier field is generated by the shot monitoring device 10 at the acquisition end based on the shot event triggering logic. The mobile terminal 20 parses the aforementioned status identifier field in conjunction with preset status code rules to identify whether the current complete set of shot results data belongs to valid shot data. In this way, the shot event determination logic of the shot monitoring device 10 can be directly reused at the data parsing level, eliminating the need to repeatedly deploy complex trajectory reconstruction algorithms on the mobile terminal 20 to determine whether the complete set of shot results data is valid, significantly reducing the computational load and response latency of the mobile terminal 20.

[0039] When the status identifier field matches the status code corresponding to valid shot data after parsing, the entire set of shot results data is deemed to meet the validity criteria, allowing it to enter the parsing and shot data model generation process in S103. If the status identifier field is an invalid shot code, such as a blank swing, a mis-spin, or exceeding the distance limit, the data conditions are deemed not met, and the non-refreshing and non-retention processing in S105 is executed. This ensures the timely removal and interception of invalid data, guaranteeing the purity of the shot statistics database and improving the accuracy and reliability of the shot results displayed by the wearable display device 30.

[0040] In an optional embodiment of this application, the preset status code rules include a first preset status code, a second preset status code, and a third preset status code. The process of identifying whether all hit result data constitutes valid hit data by combining the preset status code rules specifically includes the following steps: If the status identifier field at a preset position within the full hit result data matches the first preset status code, then the full hit result data is determined to be valid hit data. If the status identifier field at the preset position in the full shot result data matches the second preset status code, then the current shot is determined to be a miss or a blank shot. If the status identifier field at the preset position in the full ball-hitting result data matches the third preset status code, it is determined that the current ball-hitting distance exceeds the upper limit. If the status identifier field at the preset position in the full ball-hitting result data fails to match the first preset status code, the second preset status code, and the third preset status code, a data reception error message will be displayed.

[0041] Specifically, the first, second, and third preset status codes can be set according to actual needs. For example, the first preset status code can be set to 1, the second preset status code to 2, and the third preset status code to 3. In a specific implementation scenario, the total length of the complete full-scale shot result data frame is 45 bytes, ranging from Byte0 to Byte44. Byte0 is the status identifier field, and Bytes 1 to Byte44 are 11 32-bit floating-point shot result fields. The mobile terminal 20 parses the data in little-endian order. When the byte length of the full-scale shot result data meets the 45-byte requirement, the mobile terminal 20 reads the status identifier field. If Byte0=1, it determines that the full-scale shot result data is valid shot data, and then performs parsing operations to generate a shot data model and a shot data ready event. When Byte0=2, it indicates that the current shot is a miss or a blank shot. When Byte0=3, it indicates that the current shot distance exceeds the upper limit. When Byte0 is not 1, 2, or 3, it can prompt "Data reception error, please re-shot".

[0042] By using the aforementioned preset status code rules, the mobile terminal 20 does not need to perform complex trajectory reconstruction or physical parameter inversion on all ball hitting results data. It only needs to read the status identifier field at the preset position in the full ball hitting results data and compare and match it with the enumerated status code rules. This allows it to quickly identify whether the full ball hitting results data belongs to valid ball hitting data in a short time, thereby significantly shortening the data verification path, reducing the computing resource consumption of the mobile terminal 20, and improving the real-time performance of the overall data flow and the system response speed.

[0043] Furthermore, the shot results indicate that the control method also includes the following steps: When the current shot is determined to be a miss or a missed shot, or when the current shot distance exceeds the limit, the wearable display device 30 is controlled to execute the corresponding abnormal prompt.

[0044] Specifically, when the current shot is determined to be a miss or a blank shot, an error message is displayed: "The current shot is a miss or a blank shot, please try again." When the current shot distance is determined to be beyond the limit, an error message is displayed: "The current shot distance exceeds the limit, please try again."

[0045] Optionally, the error notification can be delivered via voice prompts, short-term display prompts, or other methods. The notification can be provided by the mobile terminal 20 communicating with the wearable display device 30, or by the wearable display device 30 itself. For example, if the wearable display device 30 is in a screen-on state, an error notification is displayed for a preset duration; in one embodiment, the preset duration is 2.5 seconds. If the wearable display device 30 is in a screen-off state, a voice prompt is provided.

[0046] In an optional embodiment of this application, the ball-hitting result display control method further includes the following steps: If the full hit result data does not meet the data integrity conditions, the full hit result data output by the hit monitoring device 10 will be actively reread, or the hit monitoring device 10 will be actively requested to output the full hit result data. If the maximum number of retries is reached and the complete data of the shot is still not obtained, the data transmission of the shot is deemed to have failed, and a data reception error message is displayed.

[0047] Specifically, when the complete ball-hitting result data is determined not to meet the data integrity requirements, an automatic retry mechanism is triggered. The mobile terminal 20 can choose to reread the data from its local receive buffer or actively send a data retransmission request command to the ball-hitting monitoring device 10. The retry process follows a preset interval strategy, such as waiting 100ms after the first failure, waiting 100ms after the second failure, etc., until a valid data packet that meets the integrity requirements is obtained or the maximum number of retries is reached. When the preset maximum number of retry receptions is reached, such as 3 times if the complete ball-hitting result data that meets the data integrity requirements is still not obtained, the ball-hitting data transmission is determined to have failed, the retry process is terminated, and a data reception error prompt can be executed, such as "Data reception error, please hit the ball again". In this way, the proactive retry mechanism can automatically repair data transmission problems caused by momentary network fluctuations or occasional device response delays without disrupting the players' training rhythm. This transforms single, occasional anomalies into a recoverable normal process, significantly improving data transmission success rate and system robustness, and avoiding packet loss. The maximum number of retries prevents the system from falling into an infinite retry loop, avoiding continuous occupation of communication resources that would lead to a backlog of subsequent shot data. Proactive push notifications of anomalies ensure that players are promptly aware of the current data unavailability status.

[0048] The maximum number of retry receptions can be set according to requirements.

[0049] Furthermore, the shot results indicate that the control method also includes the following steps: When multiple push reports from the ball-hitting monitoring device 10 are received within a preset time window, the content of each push report is compared. If the content of multiple push reports is completely identical, it is determined to be duplicate data, and only one push report is selected as the full ball hitting result data; If the comparison content of multiple push reports is different from each other, and each push report data meets the data conditions of completeness and validity, then they are recorded as different valid full-volume ball-hitting result data.

[0050] Specifically, when multiple push notifications from the ball-hitting monitoring device 10 are received within a preset time window, such as 3 seconds, the content of each push notification is compared byte by byte. This scenario typically occurs when the ball-hitting monitoring device 10 triggers multiple notifications due to network protocol retransmission mechanisms, device firmware jitter, or rapid, continuous ball hits by a player, resulting in a single swing triggering multiple notifications. By aggregating multiple push notifications within the preset time window and performing content comparison, the system can handle occasional retransmissions or high-frequency continuous ball hits from the ball-hitting monitoring device 10 in one go, balancing network latency tolerance and real-time response, and improving the system's throughput performance and scheduling efficiency under high-concurrency data influx scenarios.

[0051] When the comparison results show that multiple push-reported data are completely identical, with a data frame length of 45 bytes and a comparison range of Byte0 to Byte44; if they are completely identical, they are determined to be duplicate data. Only one push-reported data is selected as the full shot result data for subsequent processing, and the remaining duplicate data is directly discarded. This effectively avoids the same shot result being parsed multiple times, generated multiple times, and pushed to the wearable display device multiple times. It also prevents the same shot data from repeatedly flashing and covering the player's field of vision or the same shot from being repeatedly counted in the statistical database, thereby ensuring the stability of the display interface and the accuracy of historical data. At the same time, the deduplication operation reduces the redundant calculation overhead of the subsequent S102 to S104 process, improving overall processing efficiency and device battery life.

[0052] When the comparison results show that the content of multiple push reports are different, and each push report passes the integrity and validity checks, each data is recorded as a different valid full-volume shot result data, and then enters the subsequent parsing, model generation and display push process in sequence. In this way, multiple legal shots completed by the player in a very short period of time (such as hitting multiple balls quickly and continuously in golf chipping practice) can be accurately identified, ensuring that each valid shot gets an independent and complete processing link and obtains an effective visualization display.

[0053] Optionally, the preset time window can be set according to requirements. For example, the preset time window is set to 3 seconds.

[0054] In an optional embodiment of this application, the ball-hitting result display control method further includes the following steps: The system controls the wearable display device to provide a main results display page, a parameter details page, and a data statistics page, and drives the wearable display device to respond to page switching operation commands, switching between the main results display page, the parameter details page, and the data statistics page. Once the ball-hitting data is ready event is generated, the wearable display device is controlled to automatically switch and reset the current display page to the main results display page.

[0055] Specifically, the main results page primarily displays core shot results, such as Carry (air travel distance), Total (total shot distance), and Club (club parameters), which are key indicators that intuitively reflect shot quality. The parameter details page primarily displays specific technical parameters, such as Apex (shot apex), Smash (shot efficiency coefficient), Club Speed ​​(clubhead speed), Ball Speed ​​(ball speed), Launch Angle (launch angle), Roll (roll distance after landing), Attack Angle (angle of attack), Flight Time (flight duration), and Spin Rate (spin rate), among other detailed data. The data statistics page primarily displays aggregated statistical indicators such as Shot (single shot record), Avg (average), and Max (maximum value). The wearable display device 30 can respond to players' voice commands, gesture recognition, or physical button triggers to switch between the main results display page, parameter details page, and data statistics page, meeting players' different visual information needs. For example, players can quickly confirm their hitting performance by viewing the main results display page, understand the various hitting parameters by viewing the parameter details page, and evaluate their progress trend by viewing the data statistics page.

[0056] Once the system generates a ready-to-play event for shot data, regardless of whether the wearable display is currently on the parameter details page or the data statistics page, the page switching and reset logic is automatically triggered, forcing the currently displayed page back to the main results display page. This ensures that after each new shot, the player's attention is immediately focused on the core shot result, avoiding delays in perceiving new data due to the device remaining on the history details page or statistics page. Simultaneously, the automatic reset eliminates the burden of manually switching back to the main page, especially during continuous high-frequency shot training. Players can instantly obtain the latest feedback without needing to remember the current page state or perform additional interactions, thus improving the user experience.

[0057] In an optional embodiment of this application, the wearable display device 30 can report head posture status via cmd="Head", where 1 indicates Head up and 0 indicates Head down. Head up can serve as a display permission condition, notifying the mobile terminal 20 to allow display. The club can be selected in advance by the user on the mobile terminal 20; the wearable display device 30 can also display a club selection list by long-pressing the touchpad. The club selection list data comes from the mobile terminal 20, and the wearable display device 30 notifies the mobile terminal after the user makes a selection. Club information can be associated with the current shot result and can affect statistics such as Shot, Avg, and Max.

[0058] This invention also provides a shot result display and control system, such as... Figures 1 to 3 As shown, the ball-hitting result display control system includes a ball-hitting monitoring device 10, a mobile terminal 20, and a wearable display device 30.

[0059] The ball-hitting monitoring device 10 is used to collect various raw measurement parameters during the golf ball-hitting process and output full ball-hitting result data.

[0060] The mobile terminal 20 is communicatively connected to the ball-hitting monitoring device 10, and is used to execute the ball-hitting result display control method described above. The ball-hitting result display control method has been described in detail in the foregoing embodiments and will not be repeated here. The mobile terminal 20 can be a mobile phone, tablet computer, or other device with communication and data processing capabilities.

[0061] The wearable display device 30 is communicatively connected to the mobile terminal 20. The wearable display device 30 receives the ball-hitting data model and display control commands, and displays the result of the current shot based on the ball-hitting data model. The wearable display device 30 can be AR glasses, a smartwatch, a head-mounted display, or similar devices. As the display execution end, the wearable display device 30 does not parse the original protocol of the ball-hitting monitoring device 10, and displays the current shot result in a lightweight manner.

[0062] The shot result display control system of this invention works collaboratively between the shot monitoring device 10, the mobile terminal 20, and the wearable display device 30. The shot monitoring device 10 is responsible for collecting various raw measurement parameters during the golf shot process. The mobile terminal 20 centrally performs complex processing logic such as data verification, parsing, and shot data model generation. The wearable display device 30 focuses on real-time visual feedback. By offloading computationally intensive tasks from the resource-constrained wearable display device to the more powerful mobile terminal 20, the wearable display device 30 does not need to parse all the raw shot result data from different shot monitoring devices 10. It only needs to receive a unified and adapted shot data model and display the current shot result, thus reducing the burden of raw protocol parsing on the wearable display device 30. After receiving the full ball-hitting result data output by the ball-hitting monitoring device 10, the mobile terminal 20 first performs a dual verification of the completeness and validity of the received full ball-hitting result data. Only after the verification meets the data conditions will a unified ball-hitting data model adapted to the wearable display device be constructed, and a ball-hitting data ready event will be triggered before it is pushed to the wearable display device 30 for display. For full ball-hitting result data with abnormal verification, the original valid ball-hitting result of the wearable display device 30 is maintained, and no data retention and statistical operation is performed. This prevents abnormal full ball-hitting result data from overwriting the correct screen and polluting local statistics and backend records, thereby improving the accuracy and reliability of the ball-hitting result display of the wearable display device 30.

[0063] It should be understood that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit them. Those skilled in the art can modify the technical solutions described in the above embodiments, or make equivalent substitutions for some of the technical features; and all such modifications and substitutions should fall within the protection scope of the appended claims of the present invention.

Claims

1. A method for displaying and controlling the result of a shot, characterized in that, include: Receive all ball-hitting result data output by the ball-hitting monitoring equipment; The completeness and validity of the full set of shot results data are verified. Once the full set of shot results data meets the data conditions for completeness and validity, the full set of shot results data is parsed to generate a unified shot data model adapted to wearable display devices, and a shot data ready event is generated. Based on the ball-hitting data ready event, the ball-hitting data model and display control command are sent to the wearable display device to drive the wearable display device to display the current ball-hitting result based on the ball-hitting data model; If the full-volume shot result data does not meet the data conditions for completeness and validity, the original valid shot results on the wearable display device will not be refreshed using the current abnormal full-volume shot result data, and no retention or statistical operation will be performed on the current abnormal full-volume shot result data.

2. The method for displaying and controlling the ball striking result according to claim 1, characterized in that, The total number of shot results data includes a shot result field. The process of parsing the total number of shot results data to generate a unified shot data model specifically includes the following steps: According to the preset field mapping rules, the byte order of each field of the full ball hitting result data is parsed to extract the original ball hitting parameter values. Based on the pre-configured unit system, the extracted raw hitting parameter values ​​are converted to the corresponding units. The converted values ​​of various hitting parameters are encapsulated according to a preset standardized field structure to generate a unified hitting data model that is compatible with wearable display devices.

3. The method for displaying and controlling the ball striking result according to claim 1, characterized in that, The integrity verification of the full set of shot results data specifically includes the following steps: Determine whether the overall byte length of the full ball-hitting result data matches the preset standard length; If the overall byte length of the full ball-hitting result data matches the preset standard length, then the full ball-hitting result data is determined to meet the data integrity requirements.

4. The method for displaying and controlling the ball striking result according to claim 3, characterized in that, The full-volume shot result data includes a status identifier field. The validity verification of the full-volume shot result data specifically includes the following steps: After determining that the full range of shot results data meets the data integrity conditions, the status identifier field at a preset position within the full range of shot results data is read, and the full range of shot results data is identified as valid shot data in combination with preset status code rules. If the total number of shot results data is valid shot data, then the total number of shot results data is determined to meet the data conditions for validity.

5. The method for displaying and controlling the shot result according to claim 4, characterized in that, The preset status code rules include a first preset status code, a second preset status code, and a third preset status code. The step of combining the preset status code rules to identify whether the total number of shot results data belongs to valid shot data specifically includes the following steps: If the status identifier field at a preset position in the full-volume hit result data matches the first preset status code, then the full-volume hit result data is determined to be valid hit data. If the status identifier field at a preset position in the full shot result data matches the second preset status code, then the current shot is determined to be a miss or a blank shot. If the status identifier field at a preset position within the full ball-hitting result data matches the third preset status code, then it is determined that the current ball-hitting distance exceeds the upper limit. If the status identifier field at a preset position in the full ball-hitting result data fails to match the first preset status code, the second preset status code, and the third preset status code, a data reception error message will be displayed.

6. The method for displaying and controlling the shot result according to claim 5, characterized in that, The method for displaying and controlling the ball striking results also includes the following steps: When the current shot is determined to be a miss or a missed shot, or when the current shot distance exceeds the limit, the wearable display device is controlled to execute the corresponding abnormal prompt.

7. The method for displaying and controlling the ball striking result according to claim 1, characterized in that, The method for displaying and controlling the ball striking results also includes the following steps: If the full hit result data does not meet the data integrity condition, the full hit result data output by the hit monitoring device will be actively reread, or the hit monitoring device will be actively requested to output the full hit result data. If the maximum number of retries is reached and the complete data of the shot is still not obtained, the data transmission of the shot is deemed to have failed, and a data reception error message is displayed.

8. The method for displaying and controlling the ball striking result according to claim 7, characterized in that, The method for displaying and controlling the ball striking results also includes the following steps: When multiple push reports from the ball-hitting monitoring device are received within a preset time window, the content of each push report is compared. If the comparison content of multiple push-reported data is completely identical, it is determined to be duplicate data, and only one push-reported data is selected as the full ball hitting result data; If the comparison content of multiple push reports is different from each other, and each push report data satisfies the data conditions of completeness and validity, then they are recorded as different valid full-volume ball-hitting result data.

9. The method for displaying and controlling the shot result according to claim 1, characterized in that, The method for displaying and controlling the ball striking results also includes the following steps: The system controls the wearable display device to provide a main results display page, a parameter details page, and a data statistics page, and drives the wearable display device to respond to page switching operation commands, switching between the main results display page, the parameter details page, and the data statistics page. Once the ball-hitting data is ready event is generated, the wearable display device is controlled to automatically switch and reset the current display page to the main results display page.

10. A ball-hitting result display and control system, characterized in that, include: Shot monitoring equipment is used to collect various raw measurement parameters during the golf shot process and output full shot result data; A mobile terminal is communicatively connected to the ball-hitting monitoring device, and the mobile terminal is used to execute the ball-hitting result display control method as described in any one of claims 1-9; A wearable display device is communicatively connected to the mobile terminal. The wearable display device is used to receive the ball-hitting data model and display control commands, and to display the ball-hitting result based on the ball-hitting data model.

Images