Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: acquiring a first weight, wherein the first weight may be determined on the basis of a sounding reference signal; receiving first information, wherein the first information may be used for indicating a second weight related to a downlink precoding matrix indication; receiving second information, wherein the second information may be used for indicating a determination mode for a third weight, and the third weight is used for downlink precoding; and in response to the determination mode for the third weight, determining the third weight on the basis of the first weight and / or the second weight. In the present application, the downlink precoding matrix indication is used as one of reference factors for determining a downlink precoding weight, such that a network device can flexibly select a determination mode for the downlink precoding weight on the basis of actual situations, thereby improving the accuracy of downlink precoding weights and the efficiency of data transmission.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411835014.5, filed on December 12, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to communication methods and apparatus. Background Technology

[0003] In current communication systems, base station functions can be functionally decomposed into multiple logical units. Different logical units are used to implement different communication protocol functions within the base station. For example, a base station can be deployed as two parts: a baseband unit (BBU) and a remote radio unit (RRU). Alternatively, a base station can be divided into two logical units: a central unit (CU) and a distributed unit (DU). The CU can also be referred to as a centralized unit.

[0004] For some logic units, precoding of data symbols is supported, which typically requires processing of the sounding reference signal (SRS), such as channel estimation and SRS measurement. Precoding weights are determined based on the channel estimation and SRS measurement results. However, considering the periodicity of SRS transmission and the fact that some terminals may not be configured to transmit SRS on certain video resources, the precoding weights determined based on SRS cannot accurately reflect the channel state, thus affecting communication efficiency. Summary of the Invention

[0005] This application provides a communication method and apparatus. By using the downlink precoding matrix indication (PMI) as one of the reference factors for determining downlink precoding weights, network devices can flexibly select the method for determining downlink precoding weights according to actual conditions, thereby improving the accuracy of downlink precoding weights and data transmission efficiency.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a communication method is provided, applied to a first logic unit, which may be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. For example, the first logic unit may be an open-radio unit (O-RU). The method may include: acquiring a first weight. For example, the first weight may be determined based on a sounding reference signal (SRS). Receiving first information, which may be used to indicate a second weight related to downlink PMI. Receiving second information, which may be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. In response to the method for determining the third weight, determining the third weight based on the first weight and / or the second weight. For example, the third weight may also be referred to as a downlink precoding weight.

[0008] This application uses downlink PMI as one of the reference factors for determining downlink precoding weights. Network devices can flexibly choose the method for determining downlink precoding weights according to actual conditions, thereby improving the accuracy of downlink precoding weights and data transmission efficiency.

[0009] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight can include the weight information of each terminal's data stream on different antenna ports of the network device.

[0010] This application can be applied to single-user downlink precoding or multi-user downlink precoding scenarios, thus improving its versatility.

[0011] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight can include any of the following: determining the first weight as the third weight; determining the second weight as the third weight; or determining the third weight based on the first weight and the second weight.

[0012] This application provides multiple methods for determining single-user downlink precoding weights, allowing for flexible selection of appropriate methods to obtain accurate single-user downlink precoding weights for different scenarios.

[0013] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter could be used to combine the first and second weights. In some examples, the second information could also be used to indicate the first parameter.

[0014] This application can obtain more accurate single-user downlink precoding weights by configuring different weights for the first weight and the second weight.

[0015] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0016] This application provides a method for determining multi-user downlink precoding weights to obtain accurate multi-user downlink precoding weights.

[0017] In one possible design, the second information may include a first identifier. Determining the third weight based on the first weight and / or the second weight may include: determining the third weight corresponding to the first identifier based on the first weight and / or the second weight corresponding to the first identifier. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the third weight corresponding to the terminal identifier may be determined based on the first weight corresponding to the terminal identifier and / or the second weight corresponding to the terminal identifier. Alternatively, the third weight corresponding to the antenna port identifier may be determined based on the first weight corresponding to the antenna port identifier and / or the second weight corresponding to the antenna port identifier. Alternatively, the third weight corresponding to the frequency domain resource identifier may be determined based on the first weight corresponding to the frequency domain resource identifier and / or the second weight corresponding to the frequency domain resource identifier.

[0018] This application can indicate the determination method of the third weight at multiple granularities, so as to determine a more accurate third weight and improve communication efficiency.

[0019] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: resource element (RE) identifier; resource element group (REG) identifier; resource block (RB) identifier; or resource block group (RBG) identifier.

[0020] This application provides units that can be applied to various frequency domain resources, thereby improving the system's versatility.

[0021] In one possible design, the method may further include: receiving third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0022] The second logic unit of this application can configure more reasonable frequency domain resource scheduling for the first logic unit, thereby improving communication performance.

[0023] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0024] This application allows for flexible selection of single-user scheduling or multi-user scheduling, improving system flexibility.

[0025] In one possible design, the method may further include sending a fourth message. This fourth message can be used to indicate a third weight for single-user downlink precoding.

[0026] The second logic unit of this application can be combined with the third weight used for single-user downlink precoding to perform more precise layer 2 scheduling, thereby improving resource utilization efficiency and communication performance.

[0027] In one possible design scheme, obtaining the first weight may include: determining channel estimation information based on the SRS. The first weight is then determined based on the channel estimation information.

[0028] The first logical unit of this application can be configured to determine the first weight, thereby reducing the resource consumption and bandwidth requirements of the fronthaul interface.

[0029] In one possible design scheme, the method may also include: determining the SRS measurement results based on the SRS.

[0030] The first logic unit of this application can be configured with SRS measurement capabilities, reducing the resource consumption and bandwidth requirements of the fronthaul interface.

[0031] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; signal-to-interference-plus-noise ratio (SINR); precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0032] This application provides a variety of possible SRS measurement results to adopt more appropriate SRS measurement results in different scenarios and improve communication efficiency.

[0033] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0034] This application provides a variety of possible SINRs to adopt a more appropriate SINR in different scenarios and improve communication efficiency.

[0035] In one possible design, before receiving the second information, the method may further include: transmitting fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include the SRS.

[0036] The embodiments of this application are applicable to scenarios where the first logic unit has the ability to process reference signals, thereby improving the versatility of the system.

[0037] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0038] This application is applicable to scenarios where the second weight calculation function is deployed in different logical units, thereby allowing for flexible adjustment of the method for determining the second weight according to the actual situation, thus improving communication efficiency.

[0039] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0040] This application provides a variety of parameters for determining the second weight, so that appropriate parameters can be used in different scenarios to obtain an accurate second weight and improve communication efficiency.

[0041] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0042] This application provides a variety of possible downlink PMI types to determine a more accurate second weight by using a more appropriate downlink PMI type in different scenarios.

[0043] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0044] This application provides a variety of possible downlink PMI beam identifiers to determine more accurate second weights by using a more appropriate downlink PMI beam identifier in different scenarios.

[0045] Secondly, a communication method is provided, applied to a second logical unit, which may be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. For example, the second logical unit may be an O-DU. The method may include: sending first information. The first information may be used to indicate a second weight related to the downlink PMI. Sending second information. The second information may be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. For example, the third weight may be determined based on the first weight and / or the second weight in response to the method for determining the third weight. For example, the first weight may be determined based on SRS.

[0046] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight includes the weight information of each terminal's data stream on different antenna ports of the network device.

[0047] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight can include any of the following: determining the first weight as the third weight; determining the second weight as the third weight; or determining the third weight based on the first weight and the second weight.

[0048] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter can be used to combine the first and second weights. In some examples, the second information can also be used to indicate the first parameter.

[0049] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0050] In one possible design, the second information may include a first identifier. For example, the third weight corresponding to the first identifier is determined based on the first weight and / or the second weight corresponding to the first identifier, in response to the method of determining the third weight. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the third weight corresponding to the terminal identifier may be determined based on the first weight and / or the second weight corresponding to the terminal identifier. Alternatively, the third weight corresponding to the antenna port identifier may be determined based on the first weight and / or the second weight corresponding to the antenna port identifier. Alternatively, the third weight corresponding to the frequency domain resource identifier may be determined based on the first weight and / or the second weight corresponding to the frequency domain resource identifier.

[0051] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: RE identifier; REG identifier; RB identifier; or RBG identifier.

[0052] In one possible design, before sending the second information, the method may further include: acquiring a reference signal measurement result determined based on the reference signal; and determining the method for determining the third weight based on the reference signal measurement result and at least one measurement result threshold.

[0053] In one possible design scheme, the method for determining the third weight based on the SRS measurement result and at least one measurement result threshold may include: determining the method for determining the third weight corresponding to the terminal identifier based on the SRS measurement result corresponding to the terminal identifier and at least one measurement result threshold; or, determining the method for determining the third weight corresponding to the antenna port identifier based on the SRS measurement result corresponding to the antenna port identifier and at least one measurement result threshold; or, determining the method for determining the third weight corresponding to the frequency domain resource identifier based on the SRS measurement result corresponding to the frequency domain resource identifier and at least one measurement result threshold.

[0054] The second logic unit of this application can flexibly determine the method for determining the third weight corresponding to different granularities according to different scenarios.

[0055] In one possible design, the method may further include: sending third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0056] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0057] In one possible design, the method may further include: receiving sixth information. This sixth information is used to indicate the SRS. Channel estimation information is determined based on the SRS. A first weight is determined based on the channel estimation information. For example, the sixth information may include the SRS, or the sixth information may include the beam domain signal of the SRS.

[0058] In one possible design scheme, the method may also include: determining the SRS measurement results based on the SRS.

[0059] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; SINR; precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0060] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0061] In one possible design, before transmitting the third information, the method may further include receiving fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include the SRS (Self-Rating Signal). The third information is determined based on the channel estimation information and / or the reference signal measurement results.

[0062] In one possible design, the method may further include: receiving fourth information. This fourth information may be used to indicate a third weight for single-user downlink precoding. Determining the third information based on channel estimation information and / or reference signal measurements may include: determining the third information based on the third weight for single-user downlink precoding, and the channel estimation information and / or reference signal measurements.

[0063] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0064] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0065] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0066] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0067] Thirdly, a communication device is provided. This communication device can be a first logic unit (such as a network device implementing the corresponding function of the first logic unit), a communication module within the network device implementing the corresponding function of the first logic unit, or a chip responsible for communication functions within the network device implementing the corresponding function of the first logic unit, such as a modem chip (also known as a baseband chip) or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the first logic unit. The communication device may include: a processing unit for acquiring a first weight. For example, the first weight may be determined based on SRS. A transceiver unit for receiving first information, which may be used to indicate a second weight related to downlink PMI. The transceiver unit is further configured to receive second information, which may be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. The processing unit is further configured to determine a third weight based on the first weight and / or the second weight in response to the method for determining the third weight.

[0068] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight can include the weight information of each terminal's data stream on different antenna ports of the network device.

[0069] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight can include any of the following: determining the first weight as the third weight; determining the second weight as the third weight; or determining the third weight based on the first weight and the second weight.

[0070] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter could be used to combine the first and second weights. In some examples, the second information could also be used to indicate the first parameter.

[0071] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0072] In one possible design, the second information may include a first identifier. The processing unit is further configured to: determine a third weight corresponding to the first identifier based on a first weight corresponding to the first identifier and / or a second weight corresponding to the first identifier. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the processing unit is further configured to: determine a third weight corresponding to the terminal identifier based on the first weight corresponding to the terminal identifier and / or the second weight corresponding to the terminal identifier. Alternatively, determine a third weight corresponding to the antenna port identifier based on the first weight corresponding to the antenna port identifier and / or the second weight corresponding to the antenna port identifier, or determine a third weight corresponding to the frequency domain resource identifier based on the first weight corresponding to the frequency domain resource identifier and / or the second weight corresponding to the frequency domain resource identifier.

[0073] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: RE identifier; REG identifier; RB identifier; or RBG identifier.

[0074] In one possible design, the transceiver unit is further configured to: receive third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0075] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0076] In one possible design, the transceiver unit is also used to transmit fourth information. This fourth information can be used to indicate a third weight for single-user downlink precoding.

[0077] In one possible design, the processing unit is further configured to: determine channel estimation information based on the SRS; and determine a first weight based on the channel estimation information.

[0078] In one possible design, the processing unit is also used to: determine the SRS measurement result based on the SRS.

[0079] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; SINR; precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0080] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0081] In one possible design, before receiving the second information, the transceiver unit is further configured to: transmit fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include the SRS.

[0082] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0083] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0084] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0085] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0086] Fourthly, a communication device is provided. This communication device can be a second logic unit (such as a network device implementing the corresponding function of the second logic unit), a communication module within the network device implementing the corresponding function of the second logic unit, or a chip responsible for communication functions within the network device implementing the corresponding function of the second logic unit, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the second logic unit. The communication device may include: a transceiver unit for transmitting first information. The first information can be used to indicate a second weight related to downlink PMI. The transceiver unit is further configured to transmit second information. The second information can be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. For example, the third weight can be determined based on the first weight and / or the second weight in response to the method for determining the third weight. For example, the first weight can be determined based on SRS.

[0087] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight includes the weight information of each terminal's data stream on different antenna ports of the network device.

[0088] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight may include at least one of the following: determining the first weight as the third weight; determining the second weight as the third weight; or, determining the third weight based on the first weight and the second weight.

[0089] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter can be used to combine the first and second weights. In some examples, the second information can also be used to indicate the first parameter.

