Resource determination method and apparatus, device, and storage medium

Abstract

A resource determination method and apparatus, a device, and a storage medium, relating to the technical field of communications. The method comprises: on the basis of at least two frequency domain resources, determining the number of frequency domain units comprised in a frequency domain unit group, wherein each frequency domain resource comprises at least one frequency domain unit. By determining, on the basis of at least two frequency domain resources, the number of frequency domain units comprised in a frequency domain unit group, the size of the frequency domain unit group is determined on the basis of a combination of a plurality of frequency domain resources, and the size of the frequency domain unit group does not need to be independently determined for each frequency domain resource, thereby reducing the complexity of resource determination.

Description

Resource determination method, device, equipment and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a resource determination method, apparatus, device, and storage medium. Background Art

[0002] By configuring Carrier Aggregation (CA) in the NR (New Radio) system, higher data rates and network capacity can be achieved.

[0003] In the related art, for a NR system configured with CA, the RBG (Resource Block Group) size or subband size of each carrier in multiple carriers is determined independently based on each carrier.

[0004] The above resource determination method is highly complex because it requires independent determination of the RBG size or subband size for each carrier.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a resource determination method, apparatus, device, and storage medium. The technical solutions provided by the embodiments of the present application are as follows:

[0007] According to one aspect of an embodiment of the present application, a resource determination method is provided, the method comprising:

[0008] The number of frequency domain units included in the frequency domain unit group is determined according to at least two frequency domain resources; wherein each of the frequency domain resources includes at least one frequency domain unit.

[0009] According to one aspect of an embodiment of the present application, a resource determination device is provided, the device including:

[0010] The processing module is used to determine the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources; wherein each of the frequency domain resources includes at least one of the frequency domain units.

[0011] According to one aspect of an embodiment of the present application, a communication device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the above-mentioned resource determination method.

[0012] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to be executed by a processor to implement the above-mentioned resource determination method.

[0013] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the above-mentioned resource determination method.

[0014] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes a computer program stored in a computer-readable storage medium. A processor reads and executes the computer program from the computer-readable storage medium to implement the above-mentioned resource determination method.

[0015] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0016] By determining the number of frequency domain units included in the frequency domain unit group based on at least two frequency domain resources, the size of the frequency domain unit group is jointly determined based on multiple frequency domain resources. There is no need to independently determine the size of the frequency domain unit group for each frequency domain resource, thereby reducing the complexity of resource determination. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0018] FIG2 is a schematic diagram of a terminal carrier aggregation example provided by an embodiment of the present application;

[0019] FIG3 is a flow chart of a resource determination method provided by an embodiment of the present application;

[0020] FIG4 is a schematic diagram of RBGs obtained by division according to an embodiment of the present application;

[0021] FIG5 is a schematic diagram of RBGs obtained by division according to another embodiment of the present application;

[0022] FIG6 is a schematic diagram of RBGs obtained by dividing multiple devices sharing the same carrier according to an embodiment of the present application;

[0023] FIG7 is a schematic diagram of RBGs obtained by dividing multiple devices sharing the same carrier according to another embodiment of the present application;

[0024] FIG8 is a block diagram of a resource determination device provided by an embodiment of the present application;

[0025] FIG9 is a schematic structural diagram of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0027] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0028] Please refer to FIG1 , which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 may include: a terminal device 10 , an access network device 20 , and a core network element 30 .

[0029] The terminal device 10 may refer to a UE (User Equipment), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user apparatus. In some embodiments, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For ease of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is generally multiple, and one or more terminal devices 10 may be distributed in a cell managed by each access network device 20. The terminal device may also be referred to as a terminal or UE for short, and those skilled in the art will understand its meaning.

[0030] Access network equipment 20 is a device deployed in an access network to provide wireless communication capabilities for terminal devices 10. Access network equipment 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different wireless access technologies, the names of devices that provide access network equipment functions may vary. For example, in 5G NR systems, they are referred to as gNodeBs or gNBs. As communication technologies evolve, the term "access network equipment" may change. For ease of description, in the embodiments of this application, the aforementioned devices that provide wireless communication capabilities for terminal devices 10 are collectively referred to as access network equipment. In some embodiments, access network equipment 20 enables communication between terminal devices 10 and core network elements 30. For example, in an LTE (Long Term Evolution) system, access network equipment 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs within the EUTRAN. In a 5G NR system, access network equipment 20 may be a Radio Access Network (RAN) or one or more gNBs within the RAN. In the embodiment of the present application, unless otherwise specified, the "network device" refers to the access network device 20, such as a base station.

[0031] The core network element 30 is a network element deployed in the core network. The functions of the core network element 30 are mainly to provide user connection, user management, and service bearer, and to provide an interface to the external network as a bearer network. For example, the core network elements in the 5G NR system may include network elements such as the AMF (Access and Mobility Management Function) entity, the UPF (User Plane Function) entity, and the SMF (Session Management Function) entity.

[0032] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via an air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via an air interface technology, such as the Uu interface.

[0033] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (e.g., B5G (Beyond 5G) systems, 6G systems (6th Generation System, sixth generation mobile communication systems)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems, which are not limited in this application.

[0034] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0035] Before introducing the technical solutions of this application, we first introduce and explain some of the relevant technical knowledge involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0036] 1.CA

[0037] Carrier-assisted NR (New Radio) systems use frequency resources on multiple carriers to provide services to UEs, achieving higher data rates and network capacity. This means that multiple serving cells are configured for the UE, allowing the UE to send and receive data simultaneously in multiple cells.

[0038] Currently, all operators have multiple, non-contiguous, narrow bandwidth frequency bands. For example, Operator A is allocated 30 Mbps of bandwidth in the 1.9 GHz band, 15 Mbps in the 2.0 GHz band, and 50 Mbps in the 2.3 GHz band. Operator B is allocated 20 Mbps of bandwidth in the 1.7 GHz band, 20 Mbps in the 1.8 GHz band, 20 Mbps in the 2.3 GHz band, and 20 Mbps in the 2.5 GHz band. Operator C is allocated 15 Mbps of bandwidth in the 1.7 GHz band, 15 Mbps in the 1.8 GHz band, 20 Mbps in the 2.3 GHz band, and 20 Mbps in the 2.6 GHz band.

[0039] As shown in FIG2 , two serving cells are configured for the UE, with bandwidths of 30 Mbps and 50 Mbps respectively. In this case, the maximum transmission bandwidth of the UE is equivalent to 80 Mbps.

[0040] 2. RBG

