Methods, equipment and storage media for sports training data management

Abstract

This application discloses a method, device, and storage medium for managing sports training data, relating to the field of data management technology. The sports training data management method is applied to a server and includes: receiving first training instruction data sent by a first terminal device; sending second training instruction data to at least one target wearable device connected to the second terminal device via at least one second terminal device, so that the target wearable device can collect sports training data according to the second training instruction data, wherein the second training instruction data is the same as or determined based on the first training instruction data; receiving sports training data uploaded by the second terminal device, wherein the sports training data is collected by the target wearable device and sent to the second terminal device. This achieves stable issuance of unified training instructions to numerous wearable devices and reliable collection and centralized management of sports training data.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a method, device and storage medium for managing sports training data. Background Technology

[0002] Existing sports training data management methods mainly rely on single-point connection, that is, one terminal device connects to multiple wearable devices. The core limitation of this technology is that the effective connection range of traditional Bluetooth technology is too short. As a result, when conducting team training in large and wide venues such as football fields, basketball courts, and baseball fields, the stability of the connection between the terminal device and the wearable device cannot be guaranteed, and the communication connection between the devices is frequently interrupted.

[0003] At the same time, the number of wearable devices that a single terminal device can connect to at the same time is also very limited. This, combined with its limited connection range, further severely restricts the application effect of existing sports training data management methods in large-scale team training scenarios where many athletes need to wear devices at the same time. This makes it impossible for terminal devices to meet the requirements of efficient and stable management of large amounts of sports training data in a wide space.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a method, device and storage medium for sports training data management, which aims to solve the problem that existing sports training data management methods cannot meet the requirements of efficient and stable management of large amounts of sports training data in a wide space.

[0006] To achieve the above objectives, this application proposes a method for managing sports training data, which is applied to a server and includes:

[0007] Receive the first training instruction data sent by the first terminal device;

[0008] Through at least one second terminal device, second training instruction data is sent to at least one target wearable device connected to the second terminal device, so that the target wearable device can collect exercise training data according to the second training instruction data, wherein the second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data;

[0009] The device receives exercise training data uploaded by the second terminal device, wherein the exercise training data is collected by the target wearable device and sent to the second terminal device.

[0010] In one embodiment, the sports training data management method further includes:

[0011] Receive a lobby creation request initiated by a third terminal device, and create a virtual lobby according to the lobby creation request;

[0012] The system receives a lobby join request from at least one fourth terminal device. After verifying the lobby join request, the system adds the fourth terminal device to the virtual lobby corresponding to the lobby join request. The first terminal device and the second terminal device are terminal devices in the same virtual lobby.

[0013] In one embodiment, the first training instruction data includes training plan data, and the exercise training data management method further includes:

[0014] The device receives wearable device information sent by a terminal device in the target virtual hall, wherein the target virtual hall is the virtual hall to which the first terminal device belongs, and the wearable device information is obtained by the corresponding terminal device by scanning the surrounding wearable devices via Bluetooth.

[0015] Based on the wearable device information, at least one target wearable device that is compatible with the training plan data is determined;

[0016] Device connection information is sent to at least one terminal device in the target virtual hall so that the terminal device receiving the device connection information can establish a connection with the target wearable device according to the device connection information.

[0017] In one embodiment, the step of sending device connection information to at least one terminal device in the target virtual lobby includes:

[0018] For each target wearable device, the terminal device with the strongest signal strength between itself and the target wearable device in the target virtual hall is identified as the target terminal device;

[0019] The device connection information corresponding to the target wearable device is sent to the target terminal device so that the target terminal device can establish a connection with the target wearable device based on the device connection information.

[0020] In one embodiment, the second training instruction data includes sensor configuration information, which is used to instruct the target wearable device to configure the parameters of the sensors, which are used to collect the exercise training data.

[0021] Furthermore, to achieve the above objectives, this application also proposes a method for managing sports training data, which is applied to a first terminal device and includes:

[0022] Obtain the first training instruction data;

[0023] The first training instruction data is sent to the server so that the server can send the second training instruction data to at least one target wearable device connected to the second terminal device through at least one second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data and upload it to the server. The second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data.

[0024] In one embodiment, the sports training data management method further includes:

[0025] In response to a data query request, the system retrieves and outputs the exercise training data corresponding to the data query request from the server.

[0026] Furthermore, to achieve the above objectives, this application also proposes a method for managing sports training data, which is applied to a second terminal device and includes:

[0027] Send second training instruction data to the target wearable device connected to the second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data. The second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data. The first training instruction data is received by the server from the first terminal device.

[0028] Receive exercise training data sent by the target wearable device;

[0029] The exercise training data is uploaded to the server.

[0030] In addition, to achieve the above objectives, this application also proposes a sports training data management device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the sports training data management method as described above.

[0031] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the sports training data management method described above.

[0032] One or more technical solutions proposed in this application have at least the following technical effects:

[0033] This invention implements a distributed sports training data management scheme by connecting multiple terminal devices via a server, and at least one wearable device via each terminal device. The server receives first training instruction data from a first terminal device and sends second training instruction data to at least one target wearable device connected to the second terminal device. The target wearable device then collects exercise training data according to the second training instruction data and sends the exercise training data to the second terminal device, which then uploads it to the server. In this distributed sports training data management scheme, training instruction data sent by the user via a terminal device can be relayed to various wearable devices via the server and terminal devices. Exercise training data collected by each wearable device can also be uploaded to the server for centralized management via the terminal devices. Compared to the method of connecting wearable devices to a single terminal device, the distributed sports training data management scheme proposed in this application can connect and manage a larger number of wearable devices. It can also configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal devices as needed. This avoids the problems of frequent disconnection between devices due to the short effective distance of Bluetooth in the traditional single-point connection mode, as well as the limited number of single terminal devices that cannot support large teams for training. Thus, it enables the stable issuance of unified training instructions to numerous wearable devices and the reliable collection and centralized management of sports training data in vast venues such as football fields. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0035] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 A flowchart illustrating the first embodiment of the sports training data management method of this application;

