RU2801333C1 - Method of control of the number of data streams, terminal device and mimo system - Google Patents

Abstract

FIELD: data communication.

SUBSTANCE: invention relates to means for regulating the number of data streams. The tag may actively negotiate the number of transport layers used in the downlink process with the network device based on the operating state of the tag to adaptively and dynamically adjust the number of data streams in the downlink process.

EFFECT: reduction in the power consumption of the terminal device and an extension of the operation time of the terminal device in the standby reception mode.

28 cl, 1 tbl, 19 dwg

Description

The technical field to which the invention belongs

Embodiments of the present application relate to mobile communication technologies and, in particular, to a method for controlling the number of data streams in a Multiple-Input Multiple-Output (MIMO) system, a terminal device, and a MIMO system.

State of the art

MIMO refers to the technology of using multiple antennas at the transmitting end and at the receiving end to transmit and receive signals, respectively. MIMO is widely used in long term evolution (LTE) system, ^fifth generation mobile network (5G) system, further developed MIMO mobile system, and the like.

In a mobile MIMO system, MIMO technology can make full use of space resources and improve the channel capacity and communication quality, but the power consumed by the terminals increases. The power consumption of terminal devices is an important factor influencing the user's experience of their use. In the process of using MIMO technology, how to minimize the power consumption of terminal devices while at the same time ensuring the signaling rate to improve the user experience of their application is the direction of research of specialists in this field of technology.

Disclosure of the essence of the invention

Embodiments of the present application provide a method for regulating the number of data streams, a terminal device, and a MIMO system to reduce the power consumed by the terminal device and extend the terminal device's standby time while still meeting the data rate requirements of the terminal device.

In accordance with the first approach, an embodiment of the present application provides a method for regulating the number of data streams, which is applied on the side of the terminal device. The MIMO system includes a terminal device and a network device, and the number of transport layers used by the MIMO system in a downlink process is the first number of transport layers. The method comprises the steps in which: the terminal device recognizes the first scenario and sends a first message to the network device, where the first message is used to request the network device to reduce the number of transport layers used in the process of downstream data transfer, the first message carrying the second number of transport layers, and the second number of transport levels is less than the first number of transport levels; the terminal device receives a second message transmitted by the network device, where the second message is used to configure the number of transport layers in the downlink process, and the second message carries a third number of transport layers and a third number of transport layers less than or equal to the second number of transport layers; and the terminal device receives and analyzes the downlink signal transmitted by the network device based on the third number of transport layers.

With reference to the first approach, one transport layer corresponds to one data stream, and different transport layers are differentiated by different data streams. By implementing the method according to the first approach, the tag can actively negotiate the number of transport layers used in the downlink process to the network device based on the operating state of the tag device to adaptively and dynamically adjust the number of data streams in the downlink process. This method of regulating the number of data streams can reduce the power consumed by the terminal and increase the terminal's standby time without affecting the user experience of the terminal while still meeting the data rate requirements of the terminal.

With reference to the first approach, in some embodiments, the first scenario is one in which only a small number of data streams are needed to meet the data rate requirement of the terminal. The first scenario may contain one event or a combination of more of the following events: event A: on the end device, the first application is running in the foreground; event B: the data rate of the target device is less than the first threshold; event C: the power of the signal transmitted by the network device and received by the terminal device is greater than the second threshold; event D: terminal screen is off; event E: end device enters power saving mode; event F: end device is not charged; and event G: terminal temperature is above the third threshold.

In some embodiments, what the tag specifically recognizes as the first scenario comprises one or more of the following: the tag receives the operation of a user clicking on the first application icon on the home screen, the tag detects that the strength of the received reference signal received power, RSRP) or reference signal received power RSRP is less than the second threshold, the terminal device does not accept user operation for a specified time when the screen is on, the terminal device receives a power key operation when the screen is on, or the terminal device receives a user operation affecting the power saving mode control switch.

With reference to the first approach, in some embodiments, the tag may further recover the number of transport layers used in the downlink process. Namely, after the downlink signal transmitted by the network device is received and parsed based on the third number of transport layers, the terminal device can further recognize the second scenario corresponding to the first scenario and send a third message to the network device, where the third message is used to request the network device to recover the number of transport layers used in the downlink process; then, the tag may further receive a fourth message transmitted by the network device, where the fourth message is used to configure the number of transport layers in the downlink process, and the fourth message carries the first number of transport layers; and then the terminal device receives and analyzes the downlink signal transmitted by the network device based on the first number of transport layers. Thus, the number of downstream data streams can be flexibly adjusted to meet the data rate requirements of the terminal device in the second scenario and improve the user experience of the terminal device.

With reference to the second approach, in some embodiments, the implementation of the second scenario is a scenario in which more data flows are needed to meet the data rate requirements of the terminal device. The second scenario may include one of the following, or a combination of more of the following: on the terminal, the application that is running in the foreground is not the first application, the data rate of the terminal is greater than a fourth threshold, the strength of the signal transmitted by the network device and received by the terminal, is less than the fifth threshold, the end device's screen is on, the end device is entering performance mode, the end device is charging, or the temperature of the end device is below the sixth threshold.

In some embodiments, what the tag recognizes as the second scenario corresponding to the first scenario specifically comprises one or more of the following events: event a: the application that the tag is running in the foreground is not the first application; event b: the data rate of the target device exceeds the fourth threshold; event c: the power of the signal transmitted by the network device and received by the terminal device is less than the fifth threshold; event d: terminal screen is on; event e: end device enters performance mode; event f: end device is charging; and event g: the temperature of the terminal device is below the sixth threshold.

In some embodiments, the first scenario may be set by the terminal in advance by default, or may be independently set by the user. After the first scenario is defined, a second scenario corresponding to the first scenario is also defined.

For example, when the low rate scenario is the scenario in which event A occurs at the terminal device, the corresponding high rate scenario is the scenario in which event a occurs at the terminal device. When the low rate scenario is the scenario in which event B occurs at the terminal device, the corresponding high rate scenario is the scenario in which event b occurs at the terminal device.

When the low rate scenario is one in which event A and event B occur at the terminal device at the same time, the corresponding high rate scenario is one in which any one or more of event a and event b occur at the terminal device. When the low rate scenario is a scenario in which event B and event C occur at the terminal at the same time, the corresponding high rate scenario includes a scenario in which any one or more of event b and event c occur at the terminal.

When the low rate scenario is one in which event A, event B, event C, event E, and event F occur at the same time at the terminal, the corresponding high rate scenario is one in which any one or more of event a, event b occur at the terminal. , events c, events e, and events f, and so on.

In some embodiments, the time interval between the time the tag receives the second message and the time the tag recognizes the second scenario is greater than or equal to the first time interval. The interval between two successive adjustments of the number of data streams in the process of downlink data transmission by the MIMO system is greater than or equal to the first time period. This can prevent a situation in which a terminal often switches between a low rate scenario and a high rate scenario, so that the MIMO system often does not adjust the number of data streams in the downlink process.

In some specific embodiments, upon receiving the second message, the terminal may start the timer (timer) of the first period of time and begin to recognize at the time the timer expires whether the current scenario is the second scenario.

With reference to the first approach, in some embodiments, if in the first scenario on the tag the first application is running in the foreground, the time interval between the time the tag starts the first application in the foreground and the time the tag recognizes the first scenario , greater than or equal to the second time interval. This can ensure that the number of downstreams does not decrease in the second time period when the first application starts running in the foreground on the terminal device, and ensure that the terminal device has a higher data rate in the second time period, thus improving , the user's perception of the operation of the terminal device.

In a specific embodiment, when the first application starts (eg, by accepting a user tap operation by clicking on the first application icon on the home screen) in the foreground, the terminal device can start the timer (timer) of the second period of time and recognize whether the current scenario is the first scenario, when the timer expires.

With reference to the first approach, in some embodiments, the first message is a UE supplementary information message for the supplementary message, and the second number of transport layers is carried in the reducedMIMO-LayerFRI-DL field of the supplementary message.

With reference to the first approach, in some embodiments, the second message is an RRC reconfiguration for the Radio Resource Control, RRC Reconfiguration message, and the third number of transport layers is carried in the MaxmimoLayerNum field in the PDSCH service cell configuration for the physical downlink shared service cell configuration message. channel.

In some embodiments, the third message is a supplemental UE information message for the supplementary message and the third message does not contain a reducedMIMO-LayerFRI-DL field.

In some embodiments, the fourth message is an RRC reconfiguration for the radio resource control (RRC) reconfiguration message and the first number of transport layers carried in the fourth message is carried in the MaxmimoLayerNum field in the PDSCH service cell configuration for the service cell configuration message physical downlink shared channel.

With reference to the first approach, in some embodiments, the first number of transport layers is configured by the network device for the terminal device in response to the UE's capability reporting capability information for the capability message transmitted by the terminal. In some embodiments, the capability message carries the maximum number of downstream transport layers supported by the terminal. The maximum number of downlink transport layers supported by the terminal is less than or equal to the number of antennas configured by the terminal to provide 5G bandwidth, and less than or equal to the number of RF paths configured by the terminal.

With reference to the first approach, in a specific example, the first number of transport layers may be 4, the second number of transport layers may be 2, and the third number of transport layers may be 2.

With reference to the first approach, in some embodiments, the terminal device receiving and analyzing the downlink signal transmitted by the network device based on the third number of transport layers specifically comprises: receiving by the terminal device using the third number of transport layer antennas, the downlink signal transmitted by the network device, filtering and amplifying the downlink signal, and converting the downlink signal to baseband signal using the third number of transport layer receive RF paths, and performing the inverse layer mapping process on the baseband signal using the third number of transport layers.

With reference to the first approach, in some embodiments, the MIMO system may further reduce the number of transport layers used in the uplink process based on the operating state of the terminal.

Specifically, the number of transport layers used by the MIMO system in the uplink process is the fourth number of transport layers; the first message further carries a fifth number of transport layers and a fifth number of transport layers less than a fourth number of transport layers; the second message is also used to configure the number of transport layers in the uplink data transmission process, the second message further carries a sixth number of transport layers and a sixth number of transport layers less than or equal to the fifth number of transport layers. The tag may then transmit an upstream signal to the network device based on the sixth number of transport layers.

Thus, the tag can actively negotiate the number of transport layers used in the uplink process with the network device based on the operating state of the tag to adaptively and dynamically adjust the number of data streams in the uplink process. This method of regulating the number of data streams can reduce the power consumption of the terminal and extend the terminal's standby time without affecting the user's experience of the operation of the terminal while meeting the data rate requirements of the terminal.

In some embodiments, the tag may further recover the number of transport layers used in the uplink process. Namely, the third message sent by the terminal device is further used to request the network device to recover the number of transport layers used in the uplink process; the fourth message received by the terminal is further used to configure the number of transport layers in the uplink process, and the fourth message carries the fourth number of transport layers. The tag may then transmit an uplink signal to the network device based on the fourth number of transport layers. Thus, the number of uplinks can be flexibly adjusted to meet the data rate requirement of the terminal in the second scenario and improve the user's experience of the operation of the terminal.

In some embodiments, the first message is a UE supplementary information message for the supplementary message, and the fifth number of transport layers carries the reducedMIMO-LayerFRI-UL field of the supplementary message.

In some embodiments, the second message is a reconfiguration of the RRC reconfiguration message for RRC radio resource control, and the sixth number of transport layers carries a MaxMimoLayerCnt field in the PDSCH service cell configuration for the physical downlink shared channel service cell configuration message.

In some embodiments, the third message is a supplemental UE information message for the supplementary message and the third message does not contain a reducedMIMO-LayerFRI-UL field.

In some embodiments, the fourth message is a reconfiguration RRC message for RRC radio resource control reconfiguration and the fourth number of transport layers carries a MaxMimoLayerNum field in the PDSCH service cell configuration for the physical downlink shared channel service cell configuration message.

In some embodiments, the fourth number of transport layers is configured by the network device for the terminal device in response to the capability information of the UE for the capability report sent by the terminal device. In some embodiments, the capability message carries the maximum number of uplink transport layers supported by the terminal. The maximum number of uplink transport layers supported by the terminal is less than or equal to the number of antennas configured by the terminal to provide 5G bandwidth, and less than or equal to the number of RF transmission paths configured by the terminal.

In a specific example, the fourth number of transport levels may be 2, the fifth number of transport levels may be 1, and the sixth number of transport levels may be 1.

In some embodiments, a terminal sending an uplink signal to a network device based on the sixth number of transport layers specifically comprises: performing a level mapping on the baseband signal by the terminal using the sixth number of transport layers, converting the baseband signal to an RF signal, and filtering and amplifying the RF signal, using a third number of transport layers of RF receive paths to receive an uplink signal, and sending an uplink signal using a third number of transport layer antennas.

With reference to the first approach, the method corresponding to the first approach can be applied to a 5G system in SA networking mode. That is, both the terminal device and the network device support the 5G band and operate in the 5G band, and the network device connects to the 5G core network (5GC). In addition, the network device is a gNodeB device, and the terminal device communicates with the network device using an NR link.

With reference to the first approach, the method corresponding to the first approach is applicable to an LTE system. In the LTE system, both the terminal device and the network device both support the 4G band and operate in the 4G band, and the network device connects to the EPC. In addition, the network device is an eNodeB device, and the terminal device communicates with the network device using an LTE communication channel.