[0041] RBG is the basic scheduling unit for frequency domain resource allocation of data channels and is used for type0 frequency domain resource allocation. In the 5G NR system, type0 is a frequency domain resource allocation mode. The 5G NR system provides type0 frequency domain resource allocation and type1 frequency domain resource allocation. Among them, the Type0 frequency domain resource allocation method has a concept of RBG. In short, several RBs (Resource Blocks) are collectively called an RBG. Each RBG will have a corresponding 1 bit. If the bit is set to 1, it means that the RBG has been allocated to the UE. Therefore, the type0 frequency domain resource allocation method supports continuous and discontinuous frequency domain resource allocation. In addition, the type1 frequency domain resource allocation method is not related to the technical solution of this application and will not be introduced here.

[0042] For a carrier, a carrier can include at least one RB, and typically, a carrier includes multiple RBs. One or more BWPs (Bandwidth Parts) can be configured on a carrier. Furthermore, at least one of the configured BWPs can be activated for use. A BWP can include all or part of the RBs on the carrier. For example, a carrier includes 100 RBs, which are numbered 0 to 99, and the activated BWP on the carrier includes 10 RBs numbered 10 to 19. In addition, the basic scheduling unit for frequency domain resources on a carrier or its activated BWP is an RBG. An RBG can include at least one RB, and typically, an RBG includes multiple RBs, such as 2, 4, 8, or 16 RBs. Therefore, RBs on a carrier or its activated BWP can be grouped. All RBs on a carrier or its activated BWP can be divided into several RBGs, and resource scheduling is performed on an RBG basis.

[0043] RBG size (RBG size) indicates the number of RBs included in the RBG. The RBG size is determined by the BWP size and the high-level signaling configuration. Among them, the BWP size refers to the number of RBs included in the BWP. The above-mentioned high-level signaling configuration refers to the RRC (Radio Resource Control) signaling configuration. RRC signaling is the highest-level radio resource control signaling in the 5G NR system. It is responsible for carrying system information and completing the configuration of radio resource management. BWP consists of part or all of the RBs within a carrier. Among them, RBs can be continuous or non-continuous, and this application does not limit this. A carrier can contain multiple BWPs. The basic principle for determining RBG is to form N RBs with consecutive indexes into an RBG, where N is an integer greater than 1. See Table 1 for details. For example, when the number of RBs included in the BWP is 1 to 36, according to configuration 1 (Configuration 1), the number of RBs included in the RBG is 2; according to configuration 2 (Configuration 2), the number of RBs included in the RBG is 4, that is, the numbers in the table represent the RBG sizes corresponding to different BWP sizes and different configurations.

[0044] Table 1

[0045] The number of RBGs contained in a BWP is N RBG The calculation formula is:

[0046] Among them, mod is the modulus operator, is the number of RBs included in the i-th BWP in the carrier, is the number corresponding to the first RB in the i-th BWP in the carrier on the carrier, and P is the number of RBs included in the RBG, corresponding to the numbers in Table 1.

[0047] For the case where the number of RBs included in the BWP is not divisible by P (RBG size), the division of the sizes of the first and last RBGs in the BWP is optimized, as shown in the following formula.

[0048] The size of the first RBG:

[0049] The size of the last RBG:

[0050] if

[0051] if

[0052] The size of other RBGs is P.

[0053] 3. Sub-band

[0054] The basic unit (or granularity) for reporting CSI (Channel State Information) on a carrier or its activated BWP is a subband. A subband can include at least one RB. Typically, a subband includes multiple RBs, such as 4, 8, 16, or 32 RBs. Therefore, RBs on a carrier or its activated BWP can be grouped. All RBs on a carrier or its activated BWP can be divided into several subbands, and CSI reporting is performed on a subband basis.

[0055] The subband size indicates the number of RBs included in a subband. The subband size is determined by both the BWP size and the higher-layer signaling configuration. This higher-layer signaling configuration also refers to the RRC signaling configuration. See Table 2 for specific subband size values. For example, when the number of RBs included in a BWP is between 24 and 72, the subband size is 4 or 8. Different configurations correspond to different subband sizes. For example, when the higher-layer signaling configuration is configuration 1, the subband size is 4; when the higher-layer signaling configuration is configuration 2, the subband size is 8. In other words, the numbers in the table represent the subband sizes corresponding to different BWP sizes and different configurations.

[0056] Table 2

[0057] The subband division is as follows:

[0058] The size of the first subband is:

[0059] in, is the number of the first RB in the i-th BWP on the carrier, is the number of RBs included in the subband.

[0060] The size of the last subband yes:

[0061] if

[0062] if

[0063] The sizes of other subbands are

[0064] As can be seen from the above introduction, for the scenario of carrier aggregation, the current RBG size determination method is determined independently based on each carrier, and the frequency domain resource indication method is to send scheduling information separately for each carrier. Then, when multiple carriers are aggregated together, for example, when a terminal device is configured with frequency domain resources on multiple carriers (such as carrier 1 and carrier 2), the terminal device and the access network device still use the current RBG size determination method, that is, the access network device for carrier 1 needs to send scheduling information separately for resource scheduling, and the access network device for carrier 2 also needs to send scheduling information separately for resource scheduling. Therefore, this not only leads to a higher complexity in determining the RBG size, but also leads to an increase in the amount of scheduling information for frequency domain resources.

[0065] Similarly, in carrier aggregation scenarios, the current method for determining subband sizes is also based on each carrier independently, meaning different carriers may be configured with different subband sizes. Consequently, when measuring and reporting CSI, terminal devices must measure and report the corresponding subband size for each carrier, and access network equipment must also analyze CSI using the corresponding subband size for each carrier. This not only increases the complexity of determining subband sizes, but also increases the complexity of CSI measurement, reporting, and analysis.

[0066] Please refer to Figure 3, which shows a flow chart of a resource determination method provided by an embodiment of the present application. The execution subject of each step of the method can be the terminal device 10 or the access network device 20 in the network architecture shown in Figure 1. The method can include the following step 310.

[0067] Step 310: Determine the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources; wherein each frequency domain resource includes at least one frequency domain unit.

[0068] In some embodiments, frequency domain resources refer to frequency bands or spectrum resources used to transmit information in a communication system, and can be composed of one or more carriers. Frequency domain resources can be divided into multiple small units, namely frequency domain unit groups, in a block / group manner. A frequency domain unit group is a resource management mechanism that combines one or more frequency domain units to form a logical resource management and scheduling unit. Among them, the frequency domain unit is the basic component unit of the frequency domain unit group, and the frequency domain unit can be the smallest unit such as a subcarrier or resource block.

[0069] In some embodiments, the frequency domain resource is: a carrier; or an activated bandwidth on a carrier; or a set of frequency domain units with the same transmission direction on a carrier; or a set of frequency domain units with the same transmission direction in the activated bandwidth on a carrier.

