Frequency domain resource allocation method, first terminal, storage medium and product

By receiving downlink control information and frequency domain indication information, the frequency domain resource locations of SBFD and non-SBFD symbols are determined, thus solving the resource overlap problem and improving the transmission performance of user equipment.

CN121665353APending Publication Date: 2026-03-13CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-13
Publication Date
2026-03-13

AI Technical Summary

Technical Problem

In a non-overlapping subband full-duplex system, existing frequency domain resource allocation methods result in overlapping resource allocation between SBFD symbols and non-SBFD symbols, affecting uplink transmission performance.

Method used

By receiving downlink control information, the frequency domain indication information of the physical uplink shared channel is obtained, and the location of frequency domain resources is determined based on the time domain resources and frequency domain indication information to ensure that the frequency domain resources are within the available range and avoid resource overlap.

Benefits of technology

This effectively avoids frequency domain resource overlap, ensures normal uplink transmission, and improves the transmission performance of user equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121665353A_ABST
    Figure CN121665353A_ABST
Patent Text Reader

Abstract

The invention discloses a frequency domain resource allocation method, which is applied to a first terminal and comprises the following steps: receiving downlink control information sent by first equipment; wherein the downlink control information is used for scheduling a physical uplink shared channel; obtaining physical uplink shared channel frequency domain indication information; and determining the frequency domain resource position of the physical uplink shared channel based on the time domain resource occupied by the physical uplink shared channel and the frequency domain indication information. The invention further discloses a first terminal, a computer readable storage medium and a computer program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of communications, and particularly to a frequency domain resource allocation method, a first terminal, a computer-readable storage medium, and a computer program product. Background Technology

[0002] Currently, in subband non-overlapping full duplex (SBFD) systems, the bandwidth available for uplink / downlink transmission differs between SBFD time slots / symbols and non-SBFD time slots / symbols. Figure 1 As shown, slots #0 and #4 are non-SBFD slots / symbols, while slots #1, #2, and #3 are SBFD slots / symbols. Assuming the carrier bandwidth is 100MHz, then the bandwidth available for uplink transmission in slot #4 is 100MHz, and the bandwidth available for downlink transmission in slot #0 is 100MHz. Assuming the bandwidth of the uplink subband (UL subband) configured on the SBFD slots is 20MHz, and the bandwidth of the downlink subband (DL subband) configured on the SBFD slots is 80MHz, then the bandwidth available for uplink transmission in slots #1, #2, and #3 is the middle 20MHz.

[0003] Since the bandwidth available for uplink / downlink transmission differs between SBFD symbols and non-SBFD symbols, the frequency domain resource allocation method employed in related technologies may result in overlapping allocated resources with unavailable resources. Summary of the Invention

[0004] This application provides a frequency domain resource allocation method, a first terminal, a computer-readable storage medium, and a computer program product, such that during multi-slot transmission, the frequency domain resources allocated in the SBFD symbol fall within the range of available frequency domain resources.

[0005] Firstly, a frequency domain resource allocation method is provided, applied to a first terminal, including:

[0006] Receive downlink control information sent by a first device; wherein the downlink control information is used to schedule a physical uplink shared channel;

[0007] Obtain the physical uplink shared channel frequency domain indication information;

[0008] Based on the time-domain resources occupied by the physical uplink shared channel and the frequency-domain indication information, the frequency-domain resource location of the physical uplink shared channel is determined.

[0009] Secondly, a first terminal is provided, the first terminal comprising:

[0010] A receiving module is configured to receive downlink control information sent by a first device; wherein the downlink control information is used to schedule a physical uplink shared channel;

[0011] The acquisition module is used to obtain the physical uplink shared channel frequency domain indication information;

[0012] The processing module is used to determine the frequency domain resource location of the physical uplink shared channel based on the time domain resources occupied by the physical uplink shared channel and the frequency domain indication information.

[0013] Thirdly, a first terminal, the first terminal comprising:

[0014] Memory, used to store executable instructions;