[0037] Figure 2 This is a schematic diagram of a scenario provided for the first embodiment of the sports training data management method of this application;

[0038] Figure 3 A flowchart illustrating the second embodiment of the sports training data management method of this application;

[0039] Figure 4A flowchart illustrating the third embodiment of the sports training data management method of this application;

[0040] Figure 5 This is a flowchart illustrating the fourth embodiment of the sports training data management method of this application.

[0041] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the sports training data management method in the embodiments of this application.

[0042] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0043] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0044] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0045] The main solution of this application embodiment is as follows: A server connects multiple terminal devices, and each terminal device connects to at least one wearable device. The server receives first training instruction data sent by a first terminal device, and through at least one second terminal device, sends second training instruction data to at least one target wearable device connected to the second terminal device. This allows the target wearable device to collect exercise training data according to the second training instruction data and send the exercise training data to the second terminal device, which then uploads it to the server. This achieves a distributed exercise training data management scheme. In this distributed exercise training data management scheme, training instruction data sent by the user through the terminal device can be relayed to various wearable devices via the server and terminal devices. Exercise training data collected by each wearable device can also be uploaded to the server for centralized management via the terminal device. Compared to the method of connecting wearable devices to a single terminal device, the distributed sports training data management scheme proposed in this application can connect and manage a larger number of wearable devices. It can also configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal devices as needed. This avoids the problems of frequent disconnection between devices due to the short effective distance of Bluetooth in the traditional single-point connection mode, as well as the limited number of single terminal devices that cannot support large teams for training. Thus, it enables the stable issuance of unified training instructions to numerous wearable devices and the reliable collection and centralized management of sports training data in vast venues such as football fields.

[0046] Reference Figure 1 , Figure 1This is a flowchart illustrating the first embodiment of the sports training data management method of this application.

[0047] In this embodiment, the sports training data management method is applied to the server side. This embodiment does not limit the deployment method of the server side; the server side can be deployed in the cloud or on a traditional server. The sports training data management method includes steps S10~S30:

[0048] Step S10: Receive the first training instruction data sent by the first terminal device.

[0049] The terminal device can establish a communication connection with the server to send training instruction data. Hereinafter, the training instruction data sent by the terminal device to the server will be referred to as the first training instruction data, to distinguish it from the training instruction data sent to the wearable device, and the terminal device sending the first training instruction data will be referred to as the first terminal device for distinction. The method by which the terminal device establishes a communication connection with the server is not limited in this embodiment. For example, a client corresponding to the server can be installed on the terminal device, and the terminal device establishes a communication connection with the server by running the client. The terminal device can be an electronic device such as a mobile phone, tablet computer, or laptop computer; specific devices are not limited in this embodiment.

[0050] The first training instruction data may be uploaded by the user to the first terminal device, or it may be generated by the first terminal device based on the data uploaded by the user or the triggered instruction. In this embodiment, the method of obtaining the first training instruction data in the first terminal device is not limited.

[0051] The first training instruction data can be training-related instruction data, and the specific data content of the first training instruction data is not limited in this embodiment. In a feasible implementation, the first training instruction data may include control commands, such as training start and training end control commands, used to instruct the wearable device to start collecting data, stop collecting data, and perform other operations. In a feasible implementation, when the wearable device has multiple sensors (such as a heart rate sensor, accelerometer sensor, etc.), the first training instruction data may include information indicating which sensors the wearable device uses to collect data, to suit the different sensor data requirements of different training programs. In one feasible embodiment, the first training instruction data may include sensor configuration information to instruct the wearable device to configure corresponding sensor parameters. The sensor configuration information may be specific sensor parameter values ​​or other information that indicates what parameter values ​​the wearable device should use; this embodiment is not limited. For example, the wearable device or server may set parameter values ​​for various sensors corresponding to different sports roles or different sports types. The sensor configuration information may include sports roles and / or sports types, allowing the wearable device or server to match the sensor parameter values ​​corresponding to those sports roles and / or sports types, so that the wearable device can configure sensor parameters according to the matched sensor parameters. In one feasible embodiment, the first training instruction data may include information indicating which type of wearable device to use. Types of wearable devices include, for example, wristbands, headbands, ECG devices, etc., to suit the needs of different training programs for different types of wearable devices. In one feasible embodiment, the first training instruction data may include a status query command to query the current status of each wearable device. The status of the wearable device may include, for example, device connection status, sensor configuration status, data acquisition status, etc.

[0052] It is understood that the above are only a few examples of the first training instruction data. In this embodiment, the specific type of the first training instruction data is not limited. The first training instruction data may include any one or more of the above types of data, or it may include any one or more of the above types of data combined with other types of data.

[0053] In one feasible implementation, the server can categorize the received first training instruction data into different priorities based on their urgency, for example, into four priorities: P0 (emergency stop), P1 (training control), P2 (configuration change), and P3 (status query). P0 has the highest priority. Instructions instructing the wearable device to urgently stop data acquisition operations are assigned to P0 priority; data controlling data acquisition-related operations on the wearable device is assigned to P1 priority; data indicating configuration changes (e.g., changing wearable device type, sensor type, sensor parameters, etc.) is assigned to P2 priority; and data indicating queries about the wearable device's status is assigned to P3 priority. The server can use a priority queue data structure to manage the command sequence, ensuring that high-priority first training instruction data is processed first. The server can assign a globally unique MessageID to each first training instruction data for message tracking and deduplication.