[0070] In some embodiments, a carrier refers to a high-frequency electromagnetic wave signal used for wireless communication. In some embodiments, the activated bandwidth on a carrier refers to the portion of bandwidth that is actually activated and used within the total bandwidth of a carrier. For example, the total bandwidth of a carrier is 100MHz, but only 80MHz of the bandwidth is activated and used according to demand, then the 80MHz bandwidth is the activated bandwidth on the carrier. In the 5G NR system, the activated bandwidth on a carrier can be called the activated BWP on the carrier, that is, by configuring and activating the BWP, part or all of the frequency domain resources on the carrier can be used. However, the concept of activated bandwidth is not limited to the activated BWP. In future systems such as B5G and 6G, any bandwidth can still be activated and used as needed within a carrier.

[0071] In some embodiments, a carrier can be used for both uplink and downlink transmission directions. Uplink refers to the direction of signals transmitted from the terminal device to the access network device, and downlink refers to the direction of signals transmitted from the access network device to the terminal device. In order to better manage and schedule frequency domain resources, we can first divide the total frequency domain resources of a carrier into uplink and downlink parts according to the transmission direction. Then, within the frequency domain resource range corresponding to each transmission direction, it is further divided into multiple frequency domain units. The set of frequency domain units with the same transmission direction on a carrier refers to a set of frequency domain units belonging to the same transmission direction in a carrier. For example, a carrier with a bandwidth of 100MHz can first distinguish 40MHz for uplink, and then divide 10 uplink frequency domain units of 4MHz in size from this 40MHz, distinguish 60MHz for downlink, and divide 15 downlink frequency domain units of 4MHz in size from this 60MHz. In this way, not only can resources in different directions be flexibly scheduled, but interference between different directions can also be avoided.

[0072] In some embodiments, in the activated bandwidth on a carrier, a set of frequency domain units with the same transmission direction refers to a set of frequency domain units belonging to the same transmission direction after the frequency domain resources are divided into uplink and downlink parts according to the transmission direction within the activation bandwidth of a carrier.

[0073] The above-mentioned frequency domain resource forms reflect the continuous refinement of frequency domain resource management in wireless communications, taking into account both the overall and subdivision aspects, with the aim of improving frequency domain utilization efficiency and achieving flexible resource scheduling.

[0074] In some embodiments, at least two frequency domain resources are non-contiguous; alternatively, at least two frequency domain resources are contiguous. Frequency domain resources can be classified as either non-contiguous or contiguous. When describing the continuity of frequency domain resources, the definition is based on the carrier, not the physical spectrum. For example, if at least two frequency domain resources are physically contiguous but defined as different frequency bands during spectrum partitioning, these at least two frequency domain resources are considered non-contiguous. Non-contiguous frequency domain resources refer to non-adjacent resources distributed across different frequency bands, such as 700 MHz and 3.5 GHz. They can originate from different frequency bands or be intermittent resources within the same frequency band. These non-contiguous resources require coordinated use through technologies such as carrier aggregation and cross-band coordinated management, as the propagation characteristics of each frequency band may vary. Continuous frequency domain resources, on the other hand, refer to resources located in adjacent frequency domains, such as a single 100 MHz bandwidth. These resources are easier to use and manage, provide greater bandwidth, and have more consistent channel propagation characteristics.

[0075] In this approach, non-contiguous frequency domain resources can be aggregated to improve utilization, while contiguous frequency domain resources are easier to manage and offer greater bandwidth. NR systems can flexibly utilize both forms of frequency domain resources, leveraging their respective strengths to enhance overall wireless communication performance.

[0076] In some embodiments, each frequency domain resource includes at least one frequency domain unit, and the frequency domain unit can be an RB, where the RB can be understood as a PRB (Physical Resource Block). Generally speaking, each frequency domain resource includes multiple frequency domain units. For example, a frequency domain resource may include 10, 30, 50, or 100 RBs. In the embodiments of the present application, there is no limit on the number of RBs included in a frequency domain resource. By dividing the frequency domain resources, or grouping the frequency domain units included in the frequency domain resources, at least one frequency domain unit group can be obtained. Each frequency domain unit group may include at least one frequency domain unit. In general, each frequency domain unit group includes multiple frequency domain units, or in other words, each frequency domain unit group includes at least two frequency domain units. However, the present application does not exclude that in some cases, each frequency domain unit group includes only one frequency domain unit.

[0077] In some embodiments, the frequency domain unit group is an RBG, and the frequency domain unit is an RB. An RBG includes one or more RBs.

[0078] In some embodiments, the frequency domain unit group is a subband, and the frequency domain unit is an RB. A subband includes one or more RBs.

[0079] In some embodiments, the number of frequency domain units included in the frequency domain unit group can be understood as the size of the frequency domain unit group. For example, if the number of frequency domain units included in the frequency domain unit group is x, it can be understood that the size of the frequency domain unit group is x, where x is a positive integer. Of course, in some possible cases, the size of the frequency domain unit group can also be referred to as other names such as the size or length of the frequency domain unit group, and this application does not limit this.

[0080] In some embodiments, the frequency domain unit group is an RBG, the frequency domain unit is an RB, and the number of RBs included in the RBG can be understood as the size of the RBG, that is, the RBG size.

[0081] In some embodiments, the frequency domain unit group is a subband, the frequency domain unit is an RB, and the number of RBs included in the subband can be understood as the size of the subband, that is, subband size.

[0082] In some embodiments, the number of frequency domain units included in the frequency domain unit group is determined based on the sum of the number of frequency domain units included in at least two frequency domain resources. For example, assume there are two frequency domain resources 1 and 2. Frequency domain resource 1 contains m frequency domain units, and frequency domain resource 2 contains n frequency domain units. Then, the sum of the number of frequency domain units in the two frequency domain resources is: m+n, where m and n are integers greater than 0. Then, based on the sum of the number of frequency domain units, the number of frequency domain units included in the frequency domain unit group is determined.

[0083] In some embodiments, the number of frequency domain units included in the frequency domain unit group is determined according to a configuration parameter and the sum of the numbers of frequency domain units included in at least two frequency domain resources.

[0084] In some embodiments, the configuration parameter refers to the above-mentioned high-level signaling configuration, such as RRC signaling configuration. We regard the sum of the number of frequency domain units included in at least two frequency domain resources as a whole, and then determine the number of frequency domain units included in the frequency domain unit group based on the configuration parameter. Among them, the size of at least one frequency domain unit group can be determined based on the sum of the number of frequency domain units. For example, the sizes of at least two frequency domain unit groups can be determined based on the sum of the number of frequency domain units. The sizes of the at least two frequency domain unit groups correspond to different configuration parameters. Therefore, based on the configuration parameter, the size of one frequency domain unit group can be further determined from the sizes of the at least two frequency domain unit groups. The size of the frequency domain unit group finally determined is the number of frequency domain units included in the determined frequency domain unit group.