[0015] The processor, when executing executable instructions stored in the memory, implements the frequency domain resource allocation method described above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing one or more programs, which can be executed by one or more processors using the frequency domain resource allocation method described above.

[0017] Fifthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, implements the frequency domain resource allocation method described above.

[0018] Through the above technical solution, when uplink transmission spans SBFD symbols and non-SBFD symbols, the terminal determines the location of frequency domain resources in SBFD symbols and non-SBFD symbols, so that the allocated frequency domain resources fall within the range of usable frequency domain resources, thus ensuring UE transmission performance. Attached Figure Description

[0019] Figure 1 A schematic diagram of frequency domain resources provided for related technologies;

[0020] Figure 2 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0021] Figure 3 A schematic diagram illustrating the allocation of frequency domain resources for related technologies;

[0022] Figure 4 A flowchart illustrating the frequency domain resource allocation method provided in this application embodiment;

[0023] Figure 5A schematic diagram of frequency domain resource allocation provided in the embodiments of this application. Figure 1 ;

[0024] Figure 6 A schematic diagram of frequency domain resource allocation provided in the embodiments of this application. Figure 2 ;

[0025] Figure 7 A schematic diagram of frequency domain resource allocation provided in the embodiments of this application. Figure 3 ;

[0026] Figure 8 A schematic diagram of frequency domain resource allocation provided in the embodiments of this application. Figure 4 ;

[0027] Figure 9 A schematic block diagram of a first terminal provided for an embodiment of this application;

[0028] Figure 10 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0030] Figure 2 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0031] like Figure 2 As shown, the wireless communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0032] It should be understood that the embodiments of this application are only illustrated by way of example using a wireless communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) systems, Narrow Band Internet of Things (NB-IoT) systems, enhanced Machine-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

[0033] exist Figure 2 In the wireless communication system 100 shown, network device 120 may be an access network device that communicates with terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with terminal device 110 (e.g., UE) located within that coverage area.

[0034] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0035] Terminal device 110 includes, but is not limited to, any terminal device that is connected to network device 120 or other terminal devices via wired or wireless connection.

[0036] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0037] Terminal device 110 can be used for device-to-device (D2D) communication.

[0038] Figure 2 An exemplary illustration shows a base station and two terminal devices. Optionally, the wireless communication system 100 may include multiple base stations, and each base station may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0039] It should be noted that, Figure 2This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0040] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0041] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0042] Before explaining this application, the frequency domain resource allocation scheme in the related art is described below:

[0043] In a Time Division Duplex (TDD) system, on a single symbol within a carrier, both the base station and the terminal can only perform uplink or downlink transmission, not both simultaneously. As a result, the uplink / downlink transmission conversion delay in a TDD system is relatively large, and the uplink capacity and coverage are limited. To reduce the transmission delay and improve uplink coverage and capacity in a TDD system, SBFD technology divides the carrier bandwidth into several subbands that occupy different frequency resources, allowing the base station to perform uplink and downlink transmissions simultaneously on a single symbol.

[0044] NR supports two frequency domain resource allocation types: Resource Allocation (RA) Type 0 and RA Type 1. RA Type 0 is a resource allocation mechanism based on Resource Block Groups (RBGs). Specifically, it uses the starting frequency domain position of the Bandwidth Part (BWP) as the starting point and divides all PRBs in the BWP into N groups with RBG granularity. RBG In DCI, the FDRA field carries an RBG of length N. RBG The bitmap represents the network's allocation mechanism. Each bit corresponds to an RBG (Resource Block Group). A bit value of 1 indicates that the corresponding RBG has been allocated to the User Equipment (UE). Through RA Type 0, the network can allocate non-contiguous frequency domain resources to the terminal. RA Type 1 is a resource allocation mechanism based on Resource Indicator Value (RIV), used to allocate a set of contiguous Virtual Resource Blocks (VRBs) to the terminal. Specifically, the FDRA field in the DCI carries a Resource Indicator Value (RIV), and the starting VRB and the number of RBs can be calculated from the RIV.