[0054] In one feasible implementation, the first training instruction data and the data transmitted between each terminal device and the server in each step of the method in subsequent embodiments can all be serialized using Protocol Buffers (protobuf). Protobuf reduces data size by 60% compared to JSON (JavaScript Object Notation, a lightweight data exchange format). Protobuf is a language-neutral, platform-neutral, and scalable structured data serialization mechanism used for efficient data storage and transmission. The serialized message includes a message header (type, length, checksum) and a message body. For large messages (e.g., exceeding 1KB), gzip compression can be used to further reduce network transmission overhead. During data transmission, an acknowledgment-based transmission mechanism can be used. The sender starts a timer (e.g., a 500ms timeout) after sending the message, waiting for the receiver's acknowledgment. If no acknowledgment is received within the timeout period, exponential backoff retransmission is performed, up to a maximum of three retransmissions. The data sender can use a sliding window protocol to control the transmission rate, with the window size dynamically adjusted according to network conditions.

[0055] In this embodiment, to avoid the problem that the coach's terminal device is limited by its own Bluetooth connection range and number in the traditional single-point connection method, and cannot directly and stably issue unified training instructions to the wearable devices worn by all the athletes scattered in the field at the same time, the server acts as a central control node to uniformly receive the training instruction data sent by the terminal devices. This can smoothly support the centralized reception and management of the training intentions of the entire training team in a large open field environment, thereby laying the foundation for the subsequent distribution and collaborative execution of training instruction data.

[0056] Step S20: Send second training instruction data to at least one target wearable device connected to the second terminal device through at least one second terminal device, so that the target wearable device can collect exercise training data according to the second training instruction data, wherein the second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data.

[0057] In a specific implementation, the server can directly forward the first training instruction data to the target wearable device through the second terminal device. In this case, the second training instruction data is the same as the first training instruction data. For example, if the first training instruction data is a control command, it can be directly forwarded by the server. Alternatively, the server or the second terminal device can convert the first training instruction data into second training instruction data and then send it to the target wearable device. For example, if the first training instruction data is a protocol file, a further data conversion process of parsing and processing is required before it can be sent to the target wearable device. That is, the second training instruction data can be data that is different from the first training instruction data, as determined based on the first training instruction data.

[0058] It should be noted that if the second training instruction data is determined based on the first training instruction data, the conversion process from the first training instruction data to the second training instruction data can be performed on the server side, that is, the second terminal device directly forwards the second training instruction data sent by the server to the corresponding target wearable device; or, the conversion process can be performed on the second terminal device, that is, the second terminal device first receives the first training instruction data sent by the server, then processes the first training instruction data to obtain the second training instruction data, and then sends the second training instruction data to the corresponding target wearable device.

[0059] The target wearable device is the wearable device to which second training instruction data needs to be sent. The server can send the second training instruction data to the target wearable device through a terminal device (hereinafter referred to as the second terminal device for distinction) that is communicatively connected to the target wearable device. It should be noted that, in specific embodiments, the first terminal device may only be used to upload training instruction data to the server, in which case the first terminal device is different from the second terminal device; or, the first terminal device may be used to upload training instruction data to the server, and also undertake the function of forwarding training instruction data, and can establish a connection with the wearable device, in which case the first terminal device may also be one of the second terminal devices.

[0060] In this embodiment, since the server itself does not have the ability to directly connect to wearable devices over long distances and with multiple devices, and there are coverage blind spots and upper limits on the connection of a single terminal device to wearable devices in large open spaces, the server uses at least one second terminal device deployed in the space as a relay to send second training instruction data that is consistent with or derived from the first training instruction data to the target wearable devices within their respective physical connection ranges. This avoids the problem that a single terminal device cannot communicate stably with the remote wearable device due to the short effective connection range of Bluetooth technology, and that its own limited number of Bluetooth connections cannot support the simultaneous access of all wearable devices in the entire large team. It effectively overcomes the limitations of short coverage range and small number of single-point connections, ensuring that the first training instruction data can be stably and reliably transmitted to the target wearable devices in a wide space.

[0061] Step S30: Receive the exercise training data uploaded by the second terminal device, wherein the exercise training data is collected by the target wearable device and sent to the second terminal device.

[0062] The sports training data is real-time quantitative information that reflects the athlete's physiological or athletic state, collected by the target wearable device through its built-in sensors during the sports training process based on the second training instruction data it receives. This includes specific indicators such as heart rate, acceleration, displacement trajectory, or cadence. The sports training data is collected, generated, and transmitted by the target wearable device to the second terminal device, which then uploads it to the server for training analysis.

[0063] In this embodiment, the sports training data collected by the target wearable device is first transmitted to a second terminal device with which it has a stable short-range connection, and then uploaded to the server by the second terminal device. This avoids the problem of sports training data loss or transmission interruption caused by unstable connection when a single terminal device directly attempts to collect data from all the scattered and potentially far-distance wearable devices in a wide area, as well as the problem of being unable to receive a large amount of sports training data due to the limitation on the number of connections between a single terminal device and the wearable device. It cleverly utilizes the stable near-field connection established between the second terminal device and the wearable device to ensure the reliability of data transmission, and breaks through the bottleneck of the number of data received from a single point by sharing the data collection task with multiple second terminal devices. This allows the training data of a large team in a wide area to be completely and reliably gathered to the server for unified management.

[0064] In one feasible embodiment, the sports training data management method further includes steps S40-S50:

[0065] Step S40: Receive a lobby creation request initiated by a third terminal device, and create a virtual lobby according to the lobby creation request.

[0066] Terminal devices can initiate a lobby creation request to the server. The server then creates a virtual lobby based on the request. Other terminal devices can initiate a lobby join request to join the existing virtual lobby. Terminal devices within the same virtual lobby can interact with the server to send training instruction data to wearable devices connected to the terminal devices in the virtual lobby and collect the wearable devices' exercise training data to achieve exercise training data management.

[0067] Any terminal device can initiate a lobby creation request to the server. To distinguish them, the terminal device that initiates the lobby creation request to the server is referred to as a third terminal device.

[0068] The server can add third-party terminal devices to the virtual lobby.

[0069] The first terminal device and the second terminal device are terminal devices in the same virtual hall. That is, the first terminal device and the second terminal device are terminal devices in the same virtual hall that have been created before. The hall creation request for creating the virtual hall can be initiated by the first terminal device or by one of the second terminal devices. In this embodiment, there is no restriction.