[0085] In some embodiments, at least one set of correspondences is predefined, and each set of correspondences includes a correspondence between a quantity value range and the size of at least one frequency domain unit group. According to the sum of the numbers of frequency domain units included in at least two frequency domain resources, the quantity value range to which the sum belongs is determined (recorded as the first quantity value range), and then the size of at least one frequency domain unit group corresponding to the first quantity value range is found from the above at least one set of correspondences. Further, in combination with the configuration parameters, the size of a frequency domain unit group corresponding to the configuration parameter is determined from the size of at least one frequency domain unit group corresponding to the first quantity value range, as the size of the frequency domain unit group finally determined (that is, the number of frequency domain units included in the frequency domain unit group). The above at least one set of correspondences can be specified by the protocol or pre-configured, and this application does not limit this. In addition, when adopting the scheme provided in the present application of determining the number of frequency domain units included in the frequency domain unit group based on the sum of the number of frequency domain units included in at least two frequency domain resources, for the case where the frequency domain unit group is RBG, the at least one group of correspondences can still use the correspondences shown in Table 1 above, or a new correspondence can be redefined; similarly, for the case where the frequency domain unit group is a subband, the at least one group of correspondences can still use the correspondences shown in Table 2 above, or a new correspondence can be redefined, and the present application does not limit this.

[0086] In some embodiments, at least two frequency domain resources belong to the same resource pool, and the configuration parameters are configured for the resource pool; or, the configuration parameters are shared by at least two frequency domain resources; or, the configuration parameters corresponding to each frequency domain resource in at least two frequency domain resources are the same.

[0087] A resource pool refers to a collection of frequency domain resources. If frequency domain resources belong to the same resource pool, configuration parameters can be configured uniformly for that resource pool. For example, if frequency domain resource 1 and frequency domain resource 2 belong to the same resource pool 1, they use the configuration parameters of resource pool 1. Configuration parameters are shared by at least two frequency domain resources. That is, frequency domain resource 1 and frequency domain resource 2 share the same configuration parameters, but these two frequency domain resources can be in different resource pools or in the same resource pool. The configuration parameters corresponding to each frequency domain resource in at least two frequency domain resources are the same. That is, the configuration parameters are configured separately for each frequency domain resource, but the same parameter configuration is configured for frequency domain resource 1 and frequency domain resource 2.

[0088] The above method, by configuring at least two frequency domain resources into the same resource pool, or the at least two frequency domain resources share the same configuration parameters, or separately configure the same configuration parameters for the at least two frequency domain resources, can make the at least two frequency domain resources associated. This association and configuration consistency can facilitate the pooled management of frequency domain resources, simplify the signaling overhead of resource configuration, and make the management and scheduling of frequency domain resources simpler and more efficient.

[0089] In some embodiments, after determining the number of frequency domain units included in the frequency domain unit group based on at least two frequency domain resources, the method further includes: dividing each of the at least two frequency domain resources into at least one frequency domain unit group based on the number of frequency domain units included in the frequency domain unit group. For example, assuming that based on two frequency domain resources 1 and frequency domain resource 2, it is determined that the frequency domain unit group includes 4 frequency domain units. Frequency domain resource 1 includes 24 frequency domain units, and frequency domain resource 2 includes 35 frequency domain units. The frequency domain units on frequency domain resource 1 and frequency domain resource 2 are both numbered starting from 0. Then, the frequency domain units are grouped for frequency domain resource 1 and frequency domain resource 2, respectively, to obtain a frequency domain unit group on frequency domain resource 1 and a frequency domain unit group on frequency domain resource 2. Specifically, on frequency domain resource 1, 6 frequency domain unit groups can be divided, and each frequency domain unit group includes 4 frequency domain units; on frequency domain resource 2, 9 frequency domain unit groups can be divided, and the last frequency domain unit group includes 3 frequency domain units, and the other 8 frequency domain unit groups all include 4 frequency domain units.

[0090] The above method can better balance the utilization of frequency domain resources of different sizes and improve the overall utilization efficiency of frequency domain resources by dividing each frequency domain resource into its own frequency domain unit group.

[0091] In some embodiments, the number of frequency domain units included in the first frequency domain unit group and the last frequency domain unit group of any frequency domain resource is limited. For any frequency domain resource of at least two frequency domain resources, the number of frequency domain units included in the first frequency domain unit group obtained by dividing the frequency domain resource is PN start mod P;

[0092] If (N start +N size )mod P≠0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resource is (N start +N size )mod P;

[0093] If (N start +N size )mod P=0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resource is P;

[0094] The number of frequency domain units included in each other frequency domain unit group obtained by dividing the frequency domain resources is P, and the other frequency domain unit group refers to any frequency domain unit group except the first frequency domain unit group and the last frequency domain unit group;

[0095] Wherein, P is the number of frequency domain units included in the frequency domain unit group determined based on the at least two frequency domain resources, that is, P is the number of frequency domain units included in the frequency domain unit group determined in step 310, or the size of the frequency domain unit group. start N is the number corresponding to the first frequency domain unit of the frequency domain resource. size The number of frequency domain units included in the frequency domain resources.

[0096] In some embodiments, N start The number corresponding to the first frequency domain unit of the frequency domain resource on the first resource. When the frequency domain resource is the activated bandwidth on the carrier, the first resource is the carrier where the frequency domain resource is located. Alternatively, when the frequency domain resource is a set of frequency domain units with the same transmission direction on the carrier, the first resource is the carrier where the frequency domain resource is located. Alternatively, when the frequency domain resource is a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, the first resource is the carrier where the frequency domain resource is located. Alternatively, when the frequency domain resource is a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, the first resource is the activated bandwidth on the carrier where the frequency domain resource is located.

[0097] Exemplarily, when the frequency domain resource is a carrier, the frequency domain unit group is an RBG, and the frequency domain unit is an RB, please refer to FIG4 , which shows a schematic diagram of RBGs obtained by division according to an embodiment of the present application.

[0098] A carrier aggregation system consists of two carriers. Carrier 1 has a bandwidth of 20 MHz (including 100 RBs), and carrier 2 has a bandwidth of 10 MHz (including 50 RBs). Based on the combined bandwidth of the two carriers (150 RBs), and according to the configuration parameters of Configuration 1 in Table 1 above, the RBG size P is determined to be 16. For carrier 1, the first RBG size is 16-0 = 16, the last RBG size is 100 mod 16 = 4, and the remaining RBG sizes are 16. For carrier 2, the first RBG size is 16-0 = 16, the last RBG size is 50 mod 16 = 2, and the remaining RBG sizes are 16.

[0099] Exemplarily, when the frequency domain resource is the activated bandwidth on the carrier (taking the activated BWP as an example below), the frequency domain unit group is RBG, and the frequency domain unit is RB, please refer to Figure 5, which shows a schematic diagram of the RBG obtained by division provided in another embodiment of the present application.