[0090] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0091] In one possible design, the second information may include a first identifier. For example, the third weight corresponding to the first identifier is determined based on the first weight and / or the second weight corresponding to the first identifier, in response to the method of determining the third weight. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the third weight corresponding to the terminal identifier may be determined based on the first weight and / or the second weight corresponding to the terminal identifier. Alternatively, the third weight corresponding to the antenna port identifier may be determined based on the first weight and / or the second weight corresponding to the antenna port identifier. Alternatively, the third weight corresponding to the frequency domain resource identifier may be determined based on the first weight and / or the second weight corresponding to the frequency domain resource identifier.

[0092] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: RE identifier; REG identifier; RB identifier; or RBG identifier.

[0093] In one possible design, before sending the second information, the communication device further includes: a processing unit for acquiring a reference signal measurement result determined based on the reference signal; and determining the method for determining the third weight based on the reference signal measurement result and at least one measurement result threshold.

[0094] In one possible design, the processing unit is further configured to: determine the method for determining the third weight corresponding to the terminal identifier based on the SRS measurement result corresponding to the terminal identifier and at least one measurement result threshold; or, determine the method for determining the third weight corresponding to the antenna port identifier based on the SRS measurement result corresponding to the antenna port identifier and at least one measurement result threshold; or, determine the method for determining the third weight corresponding to the frequency domain resource identifier based on the SRS measurement result corresponding to the frequency domain resource identifier and at least one measurement result threshold.

[0095] In one possible design, the transceiver unit is further configured to: transmit third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0096] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0097] In one possible design, the transceiver unit is further configured to receive sixth information. This sixth information is used to indicate the SRS. The processing unit is further configured to determine channel estimation information based on the SRS. The processing unit is further configured to determine a first weight based on the channel estimation information. For example, the sixth information includes the SRS, or the sixth information includes a beam domain signal of the SRS.

[0098] In one possible design, the processing unit is also used to: determine the SRS measurement result based on the SRS.

[0099] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; SINR; precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0100] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0101] In one possible design, before transmitting the third information, the transceiver unit is further configured to: receive fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include SRS. The third information is determined based on the channel estimation information and / or the reference signal measurement results.

[0102] In one possible design, the transceiver unit is further configured to receive fourth information. This fourth information can be used to indicate a third weight for single-user downlink precoding. The processing unit is further configured to determine the third information based on the third weight for single-user downlink precoding, as well as channel estimation information and / or reference signal measurement results.

[0103] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0104] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0105] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0106] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0107] Fifthly, a communication device is provided. This communication device can be a first logic unit (such as a network device implementing the corresponding function of the first logic unit), or a communication module within the network device implementing the corresponding function of the first logic unit, or a chip responsible for communication functions within the network device implementing the corresponding function of the first logic unit, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the first logic unit. The communication device may include: a processor for acquiring a first weight. For example, the first weight may be determined based on SRS. A transceiver for receiving first information, which may be used to indicate a second weight related to downlink PMI. The transceiver is further configured to receive second information, which may be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. The processor is further configured to determine a third weight based on the first weight and / or the second weight in response to the method for determining the third weight.

[0108] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight can include the weight information of each terminal's data stream on different antenna ports of the network device.

[0109] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight may include at least one of the following: determining the first weight as the third weight; determining the second weight as the third weight; or, determining the third weight based on the first weight and the second weight.

[0110] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter could be used to combine the first and second weights. In some examples, the second information could also be used to indicate the first parameter.

[0111] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0112] In one possible design, the second information may include a first identifier. The processor is further configured to: determine a third weight corresponding to the first identifier based on a first weight corresponding to the first identifier and / or a second weight corresponding to the first identifier. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the processor is further configured to: determine a third weight corresponding to the terminal identifier based on the first weight corresponding to the terminal identifier and / or the second weight corresponding to the terminal identifier. Alternatively, determine a third weight corresponding to the antenna port identifier based on the first weight corresponding to the antenna port identifier and / or the second weight corresponding to the antenna port identifier. Alternatively, determine a third weight corresponding to the frequency domain resource identifier based on the first weight corresponding to the frequency domain resource identifier and / or the second weight corresponding to the frequency domain resource identifier.

[0113] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: RE identifier; REG identifier; RB identifier; or RBG identifier.

[0114] In one possible design, the transceiver is further configured to receive third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0115] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0116] In one possible design, the transceiver is also used to transmit a fourth message. This fourth message can be used to indicate a third weight for single-user downlink precoding.

[0117] In one possible design, the processor is further configured to: determine channel estimation information based on the SRS; and determine a first weight based on the channel estimation information.

[0118] In one possible design, the processor is also used to: determine the SRS measurement results based on the SRS.

[0119] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; SINR; precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0120] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0121] In one possible design, before receiving the second information, the transceiver is further configured to transmit fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include the SRS.

[0122] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0123] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0124] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0125] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0126] Sixthly, a communication device is provided. This communication device can be a second logic unit (such as a network device implementing the corresponding function of the second logic unit), a communication module within the network device implementing the corresponding function of the second logic unit, or a chip responsible for communication functions within the network device implementing the corresponding function of the second logic unit, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the second logic unit. The communication device may include: a transceiver for transmitting first information. The first information can be used to indicate a second weight related to downlink PMI. The transceiver is also used to transmit second information. The second information can be used to indicate a method for determining a third weight. The third weight is used for downlink precoding. For example, the third weight can be determined based on the first weight and / or the second weight in response to the method for determining the third weight. For example, the first weight can be determined based on SRS.

[0127] In one possible design, when downlink precoding is single-user downlink precoding, the third weight can include the weight information of a terminal's data stream on different antenna ports of the network device. Alternatively, when downlink precoding is multi-user downlink precoding, the third weight includes the weight information of each terminal's data stream on different antenna ports of the network device.

[0128] In one possible design scheme, when the downlink precoding is single-user downlink precoding, the method for determining the third weight may include at least one of the following: determining the first weight as the third weight; determining the second weight as the third weight; or, determining the third weight based on the first weight and the second weight.

[0129] In one possible design, determining the third weight based on the first and second weights can include determining the third weight based on the first weight, the second weight, and a first parameter. For example, the first parameter can be used to combine the first and second weights. In some examples, the second information can also be used to indicate the first parameter.

[0130] In one possible design scheme, when downlink precoding is multi-user downlink precoding, the method for determining the third weight may include: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

[0131] In one possible design, the second information may include a first identifier. For example, the third weight corresponding to the first identifier is determined based on the first weight and / or the second weight corresponding to the first identifier, in response to the method of determining the third weight. In some examples, the first identifier may include at least one of the following identifiers: a terminal identifier associated with the method of determining the third weight; an antenna port identifier associated with the method of determining the third weight; or a frequency domain resource identifier associated with the method of determining the third weight. Accordingly, the third weight corresponding to the terminal identifier may be determined based on the first weight and / or the second weight corresponding to the terminal identifier. Alternatively, the third weight corresponding to the antenna port identifier may be determined based on the first weight and / or the second weight corresponding to the antenna port identifier. Alternatively, the third weight corresponding to the frequency domain resource identifier may be determined based on the first weight and / or the second weight corresponding to the frequency domain resource identifier.

[0132] In one possible design, the frequency domain resource identifier includes at least one of the following identifiers: RE identifier; REG identifier; RB identifier; or RBG identifier.

[0133] In one possible design, before sending the second information, the communication device further includes: a processor for acquiring a reference signal measurement result determined based on a reference signal; and determining the method for determining the third weight based on the reference signal measurement result and at least one measurement result threshold.

[0134] In one possible design, the processor is further configured to: determine the method for determining the third weight corresponding to the terminal identifier based on the SRS measurement result corresponding to the terminal identifier and at least one measurement result threshold; or, determine the method for determining the third weight corresponding to the antenna port identifier based on the SRS measurement result corresponding to the antenna port identifier and at least one measurement result threshold; or, determine the method for determining the third weight corresponding to the frequency domain resource identifier based on the SRS measurement result corresponding to the frequency domain resource identifier and at least one measurement result threshold.

[0135] In one possible design, the transceiver is also used to transmit third information. This third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier.

[0136] In one possible design, the frequency domain resource scheduling method is single-user scheduling, with only one terminal identifier. Alternatively, the frequency domain resource scheduling method is multi-single-user scheduling, with multiple terminal identifiers.

[0137] In one possible design, the transceiver is further configured to receive sixth information. This sixth information is used to indicate the SRS. The processor is further configured to determine channel estimation information based on the SRS. The processor is further configured to determine a first weight based on the channel estimation information. For example, the sixth information may include the SRS, or the sixth information may include the beam domain signal of the SRS.

[0138] In one possible design, the processor is also used to: determine the SRS measurement results based on the SRS.

[0139] In one possible design, the SRS measurement results may include at least one of the following parameters: reference signal received power; SINR; precoding matrix indication; rank indication; channel quality indication; or, uplink timing synchronization.

[0140] In one possible design, SINR may include SINR before equalization and / or SINR after equalization.

[0141] In one possible design, before transmitting the third information, the transceiver is further configured to: receive fifth information. This fifth information may include channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal. For example, the reference signal may include the SRS (Self-Rating Signal). The third information is determined based on the channel estimation information and / or the reference signal measurement results.

[0142] In one possible design, the transceiver is further configured to receive fourth information. This fourth information can be used to indicate a third weight for single-user downlink precoding. The processor is further configured to determine the third information based on the third weight for single-user downlink precoding, as well as channel estimation information and / or reference signal measurements.

[0143] In one possible design, the first information may include the second weights. Alternatively, the first information may include one or more second parameters related to the downside PMI. For example, the second weights may be determined based on one or more second parameters related to the downside PMI.

[0144] In one possible design, the second parameter may include at least one of the following parameters: downlink PMI type; polarization direction dimension; downlink PMI beam identifier; downlink PMI beam offset identifier; or, beam selection and phase adjustment indication parameters.

[0145] In one possible design, the downlink PMI type may include downlink PMI type 1 and / or downlink PMI type 2.

[0146] In one possible design, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier and / or a downlink PMI vertical beam index.

[0147] A seventh aspect provides a communication system, the system comprising: a first logic unit and a second logic unit, the first logic unit being configured to execute the methods described in the first aspect and various possible implementations thereof, and the second logic unit being configured to execute the methods described in the second aspect and various possible implementations thereof.

[0148] Eighthly, a chip is provided, comprising interface circuitry and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the first and second aspects. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first and second aspects. The interface circuitry is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0149] Ninthly, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are executed on a computer, the computer causes the computer to perform a communication method as designed in any of the foregoing aspects.

[0150] A tenth aspect provides a computer program product. The computer program product includes a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as designed in any of the foregoing aspects.

[0151] The beneficial effects of the methods in any of the second to tenth aspects mentioned above can be referred to the description of the beneficial effects of the methods in the first aspect, and will not be repeated here. Attached Figure Description

[0152] Figure 1 is a schematic diagram of the architecture of a communication system applied in an embodiment of this application;

[0153] Figure 2 is a schematic diagram of the functional segmentation of the communication protocol between BBU and RRU provided in an embodiment of this application;

[0154] Figure 3 is a schematic diagram of a wireless access network architecture provided in an embodiment of this application;

[0155] Figure 4 is a schematic diagram of another wireless access network architecture provided in an embodiment of this application;

[0156] Figure 5 is a schematic diagram of a communication protocol function segmentation method provided in an embodiment of this application;

[0157] Figure 6 is a schematic diagram of another communication protocol function segmentation method provided in an embodiment of this application;

[0158] Figure 7 is a schematic diagram of another communication protocol function segmentation method provided in the embodiments of this application;

[0159] Figure 8 is a schematic diagram of a communication scenario provided in an embodiment of this application;

[0160] Figure 9 is a schematic diagram of another communication scenario provided by an embodiment of this application;

[0161] Figure 10 is a schematic diagram of a communication method provided in an embodiment of this application;

[0162] Figure 11 is a schematic diagram of the functional division of a network device according to an embodiment of this application;

[0163] Figure 12 is a schematic diagram of another communication method provided in an embodiment of this application;

[0164] Figure 13 is a schematic diagram of another network device function division provided in an embodiment of this application;

[0165] Figure 14 is a schematic diagram of another communication method provided in an embodiment of this application;

[0166] Figure 15 is a schematic diagram of another network device function division provided in an embodiment of this application;

[0167] Figure 16 is a schematic diagram of another communication method provided in an embodiment of this application;

[0168] Figure 17 is a schematic diagram of another network device function division provided in an embodiment of this application;

[0169] Figure 18 is a schematic diagram of another communication method provided in an embodiment of this application;

[0170] Figure 19 is a schematic diagram of a communication device provided in an embodiment of this application;

[0171] Figure 20 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0172] Figure 1 is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is wirelessly connected to the RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 via wireless or wired means. The core network equipment in core network 200 and the RAN node 110 in RAN 100 can be independent and different physical devices, or they can be the same physical device that integrates the logical functions of the core network equipment and the logical functions of the RAN node. Communication system 1000 may also include Internet 300.

[0173] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a future communications network, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0174] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station (BS), an evolved NodeB (eNodeB / eNB), a transmission reception point (TRP), a generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a future base station in a future communication network, or a base station in a future mobile communication system. RAN nodes can be macro base stations (as shown in Figure 1, 110a), micro base stations or indoor stations (as shown in Figure 1, 110b), relay nodes, or master nodes.

[0175] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). An RU can also be called a radio frequency unit. Here, the CU performs the functions of the base station's radio resource control protocol and packet data convergence protocol (PDCP), and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the base station's radio link control layer and medium access control (MAC) layer, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). RUs can be included in radio frequency equipment, such as remote radio units (RRUs) or active antenna units (AAUs). CUs can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0176] In different systems, RAN nodes may have different names. For example, in an open radio access network (O-RAN) system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, an RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0177] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0178] In some examples, the core network 200 may include any core network device such as the access and mobility management function (AMF) entity, the session management function (SMF) entity, the user plane function (UPF) entity, the sensing service control function (SSCF), the sensing data processing function (SDPF), and the unified data management (UDM).