[0070] In a specific implementation, the server can create a virtual lobby based on the lobby creation request. Specifically, it can generate a unique ID for the virtual lobby to distinguish different virtual lobbyes, and can also create a lobby record corresponding to the virtual lobby. The lobby record is used to record information related to the virtual lobby, such as the ID of the virtual lobby, the creation time, expiration time (e.g., 4 hours), and a list of participating nodes. Terminal devices can act as participating nodes in the virtual lobby. The list of participating nodes can be used to record information related to the terminal devices that join the virtual lobby, such as the IDs and node types of each participating node. Different node types of participating nodes can correspond to different functions. For example, the node type of a participating node can be an edge node or a control node, or it can be both edge node and control node. Edge nodes are used to connect to wearable devices, forward data to wearable devices, and obtain data from wearable devices and upload it to the server. Control nodes are used to send training instruction data to the server so that the server can distribute training instruction data to each wearable device connected to the edge node in the same virtual lobby.

[0071] There are many ways to generate the ID of the virtual lobby, and this embodiment does not impose any restrictions. For example, the Snowflake Algorithm can be used to generate the ID. The length of the ID of the virtual lobby can be set as needed, and this embodiment does not impose any restrictions. For example, it can be set to 6 characters.

[0072] For example, a coach can log in to the client using a mobile phone (hereinafter referred to as the coach's mobile phone) and initiate a lobby creation request to the server through the client. The server can use the Snowflake algorithm to generate a globally unique lobby ID, and can combine a timestamp and a random number to ensure the uniqueness and timeliness of the lobby ID; the server can create a corresponding lobby record in the database, including the lobby ID, creation time, expiration time (e.g., 4 hours), and a list of participating nodes (used to record the node ID, node type, etc. of each participating node).

[0073] Step S50: Receive a lobby join request sent by at least one fourth terminal device. After verifying the lobby join request, add the fourth terminal device to the virtual lobby corresponding to the lobby join request. The first terminal device and the second terminal device are terminal devices in the same virtual lobby.

[0074] The fourth terminal device refers to other terminal devices that request to join the virtual lobby.

[0075] After receiving a lobby join request from the fourth terminal device, the server can verify the request. The specific verification method is not limited in this embodiment.

[0076] After the server verifies the request to join the lobby, it can add the fourth terminal device to the virtual lobby corresponding to the request. For example, it can add the fourth terminal device to the virtual lobby corresponding to the lobby ID in the request. In a specific implementation, adding the fourth terminal device to the virtual lobby can be done by adding the fourth terminal device to the list of participating nodes, and recording the node ID, node type, etc. of the fourth terminal device.

[0077] The node type of terminal devices in the virtual lobby is determined based on the instruction information sent by the terminal devices to the server. This instruction information can be carried in the lobby creation request or the lobby joining request. This instruction information can be input by the user through a client on the terminal device, or it can be determined through negotiation among the various terminal devices in the virtual lobby. This embodiment does not limit the allocation method of node types for terminal devices in the virtual lobby.

[0078] In one feasible implementation, considering the limited load of each terminal device acting as an edge node, excessive connected wearable devices can lead to overload, affecting the efficiency of data processing. The server can employ a consistent hashing algorithm to achieve load balancing across edge nodes. For example, when the load of any edge node in the virtual lobby exceeds a preset load threshold (e.g., 80%), an automatic expansion mechanism can be triggered. An expansion command can be sent to the control node, which then outputs a prompt to the user indicating the need for expansion. When a new fourth terminal device initiates a lobby joining request and passes verification, the server uses a consistent hashing algorithm for load rebalancing, migrating wearable devices connected to overloaded edge nodes to the newly joined edge nodes.

[0079] Additionally, it should be noted that if a request to join the virtual lobby from any fourth terminal device fails verification, the server may refuse that fourth terminal device from joining the virtual lobby to ensure that the joining of unrelated terminal devices into the virtual lobby does not affect users.

[0080] In this embodiment, to incorporate relevant terminal devices into the constructed virtual lobby for targeted distribution of training instruction data and effective aggregation of exercise training data, and to avoid problems such as unrelated terminal devices mistakenly connecting to training groups or cross-interference in communication ranges between devices, as well as the connection limitations caused by manually connecting each terminal device, the system achieves logical grouping of terminal devices. This ensures that the first and second terminal devices belong to the same virtual lobby, guaranteeing that training instruction data and exercise training data only flow among members within the same group. Simultaneously, it supports convenient and quick addition of new terminal devices to the current logical group at any time, achieving expanded flexibility in the connection relationships between terminal devices.

[0081] In one feasible implementation, after receiving the lobby join request sent by at least one fourth terminal device in step S50, the method further includes step S60:

[0082] Step S60: Verify whether the lobby ID in the lobby join request is consistent with the lobby ID of each created virtual lobby. If it is consistent with the lobby ID of one of the created virtual lobbies, the verification is successful.

[0083] For example, a user can join the virtual lobby using a phone other than the coach's phone (hereinafter referred to as a relay phone for distinction). The user enters a 6-digit lobby code on the relay phone, which then sends a lobby join request to the server using the 6-digit lobby ID entered by the user. After the server verifies the validity of the 6-digit lobby ID entered by the user, it adds the relay phone to the virtual lobby corresponding to that lobby ID, assigns an edge node type to the relay phone, generates a UUID (Universally Unique Identifier) ​​as a unique identifier for the node, and can assign an RGB color code for UI recognition. That is, the relay phone is assigned a unique RGB color code within the virtual lobby, which is used to display relevant information about the relay phone in the client in a specific color to distinguish it from the relevant information of other relay phones displayed in the client. It is understood that if other relay phones exist, they will be assigned a different RGB color code than the original RGB color code, so that their relevant information is displayed in a different specific color in the client.

[0084] In a specific implementation, a bidirectional streaming channel can be built between the server, relay phone, and coach phone based on gRPC (a high-performance, cross-language RPC framework; RPC: Remote Procedure Call) for subsequent data transmission. The gRPC bidirectional streaming channel is a full-duplex communication mode in gRPC, which allows the client and server in the relay phone and coach phone to send and receive multiple message streams simultaneously and independently through the same connection.

[0085] In addition, in a specific implementation, besides verifying in step S60 whether the hall ID in the hall join request is consistent with the hall ID of each created virtual hall, it is also possible to verify whether the request time of the hall join request is within the valid time period of the virtual hall. If the hall ID in the hall join request is consistent with the hall ID of one of the virtual halls created, and the request time is within the valid time period of that virtual hall, then the verification is confirmed to be successful.

[0086] Understandably, by verifying both the lobby ID and the request time, it can be further ensured that the fourth terminal device joining the lobby is a terminal device that actually needs to join the training task. This further avoids the problem of irrelevant terminal devices mistakenly joining the training group or cross-interference in communication range between devices, and highly ensures that training instruction data and exercise training data only flow among valid group members.

[0087] In one feasible implementation, the terminal device can monitor all state change events of the connected wearable devices, such as the wearable device connecting or disconnecting, the completion of sensor configuration in the wearable device, and the start or end of sports training data collection. The terminal device can also, by pre-defining one-to-many dependencies between objects and using the observer pattern, notify relevant entities, including the server and other terminal devices in the same virtual lobby, of the state change represented by the state change event. This ensures that the recorded states among all entities are synchronized, and the state records can also be used for subsequent fault diagnosis and system optimization.

[0088] In one feasible implementation, the terminal device can automatically trigger corresponding recovery strategies based on the detected fault type. For example, if the detected fault type is a connection failure between the terminal device and the wearable device, a reconnection operation can be triggered; if the detected fault type is that the state of the terminal device is inconsistent with the state of other terminal devices, a state synchronization operation between terminal devices can be triggered; if the detected fault type is data loss in the terminal device, a data recovery operation can be triggered. The server can create incremental state snapshots at preset time intervals (e.g., 10 seconds), which may include information such as the device connection status, sensor configuration, and training progress of each terminal device. This state snapshot only records changes relative to the last state snapshot. When a data recovery operation or a system restart operation is triggered, data recovery can be performed based on this state snapshot.

[0089] In one feasible embodiment, the sports training data management method further includes step S70:

[0090] Step S70: In response to the data query request, output the data in the exercise training data that corresponds to the data query request.

[0091] A data query request is an instruction initiated by any terminal device, containing specific query conditions (such as time period or data type), used to request a subset of exercise training data that meets those conditions from the server. It is understood that a data query request can be initiated by either the first or second terminal device; this embodiment does not limit the specific terminal device that initiates the data query request. If the data query request is initiated by the first terminal device, the server responds by outputting the data from the exercise training data corresponding to the data query request to the first terminal device for data display and other operations. If the data query request is initiated by the second terminal device, the server responds by outputting the data from the exercise training data corresponding to the data query request to the second terminal device for data display and other operations.

[0092] The data corresponding to the data query request in the sports training data is a subset of sports training data filtered by the server according to the query conditions represented by the data query request, such as the heart rate and speed records of a specific team member during a certain period of time. Essentially, it is sports training data collected by the target wearable device, uploaded to the server by the second terminal device, and output to the terminal device that initiated the data query request as needed when responding to the data query request, so as to meet the needs of the terminal device for training reports or real-time analysis views.

[0093] In this embodiment, any terminal device can extract sports training data from the server on demand, enabling centralized access to any standardized sports training data uploaded by a second terminal device from any terminal device.

[0094] For example, to better understand the sports training data management method combining this embodiment with the above embodiments, please refer to... Figure 2 , Figure 2 This is a schematic diagram illustrating a scenario for sports training data management methods. Specifically: Figure 2 The coach's mobile phone is the first terminal device, the relay phone is the second terminal device, and the server is deployed in the cloud. It is understood that the relay phone and target wearable device in this diagram are merely examples and do not limit the specific number and type of the second terminal device and target wearable device in this embodiment. Furthermore, Figure 2In this diagram, I1 represents the first training instruction data, I2 represents the second training instruction data, E represents the exercise training data, and E' represents the data within the exercise training data corresponding to the data query request. Solid arrows indicate that the transmitted data is training instruction data, and dashed arrows indicate that the transmitted data is exercise training data. The diagram illustrates how the client on the coach's phone sends the first training instruction data I1 to a server deployed in the cloud. The server then directly forwards the first training instruction data I1 to the corresponding relay phone, or performs data conversion on the first training instruction data I1 to obtain the second training instruction data I2 before sending it to the corresponding relay phone. Exercise training data is collected from the target wearable device connected to the relay phone using the second training instruction data I2 via at least one relay phone. The cloud-deployed server receives the exercise training data E uploaded by the relay phones. Furthermore, in this scenario, the cloud-deployed server responds to the coach's phone's data query request by outputting the data E' within the exercise training data E corresponding to the data query request to the coach's phone. It is understood that the data query request can also be sent by any relay phone, and the corresponding E' can be returned to the relay phone that sent the data query request.

[0095] Based on the first embodiment described above, a second embodiment of the sports training data management method of this application is proposed. In this embodiment, content that is the same as or similar to that in the first embodiment can be referred to the above description, and will not be repeated hereafter. (Refer to...) Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the sports training data management method of this application.

[0096] The first training instruction data includes training plan data, and the exercise training data management method further includes steps S100~S300:

[0097] Step S100: Receive wearable device information sent by a terminal device in the target virtual hall, wherein the target virtual hall is the virtual hall to which the first terminal device belongs, and the wearable device information is obtained by the corresponding terminal device by scanning surrounding wearable devices via Bluetooth.

[0098] Wearable device information may include the device MAC (Media Access Control Address) address, signal strength, device name, etc., but this embodiment does not impose any restrictions.

[0099] It should be noted that multiple different virtual lobbies may exist simultaneously on the server side to allow different groups of terminal devices to manage sports training data concurrently. For example, the first terminal device and the second terminal device can be considered as one terminal device group. Therefore, the virtual lobbies belonging to the first terminal device are referred to as the target virtual lobbies to distinguish them from the virtual lobbies of other terminal device groups.

[0100] The terminal device that sends wearable device information in the target virtual hall can be a first terminal device and / or a second terminal device. For example, if the first terminal device only acts as a control node, then only the second terminal device, which acts as an edge node, sends wearable device information to the server. However, if the first terminal device, which acts as a control node, also acts as an edge node, then both the first terminal device and the second terminal device, which act as edge nodes, send wearable device information to the server. This embodiment does not limit the specific terminal device that sends wearable device information.

[0101] For example, the terminal devices in the target virtual hall include a coach's mobile phone as the first terminal device and a relay mobile phone as the second terminal device. In the case where the coach's mobile phone only acts as a control node and the relay mobile phone acts as an edge node, each relay mobile phone starts a low-power Bluetooth scanning mode and periodically (e.g., at 10-second intervals) scans the wearable devices around it to obtain wearable device information of the scanned wearable devices, which may include wearable device information such as device MAC address, signal strength, and device name. Then, this wearable device information is uploaded to the server.

[0102] In this embodiment, the terminal device in the target virtual hall actively scans the wearable devices around it, avoiding the problem of incomplete coverage or omission of some wearable devices when manually configuring the connection in the traditional way. This allows the server to dynamically obtain the real-time status of the wearable devices that already exist in the current venue where the terminal device is located, providing a reliable basis for subsequent screening of wearable devices.

[0103] Step S200: Based on the wearable device information, determine at least one target wearable device that is compatible with the training plan data.

[0104] Training plan data, included in the first training instruction data, defines the data collection requirements for specific training tasks. This data clearly specifies the data types (e.g., heart rate, speed, location), accuracy (e.g., sampling frequency), time range (e.g., training period), and device capabilities (e.g., support for GPS or electromyography monitoring) that the target wearable device should collect during training. This serves as the basis for the server to select wearable devices. By matching the training plan data with the wearable device information, it ensures that the selected target wearable device's functionality strictly matches the actual training needs. For example, it requires wearable devices with specific sensors to perform specialized data collection, thus avoiding problems such as invalid or non-compliant exercise training data collection due to insufficient or mismatched capabilities of the wearable device ultimately connected to the second terminal device.

[0105] To select wearable devices that meet training needs based on training plan data, and to avoid issues such as invalid or unsuitable sports training data collection due to insufficient or incompatible device capabilities of the wearable devices ultimately connected to the second terminal device, wearable devices are screened based on training plan data and wearable device information. This enables the accurate identification of the target wearable device suitable for the current training task from among multiple possible wearable devices, ensuring the effectiveness and efficiency of subsequent sports training data collection.

[0106] Step S300: Send device connection information to at least one terminal device in the target virtual hall so that the terminal device receiving the device connection information can establish a connection with the target wearable device according to the device connection information.

[0107] Device connection information is a set of necessary parameters generated by the server based on the wearable device scanning results. It guides the terminal device to establish a physical communication link with a specific target wearable device. This information may include the target wearable device's unique identifier and connection authorization credentials, such as a pairing key. In some scenarios, it may also include communication protocol configuration instructions. This allows the receiving terminal device to accurately connect to the specified wearable device without manual searching, thus eliminating the efficiency bottleneck and risk of incorrect connections associated with traditional manual pairing operations in large team scenarios. The unique identifier of the target wearable device can be, for example, a Bluetooth MAC address.

[0108] In a specific implementation, the terminal device can employ thread pool technology to achieve concurrent connections between multiple wearable devices. This means the terminal device can pre-create and manage a set of reusable threads to efficiently execute asynchronous tasks, thereby reducing the overhead of thread creation / destruction, optimizing resource allocation, and improving system throughput and response speed. Based on the device connection information sent by the server, the terminal device can initiate a single Bluetooth connection request to connect to one target wearable device, or it can simultaneously initiate multiple Bluetooth connection requests to connect to different target wearable devices. This embodiment does not limit the number of target wearable devices indicated by the device connection information sent by the server. The terminal device can establish a connection with the wearable device using the Bluetooth GATT (Generic Attribute Profile) protocol. During this connection process, the server can identify the sensor types and functionalities supported by the terminal device through a service discovery mechanism. Sensor types may include accelerometers, gyroscopes, heart rate sensors, etc., and functionalities may include acceleration measurement, heart rate detection, etc.

[0109] In a specific implementation, after the terminal device is successfully connected to the corresponding wearable device, clock synchronization between the terminal device and the target wearable device can be performed immediately, thereby ensuring the time consistency of the exercise training data collected by the multiple target wearable devices when any terminal device is connected to multiple target wearable devices.

[0110] In one feasible implementation, after the terminal device successfully connects with the corresponding wearable device, it can automatically collect complete metadata information of each wearable device, such as device firmware version, hardware serial number, calibration coefficient, battery level, etc. The terminal device can calculate the message digest of the metadata information based on the MD5 (Message Digest Algorithm 5, a cryptographic hash function) algorithm, which is used to perform integrity verification of the metadata information on the server side to ensure that it has not been tampered with during data transmission.

[0111] In one feasible implementation, the step of sending device connection information to at least one terminal device in the target virtual hall in step S300 may include steps S301-S302:

[0112] Step S301: For each target wearable device, determine the terminal device with the strongest signal strength between the target virtual hall and the target wearable device, and designate it as the target terminal device.

[0113] The target terminal device is the one with the strongest signal strength among all the terminal devices in the target virtual hall, and it is the target wearable device. In practice, when uploading wearable device information, the terminal device can send the signal strength between itself and the wearable device to which the wearable device information belongs, thus enabling the target wearable device to determine the terminal device with the strongest signal strength in the target virtual hall.

[0114] It should be noted that the specific execution time of determining the target terminal device in the target virtual hall can be during the initial connection process of each terminal device in the target virtual hall to the corresponding target wearable device after the target virtual hall is constructed, or it can be when the signal strength between the target wearable device and the connected terminal devices is lower than a preset signal strength threshold. In this case, by re-executing step S301, a terminal device with the strongest signal strength can be re-determined, thereby improving the connection stability between the terminal device and the target wearable device. In this embodiment, the specific execution time of step S301 is not limited.

[0115] In this embodiment, based on the signal strength of the connection between each terminal device in the target virtual hall and the target wearable device, the terminal device with the strongest signal strength is dynamically selected for each target wearable device. This terminal device can be considered as the edge node with the closest physical distance and the best communication quality to the target wearable device. This avoids connection instability problems caused by excessive distance or obstacles between the terminal device and the target wearable device. By specifying the optimal terminal device based on signal strength, a stable and low-latency Bluetooth link can be established.

[0116] Step S302: Send the device connection information corresponding to the target wearable device to the target terminal device so that the target terminal device can establish a connection with the target wearable device based on the device connection information.

[0117] To ensure that the pairing command between the selected terminal device with the strongest signal and the wearable device is transmitted to the corresponding terminal device, thus avoiding duplicate connections of the same wearable device by multiple terminal devices or connection conflicts and resource waste caused by unclear connection relationships, the target terminal device actively establishes a connection with the corresponding target wearable device based on the device connection information issued by the server. This achieves efficient and accurate device binding between the target wearable device and the target terminal device, thereby improving the automation and reliability of large-scale device networking.

[0118] In one feasible implementation, the second training instruction data may include sensor configuration information, which is used to instruct the target wearable device to configure the parameters of the sensors used to collect the exercise training data.

[0119] Sensor configuration information refers to the specific parameter instructions sent by the server to the target wearable device via the second training instruction data. These parameter instructions are used to configure the sensors built into the target wearable device, including but not limited to sensor on / off status, sampling frequency, measurement range, data filtering threshold, or operating mode. They can be used to dynamically control sensor behavior to match the data acquisition requirements of the training plan. For example, for an IMU (Inertial Measurement Unit) sensor, sensor configuration information may include accelerometer range (e.g., ±2g), gyroscope range (e.g., ±250° / s), and sampling frequency (e.g., 50Hz).

[0120] In a specific implementation, after receiving the sensor configuration information sent by the second terminal device, the target wearable device can use the I2C or SPI bus protocol to write the sensor configuration information into the configuration register of the sensor chip, thereby realizing the precise setting of sensor parameters.

[0121] In this embodiment, the parameters of the sensors in the target wearable device are uniformly configured through the sensor configuration information issued by the server to adapt to diverse training needs. This avoids the problems of low efficiency and easy parameter mismatch when manually configuring a large number of devices one by one in the traditional way, and realizes remote and precise control of the wearable device's data acquisition capability, thereby ensuring the effectiveness and reliability of sports training data acquisition.

[0122] Based on the first and / or second embodiments described above, a third embodiment of the sports training data management method of this application is proposed. In this embodiment, content that is the same as or similar to the first and second embodiments described above can be referred to the above description and will not be repeated hereafter. (Refer to...) Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the sports training data management method of this application.

[0123] In this embodiment, the sports training data management method is applied to a first terminal device, and the sports training data management method includes steps A10 to A20:

[0124] Step A10: Obtain the first training instruction data;

[0125] Step A20: Send the first training instruction data to the server so that the server can send the second training instruction data to at least one target wearable device connected to the second terminal device through at least one second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data and upload it to the server. The second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data.

[0126] It should be noted that the relevant content in this embodiment can be referred to the first and second embodiments described above, and will not be repeated here.

[0127] This embodiment implements a distributed sports training data management scheme. Training instructions issued by users through terminal devices can be relayed to various wearable devices via a server and terminal devices. Sports training data collected by each wearable device can also be uploaded to the server for centralized management via the terminal devices. Compared to the method of connecting wearable devices to a single terminal device, the distributed sports training data management scheme proposed in this embodiment can connect and manage a larger number of wearable devices. It can also configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal devices as needed. This avoids the problems of frequent disconnections between devices due to the short effective range of Bluetooth in the traditional single-point connection mode, as well as the limited number of connections per terminal device, which cannot support large-scale team training. Thus, it enables stable issuance of unified training instructions and reliable collection and centralized management of sports training data for numerous wearable devices in vast venues such as football fields.

[0128] In one feasible implementation, the sports training data management method further includes step A100:

[0129] Step A100: In response to the data query request, obtain the exercise training data corresponding to the data query request from the server and output it.

[0130] The sports training data corresponding to the data query request can be a subset of sports training data filtered by the server based on the query conditions indicated in the data query request. Please refer to the relevant description of the data corresponding to the data query request in the above sports training data.

[0131] In this embodiment, any terminal device can extract sports training data from the server on demand, enabling centralized access to all standardized sports training data uploaded by the second terminal device and accurate output of the sports training data required by the user.

[0132] Based on the first and / or second and / or third embodiments described above, a fourth embodiment of the sports training data management method of this application is proposed. In this embodiment, content that is the same as or similar to the first, second, and third embodiments described above can be referred to the above description and will not be repeated hereafter. (Refer to...) Figure 5 , Figure 5 This is a flowchart illustrating the fourth embodiment of the sports training data management method of this application.

[0133] In this embodiment, the sports training data management method is applied to a second terminal device, and the sports training data management method includes steps B10 to B30:

[0134] Step B10: Send second training instruction data to the target wearable device connected to the second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data. The second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data. The first training instruction data is received by the server from the first terminal device.

[0135] Step B20: Receive the exercise training data sent by the target wearable device;

[0136] Step B30: Upload the exercise training data to the server.

[0137] It should be noted that the relevant content in this embodiment can be referred to the first, second, and third embodiments described above, and will not be repeated here.

[0138] This embodiment implements a distributed sports training data management scheme. Training instructions issued by users through terminal devices can be relayed to various wearable devices via a server and terminal devices. Sports training data collected by each wearable device can also be uploaded to the server for centralized management via the terminal devices. Compared to the method of connecting wearable devices to a single terminal device, the distributed sports training data management scheme proposed in this embodiment can connect and manage a larger number of wearable devices. It can also configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal devices as needed. This avoids the problems of frequent disconnections between devices due to the short effective range of Bluetooth in the traditional single-point connection mode, as well as the limited number of connections per terminal device, which cannot support large-scale team training. Thus, it enables stable issuance of unified training instructions and reliable collection and centralized management of sports training data for numerous wearable devices in vast venues such as football fields.

[0139] This application provides a sports training data management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the sports training data management method in the first embodiment described above.

[0140] The following is for reference. Figure 6 The diagram illustrates a structural schematic of a sports training data management device suitable for implementing embodiments of this application. The sports training data management device in this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The sports training data management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0141] like Figure 6 As shown, the sports training data management device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the sports training data management device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. The communication device 1009 allows the sports training data management device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows sports training data management devices with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems may be implemented alternatively.