[0100] A carrier aggregation system consists of two carriers. Carrier 1 has a bandwidth of 20 MHz, and the activated BWPs on carrier 1 are RB0-RB29. Carrier 2 has a bandwidth of 10 MHz, and the activated BWPs on carrier 2 are RB10-RB39, as shown in Figure 5. Based on the total activated bandwidth of 60 RBs on both carriers and the configuration parameters of Configuration 1 in Table 1 above, the RBG size P is determined to be 4. For carrier 1, the first RBG size is 4-0 = 4, the last RBG size is 30 mod 4 = 2, and the remaining RBG sizes are 4. For carrier 2, the first RBG size is 4-10 mod 4 = 2. Since (10 + 30) mod 4 = 0, the last RBG size is 4, and the remaining RBG sizes are 4.

[0101] In some embodiments, for any one of the at least two frequency domain resources, when multiple devices share the frequency domain resource, frequency domain unit groups are obtained for the multiple devices based on the same frequency domain unit numbering rule. The multiple devices may refer to multiple terminal devices or multiple access network devices.

[0102] For each of the multiple devices that share the same frequency domain resource, based on the same frequency domain unit numbering rule, the frequency domain unit group obtained is divided according to the actual situation of each device. The number of frequency domain units included in the frequency domain unit group obtained by each device can be the same or different, and this application does not limit this. The so-called based on the same frequency domain unit numbering rule refers to the frequency domain units obtained by dividing on the frequency domain resource, and the number corresponding to the same frequency domain unit is the same for the above-mentioned multiple devices. For example, device 1 and device 2 share the same frequency domain resource, which includes 100 frequency domain units, which are numbered from small to large according to frequency. The numbers of these 100 frequency domain units are 0 to 99, respectively. For device 1, the numbers of these 100 frequency domain units are 0 to 99, respectively. For device 2, the numbers of these 100 frequency domain units are also 0 to 99, and the numbers corresponding to the same frequency domain unit in these 100 frequency domain units are the same for device 1 and device 2.

[0103] For example, please refer to Figure 6, which shows a schematic diagram of RBGs obtained when multiple devices share the same carrier, according to an embodiment of the present application. Terminal 1 is configured only with carrier 1, with a bandwidth of 30 RBs, and the RBG configuration parameters are configured as 1 according to Table 1 above, with an RBG size of 2. Terminal 2 is configured with carriers 0 and 1 (carrier 0 is not shown in Figure 6), with a total bandwidth of 59 RBs, and the RBG configuration parameters are configured as 1 according to Table 1 above, with an RBG size of 4. On carrier 1, terminals 1 and 2 obtain RBGs according to the same RB numbering rule, that is, both number the 30 RBs from 0 to 29, as shown in Figure 6. The first RBG obtained by terminal 1 on carrier 1 includes RBs numbered 0 and 1, the second RBG includes RBs numbered 2 and 3, the third RBG includes RBs numbered 4 and 5, and so on, until the last RBG includes RBs numbered 28 and 29. The first RBG allocated to terminal 2 on carrier 1 includes RBs numbered 0 through 3. The second RBG includes RBs numbered 4 through 7. The third RBG includes RBs numbered 8 through 11. This continues until the final RBG includes RBs numbered 28 and 29. As shown in Figure 6, although the RBG sizes for the two terminals are different, both are allocated using the same RB numbering convention on the same carrier. Therefore, the allocated RBGs have a well-nested structure. The RBGs allocated to the two different terminals completely overlap. For example, the first RBG allocated to terminal 2 completely overlaps with the first and second RBGs allocated to terminal 1. This prevents resource fragmentation. For example, the RBG consisting of RBs numbered 0 and 1 on carrier 1 can be scheduled for terminal 1, the RBG consisting of RBs numbered 2 and 3 can also be scheduled for terminal 1, and the RBG consisting of RBs numbered 4 through 7 can be scheduled for terminal 2. This eliminates fragmented, unschedulable RBs.

[0104] Conversely, if the frequency domain unit groups of multiple devices sharing the same frequency domain resources are not divided according to the same frequency domain unit numbering rules, resource fragmentation will occur. As shown in Figure 7, if RBG division is performed according to the RB numbering rules in Figure 7, the nested structure cannot be maintained, which may cause RB misalignment and fragmented RBs that cannot be scheduled. Terminal 1 is configured only with carrier 1, a bandwidth of 30 RBs, and the RBG configuration parameters are configured as 1 according to Table 1 above, with an RBG size of 2. Terminal 2 is configured with carrier 0 and carrier 1 (carrier 0 is not shown in Figure 7), with a total bandwidth of 59 RBs, and the RBG configuration parameters are configured as 1 according to Table 1 above, with an RBG size of 4. On carrier 1, terminal 1 and terminal 2 divide the RBGs according to different RB numbering rules. Assume that terminal 1 numbers the 30 RBs from 0 to 29, and terminal 2 numbers the 30 RBs from 1 to 30, as shown in Figure 7. The first RBG obtained by terminal 1 on carrier 1 includes RBs numbered 0 and 1, the second RBG includes RBs numbered 2 and 3, the third RBG includes RBs numbered 4 and 5, and so on, until the last RBG includes RBs numbered 28 and 29. The first RBG obtained by terminal 2 on carrier 1 includes RBs numbered 1 to 3, the second RBG includes RBs numbered 4 to 7, the third RBG includes RBs numbered 8 to 11, and so on, until the last RBG includes RBs numbered 28 to 30. As shown in Figure 7, if Terminal 2 is scheduled to the RBG consisting of the 4th to 7th RBs of the 30 RBs (corresponding to the RBs numbered 4 to 7 in the lower portion of Figure 7), then for Terminal 1, the 4th RB (corresponding to the RB numbered 3 in the upper portion of Figure 7) cannot be scheduled because it overlaps with the RBG scheduled for Terminal 2. However, for Terminal 1, since the 3rd to 4th RBs (corresponding to the RBs numbered 2 to 3 in the upper portion of Figure 7) are part of the same RBG, the 3rd RB (corresponding to the RB numbered 2 in the upper portion of Figure 7) cannot be scheduled for Terminal 1 either. This leads to resource fragmentation, which affects resource utilization.

[0105] For the case where multiple devices share the same carrier, the above method can avoid resource fragmentation and inefficient utilization by allowing different devices to obtain their own frequency domain unit groups based on the same frequency domain unit numbering rules.

[0106] In some embodiments, at least two frequency domain resources belong to the same resource pool, and any frequency domain resource or frequency domain unit group on any frequency domain resource combination in the resource pool is scheduled by the same signaling.