[0045] It should be noted that, with Figure 1Taking the SBFD symbols and non-SBFD symbols available for uplink / downlink transmission as an example, when the base station schedules / configures the terminal to perform uplink transmissions on multiple time slots, such as PUSCH repetition, TBoMS, configured grant, etc., the PUSCH transmission may span SBFD symbols and non-SBFD symbols. In this case, if the frequency domain resource allocation method in related technologies is used, multiple repetitions / transmissions will be allocated the same frequency domain resource location, which may lead to the overlap of frequency domain resources allocated on SBFD symbols with unavailable resources, such as... Figure 3 As shown, in the SBFD symbol, the frequency domain resource (PUSCH Rep#0) corresponding to PUSCH falls in the DL subband of Slot#3, and PUSCH transmission cannot be performed normally.

[0046] Figure 4 This is a flowchart illustrating a frequency domain resource allocation method provided in an embodiment of this application, as shown below. Figure 4 As shown, this method is applied to Figure 2 The terminal device 110 in the wireless communication system 100 shown includes the following method:

[0047] Step 401: Receive downlink control information sent by the first device.

[0048] Downlink control information is used to schedule the physical uplink shared channel.

[0049] In this embodiment of the application, the first terminal, namely Figure 2 Terminal device 110 in the middle receives the first device, that is Figure 2 The first message sent by network device 120 in the middle; wherein the first message includes DCI.

[0050] In some embodiments, the DCI includes scheduling information for the data channel, which may include transmission parameters for the data channel. Based on these transmission parameters, network devices and terminal devices transmit data through the data channel.

[0051] In some embodiments, the first message may be a radio resource control (RRC) message, a broadcast message, a system message, or a medium access control (MAC) control element (CE) message.

[0052] Step 402: Obtain the physical uplink shared channel frequency domain indication information.

[0053] In some embodiments, the frequency domain indication information includes first information and second information;

[0054] The first information is used to indicate the resource allocation of the physical uplink shared channel of the reference first frequency domain resource, or the RB index; the second information is used to indicate the frequency domain resource interval index allocated on the second time domain resource; here, the frequency domain resource allocation is the size of the reference first frequency domain resource, and the frequency domain resource allocation interval is the bandwidth size of the reference first frequency domain resource and the second frequency domain resource.

[0055] Here, the first frequency domain resource includes the UL frequency domain resource of the first time domain resource, such as the UL usable PRB or SBFD uplink subband, and the size of the first frequency domain resource is X1. The first time domain resource includes time domain resources configured as downlink or flexible symbols in the time division duplex cycle, that is, time domain resources configured as DL slots / symbols and / or flexible slots / symbols in the TDD cycle, and configured with uplink resources (SBFD uplink subband), which are SBFD symbols.

[0056] Here, the second frequency domain resource includes the UL frequency domain resource of the second time domain resource, such as UL BWP, and the size of the second frequency domain resource is X2. The second time domain resource includes time domain resources configured as uplink symbols in the time division duplex cycle and configured as UL slots / symbols in the TDD cycle, that is, non-SBFD symbols.

[0057] It should be noted that the network side determines the bit length of the physical shared channel frequency domain indication information based on the bandwidth of the second frequency domain resources, such as the bit size of the frequency domain resource allocation field in DCI.

[0058] In some embodiments, the second frequency domain resource includes M frequency domain resource intervals; wherein M is a positive integer, that is, M bits of second information are used to indicate the M frequency domain resource intervals divided by the second frequency domain resource.

[0059] Step 403: Based on the time-domain resources and frequency-domain indication information occupied by the physical uplink shared channel, determine the frequency-domain resource location of the physical uplink shared channel.

[0060] This application discloses a frequency domain resource allocation method applied to a first terminal. The method includes: receiving downlink control information sent by a first device; wherein the downlink control information is used to schedule a physical uplink shared channel; obtaining frequency domain indication information of the physical uplink shared channel; and determining the frequency domain resource location of the physical uplink shared channel based on the time domain resources occupied by the physical uplink shared channel and the frequency domain indication information. In other words, in the case of uplink transmission across SBFD symbols and non-SBFD symbols, the terminal determines the frequency domain resource location among the SBFD symbols and non-SBFD symbols, ensuring that the allocated frequency domain resources fall within the usable frequency domain resource range, thereby guaranteeing UE transmission performance.

[0061] In some embodiments, step 403, determining the frequency domain resource location of the physical uplink shared channel based on the time domain resources and frequency domain indication information occupied by the physical uplink shared channel, can be achieved through steps A1 and A2, or through step A3:

[0062] Step A1: If the time domain resources of the physical uplink shared channel are located in the second time domain resources, determine the frequency domain resource range based on the second information.

[0063] Step A2: Based on the first information, determine the location of the physical uplink shared channel frequency domain resources within the frequency domain resource interval.

[0064] Step A3: If the time domain resource of the physical uplink shared channel is located in the first time domain resource, determine the location of the physical uplink shared channel frequency domain resource within the first frequency domain resource based on the first information.

[0065] In some embodiments, determining the frequency domain resource interval based on the second information in step A1 can be achieved through step B1, or step B2, or step B3, or step B4, or step B5, or step B7, or step B8:

[0066] Step B1: If M is greater than N and m equals 0, determine the physical resource block index of the frequency domain resource interval with index m as the index from the first physical resource block (PRB) index (PRB 0) of the second frequency domain resource to the first PRB index of the second frequency domain resource plus the size of the first frequency domain resource minus 1.

[0067] in, X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

[0068] Step B2: If M is greater than N, m is greater than 0 and less than M, determine the physical resource block index of the frequency domain resource interval with index m as the index from the first physical resource block index of the second frequency domain resource + X1*m + L*m to the first physical resource block index of the second frequency domain resource + X1*(m+1) + L*m-1.

[0069] in,

[0070] Here, L is the distance between two adjacent frequency domain resource intervals, for example, ... Figure 5 The distances between M0 and M1, and between M2 and M1 are shown.

[0071] For example, with Figure 1 Taking the SBFD symbols and non-SBFD symbols available for uplink / downlink transmission as an example, in the uplink transmission scenario, the two repeated transmissions of PUSCH are located in the SBFD symbols and non-SBFD symbols respectively. Using the frequency domain resource allocation method of this application, the first information from the network side allocates PUSCH resources within the X1 bandwidth range according to the first frequency domain resource indication; that is, as shown... Figure 5 As shown, the frequency domain resource (PUSCH Rep#0) corresponding to PUSCH falls within the middle UL subband of Slot#3. The second information on the network side indicates that the second frequency domain resource interval index is 0. Therefore, the PUSCH resource allocation on the second time domain resource is the PUSCH resource allocation within the frequency domain resource interval index 0, corresponding to the X1 bandwidth indicated by the first information, i.e., as shown... Figure 5 As shown, the frequency domain resource (PUSCH Rep#1) corresponding to PUSCH falls within the frequency domain resource range corresponding to M0 of Slot#4, so that PUSCH transmission can proceed normally.

[0072] Step B3: If M equals N, X2 divides X1, and m is 0, determine the PRB index of the frequency domain resource interval with index m as the range from the first PRB index of the second frequency domain resource to the first PRB index of the second frequency domain resource + X1-1.

[0073] Step B4: If M equals N, X2 divides X1, and m is greater than 0 and less than M, determine the PRB index of the frequency domain resource interval with index m as the range from the first PRB index of the second frequency domain resource + X1*m to the first PRB index of the second frequency domain resource + X1*(m+1).

[0074] It should be noted that if the first frequency domain resource is divisible by the second frequency domain resource, it is divided into M frequency domain resource intervals according to the PRB index of the second frequency domain resource in ascending or descending order. The size of each frequency domain resource interval is equal to the size of the first frequency domain resource, and the M frequency domain resource intervals do not overlap. In this case, all the second frequency domain resource PRBs are allocated into the M frequency domain resource intervals.

[0075] For example, if X2 is divisible by X1, then the carrier bandwidth corresponding to Slot#4 symbol / time slot is allocated as follows: Figure 6 The four consecutive frequency domain resource intervals shown are... Figure 6 M0, M1, M2, and M3.

[0076] For example, with Figure 1 Taking the SBFD symbols and non-SBFD symbols available for uplink / downlink transmission as an example, in the uplink transmission scenario, the two repeated transmissions of PUSCH are located in the SBFD symbols and non-SBFD symbols respectively. Using the frequency domain resource allocation method of this application, the first information from the network side allocates PUSCH resources within the X1 bandwidth range according to the first frequency domain resource indication; that is, as shown... Figure 6 As shown, the frequency domain resource (PUSCH Rep#0) corresponding to PUSCH falls within the middle UL subband of Slot#3. The second information on the network side indicates that the second frequency domain resource interval index is 0. Therefore, the PUSCH resource allocation on the second time domain resource is the PUSCH resource allocation within the frequency domain resource interval index 0, corresponding to the X1 bandwidth indicated by the first information, i.e., as shown... Figure 6 As shown, the frequency domain resource (PUSCH Rep#1) corresponding to PUSCH falls within the frequency domain resource range corresponding to M0 of Slot#4, so that PUSCH transmission can proceed normally.

[0077] Step B5: If M equals N, X2 cannot divide X1, and m is 0, determine the PRB index of the frequency domain resource interval with index m as the range from the first PRB index of the second frequency domain resource to the first PRB index of the second frequency domain resource + X1-1.

[0078] Step B6: If M equals N, X2 cannot divide X1, and m is greater than 0 and less than M, determine the PRB index of the frequency domain resource interval with index m as the range from the first PRB index of the second frequency domain resource + X1*m to the first PRB index of the second frequency domain resource + X1*(m+1).

[0079] It should be noted that if the first frequency domain resource is not divisible by the second frequency domain resource, it is divided into M frequency domain resource intervals according to the PRB index of the second frequency domain resource in ascending or descending order. The size of each frequency domain resource interval is equal to the size of the first frequency domain resource, and the M frequency domain resource intervals do not overlap. In this case, some PRBs of the second frequency domain resource are not included in the M frequency domain resource intervals.

[0080] For example, if X2 is not divisible by X1, then the carrier bandwidth corresponding to Slot#4 symbol / time slot is allocated as follows: Figure 7 The four consecutive frequency domain resource intervals shown are... Figure 7 M0, M1, M2, and M3; meanwhile, some PRBs in the carrier bandwidth corresponding to Slot#4 symbol / time slot were not allocated into the M frequency domain resource intervals, that is, some PRBs above M3.

[0081] For example, with Figure 1 Taking the SBFD symbols and non-SBFD symbols available for uplink / downlink transmission as an example, in the uplink transmission scenario, the two repeated transmissions of PUSCH are located in the SBFD symbols and non-SBFD symbols respectively. Using the frequency domain resource allocation method of this application, the first information from the network side allocates PUSCH resources within the X1 bandwidth range according to the first frequency domain resource indication; that is, as shown... Figure 7 As shown, the frequency domain resource (PUSCH Rep#0) corresponding to PUSCH falls within the middle UL subband of Slot#3. The second information on the network side indicates that the second frequency domain resource interval index is 0. Therefore, the PUSCH resource allocation on the second time domain resource is the PUSCH resource allocation within the frequency domain resource interval index 0, corresponding to the X1 bandwidth indicated by the first information, i.e., as shown... Figure 7 As shown, the frequency domain resource (PUSCH Rep#1) corresponding to PUSCH falls within the frequency domain resource range corresponding to M0 of Slot#4, so that PUSCH transmission can proceed normally.

[0082] Step B7: If M is less than N and m is 0, determine the PRB index of the frequency domain resource interval with index m as the range from the first PRB index of the second frequency domain resource to the first PRB index of the second frequency domain resource + X1-1; where X1 represents the size of the first frequency domain resource.

[0083] Step B8: If M is less than N, and m is greater than 0 and less than M, determine the PRB index of the frequency domain resource interval with index m as from the first PRB index of the second frequency domain resource + X1*mL*m to the first PRB index of the second frequency domain resource + X1*(m+1)-L*m-1.

[0084] in, It represents an upward divisibility function.

[0085] Here, L is the overlap distance between two adjacent frequency domain resource intervals, for example, as Figure 8 The overlapping distances between M0 and M1, M1 and M2, M2 and M3, and M3 and M4 are shown.

[0086] For example, with Figure 1 Taking the SBFD symbols and non-SBFD symbols available for uplink / downlink transmission as an example, in the uplink transmission scenario, the two repeated transmissions of PUSCH are located in the SBFD symbols and non-SBFD symbols respectively. Using the frequency domain resource allocation method of this application, the first information from the network side allocates PUSCH resources within the X1 bandwidth range according to the first frequency domain resource indication; that is, as shown... Figure 8 As shown, the frequency domain resource (PUSCH Rep#0) corresponding to PUSCH falls within the middle UL subband of Slot#3. The second information on the network side indicates that the second frequency domain resource interval index is 0. Therefore, the PUSCH resource allocation on the second time domain resource is the PUSCH resource allocation within the frequency domain resource interval index 0, corresponding to the X1 bandwidth indicated by the first information, i.e., as shown... Figure 8 As shown, the frequency domain resource (PUSCH Rep#1) corresponding to PUSCH falls within the frequency domain resource range corresponding to M0 of Slot#4, so that PUSCH transmission can proceed normally.

[0087] Embodiments of this application provide a first terminal, which can be used to implement... Figure 4 A corresponding embodiment provides a frequency domain resource allocation method, referring to... Figure 9 As shown, the first terminal 900 includes:

[0088] The receiving module 901 is used to receive downlink control information sent by the first device; wherein the downlink control information is used to schedule the physical uplink shared channel;

[0089] Module 902 is used to obtain physical uplink shared channel frequency domain indication information;

[0090] The processing module 903 is used to determine the frequency domain resource location of the physical uplink shared channel based on the time domain resources and frequency domain indication information occupied by the physical uplink shared channel.

[0091] In other embodiments of this application, the frequency domain indication information includes first information and second information; wherein, the first information is used to indicate the resource allocation of the physical uplink shared channel referencing the first frequency domain resource; the second information is used to indicate the frequency domain resource interval index allocated on the second time domain resource; the first frequency domain resource includes the uplink frequency domain resource of the first time domain resource; the second frequency domain resource includes the uplink frequency domain resource of the second time domain resource; the first time domain resource includes time domain resources configured with time division duplex period as downlink or flexible symbol; the second time domain resource includes time domain resources configured with time division duplex period as uplink symbol.

[0092] In other embodiments of this application, the processing module 903 is configured to determine the frequency domain resource interval based on the second information if the time domain resource of the physical uplink shared channel is located in the second time domain resource; and to determine the location of the physical uplink shared channel frequency domain resource within the frequency domain resource interval based on the first information.

[0093] In other embodiments of this application, the processing module 903 is used to determine the location of the physical uplink shared channel frequency domain resource within the first frequency domain resource based on first information if the time domain resource of the physical uplink shared channel is located in the first time domain resource.

[0094] In other embodiments of this application, the second frequency domain resource includes M frequency domain resource intervals; where M is a positive integer.

[0095] In other embodiments of this application, the processing module 903 is configured to, if M is greater than N and m equals 0, determine the physical resource block index of the frequency domain resource interval with index m as the sum of the first physical resource block index of the second frequency domain resource and the first physical resource block index of the second frequency domain resource plus the size of the first frequency domain resource minus 1; wherein... X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

[0096] In other embodiments of this application, the processing module 903 is configured to, if M is greater than N, m is greater than 0 and less than M, determine the physical resource block index of the frequency domain resource interval with index m as being from the first physical resource block index of the second frequency domain resource + X1*m + L*m to the first physical resource block index of the second frequency domain resource + X1*(m+1) + L*m-1; wherein...

[0097] In other embodiments of this application, the processing module 903 is configured to determine, if M equals N, X2 divides X1, and m is 0, the physical resource block index of the frequency domain resource interval with index m is from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; wherein... X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

[0098] In other embodiments of this application, the processing module 903 is used to determine the physical resource block index of the frequency domain resource interval with index m as follows: if M equals N, X2 can divide X1, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is from the first physical resource block index of the second frequency domain resource + X1*m to the first physical resource block index of the second frequency domain resource + X1*(m+1).

[0099] In other embodiments of this application, the processing module 903 is configured to determine, if M equals N, X2 is not divisible by X1, and m is 0, the physical resource block index of the frequency domain resource interval with index m as the index from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; wherein... X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

[0100] In other embodiments of this application, the processing module 903 is used to determine the physical resource block index of the frequency domain resource interval with index m as follows: if M equals N, X2 cannot divide X1, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is from the first physical resource block index of the second frequency domain resource + X1*m to the first physical resource block index of the second frequency domain resource + X1*(m+1).

[0101] In other embodiments of this application, the processing module 903 is configured to, if M is less than N and m is 0, determine the physical resource block index of the frequency domain resource interval with index m as the range from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; wherein X1 represents the size of the first frequency domain resource; wherein... X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

[0102] In other embodiments of this application, the processing module 903 is configured to, if M is less than N, and m is greater than 0 and less than M, determine the physical resource block index of the frequency domain resource interval with index m as being from the first physical resource block index of the second frequency domain resource + X1*mL*m to the first physical resource block index of the second frequency domain resource + X1*(m+1)-L*m-1; wherein... It represents an upward divisibility function.

[0103] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0104] It should be noted that, in the embodiments of this application, if the above-described frequency domain resource allocation method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0105] Figure 10 This is a schematic structural diagram of a communication device 1000 provided in an embodiment of this application. This communication device can be a first terminal. Figure 10 The communication device 1000 shown includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0106] Optionally, such as Figure 10 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 can retrieve and run computer programs from the memory 1020 to implement the methods described in this embodiment.

[0107] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.

[0108] Optionally, such as Figure 10 As shown, the communication device 1000 may also include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0109] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0110] Optionally, the communication device 1000 may specifically be the first terminal in the embodiments of this application, and the communication device 1000 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0111] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0112] As one embodiment, the processor may include one or more general-purpose central processing units (CPUs). Each of these processors may be a single-core processor or a multi-core processor. Here, "processor" may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., executing instructions).

