Patent Description:
This application relates to the field of communications technologies, and in particular, to a resource configuration method and a device.

In a multiple input multiple output (English: Multiple Input Multiple Output, MIMO for short) system, PRB bundling is a technology used to improve channel estimation performance. According to a technical solution of PRB bundling, sizes (size) of contiguous PRBs (Physical resource block) using a same preprocessing manner (including beamforming and precoding) are agreed, and the size is usually greater than <NUM>, so that a terminal performs joint channel estimation by using a plurality of PRBs. When the terminal performs joint channel estimation based on a plurality of PRBs, extrapolation calculations of channel estimation can be reduced. During channel estimation, a channel estimation value obtained through an extrapolation calculation has a relatively large deviation. Therefore, channel estimation accuracy can be improved by reducing extrapolation calculations (by converting an extrapolation calculation into an interpolation calculation).

From a perspective of channel estimation, a larger PRB bundling size leads to higher channel estimation accuracy. However, when the PRB bundling size is increased to a particular value, a channel estimation accuracy gain no longer increases. Therefore, the PRB bundling size does not need to increase infinitely, but only needs a limited quantity of values to be defined. The channel estimation accuracy gain brought by an increase in the PRB bundling size is also related to a channel environment. For example, a flatter frequency domain channel leads to a smaller channel estimation extrapolation loss. In such a scenario, the channel estimation accuracy gain brought by the increase the PRB bundling size is limited.

In addition, a larger PRB bundling size leads to more complex channel estimation. Therefore, from a perspective of terminal implementation complexity, only a limited quantity of values can be defined for the PRB bundling size.

In addition to a PRB bundling size, other LTE frequency domain sizes such as a resource scheduling frequency domain size, a precoding frequency domain size, and a channel state information feedback frequency domain size have the same problem. For example, a mapping manner of binding to system bandwidth is not flexible enough, and often limits DMRS estimation performance. For example, for channels in different scenarios, channel characteristics cannot be well summarized by using only the system bandwidth. For example, in <NUM> and <NUM> carrier frequency scenarios, frequency selectivity corresponding to same system bandwidth differs greatly, and corresponding bundling sizes for obtaining optimal estimation performance also differ greatly. The document Huawei at all: "PRB bundling size for DL data precoding", R1-<NUM> is a standardization document regarding the bundling size of resources in a communication system.

To flexibly configure a resource bundling size to effectively optimize system performance in different scenario conditions, embodiments of this application provide a resource configuration method and corresponding apparatuses according to the appended claims.

Beneficial effects brought by the technical solutions provided in the embodiments of this application are as follows:.

According to the resource configuration method, the transmit end device, and the receive end device that are provided in the embodiments of this application, the transmit end device generates resource configuration information, and the receive end device may determine a resource bundling size based on the resource configuration information. Compared with the prior art in which a resource size is bound only to system bandwidth, the technical solutions provided in the embodiments of this application can flexibly determine a proper resource bundling size from a resource bundling size set based on at least one system configuration parameter, to adapt to different application scenarios. Therefore, by using the technical solutions provided in the embodiments of this application, a requirement of a wireless communications system for diversified scenarios can be met, and system performance can be effectively optimized in different scenarios.

To describe the technical solutions in the embodiments of this application more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of this application, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

According to technical solutions provided in embodiments of this application, resource configuration information is sent, and a receive end can determine a resource bundling size based on the resource configuration information. Compared with the prior art in which a resource size is bound only to system bandwidth, the technical solutions provided in the embodiments of this application can flexibly determine a proper resource bundling size from a resource bundling size set based on at least one system configuration parameter, to adapt to different application scenarios. Therefore, by using the technical solutions provided in the embodiments of this application, a requirement of a wireless communications system for diversified scenarios can be met, and system performance can be effectively optimized in different scenarios.

The technical solutions provided in the embodiments of this application are described below in detail with reference to corresponding accompanying drawings.

<FIG> is a schematic diagram of an example of a wireless communications network <NUM> according to an embodiment of this application. As shown in <FIG>, the wireless communications network <NUM> includes base stations <NUM> to <NUM> and terminal devices <NUM> to <NUM>. The base stations <NUM> to <NUM> may communicate with each other by using backhaul (backhaul) links (shown by straight lines between the base stations <NUM> to <NUM>). The backhaul link may be a wired backhaul link (for example, an optical fiber or a copper cable), or may be a wireless backhaul link (for example, microwave). The terminal devices <NUM> to <NUM> may communicate with the corresponding base stations <NUM> to <NUM> by using radio links (shown by polygonal lines between the base stations <NUM> to <NUM> and the terminal devices <NUM> to <NUM>).

The base stations <NUM> to <NUM> are configured to provide a wireless access service for the terminal devices <NUM> to <NUM>. Specifically, each base station corresponds to one service coverage area (which may also be referred to as a cell, and is shown by each elliptical area in <FIG>). A terminal device entering the area may communicate with the base station by using a radio signal, to receive the wireless access service provided by the base station. Service coverage areas of the base stations may overlap, and a terminal device in an overlapping area may receive radio signals from a plurality of base stations. Therefore, the plurality of base stations may simultaneously serve the terminal device. For example, the plurality of base stations may serve the terminal device in the overlapping area by using a coordinated multipoint (Coordinated multipoint, CoMP) technology. For example, as shown in <FIG>, service coverage areas of the base station <NUM> and the base station <NUM> overlap, and the terminal device <NUM> is in the overlapping area. Therefore, the terminal device <NUM> may receive radio signals from the base station <NUM> and the base station <NUM>, and the base station <NUM> and the base station <NUM> may simultaneously serve the terminal device <NUM>. For another example, as shown in <FIG>, service coverage areas of the base station <NUM>, the base station <NUM>, and the base station <NUM> have a common overlapping area, and the terminal device <NUM> is in the overlapping area. Therefore, the terminal device <NUM> may receive radio signals from the base station <NUM>, the base station <NUM>, and the base station <NUM>, and the base station <NUM>, the base station <NUM>, and the base station <NUM> may simultaneously serve the terminal device <NUM>.