[0107] Existing CA operating methods result in some redundant information transmission. For a terminal device configured with CA, reading multiple sets of system information is clearly redundant. If multiple component carriers can be managed centrally, for example by sharing system information, the total system overhead can be significantly reduced. Sharing frequency domain resources can improve scheduling efficiency and reduce downlink control channel overhead. Multiple carriers operate together as a serving cell. The frequency domain resources on multiple carriers act as a large resource pool and are scheduled by a single explicit control channel. This means that resource pooling can be employed to centrally place multiple common frequency domain resources within the same resource pool. For example, multiple frequency domain resources configured for a terminal device can be placed within the same resource pool for unified management and scheduling. A resource pool can contain both independent frequency domain resources and combinations of multiple frequency domain resources. Whether a resource pool contains a single frequency domain resource or a combination of frequency domain resources, frequency domain unit groups can be created. Scheduling instructions for frequency domain unit groups of any granularity within the resource pool can be issued via a unified scheduling signaling signaling sent by the access network device.

[0108] Exemplarily, the resource pool includes three frequency domain resources of different sizes: frequency domain resource 1, frequency domain resource 2, and frequency domain resource 3. Frequency domain resource 1 and frequency domain resource 2 are configured for terminal 1. For terminal 1, frequency domain resource 1 includes frequency domain unit group 1A, frequency domain unit group 1B, and frequency domain unit group 1C, and frequency domain resource 2 includes frequency domain unit group 2A and frequency domain unit group 2B.

[0109] When it is necessary to schedule resources on the frequency domain resource combination of frequency domain resource 1 and frequency domain resource 2 for terminal 1, the access network device can send a signaling, which is used to schedule the frequency domain unit group on frequency domain resource 1 and the frequency domain unit group on frequency domain resource 2. For example, the signaling is used to schedule frequency domain unit group 1A on frequency domain resource 1 for terminal 1 to use, and to schedule frequency domain unit group 2A on frequency domain resource 2 for terminal 1 to use. In this way, there is no need to send two signalings to schedule the frequency domain unit group on frequency domain resource 1 and the frequency domain unit group on frequency domain resource 2 for terminal 1 respectively.

[0110] The above method achieves centralized control of frequency domain resources within the resource pool, simplifies signaling interactions, and reduces signaling overhead. It also makes it easier to centrally plan, manage, and schedule frequency domain resources within the resource pool, improving their utilization efficiency.

[0111] In some embodiments, when a resource pool is not configured, for each of at least two frequency domain resources, the number of frequency domain units included in the frequency domain unit group divided on the frequency domain resource is determined according to the number of frequency domain units included in the frequency domain resource.

[0112] In some embodiments, when a resource pool is configured and the resource pool includes the at least two frequency domain resources described above, the method described above is adopted to determine the number of frequency domain units included in the frequency domain unit group based on the at least two frequency domain resources; then, based on the number of frequency domain units included in the frequency domain unit group, at least one frequency domain unit group is obtained by dividing each of the at least two frequency domain resources. When a resource pool is not configured, for each of the at least two frequency domain resources, based on the number of frequency domain units included in the frequency domain resource, the number of frequency domain units included in the frequency domain unit group divided on the frequency domain resource is determined; then, based on the number of frequency domain units included in the frequency domain unit group divided on the frequency domain resource, at least one frequency domain unit group is obtained by dividing the frequency domain resource.

[0113] That is to say, when a resource pool is configured, the method provided in this application can be used to combine multiple frequency domain resources in the resource pool to determine the size of the frequency domain unit group; when a resource pool is not configured, the existing method can be used to determine the size of the frequency domain unit group based on each frequency domain resource separately.

[0114] In some embodiments, the technical solution provided in the embodiments of the present application is applicable to both uplink and downlink transmission directions. At the same time, the technical solution supports the aggregation combination of TDD (Time Division Duplex) carriers, the aggregation combination of FDD (Frequency Division Duplex) carriers, and the mixed aggregation combination of TDD and FDD carriers. Operators can choose TDD same-standard aggregation, FDD same-standard aggregation, or TDD / FDD mixed aggregation according to the actual needs of network deployment, so that the technical solution can be used in different application scenarios. This solution has a wide range of applicability.

[0115] In some embodiments, the method for determining the size of a frequency domain unit group provided in this application is applicable to both terminal devices and access network devices. That is, both the terminal device and the access network device follow the same method to determine the size of the frequency domain unit group. After determining the size of the frequency domain unit group, the terminal device and the access network device can respectively divide each frequency domain resource into at least one frequency domain unit group based on the size of the frequency domain unit group.

[0116] In some embodiments, when the frequency domain unit group is RBG, the access network device performs resource scheduling based on the RBG obtained by dividing the frequency domain resources with RBG as the granularity. The access network device can send scheduling information to the terminal device to indicate the RBG allocated to the terminal device; accordingly, after receiving the scheduling information sent by the access network device, the terminal device determines the RBG allocated to itself based on the scheduling information.

[0117] In some embodiments, when the frequency domain unit group is a sub-band, the terminal device performs CSI measurement and reporting based on the sub-band obtained by dividing the frequency domain resources with the sub-band as the granularity. The terminal device can send CSI to the access network device to indicate the channel status of one or several sub-bands; accordingly, after receiving the CSI sent by the terminal device, the access network device determines the channel status of the corresponding sub-band based on the CSI.

[0118] The technical solution provided in the embodiment of the present application determines the number of frequency domain units included in the frequency domain unit group based on at least two frequency domain resources, thereby realizing the joint determination of the size of the frequency domain unit group based on multiple frequency domain resources. There is no need to independently determine the size of the frequency domain unit group for each frequency domain resource, thereby reducing the complexity of resource determination.

[0119] In addition, when the frequency domain unit group is RBG, the solution of the present application is used to jointly determine the RBG size based on multiple frequency domain resources, which not only reduces the complexity of determining the RBG size, but also reduces the amount of scheduling information of the frequency domain resources and saves signaling overhead.

[0120] In addition, when the frequency domain unit group is a subband, the solution of the present application is used to jointly determine the subband size based on multiple frequency domain resources, which can not only reduce the complexity of determining the subband size, but also reduce the complexity of CSI measurement, reporting and analysis.

[0121] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0122] Please refer to Figure 8, which shows a block diagram of a resource determination device provided by one embodiment of the present application. This device has the function of implementing the resource determination method described above. This function can be implemented by hardware or by hardware executing corresponding software. This device can be the communication device described above, or it can be provided in a communication device, which can be a terminal device or an access network device. As shown in Figure 8, the device 800 may include: a processing module 810.

[0123] The processing module 810 is configured to determine the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources; wherein each of the frequency domain resources includes at least one frequency domain unit.