[0113] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), or flash memory. The volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0114] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0115] This application also provides a computer-readable storage medium for storing computer programs.

[0116] The computer-readable storage medium can be applied to the terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0117] This application also provides a computer program product, including a computer program that can be executed by the processor of a first terminal 900 or a communication device 1000 to complete the steps described in any of the aforementioned methods.

[0118] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0119] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0120] The frequency domain resource allocation method, first terminal, computer-readable storage medium, and computer program product provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0121] It should be understood that the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0122] Unless otherwise specified, the first terminal may perform any step in the embodiments of this application by means of its processor. Unless otherwise specified, the embodiments of this application do not limit the order in which the first terminal performs the following steps. Furthermore, the methods used to process data in different embodiments may be the same or different methods.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0124] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0125] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0126] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0127] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0128] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0129] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0130] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0131] The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0132] It should be noted that in the various embodiments involved in this application, all steps or some steps may be performed, as long as a complete technical solution can be formed.

[0133] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A frequency domain resource allocation method, characterized in that, Applied to a first terminal, the method includes: Receive downlink control information sent by a first device; wherein the downlink control information is used to schedule a physical uplink shared channel; Obtain the physical uplink shared channel frequency domain indication information; Based on the time-domain resources occupied by the physical uplink shared channel and the frequency-domain indication information, the frequency-domain resource location of the physical uplink shared channel is determined.