[0179] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0180] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0181] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0182] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0183] In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. These communication devices can include network devices and terminal devices; network devices can also be called base station devices, i.e., the wireless access network devices mentioned above. Air interface resources can include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. These communication devices can also be called communication apparatuses.

[0184] The solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication can include: wireless communication between network devices and terminals, wireless communication between network devices, and wireless communication between terminals. In this application, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0185] In global system for mobile communications (GSM), wideband code division multiple access (WCDMA), universal mobile telecommunications system (UMTS), long term evolution (LTE), and 5G systems, base stations can be deployed by dividing them into two functional entities: a base unit (BBU) and a radio frequency unit (RRU), according to a bottom-layer partitioning method. This bottom-layer partitioning method can be a partitioning of the physical layer and the radio frequency (RF) portion. It is understood that in the various embodiments of this application, "partitioning" and "division" can be used interchangeably. The BBU is connected to one or more RRUs via optical fiber, metallic cabling, or microwave links. The BBU primarily performs centralized upper-layer processing of baseband signals. The RRU primarily performs baseband signal reception and transmission, as well as RF signal modulation and demodulation, data processing, and power amplification. The RRU is closer to the antenna, resulting in lower feeder loss. In some cases, the RRU can also be called an RU or an AAU. The interface between the BBU and RRU can be called a fronthaul interface or a bottom-layer partitioning interface.

[0186] Referring to Figure 2, which illustrates a functional division of the communication protocol between a BBU and an RRU, in related technologies, the interface between the BBU and RRU can use the Common Public Radio Interface (CPRI) protocol for communication interaction. The CPRI protocol defines the key communication interface specifications for communication between radio equipment control (REC) and radio equipment (RE) in a wireless communication network. For example, the REC can be considered the aforementioned BBU, and the radio equipment can be considered the aforementioned RRU. As shown in Figure 2, the CPRI interface allocates the radio frequency (RF) layer functions to RRU 1, and the physical (PHY) layer and above protocol layer functions to BBU 1. The PHY layer can be further divided into a high PHY layer and a low PHY layer. The high PHY layer can also be called High PHY, and the low PHY layer can also be called Low PHY. Protocol layer functions above the PHY layer can include the radio resource control (RRC) layer, SDAP layer, PDCP layer, radio link control (RLC) layer, and MAC layer.

[0187] The amount of data transmitted between the BBU's PHY layer and the RRU's RF layer is directly related to the size of the antenna array on the RRU. The splitting method specified by the CPRI protocol results in excessively large data volumes on the fronthaul interface, making it unsuitable for scenarios with large-scale antenna arrays. For example, assuming a fiber with a bandwidth of 9.8 gigabits per second (Gbps) can support two 4-transmit 4-receive (4T4R) antennas and a cell with a wireless bandwidth of 20 MHz on a fronthaul interface using the CPRI protocol, then for a cell with 64 4T4R antennas and a 100MHz bandwidth, approximately 32 9.8Gbps fibers would need to be deployed on the CPRI interface.

[0188] Some solutions propose an evolution of the CPRI protocol, namely an enhanced CPRI protocol, denoted as eCPRI. Referring again to Figure 2, the eCPRI protocol deploys the lower PHY layer in the RRU (e.g., RRU 2) and the higher PHY layer in the BBU (e.g., BBU 2). Furthermore, it redefines the interface specification between the BBU and RRU, i.e., between the higher and lower PHY layers. The eCPRI protocol transforms the interface between the BBU and RRU from the RF layer-PHY layer interface specified in the CPRI protocol to an interface between the higher and lower PHY layers, converting the original fiber optic communication between the RF layer and PHY layer into communication within the RRU's internal board or field-programmable gate array (FPGA) chip. Moreover, the data dimension of the communication between the higher PHY layer of the BBU and the lower PHY layer of the RRU is reduced, no longer directly related to the antenna array size on the RRU.

[0189] The splitting method used in the aforementioned CPRI or eCPRI interfaces allows the BBU to process baseband signals in a highly centralized manner. This enables centralized deployment of computing resources, resulting in high resource utilization and low deployment costs. However, it also places a significant demand on fronthaul link bandwidth, leading to higher fiber optic deployment costs.

[0190] In future communication systems, Figure 3 illustrates a potential new RAN architecture. This architecture reclassifies base station functions into RU functions, radio network area (RNA) functions, and RAN automation functions. The RNA and RU functions communicate via a low-layer split (LLS) interface, and the RU function can establish a RAN-UE interface for communication with the terminal. The RNA function communicates with the core network (CN) via the RAN-CN interface. The RAN automation function manages the RU and RNA functions through a network function (NF) management interface. The RAN automation function is controlled through network management. In this architecture, the RU function can be viewed as the aforementioned RRU or AAU, and the RNA function as the aforementioned BBU.

[0191] In related technologies, to reduce the pressure on fronthaul link bandwidth and deployment costs caused by the underlying segmentation method, 3GPP proposed a base station function partitioning method. For example, for gNBs in 5G, a higher-layer segmentation method is adopted, splitting the base station into two functional entities such as CU and DU. The midhaul link between CU and DU has lower network bandwidth requirements. The radio access network shown in Figure 4 is divided according to CU and DU. For example, the access network equipment can be a gNB, which can be composed of CU and DU. Of course, DU can include one or more, which is not limited in this embodiment. gNBs can communicate with the core network elements of the 5G core network (5GC) through the next generation (NG) interface. Different gNBs can communicate with each other through the Xn interface, for example, through the Xn-control (C) interface. CUs can communicate with different DUs through the F1 interface.

[0192] Furthermore, Figure 5 illustrates several possible communication protocol function segmentation methods. Communication protocol functions can be divided according to protocol layer granularity. For example, options 1 through 8 are provided. Option 1 can be the communication function segmentation between the RRC layer and the PDCP layer as shown in Figure 5, or option 2 can be the communication function segmentation between the SDAP layer and the PDCP layer as shown in Figure 5. It is understood that subsequent embodiments of this application will be described using the control plane RRC layer as an example. For user plane segmentation, the RRC layer can be replaced with the SDAP layer, and this will not be elaborated further in the embodiments of this application.

[0193] Option 2 can be the communication function division between the PDCP layer and the higher RLC layer, as shown in Figure 5. Option 3 can be the communication function division between the higher RLC layer and the lower RLC layer, as shown in Figure 5. Therefore, Option 3 can also be considered as communication function division within the RLC layer. Option 4 can be the communication function division between the lower RLC layer and the higher MAC layer, as shown in Figure 5. Option 5 can be the communication function division between the higher MAC layer and the lower MAC layer, as shown in Figure 5. Therefore, Option 5 can also be considered as communication function division within the MAC layer. Option 6 can be the communication function division between the lower MAC layer and the higher PHY layer, as shown in Figure 5. Option 7 can be the communication function division between the higher PHY layer and the lower PHY layer, as shown in Figure 5. Therefore, Option 7 can also be considered as communication function division within the PHY layer. Option 8 can be the communication function division between the lower PHY layer and the RF layer, as shown in Figure 5. The division method of Option 8 is exactly the same as the division method specified in the CPRI protocol.

[0194] As can be seen, more granular division of communication protocol functions can be performed within certain protocol layers. For example, protocol layers such as the RLC layer, MAC layer, and PHY layer can be divided into higher and lower layers. The following description uses the PHY layer as an example to illustrate the division of communication protocol functions within a protocol layer. The division methods for other protocol layers are similar, the difference being that the communication protocol functions within different protocol layers can differ. For specific details, please refer to the communication protocol functions within the corresponding protocol layer; this application does not impose limitations on these aspects. Referring to Figure 6, the communication functions within the PHY layer are divided for downlink (DL) communication. Assume that the PHY layer can be further divided into functions such as coding, rate mapping, scrambling, modulation, layer mapping, precoding, resource element (RE) mapping, digital beamforming (DBF), inverse fast fourier transformation (IFFT) / addition of cyclic prefix (CP), digital to analog, and analog beamforming. The specific execution process of each function shown in Figure 6 can be found in related technologies, and will not be elaborated further in this application. A resource element can be a unit radio resource consisting of a subcarrier and a symbol. Therefore, the segmentation method for option 7 can also include options 7-1, 7-2, 7-2a, and 7-3 as shown in Figure 6.

[0195] For example, referring to Figure 6, option 7-1 can be a division of communication protocol functions between IFFT / adding CP and DBF. Option 7-2 can be a division of communication protocol functions between precoding and layer mapping. Option 7-2a can be a division of communication protocol functions between DBF and RE mapping. Option 7-3 can be a division of communication protocol functions between modulation and scrambling. Option 7-2a can also be called category A, and option 7-2 can also be called category B. The core difference is that the precoding function in option 7-2a is configured in DU (or CU), while the precoding function in option 7-2 is configured in RU (or DU). Option 7-3 can also be considered the same as the downlink segmentation method of the eCPRI protocol. Option 7-3 can also be called interface e (Ie) for downlink, Ie segmentation for downlink, Ie2 for downlink, Ie2 segmentation for downlink, etc. In Figure 6, if CP is added to IFFT / to divide the communication protocol function between digital and analog, it corresponds to option 8 mentioned above, which is the segmentation method corresponding to the CPRI protocol.

[0196] It is worth noting that both radio equipment and resource particles can be abbreviated as RE. Therefore, in order to distinguish between radio equipment and resource particles, in the embodiments of this application, RE can refer to resource particles, while radio equipment is not described using this abbreviation.

[0197] In Figure 6, analog beamforming, digital beamforming, and precoding can all be considered beamforming techniques. Beamforming is a signal processing technique that uses antenna arrays to transmit and receive signals in a directional manner. By adjusting the basic elements and phase parameters of the antenna array, signals at certain angles can achieve constructive interference, while signals at other angles can achieve destructive interference, allowing the target signal to be aligned with the target receiving device. For example, the analog beamforming function shown in Figure 6 can generate a beam in a specific direction by adjusting the phase of the digital signal on the antenna at a phase shifter in the analog domain. It can be assumed that all antennas are processing the same signal. In some embodiments, for the various communication function modules within the PHY layer, such as the analog beamforming function module, assuming that all antennas in the network device implementing the PHY layer function are processing the same signal, a beam in a specific direction can be obtained by adjusting the phase of the digital signal on the antenna at a phase shifter in the analog domain. For digital beamforming modules, the phase and amplitude of baseband signals from different data streams can be adjusted to ensure that the transmitted signals on each antenna are different, thus enabling more flexible generation of multiple beams with varying directions and power intensities. This allows for more effective utilization of spatial diversity and multiplexing.

[0198] In some scenarios, digital beamforming and precoding in Figure 6 can be the same module, so digital beamforming can also be called precoding. Precoding involves adjusting the phase and amplitude of the baseband signals of different data streams to make the transmitted signals on each antenna different, which can more flexibly generate multiple beams with different directions and power intensities. This effectively utilizes spatial diversity or spatial multiplexing.

[0199] In some communication systems employing beamforming technology, the BBU may also deploy sounding reference signal-based beamforging (SRS-BF) modules, single-user beamforging (SRF) modules, and / or multi-user beamforging (MU-BF) modules. The SRS-BF module can generate weighting coefficients for single-user signals, which are then provided to the precoding module during signal precoding. The MU-BF module can generate weighting coefficients for multi-user signals, which are also provided to the precoding module during signal precoding.

[0200] A sounding reference signal (SRS) is a reference signal sent by a terminal to a base station to measure the uplink channel state. The base station can measure the SRS signal and obtain an SRS measurement report. This SRS measurement report may include a precoding matrix indication (PMI) for uplink, a channel quality indicator (CQI) for uplink, and a rank indication (RI) for uplink. The base station can send the PMI to the UE so that the UE can perform uplink beamforming. Alternatively, in time division duplex (TDD) scenarios, the base station can leverage the reciprocity between the uplink and downlink channels to input the SRS measurement report into the SU-BF module or MU-BF module, so that the SU-BF module or MU-BF module can generate weights (or weight coefficients) for downlink precoding.

[0201] Similar to SRS is the Channel State Information Reference Signal (CSI-RS). Unlike SRS, CSI-RS is a reference signal sent by the base station to the terminal to measure the downlink channel state. The terminal measures the CSI-RS to obtain a CSI-RS measurement report, also known as Channel State Information (CSI). CSI can include PMI (Power Management Information) for downlink, CQI (Cardboard Quality Information) for downlink, and RI (Reference Information) for downlink. The terminal reports the CSI to the base station, so that the base station inputs the CSI into the SU-BF (Supply-Based Function) module or MU-BF (Multi-Based Function) module to generate weights (or weight coefficients) for downlink precoding.

[0202] During uplink or downlink communication between the UE and the base station, a demodulation reference signal (DMRS) can be transmitted along with the data signal. This allows the receiver to demodulate the uplink or downlink data signal based on the received DMRS. For example, in uplink communication, the receiver can be the base station, and in downlink communication, the receiver can be the terminal. Demodulation can include channel estimation and equalization of the data signal. For instance, the receiver can perform channel estimation based on the received DMRS and the pilot sequence carried by the DMRS.