Depending on a to-be-used wireless communications technology, the base station may also be referred to as a NodeB (NodeB), an evolved NodeB (evolved NodeB, eNodeB), an access point (Access Point, AP), or the like. In addition, based on sizes of provided service coverage areas, the base stations may be divided into a macro base station configured to provide a macro cell (Macro cell), a micro base station configured to provide a micro cell (Pico cell), and a femto base station configured to provide a femto cell (Femto cell). With continuous evolution of wireless communications technologies, a future base station may have another name.

The terminal devices <NUM> to <NUM> may be various wireless communications devices having a wireless communication function, for example but not limited to, a mobile cellular phone, a cordless telephone set, a personal digital assistant (Personal Digital Assistant, PDA), a smartphone, a notebook computer, a tablet computer, a wireless data card, a wireless modem (Modulator-demodulator, Modem), or a wearable device such as a smartwatch. With rise of the Internet of Things (Internet of Things, IOT) technology, a growing quantity of devices that previously do not have a communication function, for example but not limited to, household appliances, vehicles, tools, service devices, and service facilities, begin to obtain the wireless communication function by configuring a wireless communications unit, so that they access a wireless communications network and are remotely controlled. Such devices have the wireless communication function because they are configured with the wireless communications unit, and therefore also fall within a scope of wireless communications devices. In addition, the terminal devices <NUM> to <NUM> each may also be referred to as a mobile station, a mobile device, a mobile terminal, a wireless terminal, a handheld device, a client, or the like.

The base stations <NUM> to <NUM> and the terminal devices <NUM> to <NUM> may be all configured with a plurality of antennas, to support a MIMO (multiple input multiple output, Multiple Input Multiple Output) technology. Further, the terminal devices <NUM> to <NUM> may support a single-user MIMO (Single-User MIMO, SU-MIMO) technology, and may also support multi-user MIMO (Multi-User MIMO, MU-MIMO). The MU-MIMO may be implemented based on a space division multiple access (Space Division Multiple Access, SDMA) technology. Because being configured with the plurality of antennas, the base stations <NUM> to <NUM> and the terminal devices <NUM> to <NUM> may further flexibly support a single input single output (Single Input Single Output, SISO) technology, a single input multiple output (Single Input Multiple Output, SIMO) technology, and a multiple input single output (Multiple Input Single Output, MISO) technology, to implement various diversity (for example but not limited to, transmit diversity and receive diversity) and multiplexing technologies. The diversity technology may include, for example but not limited to, a transmit diversity (Transmit Diversity, TD) technology and a receive diversity (Receive Diversity, RD) technology. The multiplexing technology may be a spatial multiplexing (Spatial Multiplexing) technology. Furthermore, the foregoing technologies may further include a plurality of implementation schemes. For example, currently frequently used transmit diversity may include diversity manners, for example but not limited to, space-time transmit diversity (Space-Time Transmit Diversity, STTD), space-frequency transmit diversity (Space-Frequency Transmit Diversity, SFTD), time switched transmit diversity (Time Switched Transmit Diversity, TSTD), frequency switched transmit diversity (Frequency Switch Transmit Diversity, FSTD), orthogonal transmit diversity (Orthogonal Transmit Diversity, OTD), and cyclic delay diversity (Cyclic Delay Diversity, CDD), and diversity manners obtained after derivation, evolution, and combination of the foregoing diversity manners. For example, in a current LTE (Long Term Evolution, Long Term Evolution) standard, transmit diversity manners such as space time block coding (Space Time Block Coding, STBC), space frequency block coding (Space Frequency Block Coding, SFBC), and the CDD are used.

In addition, the base station <NUM> may communicate with the terminal devices <NUM> to <NUM> by using various wireless communications technologies, for example but not limited to, a time division multiple access (Time Division Multiple Access, TDMA) technology, a frequency division multiple access (Frequency Division Multiple Access, FDMA) technology, a code division multiple access (Code Division Multiple Access, CDMA) technology, a time division-synchronous code division multiple access (Time Division-Synchronous Code Division Multiple Access, TD-SCDMA) technology, an orthogonal frequency division multiple access (Orthogonal FDMA, OFDMA) technology, a single carrier frequency division multiple access (Single Carrier FDMA, SC-FDMA) technology, a space division multiple access (Space Division Multiple Access, SDMA) technology, and technologies evolved and derived from these technologies. The foregoing wireless communications technologies are adopted as a radio access technology (Radio Access Technology, RAT) in numerous wireless communications standards, to construct various wireless communications systems (or networks) nowadays widely known to people, including but not limited to, a Global System for Mobile Communications (Global System for Mobile Communications, GSM), CDMA2000, Wideband CDMA (Wideband CDMA, WCDMA), Wi-Fi defined in the <NUM> series standard, Worldwide Interoperability for Microwave Access (Worldwide Interoperability for Microwave Access, WiMAX), Long Term Evolution (Long Term Evolution, LTE), LTE-Advanced (LTE-Advanced, LTE-A), systems evolved from these wireless communications systems, and the like. The wireless communications network shown in <FIG> may be any system or network in the foregoing wireless communications systems. Unless otherwise stated, the technical solutions provided in the embodiments of this application may be applied to the foregoing wireless communications technologies and wireless communications systems. In addition, the terms "system" and "network" can be interchangeable.

It should be noted that the wireless communications network <NUM> shown in <FIG> is only an example, and is not intended to limit the technical solutions of this application. A person skilled in the art should understand that in a specific implementation process, the wireless communications network <NUM> further includes another device, for example but not limited to, a base station controller (Base Station Controller, BSC), and quantities of base stations and terminal devices may be configured based on a specific need.

In an existing LTE system, a resource size is determined based only on system bandwidth. In other words, in the existing LTE, the resource size is bound or mapped only to the system bandwidth. A configuration manner is undiversified, and there is only one resource bundling size. Consequently, it is not flexible, and it is difficult to optimize system performance in different scenario conditions.