2. The method according to claim 1, characterized in that, The frequency domain indication information includes first information and second information; Wherein, the first information is used to indicate the resource allocation of the physical uplink shared channel with reference to the first frequency domain resource; the second information is used to indicate the frequency domain resource interval index allocated on the second time domain resource; the first frequency domain resource includes the uplink frequency domain resource of the first time domain resource; the second frequency domain resource includes the uplink frequency domain resource of the second time domain resource; the first time domain resource includes time domain resources configured with time division duplex period as downlink or flexible symbol; the second time domain resource includes time domain resources configured with time division duplex period as uplink symbol.

3. The method according to claim 2, characterized in that, The step of determining the frequency domain resource location of the physical uplink shared channel based on the time domain resources occupied by the physical uplink shared channel and the frequency domain indication information includes: If the time domain resources of the physical uplink shared channel are located in the second time domain resources, the frequency domain resource range is determined based on the second information; Based on the first information, the location of the physical uplink shared channel frequency domain resource within the frequency domain resource interval is determined.

4. The method according to claim 2, characterized in that, The step of determining the frequency domain resource location of the physical uplink shared channel based on the time domain resources occupied by the physical uplink shared channel and the frequency domain indication information includes: If the time domain resource of the physical uplink shared channel is located in the first time domain resource, the location of the physical uplink shared channel frequency domain resource within the first frequency domain resource is determined based on the first information.