[0203] Network devices can determine the precoding used for uplink or downlink by measuring the aforementioned reference signals. Related technologies support RUs performing downlink precoding on data symbols and allow DUs or RUs to calculate the weights required for downlink precoding. After downlink precoding and resource mapping, data symbols can be converted into subcarrier signals carrying multiple superimposed data symbols. Referring to Figure 7, current protocols stipulate that SRS processing must be performed on the DU, including channel estimation and measurement of SRS. The DU can perform layer (L)2 scheduling based on the SRS channel estimation results, determining the terminal scheduling mode corresponding to different frequency bands, such as single-user (SU) scheduling, multi-user (MU) scheduling, etc. The DU can periodically inform the RU of the CSI of each user and the scheduling status of each time slot. The CSI can be obtained by the DU based on the SRS channel estimation results, and the scheduling status of each time slot is the aforementioned SU scheduling and MU scheduling. The RU can determine the corresponding downlink precoding weights based on the CSI and the terminals corresponding to each time slot. This allows the downlink precoding weights to be used to weight data symbols, and the weighted signal to be transmitted through the corresponding antenna ports, thereby obtaining interference cancellation or diversity gains. The method by which the RU performs downlink precoding weight calculations can be called channel information-based beamforming (CIBF). It is understood that the RU in this embodiment can be a logical unit with relatively low communication functionality in the functional division of the foregoing embodiments, and the DU can be a logical unit with relatively high communication functionality in the functional division of the foregoing embodiments.

[0204] However, while the above method provides support for RU calculation of downlink precoding weights, the CSI required for this calculation is obtained based on the channel estimation results of SRS. This downlink precoding weight does not incorporate the codebook information of PMI from the CSI reported by the terminal to the base station. This PMI codebook information can be determined by the terminal measuring the downlink CSI-RS. For SRS aging or incomplete SRS reception, the downlink precoding weights determined using a single method are inaccurate. For example, if SRS is periodically transmitted, considering the scarcity of uplink communication resources, the SRS period will be relatively long. This can lead to a significant difference between the SRS measurement results and the actual current channel conditions, i.e., SRS aging. Since SRS is a reference signal sent by the terminal to the network device, considering the different usage scenarios of various terminals, the network device may not receive all SRS signals, resulting in inaccurate SRS channel estimation results. Consequently, the downlink precoding weights calculated based on the SRS channel estimation results will be inaccurate, affecting communication efficiency.

[0205] Therefore, this application provides a communication method in which precoding weights can be determined not only based on SRS measurement results but also based on downlink PMI, i.e., downlink PMI is used as one of the reference factors for determining downlink precoding weights. In this way, network devices can flexibly choose the method for determining downlink precoding weights according to actual conditions, thereby improving the accuracy of downlink precoding weights and data transmission efficiency.

[0206] The communication method and apparatus will be further described below with reference to the accompanying drawings. It is understood that the embodiments of this application use the first and second logic units as examples of the execution entities in the interactive illustration, but this application does not limit the execution entities in the interactive illustration. For example, the first and second logic units can be network devices. The method executed by the network device in this application can also be implemented by modules (e.g., circuits, processors, chips, or chip systems) in the network device, or by logic nodes, logic modules, or software that can implement all or part of the functions of the network device.

[0207] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0208] Figure 8 is a schematic diagram of a communication scenario provided by an embodiment of this application.

[0209] As shown in Figure 8, the access network device can be divided into multiple logical units such as RU 210, DU 220, and CU 230. Of course, the access network device may include one or more RU 210, one or more DU 220, and one or more CU 230. The CU 230 is connected to the 5GC 240 and is used to realize communication with the core network device. In various embodiments of this application, the core network device may also be referred to as a core network element.

[0210] Among them, 5GC 240 can be connected to multiple CU 230, one CU 230 can be connected to multiple DU 220, and one DU 220 can be connected to multiple RU 210.

[0211] The access network device can be a gNB. The access network device provides NR user plane and control plane protocol endpoints to the terminal and communicates with the 5GC 240 via the NG interface. The access network device is used to provide wireless network connectivity between the terminal and the core network.

[0212] The CU 230 can manage the RRC, SDAP, and PDCP layer protocols of access network devices and control one or more DU operations. The CU 230 communicates with the DU 220 via the F1 interface.

[0213] The DU 220 can host the RLC, MAC, and PHY layers of access network devices, and its operation is controlled by the CU 230. One DU 220 can support one or more cells, and one cell supports one DU 220.

[0214] The RU 210 can be referred to as a wireless unit, radio frequency unit, or radio frequency remote unit. Its main functions include receiving and transmitting baseband signals, as well as modulation and demodulation of radio frequency signals, data processing, and power amplification. The RU can be deployed close to the antenna, resulting in low feeder loss.

[0215] 5GC 240 may include one or more possible core network elements such as AMF entity, SMF entity, UPF entity, UDM entity, etc. 5GC and RAN together constitute the 5G network, providing users with service channels to connect to data networks and servers. Of course, 5GC 240 can also be replaced by the core network of future communication systems; this application embodiment does not limit this.

[0216] The RAN provides wireless network connectivity between the UE and the core network. The RAN can include access network equipment, such as gNBs. In some cases, "access network equipment" can refer to the entire RAN. RAN deployment can include centralized RAN (CRAN) and distributed RAN (DRAN). CRAN uses a separate BBU and RRU architecture, with each BBU located in a central equipment room, forming a BBU pool. It communicates with the RRUs via the fronthaul network. DRAN uses a distributed deployment of BBUs and RRUs. Each BBU is deployed separately in a rack, while the RRUs can be deployed together in the rack with the BBUs, or the RRUs can be deployed close to the antenna on a tower.

[0217] In some examples, RU 210, DU 220, and CU 230 can be deployed on the same physical device or on different physical devices. Alternatively, some logic units in RU 210, DU 220, and CU 230 may be deployed on the same physical device, while other logic units may be deployed on different physical devices. This embodiment of the application does not impose any limitations on this.

[0218] It is understandable that access network equipment can also include cases where it is split into two logical units. For example, if CU 230 and DU 220 are deployed on the same physical device, CU 230 and DU 220 can be regarded as a single logical unit. Alternatively, if DU 220 and RU 210 are deployed on the same physical device, DU 220 and RU 210 can be regarded as a single logical unit.

[0219] Of course, this application is not limited to the 5G network architecture; the embodiments of this application are also applicable to LTE networks and other possible future network architectures such as future communication networks. It should be understood that the embodiments of this application can be applied to any network architecture with communication connectivity capabilities.

[0220] Figure 9 is a schematic diagram of another communication scenario provided by an embodiment of this application.

[0221] The embodiments of this application can also be applied to O-RAN network architecture. Therefore, Figure 9 illustrates a scenario under the O-RAN architecture. In the O-RAN architecture, access network devices can be divided into three functional entities: O-RU, O-DU, and O-CU. The O-RU is similar to the aforementioned RU, the O-DU is similar to the aforementioned DU, and the O-CU is similar to the aforementioned CU. The interfaces between these functional entities can be referred to the descriptions in the previous embodiments, and will not be repeated here. The O-RAN network architecture may also include a near-real-time RAN intelligent controller (RIC) and service management and orchestration (SMO).

[0222] The near real-time RIC is primarily used to collect network information and perform necessary optimization tasks. The near real-time RIC communicates with the O-CU and O-DU via the E2 interface. The near real-time RIC may include a QoS management module, a radio connection management module, an interference management module, and a mobility management module.

[0223] The SMO can include multiple functional modules, such as non-real-time RIC, configuration, policy, design, and inventory modules. The main functions of the SMO can include cloud infrastructure operation, administration, and maintenance (OAM). For example, it can operate, maintain, and manage cloud infrastructure through the O2 interface. The SMO can also operate, maintain, and manage the RAN through the O1 interface. The SMO can also include a non-real-time RIC, such as one that combines artificial intelligence (AI) and big data analytics to achieve non-real-time macro-control and intervention of the O-RAN through the A1 interface. Each functional entity in the O-RAN can function as an independent entity, communicating with the SMO independently using the O1 interface. In some examples, the SMO and near-real-time RIC can communicate via either the A1 or O1 interface; the appropriate communication path can be selected based on the specific circumstances, which will not be elaborated further in this embodiment.

[0224] Figure 10 is a schematic diagram of a communication method provided by an embodiment of this application.

[0225] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1, 8, and 9. This method can be applied to LTE, LTE frequency division duplex (FDD) systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), and V2X. V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), long-term evolution-vehicle (LTE-V), vehicle-to-everything (V2X), MTC, IoT, long-term evolution-machine (LTE-M), machine-to-machine (M2M), and device-to-device (D2D) wireless communication scenarios. In the embodiments of this application, the first and second logical units can be access network devices. The first logical unit and the second logical unit can be deployed on the same access network device or on different access network devices; this application does not limit this. The following embodiments will be described using an O-RU as the first logical unit and an O-DU as the second logical unit as an example. Of course, in other examples, the first logical unit can also be an RU, O-DU, or DU, and the second logical unit can also be a DU, CU, or O-CU; this application does not limit this. In the various embodiments of this application, the logical unit can also be referred to as a network-side device, network device, network equipment, functional entity, etc., and this is not limited here. The method may include the following steps:

[0226] S101, the first logic unit obtains the first weight.

[0227] For example, the first logic unit can determine a first weight based on the SRS. This first weight can also be called the SRS weight. In some examples, the ability of the first logic unit to perform SRS processing can be pre-configured. In various embodiments of this application, SRS processing may include, but is not limited to, channel estimation of the SRS and measurement of the SRS. For example, the first logic unit performs channel estimation of the SRS to obtain channel estimation information. In various embodiments of this application, the channel estimation information can also be called the channel estimation result. For example, it can be the estimated equivalent channel. As another example, the first logic unit can perform SRS measurement to obtain SRS measurement results.

[0228] In some examples, the terminal can send SRS to the first logic unit. Correspondingly, the first logic unit can receive the SRS from the terminal through its own antenna and perform antenna-to-beam (A2B) mapping on the received SRS so that the first logic unit can process the SRS according to the mapped beam-dimensional signal. For example, the A2B mapping mentioned in this application embodiment can convert multiple antenna port-dimensional SRS into signals of multiple beam-dimensional signals. The antenna port signals can be the signals received by each antenna port of the first logic unit, and the beam-dimensional signals can include SRS from different beam directions.

[0229] A possible implementation of A2B mapping can be described as follows: Assume the first logic unit receives K-dimensional SRS from K antenna ports, denoted as y. K×1 Where K is a positive integer. The first logic unit can handle y. K×1 Performing a discrete Fourier transform (DFT) yields W. K×K *y K×1 This means obtaining signals across multiple beam dimensions. Wherein, W K×K This is the DFT transformation matrix, where each element can be... Where i,j=1,…,N. N represents the number of sampling points in the DFT transform, which can also be understood as the resolution of the DFT transform. Of course, the specific implementation process of A2B mapping can be found in relevant technologies, and will not be described in detail here.

[0230] In some embodiments, the first logic unit can determine the first weight based on the channel estimation information obtained from SRS as described above. For example, assuming the channel estimation information is the equivalent channel (or channel estimation matrix) obtained by the first logic unit, and assuming the terminal has C antennas and the first logic unit has K antennas, then the channel estimation matrix between the terminal and the first logic unit can be denoted as H. C×K You can view this H. C×K Perform singular value decomposition to determine the first weight. For example, the first logic unit can assign weights to H. C×K Perform singular value decomposition to obtain Here, matrices U and V are unitary matrices; for example, a unitary matrix multiplied by its own conjugate transpose equals the identity matrix. Matrix V is the SRS weight, i.e., the first weight. Matrix V and matrix V * They are conjugate transposes of each other. Matrix H′ is a diagonal matrix. For the first logic unit, this weight can be used to send the data stream of the corresponding terminal, that is, multiply by matrix V before sending signal x. For the terminal, the received signal can be multiplied by the conjugate matrix U of matrix U. *Assuming the signal received by the terminal is Y, the terminal can multiply Y by matrix U. * Let this be denoted as Y′. Then, Y′=U * Y = U * HVx+U * Q, where Q represents noise. According to It can be obtained It can be seen that the receiving device can perform channel equalization based on the simplified channel H′ to recover the original transmitted signal.

[0231] Of course, the above only provides one possible way to calculate the first weight. In other examples, the zero-forcing precoding method can also be used to determine the first weight. For example, the first weight can be equal to H(H H H) -1 H still represents the channel, and the superscript H indicates the conjugate transpose. This application does not limit the specific implementation of this application.

[0232] In some embodiments, the SRS measurement result mentioned above may include reference signal received power (RSRP). Alternatively, the SRS measurement result may include reference signal received quality (RSRQ). Alternatively, the SRS measurement result may include signal-to-interference-plus-noise ratio (SINR). Alternatively, the SRS measurement result may include signal-to-noise ratio (SNR). Alternatively, the SRS measurement result may include uplink PMI. Alternatively, the SRS measurement result may include uplink RI. Alternatively, the SRS measurement result may include uplink CQI. Alternatively, the SRS measurement result may include uplink timing synchronization.

[0233] In some examples, the SRS measurement results may also include: RSRP and SINR; or, uplink PMI, uplink RI, and uplink CQI; or, RSRP, SINR, uplink PMI, and uplink timing synchronization; or, RSRP, SINR, uplink PMI, uplink RI, and uplink CQI; or, RSRP, SINR, uplink PMI, uplink RI, uplink CQI, and uplink timing synchronization; or, RSRP, RSRQ, SINR, uplink PMI, uplink RI, uplink CQI, and uplink timing synchronization; or, RSRP, RSRQ, SINR, SNR, uplink PMI, uplink RI, uplink CQI, and uplink timing synchronization. It is understood that in other examples, the SRS measurement results may also include any two, three, four, five, six, or seven of the above parameters; for the sake of convenience, these will not be listed individually in the embodiments of this application.

[0234] In some cases, SINR may include SINR before equalization and / or SINR after equalization.