For example, scenario conditions of a high frequency system and a low frequency system differ greatly. The high frequency system has a quite high carrier frequency with relatively small coverage, and uses a narrow beam with very small multipath delay spread, and a frequency domain channel of the high frequency system is much flatter than that of a low frequency scenario. If a same resource bundling size configuration is used for a high frequency system and a low frequency system without considering the differences, it is difficult for the two to both achieve relatively desirable performance.

For another example, compared with when there is no direct path between a terminal and a network device, when there is a direct path between the terminal and the network device, a frequency domain channel is flatter with smaller multipath delay spread. Channel conditions of an indoor terminal and an outdoor terminal also differ greatly. If a same resource size configuration is used for all terminals at all time without considering the differences, it is difficult to take account of different terminal channel conditions.

Therefore, this application designs a resource bundling size set (resource bundling size set). The set includes at least one resource bundling size (resource bundling size). According to the technical solutions provided in the embodiments of this application, a proper resource bundling size can be flexibly determined from a resource bundling size set, to adapt to different application scenarios. It should be understood that the resource bundling size described in the embodiments of this application may also be referred to as a resource bundling granularity.

The following describes in detail an implementation process of a resource configuration method provided in this application.

<FIG> is a flowchart of an example of a resource configuration method <NUM> according to an embodiment of this application. In a specific implementation process, a transmit end device may be, for example but not limited to, the terminal devices <NUM> to <NUM> or the base stations <NUM> to <NUM> in <FIG>; a receive end device may be, for example but not limited to, the base stations <NUM> to <NUM> or the terminal devices <NUM> to <NUM> in <FIG>. It should be understood that the base stations <NUM> to <NUM> and the terminal devices <NUM> to <NUM> are peer devices respectively at a transmit end and at a receive end.

Step <NUM>: The transmit end device generates configuration information, where the configuration information is used to indicate at least one resource bundling size, the resource bundling size belongs to a resource bundling size set, and the resource bundling size set corresponds to at least one system configuration parameter. The resource bundling size may also be referred to as a resource group size; and the resource bundling size set may also be referred to as a resource group size set or is briefly referred to as a resource bundling set or a resource group set.

Step <NUM>: The transmit end device sends the configuration information.

Step <NUM>: The receive end device receives the configuration information.

Step <NUM>: The receive end device determines a resource bundling size based on the configuration information.

In the method <NUM>, the configuration information generated by the transmit end device is used to indicate a resource bundling size set that includes at least one resource bundling size, and one or more resource bundling size sets may be configured to adapt to different service scenarios.

In a possible implementation, the resource bundling size set includes a resource bundling size corresponding to a user configuration parameter, and the user configuration parameter includes: scheduling bandwidth for a terminal, or minimum continuous scheduling bandwidth for the terminal, or a divisor of continuous scheduling bandwidth for the terminal. The resource bundling size corresponding to the user configuration parameter may be a status variable. For example, the status variable instructs a target terminal to use entire or partial scheduling bandwidth. For example, in a current scheduling process, <NUM> physical resource blocks (Physical Resource Block, PRB) are scheduled for the terminal, and when a parameter is indicated, a size is <NUM> PRBs; or <NUM> PRBs are scheduled for the terminal in a scheduling process, and when another parameter is indicated, a size is <NUM> PRBs.

In this embodiment of this application, the resource bundling size set corresponds to at least one system configuration parameter, and the system configuration parameter may be a system radio carrier frequency parameter, a system bandwidth parameter, a system subcarrier spacing parameter, a service scenario parameter, or a transmission scheme parameter; and a resource bundling size in the resource bundling size set may be at least one of a resource scheduling frequency domain size, a physical resource block bundling size, a precoding frequency domain size, and a channel state information CSI feedback frequency domain size.

In this way, a resource bundling size is not only related to system bandwidth, but also may correspond to another system configuration parameter. Furthermore, the resource bundling size may be used to determine a physical resource block frequency domain size, a resource scheduling frequency domain size, a precoding frequency domain size, a CSI feedback frequency domain size, and a transmission scheme frequency domain sizes. This is flexible and diverse, and adapts to different scenario changes.

Correspondingly, the configuration information may be resource scheduling configuration information, or physical resource block configuration information, or precoding configuration information, or channel state information feedback configuration information, or transmission scheme configuration information.

In a specific implementation process, in step <NUM>, the transmit end device sends the configuration information.

In this embodiment of this application, the transmit end device may explicitly or implicitly send the resource bundling size.

In one aspect, if the transmit end device does not send explicit signaling to the receive end device for indication, the receive end device uses, by default, a resource bundling size in a resource bundling size set corresponding to a system parameter, for example, the first or the last resource bundling size.

In another aspect, the transmit end device may alternatively send a resource bundling size in a particular resource bundling set to the receive end device by using the configuration information.

In both of the foregoing two manners, after receiving the configuration information, the receive end device may obtain a corresponding resource bundling size, and may perform a corresponding operation based on the resource bundling size, for example, perform resource scheduling, or precoding, or channel estimation, or data demodulation.

Sending the configuration information by using explicit signaling may be sending the configuration information by using one piece of the following air interface signaling:.

The physical layer signaling is also referred to as Layer <NUM> (Layer <NUM>, L1) signaling, and usually may be carried by a control portion of a physical layer frame. A typical example of the L1 signaling is downlink control information (Downlink Control Information, DCI) that is carried in a physical downlink control channel (Physical Downlink Control Channel, PDCCH) as defined in an LTE standard. In some cases, the L1 signaling may alternatively be carried by a data portion of the physical layer frame. It can be easily learned that, a transmission period or a signaling period of the L1 signaling is usually a period of the physical layer frame. Therefore, the signaling is usually used to implement some dynamic control, to transfer some frequently changing information. For example, the physical layer signaling may be used to transfer resource allocation information.

The Media Access Control (Media Access Control, MAC) layer signaling belongs to Layer <NUM> (Layer <NUM>) signaling, and usually may be carried by, for example but not limited to, a frame header of a Layer <NUM> frame. The frame header may further carry, for example but not limited to, information such as a source address and a destination address. The Layer <NUM> frame usually further includes a frame body, in addition to the frame header. In some cases, the L2 signaling may alternatively be carried by the frame body of the Layer <NUM> frame. A typical example of the Layer <NUM> signaling is signaling carried in a frame control (Frame Control) field in a frame header of a MAC frame in the <NUM> series standard, or a MAC control entity (Control Entity, MAC) defined in some protocols. The Layer <NUM> frame usually may be carried in a data portion of a physical layer frame. Alternatively, the foregoing resource configuration information may be sent by using other Layer <NUM> signaling than the Media Access Control layer signaling.