5. The method according to claim 3, characterized in that, The second frequency domain resource includes M frequency domain resource intervals; wherein M is a positive integer.

6. The method according to claim 5, characterized in that, The step of determining the frequency domain resource interval based on the second information includes: If M is greater than N and m equals 0, the physical resource block index of the frequency domain resource interval with index m is determined by the sum of the first physical resource block index of the second frequency domain resource and the first physical resource block index of the second frequency domain resource plus the size of the first frequency domain resource minus 1. in, X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

7. The method according to claim 6, characterized in that, The method further includes: If M is greater than N, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource + X1*m + L*m to the first physical resource block index of the second frequency domain resource + X1*(m+1) + L*m-1. in, 8. The method according to claim 5, characterized in that, The step of determining the frequency domain resource interval based on the second information includes: If M equals N, X2 divides X1, and m is 0, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; in, X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

9. The method according to claim 8, characterized in that, The method further includes: If M equals N, X2 divides X1, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource + X1*m to the first physical resource block index of the second frequency domain resource + X1*(m+1).

10. The method according to claim 5, characterized in that, The step of determining the frequency domain resource interval based on the second information includes: If M equals N, X2 cannot divide X1, and m is 0, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; in, X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

11. The method according to claim 10, characterized in that, The method further includes: If M equals N, X2 cannot divide X1, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource + X1*m to the first physical resource block index of the second frequency domain resource + X1*(m+1).