[0235] In some embodiments, the channel estimation information and SRS measurement results obtained by the first logic unit through SRS processing can be at the terminal granularity. That is, for different terminals, the channel estimation information and SRS measurement results corresponding to that terminal can be determined, i.e., the channel estimation information and SRS measurement results between that terminal and the first logic unit (or network device). For example, it can be at the antenna port granularity. That is, for different antenna ports of the terminal, the channel estimation information and SRS measurement results corresponding to that antenna port can be determined, i.e., the channel estimation information and SRS measurement results between that antenna port and the first logic unit (or network device). For another example, it can be at the frequency domain resource granularity. That is, for different frequency domain resources, the channel estimation information and SRS measurement results corresponding to that frequency domain resource can be determined, i.e., the channel estimation information and SRS measurement results between the terminal (or the antenna port of the terminal) and the first logic unit (or network device) on that frequency domain resource. Of course, the above granularity can include one or more, or may include more possible granularities, which will not be discussed in this embodiment.

[0236] For example, at the terminal level, a terminal identifier can be used to indicate the corresponding terminal. Similarly, at the antenna port level, an antenna port identifier can be used to indicate the corresponding antenna port. And at the frequency domain resource level, a frequency domain resource identifier can be used to indicate the corresponding frequency domain resource.

[0237] It is understood that, considering that channel estimation information can be based on terminal granularity, antenna port granularity, or frequency domain resource granularity, the first weight can also be based on terminal granularity, antenna port granularity, or frequency domain resource granularity; this application embodiment does not impose any limitation on these considerations.

[0238] In some examples, the frequency domain resource identifier may include an RE identifier. For example, the frequency domain resource identifier may include a resource element group (REG) identifier. For another example, the frequency domain resource identifier may include a resource block (RB) identifier. For yet another example, the frequency domain resource identifier may include a resource block group (RBG) identifier. For instance, the frequency domain resource identifier may include: an RE identifier and an RB identifier; or, an RE identifier, a REG identifier, and an RB identifier; or, an RE identifier, a REG identifier, an RB identifier, and an RBG identifier. It is understood that in other examples, the frequency domain resource identifier may also include any two or three of the above identifiers; for the sake of convenience, these will not be listed individually in this application.

[0239] In various embodiments of this application, the identifier may be an identity (ID) or an index.

[0240] S102, the second logic unit sends first information to the first logic unit. Correspondingly, the first logic unit receives the first information from the second logic unit.

[0241] For example, the first piece of information can be used to indicate the second weights related to the downward trend of the PMI. For instance, the second weights can also be called PMI weights.

[0242] In some embodiments, the first information may include a second weight, that is, the specific value of the second weight included in the first information can be directly indicated by the first information. For example, in a scenario where the second logic unit is configured to perform the function of calculating the second weight, the second logic unit can determine the second weight, such as by performing operations like codebook recovery and reconstruction based on downlink PMI to obtain the second weight. The second logic unit then carries the specific value of the second weight in the first information and sends the first information to the first logic unit.

[0243] In other embodiments, the first information may include one or more second parameters related to the downlink PMI. These second parameters can be used to determine a second weight, meaning the second logic unit instructs the first logic unit on the second weight through indirect instruction. For example, in a scenario where the first logic unit has the function of calculating the second weight, the second logic unit can send one or more second parameters to the first logic unit so that the first logic unit can determine the second weight based on one or more second parameters in the first information. For instance, the first logic unit may perform operations such as codebook recovery and reconstruction based on the downlink PMI to obtain the second weight.

[0244] The embodiments of this application are applicable to scenarios where the second weight calculation function is deployed in different logical units, thereby flexibly adjusting the method of determining the second weight according to the actual situation and improving communication efficiency.

[0245] In some examples, the second parameter mentioned above can include the downside PMI type. For instance, the downside PMI type can include downside PMI type 1. Or, the downside PMI type can include downside PMI type 2. Or, the downside PMI type can include both downside PMI type 1 and downside PMI type 2.

[0246] For example, the second parameter may include the polarization direction dimension. For another example, the second parameter may include a downlink PMI beam offset identifier. For yet another example, the second parameter may include beam selection and phase adjustment indication parameters. For yet another example, the second parameter may include a downlink PMI beam identifier. For example, the downlink PMI beam identifier may include a downlink PMI horizontal beam identifier. For yet another example, the downlink PMI beam identifier may include a downlink PMI vertical beam identifier. For yet another example, the downlink PMI beam identifier may include both a downlink PMI horizontal beam identifier and an uplink PMI horizontal beam identifier. It is understood that the above beam identifiers may be beam indices.

[0247] The first logic unit can perform operations such as PMI codebook recovery and reconstruction based on one or more of the aforementioned second parameters. For specific implementation details, please refer to the related technologies for PMI codebook recovery and reconstruction; these details will not be elaborated upon in the embodiments of this application.

[0248] This application provides various parameters for determining the second weight, so that appropriate parameters can be used in different scenarios to obtain an accurate second weight and improve communication efficiency.

[0249] It is understood that the second weight can also be based on terminal granularity, antenna port granularity, or frequency domain resource granularity, and this application embodiment does not limit it.

[0250] S103, the second logic unit sends second information to the first logic unit. Correspondingly, the first logic unit receives the second information from the second logic unit.

[0251] For example, the second information can be used to indicate the method for determining the third weight. This third weight can be used for downlink precoding. In some embodiments, downlink precoding can be single-user downlink precoding or multi-user downlink precoding. For example, if the third weight is used for single-user downlink precoding, then the third weight can include the weight of a terminal's data stream on different antenna ports of the network device. As another example, if the third weight is used for multi-user downlink precoding, then the third weight can include the weight of each terminal's data stream on different antenna ports of the network device. Of course, the aforementioned terminal data stream can be a single data stream or multiple data streams; this application does not limit this. In various embodiments of this application, the weight can also be referred to as weight, weight coefficient, weight value coefficient, etc.

[0252] The embodiments of this application are applicable to single-user downlink precoding or multi-user downlink precoding, thus improving universality.

[0253] In some examples, when the downlink precoding is single-user downlink precoding, the method for determining the third weight may include determining the first weight as the third weight. That is, the first weight can be used as the third weight. Alternatively, the method for determining the third weight may include determining the second weight as the third weight. That is, the second weight can be used as the third weight. Or, the method for determining the third weight may include determining the third weight based on the first weight and the second weight. That is, the third weight can be obtained by combining the first weight and the second weight. It is understood that the method for determining the third weight may include any one or more of the above methods, and the embodiments of this application are not limited thereto.

[0254] Among them, SRS weights are more accurate than PMI weights. PMI weights, on the other hand, are more stable, reliable, and have a wider range of applicability and conditions compared to SRS weights. Therefore, for different communication scenarios, SRS weights and / or PMI weights can be selected according to the actual situation to obtain more suitable downlink precoding weights.

[0255] In some examples, the second information may include multiple methods for determining the third weights. For instance, these multiple methods for determining the third weights may be for different granularities, or for different terminals, different antenna ports, and / or different frequency domain resources at the same granularity.

[0256] This application provides multiple methods for determining single-user downlink precoding weights, allowing for flexible selection of appropriate methods to obtain accurate single-user downlink precoding weights for different scenarios.

[0257] For example, when determining a third weight based on a first weight and a second weight, the third weight can be determined by using the first weight, the second weight, and a first parameter. The first parameter can be used to combine the first and second weights. For instance, the first parameter can be one or more coefficients, such as the first weight coefficient and / or the second weight coefficient. In some examples, combining can also be called fusion.

[0258] In some examples, the second information can also be used to indicate the first parameter. Alternatively, the first parameter can be pre-configured in the first logic unit, which is not limited in the embodiments of this application.

[0259] The embodiments of this application can obtain more accurate single-user downlink precoding weights by configuring different weights for the first weight and the second weight.

[0260] In other examples, when downlink precoding is multi-user downlink precoding, the determination of the third weight may include determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals. That is, the multi-user downlink precoding weights corresponding to the multiple terminals can be obtained based on the single-user downlink precoding weights corresponding to each terminal. In the embodiments of this application, the third weight for single-user downlink precoding may also be called the single-user downlink precoding weight, or simply the SU weight, SU weight, etc.; the third weight for multi-user downlink precoding may also be called the multi-user downlink precoding weight, or simply the MU weight, MU weight, etc.

[0261] For example, we can assume that M terminals, denoted as UE 1, ..., UE M, are scheduled on resource block p. The number of data streams scheduled for the m-th UE (i.e., UE m) is denoted as L. m Taking the number of antennas in the first logical unit as K as an example, the SU weight of UE m can be denoted as: One way to determine the MU weights is to concatenate the SU weights of each terminal device to obtain... Where L represents the total number of flows scheduled for M terminals. In various embodiments of this application, the superscript H in the formula represents the conjugate transpose, not the channel. In some examples, the above V' can be... L×K Orthogonalization is performed using the minimum mean square error (MMSE) method to ensure orthogonality between multi-user flows and reduce inter-flow interference. This yields the MU weights for the M terminals, denoted as W. K×L =V' H (V'V' H +Q0I)-1 Where Q0 represents noise power or interference power, and I is the identity matrix.

[0262] This application provides a method for determining multi-user downlink precoding weights to obtain accurate multi-user downlink precoding weights.

[0263] In some embodiments, the second information may further include a first identifier. The first identifier may include a terminal identifier associated with the method for determining the third weight. For example, the terminal identifier may be a terminal ID. The terminal identifier can be used to indicate the terminal corresponding to the method for determining the third weight indicated in the second information. For example, the second information indicates UE 1 and determines the first weight as the third weight. This means that the first weight corresponding to UE 1 can be used as the third weight corresponding to UE 1. As another example, the second information indicates UE 2 and determines the third weight based on the first weight and the second weight. This means that the third weight corresponding to UE 2 can be determined based on the first weight corresponding to UE 2 and the second weight corresponding to UE 2 (and the first parameter corresponding to UE 2).

[0264] In other examples, the first identifier may include an antenna port identifier associated with the method of determining the third weight. For example, the antenna port identifier may be an antenna port ID. This antenna port identifier can be used to indicate the antenna port corresponding to the method of determining the third weight indicated in the second information. For example, the second information indicates antenna port 3 and that the second weight is determined as the third weight. This means that the second weight corresponding to antenna port 3 can be used as the third weight corresponding to antenna port 3. As another example, the second information indicates antenna port 4 and that the third weight is determined based on the first weight and the second weight. This means that the third weight corresponding to antenna port 4 can be determined based on the first weight corresponding to antenna port 4 and the second weight corresponding to antenna port 4 (and the first parameter corresponding to antenna port 4).

[0265] In another example, the first identifier may include a frequency domain resource identifier associated with the method of determining the third weight. For example, the frequency domain resource identifier may be a frequency domain resource ID. This frequency domain resource identifier can be used to indicate the frequency domain resource corresponding to the method of determining the third weight indicated in the second information. For example, the second information indicates frequency domain resource 5 and determines the first weight as the third weight. This means that the first weight corresponding to frequency domain resource 5 can be used as the third weight corresponding to frequency domain resource 5. As another example, the second information indicates frequency domain resource 6 and determines the third weight based on the first weight and the second weight. This means that the third weight corresponding to frequency domain resource 6 can be determined based on the first weight corresponding to frequency domain resource 6 and the second weight corresponding to frequency domain resource 6 (and the first parameter corresponding to frequency domain resource 6).

[0266] In some other examples, the first identifier may also include: a terminal identifier and an antenna port identifier; or, a terminal identifier and a frequency domain resource identifier; or, an antenna port identifier and a frequency domain resource identifier; or, a terminal identifier, an antenna port identifier, and a frequency domain resource identifier.

[0267] The embodiments of this application can indicate the determination method of the third weight at multiple granularities, so as to determine a more accurate third weight and improve communication efficiency.

[0268] In some cases, the second information can be carried by the same signaling as the first information. Alternatively, it can be carried by different signaling; this application does not limit this.

[0269] In the various embodiments of this application, there is no strict order between S101-S103. Some steps may be performed first, followed by others, depending on the actual situation. Alternatively, some steps may be performed simultaneously, and this application does not impose any limitations on this.

[0270] S104, the first logic unit, in response to the method of determining the third weight, determines the third weight based on the first weight and / or the second weight.

[0271] For example, the first logic unit determines the third weight by setting the first weight as the third weight. Then the first logic unit can use the first weight as the third weight. As another example, the first logic unit determines the third weight by setting the second weight as the third weight. Then the first logic unit can use the third weight as the third weight. Yet another example, the third weight is determined based on the first and second weights. Then the first logic unit can determine the third weight based on the first and second weights (and the first parameter). Of course, the specific process of determining the third weight can be found in the description of the corresponding embodiment in S103, and will not be repeated in this application.

[0272] In some examples, after determining the third weight, the first logic unit can determine the weight of each antenna port in the first logic unit based on the third weight, and then use the weight to weight the data signal before transmission. Specific implementation processes can be found in related technologies, and will not be elaborated upon in the embodiments of this application.

[0273] This application embodiment uses the downlink PMI as one of the reference factors for determining the downlink precoding weights. Network devices can flexibly choose the method for determining downlink precoding weights according to the actual situation, thereby improving the accuracy of downlink precoding weights and data transmission efficiency.

[0274] In the communication method provided in this application embodiment, the second logic unit can determine the method for determining the third weight. Therefore, before the second logic unit sends the second information to the first logic unit, the method may further include: the second logic unit acquiring a reference signal measurement result determined based on a reference signal. The second logic unit can determine the method for determining the third weight based on the reference signal measurement result and at least one measurement result threshold.

