WO2021226800A1 - Melody playing method, and client and storage medium - Google Patents

Abstract

Provided are a melody playing method, and a client and a storage medium, which relate to the technical field of networks. The method comprises: acquiring target fetal heart data; and according to a melody configuration rule in which a correlation between multiple pieces of fetal heart data and multiple melody files is recorded, acquiring a target melody file corresponding to the target fetal heart data, so as to play the target melody file. Compared with the prior art, target fetal heart data is converted into a melody which can be perceived by a user, such that the perception of the user is enhanced, and an interaction effect is improved.

Description

Musical playing method, user terminal and storage medium Technical field

This application relates to the field of network technology, and in particular, to a music playing method, a user terminal, and a storage medium.

Background technique

In order to improve the interaction between the user and the fetus, some wearable smart devices can be used to collect fetal heart rate data and fetal movement data, and then use the collected fetal heart rate data and fetal movement data to perform interactive operations such as drawing, so that Users can not only use the interactive results to reflect the fetal heart rate data and fetal movement data, but also enhance the interest of interaction with the fetus and enhance the user experience.

However, the current interaction scheme only establishes the interaction between the user and the fetus at a static level, and cannot dynamically establish the interaction between the user and the fetus, and the interaction effect is poor.

Summary of the invention

The purpose of this application includes providing a rhythm playing method, a user terminal, and a storage medium, which can convert fetal heart rate data into a rhythm that the user can perceive, thereby enhancing the user's perception and enhancing the interactive effect.

In order to achieve at least one of the above objectives, the technical solutions adopted in this application are as follows:

The present application provides a method for playing music. The method includes:

Obtain target fetal heart rate data;

Obtain a target rhythm file corresponding to the target fetal heart rate data according to the rhythm configuration rule; wherein the rhythm configuration rule records the correspondence between multiple fetal heart rate data and multiple rhythm files;

Playing the target melody file.

Optionally, the target fetal heart rate data includes multiple fetal heart rate values; the rhythm configuration rule records the correspondence between multiple fetal heart rate ranges and multiple melody files;

According to the rhythm configuration rule, the step of obtaining the target rhythm file corresponding to the target fetal heart rate data includes:

Obtaining an average fetal heart rate value of the multiple fetal heart rate values included in the target fetal heart rate data;

Determine the melody file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file; wherein, the target fetal heart rate range is where the average fetal heart rate value is located in the plurality of fetal heart rate ranges Fetal heart rate range.

Optionally, each melody file includes a first copy file and a second copy file;

The step of determining the melody file corresponding to the target fetal heart rate range in the melody configuration rule as the target melody file includes:

Judging whether the target fetal heart rate data includes a fetal movement identifier;

When the target fetal heart rate data does not include a fetal movement identifier, determining the first copy file included in the melody file corresponding to the target fetal heart rate range as the target melody file;

When the target fetal heart rate data includes a fetal movement identifier, the second copy file included in the melody file corresponding to the target fetal heart rate range is determined as the target melody file.

Optionally, each melody file includes multiple sub-melody files;

The step of determining the melody file corresponding to the target fetal heart rate range in the melody configuration rule as the target melody file includes:

The target melody file is determined among multiple sub-melody files included in the melody file corresponding to the target fetal heart rate range.

Optionally, the target fetal heart rate data includes multiple fetal heart rate values; the rhythm configuration rule records the correspondence between multiple fetal heart rate ranges and multiple note files;

According to the rhythm configuration rule, the step of obtaining the target rhythm file corresponding to the target fetal heart rate data includes:

Obtaining an average fetal heart rate value of the multiple fetal heart rate values included in the target fetal heart rate data;

In the rhythm configuration rule, the note file corresponding to the target fetal heart rate range is determined as the target rhythm file; wherein, the target fetal heart rate range is where the average fetal heart rate value is located in the multiple fetal heart rate ranges Fetal heart rate range.

Optionally, each note file includes multiple sub-note files;

The step of determining the note file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file includes:

The target melody file is determined among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range.

Optionally, each sub-note file corresponds to configuration parameters;

Among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range, the step of determining the target rhythm file includes:

Among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range, the target sub-note file whose difference between the corresponding configuration parameter and the set configuration parameter is within the set range is determined as the target sub-note file Describe the target melody file.

Optionally, the method further includes:

Update the set configuration parameters according to the configuration parameters of the target melody file.

Optionally, before the step of playing the target melody file, the method further includes:

When the target fetal heart rate data contains a fetal movement identifier, adjusting the scale of the target rhythm file;

The step of playing the target melody file includes:

Play the target temperament file after adjusting the scale.

Optionally, the step of adjusting the scale of the target melody file includes:

Raise the scale of the last note of the target melody file.

Optionally, the step of adjusting the scale of the target melody file includes:

The fetal movement identification sound is added to the last sound of the target melody file.

Optionally, before the step of obtaining the target rhythm file corresponding to the target fetal heart rate data according to the rhythm configuration rule, the method further includes:

The timbre configuration rule is determined in the timbre type strategy; wherein, the timbre type strategy includes multiple configuration rules.

Optionally, before the step of obtaining target fetal heart rate data, the method further includes:

Save the received fetal heart rate data to the first queue;

The steps to obtain target fetal heart rate data include:

The first queue is read in chronological order to obtain the target fetal heart rate data.

Optionally, before the step of saving the received fetal heart rate data to the first queue, the method further includes:

