Exercise training data management method and device and storage medium
Through the distributed management solution of the server and terminal devices, the connection stability and quantity limitations of terminal devices and wearable devices in large-scale team training are solved, and stable data management and unified command issuance are achieved in a wide space.
Patent Information
- Application Number
- CN202511100960.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-07
- Publication Date
- 2025-09-09
- Estimated Expiration
- 2045-08-07
AI Technical Summary
Existing sports training data management methods cannot efficiently and stably manage large amounts of sports training data in a wide space. Especially in large-scale team training scenarios, the connection stability between terminal devices and wearable devices is poor and the number of connections is limited, resulting in frequent communication interruptions.
By connecting multiple terminal devices through the server and utilizing the relay forwarding mechanism between the terminal devices and wearable devices, distributed sports training data management is achieved. The server receives training instruction data and sends instruction data to the wearable devices through multiple terminal devices. The collected data is then uploaded by the terminal devices to the server for centralized management.
It achieves the stable issuance of unified training instructions to numerous wearable devices in a wide space and the reliable collection and centralized management of sports training data, avoiding the problems of frequent disconnection and limited number of connections between devices in the traditional single-point connection mode, and supports stable data management for large-scale team training.
Smart Images

Figure CN120605495A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data management technology, and in particular to a sports training data management method, device and storage medium. Background Art
[0002] Existing sports training data management methods mainly rely on a single-point connection method, that is, one terminal device is connected to multiple wearable devices. Its core technical limitation is that the effective connection range of traditional Bluetooth technology is too short, which leads to the fact that 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 devices is frequently interrupted.
[0003] At the same time, the number of wearable devices that a single terminal device can connect to simultaneously is also very limited. This, combined with its limited connection range, further severely limits 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 effectively manage large amounts of sports training data efficiently and stably in a wide space.
[0004] The above content is only used to assist in understanding the technical solution of this application and does not constitute an admission that the above content is prior art. Summary of the Invention
[0005] The main purpose of this application is to provide a sports training data management method, device and storage medium, aiming to solve the problem that existing sports training data management methods cannot meet the needs of effectively managing a large amount of sports training data in a wide space efficiently and stably.
[0006] To achieve the above objectives, the present application proposes a sports training data management method, which is applied to a server and includes: Receiving first training instruction data sent by a first terminal device; Sending, through at least one second terminal device, second training instruction data to at least one target wearable device connected to the second terminal device, so that the target wearable device collects 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 based on the first training instruction data; Receive the 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.
[0007] In one embodiment, the sports training data management method further includes: receiving a lobby creation request initiated by a third terminal device, and creating a virtual lobby according to the lobby creation request; A lobby joining request is received from at least one fourth terminal device, and after verifying the lobby joining request, the fourth terminal device is added to a virtual lobby corresponding to the lobby joining request, wherein the first terminal device and the second terminal device are terminal devices in the same virtual lobby.
[0008] In one embodiment, the first training instruction data includes training plan data, and the sports training data management method further includes: Receiving wearable device information sent by a terminal device in a 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 through Bluetooth scanning of surrounding wearable devices; Determining, according to the wearable device information, at least one target wearable device that is compatible with the training plan data; The 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 establishes a connection with the target wearable device according to the device connection information.
[0009] In one embodiment, the step of sending device connection information to at least one terminal device in the target virtual lobby includes: For each of the target wearable devices, determining a terminal device in the target virtual hall with the strongest signal strength between the terminal device and the target wearable device 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 establishes a connection with the target wearable device according to the device connection information.
[0010] In one embodiment, the second training instruction data includes sensor configuration information, and the sensor configuration information is used to instruct the target wearable device to configure parameters of a sensor, and the sensor is used to collect the motion training data.
[0011] In addition, to achieve the above-mentioned purpose, the present application also proposes a sports training data management method, which is applied to a first terminal device and includes: acquiring first training instruction data; 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, wherein the second training instruction data is used to instruct the target wearable device to collect sports training data according to the second training instruction data and upload it to the server, and the second training instruction data is the same as the first training instruction data or is determined based on the first training instruction data.
[0012] In one embodiment, the sports training data management method further includes: In response to a data query request, the exercise training data corresponding to the data query request is acquired from the server and outputted.
[0013] In addition, to achieve the above-mentioned purpose, the present application also proposes a sports training data management method, which is applied to a second terminal device and includes: Sending second training instruction data to a target wearable device connected to the second terminal device, where the second training instruction data is used to instruct the target wearable device to collect motion 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, and the first training instruction data is received by the server from the first terminal device; Receiving sports training data sent by the target wearable device; Upload the sports training data to the server.
[0014] In addition, to achieve the above-mentioned purpose, the present application also proposes a sports training data management device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the sports training data management method described above.
[0015] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium, and when the computer program is executed by the processor, the steps of the sports training data management method described above are implemented.
[0016] One or more technical solutions proposed in this application have at least the following technical effects: A distributed sports training data management solution is implemented by connecting multiple terminal devices through a server and connecting at least one wearable device through a terminal device. The server receives first training instruction data sent by a first terminal device and sends 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 collects sports training data according to the second training instruction data and sends the sports training data to the second terminal device for uploading to the server through the second terminal device. In the distributed sports training data management solution proposed in this application, the training instruction data sent by the user through the terminal device can be relayed to each wearable device through the server and the terminal device, and the sports training data collected by each wearable device can also be uploaded to the server through the terminal device for centralized management. Compared with the method of connecting a single terminal device to a wearable device, the distributed sports training data management solution proposed in this application can connect and manage more wearable devices, and can configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal device as needed, thereby avoiding the problem of frequent disconnection between devices due to the short effective Bluetooth distance in the traditional single-point connection mode, and the limited number of connections of a single terminal device that cannot support large-scale team training. This enables the stable issuance of unified training instructions to many wearable devices and the reliable recovery and centralized management of sports training data in large venues such as football fields. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0019] Figure 1 A flowchart of the first embodiment of the sports training data management method of the present application is provided; Figure 2 A schematic diagram of a scenario provided for the first embodiment of the sports training data management method of the present application; Figure 3 A flowchart of the second embodiment of the sports training data management method of the present application is provided; Figure 4 A flowchart of the third embodiment of the sports training data management method of the present application is provided; Figure 5A flowchart of the fourth embodiment of the sports training data management method of the present application is provided; 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 embodiment of the present application.
[0020] 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 DESCRIPTION
[0021] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.
[0022] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0023] The main solution of the embodiment of the present application is: connecting multiple terminal devices through a server, and connecting at least one wearable device through a terminal device, the server receives first training instruction data sent by the first terminal device, and sends 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 collects sports training data according to the second training instruction data, sends the sports training data to the second terminal device, and uploads the sports training data to the server through the second terminal device, thereby realizing a distributed sports training data management solution. In the distributed sports training data management solution proposed in the present application, the training instruction data sent by the user through the terminal device can be relayed to each wearable device through the server and the terminal device, and the sports training data collected by each wearable device can also be uploaded to the server through the terminal device for centralized management. Compared with the method of connecting a single terminal device to a wearable device, the distributed sports training data management solution proposed in this application can connect and manage more wearable devices, and can configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal device as needed, thereby avoiding the problem of frequent disconnection between devices due to the short effective Bluetooth distance in the traditional single-point connection mode, and the limited number of connections of a single terminal device that cannot support large-scale team training. This enables the stable issuance of unified training instructions to many wearable devices and the reliable recovery and centralized management of sports training data in large venues such as football fields.
[0024] Reference Figure 1 , Figure 1 This is a flow chart of the first embodiment of the sports training data management method of the present application.
[0025] In this embodiment, the sports training data management method is applied to the server. In this embodiment, the deployment mode of the server is not limited. The server can be deployed in the cloud or in a traditional server. The sports training data management method includes steps S10 to S30: Step S10: Receive first training instruction data sent by the first terminal device.
[0026] The terminal device can establish a communication connection with the server to send training instruction data to the server. The training instruction data sent by the terminal device to the server will be referred to as the first training instruction data below to distinguish it from the training instruction data sent to the wearable device, and the terminal device that sends the first training instruction data will be referred to as the first terminal device for distinction. The manner in which the terminal device establishes a communication connection with the server is not limited in this embodiment. For example, the client corresponding to the server can be installed in 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, a tablet computer, or a laptop computer, and is not specifically limited in this embodiment.
[0027] The first training instruction data may be uploaded by the user to the first terminal device, or 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.
[0028] The first training instruction data may be instruction data related to training. In this embodiment, the specific data content of the first training instruction data is not limited. In one feasible embodiment, the first training instruction data may include control commands, such as training start and training end control commands, for instructing the wearable device to start and stop collecting data, and other operations. In one feasible embodiment, if the wearable device has multiple sensors (such as a heart rate sensor, an accelerometer sensor, etc.), the first training instruction data may include information for instructing the wearable device which sensors to use to collect data, so as to meet the requirements of different training for different sensor data. In one embodiment, the first training instruction data may include sensor configuration information for instructing the wearable device to configure corresponding sensor parameters. The sensor configuration information may be specific sensor parameter values or other information that can indicate which parameter values the wearable device should use, and this is not limited in this embodiment. 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 the sports role and / or sports type, so that the wearable device or server can match the sensor parameter values corresponding to the sports role and / or sports type, and configure the sensor parameters in the wearable device according to the matched sensor parameters. In one embodiment, the first training instruction data may include information indicating which type of wearable device to use. The types of wearable devices may include, for example, bracelets, head-mounted devices, electrocardiogram devices, etc., to meet the requirements of different training for different types of wearable devices. In one embodiment, the first training instruction data may include a status query instruction for querying the current status of each wearable device. The status of the wearable device may include, for example, device connection status, sensor configuration status, data collection status, etc.
[0029] It will be understood that the above are only a few examples of the first training indication data. In this embodiment, the specific type of the first training indication data is not limited. The first training indication data may include any one or more types of data mentioned above, or may also include a combination of any one or more types of data mentioned above and other types of data.
[0030] In one possible implementation, the server may classify received first training instruction data into different priorities based on urgency, for example, into four priorities: P0 (emergency stop), P1 (training control), P2 (configuration change), and P3 (status query), with P0 being the highest priority. Instruction data within the first training instruction data used to instruct the wearable device to urgently stop data collection operations may be assigned a P0 priority level, data used to control data collection-related operations on the wearable device may be assigned a P1 priority level, data used to instruct wearable device configuration changes (e.g., changes to the wearable device type, sensor type, or sensor parameters) may be assigned a P2 priority level, and data used to inquire about the wearable device's status may be assigned a P3 priority level. The server may employ a priority queue data structure to manage command sequences, ensuring that high-priority first training instruction data is processed first. The server may assign a globally unique MessageID (message identifier) to each first training instruction data item for message tracking and deduplication.
[0031] 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 each subsequent embodiment can be serialized using Protocol Buffers (protobuf). This 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 for efficient data storage and transmission. The serialized message consists of a message header (type, length, checksum) and a message body. Large messages (e.g., over 1KB) can be compressed using gzip (a file compression software tool) to further reduce network transmission overhead. During data transmission, an acknowledgment-based transmission mechanism can be employed. This means that after sending a message, the sender starts a timer (e.g., a 500ms timeout) and waits for an acknowledgment from the receiver. If no acknowledgment is received within the timeout, the message is retransmitted with exponential backoff, for example, up to three times. The data sender can use a sliding window protocol to control the transmission rate, with the window size dynamically adjusted based on network conditions.
[0032] In this embodiment, in order to avoid the problem that the coach's terminal device is limited by the connection range and number of its own Bluetooth in the traditional single-point connection mode, and cannot directly and stably issue unified training instructions to the wearable devices worn by all scattered athletes in the venue at the same time, the server is used as a central control node to uniformly receive the training instruction data sent by the terminal devices. This can successfully support the server to centrally receive and manage the training intentions of the entire training team in a large open venue environment, thereby laying the foundation for the subsequent distribution and collaborative execution of training instruction data.
[0033] 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 sports 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 based on the first training instruction data.
[0034] In a specific implementation, the server can forward the first training instruction data directly 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, when the first training instruction data is a control command, it can be directly forwarded on the server; or, the server or the second terminal device can convert the first training instruction data into the second training instruction data and send it to the target wearable device. For example, when the first training instruction data is a protocol file, it needs to undergo further parsing and data conversion before it can be sent to the target wearable device. That is, the second training instruction data can be data different from the first training instruction data determined based on the first training instruction data.
[0035] It should be noted that if the second training indication data is determined based on the first training indication data, the conversion process from the first training indication data to the second training indication data can be performed on the server side, that is, the second terminal device directly forwards the second training indication data sent by the server side 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 indication data sent by the server side, and then processes the first training data indication data to obtain the second training data indication data, thereby sending the second training indication data to the corresponding target wearable device.
[0036] The target wearable device is the wearable device to which the second training instruction data is to be sent. The server can send the second training instruction data to the target wearable device via 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 be used only to upload the training instruction data to the server, in which case the first terminal device is different from the second terminal device. Alternatively, the first terminal device may be used to upload the training instruction data to the server, also perform the function of forwarding the training instruction data, and establish a connection with the wearable device, in which case the first terminal device may also be one of the second terminal devices.
[0037] 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 number of wearable devices that can be connected by a single terminal device in large open venues, the server uses at least one second terminal device dispersedly deployed in the venue 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 is unable to communicate stably with a 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 of an entire large team. This effectively overcomes the limitations of short coverage range and a small number of single-point connections, ensuring that the first training instruction data can be stably and reliably transmitted to the target wearable device in a wide space.
[0038] Step S30: receiving the 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.
[0039] The sports training data is real-time quantitative information that can reflect the athlete's physiological or sports state, such as heart rate, acceleration, displacement trajectory or step frequency and other specific indicator data, collected by the target wearable device based on the second training instruction data received through the built-in sensor during the sports training process. The sports training data is collected, generated and transmitted to the second terminal device, and then uploaded to the server by the second terminal device for training analysis.
[0040] In this embodiment, the sports training data collected by the target wearable device is first transmitted to a second terminal device with which there is a stable short-range connection, and then uploaded to the server by the second terminal device. This avoids the problem of frequent loss of sports training data or transmission interruption due to unstable connection when a single terminal device directly attempts to collect data from all scattered wearable devices in a wide venue that may be too far away, and 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. The stable near-field connection established between the second terminal device and the wearable device is cleverly utilized to ensure the reliability of data transmission, and the data collection task is shared by multiple second terminal devices, breaking through the bottleneck of the number of single-point data reception, so that the training data of large teams in a wide venue can be completely and reliably aggregated to the server for unified management.
[0041] In one feasible implementation, the sports training data management method further includes steps S40 to S50: Step S40: receiving a lobby creation request initiated by a third terminal device, and creating a virtual lobby according to the lobby creation request.
[0042] The terminal device can initiate a hall creation request to the server, and the server will establish a virtual hall based on the hall creation request. Other terminal devices can initiate a hall joining request to the server to join the established virtual hall. Terminal devices in the same virtual hall can exchange data through the server, thereby sending training instruction data to wearable devices connected to the terminal devices in the virtual hall and collecting sports training data from wearable devices to realize sports training data management.
[0043] Any terminal device can initiate a lobby creation request to the server. To distinguish them, the terminal device that initiates a lobby creation request to the server is referred to as a third terminal device.
[0044] The server can add a third terminal device to the virtual lobby.
[0045] 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 has been created before, and 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, which is not limited in this embodiment.
[0046] In a specific embodiment, the server can create a virtual lobby based on a lobby creation request. Specifically, it can generate a unique ID for the virtual lobby to distinguish different virtual lobbies. It 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 serve as participating nodes in the virtual lobby. The participating node list can be used to record information related to terminal devices joining the virtual lobby, such as the ID and node type of each participating node. Participating nodes of different node types 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 an edge node and a control node. The edge node is used to connect to the wearable device, forward data to the wearable device, and obtain data from the wearable device and upload it to the server. The control node is used to send training instruction data to the server, so that the server can distribute the training instruction data to each wearable device connected to the edge node in the same virtual lobby.
[0047] There are many ways to generate the ID of the virtual hall, which are not limited in this embodiment. For example, the ID can be generated using the Snowflake Algorithm. The length of the virtual hall ID can be set as needed, which is not limited in this embodiment. For example, it can be set to 6 characters.
[0048] For example, a coach can log in to the client using a mobile phone (hereinafter referred to as the coach's phone) and initiate a lobby creation request to the server through the client. The server can use a snowflake algorithm to generate a globally unique lobby ID, and can also combine timestamps and random numbers to ensure the uniqueness and timeliness of the lobby ID. The server can then 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 (which records the node ID and node type of each participating node).
[0049] Step S50: receiving a lobby joining request sent by at least one fourth terminal device, and after verifying the lobby joining request, adding the fourth terminal device to the virtual lobby corresponding to the lobby joining request, wherein the first terminal device and the second terminal device are terminal devices in the same virtual lobby.
[0050] The fourth terminal device refers to other terminal devices that request to join the virtual lobby.
[0051] After receiving the lobby joining request initiated by the fourth terminal device, the server can verify the lobby joining request. The specific verification method is not limited in this embodiment.
[0052] After the server verifies the lobby join request, it can add the fourth terminal device to the virtual lobby corresponding to the lobby join request. For example, it can add the fourth terminal device to the virtual lobby corresponding to the lobby ID in the lobby join request. In a specific embodiment, adding the fourth terminal device to the virtual lobby can specifically include adding the fourth terminal device to the participating node list, and recording the node ID, node type, etc. of the fourth terminal device.
[0053] The node type of a terminal device in a virtual lobby is determined based on indication information sent by the terminal device to the server. This indication information can be included in a lobby creation request or lobby join request. This indication information can be input by the user through the client on the terminal device, or can be determined through negotiation among the terminal devices in the virtual lobby. This embodiment does not limit the method for assigning node types to terminal devices in the virtual lobby.
[0054] In one feasible implementation, considering that the load of each terminal device acting as an edge node is limited, when too many wearable devices are connected, the load on the terminal device will be too high, thereby affecting the efficiency of the terminal device in processing the corresponding data. The server can use a consistent hashing algorithm to achieve load balancing distribution of the edge nodes. For example, when the load of any edge node in the virtual lobby exceeds a preset load threshold (such as 80%), the expansion mechanism is automatically triggered, and an expansion instruction can be issued to the control node. The control node outputs a prompt message based on the expansion instruction to prompt the user that the capacity needs to be expanded. After a new fourth terminal device initiates a lobby joining request and is verified, the server uses a consistent hashing algorithm to rebalance the load, migrating the wearable devices connected to the overloaded edge node to the newly joined edge node.
[0055] In addition, it should be noted that, if the lobby joining request sent by any fourth terminal device fails to be verified, the server may refuse the fourth terminal device from joining the virtual lobby, so as to prevent irrelevant terminal devices from joining the virtual lobby and causing any impact on users.
[0056] In this implementation, relevant terminal devices are incorporated into a constructed virtual hall to achieve targeted distribution of training instruction data and effective aggregation of exercise training data. This prevents unrelated terminal devices from accidentally accessing a training group, cross-communication interference between devices, and connectivity limitations associated with manually connecting each terminal device. This allows terminal devices to be logically grouped, allowing the first and second terminal devices to belong to the same virtual hall. This ensures that training instruction data and exercise training data flow only between group members. Furthermore, new terminal devices can be quickly and easily added to the current logical group at any time, achieving flexible expansion of the connection relationships between terminal devices.
[0057] In one feasible implementation, after the step of receiving the lobby joining request sent by at least one fourth terminal device in step S50, the method further includes step S60: Step S60 , verifying whether the hall ID in the hall joining request is consistent with the hall ID of each created virtual hall. If it is consistent with the hall ID of one of the created virtual halls, it is determined that the verification is successful.
[0058] For example, a user can join a virtual lobby using a phone other than the trainer'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 initiates 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 the lobby ID, assigns an edge node type to the relay phone, generates a UUID (Universally Unique Identifier) as a unique node identifier, and optionally assigns an RGB color code for UI identification. Specifically, the relay phone is assigned an RGB color code unique within the virtual lobby. This color code is used to display information about the relay phone in the client, distinguishing it from information about other relay phones displayed in the client. It is understood that if other relay phones exist, they will be assigned RGB color codes different from the current RGB color code, displaying information about the other relay phones in a different color when displayed in the client.
[0059] In a specific implementation, a bidirectional stream channel can be constructed between the server and the relay phone and the trainer phone based on gRPC (a high-performance, cross-language RPC framework, RPC: Remote Procedure Call) for subsequent data transmission. The gRPC bidirectional stream channel is a full-duplex communication mode in gRPC, allowing the client and server in the relay phone and the trainer phone to send and receive multiple message streams simultaneously and independently through the same connection.
[0060] In addition, in a specific embodiment, in addition to verifying whether the lobby ID in the lobby joining request is consistent with the lobby ID of each created virtual lobby in step S60, it can also be verified whether the request time of the lobby joining request is within the valid period of the virtual lobby. If the lobby ID in the lobby joining request is consistent with the lobby ID of one of the created virtual lobbies, and the request time is within the valid period of the virtual lobby, then the verification is determined to be successful.
[0061] It can be understood that through the dual verification of the hall ID and the request time, it can be further guaranteed that the fourth terminal device joining the hall is the terminal device that actually has the need to join the training task, thereby further avoiding the problem of irrelevant terminal devices mistakenly accessing the training group or cross-interference in the communication range between devices, and highly ensuring that the training instruction data and sports training data only flow between valid group members.
[0062] In one feasible implementation, the terminal device can monitor all state change events of connected wearable devices, such as wearable device connection or disconnection, sensor configuration completion within the wearable device, and the start or end of exercise training data collection. The terminal device can also pre-define one-to-many dependencies between objects and employ an observer pattern to notify relevant entities, including the server and other terminal devices in the same virtual lobby, of the state changes represented by the state change event, thereby ensuring that the recorded states across all entities are synchronized. This state record can also be used for subsequent fault diagnosis and system optimization.
[0063] In a feasible implementation, the terminal device can automatically trigger a corresponding recovery strategy based on the type of fault detected. For example, when the detected fault type is a connection failure between the terminal device and the wearable device, a reconnection operation can be triggered; when 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; when the detected fault type is data loss in the terminal device, a data recovery operation can be triggered, wherein the server can create an incremental storage state snapshot at a preset time interval (such as 10 seconds), which can include information such as the device connection status, sensor configuration, and training progress of each terminal device. The state snapshot only records the changes relative to the last state snapshot created. When a data recovery operation is triggered or a system restart operation is triggered, data recovery can be performed based on the state snapshot.
[0064] In one feasible implementation, the sports training data management method further includes step S70: Step S70: In response to the data query request, output the data corresponding to the data query request in the sports training data.
[0065] A data query request is an instruction initiated by any terminal device and contains specific query conditions (such as time period and data type). It is used to request a subset of exercise training data that meets the query conditions from the server. It is understood that the data query request can be initiated by the first terminal device or the second terminal device, and 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 to the data query request initiated by the first terminal device and outputs the data corresponding to the exercise training data to the first terminal device, so that the first terminal device can perform operations such as data display. If the data query request is initiated by the second terminal device, the server responds to the data query request initiated by the second terminal device and outputs the data corresponding to the exercise training data to the second terminal device, so that the second terminal device can perform operations such as data display.
[0066] The data in the sports training data corresponding to the data query request is a subset of the 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 in a certain time period. Its essence is the sports training data collected by the target wearable device and uploaded to the server via the second terminal device. When responding to the data query request, it is output on demand to the terminal device that initiated the data query request to meet the needs of the terminal device for training reports or real-time analysis views.
[0067] In this embodiment, any terminal device is supported to extract sports training data from the server on demand, so that any standardized sports training data uploaded by the second terminal device can be centrally accessed in any terminal device.
[0068] For example, in order to better understand the sports training data management method after combining this embodiment with the above embodiment, please refer to Figure 2 , Figure 2 The following is a scenario diagram of a sports training data management method. Specifically: Figure 2 The coach's mobile phone is the first terminal device, the relay mobile phone is the second terminal device, and the server is deployed in the cloud. It can be understood that the relay mobile phone and the target wearable device in the figure are only examples and do not limit the specific number and type of the second terminal device and the target wearable device in this embodiment. In addition, Figure 2In the figure, 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 in the exercise training data corresponding to the data query request. Solid arrows indicate that the data being transmitted is the training instruction data, while dashed arrows indicate that the data being transmitted is the exercise training data. This figure illustrates a scenario where the client on the trainer'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 converts the first training instruction data I1 to obtain the second training instruction data I2 on the server before sending it to the corresponding relay phone. At least one relay phone collects exercise training data from a target wearable device connected to the relay phone according to the second training instruction data I2, and the server deployed in the cloud receives the exercise training data E uploaded by the relay phone. Furthermore, in this scenario, the server deployed in the cloud responds to the data query request from the trainer's phone by outputting the data E' in the exercise training data E corresponding to the data query request to the trainer's phone. It is understood that the data query request can also be sent by any relay phone, with the corresponding data E' returned to the relay phone that sent the data query request.
[0069] Based on the above first embodiment, a second embodiment of the sports training data management method of the present application is proposed. In this embodiment, the same or similar contents as those of the above first embodiment can be referred to the above introduction and will not be repeated hereafter. Figure 3 , Figure 3 This is a flow chart of the second embodiment of the sports training data management method of the present application.
[0070] The first training instruction data includes training plan data, and the sports training data management method further includes steps S100 to S300: Step S100: receiving wearable device information sent by a terminal device in a target virtual hall, wherein the target virtual hall is a virtual hall to which the first terminal device belongs, and the wearable device information is obtained by the corresponding terminal device through Bluetooth scanning of surrounding wearable devices.
[0071] The wearable device information may include the MAC (Media Access Control Address) address, signal strength, device name, etc. of the wearable device, which is not limited in this embodiment.
[0072] It should be noted that the server may simultaneously host multiple virtual halls to accommodate different groups of terminal devices for simultaneous exercise training data management. For example, the first and second terminal devices can be considered a single terminal device group. Therefore, the virtual hall to which the first terminal device belongs is referred to as the target virtual hall to distinguish it from the virtual halls of other terminal device groups.
[0073] The terminal device that sends wearable device information in the target virtual hall can be the first terminal device and / or the second terminal device. For example, if the first terminal device only serves as a control node, only the second terminal device that serves as an edge node sends wearable device information to the server; and if the first terminal device that serves as a control node also serves as an edge node, then both the first terminal device that serves as an edge node and the second terminal device send wearable device information to the server. This embodiment does not limit the specific terminal device that sends wearable device information.
[0074] Exemplarily, the terminal devices in the target virtual hall include a coach mobile phone as a first terminal device and a relay mobile phone as a second terminal device. When the coach mobile phone only serves as a control node and the relay mobile phone serves as an edge node, each relay mobile phone starts a low-power Bluetooth scanning mode and periodically (such as at intervals of 10 seconds) scans the wearable devices around it, thereby obtaining the wearable device information of the scanned wearable devices, which may include wearable device information such as device MAC address, signal strength, device name, etc., and then uploads the wearable device information to the server.
[0075] In this embodiment, the terminal device in the target virtual hall actively scans the wearable devices around it, avoiding the problem of incomplete scanning range of the terminal device or missing some wearable devices during traditional manual configuration connection. As a result, the real-time status of the wearable devices already existing in the current venue where the terminal device is located can be dynamically obtained on the server side, providing a reliable screening basis for subsequent wearable device screening.
[0076] Step S200: Determine, based on the wearable device information, at least one target wearable device that is compatible with the training plan data.
[0077] Training plan data is configuration information included in the first training instruction data that defines the data collection requirements for specific training tasks. This data can clearly specify the type of data (such as heart rate, speed, location), accuracy (such as sampling frequency), time range (such as training period), or device capabilities (such as support for GPS or electromyography monitoring) that the target wearable device should collect during training, serving as the basis for the server to screen wearable devices. By adapting the training plan data to the wearable device information, it can be ensured that the functions of the selected target wearable device strictly match the actual training needs. For example, requiring a wearable device with specific sensors to perform specialized data collection avoids the problem of invalid sports training data collection or failure to meet data requirements due to insufficient device capabilities or capability mismatch of the wearable device ultimately connected to the second terminal device.
[0078] In order to screen wearable devices that meet training needs based on training plan data, and to avoid the problem of invalid sports training data collection or non-compliance with actual data needs due to insufficient or mismatched device capabilities of the wearable device ultimately connected to the second terminal device, wearable devices are screened based on training plan data and wearable device information, thereby achieving accurate identification of target wearable devices that are suitable for the current training task among multiple possible wearable devices, thereby ensuring the effectiveness and efficiency of subsequent sports training data collection.
[0079] 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 establishes a connection with the target wearable device according to the device connection information.
[0080] Device connection information is a set of necessary parameters generated by the server based on the wearable device scan results to guide the terminal device to establish a physical communication link with a specific target wearable device. It can include the target wearable device's unique identifier and connection authorization credentials such as a pairing key. In some scenarios, it can also include communication protocol configuration instructions to enable the terminal device receiving this information to accurately establish a connection with the specified wearable device without manual search, thereby eliminating the efficiency bottleneck and risk of misconnection caused by traditional manual pairing operations in large team scenarios. Among them, the unique identifier of the target wearable device can be, for example, a Bluetooth MAC address.
[0081] In a specific embodiment, a terminal device can use thread pool technology to achieve concurrent connections with multiple wearable devices. That is, the terminal device can pre-create and manage a set of reusable threads to efficiently execute asynchronous tasks, thereby reducing thread creation and destruction overhead, 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 Bluetooth connection request to connect to a 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 use the Bluetooth GATT (Generic Attribute Profile) protocol to establish a connection with the wearable device. During this connection process, the server can identify the sensor types and functional features supported by the terminal device through the service discovery mechanism. Sensor types may include accelerometers, gyroscopes, heart rate sensors, etc. Functional features may include acceleration measurement and heart rate detection.
[0082] In a specific embodiment, after the terminal device is successfully connected to the corresponding wearable device, the clock synchronization between the terminal device and the target wearable device can be performed immediately, thereby ensuring the time consistency of the sports training data collected by multiple target wearable devices when any terminal device is connected to multiple target wearable devices.
[0083] In one feasible implementation, after the terminal device successfully connects to the corresponding wearable device, it can automatically collect complete metadata information of each wearable device, such as the device firmware version, hardware serial number, calibration coefficient, battery power, etc. The terminal device can calculate the information 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 on the metadata information on the server side to ensure that the data has not been tampered with during transmission.
[0084] In a feasible implementation manner, the step of sending device connection information to at least one terminal device in the target virtual lobby in step S300 may include steps S301 to S302: Step S301: For each target wearable device, determine a terminal device in the target virtual hall with the strongest signal strength between the terminal device and the target wearable device as the target terminal device.
[0085] The target terminal device is the terminal device with the strongest signal strength to the target wearable device among all the terminal devices in the target virtual hall. In specific implementations, 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, thereby enabling the target wearable device to determine the terminal device with the strongest signal strength to itself in the target virtual hall.
[0086] It should be noted that the specific execution time of determining the target terminal device in the target virtual lobby can be when each terminal device in the target virtual lobby is initially connected to the corresponding target wearable device after the target virtual lobby is established, or when the signal strength between the target wearable device and its connected terminal device is lower than a preset signal strength threshold, 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.
[0087] 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 reported by each terminal device, the terminal device with the strongest signal strength is dynamically selected for each target wearable device. To a certain extent, this terminal device can be reflected as the edge node with the closest physical distance to the target wearable device and the best communication quality. This can avoid the problem of unstable connection between the terminal device and the target wearable device caused by many reasons such as excessive distance or intermediate obstacles. By specifying the optimal terminal device based on signal strength, a stable and low-latency Bluetooth link can be established.
[0088] Step S302: Send the device connection information corresponding to the target wearable device to the target terminal device, so that the target terminal device establishes a connection with the target wearable device according to the device connection information.
[0089] In order to transmit the pairing instructions between the selected terminal device with the strongest signal strength and the wearable device to the corresponding terminal device in a targeted manner, so as to avoid the same wearable device being repeatedly connected to 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 sent by the server, thereby achieving 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.
[0090] In a feasible implementation, the second training instruction data may include sensor configuration information, where the sensor configuration information is used to instruct the target wearable device to configure parameters of a sensor used to collect the motion training data.
[0091] 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 the sensor's on / off state, sampling frequency, range, data filtering threshold, or operating mode. These can be used to dynamically control sensor behavior to match the data collection requirements of the training plan. For example, for an IMU (Inertial Measurement Unit) sensor, sensor configuration information may include the accelerometer range (e.g., ±2g), gyroscope range (e.g., ±250° / s), and sampling frequency (e.g., 50Hz).
[0092] In a specific embodiment, 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 achieving accurate setting of sensor parameters.
[0093] In this embodiment, the sensor configuration information sent by the server is used to uniformly configure the parameters of the sensors in the target wearable device to adapt to diverse training needs, avoiding 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 realizing remote and precise control of the wearable device collection capabilities, thereby ensuring the effectiveness and reliability of sports training data collection.
[0094] Based on the above first and / or second embodiments, a third embodiment of the sports training data management method of the present application is proposed. In this embodiment, the same or similar contents as the above first and second embodiments can be referred to the above introduction and will not be repeated hereafter. Figure 4 , Figure 4 This is a flow chart of the third embodiment of the sports training data management method of the present application.
[0095] 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: Step A10, obtaining first training instruction data; 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, wherein the second training instruction data is used to instruct the target wearable device to collect sports training data according to the second training instruction data and upload it to the server, and the second training instruction data is the same as the first training instruction data or is determined based on the first training instruction data.
[0096] It should be noted that the relevant contents in this embodiment can refer to the first and second embodiments mentioned above and will not be repeated here.
[0097] This embodiment implements a distributed sports training data management solution, in which the training instruction data sent by the user through the terminal device can be relayed to each wearable device through the server and the terminal device, and the sports training data collected by each wearable device can also be uploaded to the server through the terminal device for centralized management. Compared with the method of connecting a single terminal device to a wearable device, the distributed sports training data management solution proposed in this embodiment can connect and manage more wearable devices, and can configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal device as needed, thereby avoiding the problem of frequent disconnection between devices due to the short effective Bluetooth distance in the traditional single-point connection mode, and the limited number of connections of a single terminal device that cannot support large-scale team training. This achieves the stable issuance of unified training instructions to many wearable devices and the reliable recovery and centralized management of sports training data in large venues such as football fields.
[0098] In a feasible implementation manner, the sports training data management method further includes step A100: Step A100: In response to a data query request, obtain and output sports training data corresponding to the data query request from the server.
[0099] The sports training data corresponding to the data query request may be a sports training data subset filtered by the server according to the query conditions indicated by the data query request. For details about the data corresponding to the data query request in the sports training data, please refer to the relevant description.
[0100] In this embodiment, any terminal device is supported to extract sports training data from the server on demand, thereby enabling centralized access to all standardized sports training data uploaded by the second terminal device and accurately outputting the sports training data required by the user.
[0101] Based on the above-mentioned first and / or second embodiment and / or third embodiment, a fourth embodiment of the sports training data management method of the present application is proposed. In this embodiment, the same or similar contents as those of the above-mentioned first, second and third embodiments can be referred to above and will not be described in detail later. Figure 5 , Figure 5 This is a flow chart of the fourth embodiment of the sports training data management method of the present application.
[0102] In this embodiment, the sports training data management method is applied to the second terminal device, and the sports training data management method includes steps B10 to B30: Step B10: Sending second training instruction data to a target wearable device connected to the second terminal device, where 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, wherein the second training instruction data is the same as the first training instruction data or is determined based on the first training instruction data, and the first training instruction data is received by the server from the first terminal device; Step B20, receiving the sports training data sent by the target wearable device; Step B30: Upload the exercise training data to the server.
[0103] It should be noted that the relevant contents in this embodiment can refer to the first, second and third embodiments mentioned above, and will not be repeated here.
[0104] This embodiment implements a distributed sports training data management solution, in which the training instruction data sent by the user through the terminal device can be relayed to each wearable device through the server and the terminal device, and the sports training data collected by each wearable device can also be uploaded to the server through the terminal device for centralized management. Compared with the method of connecting a single terminal device to a wearable device, the distributed sports training data management solution proposed in this embodiment can connect and manage more wearable devices, and can configure the number of terminal devices connected to the server and the number of wearable devices connected to the terminal device as needed, thereby avoiding the problem of frequent disconnection between devices due to the short effective Bluetooth distance in the traditional single-point connection mode, and the limited number of connections of a single terminal device that cannot support large-scale team training. This achieves the stable issuance of unified training instructions to many wearable devices and the reliable recovery and centralized management of sports training data in large venues such as football fields.
[0105] An embodiment of the present 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 that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the sports training data management method in the above-mentioned embodiment one.
[0106] Reference below Figure 6 , which shows a schematic diagram of the structure of a sports training data management device suitable for implementing an embodiment of the present application. The sports training data management device in the embodiment of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), 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 only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0107] like Figure 6As shown, the athletic training data management device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs 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 athletic training data management device. The processing device 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 may be connected to the input / output interface 1006: an input device 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 1003 including, for example, a magnetic tape or hard disk; and a communication device 1009. Communication device 1009 can allow the athletic training data management device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an athletic training data management device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems can be implemented or provided instead.
[0108] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are performed.
[0109] Compared with the prior art, the beneficial effects of the sports training data management device provided in the embodiment of the present application are the same as the beneficial effects of the sports training data management method provided in the above embodiment, and the 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.
[0110] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
[0111] An embodiment of the present application provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, and the computer-readable program instructions are used to execute the sports training data management method in the above embodiment.
[0112] The computer-readable storage medium provided in the embodiments of the present application 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: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores 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.
[0113] The computer-readable storage medium may be included in the sports training data management device; or may exist independently without being assembled into the sports training data management device.
[0114] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the sports training data management device, the sports training data management device performs the functions defined in the method of the embodiment disclosed in this application.
[0115] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0116] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.
[0117] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.
[0118] The readable storage medium provided in the embodiment of the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer program) for executing the above-mentioned sports training data management method. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the embodiment of the present application are the same as the beneficial effects of the sports training data management method provided in the above-mentioned embodiment, and will not be repeated here.
[0119] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A sports training data management method, characterized in that: The sports training data management method is applied to the server, and the sports training data management method includes: Receiving first training instruction data sent by a first terminal device; Sending, through at least one second terminal device, second training instruction data to at least one target wearable device connected to the second terminal device, so that the target wearable device collects 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 based on the first training instruction data; Receive the 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.
2. The method for managing sports training data according to claim 1, wherein: The sports training data management method further includes: receiving a lobby creation request initiated by a third terminal device, and creating a virtual lobby according to the lobby creation request; A lobby joining request is received from at least one fourth terminal device, and after verifying the lobby joining request, the fourth terminal device is added to a virtual lobby corresponding to the lobby joining request, wherein the first terminal device and the second terminal device are terminal devices in the same virtual lobby.
3. The method for managing sports training data according to claim 2, wherein: The first training instruction data includes training plan data, and the sports training data management method further includes: Receiving wearable device information sent by a terminal device in a 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 through Bluetooth scanning of surrounding wearable devices; Determining, according to the wearable device information, at least one target wearable device that is compatible with the training plan data; The 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 establishes a connection with the target wearable device according to the device connection information.
4. The method for managing sports training data according to claim 3, wherein: The step of sending device connection information to at least one terminal device in the target virtual hall includes: For each of the target wearable devices, determining a terminal device in the target virtual hall with the strongest signal strength between the terminal device and the target wearable device 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 establishes a connection with the target wearable device according to 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, where the sensor configuration information is used to instruct the target wearable device to configure parameters of a sensor used to collect the motion training data.
6. A sports training data management method, characterized in that: The sports training data management method is applied to a first terminal device, and the sports training data management method includes: acquiring first training instruction data; 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, wherein the second training instruction data is used to instruct the target wearable device to collect sports training data according to the second training instruction data and upload it to the server, and the second training instruction data is the same as the first training instruction data or is determined based on the first training instruction data.
7. The method for managing sports training data according to claim 6, wherein: The sports training data management method further includes: In response to a data query request, the exercise training data corresponding to the data query request is acquired from the server and outputted.
8. A method for managing sports training data, characterized in that: The sports training data management method is applied to a second terminal device, and the sports training data management method includes: Sending second training instruction data to a target wearable device connected to the second terminal device, where the second training instruction data is used to instruct the target wearable device to collect motion 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, and the first training instruction data is received by the server from the first terminal device; Receiving sports training data sent by the target wearable device; Upload the sports training data 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, wherein the computer program is configured to implement the steps of the sports training data management method according to 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, the steps of the sports training data management method according to any one of claims 1 to 8 are implemented.
Citation Information
Patent Citations
Game enhancement system for gaming environment
CN103826711A
Method and system for monitoring and analyzing group sports activities in real time
CN108551659A
Movement system and application method thereof
CN108579060A
An exercise teaching method, device and system, a server and a storage medium
CN110289074A
Remote real-time monitoring system and method for skiing
CN113645407A