The Radio Resource Control (Radio Resource Control, RRC) signaling belongs to Layer <NUM> (Layer <NUM>) signaling, and is usually some control messages. The L3 signaling usually may be carried in a frame body of a Layer <NUM> frame. The L3 signaling usually has a relatively long transmission period or control period, and is suitable for sending some information that does not frequently change. For example, in some existing communications standards, the L3 signaling is usually used to carry some configuration information. Alternatively, the foregoing resource configuration information may be sent by using other Layer <NUM> signaling than the RRC signaling.

The foregoing is merely principle description of the physical layer signaling, the MAC layer signaling, the RRC signaling, the Layer <NUM> signaling, the Layer <NUM> signaling, and the Layer <NUM> signaling. For details about the three types of signaling, refer to the prior art. Therefore, details are not described again in this specification.

In step <NUM>, the receive end device receives the configuration information from the transmit end device.

In step <NUM>, the receive end device determines a resource bundling size based on the configuration information. In a specific implementation, the receive end device is configured to determine a corresponding resource bundling size set based on a default system configuration parameter or based on an indication of air interface signaling sent by the transmit end device, or further determine a corresponding resource bundling size based on the default system configuration parameter or based on the indication of the air interface signaling sent by the transmit end device.

For example, the receive end device determines, based on the default system configuration parameter, a resource bundling size set corresponding to the system configuration parameter and a resource bundling size in the resource bundling size set; or.

In addition, the receive end device performs channel estimation or data demodulation after determining the resource bundling size.

The following describes, by using the physical resource block (Physical Resource Block, PRB) bundling size as an example, how a correspondence between a resource bundling size set and one or more system configuration parameters is configured in the step of generating, by the transmit end device, the configuration information in the method <NUM> in this embodiment of this application. For other resource bundling sizes such as the resource scheduling frequency domain size, the precoding frequency domain size, and the channel state information feedback frequency domain size, principles are similar thereto. Therefore, descriptions about the PRB bundling size in all the embodiments of this application are also applicable to the resource scheduling frequency domain size, the precoding frequency domain size, and the channel state information feedback frequency domain size, and details are not described again. In addition, for the purpose of convenient description, a network device is used as the transmit end device, and a terminal is used as the receive end device.

Embodiment <NUM>: It is agreed that a PRB bundling size set is bound to system bandwidth (system bandwidth).

A physical resource group size set may indicate a plurality of physical resource block bundling sizes, and {<NUM>, <NUM>, <NUM>} is a physical resource group size set or a physical resource bundling size set, or may be briefly referred to as a physical resource group set or a physical resource bundling set. The set corresponds to the system bandwidth ≤ <NUM>. In the physical resource group size set {<NUM>, <NUM>, <NUM>}, <NUM> indicates that one physical resource block is bundled to form one physical resource block group, and <NUM> indicates that two physical resource block is bundled to form one physical resource block group.

When the system bandwidth is ≤ <NUM>, a PRG size set corresponding to the system bandwidth may be {<NUM>, <NUM>, <NUM>}.

When the system bandwidth is ≤ <NUM>, a PRG size set corresponding to the system bandwidth may be {<NUM>}. The set {<NUM>} includes only one value <NUM>. In other words, the system bandwidth ≤ <NUM> corresponds to one PRG size <NUM>.

When the system bandwidth is ≤ <NUM>, a PRG size set corresponding to the system bandwidth may be {<NUM>}. It may be considered that the PRG size set includes only one value <NUM>, that is, the system bandwidth ≤ <NUM> corresponds to one PRG size <NUM>.

In conclusion, a mapping relationship between a physical resource group size set and system bandwidth may vary, and a quantity of physical resource group sizes in a physical resource group size set may also vary and may include only one value.

Other resource bundling sizes such as the resource scheduling frequency domain size, the precoding frequency domain size, and the channel state information feedback frequency domain size are similar thereto, and details are not described herein again.

In one implementation, a correspondence between a PRB bundling size set and system bandwidth is agreed between the network device and the terminal, specifically as follows:.

Larger system bandwidth indicates a larger (at least the same) maximum PRB bundling size in a PRB bundling size set corresponding to the system bandwidth.

Each PRB bundling size in the PRB bundling size set is a divisor of a scheduling size (RBG) (corresponding to the system bandwidth).

A first value in each PRB bundling size set is a default value. When the network device does not configure a PRB bundling size, by default the terminal uses a first value in the PRB bundling size set agreed in a protocol.

In another implementation, the network device configures a PRB bundling size set for the terminal. When configuring the PRB bundling size set, the network device needs to consider a channel estimation capability of the terminal. The capability is reported by the terminal in advance.

In still another implementation, the network device configures a PRB bundling size in a particular PRB bundling size set for the terminal.

In the foregoing three implementations, the network device may explicitly or implicitly configure a PRB bundling size, specifically as follows:.

After configuring a mapping relationship between a PRB bundling size set and system bandwidth, the network device sends the mapping relationship to each terminal by using configuration information, and each terminal obtains a PRB bundling size based on the configuration information, to perform channel estimation.

Embodiment <NUM>: It is agreed that a PRB bundling size set is bound to a system radio carrier frequency (system radio carrier frequency, RCF) parameter.

In one implementation, a correspondence between a PRB bundling size set and a system radio carrier frequency is agreed in a protocol.

A higher system radio carrier frequency indicates a larger (at least the same) maximum PRB bundling size in a PRB bundling size set corresponding to the system radio carrier frequency.

Each PRB bundling size in the PRB bundling size set is a divisor of a scheduling size (RBG) (corresponding to system radio carrier frequency).

The first or the last value in each PRB bundling size set is a default value. When the network device does not configure a PRB bundling size, by default the terminal uses a first or last value in the PRB bundling size set agreed in a protocol.