Determine whether the remaining playing time is less than the first threshold;

When it is yes, execute the step of saving the received fetal heart rate data to the first queue.

Optionally, before the step of obtaining target fetal heart rate data, the method further includes:

Save the read historical fetal heart rate data to the first queue, and update the number of data; wherein the number of data is configured to indicate the number of historical fetal heart rate data stored in the first queue;

When the number of data reaches the second threshold, the step of obtaining target fetal heart rate data includes:

Read the historical fetal heart rate data stored in the first queue according to the second threshold to obtain the target fetal heart rate data, and reset the first queue and the number of data.

Optionally, after the step of obtaining the target rhythm file corresponding to the target fetal heart rate data in the rhythm file library, the method further includes:

Saving the target rhythm file to a second queue; wherein the second queue is configured to save the rhythm file corresponding to the fetal heart rate data;

When the merge instruction is received, all the melody files in the second queue are merged to generate an audio file.

This application also provides a user terminal, including:

The memory is configured to store one or more programs;

processor;

When the one or more programs are executed by the processor, the above-mentioned melody playing method is realized.

The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned melody playback method is realized.

Description of the drawings

FIG. 1 shows a schematic application scenario diagram of the music playing method provided by the present application;

FIG. 2 shows a schematic structural block diagram of the user terminal provided by the present application;

FIG. 3 shows a schematic flow chart of the method for playing music provided by the present application;

FIG. 4 shows a schematic flowchart of the sub-steps of step 204 in FIG. 3;

FIG. 5 shows a schematic flowchart of the sub-steps of step 204-2 in FIG. 4;

FIG. 6 shows another schematic flowchart of the sub-steps of step 204 in FIG. 3;

FIG. 7 shows still another schematic flowchart of the sub-steps of step 204 in FIG. 3;

FIG. 8 shows another schematic flow chart of the music playing method provided by the present application;

FIG. 9 shows still another schematic flow chart of the music playing method provided by the present application;

FIG. 10 shows still another schematic flow chart of the music playing method provided by the present application;

FIG. 11 shows still another schematic flowchart of the music playing method provided by the present application;

FIG. 12 shows still another schematic flow chart of the music playing method provided by the present application;

Fig. 13 shows still another schematic flow chart of the music playing method provided by the present application.

In the figure: 100-user terminal; 101-memory; 102-processor; 103-storage controller; 104-peripheral interface; 105-radio frequency unit; 106-communication bus/signal line; 107-playing unit.

Detailed ways

In order to make the purpose, technical solutions and advantages of this application clearer, the following will clearly and completely describe the technical solutions provided by this application in conjunction with the drawings in some embodiments of this application. Obviously, the described embodiments are the same for this application. Part of the embodiments, but not all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various different configurations.

Therefore, the following detailed description of the embodiments of the application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents a part of the selected embodiments of the application. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

It should be noted that similar reference numerals and letters indicate similar items in the following figures. Therefore, once a certain item is defined in one figure, it does not need to be further defined and explained in subsequent figures. At the same time, in the description of the present application, the terms "first", "second", etc. only indicate distinguishing description, and cannot be understood as indicating or implying relative importance.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply one of these entities or operations. There is any such actual relationship or order between. Moreover, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes those that are not explicitly listed Other elements of, or also include elements inherent to this process, method, article or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or equipment that includes the element.

For example, in the above scenario where the user can interact with the fetus using fetal heart rate data and fetal movement data, the current solution is generally based on the fetal heart rate data and fetal movement data for drawing operations; based on the fetal heart rate data and fetal movement data, the user It can establish an emotional connection with the fetus and realize interesting interactions, which can increase the emotion between the user and the fetus.

However, operations such as drawing are only to establish the interaction between the user and the fetus at a static level, and the user's perception of the fetal heart data and fetal movement data of the fetus is not strong, and the interaction effect is poor.

To this end, a possible implementation manner provided by this application is to obtain target fetal heart rate data, and obtain the target fetal heart rate data according to the rhythm configuration rule that records the correspondence between multiple fetal heart rate data and multiple rhythm files. Corresponding target melody file, thereby playing the target melody file, converting the target fetal heart rate data into a melody that the user can perceive, thereby enhancing the user’s perception and enhancing the interactive effect.

Hereinafter, some embodiments of the present application will be described in detail with reference to the accompanying drawings. In the case of no conflict, the following embodiments and features in the embodiments can be combined with each other.

Please refer to FIG. 1, which shows a schematic application scenario diagram of the melody playback method provided by the present application; in one embodiment, the front-end device establishes communication with the user end to realize data between the front-end device and the user end Interactive.

For example, in an embodiment, the front-end device and the user terminal may be located in a wireless network or a wired network, and the front-end device and the user terminal perform data interaction through the wireless network or the wired network.

Or, in another embodiment, the front-end device and the user terminal may establish communication by using, for example, Bluetooth (bluetooth) or a local area network, so as to realize the data interaction between the front-end device and the user terminal.

In an embodiment, the user terminal may use a mobile terminal device, such as a smart phone, a personal computer (PC), a tablet computer, a personal digital assistant (PDA), and a wearable mobile device. Terminal and so on.

The music playing method provided in this application can be applied to the client as shown in FIG. It can be implemented by an application installed in the client.