[0142] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0143] Compared with the prior art, the beneficial effects of the sports training data management device provided in this application embodiment are the same as the beneficial effects of the sports training data management method provided in the above embodiment, and other technical features in the sports training data management device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0144] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0145] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the exercise training data management method described in the above embodiments.

[0146] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0147] The aforementioned computer-readable storage medium may be included in the sports training data management device; or it may exist independently and not be assembled into the sports training data management device.

[0148] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the sports training data management device, cause the sports training data management device to perform the functions defined in the methods of the embodiments disclosed in this application.

[0149] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0150] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0151] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0152] The readable storage medium provided in this application embodiment is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-described sports training data management method. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application embodiment are the same as the beneficial effects of the sports training data management method provided in the above-described embodiments, and will not be repeated here.

[0153] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for managing sports training data, characterized in that, The sports training data management method is applied to the server side, and the sports training data management method includes: Receive the first training instruction data sent by the first terminal device; A second training instruction data is sent to at least one target wearable device connected to the second terminal device via at least one second terminal device, so that the target wearable device can collect exercise training data according to the second training instruction data. The second training instruction data is the same as or determined based on the first training instruction data. Both the first and second terminal devices have a client corresponding to the server installed, and the first and second terminal devices establish a communication connection with the server by running the client. When the first terminal device is simultaneously used to upload the first training instruction data to the server and connect to the target wearable device, the second terminal device includes the first terminal device. The device receives exercise training data uploaded by the second terminal device, wherein the exercise training data is collected by the target wearable device and sent to the second terminal device.