In another implementation, the network device configures a PRB bundling size set for the terminal.

During the configuration, the network device needs to consider a channel estimation capability of the terminal. The capability is reported by the terminal in advance.

Similarly, in the foregoing three implementations, the network device may explicitly or implicitly configure a PRB bundling size, specifically as follows:.

After configuring a mapping relationship between a PRB bundling size set and system radio carrier frequency, the network device sends the mapping relationship to each terminal by using configuration information, and each terminal obtains a PRB bundling size based on the configuration information, to perform channel estimation.

Embodiment <NUM>: It is agreed that a PRB bundling size set is bound to a system subcarrier spacing (system subcarrier spacing).

In one implementation, a correspondence between a PRB bundling size set and a system subcarrier spacing is agreed.

A larger system subcarrier spacing indicates a smaller (at least the same) maximum PRB bundling size in a PRB bundling size set corresponding to the system subcarrier spacing.

Each PRB bundling size in the PRB bundling size set is a divisor of a scheduling size (RBG) (corresponding to system subcarrier spacing).

A first or last value in each PRB bundling size set is a default value. When the network device does not configure a PRB bundling size, by default the terminal uses a first or last value in the PRB bundling size set agreed in a protocol.

After configuring a mapping relationship between a PRB bundling size set and system subcarrier spacing, the network device sends the mapping relationship to each terminal by using configuration information, and each terminal obtains a PRB bundling size based on the configuration information, to perform channel estimation.

Embodiment <NUM>: It is agreed that a PRB bundling set is bound to a plurality of system parameters (for example, RCF and bandwidth).

A PRB bundling size set configured by the network device includes a PRG size corresponding to a user configuration parameter. The user configuration parameter includes scheduling bandwidth for a terminal. In another implementation, the user configuration parameter may alternatively be minimum continuous scheduling bandwidth for the terminal or a divisor of continuous scheduling bandwidth for the terminal. The resource bundling size corresponding to the user configuration parameter may be a status variable. For example, the status variable instructs a target terminal to use entire or partial scheduling bandwidth. For example, in a current scheduling process, <NUM> physical resource blocks (Physical Resource Block, PRB) are scheduled for the terminal, and when a parameter is indicated, a size is <NUM> PRBs; or <NUM> PRBs are scheduled for the terminal in a scheduling process, and when another parameter is indicated, a size is <NUM> PRBs. A process of sending corresponding configuration information by the network device is similar to that in Embodiment <NUM> to Embodiment <NUM>, and details are not described herein again.

Embodiment <NUM>: It is agreed that a PRB bundling set is bound to a transmission scheme (transmission scheme, TS).

Processes of configuring a PRB bundling size and sending corresponding configuration information by the network device are similar to those in Embodiment <NUM> to Embodiment <NUM>, and details are not described herein again.

In Embodiment <NUM> to Embodiment <NUM>, the PRB bundling size set is used as an example to describe an implementation process in which the transmit end device configures a relationship between a resource bundling size set and a system configuration parameter, and sends the relationship to the receive end device.

In Embodiment <NUM>, a process in which the receive end device reports, to the transmit end device, information indicating a resource bundling size is described.

In Embodiment <NUM>, that the transmit end device is a network device and the receive end device is a terminal is still used as an example for description.

The receive end device, namely, the terminal determines a resource bundling size that the terminal needs to feed back, and sends a message to the network device to report or feed back the resource bundling size.

In an implementation, the resource bundling size fed back by the terminal is a resource bundling size that the network device should use; or the resource bundling size fed back by the terminal may be merely used as a resource bundling size suggested by the terminal for a network device, and the network device determines an actually to-be-used resource bundling size.

In a specific implementation, the terminal may determine the resource bundling size by using a plurality of implementation methods:.

For example, the terminal may first determine a proper resource bundling size through channel measurement. For example, the terminal may receive a downlink reference signal, to measure a frequency domain channel, calculate channel coherent bandwidth, and determine a proper resource bundling size based on the channel coherent bandwidth.

For another example, the terminal may collect statistics about a relationship between a resource bundling size and transmission performance under parameter conditions, such as a location, a movement speed, time, a carrier frequency, bandwidth, and a service characteristic of the terminal, to determine an optimal resource bundling size for each parameter value, and then select a current optimal resource bundling size based on a current parameter value of the terminal.

For another example, the network device may send a rule or a parameter (for example, a coherent bandwidth threshold or a resource bundling size adjustment factor) to the terminal, so that the terminal determines a resource bundling size based on the rule or the parameter and a parameter condition of the terminal.

In a specific implementation, the terminal may feed back the resource bundling size to the network device by using a plurality of implementation methods:.

For example, the terminal directly sends a message to the network device, to indicate how many RBs the resource bundling size includes.

For another example, the terminal sends a message to the network device, to indicate a resource bundling size change. For example, one bit is used to indicate unchanged/changed, or two bits are used to indicate decreased/unchanged/increased/a jump, or the like.

For another example, based on a basic resource bundling size agreed in advance (for example, the basic resource bundling size is determined based on an agreement in a standard) or based on a basic resource bundling size configured by using network signaling (for example, the basic resource bundling size is determined based on the method of Embodiment <NUM>), the terminal sends a message to the network device, to indicate a multiple relationship between the resource bundling size and the basic resource bundling size.

For another example, the terminal sends information to the transmit end device based on a plurality of resource bundling size configuration tables that are agreed in advance with the network device, to indicate a specific resource bundling size configuration table for use by the resource bundling size determined by the terminal. Specifically, based on a resource bundling size table (for example, Table <NUM>) agreed in advance, the terminal sends a message to the network device, to indicate a column in the table to be used by the determined resource bundling size (for example, indicate that a value of a case is <NUM> or <NUM>).

For another example, based on a plurality of resource bundling size tables agreed in advance, the terminal sends a message to the network device, to indicate a table to be used by the resource bundling size.