With reference to the first approach, the method corresponding to the first approach can further be applied to the MIMO system in the future development of mobile communications, and no limitation is imposed in the embodiment of the present application.

In accordance with the second approach, an embodiment of the present application provides a terminal device containing one or more processors and one or more memories. One or more memories are associated with one or more processors. One or more memories are configured to store a computer control program. The computer control program contains computer instructions, and when one or more processors execute the computer instructions, the terminal device is configured to implement a method corresponding to any of the first approach or possible implementations of the first approach.

According to a third approach, an embodiment of the present application provides a computer medium containing computer instructions which, when those computer instructions are executed on a terminal device, causes the communication device to execute the method corresponding to the first approach or possible implementations of the first approach.

According to a fourth approach, an embodiment of the present application provides a computer program product in which, when the computer program product is running on the computer, the computer executes the method according to the first approach or possible implementations of the first approach.

In accordance with the fifth approach, an embodiment of the present application provides a MIMO system comprising a terminal device and a network device, where the terminal device may be a terminal device corresponding to the second approach.

By implementing the technical solutions according to the embodiments of the present application, the tag can actively negotiate with the network device the number of transport layers used in the downlink process based on the operating state of the tag device to adaptively and dynamically adjust the number of data streams in the downlink process. This method of regulating the number of data streams can reduce the power consumption of the terminal and extend the terminal's standby time without affecting the user's experience of the terminal while meeting the data rate requirements of the terminal.

Brief description of the drawings

Fig. 1A is a schematic representation of the hardware involved in the processing of information by a network device in a downlink process;

fig. 1B is a schematic representation of the hardware involved in the processing of information by the terminal during the downlink process;

fig. 2 is a schematic representation of the structure of a MIMO system according to an embodiment of the present application;

fig. 3A is a schematic representation of the hardware structure of a terminal device according to an embodiment of an embodiment of the present application;

fig. 3B is a schematic representation of the software architecture of a terminal device according to an embodiment of the present application;

fig. 3C is a schematic representation of a hardware structure of a network device according to an embodiment of the present application;

fig. 4A-4C(1)-4C(2) - a user interface implemented on a terminal device corresponding to an embodiment of the present application;

fig. 5 is a flowchart of a method for controlling the number of downstream data streams in a MIMO system according to an embodiment of the present application;

fig. 6A and FIG. 6B is a schematic representation of time nodes for controlling the amount of downstream data in the MIMO system according to Embodiment 1;

fig. 7 is a flowchart of a method for controlling the amount of downstream data in a MIMO system according to an embodiment of the present application;

fig. 8A and FIG. 8B is a schematic representation of temporary nodes for controlling the amount of downstream data in the MIMO system according to Embodiment 2;

fig. 9 is a flowchart of a method for controlling the number of downstream data streams in a MIMO system according to an embodiment of the present application;

fig. 10A and FIG. 10B is a schematic representation of time nodes for controlling the amount of downstream data in the MIMO system according to Embodiment 3; And

fig. 11 is a flowchart of a method for controlling the amount of uplinks in a MIMO system according to an embodiment of the present application.

Implementation of the invention

The technical solutions in the embodiments of the present application will be clearly and in detail described with reference to the accompanying drawings. In the descriptions of embodiments of the present application, unless otherwise specified, "/" means "or", for example, A/B can mean A or B. The term "and/or" in this description represents only a relationship relationship for describing related objects and represents that three relations can exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. Also, in the description of embodiments of the present application, "multiple" refers to two or more.

Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying the relative importance or implying the number of said technical features. Therefore, a feature defined using the terms "first" or "second" may explicitly or implicitly contain one or more features, and in the descriptions of embodiments of the present application, "many" means two or more, unless specifically defined otherwise.

The MIMO technology is applicable to uplink data transmission and downlink data transmission in the field of mobile communication. The amount of downstream data transfer is usually much larger than the amount of upstream data transfer. The following embodiments of the present application will be explained mainly using the application of MIMO technology in a downlink process as an example. The downlink processes mentioned in the following embodiments are all downlink processes based on MIMO technology, that is, downlink processes performed in a MIMO system.

The downlink process must be terminated by the network device (eg, base station) and terminal device together. In the downlink process, the network device is the transmitting end of the signal transmission, and the terminal device is the receiving end of the signal reception. A terminal device may also be referred to as user equipment (UE). The network device converts the original data stream into multiple parallel signal paths that are transmitted from multiple transmit antennas simultaneously, respectively; and a plurality of receive antennas at the receiving end receive the signals and analyze the signals to recover the original signals. In this process, multiple data streams may be transmitted in parallel over the air.

During the downlink process, the network device must process the original data to be sent to the terminal device to ensure that the original data can be transmitted over the wireless spatial channel between the network device and the terminal device. In FIG. 1A shows the device used by the network device during raw data processing. The processing contains mainly baseband processing and RF processing.

First of all, the baseband processing mainly contains the physical layer algorithm executed by the baseband integrated circuit (baseband processor, baseband processor) (baseband integrated circuits, baseband integrated circuits, BBIC), upper layer protocol processing, implementation of multi-mode compatibility, etc. .P. Baseband processing may include the following:

1. Scrambling

Scrambling refers to calculation on patterns, and pattern scrambling is used to randomize interference between data and can resist interference. Codewords are a bitstream obtained after channel coding and interleaving. A bitstream is obtained by processing raw data (eg, images, text, web pages, or videos) by a network device.

2. Modulation

Modulation is the process of mapping a bit stream onto a complex plane and is also referred to as complex modulation.

3. Layer mapping

The layer mapping must reorganize the modulated bitstreams based on certain rules and map codewords independent of each other to the spatial transport layer (layer). Since the number of codewords and the number of levels are not necessarily the same, a display of levels is required. One level corresponds to one data stream and different levels are distinguished by different data streams. That is, the data flow refers to the data transmitted at the same level. The number of layers is less than or equal to the rank (rank) of the MIMO channel matrix.

4. Precoding

The precoding must represent the data output by each layer to a different antenna port for diversity or multiplexing purposes.

5. Resource mapping and generation of orthogonal frequency division multiplexing (OFDM) signals.

Resource mapping refers to the mapping of pre-coded data into a two-dimensional physical resource element (resource element, RE) consisting of subcarriers and time slots at each specific antenna port.

The radio frequency processing mainly comprises a conversion between a baseband signal and a radio frequency signal performed by an integrated radio frequency circuit (radio frequency processor, radio frequency processor) (radio frequency integrated circuits, RFIC). The RF processor may convert the baseband signal output from the baseband processor to an RF signal. The RF processor may alternatively be implemented as a modulator and demodulator.

The RF processing further comprises signal processing performed by the RF Front End Module (FEM). The RF input module may contain: a power amplifier (PA), a filter (filter), a duplexer or multiplexer (duplexer or multiplexer), a low noise amplifier (LNA), an antenna switch (switch) or a tunable antenna module ( antenna tuning module, ASM), etc. During the downlink process, the PA is configured to amplify the power of the signal output from the baseband processor, and the filter is configured to filter the signal.

The processed signal is then transmitted using a physical antenna and a duplexer. After the network device transmits the processed signal using the antenna, the signal is transmitted through the spatial channel and received by the multiple physical antennas (antenna, ANT) of the terminal device. Here, the number of physical antennas used by the terminal is related to the number of layers negotiated with the MIMO system. The number of physical antennas used by a terminal is typically equal to the number of layers negotiated with the MIMO system. Upon receiving the signal, the physical antennas of the terminal device perform the reverse processing on the signal by the network device.

In FIG. 1B is a schematic diagram of a scenario in which a terminal device processes a received signal. Specifically, the terminal device first performs RF processing of the received signal, which mainly comprises filtering the signal with a filter, the LNA performs a low-noise signal amplification process, and the RF processor converts the RF output signal from the output of the RF front end module to a baseband signal. Here, devices (comprising RFIC, filter, LNA, etc.) participating in the RF processing of one signal channel (ie, data stream) can be combined into an RF path. Finally, the terminal performs baseband inverse processing on the signal. The terminal device first reads the corresponding data from the OFDM time-frequency resource, performs the inverse processes of precoding and level mapping, then performs demodulation and descrambling, and finally restores the original information bits. Then, a higher level terminal device, such as a MAC or an application, can read the values of the original information bits based on the encapsulation method and the source encoding method, and restore the original data (such as images, text, web pages, video, or audio) transmitted network device.

It should be understood that in a downlink process, more layers indicate more physical antennas used when the terminal device receives the signal transmitted by the network device and more RF receive paths used for signal processing. The RF receive path may include a filter, an LNA, a radio frequency processor (RFIC), and the like. As shown in FIG. 1B, when the number of layers is 4, the terminal can use four antennas (ANT1-ANT4) to receive different data streams. One data stream received by ANT1 is processed by the RF receive path containing Rx_l_A, one data stream received by ANT2 is processed by the RF receive path containing Rx_l_B, one data stream received by ANT3 is processed by the RF receive path containing Rx_2_A, and one data stream, received by ANT4 is processed by a receive RF path containing Rx_2_B. When the number of layers is 2, the terminal can receive data streams using four antennas (ANT1-ANT4). ANT1 and ANT2 receive one data stream, and ANT3 and ANT4 receive another data stream; or the terminal device can receive different data streams using two antennas ANT1 and ANT2, respectively; and after each antenna receives the data streams, the data streams are transmitted to the respective RF receive paths for processing.

It should be understood that the number of layers can affect the data processing of the terminal during the downlink process, mainly including in the baseband processing the number of receive antennas used by the terminal, the number of receive RF paths used, and the inverse layer mapping and precoding processes.

Obviously, in a downlink process, more data streams indicate more layers, more antennas and RF receive paths used by the terminal, and higher power consumption.

In existing technology, the number of data streams in a downlink process is typically determined based on the hardware capabilities (eg, number of antennas and number of RF receive paths) of the terminal. In this method of determining data streams, as many data streams as possible are selected for downlink data transmission with the support of the terminal device in order to guarantee high-speed data transmission. Although this method can satisfy the requirement of high data rate in a MIMO system, the actual data transmission and power consumption requirements of the terminal device are not considered, which will lead to excessively high power consumption of the terminal device and affect the user's perception of the operation of the terminal device. For example, in a 5G MIMO mobile system, a network device (e.g., next generation NodeB (gNB)) typically allocates four tag layers for downlink data transmission, that is, four data streams can be used for downlink data transmission between a tag and network device. However, when the downlink speed requirements of the terminal device are low, such as in some online text reading scenarios, the actual data transmission requirements of the terminal device can be met by using two data streams, and if four data streams are used, this is excessively wasteful and may increase the power consumption of the terminal device.

Based on the shortcomings of the existing technology, the following embodiments of the present application present a method for controlling the number of data streams, a terminal device, and a MIMO system.

According to the method according to an embodiment of the present application, a terminal in a MIMO system may request a network device to reduce the number of layers in the downlink and/or uplink process in some scenarios where the data rate requirements are low. In addition, in some scenarios where the data rate requirements are higher, the tag may additionally request the network device to restore the number of layers during the downlink and/or uplink. Adjusting the number of levels is equivalent to adjusting the number of data streams. Thus, the tag can actively negotiate the number of layers used in the downlink and/or uplink process with the network device based on the operating state of the tag to adaptively and dynamically adjust the number of data streams in the downlink and/or uplink process. This method of regulating the number of data streams can reduce the power consumption of the terminal device and extend the terminal's standby time without affecting the user's perception of the operation of the terminal device while meeting the data rate requirements of the terminal device.

For ease of description, in the following embodiments, a scenario in which the data rate requirement of a terminal device is low is referred to as a low rate scenario. The low rate scenario can be a single event or a combination of more of the following events: event A: the first application executed by the end device is running in the foreground; event B: the data rate of the target device is less than the first threshold; event C: the power of the signal transmitted by the network device 200 and received by the terminal device is greater than the second threshold, event D: the screen of the terminal device is turned off; event E: end device enters power saving mode; event F: end device is not charging; and event G: terminal temperature is above the third threshold.

For ease of description, in the following embodiments, a scenario in which the data rate requirement of the terminal device is higher is referred to as a high rate scenario. The high-velocity scenario is evaluated relative to the low-velocity scenario. The high rate scenario may be a single event or a combination of more of the following events: event a: the application being run by the terminal in the foreground is not the first application; event b: fourth threshold terminal data rate; event c: the power of the signal transmitted by the network device 200 and received by the terminal device is less than the fifth threshold; event d: terminal screen is on; event e: end device enters performance mode; event f: end device is charging; and event g: the temperature of the terminal device is below the sixth threshold.

In the following embodiments of the method, the specific meaning of the low-rate scenario and the high-rate scenario and the method for recognizing the low-rate scenario and the high-rate scenario by the terminal device are explained in detail and are not described in detail here.

The method according to the embodiment of the present application can be applied to MIMO systems using MIMO technology, such as a long-term evolution (LTE) system, a fifth generation mobile network (5G) network system, and a mobile MIMO system, developed further. The network mode of a 5G system can be standalone (SA) network or non-standalone (NSA) network.

In FIG. 2 schematically shows the structure of a MIMO system 10 according to an embodiment of the present application. The MIMO system 10 shown in FIG. 2, can operate in the high frequency band, and specifically can be an LTE system, a 5G system, a New Radio (NR) system, a machine to machine (M2M) communication system, a Wi-Fi system, etc. .P.