2. The sports training data management method as described in claim 1, characterized in that, The sports training data management method also includes: Receive a lobby creation request initiated by a third terminal device, and create a virtual lobby according to the lobby creation request; The system receives a lobby join request from at least one fourth terminal device. After verifying the lobby join request, the system adds the fourth terminal device to the virtual lobby corresponding to the lobby join request. The first terminal device and the second terminal device are terminal devices in the same virtual lobby.

3. The sports training data management method as described in claim 2, characterized in that, The first training instruction data includes training plan data, and the exercise training data management method further includes: The device receives wearable device information sent by a terminal device in the target virtual hall, wherein the target virtual hall is the virtual hall to which the first terminal device belongs, and the wearable device information is obtained by the corresponding terminal device by scanning the surrounding wearable devices via Bluetooth. Based on the wearable device information, at least one target wearable device that is compatible with the training plan data is determined; Device connection information is sent to at least one terminal device in the target virtual hall so that the terminal device receiving the device connection information can establish a connection with the target wearable device according to the device connection information.

4. The sports training data management method as described in claim 3, characterized in that, The step of sending device connection information to at least one terminal device in the target virtual hall includes: For each target wearable device, the terminal device with the strongest signal strength between itself and the target wearable device in the target virtual hall is identified as the target terminal device; The device connection information corresponding to the target wearable device is sent to the target terminal device so that the target terminal device can establish a connection with the target wearable device based on the device connection information.