12. The method according to claim 5, characterized in that, The step of determining the frequency domain resource interval based on the second information includes: If M is less than N and m is 0, the physical resource block index of the frequency domain resource interval with index m is determined as the index from the first physical resource block index of the second frequency domain resource to the first physical resource block index of the second frequency domain resource + X1-1; where X1 represents the size of the first frequency domain resource. in, X2 represents the size of the second frequency domain resource, and X1 represents the size of the first frequency domain resource. The function represents the downward divisibility function, where m is the index of the frequency domain resource interval.

13. The method according to claim 12, characterized in that, The method further includes: If M is less than N, and m is greater than 0 and less than M, the physical resource block index of the frequency domain resource interval with index m is determined to be from the first physical resource block index of the second frequency domain resource + X1*mL*m to the first physical resource block index of the second frequency domain resource + X1*(m+1)-L*m-1. in, It represents an upward divisibility function.

14. A first terminal, characterized in that, The first terminal includes: A receiving module is configured to receive downlink control information sent by a first device; wherein the downlink control information is used to schedule a physical uplink shared channel; The acquisition module is used to obtain the physical uplink shared channel frequency domain indication information; The processing module is used to determine the frequency domain resource location of the physical uplink shared channel based on the time domain resources occupied by the physical uplink shared channel and the frequency domain indication information.

15. A first terminal, characterized in that, The first terminal includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the frequency domain resource allocation method according to any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the frequency domain resource allocation method according to any one of claims 1 to 13.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the frequency domain resource allocation method according to any one of claims 1 to 13.