[0275] In some examples, the reference signal can be a downlink reference signal, such as SRS or downlink DMRS. Then, the first logic unit can send fifth information to the second logic unit. Correspondingly, the second logic unit receives the fifth information from the first logic unit. For example, the fifth information may include reference signal measurement results determined based on the reference signal. For instance, the fifth information may include SRS measurement results and / or downlink DMRS measurement results.

[0276] In other examples, the reference signal can be an uplink reference signal, such as CSI-RS or uplink DMRS. The second logic unit can then measure these uplink reference signals to obtain corresponding measurement results, such as CSI-RS measurement results and / or uplink DMRS measurement results.

[0277] In some embodiments, the second logic unit may be pre-configured with one or more measurement result thresholds. This allows the second logic unit to determine a suitable method for determining the third weight by comparing the reference signal measurement result with the aforementioned one or more measurement result thresholds. For example, the measurement result thresholds may include measurement result threshold 1. If the reference signal measurement result is less than measurement result threshold 1, the method for determining the third weight may be to determine the first weight as the third weight; if the reference signal measurement result is greater than measurement result threshold 1, the method for determining the third weight may be to determine the third weight based on the first weight and the second weight. Of course, for the case where the reference signal measurement result is equal to measurement result threshold 1, the method for determining the third weight may be to determine the first weight as the third weight, or to determine the third weight based on the first weight and the second weight, depending on the actual situation. This embodiment of the application does not impose limitations on this.

[0278] For example, the measurement result thresholds include measurement result threshold 2 and measurement result threshold 3. If the reference signal measurement result is less than measurement result threshold 1, the third weight can be determined by setting the first weight as the third weight; if the reference signal measurement result is greater than measurement result threshold 1 and less than measurement result threshold 2, the third weight can be determined by setting the second weight as the third weight; if the reference signal measurement result is greater than measurement result threshold 2, the third weight can be determined based on the first and second weights. Of course, for the case where the reference signal measurement result is equal to measurement result threshold 1, the third weight can be determined by setting the first weight as the third weight or by setting the second weight as the third weight, depending on the actual situation. For the case where the reference signal measurement result is equal to measurement result threshold 2, the third weight can be determined by setting the second weight as the third weight or by setting the third weight based on the first and second weights, and this embodiment of the application does not limit the determination.

[0279] It is understood that the above is only an exemplary description. The specific relationship between the reference signal measurement result and the threshold, and the method for determining which third weight is used, can be matched with each other according to the actual situation. This application does not limit the specific implementation.

[0280] In some examples, the measurement results for the reference signal can be at the terminal granularity, the antenna port granularity, or the frequency domain resource granularity. Correspondingly, one or more measurement result thresholds can also be at the terminal granularity, the antenna port granularity, or the frequency domain resource granularity. This allows the second logic unit to determine how to determine the third weight corresponding to the appropriate granularity.

[0281] The second logic unit in this embodiment can flexibly select a suitable method for determining the third weight based on the measurement results of the reference signal, so as to determine a more accurate third weight.

[0282] In the communication method provided in the embodiments of this application, the second logic unit can also perform layer 2 scheduling. For example, it determines whether a certain frequency domain resource should be scheduled by SU or MU. Accordingly, for that frequency domain resource, the first logic unit determines whether to use SU weights or MU weights to weight the data signal. In various embodiments of this application, layer 2 scheduling can also be referred to as layer 2 decision-making.

[0283] In some examples, the second logic unit can process the reference signal to obtain channel estimation information and / or reference signal measurement results. For example, the reference signal can be SRS or uplink DMRS. The second logic unit can determine third information based on the channel estimation information and / or reference signal measurement results. For example, the third information may include at least one of the following: a scheduled frequency domain resource identifier, a frequency domain resource scheduling method, and a terminal identifier. The frequency domain resource scheduling method may include SU scheduling, MU scheduling, etc. For SU scheduling, there can be one terminal identifier. For MU scheduling, there can be multiple terminal identifiers.

[0284] For example, the third information may include frequency domain resource identifier A, SU scheduling, and terminal identifier a. Frequency domain resource identifier A indicates frequency domain resource A, and terminal identifier a indicates terminal a. Therefore, the third information could indicate that terminal a is scheduled on frequency domain resource A using SU scheduling. For instance, the first logic unit uses the SU weight corresponding to terminal a to weight the data signal.

[0285] For example, the third information may include frequency domain resource identifier B, MU scheduling, and terminal identifiers b, c, and d. Frequency domain resource identifier B indicates frequency domain resource B, terminal identifier b indicates terminal b, terminal identifier c indicates terminal c, and terminal identifier d indicates terminal d. Therefore, the third information can indicate that terminals b, c, and d are scheduled on frequency domain resource B using MU scheduling. For instance, the first logic unit uses the MU weights corresponding to terminals a, c, and d to weight the data signals.

[0286] The embodiments of this application can flexibly select single-user scheduling or multi-user scheduling, which improves the system flexibility.

[0287] In some examples, the second logic unit can send the aforementioned third information to the first logic unit. Correspondingly, the first logic unit receives the third information from the second logic unit. That is, the second logic unit indicates the scheduling result of layer 2 scheduling to the first logic unit. In this embodiment, the second logic unit can configure more reasonable frequency domain resource scheduling for the first logic unit, improving communication performance.

[0288] In some examples, considering that the second logic unit may not be configured to process the reference signal, the first logic unit may send fifth information to the second logic unit. This fifth information may include channel estimation information determined based on the reference signal and / or reference signal measurement results determined based on the reference signal. For example, if the first logic unit can process the SRS and / or uplink DMRS, then the first logic unit may inform the second logic unit of the channel estimation information determined based on the SRS and / or the reference signal measurement results determined based on the SRS; alternatively, the first logic unit may inform the second logic unit of the channel estimation information determined based on the uplink DMRS and / or the reference signal measurement results determined based on the uplink DMRS.

[0289] The embodiments of this application are applicable to scenarios where the first logic unit has the ability to process reference signals, thereby improving the versatility of the system.

[0290] In some embodiments, the second logic unit, in determining the third information, may also consider the SU weights corresponding to different terminals to better decide whether to perform MU scheduling and / or for which UEs to perform MU scheduling. Therefore, the first logic unit can inform the second logic unit of the SU weights corresponding to the terminals. For example, the first logic unit sends fourth information to the second logic unit. Accordingly, the second logic unit receives the fourth information from the first logic unit. This fourth information can be used to indicate the third weights used for single-user downlink precoding. The second logic unit can determine the aforementioned third information based on the third weights used for single-user downlink precoding, as well as channel estimation information and / or reference signal measurement results.

[0291] For example, if the fourth information indicates the SU weight corresponding to one terminal, the second logic unit can determine, based on the SU weight, channel estimation information, and / or reference signal measurement results, whether to perform SU scheduling on that terminal, and which frequency domain resource to schedule the terminal on. As another example, if the fourth information indicates the SU weight corresponding to multiple terminals, the second logic unit can determine, based on the multiple SU weights, channel estimation information, and / or reference signal measurement results, whether to perform MU scheduling on that terminal, and which frequency domain resource to schedule the multiple terminals on.

[0292] The second logic unit in this embodiment can be combined with the third weight used for single-user downlink precoding to perform more precise layer 2 scheduling, thereby improving resource utilization efficiency and communication performance.

[0293] The above scheme will now be described with more specific examples.

[0294] Figure 11 is a schematic diagram of the functional division of a network device provided in an embodiment of this application.

[0295] Referring to Figure 11, the second logic unit can deploy layer 2 scheduling functions, scrambling functions, and higher-layer communication protocol functions. The first logic unit can deploy SRS A2B mapping functions, SRS channel estimation and SRS measurement functions, SU weight calculation functions, MU weight calculation functions, modulation functions, layer mapping functions, precoding functions, RE mapping functions, and lower-layer communication protocol functions. In some examples, the PMI weight function can be deployed on either the second logic unit or the first logic unit. In various embodiments of this application, the function can also be referred to as a functional module, communication function, communication functional module, communication protocol function, communication protocol functional module, etc.

[0296] Figure 12 is a schematic diagram of another communication method provided by an embodiment of this application.

[0297] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1, 8, and 9, and to the network device function partitioning method shown in Figure 11. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The first and second logical units involved in this application embodiment can be access network devices. The first and second logical units can be deployed on the same access network device or on different access network devices; this application embodiment does not impose any limitations on this. The following embodiment will describe the first logical unit as O-RU and the second logical unit as O-DU. Of course, in other examples, the first logical unit can also be RU, O-DU, or DU, and the second logical unit can also be DU, CU, or O-CU; this application embodiment does not impose any limitations on this. The method may include the following steps:

[0298] S201, the terminal sends an SRS to the O-RU. Correspondingly, the O-RU receives the SRS from the terminal.

[0299] For example, one or more UEs within a cell can send SRS to a network device (such as an O-RU). The network device (such as an O-RU) receives SRS from one or more UEs. In some examples, the network device can schedule different UEs and / or different antenna ports of the same UE to send SRS on different time-frequency resources; it can also instruct UEs to send SRS at corresponding time-frequency locations at a certain period.

[0300] S202, O-RU processes SRS to obtain channel estimation information and SRS measurement results.

[0301] For example, the O-RU performs SRS A2B, SRS channel estimation, and SRS measurement on the SRS. The O-RU converts the received SRS from multiple antenna port dimensions into signals from multiple beam dimensions. Based on the SRS beam signals, the O-RU performs channel estimation and channel measurement to obtain channel estimation information (or channel estimation results) and SRS measurement results.

[0302] S203, the O-RU sends the fifth message to the O-DU. Correspondingly, the O-DU receives the fifth message from the O-RU.

[0303] For example, the O-RU can send fifth information to the O-DU. This fifth information may include one or more channel estimation information and SRS measurement results.

[0304] In some examples, channel estimation information and SRS measurement results can be based on terminal granularity, antenna port granularity, or frequency domain resource granularity. For instance, the fifth piece of information may include one or more UE identifiers and the channel estimation information between the UE and the network device corresponding to that identifier. Another example is that the fifth piece of information may include different antenna port identifiers of the UE and the corresponding channel estimation information between that antenna port and the network device's antenna port. Yet another example is that the fifth piece of information may include different frequency domain resource identifiers and the channel estimation information between the UE's antenna port and the base station's antenna port on that frequency domain resource.

[0305] For example, frequency domain resources can be resource particles, resource particle groups, resource blocks, or resource block groups.

[0306] S204, O-DU determines the method for determining the SU weights based on the SRS measurement results.

[0307] For example, the determination of SU weights can include: using PMI weights as SU weights; using channel estimation information from SRS to calculate weights (referred to as SRS weights) as SU weights; or using a fusion of PMI weights and SRS weights to calculate SU weights (the SU weights obtained after this fusion can also be called SRS and PMI fused weights).

[0308] In some cases, the O-DU can determine which weighting method to use based on the SRS measurement results corresponding to a specific UE, antenna port, or frequency domain resource. For example, the O-DU can determine whether to use the SRS weights as the SU weights, or use a certain weighting method, based on whether the pre-equalization SINR in the SRS measurement results exceeds a preset measurement result threshold. If the pre-equalization SINR is lower than the measurement result threshold, then the O-DU can determine not to use the SRS weights as the SU weights.

[0309] Of course, the above is only an exemplary description. The specific SRS measurement results used and the number of measurement result thresholds used to determine which weighting method is used can be adjusted according to the actual situation. This application embodiment does not limit this.

[0310] S205, the O-DU sends a second message to the O-RU. Correspondingly, the O-RU receives the second message from the O-DU.

[0311] For example, the O-DU can notify the O-RU of the method for determining the SU weight through instruction information (i.e., second information).

[0312] In some examples, the second information may carry the UE ID associated with different weight determination methods. For example, the second information may include: a UE ID using PMI weights as SU weights; and / or, a UE ID using SRS weights as SU weights; and / or, a UE ID using a fusion of PMI and SRS weights.

[0313] For example, the second information may carry the antenna port identifier of the UE associated with different weight determination methods. For instance, the second information may include: antenna port identifiers using PMI weights as SU weights; and / or, antenna port identifiers using SRS weights as SU weights; and / or, antenna port identifiers using a fused PMI and SRS weight.

[0314] For example, the second information may carry frequency domain resource identifiers associated with different weight determination methods. For instance, the second information may include frequency domain resource identifiers using PMI weights as SU weights; and / or, using SRS weights as SU weights; and / or, using frequency domain resource identifiers using a fusion of PMI and SRS weights.

[0315] Optionally, when using SRS and PMI fusion weights, the second information may also include a fusion coefficient (i.e., a first coefficient). This fusion coefficient can be used to superimpose the PMI weights and SRS weights. The fusion coefficient can be indicated by one or more pre-defined indices; for example, an index may be associated with one or a set of coefficients. Alternatively, the fusion coefficient may be associated with the UEID, antenna port identifier, and / or frequency domain resource identifier.

[0316] S206, the O-DU sends the first message to the O-RU. Correspondingly, the O-RU receives the first message from the O-DU.

[0317] In some examples, the first information can be used to indicate the PMI weights related to the downlink PMI. The content indicating the weights can vary depending on the deployment location of the PMI weight calculation function. For example, if the PMI weight calculation function is deployed in the O-DU, the first information can directly indicate the PMI weights. These PMI weights can be considered as obtained from the O-DU based on PMI codebook recovery and reconstruction. As another example, if the PMI weight calculation function is deployed in the O-RU, the first information can include various parameters required for PMI weight calculation, such as: PMI type I, PMI type II, polarization direction dimension, PMI horizontal beam index, PMI vertical beam index, PMI beam offset index, beam selection, and phase adjustment indication information. It is understood that specific related parameters can be referenced from the codebook content for PMI type I and PMI type II in related technologies, and this application embodiment does not limit them.