As shown in FIG. 2, MIMO system 10 includes terminal device 100 and network device 200.

The terminal device 100 may be a smartphone (for example, an Android or iOS phone), a tablet computer, a laptop computer, a PDA, a mobile Internet device (MID), a wearable device (for example, a smart watch or smart band), radio unit, remote unit, end agent, mobile client, or other device that can access the Internet. Terminal device 100 may be fixed or mobile.

The network device 200 may be an evolved NodeB (eNB), gNB, an access point (AP), a transmit/receive point (TRP), a central unit (CU), or other network device. object. The network device 200 may be fixed or mobile.

The network device 200 is responsible for connecting the terminal device 100 to the core network using wired or wireless technology and provides a connection between the terminal device 100 and the network. That is, the network device 200 is configured to provide a wireless network access service to the terminal device 100. One or more wireless protocols may be used for communication between the network device 200 and the terminal device 100, and the communication protocols may include, but are not limited to, 802.11a/b/g/n/ac standards for LTE, LTE-advanced (LTE-A), high speed packet access (HSPA) and Wi-Fi. That is, communication between the network device 200 and the terminal device 100 may be performed using an LTE link, may be performed using an NR link, and may be performed using a Wi-Fi link.

The MIMO wireless system 10 is a MIMO system. The network device 200 may be provided with a large scale antenna array, and the terminal device 100 may also be provided with an antenna array. The multiple antennas of network device 200 and terminal device 100 may transmit signals using multi-antenna technologies such as space division multiplexing, space diversity, space diversity, space division multiple access, SDMA, or beamforming.

In this embodiment of the present application, in a low rate scenario, tag 100 may be used to request network device 200 to reduce the number of layers in the downlink process. Furthermore, in a high speed scenario, terminal device 100 may optionally be used to request network device 200 to recover the number of layers in the downlink process. After the network device 200 adjusts (reduces or restores) the number of layers in the downlink process based on the request of the terminal device 100, the number of data streams used in the MIMO system is also adjusted. Then, in the downlink process, terminal device 100 will use the adjusted number of layers to analyze the signal received from network device 200 to obtain the original data transmitted by network device 200. For the signal analysis process of terminal device 100, refer to FIG. 1B and accompanying descriptions.

Here, for the low rate scenario and the high rate scenario, refer to the detailed descriptions in the following method embodiments. For the method in which terminal device 100 requests network device 200 to adjust the number of layers in the downlink process, reference can also be made to detailed descriptions of subsequent embodiments of the method, and the method will not be described in detail here.

In this embodiment of the present application, the network device 200 may be configured to receive a message when the terminal device 100 requests regulation of the number of layers in the downlink process, and may in response to the message determine the number of layers to be used in the downlink process, with reference to frequency bands, antenna configurations, and the like. supported by the terminal device 100 and the network device 200, and notify the terminal device 100 of the determination result. Then, the network device 200 processes the raw data to be transmitted based on the determined number of layers, and transmits the processed signal to the terminal device 100. For the raw data processing process of the network device 200, refer to FIG. 1A and accompanying descriptions.

The structures of terminal device 100 and network device 200 corresponding to embodiments of the present application are described below.

In FIG. 3A shows an example of a schematic structure of terminal device 100.

End device 100 may include the following: processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charge control module 140, power management module 141, battery 142, antenna 1, antenna 2 , mobile module 150, wireless module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headset jack 170D, sensor module 180, key 190, motor 191, indicator 192, camera 193, display 194, module card interface 195 subscriber identification module (SIM), etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, an optical proximity sensor 180G, a digital fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, a 180L ambient light, 180M bone conduction sensor, etc.

It should be understood that the structure shown in this embodiment of the present application does not specifically limit the terminal device 100. In some other embodiments of the present application, the terminal device 100 may contain more or less components than shown in the drawing, combine some components or separate some components or have other layouts. The components shown may be implemented using hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, for example: processor 110 may include an application processor (AP), a modem processor (i.e., the RFIC mentioned in the previous embodiment), a graphics processing unit (GPU), a signal image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, etc. The various processor units may be independent devices or may be integrated into one or more processors.

The controller may be a control center and a command center of the terminal device 100. The controller may generate an operation control signal based on the operation code instruction and the clock signal, and read the instruction and control the execution of the instructions.

The processor 110 may further provide memory for storing instructions and data.

The USB interface 130 is an interface conforming to the specifications of the USB standard, and may specifically be a mini USB interface, a micro USB interface, a USB type C interface, or the like. USB interface 130 may be configured to connect a charger to charge terminal device 100 and may also be configured to transfer data between terminal device 100 and a peripheral.

The charge control module 140 is configured to connect a charging input from a charger. The charger may be a wireless charger or may be a wired charger.

Terminal 100 is provided with a plurality of antennas. The wireless communication function of terminal device 100 may be implemented using a plurality of antennas, such as antenna 1 and antenna 2, mobile communication module 150, wireless communication module 160, a modem processor, and a baseband processor.

The antennas are configured to transmit and receive electromagnetic wave signals. Each antenna in terminal 100 may be used to cover one or more communication bands. For example, terminal device 100 may comprise 11 antennas, where four antennas span the 5G NR communications band, four antennas span the LTE communications bandwidth, two antennas span the Wi-Fi communications bandwidth, and one antenna spans the GPS communications bandwidth. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a wireless LAN diversity antenna. In some other embodiments, an antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution containing wireless communication such as 2G/3G/4G/5G and applied to terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low Noise Amplifier, LNA), etc. The mobile communication unit 150 can receive electromagnetic waves using the antenna 1, perform filtering, amplification and other processing of the received electromagnetic waves, and transmit the waves to a modem processor for demodulation. The mobile communication unit 150 can further amplify the signal modulated by the modem processor and convert the signal into electromagnetic waves using the radiation antenna 1 . In some embodiments, at least some functional modules of the mobile communication module 150 may be located in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be located in at least the same device itself as some processor modules 110.

The modem processor may include a modulator and a demodulator. The modulator is configured to modulate the low frequency baseband signal to be transmitted into a medium to high frequency signal. The demodulator is configured to demodulate the received electromagnetic wave signal into a low frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs an audio signal using an audio device (not limited to speaker 170A, receiver 170B, or the like) or displays an image or video using display 194. In some embodiments, the modem processor may be an independent device. In some other embodiments, the implementation of the modem processor may be independent of the processor 110 and located in the same device as the module 150 mobile communication or other functional modules.