In a specific implementation, the message sent by the terminal to the network device may be used to feed back only one resource bundling size, or may be used to feed back a plurality of (suggested) resource bundling sizes. The plurality of resource bundling sizes may be fed back by sending one message, or may be fed back by sending a plurality of messages. When the plurality of resource bundling sizes are fed back by sending one message, the message may carry a plurality of IEs. Each IE indicates one resource bundling size. Alternatively, the message may carry only one IE to simultaneously indicate the plurality of resource bundling sizes. For example, a table shown in Table <NUM> is used, and one bit may be used to indicate a resource bundling size or a suggested range of resource bundling sizes. The range may include a plurality of resource bundling sizes.

The method in Embodiment <NUM> may also be used by the terminal to send a message to the network device to indicate another resource bundling size, for example, indicate a CSI feedback bundling size, such as a sub-band (sub-Band, SB) size, or indicate a resource scheduling bundling size, such as a resource block group (Resource Block Group, RBG) size.

In the foregoing embodiments, a value in a resource bundling size set may be an integer, or may be a multiple of a known size such as an RBG, as shown in Table <NUM>:.

In Embodiment <NUM> to Embodiment <NUM>, that a PRB bundling size set is bound to a system configuration parameter is mainly used as an example for description, and the system configuration parameter is a value range, so that different system configuration parameters adapt to different scenarios to improve estimation performance.

In a simple implementation, one resource bundling size set corresponds to one system configuration parameter; and one resource bundling size set has only one resource bundling size, or one resource bundling size set has a plurality of resource bundling sizes. The following describes an implementation process of this case by using Embodiment <NUM>.

Herein, this concept is described by using physical resource block configuration information and the existing LTE standard as an example. In an LTE system, a physical resource block group PRG is used to indicate a width of a frequency band for channel estimation, and this application is similar to the LTE system hereto.

The physical resource block configuration information in the method <NUM> may include a frequency bandwidth parameter. In this case, frequency bandwidth indicated by the physical resource block configuration information is equal to a product of multiplying the frequency bandwidth parameter by reference frequency bandwidth. Optionally, the reference frequency bandwidth is equal to frequency bandwidth of a resource unit. The resource unit may be a resource block (Resource Block, RB for short) in the LTE standard, or may be a newly defined unit similar to the RB. In addition, the frequency bandwidth parameter may be a specific numerical value. For example, the frequency bandwidth parameter is a numerical value <NUM>, and the resource unit is indicated by using the RB in the LTE standard. Then the frequency bandwidth indicated by the physical resource block configuration information is frequency bandwidth of three RBs. To be specific, a width of a frequency band for a physical resource block configuration is <NUM> <NUM> × <NUM> × <NUM>). It should be noted that in a specific implementation process, the reference frequency bandwidth may alternatively be another width, for example but not limited to, a subcarrier spacing.

Optionally, the physical resource block configuration information in the method <NUM> may further include a width value of a frequency band for channel estimation or an index of the width value, and the width value or the index of the width value is used to determine a width of the frequency band for channel estimation. For example, physical resource block configuration information generated by the transmit end device carries a specific width value used to indicate a width of a frequency band for channel estimation. For example, the width value may be <NUM>, and the width value <NUM> is a width of the frequency band for channel estimation that is indicated by the transmit end device to the receive end device and that is optimal in a particular scenario. The scenario may be a high frequency scenario (with a radio carrier frequency higher than <NUM>), a low frequency scenario (with a radio carrier frequency lower than <NUM>), or the like, and the scenario may be set depending on a specific need, which is not limited herein. For another example, physical resource block configuration information generated by the transmit end device carries an index used to indicate a width value of a frequency band for channel estimation, and after receiving the index, the receive end device can determine, based on a correspondence agreed in advance between the width value and the index, an optimal width of the frequency band for channel estimation that is indicated by the transmit end device to the receive end device. Specifically, for the correspondence between the width value and the index, refer to Table <NUM> below.

In an implementation, the physical resource block configuration information in the method <NUM> may further include an index of a width mapping rule. The width mapping rule records a correspondence between system bandwidth and a width of a frequency band for channel estimation. The index of the width mapping rule is used to indicate the width mapping rule. In this case, the receive end device may determine the frequency bandwidth based on the width mapping rule and the system bandwidth. For example, physical resource block configuration information generated by the transmit end device carries an index used to indicate a width mapping rule, and the width mapping rule is determined by using the index. The mapping rule may be indicated in a table form, or may be indicated in another form. Using the LTE standard as an example, for the table form, refer to Table <NUM> below (for ease of description, the index is represented by idx, the width of the frequency band is represented by P, and a unit of the frequency bandwidth is represented by a physical resource block PRB in the prior art). The correspondence between the system bandwidth and the width of the frequency band for channel estimation is determined based on a value of the index idx. For example, a value of idx is <NUM>, the system bandwidth is <NUM> to <NUM> PRBs, and P is equal to two PRBs, namely, <NUM>.

Preferably, the physical resource block configuration information in the method <NUM> may further include a width update parameter. The width update parameter is used to update a current width of a frequency band for channel estimation. For example, physical resource block configuration information generated by the transmit end device carries a width update parameter, and the width update parameter is used to indicate an update that needs to be made to the current width of the frequency band for channel estimation. Specific update content may be indicated in a calculation formula form. For details, refer to Table <NUM> below (for ease of description, the width update parameter is represented by CASE, the current width of the frequency band for channel estimation is represented by P, an updated width of the frequency band is represented by P*, and a unit of the frequency bandwidth is represented by a physical resource block PRB in the prior art). An updated width, corresponding to corresponding system bandwidth, of the frequency band for channel estimation is determined based on a value of the width update parameter CASE (for example, the value of CASE is <NUM> or <NUM>).

In a specific implementation process, in step <NUM>, the transmit end device sends the physical resource block configuration information to the receive end device by using a determined resource. The physical resource block configuration information may be sent by using one of the following signaling types: broadcast signaling; unicast signaling; physical layer signaling; Media Access Control layer signaling; and Radio Resource Control signaling.

In the foregoing embodiment, the physical resource block configuration information is used as an example for description. For the resource scheduling configuration information corresponding to the resource scheduling frequency domain size, or the precoding configuration information corresponding to the precoding frequency domain size, or the channel state information feedback configuration information corresponding to the channel state information feedback frequency domain size, or the transmission scheme configuration information, an implementation is similar thereto, and details are not described herein again.