[0318] In some examples, the first message can also be triggered based on the CSI report submitted by the terminal. In other words, the frequency of sending the first message can be consistent with the frequency of CSI reports submitted by the terminal.

[0319] In some examples, the first and second information can be carried by the same or different signaling. Furthermore, the order of S205 and S206 is not strictly defined. For example, S205 can be executed before S206, or S206 can be executed before S205, or S205 and S206 can be executed simultaneously; this application's embodiments do not impose any limitations.

[0320] S207, O-RU determines the SU weights according to the method for determining SU weights.

[0321] For example, if the O-DU indicates that the SRS weights are used as the SU weights, then the O-RU can calculate the SRS weights based on local channel estimation information and use them as the SU weights. As another example, if the O-DU indicates that the PMI weights are used as the SU weights, then the O-RU can use the PMI weights as the SU weights. Yet another example is if the O-DU indicates that the SU weights are a fusion of PMI and SRS weights (optionally, a fusion coefficient is specified), then the O-RU can superimpose the SRS weights obtained based on channel estimation information and the PMI weights obtained based on PMI recovery and reconstruction (optionally, it can also multiply by a fusion coefficient) to obtain the SU weights.

[0322] It is understandable that the fusion coefficient can be pre-configured or predefined by the protocol, in which case the fusion coefficient does not need to be indicated.

[0323] In some cases, the O-DU indicates terminal identifiers, antenna port identifiers, or frequency domain resource identifiers associated with different weight determination methods. For example, if the weight determination method associated with the terminal identifier, antenna port identifier, or frequency domain resource identifier is SRS weight, then the O-RU can use the channel estimation information corresponding to that terminal identifier, antenna port identifier, or frequency domain resource identifier to calculate the SRS weight, and use that SRS weight as the SU weight. As another example, if the weight determination method associated with the terminal identifier, antenna port identifier, or frequency domain resource identifier is PMI weight, then the O-RU can use the PMI weight corresponding to that terminal identifier, antenna port identifier, or frequency domain resource identifier as the SU weight. Yet another example is if the weight determination method associated with the terminal identifier, antenna port identifier, or frequency domain resource identifier is a fusion of SRS and PMI weights, then the O-RU can fuse the SRS weight and PMI weight corresponding to that terminal identifier, antenna port identifier, or frequency domain resource identifier to obtain the SU weight.

[0324] The aforementioned SU weights may include one or more UE identifiers, and the weighting weights / coefficients of the UE data stream corresponding to those identifiers on different base station antenna ports; or, they may include one or more antenna port identifiers of the UE, and the weighting weights / coefficients of the data stream corresponding to those antenna port identifiers on different base station antenna ports; or, they may include one or more frequency domain resource identifiers, and the weighting weights / coefficients of the UE data stream on those frequency domain resources on different base station antenna ports. For example, the weighting weights / coefficients may include in-phase and quadrature components (IQ).

[0325] S208, the O-RU sends the fourth message to the O-DU. Correspondingly, the O-DU receives the fourth message from the O-RU.

[0326] For example, the fourth information may include one or more SU weights determined in S207.

[0327] S209, O-DU determines the third information based on channel estimation information, SRS measurement results, and SU weights.

[0328] For example, the O-DU can perform Layer 2 scheduling based on the SRS measurement results and channel estimation information obtained in S203, and the SU weights obtained in S208, to determine the user groups scheduled on different frequency domain resources. For example, whether a certain frequency domain resource is scheduled by SU or MU.

[0329] In some examples, the third information may include the result of the layer 2 scheduling determined in S209. For example, the third information may include at least one of the following: the number of scheduled frequency domain resources and the corresponding frequency domain resource identifiers, the number of paired users and user identifiers on each frequency domain resource, the number of streams of the scheduled users and the corresponding stream identifiers on each frequency domain resource, whether each frequency domain resource is SU scheduling (or SU pairing) or MU scheduling (or MU pairing), and the size of each frequency domain resource.

[0330] S210, the O-DU sends third information to the O-RU. Correspondingly, the O-RU receives the third information from the O-DU.

[0331] S211, O-RU determines the MU weights based on the third information.

[0332] For example, if the third information indicates MU scheduling, then the O-RU can obtain the MU weight based on the SU weight and the layer 2 scheduling result in the third information.

[0333] In some examples, the O-RU can apply corresponding SU or MU weights to weight the data of different streams from different UEs on each antenna port for each scheduled frequency domain resource. After processing such as frequency domain transformation to time domain, the data is then sent to the UE via the air interface.

[0334] It is understood that the specific implementation process of each embodiment in S201-S211 above can be referred to the description of the corresponding embodiments in S101-S104, and will not be repeated in the embodiments of this application.

[0335] This application's embodiments consider a communication protocol function partitioning approach where SRS processing, SU weighting, and MU weighting are deployed on the O-RU, and PMI weighting can be deployed on either the O-DU or the O-RU. By dynamically instructing the O-RU on the weighting determination method through the O-DU, the accuracy of the O-RU's weighting calculation is improved, thereby enhancing the efficiency of multi-antenna data transmission over the air interface between the UE and the base station.

[0336] Figure 13 is a schematic diagram of another network device function division provided in an embodiment of this application.

[0337] Figure 13 is similar to Figure 11, except that the second logic unit can also be equipped with SRS channel estimation and SRS measurement functions. In other words, both the first and second logic units are equipped with SRS channel estimation and SRS measurement functions. Accordingly, there is no need for the first and second logic units to exchange channel estimation information and SRS measurement results.

[0338] Figure 14 is a schematic diagram of another communication method provided by an embodiment of this application.

[0339] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1, 8, and 9, and to the network device function partitioning method shown in Figure 13. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The first and second logical units involved in this application embodiment can be access network devices. The first and second logical units can be deployed on the same access network device or on different access network devices; this application embodiment does not impose any limitations on this. The following embodiment will describe the first logical unit as O-RU and the second logical unit as O-DU. Of course, in other examples, the first logical unit can also be RU, O-DU, or DU, and the second logical unit can also be DU, CU, or O-CU; this application embodiment does not impose any limitations on this. The method may include the following steps:

[0340] S301, the terminal sends an SRS to the O-RU. Correspondingly, the O-RU receives the SRS from the terminal.

[0341] It is understood that the implementation process of S301 is similar to that of S201, and will not be described again in the embodiments of this application.

[0342] S302, O-RU performs A2B mapping on SRS to obtain the beam domain signal of SRS.

[0343] The beam domain signal of this SRS is the beam dimension signal (or beam signal) mentioned above. It is understood that the A2B mapping process in S302 is similar to that in S202, and the description of the A2B part in S202 can be referred to. It will not be repeated in the embodiments of this application.

[0344] S303, the O-RU transmits the beam domain signal of the SRS to the O-DU. Correspondingly, the O-DU receives the beam domain signal of the SRS from the O-RU.

[0345] The S304 O-RU processes the beam domain signal of the SRS to obtain channel estimation information and SRS measurement results.

[0346] The S305 O-DU processes the beam domain signal of the SRS to obtain channel estimation information and SRS measurement results.

[0347] It is understood that the channel estimation and SRS measurement processes in S304 and S305 are similar to those in S202, and can be referred to the description of the channel estimation and SRS measurement in S202. The embodiments of this application will not be repeated here.

[0348] S306, O-DU determines the method for determining the SU weights based on the SRS measurement results.

[0349] Understandably, O-DU can determine the SU weighting method based on locally determined channel estimation information and SRS measurement results.

[0350] S307, the O-DU sends a second message to the O-RU. Correspondingly, the O-RU receives the second message from the O-DU.

[0351] S308, the O-DU sends the first message to the O-RU. Correspondingly, the O-RU receives the first message from the O-DU.

[0352] It is understood that the implementation process of S306 is similar to that of S204, the implementation process of S307 is similar to that of S205, and the implementation process of S308 is similar to that of S206. You can refer to the corresponding descriptions in S204-S206. The embodiments of this application will not be repeated.

[0353] S304 can be executed at any time between S305 and S308, or it can be executed before S305 or after S308. Alternatively, S304 and S305 can be executed simultaneously, or S304 and S308 can be executed simultaneously. This application embodiment does not limit the execution of S304.

[0354] S309, O-RU determines the SU weights according to the method for determining SU weights.

[0355] S310, the O-RU sends the fourth message to the O-DU. Correspondingly, the O-DU receives the fourth message from the O-RU.

[0356] S311, O-DU determines the third information based on channel estimation information, SRS measurement results and SU weights.

[0357] For example, the O-DU can refer to local channel estimation information, SRS measurement results, and SU weights informed by the O-RU to perform layer 2 scheduling.

[0358] S312, the O-DU sends third information to the O-RU. Correspondingly, the O-RU receives the third information from the O-DU.

[0359] S313, O-RU determines the MU weights based on the third information.

[0360] It is understood that the implementation process of S309-S313 is similar to that of S207-S211, and the corresponding descriptions in S207-S211 can be referred to. The embodiments of this application will not be repeated here.

[0361] This application embodiment considers a communication protocol function division method where SRS processing, SU weight calculation, and MU weight calculation are located in the O-RU, and the O-DU retains the SRS processing function, and the PMI weight calculation function is located in either the O-DU or the O-RU. By determining the weight determination method based on the local SRS measurement results in the O-DU, the accuracy of the O-RU's weight calculation is improved, thereby enhancing the efficiency of multi-antenna data transmission over the air interface.

[0362] Figure 15 is a schematic diagram of another network device function division provided in an embodiment of this application.

[0363] Figure 15 is similar to Figure 11, except that the second logical unit can also be deployed with SU weight calculation functionality. That is, both the first and second logical units are deployed with SU weight calculation functionality. Correspondingly, there is no need for the first and second logical units to exchange SU weights.

[0364] Figure 16 is a schematic diagram of another communication method provided by an embodiment of this application.

[0365] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1, 8, and 9, and to the network device function partitioning method shown in Figure 15. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The first and second logical units involved in this application embodiment can be access network devices. The first and second logical units can be deployed on the same access network device or on different access network devices; this application embodiment does not impose any limitations on this. The following embodiment will describe the first logical unit as O-RU and the second logical unit as O-DU. Of course, in other examples, the first logical unit can also be RU, O-DU, or DU, and the second logical unit can also be DU, CU, or O-CU; this application embodiment does not impose any limitations on this. The method may include the following steps:

[0366] S401, the terminal sends an SRS to the O-RU. Correspondingly, the O-RU receives the SRS from the terminal.

[0367] S402, O-RU processes SRS to obtain channel estimation information and SRS measurement results.

[0368] S403, the O-RU sends the fifth message to the O-DU. Correspondingly, the O-DU receives the fifth message from the O-RU.

[0369] S404, O-DU determines the method for determining the SU weights based on the SRS measurement results.

[0370] S405, the O-DU sends a second message to the O-RU. Correspondingly, the O-RU receives the second message from the O-DU.

[0371] S406, the O-DU sends the first message to the O-RU. Correspondingly, the O-RU receives the first message from the O-DU.

[0372] S407, O-RU determines the SU weights according to the method for determining SU weights.

[0373] It is understood that the implementation process of S401-S407 is similar to that of S201-S207, and the corresponding descriptions in S201-S207 can be referred to. The embodiments of this application will not be repeated here.

[0374] S408, O-DU determines the SU weight based on the method for determining the SU weight.

[0375] It is understood that the implementation process of S408 is similar to that of S207, and the corresponding description in S207 can be referred to. The embodiments of this application will not be repeated here.

[0376] S409, O-DU determines the third information based on channel estimation information, SRS measurement results, and SU weights.

[0377] For example, the O-DU performs layer 2 scheduling based on the channel estimation information provided by the O-RU, the SRS measurement results, and the locally determined SU weights.

[0378] S410, the O-DU sends third information to the O-RU. Correspondingly, the O-RU receives the third information from the O-DU.

[0379] S411, O-RU determines the MU weights based on the third information.

[0380] It is understood that the implementation process of S409-S411 is similar to that of S209-S211, and the corresponding descriptions in S209-S211 can be referred to. The embodiments of this application will not be repeated here.

[0381] Of course, S407 can be executed at any time between S408 and S410, or it can be executed before S408 or after S410. Alternatively, S407 and S408 can be executed simultaneously, or S407 and S410 can be executed simultaneously. This application embodiment does not limit the execution of S407.

[0382] This application embodiment considers a communication protocol function division method where SRS processing, SU weight calculation, and MU weight calculation are located in the O-RU, the O-DU retains the SU weight calculation function, and the PMI weight calculation is located in either the O-DU or the O-RU. By determining the weight determination method based on the SRS measurement results reported from the O-RU by the O-DU, the accuracy of the O-RU weights is improved, and the efficiency of air interface data transmission is enhanced.

[0383] Figure 17 is a schematic diagram of another network device function division provided in an embodiment of this application.

[0384] Figure 17 is similar to Figure 11, except that the second logical unit can also be equipped with SRS channel estimation and SRS measurement functions, as well as SU weight calculation functions. In other words, both the first and second logical units are equipped with SRS channel estimation and SRS measurement functions, and SU weight calculation functions. Accordingly, there is no need for the first and second logical units to exchange channel estimation information, SRS measurement results, and SU weights.

[0385] Figure 18 is a schematic diagram of another communication method provided by an embodiment of this application.