Schematically, please refer to FIG. 2. FIG. 2 shows a schematic structural block diagram of the client 100 provided by the present application; the client 100 may include a memory 101, one or more (only one is shown in the figure) processing The device 102, the storage controller 103, the peripheral interface 104, the radio frequency unit 105, the playback unit 107, and so on. These components can communicate with each other through one or more communication buses/signal lines 106.

The memory 101 may be configured to store software programs and modules, such as program instructions/modules corresponding to the melody playback method provided in this application. The processor 102 executes the software programs and modules stored in the memory 101 by running the software programs and modules. Various functional applications and image processing, etc., to implement the melody playback method provided in this application.

The memory 101 can be, but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), which can be Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), etc.

The processor 102 may be an integrated circuit chip with signal processing capabilities. The aforementioned processor 102 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), a voice processor, a video processor, etc.; it may also be a digital signal processor ( Digital Signal Processing, DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components Wait. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor 102 may also be any conventional processor or the like.

The peripheral interface 104 couples various input/input devices to the processor 102 and the memory 101. In some embodiments, the peripheral interface 104, the processor 102, and the storage controller 103 may be implemented in a single chip. In some other embodiments of this application, they can also be implemented by independent chips.

The radio frequency unit 105 is configured to receive and send electromagnetic waves, realize mutual conversion between electromagnetic waves and electrical signals, and communicate with a communication network or other devices.

The playing unit 107 is configured to play a melody file or an audio file, etc., to output melody information or audio information and the like.

It can be understood that the structure shown in FIG. 2 is only for illustration, and the user terminal 100 may also include more or fewer components than those shown in FIG. 2, or have a configuration different from that shown in FIG. 2. The components shown in FIG. 2 can be implemented by hardware, software, or a combination thereof.

In the following, the user terminal 100 shown in FIG. 2 is used as an exemplary execution subject to exemplarily describe the melody playback method provided in the present application.

Please refer to FIG. 3. FIG. 3 shows a schematic flow chart of the music playing method provided by the present application, which may include the following steps:

Step 202: Obtain target fetal heart rate data;

Step 204: Obtain a target rhythm file corresponding to the target fetal heart rate data according to the rhythm configuration rule;

Step 206: Play the target melody file.

In one embodiment, when the user terminal executes the rhythm playback method provided in this application, it can first obtain target fetal heart rate data; then use the target fetal heart rate data to compose music, thereby obtaining the target rhythm file corresponding to the target fetal heart rate data, so that The client can play the target melody file.

Among them, when the user side obtains the target fetal heart rate data, it can use the received fetal heart rate data sent by other devices such as front-end equipment as the target fetal heart rate data as shown in the scenario shown in Figure 1; The downloaded fetal heart rate data is used as the target fetal heart rate data; or, the user terminal can use the stored fetal heart rate data as the target fetal heart rate data.

In addition, the user terminal can store a rhythm configuration rule, which records the correspondence between multiple fetal heart data and multiple rhythm files; when the user terminal obtains the target rhythm file, it can configure the rhythm configuration according to the rhythm configuration rule The melody file corresponding to the target fetal heart rate data in the rule is determined to be the target melody file.

In this way, the user terminal can play the target rhythm file, that is, convert the target fetal heart rate data into a rhythm that the user can perceive, thereby enhancing the user's perception and enhancing the interactive effect.

It should be noted that when the user terminal executes step 204, the target rhythm file corresponding to the target fetal heart rate data may be obtained in various ways.

For example, in some applicable application scenarios, the fetal heart rate of the fetus is generally between 110 beats/minute and 160 beats/minute; for this reason, in one embodiment, the user terminal can set the complete fetal heart rate range The range is divided into multiple different fetal heart rate ranges, and different rhythm files are pre-stored for different fetal heart rate ranges, that is: different rhythm files can be configured for different fetal heart rate ranges in advance, and the rhythm configuration rules saved on the user terminal can be used. Correspondences between multiple fetal heart rate ranges and multiple melody files are recorded.

To this end, on the basis of FIG. 3, please refer to FIG. 4. FIG. 4 shows a schematic flowchart of the sub-steps of step 204 in FIG. 3. In an embodiment, step 204 may include the following sub-steps:

Step 204-1: Obtain an average fetal heart rate value of multiple fetal heart rate values included in the target fetal heart rate data;

Step 204-2: Determine the melody file corresponding to the target fetal heart rate range in the melody configuration rule as the target melody file.

In one embodiment, in order to avoid large fluctuations in the rhythm of the fetal heart rate within a short period of time, when the user terminal executes step 202, the obtained multiple fetal heart rate values may be used as target fetal heart rate data, for example, a period of time All fetal heart rate values in a range (for example, every 5 seconds) are used as target fetal heart rate data. In this way, when step 204 is performed, the average fetal heart rate value of the multiple fetal heart rate values included in the target fetal heart rate data may be obtained first.

Then, the user terminal can combine the saved rhythm configuration rules to determine the fetal heart rate range where the average fetal heart rate value is located among the multiple fetal heart rate ranges recorded by the rhythm configuration rule as the target fetal heart rate range.

In this way, the user terminal can determine the melody file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file according to the calculated average fetal heart rate value.

For example, suppose that the tone configuration rules saved on the client side can be as shown in Table 1 below:

Table 1

Fetal heart (N) range	Melody file theme
N<110	still
110<=N<120	Tick
120<=N<130	Soothing
130<=N<140	story
140<=N<150	wake
150<=N<160	sports
160<=N	run

Combining the melody configuration rules in the example of Table 1 above, assuming that the average fetal heart rate calculated by the user terminal is 136, the user terminal can select the melody file with the theme name "Story" as the target melody file.

In addition, in some possible application scenarios, the fetal heart rate data measured by the front-end equipment may be accompanied by fetal movement data.

Therefore, to enable the fetal movement of the fetus to be reflected in the rhythm played by the user terminal, in one embodiment, different copy files may be used to compare the target fetal heart rate data with the fetal movement identification and the target fetal heart rate data without the fetal movement identification. Make a distinction; that is: in the melody configuration rules recorded on the user side, each melody file may include a first copy file and a second copy file. For example, in combination with the example in Table 1, the theme is "story". The file includes two duplicate files, one of which indicates that there is no fetal movement identifier in the corresponding fetal heart rate data, and the other indicates that the corresponding fetal heart rate data contains a fetal movement identifier.

For example, it can be assumed that the first copy file of each rhythm file indicates that the corresponding fetal heart rate data does not contain a fetal movement identifier, and the second copy file indicates that the corresponding fetal heart rate data contains a fetal movement identifier.

In this way, on the basis of FIG. 4, please refer to FIG. 5. FIG. 5 shows a schematic flowchart of the sub-steps of step 204-2 in FIG. 4. In an embodiment, step 204-2 may include the following sub-steps step:

Step 204-2a, judge whether the target fetal heart rate data contains a fetal movement identifier; if it is no, execute step 204-2b; if it is yes, execute step 204-2c;

Step 204-2b: Determine the first copy file included in the melody file corresponding to the target fetal heart rate range as the target melody file;

Step 204-2c: Determine the second copy file included in the melody file corresponding to the target fetal heart rate range as the target melody file.

In one embodiment, when the user terminal performs step 204-2, it can determine whether the target fetal heart rate data contains a fetal movement identifier; when the user terminal determines that the target fetal heart rate data does not contain a fetal movement identifier, the user terminal can choose to The first copy file included in the melody file corresponding to the target fetal heart rate range is determined to be the target melody file. For example, the first copy file included in the melody file with the subject name "Story" in the above example is determined to be the target melody file; When the terminal determines that the target fetal heart rate data contains the fetal movement identifier, the user terminal can choose to determine the second copy file contained in the melody file corresponding to the target fetal heart rate range as the target melody file. For example, the subject name in the above example is "Story" The second copy file included in the melody file is determined to be the target melody file.

Among them, it should be noted that the fetal movement identifier contained in the target fetal heart rate data can be, for example, when the front-end equipment in the scene shown in Figure 1 collects fetal heart rate data, whenever a piece of fetal movement data is collected, it is the corresponding time point. The fetal heart rate data records a fetal movement flag to indicate that a fetal movement occurred at the time point corresponding to the fetal heart rate data.

Alternatively, different time series can be used to record the fetal heart rate data and fetal movement data respectively. The fetal heart rate data is recorded once every second, and the fetal movement data is recorded once every time it occurs; the user terminal can read the fetal heart rate data at the same time when performing step 202 The time series of the fetal movement data and the time series of the fetal movement data, and when the target fetal heart rate data is obtained, the fetal movement variable is used to record the number of fetal movements read, so that when step 204-2a is executed, the user terminal can use the value of the fetal movement variable to determine the target fetal movement. Whether the fetal movement identifier is included in the heart data; for example, if the value of the fetal movement variable read by the user terminal is 0, it means that the target fetal heart data does not contain the fetal movement identifier; if the value of the fetal movement variable read by the user terminal is greater than 0, it means that the target fetal heart rate data contains a fetal movement indicator.

In this way, the user terminal uses different duplicate files to distinguish between the fetal movement identification and the absence of the fetal movement identification in the fetal heart rate data, so that the user can distinguish whether the fetus has the fetus when the corresponding fetal heart rate data is collected through different duplicate files. Fetal movement occurs, which in turn enhances user perception and enhances interactive effects.

In addition, in order to avoid that each fetal heart rate range corresponds to only a single melody file, so that during continuous playback, the generated melody is relatively single, each melody file saved on the user terminal may include multiple sub-melody files.

For this reason, when performing step 204-2, the user terminal may determine the target melody file among the multiple sub-melody files included in the melody file corresponding to the target fetal heart rate range.

For example, three sub-melody files can be saved for each melody file in advance; in the above example of the melody file corresponding to the target fetal heart data with the theme named "story", when step 204-2 is executed, the user terminal For example, a random algorithm can be used to randomly select one of the three sub-melody files included in the "story" as the target melody file.

Illustratively, suppose that the three sub-melody files contained in the melody file with the theme "story" are respectively numbered 0, 1, and 2, and the number is recorded as total; the user terminal can perform step 204-2 with the accuracy to The current timestamp of the system in milliseconds is currentTsInMillSecond, and the calculation formula for the number of the target melody file can satisfy the following:

index=(currentTsInMillSecond*31)%total

That is, the product of currentTsInMillSecond multiplied by 31 is divided by total and the remainder is taken, and then the sub-melody file with the corresponding number is selected as the target melody file according to the result of taking the remainder.

In this way, the user terminal can play different melody in different playback periods, even if different target fetal heart rate data correspond to the same fetal heart rate range, and can avoid a single melody when the music is played continuously.

It is understandable that the above-mentioned implementation provided by this application is based on pre-arranging different melody files for different fetal heart rate ranges to perform melody playback. In some other possible implementations of this application, the user terminal may also pre-store different note files for different fetal heart rate ranges, that is: the way of configuring notes may also be used to play the rhythm, and the rhythm configuration saved by the user terminal at this time The rule can record the correspondence between multiple fetal heart rate ranges and multiple note files.

To this end, on the basis of FIG. 3, please refer to FIG. 6. FIG. 6 shows another schematic flowchart of the sub-steps of step 204 in FIG. 3. In another embodiment, step 204 may also include the following sub-steps: step:

Step 204-6, obtaining an average fetal heart rate value of multiple fetal heart rate values included in the target fetal heart rate data;

Step 204-7: Determine the note file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file;

In another embodiment, also in order to avoid large fluctuations in the rhythm caused by the excessive variation of the fetal heart rate in a short period of time, the user terminal may use the obtained multiple fetal heart rate values as the target fetal heart rate data, and calculate the target fetal heart rate data. The average fetal heart rate of multiple fetal heart rate values.

Then, the user terminal may determine the fetal heart rate range where the average fetal heart rate value is located as the target fetal heart rate range, and determine the note file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target musical scale file.

Among them, it should be noted that in the above two implementation manners listed in this application, the solutions provided in step 204-1 to step 204-2 are played in a complete melody, that is, the complete melody is pre-stored; and the step The solutions provided in 204-6 to step 204-7 are played based on notes, that is, the notes are stored in advance, and the music is arranged through continuous playing of the notes instead of playing the complete melody.

In addition, in order to increase the diversity when using the note file to arrange music, each note file saved on the user terminal may include multiple sub-note files.

In this way, when the user terminal performs step 204-7, the target melody file can be determined from among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range; for example, the random algorithm described above can be used to determine the target melody file .

Moreover, in one embodiment, in order to avoid continuous playback, because the scales of two adjacent matching files are too different, resulting in poor tempo effect played on the user side, corresponding configuration parameters can be set for each sub-note file. , So that when the user terminal is continuously playing, it can make the configuration parameters of two consecutive note files differ within the set range according to the set configuration parameters.

For example, you can divide all sub-note files into 3 octaves of sub-note files, which are three types: bass, midrange, and treble. Each type contains a complete note.

Each sub-note file is a note in the note, such as 1 (do) for the bass, 3 (mi) for the midrange, and 5 (so) for the treble; each note can contain multiple different sub-note files. The difference lies in the duration of time, for example, ranging from 2 seconds to 6 seconds; assuming that every 0.5 second is a sound speed unit, then: the speed of sound with a duration of 2 seconds is 4, and the speed of sound with a duration of 4 seconds is 8.

In this way, each sub-note file can be named in the format of pitch (lastScale)-sound intensity (lastVolume)-speed of sound (lastSpeed); for example, for midrange 1 with a pitch of 3 and a speed of 8, its corresponding sub-note file can be named It is (midrange 1+3+8), that is, the configuration parameters corresponding to the sub-note file are pitch 3 and speed 8.

Therefore, when the user terminal performs step 204-7, it can set the difference between the corresponding configuration parameter and the set configuration parameter among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range. The target sub-note file within the range is determined as the target temperament file.

For example, it can be assumed that 3 degrees is within the set range, that is, the scale of the target temperament file and the set configuration parameters do not exceed 3 degrees.

It is assumed that the musical temperament configuration rules saved on the client side can also contain the following content:

(1) When the average fetal heart rate is less than 110, choose a scale with bass, volume intensity not greater than 4, and sound velocity not less than 12;

(2) When the average fetal heart rate is greater than or equal to 110 and less than 125, use a scale with bass, volume intensity between 2-5, and sound velocity not less than 10;

(3) When the average fetal heart rate is greater than or equal to 125 and less than 145, the midrange, the volume intensity is between 3-7, and the speed of sound is between 8-10;

(4) When the average fetal heart rate is greater than or equal to 145 and less than 160, a scale with a high pitch, a volume intensity of 5-8, and a speed of sound not greater than 8 is selected;

(5) When the average fetal heart rate is greater than 160, a scale with high pitch, volume intensity not less than 6, and sound velocity not greater than 6 is selected.

In this way, the user terminal can be based on the above-mentioned rhythm configuration rules, according to the target fetal heart rate range where the target fetal heart rate data is located, and the configuration parameters of the pitch, intensity, and speed of each sub-note file, combined with the set configuration parameters, The sub-note file whose difference between the corresponding configuration parameter and the set configuration parameter is within the set range is used as the target melody file.

Among them, the set configuration parameter can be a fixed parameter value set by the user, or it can be the user side when the user terminal is continuously arranging music. In order to avoid the scale difference of the two adjacent note files being played, the user side can choose The configuration parameter of the last sub-note file determined as the target temperament file is used as the configuration parameter of the setting.

In this way, on the basis of FIG. 6, please refer to FIG. 7. FIG. 7 shows still another schematic flowchart of the sub-steps of step 204 in FIG. step:

Step 204-8, update the set configuration parameters according to the configuration parameters of the target melody file.

Through continuous iteration, after the user terminal determines the target melody file in step 204-7, it can update the set configuration parameters according to the configuration parameters of the target melody file, for example, update the set configuration parameters to the target melody file Configuration parameters.

In addition, in the implementation of using musical notes to compose music, in order to reflect the fetal movement during the measurement of the fetal heart rate data, as a possible implementation, on the basis of Figure 6, please refer to Figure 8. Figure 8 shows Another schematic flowchart of the music playing method provided in the present application. Before step 206 is executed, the music playing method may further include the following steps:

Step 205: When the target fetal heart rate data contains the fetal movement identifier, adjust the scale of the target rhythm file.

Among them, the user terminal can use, for example, the above-mentioned implementation methods provided in this application to determine whether the target fetal heart rate data contains a fetal movement identifier, which will not be repeated in this application.

Therefore, when the user terminal determines that the target fetal heart rate data contains the fetal movement identifier, the scale of the target melody file can be adjusted, and when step 206 is executed, the target melody file after the adjusted scale is played, so that the user can pass the played melody The change of the musical scale can sense that the fetus has fetal movement within the time period corresponding to the target fetal heart rate data, which enhances the user's perception.

In one embodiment, when the user terminal adjusts the scale of the target melody file, the user terminal may raise the scale of the last tone of the target melody file, for example, raise the last tone by 8 degrees.

Or, in another embodiment, when the user terminal adjusts the scale of the target melody file, the user terminal can add a fetal movement identification sound to the last sound of the target melody file, such as adding a preset fetal movement special sound, so that the user can By recognizing the fetal movement identification sound, it is determined whether the fetus has fetal movement within the corresponding time period.

In one embodiment, in order to enhance the user's experience, multiple configuration rules of different timbre types may be pre-recorded on the user terminal, so that the user terminal can generate temperaments of different timbre types.

To this end, on the basis of FIG. 3, please refer to FIG. 9. FIG. 9 shows another schematic flowchart of the music playing method provided by the present application. Before step 202 is performed, the music playing method may further include the following steps :

Step 200: Determine a temperament configuration rule in the timbre type strategy.

In one embodiment, the user terminal may save a tone type strategy, which includes multiple configuration rules, such as hand disc tone configuration rules, piano tone configuration rules, harmonica tone configuration rules, violin tone configuration rules, and so on.

When the user terminal executes the tone playing method provided in the present application, it can determine a configuration rule in the tone color type strategy as the tone configuration rule.

For example, one of the configuration rules selected by the user can be received as the rhythm configuration rule; or, for example, the random algorithm described above can be used to select a configuration rule as the rhythm based on the current timestamp when the user terminal executes the rhythm playback method. Configure rules.

In this way, the user terminal can generate the target rhythm file corresponding to the target fetal heart rate data according to the rhythm configuration rules determined from the tone color type strategy, so that the user terminal can play different tone color types of rhythms.

It should be noted that, as described above, the target fetal heart rate data obtained by the user terminal may be the fetal heart rate data received by the user terminal, for example, sent by the front-end device, or the fetal heart rate data downloaded by the user terminal from the server, or the user terminal itself Stored fetal heart data.

For this reason, in application scenarios such as receiving the fetal heart rate data sent by the front-end equipment at the user end, as a possible implementation, on the basis of Fig. 3, please refer to Fig. 10, which shows the rhythm playback provided by this application. In yet another schematic flowchart of the method, before step 202 is performed, the melody playback method may further include the following steps:

Step 201-2, save the received fetal heart rate data to the first queue;

In an embodiment, the user terminal may set a first queue, and the first queue may be configured to store the received fetal heart rate data. In this way, when the user terminal receives the fetal heart rate data, the user terminal can save the received fetal heart rate data to the first queue.

Therefore, when performing step 202, the user terminal may read the first queue in a time sequence, thereby reading the fetal heart rate data stored in the first queue, to obtain the target fetal heart rate data.

It should be noted that, as mentioned above, the fetal heart rate data is generally measured every second; in some possible implementations, in order to avoid large fluctuations in the rhythm caused by the excessive variation of the fetal heart rate in a short period of time, the user terminal can select The fetal heart rate for a period of time is used as the target fetal heart rate data.

However, when the user terminal is playing the target rhythm file, the duration of the target rhythm file may be longer than the time collected by the target fetal heart rate data; for example, you can collect the target fetal heart rate data for 5 seconds to obtain a target that can be played for 20 seconds. Melody file, that is, use a small amount of fetal heart rate data to play a longer tone. Therefore, in some possible implementations, the user end may discard some received fetal heart rate data.

To this end, on the basis of FIG. 10, please refer to FIG. 11. FIG. 11 shows another schematic flowchart of the music playing method provided by the present application. Before step 201-2 is performed, the music playing method may further include The following steps:

Step 201-1, judge whether the remaining playing time is less than the first threshold; if yes, execute step 201-2; if no, execute step 201-3;

Step 201-2, save the received fetal heart rate data to the first queue;

Step 201-3, discard the received fetal heart rate data.

In one embodiment, the user terminal may record the remaining playing time of the music file when playing the music file; then, whenever the fetal heart rate data is received, the user terminal compares the recorded remaining playing time with the first threshold, when When the remaining playing time is less than the first threshold, the user terminal performs step 201-2 to save the received fetal heart rate data to the first queue; otherwise, when the remaining playing time is greater than or equal to the first threshold, the user terminal performs step 201 -3, discard the received fetal heart rate data.

For example, taking the above target fetal heart rate data including 5 fetal heart rates as an example, assume that the first threshold is set to 5 seconds; whenever the user terminal receives the fetal heart rate data, it is judged whether the remaining playing time of the rhythm file is less than 5 seconds ; If the remaining playback time is less than 5 seconds, the user terminal saves the received fetal heart rate data to the first queue; if the remaining playback time is greater than or equal to 5 seconds, the user terminal discards the received fetal heart rate data.

In addition, in application scenarios such as downloading fetal heart rate data from the server on the client side, or using its own stored fetal heart rate data, as another possible implementation method, refer to Figure 12 on the basis of Figure 3. 12 shows still another schematic flowchart of the music playing method provided by the present application. Before step 202 is performed, the music playing method may further include the following steps:

Step 201-6, save the read historical fetal heart rate data to the first queue, and update the number of data;

In one embodiment, the user terminal can use the fetal heart rate data stored by itself or the fetal heart rate data downloaded from the server as historical fetal heart rate data; then, the user terminal can read the historical fetal heart rate data, and according to the time series, Save the read historical fetal heart rate data to the first queue, and update the number of data, where the number of data is configured to indicate the number of historical fetal heart rate data saved in the first queue; for example, when the number of data is " When it is 4", it means that the number of historical fetal heart rate data saved in the first queue is 4, that is, the first queue saves 4 seconds of fetal heart rate data.

Therefore, the user end can monitor the number of data, and when the number of data reaches the second threshold, the user end can execute step 202 and read the historical fetal heart rate data stored in the first queue according to the second threshold to obtain the target fetus. Heart data, and reset the first queue and the number of data.

For example, assuming that the second threshold is set to "5", when the number of monitored data on the user end reaches "5", the user end can read "5" historical fetal heart rate data saved in the first queue, thereby setting "5" One historical fetal heart rate data is used as the target fetal heart rate data, then the first queue is cleared, and the number of data is reset to "0".

In addition, in some possible implementation manners, the user can also choose to save the continuously played melody file, so that the user can share it or play it again.

Therefore, as a possible implementation manner, on the basis of FIG. 3, please refer to FIG. 13. FIG. 13 shows still another schematic flowchart of the rhythm playing method provided in this application. The playing method may also include the following steps:

Step 208: Save the target melody file to the second queue;

Step 210: When the merge instruction is received, merge all the melody files in the second queue to generate an audio file.

In an embodiment, the user terminal may be provided with a second queue, and the second queue is configured to save the rhythm file corresponding to the fetal heart rate data.

For this reason, after the user terminal obtains the target melody file in step 206, the user terminal can save the target melody file to the second queue; and, when the user terminal receives the merge instruction, the user terminal can save all the melody files in the second queue. The files are merged to generate audio files.

For example, the user end may use the received composition end instruction as a merge instruction. When receiving the composition end instruction, the user end may execute step 210 to merge all the rhythm files in the second queue to generate an audio file, and generate an audio file. The audio file of is saved locally, or uploaded to the cloud server for storage; or, when the user terminal uses historical fetal heart rate data for rhythm playback, if the user terminal finishes reading the historical fetal heart rate data, the traversal ends all the fetal heart rate According to the data, the user terminal can determine to obtain the merge instruction, and thus execute step 210.

In the embodiments provided in this application, it should be understood that the disclosed method may also be implemented in other ways. The method embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the drawings show the possible implementation architecture, functions, and functions of the functional modules, methods, and computer program products according to some embodiments of the present application. operate. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more options that can realize the specified logical function. Execute instructions.

It should also be noted that in some alternative implementations, the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two consecutive blocks can actually be executed in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved.

It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or actions Or it can be realized by a combination of dedicated hardware and computer instructions.

In addition, the functional modules in some embodiments of the present application may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.

If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

Moreover, the above description is only a part of the embodiments of the present application, and does not mean to limit all the implementation manners of the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection scope of this application.

For those skilled in the art, it is obvious that the present application is not limited to the details of the foregoing exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of this application is defined by the appended claims rather than the above description, and therefore it is intended to fall into the claims. All changes in the meaning and scope of the equivalent elements of are included in this application. Any reference signs in the claims should not be regarded as limiting the claims involved.

Industrial applicability

According to a rhythm playing method, user terminal, and storage medium provided by the present application, the target fetal heart rate data is obtained, and the corresponding relationship between multiple fetal heart rate data and multiple rhythm files is recorded according to the rhythm configuration rule to obtain the target fetal heart rate. The target melody file corresponding to the data is played, and compared with the prior art, the target fetal heart rate data is converted into a melody that the user can perceive, thereby enhancing the user's perception and enhancing the interactive effect.

In addition, the user terminal uses different duplicate files to distinguish between the fetal movement data and the fetal movement data not contained in the fetal heart rate data, so that the user can distinguish whether the fetus has occurred when the corresponding fetal heart rate data is collected through different duplicate files. Fetal movement, thereby enhancing user perception and enhancing interactive effects.

Claims (18)

1. A method for playing music, characterized in that the method includes:

   Obtain target fetal heart rate data;

   Obtain a target rhythm file corresponding to the target fetal heart rate data according to the rhythm configuration rule; wherein the rhythm configuration rule records the correspondence between multiple fetal heart rate data and multiple rhythm files;

   Playing the target melody file.
2. The method according to claim 1, wherein the target fetal heart rate data includes multiple fetal heart rate values; the rhythm configuration rule records the correspondence between multiple fetal heart rate ranges and multiple melody files;

   According to the rhythm configuration rule, the step of obtaining the target rhythm file corresponding to the target fetal heart rate data includes:

   Obtaining an average fetal heart rate value of the multiple fetal heart rate values included in the target fetal heart rate data;

   Determine the melody file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file; wherein, the target fetal heart rate range is where the average fetal heart rate value is located in the plurality of fetal heart rate ranges Fetal heart rate range.
3. 3. The method of claim 2, wherein each melody file includes a first copy file and a second copy file;

   The step of determining the melody file corresponding to the target fetal heart rate range in the melody configuration rule as the target melody file includes:

   Judging whether the target fetal heart rate data includes a fetal movement identifier;

   When the target fetal heart rate data does not include a fetal movement identifier, determining the first copy file included in the melody file corresponding to the target fetal heart rate range as the target melody file;

   When the target fetal heart rate data includes a fetal movement identifier, the second copy file included in the melody file corresponding to the target fetal heart rate range is determined as the target melody file.
4. The method according to claim 2 or 3, wherein each melody file includes a plurality of sub-melody files;

   The step of determining the melody file corresponding to the target fetal heart rate range in the melody configuration rule as the target melody file includes:

   The target melody file is determined among multiple sub-melody files included in the melody file corresponding to the target fetal heart rate range.
5. The method of claim 1, wherein the target fetal heart rate data includes multiple fetal heart rate values; the rhythm configuration rule records the correspondence between multiple fetal heart rate ranges and multiple note files;

   According to the rhythm configuration rule, the step of obtaining the target rhythm file corresponding to the target fetal heart rate data includes:

   Obtaining an average fetal heart rate value of the multiple fetal heart rate values included in the target fetal heart rate data;

   In the rhythm configuration rule, the note file corresponding to the target fetal heart rate range is determined as the target rhythm file; wherein, the target fetal heart rate range is where the average fetal heart rate value is located in the multiple fetal heart rate ranges Fetal heart rate range.
6. The method of claim 5, wherein each note file includes a plurality of sub-note files;

   The step of determining the note file corresponding to the target fetal heart rate range in the rhythm configuration rule as the target rhythm file includes:

   The target melody file is determined among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range.
7. 8. The method of claim 6, wherein each sub-note file corresponds to configuration parameters;

   Among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range, the step of determining the target rhythm file includes:

   Among the multiple sub-note files included in the note file corresponding to the target fetal heart rate range, the target sub-note file whose difference between the corresponding configuration parameter and the set configuration parameter is within the set range is determined as the target sub-note file Describe the target melody file.
8. 8. The method of claim 7, wherein the method further comprises:

   Update the set configuration parameters according to the configuration parameters of the target melody file.
9. 8. The method according to any one of claims 5-8, characterized in that, before the step of playing the target melody file, the method further comprises:

   When the target fetal heart rate data contains a fetal movement identifier, adjusting the scale of the target rhythm file;

   The step of playing the target melody file includes:

   Play the target temperament file after adjusting the scale.
10. 9. The method of claim 9, wherein the step of adjusting the scale of the target melody file comprises:

    Raise the scale of the last note of the target melody file.
11. 9. The method of claim 9, wherein the step of adjusting the scale of the target melody file comprises:

    The fetal movement identification sound is added to the last sound of the target melody file.
12. The method according to any one of claims 1-11, wherein before the step of obtaining a target rhythm file corresponding to the target fetal heart rate data according to a rhythm configuration rule, the method further comprises:

    The timbre configuration rule is determined in the timbre type strategy; wherein, the timbre type strategy includes multiple configuration rules.
13. The method according to any one of claims 1-12, wherein before the step of obtaining target fetal heart rate data, the method further comprises:

    Save the received fetal heart rate data to the first queue;

    The steps to obtain target fetal heart rate data include:

    The first queue is read in chronological order to obtain the target fetal heart rate data.
14. The method of claim 13, wherein before the step of saving the received fetal heart rate data to the first queue, the method further comprises:

    Determine whether the remaining playing time is less than the first threshold;

    When it is yes, execute the step of saving the received fetal heart rate data to the first queue.
15. The method according to any one of claims 1-12, wherein before the step of obtaining target fetal heart rate data, the method further comprises:

    Save the read historical fetal heart rate data to the first queue, and update the number of data; wherein the number of data is configured to indicate the number of historical fetal heart rate data stored in the first queue;

    When the number of data reaches the second threshold, the step of obtaining target fetal heart rate data includes:

    Read the historical fetal heart rate data stored in the first queue according to the second threshold to obtain the target fetal heart rate data, and reset the first queue and the number of data.
16. 15. The method according to any one of claims 1-15, wherein, after the step of obtaining a target melody file corresponding to the target fetal heart rate data in the melody file library, the method further comprises:

    Saving the target rhythm file to a second queue; wherein the second queue is configured to save the rhythm file corresponding to the fetal heart rate data;

    When the merge instruction is received, all the melody files in the second queue are merged to generate an audio file.
17. A user terminal, characterized in that it includes:

    The memory is configured to store one or more programs;

    processor;

    When the one or more programs are executed by the processor, the method according to any one of claims 1-16 is realized.
18. A computer-readable storage medium with a computer program stored thereon, wherein the computer program implements the method according to any one of claims 1-16 when the computer program is executed by a processor.

Images