[0124] In some embodiments, the frequency domain resources are: a carrier; or an activated bandwidth on a carrier; or a set of frequency domain units with the same transmission direction on a carrier; or a set of frequency domain units with the same transmission direction in the activated bandwidth on a carrier.

[0125] In some embodiments, the processing module 810 is configured to determine the number of frequency domain units included in the frequency domain unit group according to the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

[0126] In some embodiments, the processing module 810 is configured to determine the number of frequency domain units included in the frequency domain unit group according to a configuration parameter and the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

[0127] In some embodiments, the at least two frequency domain resources belong to the same resource pool, and the configuration parameters are configured for the resource pool; or, the configuration parameters are shared by the at least two frequency domain resources; or, the configuration parameters corresponding to each frequency domain resource in the at least two frequency domain resources are the same.

[0128] In some embodiments, the processing module 810 is further configured to divide each of the at least two frequency domain resources into at least one frequency domain unit group according to the number of frequency domain units included in the frequency domain unit group.

[0129] In some embodiments, for any one of the at least two frequency domain resources, the number of frequency domain units included in the first frequency domain unit group obtained by dividing the frequency domain resource is PN start mod P;

[0130] If (N start +N size ) mod P≠0, then the number of the frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is (N start +N size )mod P;

[0131] If (N start +N size ) mod P = 0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is P;

[0132] The number of frequency domain units included in each other frequency domain unit group obtained by dividing the frequency domain resources is P, and the other frequency domain unit group refers to the frequency domain unit group other than the first frequency domain unit group and the last frequency domain unit group;

[0133] Wherein, P is the number of frequency domain units included in the frequency domain unit group determined according to the at least two frequency domain resources, and N start is the number corresponding to the first frequency domain unit of the frequency domain resource, N size is the number of frequency domain units included in the frequency domain resources.

[0134] In some embodiments, N start The number corresponding to the first frequency domain unit of the frequency domain resource on the first resource;

[0135] The frequency domain resource is an activated bandwidth on a carrier, and the first resource is a carrier where the frequency domain resource is located; or

[0136] The frequency domain resource is a set of frequency domain units with the same transmission direction on a carrier, and the first resource is the carrier where the frequency domain resource is located; or

[0137] The frequency domain resource is a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resource is the carrier where the frequency domain resource is located; or

[0138] The frequency domain resources are a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resources are the activated bandwidth on the carrier where the frequency domain resources are located.

[0139] In some embodiments, for any one of the at least two frequency domain resources, when multiple devices share the frequency domain resource, frequency domain unit groups are obtained for the multiple devices based on the same frequency domain unit numbering rule.

[0140] In some embodiments, the at least two frequency domain resources belong to the same resource pool, and any frequency domain resource or frequency domain unit group on any frequency domain resource combination in the resource pool is scheduled by the same signaling.

[0141] In some embodiments, the at least two frequency domain resources belong to the same resource pool, and the processing module 810 is further configured to:

[0142] When the resource pool is not configured, for each of the at least two frequency domain resources, the number of frequency domain units included in the frequency domain unit group obtained by dividing the frequency domain resource is determined according to the number of frequency domain units included in the frequency domain resource.

[0143] In some embodiments, the at least two frequency domain resources are non-contiguous; or, the at least two frequency domain resources are contiguous.

[0144] In some embodiments, the frequency domain unit group is an RBG; or, the frequency domain unit group is a subband.

[0145] The technical solution provided in the embodiment of the present application determines the number of frequency domain units included in the frequency domain unit group based on at least two frequency domain resources, thereby realizing the joint determination of the size of the frequency domain unit group based on multiple frequency domain resources. There is no need to independently determine the size of the frequency domain unit group for each frequency domain resource, thereby reducing the complexity of resource determination.

[0146] Please refer to Figure 9, which shows a schematic diagram of the structure of a communication device provided by one embodiment of the present application. The communication device can be the terminal device described above or the access network device described above. The communication device 900 may include: a processor 901, a transceiver 902, and a memory 903. The processor 901 is configured to implement the functions of the processing module 810 described above.

[0147] The processor 901 includes one or more processing cores. The processor 901 executes various functional applications and information processing by running software programs and modules.

[0148] The transceiver 902 may include a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0149] The memory 903 may be connected to the processor 901 and the transceiver 902 .

[0150] The memory 903 may be used to store a computer program executed by the processor, and the processor 901 is used to execute the computer program to implement each step in the above method embodiment.

[0151] In some embodiments, the processor 901 is configured to determine the number of frequency domain units included in the frequency domain unit group based on at least two frequency domain resources; wherein each of the frequency domain resources includes at least one frequency domain unit.

[0152] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0153] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0154] The embodiment of the present application also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the above-mentioned resource determination method. In some embodiments, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or optical disks, etc. Among them, random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0155] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the above-mentioned resource determination method.

[0156] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor reads and executes the computer program from the computer-readable storage medium to implement the above-mentioned resource determination method.

[0157] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0158] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0159] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0160] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the BLE protocol, the Wi-Fi protocol and related protocols used in future communication systems, and the present application does not limit this.

[0161] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0162] The term “greater than or equal to” mentioned herein may mean greater than or equal to, or greater than, and the term “less than or equal to” may mean less than or equal to, or less than.

[0163] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0164] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0165] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A resource determination method, characterized in that: The method comprises: Determine the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources; Each of the frequency domain resources includes at least one frequency domain unit.

2. The method according to claim 1, characterized in that The frequency domain resources are: carrier; or, The activation bandwidth on the carrier; or, A set of frequency domain units with the same transmission direction on a carrier; or, A set of frequency domain units with the same transmission direction in the activated bandwidth on a carrier.

3. The method according to claim 1 or 2, characterized in that: The step of determining the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources comprises: The number of frequency domain units included in the frequency domain unit group is determined according to the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

4. The method according to claim 3, characterized in that The determining, according to the sum of the numbers of the frequency domain units included in the at least two frequency domain resources, the number of frequency domain units included in the frequency domain unit group comprises: The number of frequency domain units included in the frequency domain unit group is determined according to a configuration parameter and the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

5. The method according to claim 4, characterized in that The at least two frequency domain resources belong to the same resource pool, and the configuration parameter is configured for the resource pool; or, The configuration parameter is shared by the at least two frequency domain resources; or, The configuration parameters corresponding to each frequency domain resource in the at least two frequency domain resources are the same.

6. The method according to any one of claims 1 to 5, characterized in that: After determining the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources, the method further includes: According to the number of frequency domain units included in the frequency domain unit group, at least one frequency domain unit group is obtained by dividing each frequency domain resource in the at least two frequency domain resources.