In addition, the function of the physical resource block bundling size is not limited to channel estimation, but the physical resource block bundling size may also be used for data demodulation and the like. This is well-known to a person skilled in the art, and is not described in detail herein again.

It can be easily learned that the transmit end device generates resource configuration information, and the receive end device may determine a resource bundling size based on the resource configuration information. Compared with the prior art in which a resource size is bound only to system bandwidth, the technical solution provided in this embodiment of this application can flexibly determine a proper resource bundling size from a resource bundling size set, to adapt to different application scenarios. Therefore, by using the technical solution provided in this embodiment of this application, a requirement of a wireless communications system for diversified scenarios can be met, and system performance can be effectively optimized in different scenarios.

<FIG> is a schematic diagram of a logical structure of a transmit end device <NUM> according to an embodiment of this application. In a specific implementation process, the transmit end device may be, for example but not limited to, the terminal devices <NUM> to <NUM> or the base stations <NUM> to <NUM> in <FIG>. As shown in <FIG>, the device <NUM> includes a generation module <NUM> and a transceiver module <NUM>.

The generation module <NUM> is configured to generate configuration information, where the configuration information is used to indicate at least one resource bundling size, the resource bundling size belongs to a resource bundling size set, and the resource bundling size set corresponds to at least one system configuration parameter.

The transceiver module <NUM> is configured to send the configuration information generated by the generation module <NUM>.

The resource bundling size set generated by the generation module <NUM> corresponds to at least one system configuration parameter. In addition, the system configuration parameter includes at least one of a system radio carrier frequency parameter, a system bandwidth parameter, a system subcarrier spacing parameter, a service scenario parameter, and a transmission scheme parameter.

In addition, the resource bundling size set includes a resource bundling size corresponding to a user configuration parameter.

The transceiver module <NUM> sends, to a receive end device, configuration information indicating a resource bundling size set or configuration information indicating a resource bundling size in a resource bundling size set.

Specifically, the transceiver module <NUM> sends the configuration information to the receive end device based on channel information, or multi-user (multiple user, MU) pairing information, or a demodulation reference signal pattern.

In addition, the transceiver module <NUM> further sends the configuration information by using air interface signaling, for example, broadcast signaling, unicast signaling, Radio Resource Control signaling, downlink control signaling, or Media Access Control control element MAC CE signaling.

In addition, the transceiver module <NUM> is further configured to receive information that is reported by the receive end device and that indicates a resource bundling size.

The device <NUM> is configured to perform the method <NUM> shown in <FIG>. Technical features related to the device <NUM> are described above in detail with reference to an accompanying drawing, for example but not limited to, <FIG>. Therefore, details are not described herein again.

<FIG> is a schematic diagram of a logical structure of a receive end device <NUM> according to an embodiment of this application. In a specific implementation process, the receive end device may be, for example but not limited to, the base stations <NUM> to <NUM> or the terminal devices <NUM> to <NUM> in <FIG>. As shown in <FIG>, the device <NUM> includes a transceiver module <NUM> and a determining module <NUM>.

The transceiver module <NUM> is configured to receive configuration information, where the configuration information is used to indicate at least one resource bundling size, the resource bundling size belongs to a resource bundling size set, and the resource bundling size set corresponds to at least one system configuration parameter.

The determining module <NUM> is configured to determine a resource bundling size based on the configuration information. In addition, the determining module <NUM> is further configured to perform channel estimation or data demodulation after determining the resource bundling size.

In a specific implementation, the determining module <NUM> is further configured to determine a corresponding resource bundling size set based on a default system configuration parameter or based on an indication of air interface signaling sent by a transmit end device, or further determine a corresponding resource bundling size based on the default system configuration parameter or based on the indication of the air interface signaling sent by the transmit end device.

For example, the determining module <NUM> determines, based on the default system configuration parameter, a resource bundling size set corresponding to the system configuration parameter and a resource bundling size in the resource bundling size set; or.

In an implementation, the transceiver module <NUM> is further configured to report, to the transmit end device, information indicating a resource bundling size. Specifically, the transceiver module <NUM> directly sends, to the transmit end device, information indicating how many resource blocks a resource bundling size includes; or sends, to the transmit end device, information indicating a resource bundling size change; or sends, to the transmit end device, a multiple relationship between the resource bundling size and a basic resource bundling size, where the basic resource bundling size is agreed in advance between the transmit end device and the receive end device or preconfigured based on network signaling; or sends information to the transmit end device based on a resource bundling size configuration table that is agreed in advance with the transmit end device, to indicate that the resource bundling size determined by the receive end device is one or more resource bundling sizes in the resource bundling size configuration table; or sends information to the transmit end device based on a plurality of resource bundling size configuration tables that are agreed in advance with the transmit end device, to indicate a specific resource bundling size configuration table for use by the resource bundling size determined by the receive end device.

The determining module <NUM> is further configured to determine the resource bundling size to be reported by the receive end device, and specifically, determine the resource bundling size to be reported by the receive end device, based on a channel measurement result, or based on a correspondence between a resource bundling size and transmission performance, or based on a parameter received by the transceiver from a network device.

The device <NUM> is a receive side device corresponding to the device <NUM>, and is configured to perform the method <NUM> shown in <FIG>. Technical features related to the device <NUM> are described above in detail with reference to an accompanying drawing, for example but not limited to, <FIG>. Therefore, details are not described herein again.

<FIG> is a schematic diagram of a hardware structure of a transmit end device <NUM> according to an embodiment of this application. As shown in <FIG>, the device <NUM> includes a processor <NUM>, a transceiver <NUM>, a plurality of antennas <NUM>, a memory <NUM>, an I/O (input/output, Input/Output) interface <NUM>, and a bus <NUM>. The transceiver <NUM> further includes a transmitter <NUM> and a receiver <NUM>. The memory <NUM> is further configured to store an instruction <NUM> and data <NUM>. In addition, the processor <NUM>, the transceiver <NUM>, the memory <NUM>, and the I/O interface <NUM> are communicatively connected to each other by using the bus <NUM>, and the plurality of antennas <NUM> are connected to the transceiver <NUM>.