The wireless communication module 160 can provide wireless communication solutions applied to the terminal device 100, including a wireless local area network (WLAN) (such as a Wi-Fi network (wireless fidelity, Wi-Fi)), Bluetooth ( Bluetooth, BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (infrared, IR, IR) and etc. The wireless communication module 160 may be one or more devices that are integrated in at least one communication processing module. The wireless communication module 160 receives electromagnetic waves using the antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and transmits the processed signal to the processor 110. The wireless communication module 160 may further receive the signal to be transmitted from the processor 110, perform frequency modulation and signal amplification, and convert the signal into electromagnetic waves using antenna 2 for radiation.

In some embodiments, antenna 1 of terminal device 100 is associated with mobile communication module 150 and antenna 2 is associated with wireless communication module 160 such that terminal device 100 can communicate with the network and other devices (e.g., network device 200) using wireless technology. connections. Wireless technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband a wideband code division multiple access (WCDMA) system, a time division code division multiple access (TD-SCDMA) system, a long term evolution (LTE) system, NR, BT technologies, GNSS, WLAN, NFC, FM and/or IR, etc. GNSS can include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (quasi-zenith satellite system, QZSS) and/or augmentation systems based on satellite communications (satellite based augmentation systems, SBAS).

In this embodiment of the present application, the downlink process may be completed by the mobile communication module 150 of terminal device 100 acting in conjunction with other modules such as antenna and modem, or may be completed by the wireless communication module 160 of terminal device 100 acting in conjunction with other modules. .

In this embodiment of the present application, the processor 110 may be configured to recognize the low rate scenario and generate a message requesting the network device 200 to reduce the number of layers in the downstream data transmission process in the low rate scenario. The antenna may be configured to send a message to the network device 200 requesting the network device 200 to reduce the number of layers in the downlink process. The antenna may then further receive a message transmitted by the network device 200 indicating the number of levels after reduction. Here, for the specific implementation of the message transmitted by the antenna to request the network device 200 to reduce the number of layers in the downlink process and the message transmitted by the network device 200 to indicate the number of layers after reducing them, refer to the accompanying descriptions in the following embodiments of the method. Details are not described here.

In this embodiment of the present application, the processor 110 may be further configured to recognize the high speed scenario and generate a request message of the network device 200 to recover the number of layers in the downlink process in the high speed scenario. The antenna may be configured to send a network device 200 request message to the network device 200 to recover the number of layers in the downlink process. The antenna may then further receive from the network device 200 a message indicating the number of levels after recovery. Here, for the specific implementation of the message transmitted by the antenna to request the network device 200 to recover the number of layers in the downlink process and the message transmitted by the network device 200 to indicate the number of layers after recovery, refer to the accompanying descriptions in the following embodiments of the method. Details are not described here.

In this embodiment of the present application, in the downlink process, the terminal device 100 is used as the receiving end for receiving data, and the antenna of the terminal device 100 can be configured to receive a signal transmitted by the network device 200. A modem processor, an RF receive path (comprising RFIC, filter, LNA, etc.), and the baseband processor of the terminal device 100 are further configured to analyze the signal together. For the signal analysis process, refer to the preceding accompanying descriptions of FIG. 1b.

Terminal device 100 implements a display function using a GPU, display 194, application processor, or the like. The GPU is an image processing microprocessor and connects the display 194 to the application processor. The GPU is capable of mathematical and geometric calculations for graphical rendering. The processor 110 may include one or more GPUs, where the one or more GPUs execute software instructions to generate or modify display information.

The display 194 is configured to display an image, video, or the like. In some embodiments, terminal 100 may include one or N displays 194, where N is a positive integer greater than 1.

The internal memory 121 may be configured to store an executable control program, where the executable control program contains instructions. The processor 110 executes various functional applications and data processing of the terminal device 100 by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area.

The pressure sensor 180A is configured to detect the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be located on display 194. There are many types of pressure sensors 180A, such as a resistive pressure sensor, an inductive pressure sensor, and a capacitive pressure sensor. The capacitive pressure sensor may be a parallel plate containing at least two conductive materials. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. Terminal 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to the display 194, the terminal device 100 detects the intensity of the touch operation based on the pressure sensor 180A. Terminal 100 may also calculate the location of the touch based on the detection signal of pressure sensor 180A.

The temperature sensor 180J is configured to detect the temperature. In some embodiments, tag 100 performs the accepted temperature processing order using the temperature detected by temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, tag 100 reduces the performance of a processor located in the vicinity of temperature sensor 180J to reduce power consumption and implement thermal protection. In some other embodiments, when the temperature is below another threshold, terminal 100 warms battery 142 to prevent terminal 100 from crashing due to low temperature. In some other embodiments, when the temperature is below another other threshold, terminal 100 raises the output voltage of battery 142 to prevent a low temperature shutdown.

The 180K touch sensor is also referred to as the "touch pad". The touch sensor 180K may be located on the display 194 and the touch sensor 180K and the display 194 form a touch screen, which is also referred to as a "touch screen control". The touch sensor 180k is configured to detect a touch operation on or near the touch sensor 180K. The touch sensor may communicate the detected touch operation to the application processor to determine the type of touch event. Visual output associated with a touch operation may be provided by display 194. In some other embodiments, touch sensor 180K may alternatively be located on the surface of terminal 100 at a location other than display 194.

The software system of terminal device 100 may have a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. This embodiment of the present application, as an example, describes the software architecture of the terminal device 100 using the Android system with a layered architecture.

In FIG. 3B is a software architecture block diagram of a terminal device 100 according to an embodiment of the present application.

The layered architecture divides the software into multiple layers and each layer has a specific function and division of tasks. The levels communicate with each other using a programming interface. In some embodiments, the Android system is divided into four layers, i.e., application layer, application framework layer, Android runtime layer, and system library and kernel layer from top to bottom.

The application layer can contain a number of application packages.

As shown in FIG. 3B, application packages may contain applications such as camera, gallery, calendar, calls, display, navigation, WLAN, Bluetooth, music, video, and short message service.

The application framework layer provides an application programming interface (API) and a programming platform for applications at the application layer. The application structure layer contains some specified functionality.

As shown in FIG. 3B, the application structure layer may contain a window manager, a content provider, a video system, a telephone manager, a resource manager, a notification manager, and the like.

The window manager is configured to control a window program. The window manager can get the size of the display, determine if the display has a status bar, lock the screen, take a screenshot, and so on.

The content provider is configured to store and provide data to make it available to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, address book, and so on.

The viewer contains visual controls such as text display control or image display control. The viewing system may be configured to build applications. The display interface may be formed by one or more images. For example, a display interface containing a short message service notification icon may include a text display view and an image display view.

The telephone manager is configured to provide a communication function of terminal device 100 such as call state control (including connection, idle, etc.).

The resource manager provides various resources for applications, such as localized strings, icons, images, location files, and video files.

The notification manager allows applications to display notification information in the status bar, can be used to send notification type messages, and can automatically disappear after a short pause without user intervention. For example, the notification manager is used for download completion notification, alarm message, and the like. The notification manager may further be a notification that appears in the status bar at the top of the system in the form of a bar or a scrolling text bar, such as a notification that an application is running in the background or a notification that appears on the screen in the form of a dialog box. For example, help text information is presented in the status bar, an alert tone sounds, the terminal vibrates, and the indicator flashes.

Android runtime contains a kernel library and a virtual machine. The Android uptime feature is responsible for scheduling and managing the Android system.

The core library contains two parts: one part is a function that should call the Java language when necessary, and the other part is the Android core library.

The application layer and the application fabric layer run on a virtual machine. The virtual machine executes Java files at the application layer and application fabric layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, flow management, security and exception management, and garbage collection.

The system library may contain a plurality of functional modules, such as a surface manager (surface manager), a multimedia library (Media Libraries), a three-dimensional graphics processing library (for example, OpenGLES), a two-dimensional (2D) graphics engine (for example, SGL).

The surface manager is configured to control the display subsystem and provides a combination of 2D and 3D layers for a variety of applications.

The media library supports the playback and recording of audio and video in various commonly used formats, still image files, and so on. The media library can support many audio and video encoding formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

The 3D Graphics Processing Library is used to implement 3D graphics drawings, image presentation, synthesis, level processing, and the like.

The 2D (2D) graphics engine is a drafting engine for 2D drawings.

The kernel layer is the layer between hardware and software. The kernel level contains at least a display driver, a camera driver, an audio driver, and a sensor driver.

In FIG. 3C is a schematic structure of a network device 200 according to an embodiment of the present application. Network device 200 may include one or more processors 201, memory 202, communication interface 203, mobile communication module 205, and antenna 206. These components may be connected by bus 204 or in some other manner. In FIG. 3c bus connection is used as an example.

Processor 201 may include one or more processor units, for example: processor 110 may include an application processor (AP), modem processor, controller, memory, baseband processor, and the like. The various processor units may be independent devices or may be integrated into one or more processors.

Communication interface 203 may be configured to allow network device 200 to communicate with other communication devices, such as terminal device 100 or other network devices. namely, the communication interface 203 may be a 5G interface or a future new wireless communication interface. In addition to the wireless communication interface, the network device 200 may also be provided with a wired communication interface 203 to support wired communication, for example, the transport channel between one network device 200 and another network device may be a wired communication connection.

The mobile communication module 205 can provide a solution including wireless communication such as 2G/3G/4G/5G and applicable to a network device. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 205 may receive electromagnetic waves using the antenna 206, perform filtering, amplification, and other processing of the received electromagnetic waves, and transmit the waves to a modem processor for demodulation. The mobile communication module 205 can further amplify the signal modulated by the modem processor and convert the signal into electromagnetic waves using the radiation antenna 206 . In some embodiments, at least some of the functional modules of the mobile communication module 205 may be located in the processor 201. In some embodiments, at least some of the functional modules of the mobile communication module 205 may be located in at least the same device as some processor modules 201.

Antenna 206 may be configured to convert electromagnetic energy present in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves present in free space into electromagnetic energy in the transmission line. Antenna 206 may be configured to cover a single or multiple communication lanes. For example, antenna 206 may span a 5GNR band, an LTE band, a Wi-Fi band, a GPS band, and the like. Multiple antennas 206 may be provided. It should be understood that network device antennas 206 may be implemented as a large scale antenna array.

In this embodiment of the present application, antenna 206 may be configured to receive a message sent by terminal device 100 to request network device 200 to adjust (reduce or restore) the number of layers in the downlink process. The processor 201 may then determine the number of layers to be used in the downlink process based on the frequency bands, antenna configurations, and the like supported by the tag 100 and the network device 200, and send a message to the tag 100 using the antenna 206 to specify a certain number of levels.

In this embodiment of the present application, in the downlink process, the network device 200 serves as the transmitting end of the data transmission and performs baseband processing and RF processing of the original data. Reference may be made to FIG. 1A and related descriptions.

Memory 202 is coupled to processor 201 and is configured to store various programs and/or multiple instruction sets. Specifically, the memory 202 may include high speed random access memory and may also include non-volatile memory such as one or more disk storage devices, a flash memory device, or other non-volatile solid state storage device.

Memory 202 may store an operating system (hereinafter referred to as "system"), such as an embedded operating system such as uCOS, VxWorks, or RTLinux. The memory 202 may further store a network communications program that may be used to communicate with one or more accessory devices, one or more terminal devices, or one or more network devices.

In this embodiment of the present application, the processor 201 may be configured to read and execute computer-readable instructions. Specifically, the processor 201 may be configured to call a program stored in the memory 202, such as a program for implementing the method of one or more embodiments of the present application on the side of the network device 200, and execute the instructions contained in the program.

It should be noted that the network device 200 shown in FIG. 3C is only one implementation of this embodiment of the present application, and in actual use, the network device 200 may further comprise more or fewer components. It is not limited here.

Based on the MIMO system 10 shown in FIG. 2 terminal device 100 shown in FIG. 3A and FIG. 3B and the network device 200 shown in FIG. 3C, the method for adjusting the number of data streams according to this embodiment of the present application will be described below.

The method according to this embodiment of the present application comprises two scenarios: a low rate scenario and a high rate scenario. Before describing in detail the method according to this embodiment of the present application, these two scenarios will first be described.

(I) Low speed scenario

In this embodiment of the present application, the low rate scenario may be any combination of one or more of the following events: event A: on terminal device 100, the first application is running in the foreground; event B: the data rate of the terminal device 100 is less than the first threshold; event C: the strength of the signal transmitted by the network device 200 and received by the terminal device 100 is greater than the second threshold, event D: the screen of the terminal device 100 is turned off; event E: terminal 100 enters power saving mode; event F: terminal device 100 is not charging; or event G: the temperature of the terminal device 100 is above the third threshold.

Below, events A-G are explained one after the other in sequence:

1. Event A: On terminal 100, the first application is running in the foreground.

The application providing the interface of the terminal device 100 shown on the display is the application running in the foreground. That is, the application in which the user can currently work on the display is the application running in the foreground.

One or more first applications may be provided. The first application may include: an application for which the average data rate of the terminal device 100 during application execution is less than a predetermined value. The average data rate may be the downstream average data rate when the first application is running on terminal device 100. The set value can be set in advance, and in this embodiment of the present application, no restriction is imposed on this set value.

That is, the first application is an application that does not require a high data rate, but only requires a small number of data streams to meet the data transmission requirements of the first application. The first application may be defined by the terminal device or may be updated in real time by the terminal device based on information obtained from the network. For example, the first application may be a reader type application, an instant messaging type application, a text writing type application, and the like.

In some embodiments, a whitelist may be stored in tag 100 and the whitelist may contain all first applications installed on tag 100. In some other embodiments, a blacklist may be stored in tag 100 and the blacklist may contain all first applications installed on terminal device 100. In this manner, terminal device 100 may determine the application currently running in the foreground as the first application when it recognizes that the application running in the foreground is whitelisted or not blacklisted.

It should be understood that there are many possible situations in which event A occurs at terminal device 100 and no limitation is placed on this in this embodiment of the present application. For example, when the terminal device 100 receives a touch operation of the user tapping the icon of the first application on the home screen, the terminal device 100 starts the first application in the foreground, that is, event A occurs on the terminal device 100. FIG. 4A shows a scenario in which event A occurs at terminal 100. As shown in FIG. 4A, the terminal device 100 may launch and operate the memorandum application in the foreground in response to a user tap operation of the memorandum application icon.

It should be understood that when an event A occurs on terminal device 100, i.e. when the first application is running in the foreground on terminal device 100, the data rate requirements are not high and only a small amount of data streams.

2. Event B: The data rate of the terminal device 100 is less than the first threshold.

Here, when the data rate of the tag 100 is less than the first threshold, any of the following can mean: the data rate of the tag 100 at a single point in time is less than the first threshold, the average data rate of the tag 100 over a period of time is less than the first threshold, the data rate of the tag device 100 at any time is less than the first threshold and the data rate of the terminal device 100 for k time samples in a row is less than the first threshold. The time period and k can be set, and in this embodiment of the present application, no limitation is imposed on this.

In some embodiments, tag 100 data rates may be all tag 100 data rates, such as all tag 100 downstream data rates. no threshold is imposed. For example, the first threshold might be 5 million bits per second (Mbps, Mbps).

In some other embodiments, the data rate of tag 100 may be the data rate of tag 100 while the foreground application is running, such as the downstream data rate of tag 100 while the foreground application is running. In this case, different applications running in the foreground may meet different first thresholds. Here, the first threshold corresponding to each foreground application may be set, and in this embodiment of the present application, no restriction is imposed on the first threshold.

For example, Table 1 shows examples of first thresholds corresponding to several applications.

Table 1

Foreground application First threshold Read class application 3 Mbps Instant messaging type application 5 Mbps Text entry type application 2 Mbps

It should be understood that there are many possible situations in which event B occurs at terminal 100 and no limitation is placed on this in this embodiment of the present application. For example, when a video type application is running on terminal device 100, the data rate of terminal device 100 may be less than the first threshold after the video currently being viewed by the user is buffered, that is, event B occurs on terminal device 100 As another example, when an audio-type application is running on terminal device 100, if the user issues a pause command while playing audio, the data rate of terminal device 100 may be less than the first threshold, that is, event B occurs on terminal device 100.

It should be understood that when a B event occurs at terminal device 100, that is, the data rate of terminal device 100 is less than the first threshold, this indicates that the data rate requirements in the current scenario are low and to meet the data transfer requirements of terminal device 100, only a small number of data streams.

3. Event C: The strength of the signal transmitted by the network device 200 and received by the terminal device 100 is greater than the second threshold.

The signal strength received by the terminal device 100 can be measured based on the received reference signal receiving power (RSRP), the reference signal receiving quality (RSRQ), and the received signal strength indication (RSSI) . The second threshold can be set, and in this embodiment of the present application, no restriction is imposed on the second threshold.

It should be understood that there are many possible situations in which event C occurs at terminal device 100 and no limitation is placed on this in this embodiment of the present application. For example, when terminal device 100 moves closer to network device 200, the signal strength transmitted by network device 200 and received by terminal device 100 may be greater than the second threshold, i.e., event C occurs at terminal device 100.

It should be understood that when an event C occurs at the terminal device 100, i.e., the power of the signal transmitted by the network device 200 and received by the terminal device 100 is relatively high, the terminal device 100 can effectively receive the signal transmitted by the network device and therefore, in order to meet the requirements for terminal device 100 for data communication, only a small number of data streams are required.

4. Event d: Terminal 100 screen is off.

Screen off means that some or all of the display pixels of terminal 100 are off.

It should be understood that there are many possible situations in which event D occurs at terminal 100, and no limitation is placed on this in this embodiment of the present application. In FIG. 4B shows a scenario in which the screen of the terminal device 100 is turned off. For example, as shown in FIG. 4B, when the terminal device 100 does not receive a user operation (including a touch operation acting on a display, a pressing operation acting on a physical key, or entering a voice command) within a predetermined time period (e.g., one minute or 30 seconds), the end device 100 may turn off some of the display pixels, that is, cut off power to those pixels and only display the time on a small portion of the display.

In some other embodiments, tag 100 may further turn off all display pixels upon receiving a user operation (eg, a power key operation), that is, cut off power to all pixels.

Obviously, when an event D occurs on the terminal device 100, i.e. after the screen of the terminal device 100 is turned off, most of the applications running on the terminal device 100 go into the background to work or stop working. In this case, the requirements for the terminal device 100 for data transmission are low, and only a small number of data streams are required to meet the requirements.

5. Event E: Terminal 100 enters power saving mode.

The power saving mode is the operating mode of the terminal device. The power saving mode refers to a mode in which the terminal device 100 performs a series of power saving measures in order to save power and extend standby time. After entering the power saving mode, the terminal device performs a series of power saving measures, such as reducing the performance of the central processing unit (CPU), turning off some unnecessary functions, such as reducing the number of processor cores, lowering the screen brightness, turning off unnecessary applications running in background mode (such as GPS positioning), reducing the transmitted signal strength, reducing the volume of audio playback, turning off the Bluetooth function, and turning off the mobile data function, in order to achieve the goal of saving power and extending the standby time.

Power saving measures corresponding to the power saving mode of terminal devices of different manufacturers or different models may differ, and in this embodiment of the present application, no restrictions are imposed on this. The same terminal may also correspond to a plurality of power saving modes having different powers, for example, a normal power saving mode and a super power saving mode containing more power saving measures can be used.

It should be understood that the power saving mode is only a term used in this embodiment, and its meanings have been described in this embodiment, and its name cannot constitute a limitation of this embodiment. In addition, in some other embodiments of the present application, the power saving mode may also be referred to as other terms such as "balanced mode".

In FIG. 4C(1)-4C(2) show a scenario in which terminal 100 enters a power save mode.

The user interface shown in Fig. 4c may be provided with a settings application installed on terminal device 100. As shown in the figure, the user interface includes a control switch for two power saving modes: a control switch 401 for power saving mode and a control switch 402 for super power saving mode. The control switch 401 or the control switch 402 may control the user's operation, and the terminal device 100 may enter an appropriate power saving mode in response to the user's operation. For example, as shown in FIG. 4C(1)-4C(2), the user may press the power save mode control switch 401 to cause the terminal device 100 to enter the power save mode.

It should be understood that after the terminal device 100 occurs an event E, that is, the terminal device 100 enters the power saving mode, because the terminal device 100 performs various power saving measures, the data transmission requirements of the terminal device 100 may be low and only a small number of data streams to meet the requirements. In addition, after the terminal device 100 enters the power saving mode, only a small number of data streams are used for data transmission, and power consumption can be further saved, which is equivalent to implementing new power saving measures.

6. Event F: Terminal 100 is not charging.

Specifically, the terminal device 100 can determine that the terminal device is currently in a charge state based on the connection state between the charging port (such as a USB interface) and a peripheral device (such as a charger). Whether the terminal device 100 is in a state of charge is determined by the user.

It should be understood that when an event F occurs at the terminal device 100, that is, the terminal device 100 is not being charged, the power supply of the terminal device 100 cannot be replenished in time. In this case, a small number of data streams can be used to meet the data communication requirements of the terminal device 100, thus reducing the power consumed by the terminal device 100.

7. Event G: The temperature of terminal 100 is greater than the third threshold.

Specifically, the temperature of terminal device 100 may be determined based on data collected by the temperature sensor. The third threshold may be set, for example, may be equal to 41°C.

It should be understood that there are many possible situations in which an event G occurs at terminal 100, and no limitation is placed on this in this embodiment of the present application. For example, when tag 100 continuously operates at a high speed for a long time, or when tag 100 is in a high temperature environment, the temperature of tag 100 may be above the third threshold, that is, an event G may occur at tag 100.

It should be understood that when an event G occurs at terminal device 100, that is, the temperature of terminal device 100 is above the third threshold, because the temperature rises, terminal device 100 additionally consumes more power. In this case, a small number of data streams can be used to meet the requirements of the terminal device 100 for data transmission, thereby reducing the power consumed by the terminal device 100.

(II) High Speed Scenario

In this embodiment of the present application, the high speed scenario may be any combination of a large number of the following events: event a: the application being run by the foreground terminal 100 is not the first application; event b: data rate of terminal device 100 is greater than the fourth threshold; event c: the power of the signal transmitted by the network device 200 and received by the terminal device 100 is less than the fifth threshold; event d: terminal screen 100 is on; event e: end device enters performance mode; event f: terminal device 100 is charging; and event G: the temperature of the terminal 100 is below the sixth threshold.

Events a-g are explained one by one below:

Event a: The application being run by the terminal device 100 in the foreground is not the first application.

Event a and event A are mutual events and will not be explained in detail here.

It should be understood that there are many possible situations in which event a occurs at terminal device 100 and no limitation is placed on this in this embodiment of the present application. For example, terminal 100 may detect a user operation to exit the first application. As shown in FIG. 4A, when the terminal device 100 is running on the memorandum application, a swipe operation that is entered by the user from the bottom of the display upwards can be detected, in response to the swipe operation, the main screen is re-displayed and the memorandum application runs in the background.

It should be understood that when event a occurs on terminal device 100, that is, when an application is running in the foreground and is not the first application on terminal device 100, the data rate requirements are higher and more data streams are required to meet the requirements. to terminal device 100 for data transmission.

2. Event b: The data rate of the terminal device 100 is greater than the fourth threshold.

Event b is similar to event B and will not be explained in detail here. Here, the fourth threshold is greater than or equal to the first threshold in the event B. The fourth threshold can be set, and in this embodiment of the present application, there is no restriction on it.

It should be understood that there are many possible situations in which event b occurs at terminal 100 and no limitation is placed on this in this embodiment of the present application. For example, when a video type application is running on terminal device 100 and a user opens a video channel to watch online video, the data rate of terminal device 100 may be greater than the fourth threshold, that is, event b occurs at terminal device 100. As another example, when the terminal device 100 is running an audio type application, if the user instructs to play audio online, the data rate of the terminal device 100 may be greater than the fourth threshold, that is, an event b occurs at the terminal device.

It should be understood that when an event b occurs at terminal device 100, i.e., the data rate of terminal device 100 is greater than the fourth threshold, the data rate requirements are higher and more data streams are required to meet the requirements of terminal device 100 for data transmission.

3. Event c: The strength of the signal transmitted by the network device 200 and received by the terminal device 100 is less than the fifth threshold.

Event c is similar to event C and will not be explained in detail here. Here, the fifth threshold is less than or equal to the second threshold in event C. The fifth threshold can be set, and in this embodiment of the present application, no restriction is placed on it.

It should be understood that there are many possible situations in which event c occurs at terminal 100 and no limitation is placed on this in this embodiment of the present application. For example, when tag 100 moves away from network device 200, the signal strength transmitted by network device 200 and received by tag 100 may be less than a fifth threshold, that is, event c occurs at tag 100.

It should be understood that when event c occurs at terminal device 100, that is, the power of the signal transmitted by network device 200 and received by terminal device 100 is relatively low, terminal device 100 may not efficiently receive the signal transmitted by the network device, and therefore, in order to meet the requirements terminal device 100 requires more data streams to transmit data.

4. Event D: Terminal 100 screen is on.

That the screen is on means that some or all of the display pixels of terminal 100 are lit. Event d and event D are mutual events and are not explained in detail here.

It should be understood that there are many possible situations in which event d occurs at terminal device 100 and no limitation is placed on this in this embodiment of the present application. For example, terminal device 100 may light all display pixels when a user operation (eg, a power key operation or lift operation of terminal device 100) is received, i.e., power is applied to all pixels. As another example, terminal device 100 may additionally light up all display pixels when an authorized human face is detected.

It should be understood that when event d occurs at the terminal, i.e. when the screen of the terminal 100 is turned on, the power of the terminal 100 will increase and in this case the communication requirements of the terminal 100 will also increase and more data streams will be required to satisfy requirements.

5. Event e: Endpoint enters performance mode.

The performance mode is the operating mode of the target device. The performance mode refers to a mode in which the tag 100 performs a series of measures to provide an optimal user experience for the tag without regard to power consumption. After entering the performance mode, the end device will perform a series of actions such as maximizing the CPU, increasing the number of processor cores, increasing the screen brightness, running applications in the background, increasing the transmitted signal strength, increasing the volume of the audio being played, turning on the Bluetooth function, and allowing mobile data transmission. , thus realizing an optimal user experience for using the terminal device.

Measures corresponding to the performance mode of terminal devices of different manufacturers or different models may vary, and no limitation is imposed on this in this embodiment of the present application. The same terminal may also correspond to multiple performance modes having different benefits, such as a normal performance mode and a super performance mode, in which more measures can be included.

The performance mode is only a term used in this embodiment, and its meaning has been described in this embodiment, and its name cannot be a limitation of this embodiment. In addition, in some other embodiments of the present application, the performance mode may also be referred to as another term, such as "high speed mode".

As shown in FIG. 4C(1)-4C(2), the user interface shown in FIG. 4C(1)-4C(2) may further comprise a performance mode control switch 403. The control switch 403 may control the user's operation, and the terminal device 100 may enter a performance mode in response to the user's operation.

It should be understood that after the event e occurs at the terminal device 100, that is, the terminal device 100 enters the performance mode, because the terminal device 100 performs various measures to guarantee the user experience, the requirements for the terminal device 100 for data transmission become higher. and more data streams are required to meet the requirements. In addition, after the terminal device enters the power saving mode, more data streams are used for data transmission, and the user experience of using the terminal device can be further provided, which is equivalent to implementing new measures.

6. event f: terminal device 100 is charging.

Event f and event F are mutual events and will not be explained in detail here. It should be understood that when an event f occurs at the terminal device 100, that is, the terminal device 100 is in a state of charge, the power of the terminal device 100 can be replenished in time. In this case, more data streams can be used to meet the requirements of the terminal device 100 for data transmission.

7. Event g: The temperature of terminal 100 is below the sixth threshold.

Event g is similar to event G and will not be explained in detail here. Here, the sixth threshold is less than or equal to the third threshold in event G. The sixth threshold can be set, and in this embodiment of the present application, no limitation is imposed on it.

It should be understood that there are many possible situations in which event g occurs at terminal 100, and no limitation is placed on this in this embodiment of the present application. For example, when tag 100 is operating at low speed or when tag 100 is in a low temperature environment, the temperature of tag 100 may be less than the third threshold, that is, event g may occur at tag 100.

It should be understood that when an event g occurs at terminal device 100, that is, the temperature of terminal device 100 is below the sixth threshold, the temperature does not cause any additional power consumption and more data streams can be used to meet the requirements of terminal device 100 for data transmission.

Below, a method for controlling the number of data streams in a MIMO system according to an embodiment of the present application is described using four embodiments.

The following four embodiments will be used to describe in detail the technical solutions corresponding to the embodiments of the present application, mainly using the regulation of the amount of data flows in the downlink process in a 5G system in the SA networking mode as an example.

That is, in the following four embodiments, the MIMO system 10 composed of the terminal device 100 and the network device 200 is a 5G system in SA networking mode, that is, both the terminal device 100 and the network device 200 support the 5G band and operate in 5G band, and the network device 200 connects to the 5G core network (5GC). In addition, the network device 200 is a gNodeB, and the terminal device 100 communicates with the network device 200 using an NR link.

(I) Embodiment 1

In Embodiment 1, the MIMO system can reduce the number of data streams in the downstream process when the terminal device 100 is in a low rate scenario, and recover the number of data streams in the downstream process when the terminal device 100 is in a high rate scenario, thus dynamically by adjusting the number of data streams in the downstream process. In Embodiment 1, the power consumed by the terminal can be reduced and the terminal's standby time can be extended without affecting the user's perception of the operation of the terminal while the terminal's data rate requirements are met.

In FIG. 5 is a schematic example flowchart of a method for controlling the amount of downstream data in a MIMO system, which is performed in a 5G system in SA networking mode.

S101: The terminal device 100 transmits the capability information of the UE for the capability report to the network device 200, where the capability message carries the maximum number of downlinks supported by the terminal device 100.

Terminal device 100 may send a capability message during the process of attaching to the network, or may send a capability message after receiving a UE capability enquiry message sent by network device 200.

The maximum number of downstream layers supported by terminal device 100 may be carried in the following information element (IE) in the capability message: Downstream MIMO Capability (MIMO-CapabilityDL-rlO).

The maximum number of downlinks supported by terminal device 100 is determined based on the reception capabilities of terminal device 100. The capabilities of terminal device 100 may include the number of antennas configured by terminal device 100 to support the 5G band, the number of RF receive paths configured by terminal device 100, and the like. . It should be understood that the maximum number of downlink layers supported by terminal device 100 is less than or equal to the number of antennas configured by terminal device 100 to support the 5G band, and also less than or equal to the number of RF receive paths configured by terminal device 100. For example, the maximum number of downlink layers supported by end device 100 may be 4.

S102: The network device 200 sends to the terminal device 100 an RRC reconfiguration message (RRC reconfiguration), where the RRC reconfiguration message carries a first number of layers, wherein the first number of layers is less than or equal to the maximum number of downlink layers supported by the terminal device 100, and the RRC reconfiguration message is used to configure the number of layers in the downlink process.

Then, based on the first number of layers, a downlink process between terminal device 100 and network device 200 can be performed. For example, the first number of layers can be 4.

S103: Terminal 100 recognizes the low rate scenario.

Specifically, the low rate scenario may be any combination of event A and event B. The low rate scenario may be set by terminal 100 (eg, the low rate scenario may be set by terminal 100 upon delivery) or may be set independently by the user.

For example, a low rate scenario could be one in which event A occurs on terminal device 100, i.e., the application that is running in the foreground on terminal device A is the first application. In a specific example, when the terminal device 100 receives a user's touch operation of pressing the first application icon on the home screen, the terminal device 100 recognizes the low rate scenario.

In another example, a low rate scenario may be a scenario where event A and event B occur simultaneously on tag 100, i.e., tag 100 is running the first application in the foreground and tag 100's data rate is less than a first threshold. In a specific example, when the terminal device 100 receives a user's touch operation of pressing the first application icon on the home screen, and the user instructs the audio to pause, the terminal device 100 recognizes the low-rate scenario.

As another example, a low rate scenario may be a scenario in which event A, event B, event C, event E, and event F occur on terminal device 100 at the same time, i.e., on terminal device 100, the first application is running in the foreground, the terminal device 100 enters the power saving mode, the signal strength transmitted by the network device 200 and received by the terminal device 100 is greater than the second threshold, the terminal device 100 is not charging, and the data rate of the terminal device 100 is less than the first threshold. In a specific example, when the terminal device 100 receives the user's touch operation of pressing the first application icon on the home screen, the user instructs the audio to pause, the terminal device 100 moves closer to the network device 200, the user presses the control switch 401 for power saving mode, and the user removes the charger from the charging port, the terminal device 100 recognizes the low speed scenario.

Refer to the detailed descriptions of the low rate scenario in part (I) for the way in which the terminal device 100 recognizes the low rate scenario. The details are not re-described here.

S104-S106: The terminal device 100 and the network device 200 agree to reduce the number of layers in the downlink process.

S104: The terminal device 100 transmits the first message to the network device 200, where the first message is used to request the network device 200 to reduce the number of layers in the downlink process, the first message carries the second number of layers, and the second number of layers is the number of layers that the terminal the device 100 must use in the downstream process; wherein the second number of levels is less than the first number of levels.

In some embodiments, the first message may be implemented as an auxiliary message (UE help information message). The auxiliary message is signaled by terminal 100 via radio resource control (RRC) signaling. An auxiliary message may be used to reduce the number of layers used in data transmission. The description of the UE help information auxiliary message according to the protocol is as follows:

1. if the UE prefers a configuration primarily optimized for power saving:

2> set powerPrefindication to lowPowerConsumption (set powerPrefindication to lowPowerConsumption);

2. else

2 > start or restart T340 with the timervalUE set to the PowerprefindicationTimer

2 > set PowerprefindicationTimer to normal; (set PowerprefindicationTimer as normal);

The UE must send a UE Assistanceinformation message to the lower layers for transmission.

The second number of levels is less than the first number of levels. For example, the second number of layers may be 2. In some embodiments, the second number of layers may be carried in the reducedMIMO-LayerFRI-DL field of the auxiliary message.

S105: The network device 200 receives the first message and transmits to the terminal device 100 a second message, where the second message carries a third number of layers, and the third number of layers is less than or equal to the second number of layers, and the second message is used to configure the number of layers in the downlink process .

That is, the network device 200, in response to the first message, can reduce the number of layers used in the downlink process from the first number of layers to the third number of layers, thereby reducing the number of data streams used in the downlink process.

In some embodiments, the second message may be implemented as an RRC reconfiguration message. In some embodiments, network device 200 may carry a third number of layers in a maximum layer field (MaxMimoLayerNuni) in a service cell configuration (PDSCH service cell configuration) message sent on a physical downlink shared channel (PDSCH).

S106: After receiving the second message, the terminal device 100 sends back to the network device 200 an acknowledgment message.

The acknowledgment message is used to indicate that the tag 100 has received the second message transmitted by the network device 200. The acknowledgment message may be implemented as an RRC reconfiguration complete message.

It should be understood that S106 is an optional step. In some other embodiments, the MIMO system may directly use the third number of layers for downlink data transmission after performing steps S103-S105 without an acknowledgment response message from terminal 100. This may reduce signaling traffic and further reduce power consumption.

It should be understood that the signaling in the existing standard protocol can be reused for messages (such as an auxiliary message, an RRC reconfiguration message, and an acknowledgment message) transmitted between the terminal device 100 and the network device 200 in steps S104-S106, so that the existing protocol communication could be used to transfer between the terminal device 100 and the network device 200 messages involved in the implementation of the present application, which is simple and convenient. Without being limited to this, in some other embodiments, a proprietary protocol for passing the aforementioned messages may alternatively be used between terminal device 100 and network device 200, and no limitation is placed thereon.

S107-S109: terminal device 100 and network device 200 transmit downlink data based on the agreed number of layers after reduction.

S107: The network device 200, based on the third number of layers, processes the data to be transmitted to the terminal device 100 to obtain a signal to be transmitted.

Specifically, the data to be transmitted to terminal device 100 may be text, image, video, URL, and the like. In this embodiment of the present application, no limitation is imposed on this.

For processing data to be transmitted by the network device 200, refer to FIG. 1A and the preceding related descriptions. The processing may include baseband processing, RF processing, transmission via an antenna, and the like. The number of layers participating in the layer mapping in the baseband processing is equal to the third number of layers, and the number of RF transmission paths used by the network device 200 in the RF processing is also equal to the third number of layers.

S108: The network device 200 transmits to the terminal device 100 a signal to be transmitted.

Specifically, the network device 200 transmits a processed signal to be transmitted using a plurality of antennas.

S109: The terminal device 100 receives the signal transmitted by the network device 200 and analyzes the signal based on the third number of layers.

Specifically, terminal device 100 uses a plurality of antennas to receive a signal transmitted by network device 200. In some embodiments, the number of antennas used by terminal device 100 when receiving a signal is three times the number of levels. For example, when the third number of layers is 2, the terminal device 100 uses two antennas to receive the signal transmitted by the network device 200.

After receiving the signal transmitted by the network device 200, the signal analysis process by the terminal device 100 may specifically comprise RF processing and baseband processing. The number of receiving RF paths involved in the RF processing is equal to the third number of levels, and the number of levels involved in the mapping of layers in baseband processing is equal to the third number of levels. For a detailed process for implementing signal analysis by terminal 100, refer to FIG. 1B and the preceding related descriptions.

By performing steps S101-S109, when operating in a low rate scenario, the terminal may request the network device 200 to reduce the number of layers used in the downlink process, thereby reducing the number of data streams. This can reduce the power consumption of the terminal and extend the standby time of the terminal while meeting the data rate requirements of the terminal without affecting the user experience of the terminal.

In some embodiments, after the MIMO system reduces the number of data streams by performing steps S101-S109, the original number of data streams may be further restored when terminal 100 is in a high speed scenario. Thus, the method according to the embodiment shown in FIG. 5 may further comprise the following steps.

S110: The terminal device 100 recognizes the high rate scenario corresponding to the low rate scenario in step S103.

The high-speed script may be pre-set by terminal 100 (eg, may be pre-set by terminal 100 when shipped) or may be set individually by the user. The low speed scenario in step S103 corresponds to the high speed scenario in step S110, and their correspondence will be explained below with an example.

When the low rate scenario is the scenario in which an event occurs on the terminal device 100, the corresponding high rate scenario is the scenario in which the event occurs on the terminal device 100. In a specific example, when the "memorandum" application is running on the terminal device 100, if an operation is detected that is entered by the user from the bottom of the display up, the high-speed script is recognized. When the low rate scenario is the scenario in which event B occurs at terminal device 100, the corresponding high rate scenario is the scenario in which event b occurs at terminal device 100. In a specific example, when a video type application is running on terminal device 100, if a user opens a video channel to watch online video, a high-speed scenario is recognized. When the low rate scenario is the scenario in which event C occurs at the terminal device 100, the corresponding high rate scenario is the scenario in which event c occurs at the terminal device 100, and so on.

When the low rate scenario is one in which event A and event B occur at the terminal device 100 simultaneously, the corresponding high rate scenario is one in which any one or more events a and b occur at the terminal device 100. When the low rate scenario is one in which event b and event c occur at tag 100 at the same time, the corresponding high rate scenario includes a scenario in which any one or more of events b and c occur at tag 100, and so on.

When the low rate scenario is a scenario in which event A, event B, event C, event E, and event F occur at the terminal device 100 at the same time, the corresponding high rate scenario is a scenario in which any one or more of event a, event b, event c, events e and events f occur at terminal 100, and so on.

Refer to the detailed descriptions of the high-speed scenario in part (II) for the way in which the terminal device 100 recognizes the high-speed scenario. The details are not repeated here.

S111-S113: the terminal device 100 and the network device 200 agree on restoring the number of layers in the downlink process. Steps S111-S113 are similar to steps S104-S106 except that S104-S106 are used to reduce the number of levels, while steps S111-S113 are used to restore the number of levels.

S111: terminal device 100 transmits a third message to the network device 200, where the third message is used to request the network device 200 to recover the number of layers in the downlink process.

In some embodiments, the third message may be implemented as a UE assistance information message. Specifically, the auxiliary message transmitted by the terminal device 100 in step S111 cannot carry the reducedMIMO-LayerFRLD field or the reducedMIMO-LayerFRI-DL field is empty so as to request the network device 200 to restore the number of layers in the downlink process. Here, recovery refers to the recovery of the number of layers in the downlink process from the third number of layers after reduction to the first number of layers before the reduction.

S112: The network device 200 receives the third message and transmits the fourth message to the terminal device 100, where the fourth message carries the first number of layers and is used to configure the number of layers in the downlink process.

That is, the network device 200, in response to the third message, can restore the number of layers used in the downlink process from the third number of layers to the first number of layers before the decrease, thereby increasing the number of data streams used in the downlink process. .

In some embodiments, the fourth message may be implemented as an RRC reconfiguration message.

S113: after receiving the fourth message, the terminal device 100 sends back to the network device 200 an acknowledgment message.

The acknowledgment message is used to indicate that the tag 100 has received the fourth message transmitted by the network device 200. The acknowledgment message may be implemented as an RRC reconfiguration complete message.

It should be understood that step S113 is an optional step. In some other embodiments, the MIMO system may directly use the first number of layers for downlink data transmission after performing step s113 without receiving an acknowledgment message at terminal 100. This may reduce signaling and further reduce power consumption.

It should be understood that the signaling in the existing standard protocol can be reused for messages (such as the first message, the second reconfiguration message, and the acknowledgment message) transmitted between the terminal device 100 and the network device 200 in steps S111-S113, so that the existing protocol communication could be used to transfer between the terminal device 100 and the network device 200 messages involved in the implementation of the present application, which is simple and convenient. Without limiting this, in some other embodiments, a proprietary protocol may alternatively be used between terminal device 100 and network device 200 to convey the above messages, and no restriction is placed thereon.

S114: The network device 200, based on the first number of layers, processes data to be transmitted to the terminal device 100 to obtain a signal to be transmitted.

S115: The network device 200 transmits to the terminal device 100 a signal to be transmitted.

S116: terminal device 100 receives the signal transmitted by the network device 200 and analyzes the signal based on the first number of layers.

For a specific implementation of S114-S116, refer to the accompanying descriptions of steps S107-S109. The details are not repeated here.

In the embodiment shown in FIG. 5, the signal transmitted by the network device 200 to the terminal device 100 may also be referred to as a downstream signal.

By performing steps S110-S116, in the high speed scenario, the terminal may request the network device 200 to restore the number of layers used in the downlink process, thereby increasing the number of data streams. Thus, the number of data streams can be flexibly adjusted to meet the data rate requirements of the terminal device in a high-speed scenario and improve the user's experience of the operation of the terminal device.

The embodiment of the method shown in FIG. 5 shows the process of adjusting the number of data streams in two downlink data transmission processes performed by the MIMO system. In a specific implementation, the MIMO system may alternatively repeatedly adjust the number of data streams during the downlink. In this embodiment of the present application, no limitation is imposed on this. For example, after step S116, the MIMO system may further recognize the low rate scenario again and reduce the number of data streams in the downlink process for the second time, and then the MIMO system may further recognize the high rate scenario again and recover the number of data streams for the second time in the downlink process. .

Referring to FIG. 6A and FIG. 6B in order to better understand the solution according to Embodiment 1 shown in FIG. 5, in this embodiment of the present application, two examples are further provided.

For the case where the low rate scenario is the scenario in which event A occurs at terminal device 100, in the example shown in FIG. 6A shows the time periods or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process.

For the case where the low rate scenario is the scenario in which event A, event B, event C, event E, and event F simultaneously occur at terminal device 100, in the example shown in FIG. 6B shows the time periods or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process.

From FIG. 6A and 6B, it can be seen that the MIMO system of Embodiment 1, when the terminal device 100 is in a low rate scenario or a high rate scenario, immediately adjusts the number of layers in the downlink process.

(II) Embodiment 2

Embodiment 2 differs from Embodiment 1 in that the interval between two successive adjustments of the number of data streams in the process of downlink data transmission by the MIMO system is greater than or equal to the first time period. This can prevent the terminal device 100 from frequently switching between the low rate scenario and the high rate scenario so that the MIMO system does not frequently adjust the number of data streams during the downlink. Also, in Embodiment 2, the power consumption of the terminal can be reduced and the standby time of the terminal can be extended without affecting the user experience of the terminal while the data rate requirements of the terminal are met.

In FIG. 7 is a schematic flowchart of another flow rate control method that is performed in a 5G system in SA networking mode according to an embodiment of the present application.

Fig. 7 is different from FIG. 5 in that after the tag 100 and the network device 200 have agreed to reduce the number of layers in the downlink process, only after the first time period, the tag 100 and the network device 200 can begin to recognize the high-speed scenario and perform the operation after high-speed scenario is recognized.

Specifically, the start time of the first time period may be the time when the MIMO system performs any of steps S204, S205, and S206. In some embodiments, terminal device 100 may turn on the timer at step S204 (ie, by sending an auxiliary message) or at step S205 (that is, by receiving an RRC reconfiguration message) or at step S206 (that is, by sending an acknowledgment message ) and recognize the current scenario when the timer expires. The duration of the timer (timer) is the first period of time. The first interval may be specified, for example it may be one minute or two minutes. No restriction is placed on this in this embodiment of the present application.

In some other embodiments, the MIMO system may not control the interval between two successive adjustments of the number of data streams in the downstream process so that it is greater than or equal to the first time period, but may only control the interval between each case when the number of data streams decreases, and the next case when the number of data streams is restored to be greater than or equal to the first time period, or to control only the interval between each case when the number of data streams is restored and the next case when the number of data streams is reduced to be greater than or equal to the first period of time. This can reduce the use of the timer and reduce the power consumption of the tag and extend the standby time of the tag without affecting the user's perception of the tag's performance while meeting the tag's data rate requirements.

Referring to FIG. 8A and FIG. 8B in order to better understand the solution of Embodiment 2 shown in FIG. 7, in the following, two examples are presented for this embodiment of the present application.

For the case where the low rate scenario is the scenario in which event A occurs at terminal device 100, FIG. 8A shows an example of the time period or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process. Compared to that shown in FIG. 6A, although the timings at which each event occurs at terminal 100 are the same, the interval between two successive layer number switching operations in FIG. 8A is greater than or equal to the first time period in which frequent switching is avoided.

For the case where the low rate scenario is a scenario in which an event A, an event B, an event C, an event E, and an event F simultaneously occur at the terminal device 100, FIG. 8B shows an example of the time periods or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process. Compared to that shown in FIG. 6B, although the times at which each event occurs at terminal 100 are the same, the interval between two successive level switching operations in FIG. 8V is greater than or equal to the first gap in which frequent switching is avoided.

From FIG. 8A and FIG. 8B, it can be seen that the interval between two successive layer number adjustments in the downlink process of the MIMO system in Embodiment 2 is longer than the first interval.

(III) Embodiment 3

In order to provide a better user experience of the tag, in the second time period when the tag 100 has the first application running in the foreground, it is generally ensured that the tag 100 has a higher data rate in the second time period to improve the user experience of the tag. devices. This requires that the MIMO system does not reduce the number of data streams in the downlink process in the second time period when the first application is running in the foreground on the terminal device 100. Option 3 implementation is presented to achieve this goal.

In Embodiment 3, when the low rate scenario contains an event A, the terminal device 100 starts to recognize the low rate scenario after the event A continues in the second time period, and if the low rate scenario is recognized, negotiates with the network device 200 to reduce the number of layers in the downstream process. data. In Embodiment 3, it can be ensured that the number of data streams in the downstream process will not decrease in the second time period when, on terminal device 100, the first application is running in the foreground, to ensure that terminal device 100 has a higher transfer rate. data in the second time period, thus improving the user experience of the operation of the terminal.

As shown in FIG. 9, the method may include the following steps.

S301 and S302: Reference may be made to S101 and S102.

S303: On terminal 100, the first application starts running in the foreground.

Specifically, on the terminal device 100, the first application may start running in the foreground in response to a user's touch operation of pressing the first application icon on the home screen. Without limiting this, on terminal device 100, the first application may start running in the foreground in response to a voice command, a shake command, or the like. No restriction is placed on this in this embodiment of the present application.

S304: After the second period of time, the terminal device 100 recognizes the low rate scenario, where the low rate scenario contains event A.

Specifically, the start time of the second time period may be the time when the terminal device 100 starts the first application in the foreground, that is, the start time of step S303. In some embodiments, tag 100 may turn on the timer when the first application in the foreground is running and recognize the current scenario when the timer expires. The running time of the timer (timer) is the second period of time. The second interval may be specified, for example it may be 30 seconds or one minute. No restriction is placed on this in this embodiment of the present application.

For steps S305-S317, refer to steps S104-S116 in the embodiment shown in FIG. 5. The details are not repeated here.

The embodiment of the method shown in FIG. 9 shows the process of adjusting the number of data streams in two downlink data transmission processes performed by the MIMO system. In a particular implementation, the MIMO system may alternatively repeatedly adjust the number of data streams during the downlink. No restriction is placed on this in this embodiment of the present application.

Refer to FIG. 10A and 10B in order to better understand the solutions of Embodiment 3 shown in FIG. 9, in this embodiment of the present application, two examples are further presented.

For the case where the low rate scenario is the scenario in which event A occurs at terminal device 100, FIG. 10A shows an example of the time periods or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process. Compared to FIG. 6A, although the times at which each event occurs at terminal 100 are the same, in FIG. 10A, the MIMO system does not reduce the number of data streams in the downlink process in the second time period when the first application is running in the foreground on the terminal device 100.

For the case where the low rate scenario is a scenario in which an event A, an event B, an event C, an event E, and an event F simultaneously occur at the terminal device 100, FIG. 10B shows an example of the time periods or times at which each event occurs at terminal 100 and the times at which the MIMO system switches the number of layers in the downlink process. Compared to FIG. 6B, although the times at which each event occurs at terminal 100 are the same, in FIG. 10B, the MIMO system does not reduce the number of data streams in the downlink process in the second time period when the first application is running in the foreground on the terminal device 100.

As can be understood from FIG. 10A and FIG. 10B, the interval between two successive adjustments by the MIMO system of the number of layers in the downlink process in Embodiment 2 is longer than the first interval.

It should be understood that Embodiment 2 and Embodiment 3 of the embodiments of the present application may be implemented in combination.

(IV) Option 4 implementation

Embodiments 1-3 describe a method in which a MIMO system adjusts the number of data streams in a downlink process, but the embodiments are not limited to this. Embodiments of the present application are also applicable to the regulation by the MIMO system of the number of data streams in the process of uplink data transmission.

In the uplink process, the roles of terminal device and network device are interchangeable. The terminal device is the transmitting end of the signal transmission, and the network device is the receiving end of the signal reception. The terminal converts the input data stream into multiple parallel signal paths that are transmitted from multiple transmit antennas simultaneously, respectively; and a plurality of receiving antennas of the network device receive the signals and restore the original signals.

In Embodiment 4, the MIMO system can reduce the number of data streams in the uplink process when the terminal device 100 is in the low rate scenario state, and restore the number of data streams in the uplink process when the terminal device 100 is in the high rate scenario state, thereby dynamically adjusting the number of data streams in the uplink process. Here, the method in which the MIMO system adjusts (reduces or restores) the number of data streams in the uplink process is similar to the method in which the MIMO system adjusts (reduces or restores) the number of data streams in the downlink process.

In FIG. 11 is a schematic example flowchart of a method for controlling the amount of upstream data in a MIMO system, which is performed in a 5G system in SA networking mode.

S401: The terminal device 100 transmits a capability message (UE capability information) to the network device 200, where the capability message carries the maximum number of uplinks supported by the terminal device 100.

Refer to the corresponding descriptions in Embodiment 1 for reporting capabilities.

The maximum number of uplinks supported by terminal device 100 is determined based on the transmission capabilities of terminal device 100. The capabilities of terminal device 100 may include the number of antennas configured by terminal device 100 to support the 5G band, the number of RF transmission paths configured by terminal device 100, and the like. . It should be understood that the maximum number of uplink layers supported by terminal device 100 is less than or equal to the number of antennas configured by terminal device 100 to support the 5G band, and also less than or equal to the number of RF transmission paths configured by terminal device 100. For example, the maximum number of uplink layers supported by end device 100 may be equal to 2.

S402: The network device 200 transmits to the terminal device 100 an RRC reconfiguration message (RRC reconfiguration), where the RRC reconfiguration message carries a fourth number of layers, wherein the fourth number of layers is less than or equal to the maximum number of uplink layers supported by the terminal device 100, and the RRC reconfiguration message is used to configure the number of layers in the uplink process.

For example, the fourth layer count could be 2.

Step S403: Terminal 100 recognizes the low rate scenario.

Steps S404-S406: terminal device 100 and network device 200 negotiate layer reduction in the uplink process.

S404: the terminal device 100 transmits a first message to the network device 200, where the first message is used to request the network device 200 to reduce the number of layers in the uplink process, the first message carries the fifth number of layers, and the fifth number of layers is the number of layers that the terminal device 100 must use in the process of uplink data transmission; and the fifth number of levels is less than the fourth number of levels.

In some embodiments, the first message may be implemented as a UE assistance information message. For a specific implementation of the auxiliary message, refer to the respective descriptions in step S104.

In some embodiments, a fifth number of layers may be carried in the reducedMIMO-LayerFRI-UL field of the auxiliary message.

Step S405: The network device 200 receives the first message and transmits to the terminal device 100 a second message, where the second message carries a sixth number of layers, where the sixth number of layers is less than or equal to the fifth number of layers, and the second message is used to configure the number of layers in the uplink process data.

That is, the network device 200, in response to the first message, can reduce the number of layers used in the uplink process from the fourth number of layers to the sixth number of layers, thereby reducing the number of data streams used in the uplink process.

In some embodiments, the second message may be implemented as an RRC reconfiguration message. In some embodiments, network device 200 may carry a third number of layers in a maximum layer (MaxMimoLayerNuni) field in a PDSCH-serving cell configuration message sent on a physical uplink shared channel (PDSCH).

Step S406: after receiving the second message, the terminal device 100 sends back to the device 200 an acknowledgment message.

Steps S407-S409: the terminal device 100 and the data network device 200 transmit uplink data based on the negotiated sixth number of layers after reduction.

Step S410: The terminal device 100 recognizes the high rate scenario corresponding to the low rate scenario to step S103.

Steps S411-S413: terminal device 100 and network device 200 negotiate the recovery of the number of layers in the uplink process.

Step S411: terminal device 100 transmits the third message to the network device 200, where the third message is used to request that the network device 200 restore the number of layers in the uplink process.

In some embodiments, the third message may be implemented as a UE assistance information message. Specifically, the auxiliary message transmitted by the terminal device 100 in step S411 may not carry any reducedMIMO-LayerFRI-UL field or the reducedMIMO-LayerFRI-UL field is empty to request the network device 200 to restore the number of layers in the uplink process. Here, restoration refers to restoring the number of layers in the uplink process from the sixth number of layers existing after reduction to the fourth number of layers existing before reduction.

Step S412: The network device 200 receives the third message and transmits a fourth message to the terminal device 100, where the fourth message carries the fourth number of layers and is used to configure the number of layers in the uplink process.

In some embodiments, the fourth message may be implemented as an RRC reconfiguration message.

Step S413: after receiving the fourth message, the terminal device 100 sends back an acknowledgment message to the network device 200.

Step S414: The terminal device 100 processes data to be transmitted to the network device 200 based on the fourth number of layers to obtain a signal to be transmitted.

Step S415: the terminal device 100 transmits to the network device 200 a signal to be transmitted.

Step S416: The network device 200 receives the signal transmitted by the terminal device 100 and analyzes the signal based on the fourth number of layers.

In the embodiment shown in FIG. 11, the signal transmitted by terminal device 100 to network device 200 may also be referred to as an uplink signal.

It should be understood that Embodiment 1 and Embodiment 4 may be implemented in combination, and the same message may implement a function in Embodiment 1 and Embodiment 4. The capability message sent by terminal device 100 to network device 200 may carry the maximum number of downstream layers supported by terminal device 100 and the maximum number of upstream layers supported by terminal device 100, and the first message transmitted by terminal device 100 to network device 200 thereafter. how the terminal recognizes that the low rate scenario can carry a second number of layers and a fifth number of layers. The second message transmitted by the network device 200 to the terminal device in response to the first message may carry a third number of layers and a sixth number of layers, the third message transmitted by the terminal device 100 to the network device 200 after the terminal device recognizes that a high-speed script can be used to request recovering the number of uplinks and the number of downlinks, and the fourth message transmitted by the network device 200 to the terminal device in response to the third message may carry a first number of layers and a fourth number of layers.

It should be understood that the ideas contained in Embodiment 2 and Embodiment 3 can also be applied to the method for controlling the amount of upstream data in Embodiment 4.

That is, in some embodiments, the interval between two successive adjustments in the number of data streams in the process of uplink data transmission by the MIMO system is greater than or equal to the first time period. This can prevent the situation in which the terminal device 100 frequently switches between the low rate scenario and the high rate scenario so that the MIMO system does not frequently adjust the number of data streams in the uplink process. For details, refer to the respective descriptions in Embodiment 2.

In some embodiments, when the low rate scenario contains event A, tag 100 begins to recognize the low rate scenario after event A continues in the second time period, and if the low rate scenario is recognized, negotiates with the network device 200 to reduce the number of layers during the uplink. . For details, refer to the respective descriptions in the embodiments.

In addition to the 5G system in SA networking mode described in Embodiments 1 to 4, the technical solutions corresponding to the embodiments of the present application are also applicable to the 5G system in NSA networking mode. When the MIMO system shown in FIG. 2 is a 5G system in NSA networking mode, the system may further comprise a network device 300, where the network device 200 may be an eNodeB device and the network device 300 may be a gNodeB device. The tag device 100 communicates with the network device 200 using the LTE link, and the tag device 100 further communicates with the network device 300 using the NR link to realize dual connectivity. In addition, the network device 200 is connected to the network device 300, and the network device 200 and the network device 300 are both connected to a 4G core network (evolved packet core, EPC).

The 5G system in NSA networking mode is also applicable to the method for regulating the number of data streams according to the embodiment of the present application, that is, the number of data streams used in the data transmission process between the network device 300 and the terminal device 100 can also be adjusted. For an implementation in which the number of data flows between the network device 300 and the terminal device 100 is adjusted for the communication process between the network device 300 and the terminal device 100, refer to the respective descriptions in Embodiments 1-3. The difference is that all messages (such as the first message, the second message, the third message, and the fourth message) exchanged between the network device 300 and the terminal device 100 are transmitted using the network device 200. In another implementation, when the number of data streams between the network device 300 and the terminal device 100 is regulated, for the interaction process between the network device 300 and the terminal device 100, refer to the respective descriptions in Embodiments 1 to 3. The network device 300 and the terminal device 100 may exchange messages directly (such as the first message, second message, third message, and fourth message described above).

In addition to the 5G system in the SA networking mode described above, the technical solutions according to the embodiments of the present application are also applicable to the LTE system. In the LTE system, both the terminal device 100 and the network device 200 both support 4G band and operate in the 4G band, and the network device 200 connects to the EPC. In addition, the network device 200 is an eNodeB device, and the terminal device 100 communicates with the network device 200 using an LTE communication channel. When the data flow rate control method according to the embodiment of the present application is applied to the LTE system for the interaction process between the network device 200 and the terminal device 100, refer to the respective descriptions in Embodiments 1 to 3. The details are not repeated here.

In an embodiment of the present application, the first number of levels is the first number of transport levels, the second number of levels is the second number of transport levels, the third number of levels is the third number of transport levels, the fourth number of levels is the fourth number of transport levels, the fifth number of levels is the fifth number of transport levels, and the sixth number of levels is the sixth number of transport levels.

Various implementations of the present application may be arbitrarily combined to achieve various technical effects.

The foregoing embodiments may be implemented in whole or in part in software, hardware, firmware, or any combination thereof. When implemented as software, the embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product contains one or more computer instructions. When the instructions of a computer program are loaded and executed on a computer, all or some of the processes or functions associated with that application are formed. The computer may be a mainframe computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored on a computer-readable medium or transferred from one computer-readable medium to another computer-readable medium. For example, computer commands may be transmitted from one website site, computer, server, or data center to another website, computer, server, or data center by wire (for example, coaxial cable, optical fiber, or digital subscriber line) or wirelessly. (eg infrared, radio, or microwave) method. Computer-readable media can be any available media that can be accessed by a computer or storage device, such as a server or data center, that contains one or more available media. The available media can be magnetic media (eg, floppy disk, hard disk, or magnetic tape), optical media (eg, DVD), semiconductor media (eg, Solid State Disk), and the like.

One of ordinary skill in the art would understand that all or some of the processes for implementing the method of the above embodiment may be entirely performed using a computer program for issuing hardware-related commands. The program may be stored on a computer-readable medium. the program, when executed, may contain processes of embodiments of the method described above. The above-mentioned storage medium contains various media that can store a control program such as ROM, RAM, magnetic disk or optical disk.

In conclusion, the foregoing are only embodiments of the technical solutions of the present invention and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made on the basis of the disclosure of the present invention will fall within the protection scope of the present invention.

Claims (67)

1. A method for adjusting the number of data streams, in which the MIMO system comprises a terminal device and a network device, and the number of transport layers used by the MIMO system in the downstream data transmission process is the first number of transport layers, comprising steps in which: the first scenario is recognized, by the terminal, and the first message is transmitted to the network device, the first message being used to request that the network device reduce the number of transport layers used in the downlink process, the first message carrying the second number of transport layers and the second the transport levels are less than the first number of transport levels; receive, with the terminal device, a second message transmitted by the network device, wherein the second message is used to configure the number of transport layers in the downlink process, and the second message carries a third number of transport layers, where the third number of transport layers is less than or equal to the second number of transport layers levels; And receive and analyze, using the terminal device, the downlink signal transmitted by the network device, based on the third number of transport layers; wherein the first scenario contains one or a combination of several of the following: on the end device, the first application is running in the foreground, the data rate of the end device is less than the first threshold, the signal strength transmitted by the network device and received by the end device is greater than the second threshold, the screen of the end device is turned off , the terminal device enters the power saving mode, the terminal device is not charging or the temperature of the terminal device is above the third threshold; and the step of recognizing, with the help of the terminal device, the first scenario, in particular, comprises one or more of the sub-steps of: receiving, with the help of the terminal device, the operation of the user, which is the impact on the icon of the first application on the main screen, detecting, with the help of the terminal device of the device that the received reference signal power (RSRP) or the received reference signal quality (RSRQ) is less than the second threshold, receive, with the terminal device, the absence of user operation in a predetermined time period when the screen is turned on, receive, with the terminal device, operation pressing the power key when the screen is turned on, or receiving, by the terminal device, a user operation of operating the power saving mode control switch. 2. The method of claim 1, wherein after the step of receiving and parsing, with the terminal device, the downstream signal transmitted by the network device based on the third number of transport layers, the method further comprises the steps of: recognizing, by the terminal device, a second scenario corresponding to the first scenario, and transmitting a third message to the network device, the third message being used to request a recovery, by the network device, of the number of transport layers used in the downlink process; receiving, by the terminal device, a fourth message transmitted by the network device, wherein the fourth message is used to configure the number of transport layers in the downlink process, and the fourth message carries the first number of transport layers; And receiving and analyzing, by the terminal device, the downstream signal transmitted by the network device based on the first number of transport layers. 3. The method according to claim 2, in which the second scenario contains one or a combination of the following: the application that the terminal device is running in the foreground is not the first application, the data rate of the terminal device is greater than the fourth threshold, the signal strength transmitted by the network device and received by the terminal device is less than the fifth threshold, the target device's screen is on, the target device is entering performance mode, the target device is charging, or the temperature of the target device is below the sixth threshold. 4. The method according to claim 3, in which the step of recognizing, by the terminal device, the second scenario corresponding to the first scenario, in particular, comprises one or more of the sub-steps of: accepting, using the terminal device, a user operation to exit the first application during the operation of the first application, detecting, by the terminal device that the received reference signal power (RSRP) or the received reference signal quality (RSRQ) is less than the fifth threshold, by the terminal device, a press operation representing the operation of the power key when the screen is turned off, or received, with using the end device, a user operation, which is an action on the performance mode control switch. 5. The method according to any one of paragraphs. 2-4, in which the time interval between the time the terminal receives the second message and the time the terminal recognizes the second scenario is greater than or equal to the first time period. 6. The method according to any one of paragraphs. 1-5, in which the first scenario contains that the terminal device operates in the first application in the foreground; and the time interval between the time when the first application starts running in the foreground on the terminal device and the time when the terminal device recognizes the first scenario is greater than or equal to the second time period. 7. The method according to any one of paragraphs. 1-6, in which the first message is a UE supplementary information message for the supplementary message, while the second number of transport layers is carried in the reducedMIMO-LayerFRI-DL field of the supplementary message. 8. The method according to any one of paragraphs. 1-6, in which the second message is an RRC reconfiguration message for a Radio Resource Control (RRC) reconfiguration message, and the third number of transport layers is carried in the MaxMimoLayerNum field of the maximum number of transport layers in the service cell configuration message for the physical downlink shared channel PDSCH service cell configuration. 9. The method according to paragraphs. 2-6, in which the third message is an ancillary message for the UE supplementary information message, and the third message does not contain a reducedMIMO-LayerFRI-DL field. 10. The method according to any one of paragraphs. 2-6, in which the fourth message is an RRC reconfiguration message for radio resource control RRC reconfiguration, wherein the first number of transport layers carried in the fourth message is carried in the MaxMimoLayerNum field in the service cell configuration message for physical downlink shared channel PDSCH service cell configuration. 11. The method according to any one of paragraphs. 1-10, in which the first number of transport layers is configured by the network device for the terminal device in response to the UE capability reporting capability information transmitted by the terminal device. 12. The method according to any one of paragraphs. 1-11, wherein the steps of receiving and parsing, by the terminal device, the downlink signal transmitted by the network device based on the third number of transport layers specifically comprise sub-steps of: receiving, by the terminal device, using the third number of transport layer antennas, the downlink signal transmitted by the network device, filtering and amplifying the downlink signal, and converting the downlink signal to baseband signal using the third number of transport layer receiving RF paths, and performing the inverse mapping process levels for the baseband signal, using the third number of transport layers. 13. The method according to any one of paragraphs. 1-12, in which the number of transport layers used by the MIMO system in the process of uplink data transmission is the fourth number of transport layers; the first message further carries a fifth number of transport layers, wherein the fifth number of transport layers is less than the fourth number of transport layers; the second message is further used to configure the number of transport layers in the uplink process, the second message further carrying a sixth number of transport layers, wherein the sixth number of transport layers is less than or equal to the fifth number of transport layers; and the method further comprises transmitting, by the terminal device, an uplink signal to the network device based on the sixth number of transport layers. 14. A terminal device for adjusting the number of data streams, comprising a memory and one or more processors, wherein the memory is connected to one or more processors and the memory is configured to store a control computer program, the control computer program containing computer instructions, and one or more processors causing computer commands to ensure execution by the end device: recognizing the first scenario and transmitting the first message to the network device, wherein the first message is used to request a reduction, by the network device, of the number of transport layers used in the downlink process, the first message carrying a second number of transport layers, the second number of transport layers being less, than the first number of transport layers; and the first number of transport layers is the number of transport layers used by the terminal device and the network device in the downlink process; receive a second message transmitted by the network device, where the second message is used to configure the number of transport layers in a downlink process, the second message carrying a third number of transport layers and a third number of transport layers less than or equal to the second number of transport layers; And receiving and analyzing the downlink signal transmitted by the network device based on the third number of transport layers; wherein the first scenario contains one or a combination of the following: on the terminal device, the first application is running in the foreground, the data rate of the terminal device is less than the first threshold, the signal strength transmitted by the network device and received by the terminal device is greater than the second threshold, the screen of the terminal device is turned off, the end device enters the power saving mode, the end device is not charging or the temperature of the end device is above the third threshold; A the recognition, by the terminal, of the first scenario specifically comprises one or more of: receive, by the terminal, a user operation that is an action on the first application icon on the main screen, detect, by the terminal, that the received reference signal power (RSRP) or the received reference signal quality (RSRQ) is less than the second threshold, the receipt, by the terminal, of no user operation in a given period of time when the screen is on, or the receipt, by the terminal, of a press operation representing the impact on the power key when the screen is on, or the reception , terminal device, user operation, which is the impact on the power saving mode control switch. 15. The terminal device according to claim 14, in which one or more processors are additionally configured to call computer commands to ensure that the terminal device executes: recognition, after the downlink signal transmitted by the network device is received and parsed, based on the third number of transport layers, the second scenario corresponding to the first scenario, and transmission, to the network device, of the third message, the third message being used to request recovery, by the network device , the number of transport layers used in the downlink process; receiving a fourth message transmitted by the network device, the fourth message being used to configure the number of transport layers in the downlink process, and the fourth message carrying the first number of transport layers; And receiving and analyzing the downlink signal transmitted by the network device based on the first number of transport layers. 16. The terminal device according to claim 15, in which the second scenario contains one or a combination of the following: the application that the terminal device is running in the foreground is not the first application, the data rate of the terminal device is greater than the fourth threshold, the signal strength transmitted by the network device and received by the terminal device is less than the fifth threshold, the end device's screen is on, the end device is entering performance mode, the end device is charged, or the temperature of the end device is below the sixth threshold. 17. The terminal device according to claim 16, in which recognition by the terminal of a second scenario corresponding to the first scenario, in particular, comprises one or more of: receiving by the terminal a user operation to exit the first application while the first application is running, detecting by the terminal that the received reference signal power (RSRP) or the reference signal reception quality (RSRQ) is below the fifth threshold, the terminal receiving a press operation representing the operation of the power key when the screen is turned off, or the terminal receiving the user operation representing the operation of the performance mode control switch. 18. The terminal device according to any one of paragraphs. 15-17, in which the time interval between the time the terminal receives the second message and the time the terminal recognizes the second scenario is greater than or equal to the first time period. 19. The terminal device according to any one of paragraphs. 14-18, in which the first scenario includes the case where the terminal device has the first application running in the foreground; and the interval between the time when the first application starts running in the foreground on the terminal device and the time when the terminal device recognizes the first scenario is greater than or equal to the second time period. 20. Terminal device according to any one of paragraphs. 14-19, in which the first message is a UE supplementary information message for the supplementary message, while the second number of transport layers is carried in the reducedMIMO-LayerFRI-DL field of the supplementary message. 21. The terminal device according to any one of paragraphs. 14-19, in which the second message is an RRC reconfiguration message for radio resource control (RRC) reconfiguration, wherein the third number of transport layers is carried in the MaxMimoLayerNum field in the PDSCH service cell configuration message for the physical downlink shared channel service cell configuration. 22. The terminal device according to any one of paragraphs. 15-19, in which the third message is a supplemental UE information message for the supplementary message, and the third message does not contain the reducedMIMO-LayerFRI-DL field. 23. The terminal device according to any one of paragraphs. 15-19, in which the fourth message is a Radio Controlled Resource Reconfiguration (RRC) message for RRC reconfiguration, wherein the first number of transport layers carried in the fourth message is carried in the MaxMimoLayerNum field in the service cell configuration message for physical downlink shared channel (PDSCH) service cell configuration. 24. The terminal device according to any one of paragraphs. 14-23, in which the first number of transport layers is configured by the network device for the terminal device in response to the capability information of the UE for the capability report transmitted by the terminal device. 25. The terminal device according to any one of paragraphs. 14-24, in which one or more processors, in particular, are configured to call computer instructions, to ensure execution, by the terminal device: receiving, using the third number of transport layer antennas, the downlink signal transmitted by the network device, filtering and amplifying the downlink signal, and converting the downlink signal to baseband signal using the third number of transport layer receive RF paths, and performing the inverse level mapping process for the baseband signal, using a third number of transport layers. 26. The terminal device according to any one of paragraphs. 14-25, in which the number of transport layers used by the terminal device and the network device in the uplink process is the fourth number of transport layers; the first message further carries a fifth number of transport layers, wherein the fifth number of transport layers is less than the fourth number of transport layers; the second message is further used to configure the number of transport layers in the uplink process, the second message further carrying a sixth number of transport layers, the sixth number of transport layers being less than or equal to the fifth number of transport layers; And the one or more processors are further configured to invoke computer instructions to cause the terminal to execute, to the network device, an upstream signal based on the sixth number of transport layers. 27. A computer-readable medium containing commands that cause, when executing commands on an electronic device, execution, by an electronic device of the method according to any one of paragraphs. 1-13. 28. A device for adjusting the number of data streams, comprising a memory, a processor and a computer program stored in the memory and causing, when executed by the processor, the execution, UE, of the method according to any one of paragraphs. 1-13.