7. The method according to claim 6, characterized in that For any one frequency domain resource of the at least two frequency domain resources, The number of frequency domain units included in the first frequency domain unit group obtained by dividing the frequency domain resources is PN start mod P; If (N start +N size ) mod P≠0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is (N start +N size )mod P; If (N start +N size )mod P=0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is P; The number of frequency domain units included in each other frequency domain unit group obtained by dividing the frequency domain resources is P, and the other frequency domain unit group refers to any frequency domain unit group except the first frequency domain unit group and the last frequency domain unit group; Wherein, P is the number of frequency domain units included in the frequency domain unit group determined according to the at least two frequency domain resources, and N start is the number corresponding to the first frequency domain unit of the frequency domain resource, N size is the number of frequency domain units included in the frequency domain resources.

8. The method according to claim 7, characterized in that N start A number corresponding to the first frequency domain unit of the frequency domain resource on the first resource; The frequency domain resource is an activated bandwidth on a carrier, and the first resource is a carrier where the frequency domain resource is located; or, The frequency domain resource is a set of frequency domain units with the same transmission direction on a carrier, and the first resource is the carrier where the frequency domain resource is located; or The frequency domain resource is a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resource is the carrier where the frequency domain resource is located; or The frequency domain resources are a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resource is the activated bandwidth on the carrier where the frequency domain resources are located.

9. The method according to any one of claims 1 to 8, characterized in that: For any one of the at least two frequency domain resources, when multiple devices share the frequency domain resource, frequency domain unit groups are obtained for the multiple devices based on the same frequency domain unit numbering rule.

10. The method according to any one of claims 1 to 9, characterized in that: The at least two frequency domain resources belong to the same resource pool, and any frequency domain resource or frequency domain unit group on any frequency domain resource combination in the resource pool is scheduled by the same signaling.

11. The method according to any one of claims 1 to 10, characterized in that: The at least two frequency domain resources belong to the same resource pool, and the method further includes: When the resource pool is not configured, for each of the at least two frequency domain resources, the number of frequency domain units included in the frequency domain unit group obtained by dividing the frequency domain resource is determined according to the number of frequency domain units included in the frequency domain resource.

12. The method according to any one of claims 1 to 11, characterized in that: The at least two frequency domain resources are non-contiguous; or, the at least two frequency domain resources are contiguous.

13. The method according to any one of claims 1 to 12, characterized in that: The frequency domain unit group is a resource block group RBG; or, the frequency domain unit group is a subband.

14. A resource determination device, characterized in that: The device comprises: A processing module, configured to determine the number of frequency domain units included in the frequency domain unit group according to at least two frequency domain resources; Each of the frequency domain resources includes at least one frequency domain unit.

15. The device according to claim 14, characterized in that The frequency domain resources are: carrier; or, The activation bandwidth on the carrier; or, A set of frequency domain units with the same transmission direction on a carrier; or, A set of frequency domain units with the same transmission direction in the activated bandwidth on a carrier.

16. The device according to claim 14 or 15, characterized in that The processing module is used to determine the number of frequency domain units included in the frequency domain unit group according to the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

17. The device according to claim 16, characterized in that The processing module is used to determine the number of frequency domain units included in the frequency domain unit group according to the configuration parameters and the sum of the numbers of the frequency domain units included in the at least two frequency domain resources.

18. The device according to claim 17, characterized in that The at least two frequency domain resources belong to the same resource pool, and the configuration parameter is configured for the resource pool; or, The configuration parameter is shared by the at least two frequency domain resources; or, The configuration parameters corresponding to each frequency domain resource in the at least two frequency domain resources are the same.

19. The device according to any one of claims 14 to 18, characterized in that The processing module is further used to divide each frequency domain resource in the at least two frequency domain resources into at least one frequency domain unit group according to the number of frequency domain units included in the frequency domain unit group.

20. The device according to claim 19, characterized in that For any one frequency domain resource of the at least two frequency domain resources, The number of frequency domain units included in the first frequency domain unit group obtained by dividing the frequency domain resources is PN start mod P; If (N start +N size ) mod P≠0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is (N start +N size )mod P; If (N start +N size )mod P=0, then the number of frequency domain units included in the last frequency domain unit group obtained by dividing the frequency domain resources is P; The number of frequency domain units included in each other frequency domain unit group obtained by dividing the frequency domain resources is P, and the other frequency domain unit group refers to any frequency domain unit group except the first frequency domain unit group and the last frequency domain unit group; Wherein, P is the number of frequency domain units included in the frequency domain unit group determined according to the at least two frequency domain resources, and N start is the number corresponding to the first frequency domain unit of the frequency domain resource, N size is the number of frequency domain units included in the frequency domain resources.

21. The device according to claim 20, characterized in that N start A number corresponding to the first frequency domain unit of the frequency domain resource on the first resource; The frequency domain resource is an activated bandwidth on a carrier, and the first resource is a carrier where the frequency domain resource is located; or, The frequency domain resource is a set of frequency domain units with the same transmission direction on a carrier, and the first resource is the carrier where the frequency domain resource is located; or The frequency domain resource is a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resource is the carrier where the frequency domain resource is located; or The frequency domain resources are a set of frequency domain units with the same transmission direction in the activated bandwidth on the carrier, and the first resource is the activated bandwidth on the carrier where the frequency domain resources are located.

22. The device according to any one of claims 14 to 21, characterized in that For any one of the at least two frequency domain resources, when multiple devices share the frequency domain resource, frequency domain unit groups are obtained for the multiple devices based on the same frequency domain unit numbering rule.

23. The device according to any one of claims 14 to 22, characterized in that The at least two frequency domain resources belong to the same resource pool, and any frequency domain resource or frequency domain unit group on any frequency domain resource combination in the resource pool is scheduled by the same signaling.

24. The device according to any one of claims 14 to 23, characterized in that The at least two frequency domain resources belong to the same resource pool, and the processing module is also used to determine, for each of the at least two frequency domain resources, the number of frequency domain units included in the frequency domain unit group obtained by dividing the frequency domain resource according to the number of frequency domain units included in the frequency domain resource when the resource pool is not configured.

25. The device according to any one of claims 14 to 24, characterized in that The at least two frequency domain resources are non-contiguous; or, the at least two frequency domain resources are contiguous.

26. The device according to any one of claims 14 to 25, characterized in that The frequency domain unit group is a resource block group RBG; or, the frequency domain unit group is a subband.

27. A communication device, characterized in that: The communication device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 13.

28. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the method according to any one of claims 1 to 13.

29. A chip, characterized in that: The chip comprises a programmable logic circuit and / or program instructions, and when the chip is running, it is used to implement the method according to any one of claims 1 to 13.

30. A computer program product, characterized in that The computer program product comprises a computer program, wherein the computer program is stored in a computer-readable storage medium, and a processor reads and executes the computer program from the computer-readable storage medium to implement the method according to any one of claims 1 to 13.

Images