The processor <NUM> may be a general-purpose processor, for example but not limited to, a central processing unit (Central Processing Unit, CPU), or may be a dedicated processor, for example but not limited to, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), or a field programmable gate array (Field Programmable Gate Array, FPGA). In addition, the processor <NUM> may alternatively be a combination of a plurality of processors. Particularly, in the technical solution provided in this embodiment of this application, the processor <NUM> may be configured to perform, for example, step <NUM> in the resource configuration method <NUM> shown in <FIG>, and an operation performed by the generation module <NUM> in the transmit end device <NUM> shown in <FIG>. The processor <NUM> may be a processor specially designed to perform the foregoing step and/or operation, or may be a processor that performs the foregoing step and/or operation by reading and executing the instruction <NUM> stored in the memory <NUM>, and the processor <NUM> may need to use the data <NUM> when performing the foregoing step and/or operation.

The transceiver <NUM> includes the transmitter <NUM> and the receiver <NUM>. The transmitter <NUM> is configured to send a signal by using at least one of the plurality of antennas <NUM>. The receiver <NUM> is configured to receive a signal by using at least one of the plurality of antennas <NUM>. Particularly, in the technical solution provided in this embodiment of this application, the transmitter <NUM> may be specifically configured to perform, for example, step <NUM> in the resource configuration method <NUM> shown in <FIG>, and an operation performed by the transceiver module <NUM> in the transmit end device <NUM> shown in <FIG>, by using at least one of the plurality of antennas <NUM>.

The memory <NUM> may be various types of storage media, for example, a random access memory (Random Access Memory, RAM), a read-only memory (Read-Only Memory, ROM), a non-volatile RAM (Non-Volatile RAM, NVRAM), a programmable ROM (Programmable ROM, PROM), an erasable PROM (Erasable PROM, EPROM), an electrically erasable PROM (Electrically Erasable PROM, EEPROM), a flash memory, an optical memory, or a register. The memory <NUM> is specifically configured to store the instruction <NUM> and the data <NUM>. The processor <NUM> may perform the foregoing step and/or operation by reading and executing the instruction <NUM> stored in the memory <NUM>, and may need to use the data <NUM> when performing the foregoing step and/or operation.

The I/O interface <NUM> is configured to receive an instruction and/or data from a peripheral device, and output an instruction and/or data to the peripheral device.

It should be noted that in a specific implementation process, the device <NUM> may further include other hardware devices, which are not enumerated one by one in this specification.

<FIG> is a schematic diagram of a hardware structure of a receive end device <NUM> according to an embodiment of this application. As shown in <FIG>, the device <NUM> includes a processor <NUM>, a transceiver <NUM>, a plurality of antennas <NUM>, a memory <NUM>, an I/O (input/output, Input/Output) interface <NUM>, and a bus <NUM>. The transceiver <NUM> further includes a transmitter <NUM> and a receiver <NUM>. The memory <NUM> is further configured to store an instruction <NUM> and data <NUM>. In addition, the processor <NUM>, the transceiver <NUM>, the memory <NUM>, and the I/O interface <NUM> are communicatively connected to each other by using the bus <NUM>, and the plurality of antennas <NUM> are connected to the transceiver <NUM>.

The processor <NUM> may be a general-purpose processor, for example but not limited to, a central processing unit (Central Processing Unit, CPU), or may be a dedicated processor, for example but not limited to, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), or a field programmable gate array (Field Programmable Gate Array, FPGA). In addition, the processor <NUM> may alternatively be a combination of a plurality of processors. Particularly, in the technical solution provided in this embodiment of this application, the processor <NUM> may be configured to perform, for example, step <NUM> in the method <NUM> shown in <FIG>, and an operation performed by the determining module <NUM> in the device <NUM> shown in <FIG>. The processor <NUM> may be a processor specially designed to perform the foregoing step and/or operation, or may be a processor that performs the foregoing step and/or operation by reading and executing the instruction <NUM> stored in the memory <NUM>, and the processor <NUM> may need to use the data <NUM> when performing the foregoing step and/or operation.

The transceiver <NUM> includes the transmitter <NUM> and the receiver <NUM>. The transmitter <NUM> is configured to send a signal by using at least one of the plurality of antennas <NUM>. The receiver <NUM> is configured to receive a signal by using at least one of the plurality of antennas <NUM>. Particularly, in the technical solution provided in this embodiment of this application, the receiver <NUM> may be specifically configured to perform, for example, step <NUM> in the method <NUM> shown in <FIG>, and an operation performed by the transceiver module <NUM> in the receive end device <NUM> shown in <FIG>, by using at least one of the plurality of antennas <NUM>.

<FIG> is a schematic structural diagram of a resource configuration system <NUM> according to an embodiment of this application. In a specific implementation process, as shown in <FIG>, the resource configuration system <NUM> may include: a transmit end device <NUM> and a receive end device <NUM>.

In a possible implementation, the transmit end device <NUM> is the transmit end device <NUM> shown in <FIG>; and the receive end device <NUM> is the receive end device <NUM> shown in <FIG>.

In another possible implementation, the transmit end device <NUM> is the transmit end device <NUM> shown in <FIG>; and the receive end device <NUM> is the receive end device <NUM> shown in <FIG>.

It should be understood that sequence numbers of the foregoing processes do not mean execution sequences in the embodiments of this application.

In the embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one position, or may be distributed on a plurality of network units.

When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The software product is stored in a storage medium, and includes instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in the embodiments of this application. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

Claim 1:
A resource configuration method, wherein the method comprises:
receiving (<NUM>), by a receive end device, configuration information from a transmit end device, wherein the configuration information indicates a resource block group, RBG, size, the RBG size belongs to a RBG size set, and the RBG size set corresponds to a system bandwidth parameter and comprises at least two RBG sizes; and
determining (<NUM>), by the receive end device, a RBG size based on the configuration information,
wherein the RBG size is a resource scheduling frequency domain size.