[0386] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1, 8, and 9, and to the network device function partitioning method shown in Figure 18. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The first and second logical units involved in this application embodiment can be access network devices. The first and second logical units can be deployed on the same access network device or on different access network devices; this application embodiment does not impose any limitations on this. The following embodiment will describe the first logical unit as O-RU and the second logical unit as O-DU. Of course, in other examples, the first logical unit can also be RU, O-DU, or DU, and the second logical unit can also be DU, CU, or O-CU; this application embodiment does not impose any limitations on this. The method may include the following steps:

[0387] S501, the terminal sends an SRS to the O-RU. Correspondingly, the O-RU receives the SRS from the terminal.

[0388] S502, O-RU performs A2B mapping on SRS to obtain the beam domain signal of SRS.

[0389] S503, the O-RU sends the beam domain signal of the SRS to the O-DU. Correspondingly, the O-DU receives the beam domain signal of the SRS from the O-RU.

[0390] In some embodiments, the O-DU can also deploy an SRS A2B mapping function. Then the O-RU can forward the received SRS to the O-DU. In this case, S503 may not be executed, and the O-DU performs A2B mapping on the SRS to obtain the beam domain signal of the SRS. This process is similar to S502.

[0391] The S504 O-RU processes the beam domain signal of the SRS to obtain channel estimation information and SRS measurement results.

[0392] The S505 O-DU processes the beam domain signal of the SRS to obtain channel estimation information and SRS measurement results.

[0393] S506, O-DU determines the method for determining the SU weights based on the SRS measurement results.

[0394] S507, the O-DU sends a second message to the O-RU. Correspondingly, the O-RU receives the second message from the O-DU.

[0395] S508, the O-DU sends the first message to the O-RU. Correspondingly, the O-RU receives the first message from the O-DU.

[0396] It is understood that the implementation process of S501-S508 is similar to that of S301-S308, and will not be described again in the embodiments of this application.

[0397] S509, O-RU determines the SU weights according to the method for determining SU weights.

[0398] S510, O-DU determines the SU weight based on the method for determining the SU weight.

[0399] S511, O-DU determines the third information based on channel estimation information, SRS measurement results and SU weights.

[0400] S512, the O-DU sends third information to the O-RU. Correspondingly, the O-RU receives the third information from the O-DU.

[0401] S513, O-RU determines the MU weights based on the third information.

[0402] It is understood that the implementation process of S509-S513 is similar to that of S407-S411, and will not be described again in the embodiments of this application.

[0403] This application's embodiments consider communication protocol function partitioning methods where SRS processing, SU weight calculation, and MU weight calculation are located in the O-RU, and the O-DU retains the SRS processing and SU weight calculation functions, while PMI weight calculation is located in either the O-DU or O-RU. By determining the weights based on local SRS measurement results from the O-DU, the accuracy of O-RU weights is improved, thus enhancing air interface data transmission efficiency.

[0404] In the embodiments described in Figures 11 to 18, the information exchanged between the O-DU and O-RU can also be carried in separate control plane signaling (such as O-RAN control plane messages) or separate management plane signaling (such as O-RAN management plane messages).

[0405] It is understood that each of the above embodiments of this application can be implemented independently or in combination with each other; there is no absolute subordinate relationship between the embodiments, and they can be combined with each other under any conditions to obtain the corresponding effect.

[0406] It is understood that, in order to achieve the functions in the above embodiments, the network device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0407] Figures 19 and 20 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first or second logic unit in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the RAN node 110 shown in Figure 1, wherein the RAN node can also be called an access network device or a network device. The communication device can also be a module (such as a chip) applied to the network device.

[0408] In this embodiment of the application, the device for implementing the function of the network device can be the network device itself, or it can be a device that enables the network device to implement the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0409] In this embodiment of the application, the chip system may be composed of chips, or it may include chips and other discrete devices.

[0410] As shown in Figure 19, the communication device 1900 includes a processing unit 1910 and a transceiver unit 1920. The communication device 1900 is used to implement the functions of the first logic unit and the second logic unit in the method embodiments shown in Figures 10, 12, 14, 16, and 18.

[0411] When the communication device 1900 is used to implement the function of the first logic unit in the method embodiment shown in FIG10: the processing unit 1910 is used to acquire a first weight. The transceiver unit 1920 is used to receive first information. The transceiver unit 1920 is also used to receive second information. The processing unit 1910 is also used to determine a third weight based on the first weight and / or the second weight, in response to the method of determining the third weight.

[0412] When the communication device 1900 is used to implement the function of the second logic unit in the method embodiment shown in FIG10: the transceiver unit 1920 is used to send first information. The transceiver unit 1920 is also used to send second information. The processing unit 1910 is used to execute any processing function in the second logic unit other than sending and receiving.

[0413] For a more detailed description of the processing unit 1910 and the transceiver unit 1920, please refer to the relevant description of the method embodiments shown in Figures 10, 12, 14, 16, and 18.

[0414] As shown in Figure 20, the communication device 2000 includes a processor 2010 and an interface circuit 2020. The processor 2010 and the interface circuit 2020 are coupled together. It is understood that the interface circuit 2020 can be a transceiver or an input / output interface. Optionally, the communication device 2000 may also include a memory 2030 for storing instructions executed by the processor 2010, or storing input data required by the processor 2010 to execute instructions, or storing data generated after the processor 2010 executes instructions. Sometimes, the interface circuit 2020 can also be understood as part of the processor 2010, in which case the communication device 2000 includes the processor 2010.

[0415] When the communication device 2000 is used to implement the methods shown in Figures 10, 12, 14, 16, and 18, the processor 2010 is used to implement the functions of the processing unit 1910, and the interface circuit 2020 is used to implement the functions of the transceiver unit 1920.

[0416] When the aforementioned communication device is a chip applied to an access network device, the access network device chip implements the functions of the access network device in the above method embodiments. The access network device chip receives information from a terminal or core network device, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the access network device, and then sent to the access network device chip by these modules. The access network device chip sends information to a terminal or core network device, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the terminal or core network device, and then sent back to the terminal or core network device by these modules.

[0417] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0418] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or one or more of other general-purpose processors, digital signal processors (DSPs), microprocessor units (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), artificial intelligence processors (AI processors), or neural processing units (NPUs); or, the processor mentioned in the embodiments of this application can be application-specific integrated circuits (ASICs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components (or parts), or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor, etc.

[0419] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in memory, such as volatile memory and / or non-volatile memory. The non-volatile memory can be flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM). The volatile memory can be a cache or random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes a variety of forms, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). The memory can also be in registers, hard disks, portable hard disks, compact disc (CD) ROMs, or any other form of storage medium well known in the art.

[0420] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0421] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0422] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0423] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0424] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0425] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0426] The terms "first" and "second," etc., used in the specification and drawings of the embodiments of this application are used to distinguish different objects or to distinguish different processing of the same object. The terms "first" and "second," etc., can distinguish identical or similar items with substantially the same function and effect. For example, "first device" and "second device" are merely to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first" and "second," etc., do not limit the quantity or execution order, and that "first" and "second," etc., do not necessarily imply that they are different.

[0427] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of the embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0428] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0429] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of the embodiments of this application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of the embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0430] It is understood that in the embodiments of this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a time, nor do they require a judgment action during implementation, nor do they imply any other limitations.

[0431] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0432] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined to form new embodiments, implementation methods, methods, or implementation approaches based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: Obtain a first weight, wherein the first weight is determined based on the detection reference signal SRS; Receive first information, the first information being used to indicate a second weight related to the downlink precoding matrix indication PMI; Receive second information, the second information being used to indicate the method for determining the third weight, the third weight being used for downlink precoding; In response to the method of determining the third weight, the third weight is determined based on the first weight and / or the second weight.

2. The method according to claim 1, characterized in that, The downlink precoding is single-user downlink precoding, and the third weight includes weight information of a terminal's data stream on different antenna ports of the network device; or, The downlink precoding is multi-user downlink precoding, and the third weight includes the weight information of the data streams of each terminal in the network device on different antenna ports.

3. The method according to claim 2, characterized in that, The downlink precoding is single-user downlink precoding, and the determination of the third weight can be any of the following methods: The first weight is determined as the third weight; The second weight is determined as the third weight; or, The third weight is determined based on the first weight and the second weight.

4. The method according to claim 3, characterized in that, Determining the third weight based on the first weight and the second weight includes: The third weight is determined based on the first weight, the second weight, and the first parameter, wherein the first parameter is used to combine the first weight and the second weight.

5. The method according to claim 2, characterized in that, The downlink precoding is multi-user downlink precoding, and the method for determining the third weight includes: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

6. The method according to any one of claims 1-5, characterized in that, The second information includes a first identifier; determining the third weight based on the first weight and / or the second weight includes: The third weight corresponding to the first identifier is determined based on the first weight corresponding to the first identifier and / or the second weight corresponding to the first identifier; The first identifier includes at least one of the following identifiers: The terminal identifier associated with the method for determining the third weight; Antenna port identifier associated with the method for determining the third weight; or, Frequency domain resource identifier associated with the method of determining the third weight.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive third information, which includes at least one of the following: frequency domain resource identifier, frequency domain resource scheduling method, and terminal identifier.

8. The method according to claim 7, characterized in that, The frequency domain resource scheduling method is single-user scheduling, and the terminal identifier is one; or, the frequency domain resource scheduling method is multi-single-user scheduling, and the terminal identifier is multiple.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: A fourth message is sent, which indicates the third weight used for single-user downlink precoding.

10. The method according to any one of claims 1-9, characterized in that, Before receiving the second information, the method further includes: Send a fifth message, which includes channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal, wherein the reference signal includes the SRS.

11. The method according to any one of claims 1-10, characterized in that, The first information includes the second weight; or, the first information includes one or more second parameters related to the downlink PMI, wherein the second weight is determined based on the one or more second parameters related to the downlink PMI.

12. The method according to claim 11, characterized in that, The second parameter includes at least one of the following parameters: Downward PMI type; Polarization direction dimension; Downlink PMI beam indicator; Downlink PMI beam offset indicator; or, Beam selection and phase adjustment indication parameters.

13. A communication method, characterized in that, The method includes: Send a first message, which is used to indicate a second weight related to the downlink precoding matrix indication PMI; Send a second message, the second message being used to indicate the method for determining a third weight, the third weight being used for downlink precoding, wherein the third weight is determined in response to the method for determining the third weight, based on a first weight and / or a second weight, the first weight being determined based on a sounding reference signal (SRS).

14. The method according to claim 13, characterized in that, The downlink precoding is single-user downlink precoding, and the third weight includes weight information of a terminal's data stream on different antenna ports of the network device; or, The downlink precoding is multi-user downlink precoding, and the third weight includes the weight information of the data streams of each terminal in the network device on different antenna ports.

15. The method according to claim 14, characterized in that, The downlink precoding is single-user downlink precoding, and the determination of the third weight can be any of the following methods: The first weight is determined as the third weight; The second weight is determined as the third weight; or, The third weight is determined based on the first weight and the second weight.

16. The method according to claim 15, characterized in that, Determining the third weight based on the first weight and the second weight includes: The third weight is determined based on the first weight, the second weight, and the first parameter, wherein the first parameter is used to combine the first weight and the second weight.

17. The method according to claim 14, characterized in that, The downlink precoding is multi-user downlink precoding, and the method for determining the third weight includes: determining the third weight for multi-user downlink precoding based on the third weights for single-user downlink precoding corresponding to each of the multiple terminals.

18. The method according to any one of claims 13-17, characterized in that, The second information includes a first identifier, wherein the third weight corresponding to the first identifier is determined in response to the method of determining the third weight, based on the first weight corresponding to the first identifier and / or the second weight corresponding to the first identifier; The first identifier includes at least one of the following identifiers: The terminal identifier associated with the method for determining the third weight; Antenna port identifier associated with the method for determining the third weight; or, Frequency domain resource identifier associated with the method of determining the third weight.

19. The method according to any one of claims 13-18, characterized in that, Before sending the second information, the method further includes: Obtain the measurement results of the reference signal determined based on the reference signal; The method for determining the third weight is determined based on the measurement results of the reference signal and at least one measurement result threshold.

20. The method according to any one of claims 13-19, characterized in that, The method further includes: Send a third piece of information, which includes at least one of the following: the frequency domain resource identifier, the frequency domain resource scheduling method, and the terminal identifier.

21. The method according to claim 20, characterized in that, The frequency domain resource scheduling method is single-user scheduling, and the terminal identifier is one; or, the frequency domain resource scheduling method is multi-single-user scheduling, and the terminal identifier is multiple.

22. The method according to claim 20 or 21, characterized in that, Before sending the third information, the method further includes: Receive fifth information, the fifth information including channel estimation information determined based on a reference signal and / or reference signal measurement results determined based on the reference signal, wherein the reference signal includes the SRS; The third information is determined based on the channel estimation information and / or the reference signal measurement results.

23. The method according to claim 22, characterized in that, The method further includes: Receive fourth information, the fourth information being used to indicate the third weight for single-user downlink precoding; Determining the third information based on the channel estimation information and / or the reference signal measurement results includes: The third information is determined based on the third weights used for single-user downlink precoding, the channel estimation information, and / or the reference signal measurement results.

24. The method according to any one of claims 13-23, characterized in that, The first information includes the second weight; or, the first information includes one or more second parameters related to the downlink PMI, wherein the second weight is determined based on the one or more second parameters related to the downlink PMI.

25. The method according to claim 24, characterized in that, The second parameter includes at least one of the following parameters: Downward PMI type; Polarization direction dimension; Downlink PMI beam indicator; Downlink PMI beam offset indicator; or, Beam selection and phase adjustment indication parameters.

26. A communication device, characterized in that, Includes a module for performing the method according to any one of claims 1-25.

27. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1-25 through logic circuits and / or executing code instructions.

28. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-25.

29. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1-25.

Images