5. The sports training data management method according to any one of claims 1 to 4, characterized in that, The second training instruction data includes sensor configuration information, which is used to instruct the target wearable device to configure the parameters of the sensors, and the sensors are used to collect the exercise training data.

6. A method for managing sports training data, characterized in that, The sports training data management method is applied to a first terminal device, and the sports training data management method includes: Obtain the first training instruction data; The server sends the first training instruction data to the server so that the server can send the second training instruction data to at least one target wearable device connected to the second terminal device through at least one second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data and upload it to the server. The second training instruction data is the same as the first training instruction data or is determined according to the first training instruction data. The first terminal device and the second terminal device have a client corresponding to the server installed. The first terminal device and the second terminal device establish a communication connection with the server by running the client. When the first terminal device is used to upload the first training instruction data to the server and connect to the target wearable device, the second terminal device includes the first terminal device.

7. The sports training data management method as described in claim 6, characterized in that, The sports training data management method also includes: In response to a data query request, the system retrieves and outputs the exercise training data corresponding to the data query request from the server.

8. A method for managing sports training data, characterized in that, The exercise training data management method is applied to a second terminal device, and the exercise training data management method includes: A second training instruction data is sent to a target wearable device connected to the second terminal device. The second training instruction data is used to instruct the target wearable device to collect exercise training data according to the second training instruction data. The second training instruction data is the same as or determined according to the first training instruction data. The first training instruction data is received by the server from the first terminal device. The first terminal device and the second terminal device have a client corresponding to the server installed. The first terminal device and the second terminal device establish a communication connection with the server by running the client. When the first terminal device is used to upload the first training instruction data to the server and connect to the target wearable device at the same time, the second terminal device includes the first terminal device. Receive exercise training data sent by the target wearable device; The exercise training data is uploaded to the server.

9. A sports training data management device, characterized in that, The sports training data management device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the sports training data management method as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the sports training data management method as described in any one of claims 1 to 8.

Images