WO2023137972A1 - 一种资源配置方法、电子设备和存储介质 - Google Patents

一种资源配置方法、电子设备和存储介质 Download PDF

Info

Publication number
WO2023137972A1
WO2023137972A1 PCT/CN2022/100526 CN2022100526W WO2023137972A1 WO 2023137972 A1 WO2023137972 A1 WO 2023137972A1 CN 2022100526 W CN2022100526 W CN 2022100526W WO 2023137972 A1 WO2023137972 A1 WO 2023137972A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
pucch resource
offset
resource set
configuration table
Prior art date
Application number
PCT/CN2022/100526
Other languages
English (en)
French (fr)
Inventor
刘文丰
戴博
胡有军
陈梦竹
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023137972A1 publication Critical patent/WO2023137972A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the technical field of wireless communication, and in particular to a resource configuration method, electronic equipment and storage media.
  • Reduced Capability is a new type of IoT technology established by the 3GPP standardization organization. It is mainly aimed at mid-range IoT devices such as industrial wireless sensors, video surveillance, and wearable devices. It has the characteristics of low complexity, low cost, low power consumption, and compact size. Input Multiple Output, MIMO) layer number, modulation order and other aspects are simplified to achieve a compromise between cost and performance.
  • MIMO Multiple Output
  • RedCap technology needs to achieve the least impact on network performance under the premise of meeting the use case requirements.
  • the maximum supported bandwidth of NR conventional terminals is 100M.
  • the maximum supported bandwidth of RedCap terminals is reduced to 20M.
  • the physical uplink control channel (PUCCH) resources of RedCap terminals located on both sides of the bandwidth will use the Physical Uplink Share Channel (PUS) of NR conventional terminals.
  • PUS Physical Uplink Share Channel
  • the 3GPP standard meeting decided to cancel the RedCap PUCCH frequency hopping in the initial access stage.
  • the new SIB signaling is used to indicate the enablement or cancellation of the PUCCH frequency hopping of the RedCap terminal.
  • the cancellation of the PUCCH frequency hopping makes the PUCCH resources of the RedCap terminal concentrate on one side of the bandwidth, reducing the problem of PUSCH resource fragmentation.
  • NR conventional terminals use frequency hopping to transmit PUCCH resources by default in the initial access phase to achieve greater uplink coverage and better transmission performance.
  • the SIB signaling indicates to cancel the frequency hopping of the RedCap terminal
  • the RedCap terminal transmits PUCCH without frequency hopping.
  • the existing PUCCH resource configuration method for NR conventional terminals cannot be directly applied to the RedCap terminal.
  • each PUCCH resource set configured for the RedCap terminal should also include 16 PUCCH resources.
  • terminals based on PUCCH frequency-hopping transmission and terminals based on PUCCH non-frequency-hopping transmission multiplex the same resource block to transmit PUCCH
  • the non-orthogonal nature of the transmission sequence makes it impossible for the two types of terminals to achieve code division multiplexing, thereby reducing network capacity.
  • the main purpose of the embodiments of the present application is to provide a resource allocation method, electronic equipment, and a storage medium.
  • An embodiment of the present application provides a resource configuration method, wherein the method includes: determining edge position information of PUCCH resources according to base station signaling; determining a common PUCCH resource set in a PUCCH resource set configuration table according to the edge position information and an SIB message; determining a PUCCH resource according to the edge position information and a physical resource unit offset corresponding to the common PUCCH resource set.
  • the embodiment of the present application also provides an electronic device, wherein the electronic device includes: one or more processors; a memory for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors implement any method described in the embodiments of the present application.
  • the embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs are executed by the one or more processors to implement any method described in the embodiments of the present application.
  • FIG. 1 is a flow chart of a resource allocation method provided by an embodiment of the present application
  • FIG. 2 is a flow chart of another resource allocation method provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a resource configuration device provided in an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the RedCap terminal and the NR regular terminal share the same public network, and the PUCCH resources of the RedCap terminal located on both sides of the bandwidth will divide the PUSCH resource of the NR regular terminal into multiple sub-parts, resulting in the problem of PUSCH resource fragmentation, thereby reducing the uplink peak data rate of the NR regular terminal.
  • the common PUCCH resource set configuration table 2.1 used by NR conventional terminals in the initial stage is as follows:
  • NR conventional terminals use frequency hopping to transmit PUCCH resources by default in the initial access phase to achieve greater uplink coverage and better transmission performance. Specifically, based on the common PUCCH resource set configuration table 2.1 maintained by the base station and the terminal, the NR conventional terminal first determines a common PUCCH resource set (each PUCCH resource set includes 16 PUCCH resources) according to the PUCCH resource configuration number notified by SIB1, and then determines a PUCCH resource whose index is r PUCCH , 0 ⁇ r PUCCH ⁇ 15 in the common PUCCH resource set by combining DCI and CCE. For each PUCCH resource index r PUCCH , the corresponding PUCCH resource frequency domain position and initial cyclic offset configuration are:
  • the first hop PRB index of NR regular terminal PUCCH transmission is The second hop PRB index is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS ;
  • the first hop PRB index of NR regular terminal PUCCH transmission is The second hop PRB index is The initial cyclic offset index in the initial cyclic offset set is (r PUCCH -8) mod N CS ;
  • PRB is used to describe the relative position of resource blocks in actual transmission, Indicates the number of PRBs configured for the initial uplink BWP of the RedCap terminal, Indicates the PRB offset defined in Table 2.1, N CS indicates the total number of indexes in the initial cyclic offset set, It means rounding down, and mod means modulo operation.
  • each PUCCH resource set configured for the RedCap terminal should also include 16 PUCCH resources.
  • terminals based on PUCCH frequency hopping transmission and terminals based on PUCCH non-frequency hopping transmission are multiplexed to transmit PUCCH on the same resource block, the non-orthogonality of the transmission sequence makes it impossible for the two types of terminals to achieve code division multiplexing, thereby reducing network capacity.
  • Fig. 1 is a flow chart of a resource configuration method provided by the embodiment of the present application.
  • the embodiment of the present application is applicable to the configuration of RedCaps terminal transmission resources.
  • the method can be executed by a resource configuration device, which can be implemented by software and/or hardware methods, and is generally integrated in the RedCap terminal.
  • the method provided by the embodiment of the present application specifically includes the following steps:
  • Step 110 determine the edge position information of the PUCCH resource according to the base station signaling.
  • the edge position information may be the position of the PUCCH resource used by the RedCap terminal in a partial bandwidth (Bandwidth Part, BWP), and the edge position information may indicate the upper edge, the lower edge, and both sides of the uplink BWP, or the upper edge and the lower edge of the uplink BWP, or a certain side of the uplink BWP, and both sides of the uplink BWP.
  • BWP Bandwidth Part
  • the RedCap terminal can indicate the edge position information of the PUCCH resource used by the base station signaling, and can determine the position of the PUCCH resource located on the uplink BWP through the base station signaling, for example, it can be the upper edge, lower edge, and both sides of the uplink BWP, or the upper edge and lower edge of the uplink BWP, or a certain side of the uplink BWP, or both sides of the uplink BWP.
  • Step 120 Determine the common PUCCH resource set in the PUCCH resource set configuration table according to the edge position information and the SIB message.
  • the RedCap terminal can use the determined edge location information and a system information block (System Information Blocks, SIB) message to jointly determine a common PUCCH resource set in the PUCCH resource set configuration table, where the PUCCH resource set configuration table can be jointly maintained by the RedCap terminal and the base station.
  • SIB System Information Blocks
  • Step 130 Determine the PUCCH resource according to the edge position information and the physical resource unit offset corresponding to the common PUCCH resource set.
  • the physical resource unit offset configured in the common PUCCH resource set can be determined, and the position of the PUCCH resource used by the RedCap terminal can be determined according to the physical resource unit offset and edge position information, for example, parameters such as the frequency domain position of the PUCCH resource used by the RedCap terminal and the initial cyclic offset configuration can be determined.
  • the edge position information of the PUCCH resource is determined through base station signaling, the common PUCCH resource set is determined in the PUCCH resource set configuration table using the edge position information and the SIB message, and the PUCCH resource is determined by using the edge position information and the physical resource unit offset corresponding to the public PUCCH resource set, so as to realize the PUCCH resource configuration of the RedCap terminal, reduce the impact on the performance of the public network, and improve the network capacity.
  • the base station signaling includes at least one of the following: the remaining minimum system information SIB1, downlink control information DCI, and other system information.
  • the remaining minimum system message SIB1 or downlink control information can be used to indicate the position of the PUCCH resource used by the RedCap terminal in the uplink BWP. It can be understood that other system messages sent by other base stations to the RedCap terminal can also be used to indicate the edge position information of the PUCCH resource.
  • the edge position information includes at least one of the following situations: the upper edge of the uplink BWP, the lower edge of the uplink BWP, the two sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or a certain side of the uplink BWP, or both sides of the uplink BWP.
  • the edge position information may refer to that the PUCCH is located on the upper edge, the lower edge, or both sides of the uplink BWP, or the upper edge, the lower edge of the uplink BWP, or a certain side of the uplink BWP, both sides of the uplink BWP, etc.
  • the PUCCH resource set configuration table includes at least one of the following: a common PUCCH resource set configuration table for NR conventional terminals, and a dedicated PUCCH resource set configuration table.
  • the PUCCH resource set configuration table may be a common PUCCH resource set configuration table of the NR regular terminal, that is, the RedCap terminal may share the same PUCCH resource set configuration table with the NR regular terminal.
  • the RedCap terminal may maintain a separate dedicated PUCCH resource set configuration table, and the PUCCH resource set configuration table may have all or part of the content different from the common resource set configuration table of the NR conventional terminal.
  • the physical resource unit offset included in the dedicated PUCCH resource set configuration table has a linear relationship with the physical resource unit offset of the common PUCCH resource set configuration table of the NR conventional terminal.
  • the value of the physical resource block offset (Physical Resource Block offset, PRB offset) in the dedicated PUCCH resource set configuration table can be linearly related to the value of the physical resource unit offset included in the public PUCCH resource set configuration table of the NR conventional terminal.
  • the physical resource unit offset of the PUCCH resource set configuration table is multiplied or added, and the operation result can be used as the physical resource unit offset in the dedicated PUCCH resource set configuration table.
  • the transformation parameter used in the linear transformation process can be an indicated value or a preset value.
  • the linear relationship between the multiple physical resource unit offsets included in the dedicated PUCCH resource set configuration table and the multiple physical resource unit offsets of the common PUCCH resource set configuration table of the NR conventional terminal may be different, for example, the physical resource unit offsets of indexes 0 to 14 in the dedicated PUCCH resource set configuration table may be consistent with the physical resource unit offsets of indexes 0 to 14 in the common PUCCH resource set configuration table of the NR conventional terminal.
  • the physical resource unit offset may conform to the additive linear relationship with the physical resource unit offset of index 15 in the common PUCCH resource set configuration table of the NR conventional terminal.
  • Fig. 2 is a flow chart of another resource allocation method provided by the embodiment of the present application.
  • the embodiment of the present application is based on the embodiment of the above application. Referring to Fig. 2, the method provided by the embodiment of the present application specifically includes the following steps:
  • Step 210 determine the edge location information of the PUCCH resource according to the base station signaling.
  • Step 220 Determine the common PUCCH resource set in the PUCCH resource set configuration table according to the edge position information and the SIB message.
  • Step 230 determine the configured additional offset factor according to the edge location information and/or base station signaling, and determine the physical resource unit offset according to the additional offset factor.
  • the additional offset factor may be a further offset of the physical resource unit offset used by the RedCap terminal based on the NR conventional terminal, and the additional offset factor may be used for performing linear operations with the physical resource unit offset in the PUCCH resource set configuration table of the NR conventional terminal.
  • the additional offset factor may be used to determine the physical resource unit offset used by the RedCAP terminal, and may be used to perform a linear operation on the physical resource unit offset included in the public PUCCH resource set. The sum or product of the physical resource unit offset and the additional offset factor is used as the new physical resource unit offset.
  • Step 240 Determine the PUCCH resource according to the edge position information and the physical resource unit offset corresponding to the common PUCCH resource set.
  • the additional offset factor is configured by the system information block SIB message or the downlink control information DCI, and the additional offset factor adjusts the physical resource unit offset based on an addition operation or a multiplication operation, and the number of occupied bits of the additional offset factor includes at least one of: 1 bit, 2 bits or 3 bits.
  • the additional offset factor used by the RedCap terminal can be configured by the SIB message or the downlink control information DCI.
  • the additional offset factor can be used for multiplication or addition with the physical resource unit PRB, and the operation result can be used as the physical resource unit offset used by RedCap.
  • the additional offset factor can occupy 1 bit, 2 bits or 3 bits.
  • the OFDM symbol of the PUCCH resource includes at least two parts, and the value of the frequency hopping index parameter of the PUCCH transmission sequence corresponding to the OFDM symbol of each part includes: 0, 1 or a signaling indication value.
  • the Orthogonal Frequency Division Multiplexing (OFMD) symbol occupied by the PUCCH resource configured by RedCap may include at least two parts, and the frequency hopping index parameter of the PUCCH transmission sequence corresponding to the OFDM symbol of each part may be 0, 1 or a signaling indication value, and the value of the frequency hopping index parameter may indicate whether the PUCCH transmission sequence performs frequency hopping.
  • the OFDM symbol of the PUCCH resource includes at least two parts, and the value of the initial cyclic offset index of the PUCCH transmission sequence corresponding to the OFMD symbol of each part includes: r PUCCH mod N CS , (r PUCCH -8) mod N CS or a signaling indication value, where N CCE is the number of control channel element CCEs contained in the PDCCH resource set, n CCE,0 is the first control channel element CCE index received by the PDCCH, ⁇ PRI is the value of the PUCCH resource indication field in the DCI, and N CS represents the total number of indexes in the initial cyclic offset set.
  • the Orthogonal Frequency Division Multiplexing (Orthogonal Frequency Division Multiplexing, OFMD) symbol occupied by the PUCCH resource configured by RedCap may include at least two parts, and the frequency hopping index parameter of the PUCCH transmission sequence corresponding to the OFDM symbol of each part may be r PUCCH mod N CS , (r PUCCH -8) mod N CS or a signaling indication value, and the value of the frequency hopping index parameter may indicate whether the PUCCH transmission sequence is performed frequency hopping.
  • OFMD Orthogonal Frequency Division Multiplexing
  • the PUCCH resources include at least one of the following: common PUCCH resources, PUCCH resources corresponding to MSG4 messages, and PUCCH resources corresponding to MSGB messages.
  • the RedCap terminal and the regular NR terminal use the same common PUCCH resource set configuration table 2.1 to configure resources.
  • the RedCap terminal determines a common PUCCH resource set according to the PUCCH resource configuration number notified by the SIB1 message, wherein each PUCCH resource set includes 16 PUCCH resources, and determines a PUCCH resource whose index is r PUCCH in the determined common PUCCH resource set by combining DCI and CCE, where N CCE is the number of Control Channel Elements (CCE) included in the PDCCH CORESET, n CCE,0 is the first CCE index received by the PDCCH, and ⁇ PRI is the value of the PUCCH resource indication field in the DCI format.
  • CCE Control Channel Elements
  • a new field Additional_PRBoffset can be defined in the SIB or DCI, which can represent an additional offset factor.
  • the RedCap terminal uses the common PUCCH resource set configuration table 2.1 of the NR conventional terminal by default.
  • the field Additional_PRBoffset when the field Additional_PRBoffset is configured and occupies 1 bit, its value ⁇ is selected from the set ⁇ 4, 6 ⁇ or ⁇ 0, 4 ⁇ or ⁇ 0, 6 ⁇ or ⁇ 4, 2 ⁇ or ⁇ 6, 2 ⁇ or ⁇ 4, -2 ⁇ or ⁇ 6, -2 ⁇ ; when the field Additional_PRBoffset is configured and occupies 2 bits, its value ⁇ is selected from the set ⁇ 4, 6, 0, -2 ⁇ or ⁇ 4, 6, 2, -2 ⁇ or ⁇ 4 , 6, 0, 2 ⁇ to choose from.
  • ⁇ takes a negative number is only for the PUCCH resource set with index 15 in Table 2.1, which means reducing the original PRB offset instead of adding an additional PRB offset.
  • the field Additional_PRBoffset when the field Additional_PRBoffset is configured and occupies 1 bit, its value ⁇ is fixed to a constant greater than zero.
  • the base station makes the PUCCH resources of the RedCap terminal located on both sides of the uplink BWP through scheduling.
  • the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS ; when When , the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is (r PUCCH -8) mod N CS .
  • the base station instructs the RedCap terminal that the PUCCH resource is located at the lower edge of the uplink BWP through SIB or DCI signaling, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS ; when When , the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is (r PUCCH -8) mod N CS .
  • the base station instructs the RedCap terminal that the PUCCH resource is located at the upper edge of the uplink BWP through SIB or DCI signaling, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS ; when When , the PRB index of RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is (r PUCCH -8) mod N CS .
  • the PUCCH resources of the RedCap terminal are configured on both sides of the uplink BWP with a certain offset, and 8 PUCCH resources are distributed on each side.
  • this embodiment uses the original PRB offset (that is, the PRB offset configured in Table 2.1 ) on the basis of adding signaling to indicate additional PRB offsets, so as to prevent the PUCCH transmission of RedCap terminals from interfering with the PUCCH transmission of regular terminals, and realize frequency division multiplexing of multiple types of terminals.
  • the base station signaling can instruct the RedCap terminal to only use the PUCCH resources at the upper or lower edge of the bandwidth, thereby effectively alleviating the problem of PUSCH resource fragmentation.
  • the RedCap terminal determines a common PUCCH resource set (each PUCCH resource set includes 16 PUCCH resources) according to the PUCCH resource configuration number notified by SIB1, and then determines a PUCCH resource whose index is r PUCCH in the common PUCCH resource set by combining DCI and CCE, where N CCE is the number of CCEs included in the PDCCH CORESET, n CCE,0 is the index of the first CCE received by the PDCCH, and ⁇ PRI is the value of the PUCCH resource indication field in the DCI format.
  • a new field Additional_PRBoffset can be defined in the SIB or DCI, which can represent an additional offset factor.
  • the RedCap terminal uses the common PUCCH resource set configuration table 2.1 of the NR conventional terminal by default.
  • the field Additional_PRBoffset when the field Additional_PRBoffset is configured and occupies 1 bit, its value ⁇ is selected from the set ⁇ 4, 6 ⁇ or ⁇ 0, 4 ⁇ or ⁇ 0, 6 ⁇ or ⁇ 4, 2 ⁇ or ⁇ 6, 2 ⁇ or ⁇ 4, -4 ⁇ or ⁇ 6, -4 ⁇ ; when the field Additional_PRBoffset is configured and occupies 2 bits, its value ⁇ is selected from the set ⁇ 4, 6, 0, -4 ⁇ or ⁇ 4, 6, 2, -4 ⁇ or ⁇ 4 , 6, 0, 2 ⁇ or ⁇ 4, 6, 8, 9 ⁇ or ⁇ 6, 8, 9, 10 ⁇ ; when the field Additional_PRBoffset is configured and occupies 3 bits, its value ⁇ is selected from the set ⁇ 4, 6, 8, 9, 10, 2, -4, 0 ⁇ .
  • the base station can indicate through the SIB or DIC that the PUCCH resource of the RedCap terminal is located at the lower edge of the uplink BWP, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of the RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS .
  • the base station instructs the RedCap terminal that the PUCCH resource is located at the upper edge of the uplink BWP through SIB or DCI signaling, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of the RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS .
  • the PUCCH resources of the RedCap terminal are configured on a certain side of the bandwidth with a certain offset, and 16 PUCCH resources are distributed on this side.
  • the base station instructs the RedCap terminal through signaling that all 16 PUCCH resources are specifically distributed on the upper edge or lower edge of the bandwidth, thereby alleviating the problem of PUSCH resource fragmentation.
  • this embodiment uses the original PRB offset (that is, the PRB offset configured in Table 2.1 ) on the basis of adding signaling to indicate additional PRB offsets, so as to prevent the PUCCH transmission of RedCap terminals from interfering with the PUCCH transmission of conventional terminals, and realize frequency division multiplexing of multiple types of terminals.
  • the original PRB offset that is, the PRB offset configured in Table 2.1
  • the base station and the RedCap terminal jointly maintain a common PUCCH resource set configuration table 2.2, and the common PUCCH resource set configuration table 2.2 may be a dedicated resource set configuration table for the RedCaP terminal.
  • the RedCap terminal determines a common PUCCH resource set (each PUCCH resource set includes 16 PUCCH resources) according to the PUCCH resource configuration number notified by SIB1, and then determines a PUCCH resource whose index is r PUCCH in the common PUCCH resource set by combining DCI and CCE, where N CCE is the number of CCEs included in the PDCCH CORESET, n CCE,0 is the index of the first CCE received by the PDCCH, and ⁇ PRI is the value of the PUCCH resource indication field in the DCI format.
  • a new field Additional_PRBoffset is defined in the SIB or DCI to represent an additional offset factor.
  • the RedCap terminal uses the common PUCCH resource set configuration table 2.2 of the NR regular terminal by default.
  • the PRB_offset used by the RedCap terminal in Table 2.2 can be the result of linear processing of the physical resource unit offset in Table 2.1 for the common PUCCH resource set configuration used by NR conventional terminals, and the linear processing can include multiplication or addition.
  • the base station instructs the RedCap terminal that the PUCCH resource is located at the lower edge of the bandwidth BWP through SIB or DCI signaling, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of the RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS .
  • the base station instructs the RedCap terminal that the PUCCH resource is located at the upper edge of the uplink BWP through SIB or DCI signaling, and then the RedCap terminal determines the specific PUCCH resource location according to the signaling instruction.
  • the PRB index of the RedCap terminal PUCCH transmission is The initial cyclic offset index in the initial cyclic offset set is r PUCCH mod N CS .
  • the field Additional_PRBoffset is not configured, Equal to the PRB offset configured in Table 2.2
  • ⁇ is the value of the configured Additional_PRBoffset, It is the PRB offset configured in Table 2.2.
  • the PUCCH resources of the RedCap terminal are configured on a certain side of the bandwidth with a certain offset, and 16 PUCCH resources are distributed on this side.
  • the base station instructs the RedCap terminal through signaling that all 16 PUCCH resources are specifically distributed on the upper edge or lower edge of the bandwidth, thereby alleviating the problem of PUSCH resource fragmentation.
  • a new RedCap exclusive PUCCH resource set configuration table 2.2 is defined, which redefines the original PRB offset (i.e.
  • the additional PRB offset is indicated by adding signaling, so as to avoid the PUCCH transmission of the RedCap terminal from interfering with the PUCCH transmission of the conventional terminal, and realize frequency division multiplexing of multiple types of terminals.
  • the sequences transmitted by the two types of terminals are non-orthogonal, which reduces network capacity.
  • the base sequence and cyclic offset can be further processed to realize code division multiplexing of different types of terminals, thereby improving the multiplexing capability of multiple users.
  • the low PAPR sequence transmitted on the PUCCH resource is expressed as:
  • M ZC represents the transmission sequence length
  • u represents the group number of the base sequence
  • v represents the base sequence number in the group
  • ⁇ represents the cyclic offset
  • u and v are parameters related to the frequency hopping index n hop
  • ⁇ is a parameter related to the initial cycle offset m 0 in the common PUCCH resource set configuration table.
  • the conventional terminal uses frequency hopping to transmit PUCCH resources by default in the initial access phase, and in the first hop of the PUCCH transmission of the conventional terminal, the frequency hopping index parameter n hop in u and v takes a value of 0; in the second hop of the conventional terminal PUCCH transmission, the frequency hopping index parameter n hop in u and v takes a value of 1.
  • the RedCap terminal cancels the PUCCH frequency hopping in the initial access stage, the value of the frequency hopping index parameter n hop in u and v is fixed at 0, which leads to the fact that the PUCCH base sequences transmitted by the RedCap terminal and the NR regular terminal are not orthogonal, and code division multiplexing cannot be realized. Therefore, for the RedCap msg4 PUCCH transmission, this embodiment introduces a new signaling to indicate the value of the frequency hopping index parameter n hop to ensure the orthogonality with the regular terminal PUCCH transmission sequence.
  • the PUCCH transmission can be A time-domain OFDM symbol is divided into N sub-parts, and the number of symbols occupied by each is ⁇ , Wherein N is preferably 2.
  • N is preferably 2.
  • the value of the frequency hopping index parameter n hop in u and v is fixed to 0; for the OFDM symbols in the last N-1 subparts in the PUCCH transmission, the value of the frequency hopping index parameter n hop in u and v is 0 or 1, and the specific value is indicated by the base station signaling.
  • the PUCCH transmission A time-domain OFDM symbol is divided into N sub-parts, and the number of symbols occupied by each is ⁇ , Wherein N is preferably 2.
  • N is preferably 2.
  • the value of the frequency hopping index parameter n hop in u and v is fixed at 0; for the OFDM symbols in the last N-1 subparts of PUCCH transmission, the frequency hopping index parameter n hop in u and v is fixed at 1.
  • the PUCCH transmission A time-domain OFDM symbol is divided into N sub-parts, and the number of symbols occupied by each is ⁇ , Wherein N is preferably 2.
  • the frequency hopping index parameter n hop in u and v takes a value of 0 or 1 or is indicated by the base station signaling.
  • the PUCCH sequences of different terminals may be transmitted under the same frequency domain resource at different times, and the corresponding initial cyclic prefixes are also different.
  • the initial cyclic prefixes corresponding to PUCCH transmissions in different time periods under the same frequency domain resources are constant, and it is difficult to maintain orthogonality with multiple conventional terminal PUCCH transmissions with different initial cyclic offsets at the same time. For this reason, this embodiment proposes to divide the OFDM symbols transmitted by the PUCCH of the RedCap terminal into multiple sub-parts, and configure different initial cyclic offsets respectively, so as to implement code division multiplexing with conventional terminals.
  • the PUCCH transmission A time-domain OFDM symbol is divided into N sub-parts, and the number of symbols occupied by each is ⁇ , Wherein N is preferably 2.
  • the initial cyclic offset parameter m in ⁇ is the value corresponding to the index r PUCCH mod N CS or (r PUCCH -8) mod N CS in the initial cyclic offset set, where rPUCCH represents the PUCCH resource index, and N CS represents the total number of indexes in the initial cyclic offset set in the public PUCCH resource set configuration table;
  • the value corresponding to the index r PUCCH mod N CS or (r PUCCH -8) mod N CS or other indexes in the offset set, and the specific index value is indicated by the base station through signaling.
  • the PUCCH transmission A time-domain OFDM symbol is divided into N sub-parts, and the number of symbols occupied by each is ⁇ , Wherein N is preferably 2.
  • the value of the initial cyclic offset parameter m0 in ⁇ is the value corresponding to the index r PUCCH mod N CS or (r PUCCH -8) mod N CS or other indexes in the initial cyclic offset set, and the specific index value is indicated by the base station through signaling.
  • the RRC signaling PUCCH-ConfigCommon is used to configure the PUCCH resource information in the initial access phase.
  • the scrambling identification parameter hoppingId, power control parameter p0-nominal, group frequency hopping parameter pucch-GroupHopping and common PUCCH resource index parameter pucch-ResourceCommon can be shared with conventional terminals or configured separately to achieve frequency division multiplexing or uplink coverage enhancement and other requirements.
  • Fig. 3 is a schematic structural diagram of a resource allocation device provided by an embodiment of the present application, which can execute the method provided by any embodiment of the present application, and has corresponding functional modules and beneficial effects for executing the method.
  • the apparatus may be implemented by software and/or hardware, and specifically includes: a location determination module 301 , a resource collection module 302 and a resource configuration module 303 .
  • the position determination module 301 is configured to determine edge position information of PUCCH resources according to base station signaling.
  • the resource set module 302 is configured to determine a common PUCCH resource set in the PUCCH resource set configuration table according to the edge position information and the SIB message.
  • the resource configuration module 303 is configured to determine a PUCCH resource according to the edge location information and the physical resource unit offset corresponding to the common PUCCH resource set.
  • the edge location information of the PUCCH resource is determined by the location determination module according to the base station signaling
  • the resource collection module uses the edge location information and the SIB message to determine the common PUCCH resource set in the PUCCH resource set configuration table
  • the resource configuration module uses the edge location information and the physical resource unit offset corresponding to the public PUCCH resource set to determine the PUCCH resource, realizes the PUCCH resource configuration of the RedCap terminal, reduces the impact on the performance of the public network, and can improve network capacity.
  • the base station signaling in the device includes at least one of the following: the remaining minimum system information SIB1, downlink control information DCI, and other system information.
  • the edge position information in the device includes at least one of the following situations: the upper edge of the uplink BWP, the lower edge of the uplink BWP, the two sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or a certain side of the uplink BWP, or both sides of the uplink BWP.
  • the PUCCH resource set configuration table in the device includes at least one of the following: a common PUCCH resource set configuration table for NR conventional terminals, and a dedicated PUCCH resource set configuration table.
  • the physical resource unit offset included in the dedicated PUCCH resource set configuration table in the device has a linear relationship with the physical resource unit offset of the common PUCCH resource set configuration table of the NR conventional terminal.
  • an offset factor module configured to determine a configured additional offset factor according to edge position information and/or base station signaling, and determine the physical resource unit offset according to the additional offset factor.
  • the additional offset factor in the offset factor module is configured by a scheduling message SIB or downlink control information DCI, and the additional offset factor adjusts the physical resource unit offset based on an addition operation or a multiplication operation, and the number of occupied bits of the additional offset factor includes at least one of: 1 bit, 2 bits or 3 bits.
  • the OFDM symbol of the PUCCH resource includes at least two parts, and the value of the frequency hopping index parameter of the PUCCH transmission sequence corresponding to the OFDM symbol of each part includes: 0, 1 or a signaling indication value.
  • the OFDM symbol of the PUCCH resource includes at least two parts, and the value of the initial cyclic offset index of the PUCCH transmission sequence corresponding to the OFMD symbol of each part includes: r PUCCH mod N CS, (r PUCCH -8) mod N CS or a signaling indication value.
  • the PUCCH resources include at least one of the following: common PUCCH resources, PUCCH resources corresponding to MSG4 messages, and PUCCH resources corresponding to MSGB messages.
  • Fig. 4 is a schematic structural view of an electronic device provided by the embodiment of the present application, the electronic device includes a processor 40, a memory 41, an input device 42 and an output device 43; the number of processors 40 in the electronic device can be one or more, and one processor 40 is used as an example in Fig. 4; the processor 40, memory 41, input device 42 and output device 43 in the electronic device can be connected by a bus or in other ways, and in Fig. 4, the connection by a bus is used as an example.
  • the memory 41 can be used to store software programs, computer-executable programs and modules, such as the modules corresponding to the device in the embodiment of the present application (location determination module 301, resource collection module 302 and resource configuration module 303).
  • the processor 40 executes various functional applications and data processing of the electronic device by running software programs, instructions and modules stored in the memory 41 , that is, implements the above-mentioned method.
  • the memory 41 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required by a function; the data storage area can store data created according to the use of the electronic device, and the like.
  • the memory 41 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • the memory 41 may further include a memory that is remotely located relative to the processor 40, and these remote memories may be connected to the electronic device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the input device 42 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the electronic device.
  • the output device 43 may include a display device such as a display screen.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute a resource allocation method when executed by a computer processor.
  • the method includes:
  • the present application can be implemented by means of software and necessary general-purpose hardware, of course it can also be implemented by hardware, but in many cases the former is a better implementation.
  • the technical solution of the present application or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (FLASH), a hard disk or an optical disk, etc., including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute various aspects of the application.
  • a computer device which can be a personal computer, a server, or a network device, etc.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be executed cooperatively by several physical components.
  • Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
  • a processor such as a central processing unit, digital signal processor, or microprocessor
  • Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and that can be accessed by a computer.
  • communication media typically embody computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is known to those of ordinary skill in the art.

Abstract

本申请实施例提出了一种资源配置方法、电子设备和存储介质，其中，该方法包括：根据基站信令确定PUCCH资源的边缘位置信息；根据所述边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合；根据所述边缘位置信息和所述公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。

Description

一种资源配置方法、电子设备和存储介质
相关申请的交叉引用
本申请基于申请号为202210062080.8、申请日为2022年01月19日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种资源配置方法、电子设备和存储介质。
背景技术
降低能力(Reduced Capability，RedCap)是3GPP标准化机构立项的一种新型物联网技术，主要面向工业无线传感器、视频监控和可穿戴设备等中端物联网设备，具有低复杂度、低成本、低功耗、紧凑尺寸等特点，相比于5G增强型移动宽带eMBB和超高可靠低时延通信uRLLC技术，RedCap在部分带宽(BandWidth Part，BWP)、天线数、多输入多输出(Multiple Input Multiple Output，MIMO)层数、调制阶数等方面进行精简，实现成本和性能的折中。
RedCap技术需要在满足用例要求的前提下，实现对网络性能的影响最小。在FR1频段下，NR常规终端的最大支持带宽为100M，而为了实现复杂度和成本的降低，RedCap终端的最大支持带宽被降低为20M，由于RedCap终端和NR常规终端共用公网，RedCap终端位于带宽两侧的物理上行链路控制信道(Physical Uplink Control Channel，PUCCH)资源会将NR常规终端的物理上行链路共享信道(Physical Uplink Share Channel，PUSCH)资源分割为多个子部分，产生PUSCH资源碎片问题，从而导致公网中NR常规终端的上行峰值数据率的下降。目前，3GPP标准会议上决定取消初始接入阶段的RedCap PUCCH跳频，具体来说，通过新增SIB信令来指示使能或取消RedCap终端的PUCCH跳频，PUCCH跳频的取消使得RedCap终端的PUCCH资源集中在带宽的一侧，降低PUSCH资源碎片问题。
在授权频谱下，NR常规终端在初始接入阶段默认使用跳频的方式来传输PUCCH资源，以实现更大的上行覆盖范围和更好的传输性能。但是在SIB信令指示取消RedCap终端的跳频时，RedCap终端以不跳频的方式传输PUCCH，此时现有针对NR常规终端的PUCCH资源配置方法无法直接应用于RedCap终端，并且，为了保证多用户复用能力不变，配置给RedCap终端的每个PUCCH资源集合中也应该包括16个PUCCH资源。此外，当基于PUCCH跳频传输的终端和基于PUCCH不跳频传输的终端复用同一个资源块上传输PUCCH时，传输序列的非正交性使得两种类型终端无法实现码分复用，从而降低网络容量。
发明内容
本申请实施例的主要目的在于提出一种资源配置方法、电子设备和存储介质。
本申请实施例提供了一种资源配置方法，其中，该方法包括：根据基站信令确定PUCCH资源的边缘位置信息；根据所述边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合；根据所述边缘位置信息和所述公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
本申请实施例还提供了一种电子设备，其中，该电子设备包括：一个或多个处理器；存储器，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使 得所述一个或多个处理器实现如本申请实施例中任一所述方法。
本申请实施例还提供了一种计算机可读存储介质，其中，所述计算机可读存储介质存储有一个或多个程序，所述一个或多个程序被所述一个或多个处理器执行，以实现如本申请实施例中任一所述方法。
附图说明
图1是本申请实施例提供的一种资源配置方法的流程图；
图2是本申请实施例提供的另一种资源配置方法的流程图；
图3是本申请实施例提供的一种资源配置装置的结构示意图；
图4是本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
在后续的描述中，使用用于表示元件的诸如“模块”、“部件”或“单元”的后缀仅为了有利于本申请的说明，其本身没有特有的意义。因此，“模块”、“部件”或“单元”可以混合地使用。
在本申请实施例中，RedCap终端和NR常规终端共用一张公网，RedCap终端位于带宽两侧的PUCCH资源会将NR常规终端的PUSCH资源分割为多个子部分，产生PUSCH资源碎片问题，从而降低NR常规终端的上行峰值数据率。NR常规终端在初始阶段使用的公共PUCCH资源集合配置表2.1如下：
Figure PCTCN2022100526-appb-000001
在授权频谱下，NR常规终端在初始接入阶段默认使用跳频的方式来传输PUCCH资源，以实现更大的上行覆盖范围和更好的传输性能。具体来说，基于基站和终端共同维护的公共PUCCH资源集合配置表2.1，NR常规终端首先根据SIB1通知的PUCCH资源配置编号，确定一个公共的PUCCH资源集合(每个PUCCH资源集合包括16个PUCCH资源)，然后通过DCI和CCE相结合的方式在该公共PUCCH资源集合中确定一个索引为r PUCCH,0≤r PUCCH≤15的PUCCH资源。针对每一个PUCCH资源索引r PUCCH，相应的PUCCH资源频域位置和初始循环偏移配置为：
当
Figure PCTCN2022100526-appb-000002
时，NR常规终端PUCCH传输的第一跳PRB索引为
Figure PCTCN2022100526-appb-000003
第二跳PRB索引为
Figure PCTCN2022100526-appb-000004
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS；
当
Figure PCTCN2022100526-appb-000005
时，NR常规终端PUCCH传输的第一跳PRB索引为
Figure PCTCN2022100526-appb-000006
Figure PCTCN2022100526-appb-000007
第二跳PRB索引为
Figure PCTCN2022100526-appb-000008
初始循环偏移集合中的初始循环偏移索引为(r PUCCH-8)mod N CS；
其中，PRB用于描述资源块在实际传输中的相对位置，
Figure PCTCN2022100526-appb-000009
表示配置给RedCap终端的初始上行BWP的PRB数目，
Figure PCTCN2022100526-appb-000010
表示表2.1中所定义的PRB偏移，N CS表示初始循环偏移集合中的索引总数目，
Figure PCTCN2022100526-appb-000011
表示向下取整，mod表示取模运算。
当SIB信令指示取消PUCCH跳频时，RedCap终端以不跳频的方式传输PUCCH，此时上述针对NR常规终端的PUCCH资源配置方法无法直接应用于RedCap终端。并且，为了保证多用户复用能力不变，配置给RedCap终端的每个PUCCH资源集合中也应该包含16个PUCCH资源。此外，当基于PUCCH跳频传输的终端和基于PUCCH不跳频传输的终端复用在同一个资源块上传输PUCCH时，传输序列的非正交性使得两种类型终端无法实现码分复用，从而降低网络容量。
图1是本申请实施例提供的一种资源配置方法的流程图，本申请实施例可适用于RedCaps终端传输资源配置的情况，该方法可以由资源配置装置来执行，该装置可以通过软件和/或硬件的方法实现，一般集成在RedCap终端中，参见图1，本申请实施例提供的方法具体包括如下步骤：
步骤110、根据基站信令确定PUCCH资源的边缘位置信息。
其中，边缘位置信息可以是RedCap终端使用的PUCCH资源在部分带宽(Bandwidth Part，BWP)中的位置，边缘位置信息可以指示上行BWP的上边缘、下边缘、两侧边缘，或者，上行BWP的上边缘、下边缘，或者，上行BWP的某一侧、上行BWP的两侧。
在本申请实施例中，RedCap终端可以由基站信令指示使用的PUCCH资源的边缘位置信息，可以由基站信令确定出PUCCH资源位于上行BWP的位置，例如，可以是上行BWP的上边缘、下边缘、两侧边缘，或者，上行BWP的上边缘、下边缘，或者，上行BWP的某一侧、上行BWP的两侧。步骤120、根据边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合。
具体的，RedCap终端可以使用确定的边缘位置信息以及系统信息块(System Information Blocks，SIB)消息共同在PUCCH资源集合配置表中确定一个公共PUCCH资源集合，其中，PUCCH资源集合配置表可以由RedCap终端和基站共同维护。
步骤130、根据边缘位置信息和公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
在本申请实施例中，可以确定公共PUCCH资源集合中配置的物理资源单元偏移，可以按照该物理资源单元偏移以及边缘位置信息确定RedCap终端使用的PUCCH资源的位置，例如，可以确定出RedCap终端使用的PUCCH资源频域位置以及初始循环偏移配置等参数。
本申请实施例，通过基站信令确定PUCCH资源的边缘位置信息，使用边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合，使用边缘位置信息和公共PUCCH 资源集合对应的物理资源单元偏移来确定PUCCH资源，实现RedCap终端的PUCCH资源配置，降低对公网网络性能的影响，可提高网络容量。
进一步的，在上述申请实施例的基础上，基站信令包括以下至少之一：剩余最小系统消息SIB1、下行控制信息DCI、其他系统消息。
在本申请实施例中，可以通过剩余最小系统消息SIB1或者下行控制信息(Downlink Control Channel，DCI)指示RedCap终端使用的PUCCH资源在上行BWP的位置，可以理解的是，还可以使用其他基站向RedCap终端发送的其他系统消息指示PUCCH资源的边缘位置信息。
进一步的，在上述申请实施例的基础上，边缘位置信息包括以下至少一种情况：上行BWP的上边缘、上行BWP的下边缘、上行BWP的两侧，或者上行BWP的上边缘、上行BWP的下边缘，或者上行BWP的某一侧、上行BWP的两侧。
在本申请实施例中，边缘位置信息可以是指PUCCH位于上行BWP的上边缘、下边缘、两侧边缘，或者，上行BWP的上边缘、下边缘，或者，上行BWP的某一侧、上行BWP的两侧等。
进一步的，在上述申请实施例的基础上，PUCCH资源集合配置表至少包括以下之一：NR常规终端的公共PUCCH资源集合配置表、专用PUCCH资源集合配置表。
具体的，PUCCH资源集合配置表可以是NR常规终端的公共PUCCH资源集合配置表，也即RedCap终端可以与NR常规终端共用相同的PUCCH资源集合配置表。或者，RedCap终端可以维护单独的专用的PUCCH资源集合配置表，该PUCCH资源集合配置表可以存在全部或者部分内容与NR常规终端的公共资源集合配置表不同。
进一步的，在上述申请实施例的基础上，专用PUCCH资源集合配置表包括的物理资源单元偏移与所述NR常规终端的公共PUCCH资源集合配置表的物理资源单元偏移呈线性关系。
在本申请实施例中，专用PUCCH资源集合配置表中的物理资源单元偏移(Physical Resource Block offset，PRB offset)的取值可以与NR常规终端的公共PUCCH资源集合配置表包括的物理资源单元偏移的取值呈线性关系，专用PUCCH资源集合配置表中的物理资源单元偏移可以通过对NR常规终端的公共PUCCH资源集合配置表的物理资源单元偏移进行线性变换获取，例如，可以对NR常规终端的公共PUCCH资源集合配置表的物理资源单元偏移进行乘法运算或者加法运算，可以将运算结果作为专用PUCCH资源集合配置表中的物理资源单元偏移，可以理解的是，线性变换过程中使用的变换参数可以为指示值或者预设值。进一步的，可以理解的是，专用PUCCH资源集合配置表包括的多个物理资源单元偏移分别与NR常规终端的公共PUCCH资源集合配置表的多个物理资源单元偏移符合的线性关系可以不同，例如，专用PUCCH资源集合配置表中索引0至14的物理资源单元偏移可以分别与NR常规终端的公共PUCCH资源集合配置表中索引0至14的物理资源单元偏移符合可以符合乘法线性关系，而专用PUCCH资源集合配置表中索引15的物理资源单元偏移可以与NR常规终端的公共PUCCH资源集合配置表中索引15的物理资源单元偏移符合加法线性关系。
图2是本申请实施例提供的另一种资源配置方法的流程图，本申请实施例是在上述申请实施例基础上的具体化，参见图2，本申请实施例提供的方法具体包括如下步骤：
步骤210、根据基站信令确定PUCCH资源的边缘位置信息。
步骤220、根据边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合。
步骤230、根据边缘位置信息和/或基站信令确定配置的额外偏移因子，并根据额外偏移 因子确定物理资源单元偏移。
其中，额外偏移因子可以是RedCap终端基于NR常规终端使用的物理资源单元偏移进一步的偏移量，该额外偏移因子可以用于与NR常规终端的PUCCH资源集合配置表中的物理资源单元偏移进行线性运算。
在本申请实施例中，可以通过边缘位置信息和/或基站信令确定是否配置有额外偏移因子，在确定配置额外偏移因子后，可以使用该额外偏移因子用于确定RedCAP终端使用的物理资源单元偏移，可以用于对公共PUCCH资源集合中包括的物理资源单元偏移进行线性运算，该确定过程可以是将公共PUCCH资源集合中的物理资源单元偏移与额外偏移因子进行线性运算的结果作为RedCap终端使用的物理资源单元偏移，例如，可以将公共PUCCH资源集合包括的物理资源单元偏移与额外偏移因子的和或积作为新的物理资源单元偏移。
步骤240、根据边缘位置信息和公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
进一步的，在上述申请实施例的基础上，额外偏移因子由系统信息块SIB消息或下行控制信息DCI配置，额外偏移因子基于加法运算或乘法运算调整所述物理资源单元偏移，额外偏移因子的占用比特数包括至少之一：1比特、2比特或3比特。
具体的，RedCap终端使用的额外偏移因子可以由SIB消息或下行控制信息DCI配置，额外偏移因子可以用于与物理资源单元PRB进行乘法运算或者加法运算，可以将运算结果作为RedCap使用的物理资源单元偏移，额外偏移因子可以占用1比特、2比特或3比特。
进一步的，在上述申请实施例的基础上，PUCCH资源的OFDM符号包括至少两个部分，各所述部分的OFDM符号对应的PUCCH传输序列的跳频索引参数取值包括：0、1或信令指示值。
在本申请实施例中，RedCap配置的PUCCH资源占用的正交频分复用(Orthogonal Frequency Division Multiplexing，OFMD)符号可以包括至少两个部分，每个部分的OFDM符号对应的PUCCH传输序列的跳频索引参数可以为0,1或者信令指示值，可以通过跳频索引参数的取值指示PUCCH传输序列是否进行跳频。
进一步的，在上述申请实施例的基础上，PUCCH资源的OFDM符号包括至少两个部分，各所述部分的所述OFMD符号对应的PUCCH传输序列的初始循环偏移索引的取值包括：r PUCCHmod N CS、(r PUCCH-8)mod N CS或信令指示值，其中
Figure PCTCN2022100526-appb-000012
N CCE是PDCCH资源集合包含的控制信道单元CCE数目，n CCE,0是PDCCH接收的第一个控制信道单元CCE索引，Δ PRI是DCI中PUCCH资源指示域的值，N CS表示初始循环偏移集合中的索引总数目。
在本申请实施例中，RedCap配置的PUCCH资源占用的正交频分复用(Orthogonal Frequency Division Multiplexing，OFMD)符号可以包括至少两个部分，每个部分的OFDM符号对应的PUCCH传输序列的跳频索引参数可以为r PUCCHmod N CS、(r PUCCH-8)mod N CS或信令指示值，可以通过跳频索引参数的取值指示PUCCH传输序列是否进行跳频。
进一步的，在上述申请实施例的基础上，PUCCH资源包括以下至少之一：公共PUCCH资源、MSG4消息对应的PUCCH资源、MSGB消息对应的PUCCH资源。
在一个示例性的实施方式中，RedCap终端与常规NR终端使用相同的公共PUCCH资源集合配置表2.1配置资源。RedCap终端根据SIB1消息通知的PUCCH资源配置编号确定一个公共的PUCCH资源集合，其中，每个PUCCH资源集合中包括16个PUCCH资源，通过DCI和CCE 相结合的方式在确定的公共PUCCH资源集合中确定一个索引为r PUCCH的PUCCH资源，其中
Figure PCTCN2022100526-appb-000013
N CCE是PDCCH CORESET所包含的控制信道单元(Control Channel Elements，CCE)数目，n CCE,0是PDCCH接收的第一个CCE索引，Δ PRI是DCI格式中PUCCH资源指示域的值。
进一步的，可以在SIB或DCI中定义新的字段Additional_PRBoffset,该字段可以表示额外偏移因子，在字段Additional_PRBoffset未配置时，RedCap终端默认使用NR常规终端的公共PUCCH资源集合配置表2.1。
进一步的，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ在集合{4，6}或{0，4}或{0，6}或{4，2}或{6，2}或{4，-2}或{6，-2}中选择；当字段Additional_PRBoffset被配置且占用2bit时，其取值ρ在集合{4，6，0，-2}或{4，6，2，-2}或{4，6，0，2}中选择。其中，ρ取负数的情况仅针对表2.1中索引15的PUCCH资源集合，意味着减少原始的PRB偏移量而不是新增额外的PRB偏移量。或者，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ固定为某个大于零的常数。
进一步的，在上述申请实施例的基础上，基站通过调度使得RedCap终端的PUCCH资源位于上行BWP的两侧。具体而言，当
Figure PCTCN2022100526-appb-000014
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000015
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS；当
Figure PCTCN2022100526-appb-000016
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000017
初始循环偏移集合中的初始循环偏移索引为(r PUCCH-8)mod N CS。其中，当字段Additional_PRBoffset未被配置时，
Figure PCTCN2022100526-appb-000018
等于表2.1中所配置的PRB偏移
Figure PCTCN2022100526-appb-000019
当字段Additional_PRBoffset被配置时，
Figure PCTCN2022100526-appb-000020
或
Figure PCTCN2022100526-appb-000021
ρ为所配置的Additional_PRBoffset的取值，
Figure PCTCN2022100526-appb-000022
为表2.1中所配置的PRB偏移。
进一步的，在上述申请实施例的基础上，基站通过SIB或DCI信令指示RedCap终端的PUCCH资源位于上行BWP的下边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，当
Figure PCTCN2022100526-appb-000023
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000024
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS；当
Figure PCTCN2022100526-appb-000025
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000026
初始循环偏移集合中的初始循环偏移索引为(r PUCCH-8)mod N CS。
进一步的，在上述申请实施例的基础上，基站通过SIB或DCI信令指示RedCap终端的PUCCH资源位于上行BWP的上边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，当
Figure PCTCN2022100526-appb-000027
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000028
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS；当
Figure PCTCN2022100526-appb-000029
时，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000030
初始循环偏移集合中的初始循环偏移索引为(r PUCCH-8)mod N CS。
进一步的，在上述申请实施例的基础上，RedCap终端的PUCCH资源被以一定的偏移量配置在上行BWP的两侧，每侧各分布8个PUCCH资源。相比于常规终端的PUCCH资源配置方法，本实施例在原始PRB偏移(即表2.1中所配置的PRB偏移
Figure PCTCN2022100526-appb-000031
)的基础上，通过新增信令指示额外的PRB偏移，以此避免RedCap终端的PUCCH传输对常规终端的PUCCH传输产生干扰， 实现多类型终端的频分复用。同时，可通过基站信令指示RedCap终端仅使用带宽上边缘或下边缘的PUCCH资源，从而有效减轻PUSCH资源碎片问题。
在一个示例性的实施方式中，首先，基于基站和终端共同维护的公共PUCCH资源集合配置表2.1，RedCap终端根据SIB1通知的PUCCH资源配置编号，确定一个公共的PUCCH资源集合(每个PUCCH资源集合包括16个PUCCH资源)，然后通过DCI和CCE相结合的方式在该公共PUCCH资源集合中确定一个索引为r PUCCH的PUCCH资源，其中
Figure PCTCN2022100526-appb-000032
N CCE是PDCCH CORESET所包含的CCE数目，n CCE,0是PDCCH接收的第一个CCE索引，Δ PRI是DCI格式中PUCCH资源指示域的值。
进一步的，可以在SIB或DCI中定义新的字段Additional_PRBoffset,该字段可以表示额外偏移因子，在字段Additional_PRBoffset未配置时，RedCap终端默认使用NR常规终端的公共PUCCH资源集合配置表2.1。
进一步的，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ在集合{4，6}或{0，4}或{0，6}或{4，2}或{6，2}或{4，-4}或{6，-4}中选择；当字段Additional_PRBoffset被配置且占用2bit时，其取值ρ在集合{4，6，0，-4}或{4，6，2，-4}或{4，6，0，2}或{4，6，8，9}或{6，8，9，10}中选择；当字段Additional_PRBoffset被配置且占用3bit时，其取值ρ在集合{4，6，8，9，10，2，-4，0}中选择。其中，ρ取负数的情况仅针对表2.1中索引15的PUCCH资源集合，意味着减少原始的PRB偏移量而不是新增额外的PRB偏移量。或者，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ固定为某个大于零的常数。
进一步的，在上述申请实施例的基础上，基站可以通过SIB或者DIC指示RedCap终端的PUCCH资源位于上行BWP的下边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000033
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS。其中，当字段Additional_PRBoffset未被配置时，
Figure PCTCN2022100526-appb-000034
等于表2.1中所配置的PRB偏移
Figure PCTCN2022100526-appb-000035
或等于
Figure PCTCN2022100526-appb-000036
(κ为大于零的固定值，优选为2)；当字段Additional_PRBoffset被配置时，
Figure PCTCN2022100526-appb-000037
或
Figure PCTCN2022100526-appb-000038
或
Figure PCTCN2022100526-appb-000039
或
Figure PCTCN2022100526-appb-000040
ρ为所配置的Additional_PRBoffset的取值，
Figure PCTCN2022100526-appb-000041
为表2.1中所配置的PRB偏移。
进一步的，在上述申请实施例的基础上，基站通过SIB或DCI信令指示RedCap终端的PUCCH资源位于上行BWP的上边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000042
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS。其中，当字段Additional_PRBoffset未被配置时，
Figure PCTCN2022100526-appb-000043
等于表2.1中所配置的PRB偏移
Figure PCTCN2022100526-appb-000044
或等于
Figure PCTCN2022100526-appb-000045
(κ为大于零的固定值，优选为2)；当字段Additional_PRBoffset被配置时，
Figure PCTCN2022100526-appb-000046
或
Figure PCTCN2022100526-appb-000047
或
Figure PCTCN2022100526-appb-000048
或
Figure PCTCN2022100526-appb-000049
ρ为所配置的Additional_PRBoffset的取值，
Figure PCTCN2022100526-appb-000050
为表2.1中所配置的PRB偏移。
进一步的，在上述申请实施例的基础上，RedCap终端的PUCCH资源被以一定的偏移量配置在带宽的某一侧，该侧分布16个PUCCH资源。并且，基站通过信令指示RedCap终端，所 有16个PUCCH资源具体分布在带宽上边缘或者下边缘，由此减轻PUSCH资源碎片问题。此外，相比于常规终端的PUCCH资源配置方法，本实施例在原始PRB偏移(即表2.1中所配置的PRB偏移
Figure PCTCN2022100526-appb-000051
)的基础上，通过新增信令指示额外的PRB偏移，以此避免RedCap终端的PUCCH传输对常规终端的PUCCH传输产生干扰，实现多类型终端的频分复用。
在一个示例性的实施方式中，基站和RedCap终端共同维护一个公共的PUCCH资源集合配置表2.2，该公共PUCCH资源集合配置表2.2可以是RedCaP终端专用的资源集合配置表。RedCap终端根据SIB1通知的PUCCH资源配置编号，确定一个公共的PUCCH资源集合(每个PUCCH资源集合包括16个PUCCH资源)，然后通过DCI和CCE相结合的方式在该公共PUCCH资源集合中确定一个索引为r PUCCH的PUCCH资源，其中
Figure PCTCN2022100526-appb-000052
N CCE是PDCCH CORESET所包含的CCE数目，n CCE,0是PDCCH接收的第一个CCE索引，Δ PRI是DCI格式中PUCCH资源指示域的值。
进一步的，在上述申请实施例的基础上，在SIB或DCI中定义新的字段Additional_PRBoffset，表征额外偏移因子。当字段Additional_PRBoffset未配置时，RedCap终端默认使用NR常规终端的公共PUCCH资源集合配置表2.2。
进一步的，在上述申请实施例的基础上，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ在集合{4，6}或{0，4}或{0，6}或{4，2}或{6，2}或{4，-4}或{6，-4}中选择；当字段Additional_PRBoffset被配置且占用2bit时，其取值ρ在集合{4，6，0，-4}或{4，6，2，-4}或{4，6，0，2}。其中，ρ取负数的情况仅针对表2.2中索引15的PUCCH资源集合，意味着减少原始的PRB偏移量而不是新增额外的PRB偏移量。或者，当字段Additional_PRBoffset被配置且占用1bit时，其取值ρ固定为某个大于零的常数。表2.2：RedCap终端在接入阶段的公共PUCCH资源集合配置表如下：
表2.2：RedCap终端初始接入阶段的公共PUCCH资源集合配置
Figure PCTCN2022100526-appb-000053
其中，表2.2中RedCap终端使用的物理资源单元偏移PRB_offset可以是对NR常规终端使用的共PUCCH资源集合配置表2.1中的物理资源单元偏移的线性处理结果，该线性处理可 以包括乘法或者加法。
进一步的，在上述申请实施例的基础上，基站通过SIB或DCI信令指示RedCap终端的PUCCH资源位于带宽BWP的下边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000054
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS。其中，当字段Additional_PRBoffset未被配置时，
Figure PCTCN2022100526-appb-000055
等于表2.2中所配置的PRB偏移
Figure PCTCN2022100526-appb-000056
当字段Additional_PRBoffset被配置时，
Figure PCTCN2022100526-appb-000057
或
Figure PCTCN2022100526-appb-000058
ρ为所配置的Additional_PRBoffset的取值，
Figure PCTCN2022100526-appb-000059
为表2.2中所配置的PRB偏移。
进一步的，在上述申请实施例的基础上，基站通过SIB或DCI信令指示RedCap终端的PUCCH资源位于上行BWP的上边缘，然后RedCap终端根据该信令指示确定具体的PUCCH资源位置。具体而言，RedCap终端PUCCH传输的PRB索引为
Figure PCTCN2022100526-appb-000060
初始循环偏移集合中的初始循环偏移索引为r PUCCHmod N CS。其中，当字段Additional_PRBoffset未被配置时，
Figure PCTCN2022100526-appb-000061
等于表2.2中所配置的PRB偏移
Figure PCTCN2022100526-appb-000062
当字段Additional_PRBoffset被配置时，
Figure PCTCN2022100526-appb-000063
或
Figure PCTCN2022100526-appb-000064
ρ为所配置的Additional_PRBoffset的取值，
Figure PCTCN2022100526-appb-000065
为表2.2中所配置的PRB偏移。
进一步的，在上述申请实施例的基础上，RedCap终端的PUCCH资源被以一定的偏移量配置在带宽的某一侧，该侧分布16个PUCCH资源。并且，基站通过信令指示RedCap终端，所有16个PUCCH资源具体分布在带宽上边缘或者下边缘，由此减轻PUSCH资源碎片问题。本实施例中定义了一个新的RedCap专有PUCCH资源集合配置表2.2，该表重新定义了原始PRB偏移(即表2.2中所配置的PRB偏移
Figure PCTCN2022100526-appb-000066
)，在此基础上通过新增信令指示额外的PRB偏移，以此避免RedCap终端的PUCCH传输对常规终端的PUCCH传输产生干扰，实现多类型终端的频分复用。
在一个示例性的实施方式中，在使能PUCCH跳频的终端和取消PUCCH跳频的终端在同一个资源块上传输PUCCH时，两种类型终端所传输的序列是非正交的，从而导致了网络容量的降低。可以在上述申请实施例的基础上，对基序列和循环偏移作进一步的处理，实现不同类型终端的码分复用，从而提升多用户复用能力。具体的，PUCCH资源上所传输的低PAPR序列表示为：
Figure PCTCN2022100526-appb-000067
其中，M ZC表示传输序列长度，u表示基序列的组号，v表示组内的基序列号，α表示循环偏移，
Figure PCTCN2022100526-appb-000068
表示和u、v相关的基序列，其具体取值由标准协议TS 38.211中的第5.2.2小节决定。并且，u和v是和跳频索引n hop相关的参数，α是和公共PUCCH资源集合配置表中的初始循环偏移m 0相关的参数。
常规终端在初始接入阶段默认使用跳频的方式来传输PUCCH资源，并且常规终端PUCCH传输的第一跳中，u和v中的跳频索引参数n hop取值为0；常规终端PUCCH传输的第二跳中，u和v中的跳频索引参数n hop取值为1。当RedCap终端在初始接入阶段取消PUCCH跳频时，u和v中的跳频索引参数n hop取值固定为0，由此导致RedCap终端和NR常规终端所传输的PUCCH基序列并不正交，无法实现码分复用。为此，针对RedCap msg4 PUCCH传输，本实施例引入新的信令指示跳频索引参数n hop的取值，以保证和常规终端PUCCH传输序列的正交性。
进一步的，可以将PUCCH传输的
Figure PCTCN2022100526-appb-000069
个时域OFDM符号划分成N个子部分，分别占用的符号数为
Figure PCTCN2022100526-appb-000070
Λ，
Figure PCTCN2022100526-appb-000071
其中N优选为2。对于PUCCH传输中的前
Figure PCTCN2022100526-appb-000072
个OFDM符号，u和v中的跳频索引参数n hop取值固定为0；对于PUCCH传输中的后N-1个子部分中的OFDM符号，u和v中的跳频索引参数n hop取值为0或1，具体取值由基站信令指示。
进一步的，将PUCCH传输的
Figure PCTCN2022100526-appb-000073
个时域OFDM符号划分成N个子部分，分别占用的符号数为
Figure PCTCN2022100526-appb-000074
Λ，
Figure PCTCN2022100526-appb-000075
其中N优选为2。对于PUCCH传输中的前
Figure PCTCN2022100526-appb-000076
个OFDM符号，u和v中的跳频索引参数n hop取值固定为0；对于PUCCH传输中的后N-1个子部分中的OFDM符号，u和v中的跳频索引参数n hop固定为1。
进一步的，将PUCCH传输的
Figure PCTCN2022100526-appb-000077
个时域OFDM符号划分成N个子部分，分别占用的符号数为
Figure PCTCN2022100526-appb-000078
Λ，
Figure PCTCN2022100526-appb-000079
其中N优选为2。对于每个子部分中的OFDM符号，u和v中的跳频索引参数n hop取值为0或1或由基站信令指示。
在PUCCH跳频传输情况下，同一频域资源下不同时间内可能传输的是不同终端的PUCCH序列，相应的初始循环前缀也不同。对于取消PUCCH跳频的RedCap终端而言，同一频域资源下不同时间内的PUCCH传输对应的初始循环前缀是恒定的，难以同时和具有不同初始循环偏移的多个常规终端PUCCH传输保持正交。为此，本实施例提出将RedCap终端PUCCH传输的OFDM符号划分为多个子部分，并分别配置不同的初始循环偏移，以此实现和常规终端的码分复用。
进一步的，将PUCCH传输的
Figure PCTCN2022100526-appb-000080
个时域OFDM符号划分成N个子部分，分别占用的符号数为
Figure PCTCN2022100526-appb-000081
Λ，
Figure PCTCN2022100526-appb-000082
其中N优选为2。对于PUCCH传输中的前
Figure PCTCN2022100526-appb-000083
个OFDM符号，α中的初始循环偏移参数m 0取值为初始循环偏移集合中索引r PUCCHmod N CS或(r PUCCH-8)mod N CS对应的数值，其中， rPUCCH表示PUCCH资源索引，N CS表示公共PUCCH资源集合配置表中初始循环偏移集合中的索引总数目；对于PUCCH传输中的后N-1个子部分中的OFDM符号，α中的初始循环偏移参数m 0取值为初始循环偏移集合中索引r PUCCHmod N CS或(r PUCCH-8)mod N CS或其他索引所对应的数值，具体索引取值由基站通过信令指示。
进一步的，将PUCCH传输的
Figure PCTCN2022100526-appb-000084
个时域OFDM符号划分成N个子部分，分别占用的符号数为
Figure PCTCN2022100526-appb-000085
Λ，
Figure PCTCN2022100526-appb-000086
其中N优选为2。对于每个子部分中的OFDM符号，α中的初始循环偏移参数m 0取值为初始循环偏移集合中索引r PUCCHmod N CS或(r PUCCH-8)mod N CS或其他索引所对应的数值，具体索引取值由基站通过信令指示。
对于RedCap终端的PUCCH传输而言，RRC信令PUCCH-ConfigCommon用于配置初始接入阶段的PUCCH资源信息，其中加扰标识参数hoppingId、功率控制参数p0-nominal、组跳频参数pucch-GroupHopping和公共PUCCH资源索引参数pucch-ResourceCommon均可以和常规终端共享或单独配置，以实现频分复用或上行覆盖增强等需求。
图3是本申请实施例提供的一种资源配置装置的结构示意图，可执行本申请任意实施例所提供的方法，具备执行方法相应的功能模块和有益效果。该装置可以由软件和/或硬件实现， 具体包括：位置确定模块301、资源集合模块302和资源配置模块303。
位置确定模块301，用于根据基站信令确定PUCCH资源的边缘位置信息。
资源集合模块302，用于根据所述边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合。
资源配置模块303，用于根据所述边缘位置信息和所述公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
本申请实施例，通过位置确定模块根据基站信令确定PUCCH资源的边缘位置信息，资源集合模块使用边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合，资源配置模块使用边缘位置信息和公共PUCCH资源集合对应的物理资源单元偏移来确定PUCCH资源，实现RedCap终端的PUCCH资源配置，降低对公网网络性能的影响，可提高网络容量。
进一步的，在上述申请实施例的基础上，装置中的基站信令包括以下至少之一：剩余最小系统消息SIB1、下行控制信息DCI、其他系统消息。
进一步的，在上述申请实施例的基础上，装置中边缘位置信息包括以下至少一种情况：上行BWP的上边缘、上行BWP的下边缘、上行BWP的两侧，或者上行BWP的上边缘、上行BWP的下边缘，或者上行BWP的某一侧、上行BWP的两侧。
进一步的，在上述申请实施例的基础上，装置中PUCCH资源集合配置表至少包括以下之一：NR常规终端的公共PUCCH资源集合配置表、专用PUCCH资源集合配置表。
进一步的，在上述申请实施例的基础上，装置中专用PUCCH资源集合配置表包括的物理资源单元偏移与所述NR常规终端的公共PUCCH资源集合配置表的物理资源单元偏移呈线性关系。
进一步的，在上述申请实施例的基础上，还包括：偏移因子模块，用于根据边缘位置信息和/或基站信令确定配置的额外偏移因子，并根据所述额外偏移因子确定所述物理资源单元偏移。
进一步的，在上述申请实施例的基础上，偏移因子模块中额外偏移因子由调度消息SIB或下行控制信息DCI配置，所述额外偏移因子基于加法运算或乘法运算调整所述物理资源单元偏移，所述额外偏移因子的占用比特数包括至少之一：1比特、2比特或3比特。
进一步的，在上述申请实施例的基础上，PUCCH资源的OFDM符号包括至少两个部分，各所述部分的所述OFDM符号对应的PUCCH传输序列的跳频索引参数取值包括：0、1或信令指示值。
进一步的，在上述申请实施例的基础上，PUCCH资源的OFDM符号包括至少两个部分，各所述部分的所述OFMD符号对应的PUCCH传输序列的初始循环偏移索引的取值包括：r PUCCHmod N CS、(r PUCCH-8)mod N CS或信令指示值。
进一步的，在上述申请实施例的基础上，PUCCH资源包括以下至少之一：公共PUCCH资源、MSG4消息对应的PUCCH资源、MSGB消息对应的PUCCH资源。
图4是本申请实施例提供的一种电子设备的结构示意图，该电子设备包括处理器40、存储器41、输入装置42和输出装置43；电子设备中处理器40的数量可以是一个或多个，图4中以一个处理器40为例；电子设备中处理器40、存储器41、输入装置42和输出装置43可 以通过总线或其他方式连接，图4中以通过总线连接为例。
存储器41作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请实施例中的装置对应的模块(位置确定模块301、资源集合模块302和资源配置模块303)。处理器40通过运行存储在存储器41中的软件程序、指令以及模块，从而执行电子设备的各种功能应用以及数据处理，即实现上述的方法。
存储器41可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据电子设备的使用所创建的数据等。此外，存储器41可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器41可进一步包括相对于处理器40远程设置的存储器，这些远程存储器可以通过网络连接至电子设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置42可用于接收输入的数字或字符信息，以及产生与电子设备的用户设置以及功能控制有关的键信号输入。输出装置43可包括显示屏等显示设备。
本申请实施例还提供一种包含计算机可执行指令的存储介质，所述计算机可执行指令在由计算机处理器执行时用于执行一种资源配置方法，该方法包括：
根据基站信令确定PUCCH资源的边缘位置信息；
根据所述边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合；
根据所述边缘位置信息和所述公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
通过以上关于实施方式的描述，所属领域的技术人员可以清楚地了解到，本申请可借助软件及必需的通用硬件来实现，当然也可以通过硬件实现，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、闪存(FLASH)、硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
值得注意的是，上述装置的实施例中，所包括的各个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能单元的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、设备中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。
在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包 括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上参照附图说明了本申请的若干实施例，并非因此局限本申请的权利范围。本领域技术人员不脱离本申请的范围和实质内所作的任何修改、等同替换和改进，均应在本申请的权利范围之内。

Claims (12)

  1. 一种资源配置方法，所述方法包括：
    根据基站信令确定PUCCH资源的边缘位置信息；
    根据所述边缘位置信息和SIB消息在PUCCH资源集合配置表中确定公共PUCCH资源集合；
    根据所述边缘位置信息和所述公共PUCCH资源集合对应的物理资源单元偏移确定PUCCH资源。
  2. 根据权利要求1所述方法，其中，所述基站信令包括以下至少之一：剩余最小系统消息SIB1、下行控制信息DCI、其他系统消息。
  3. 根据权利要求1所述方法，其中，所述边缘位置信息包括以下至少一种情况：上行BWP的上边缘、上行BWP的下边缘、上行BWP的两侧，或者上行BWP的上边缘、上行BWP的下边缘，或者上行BWP的某一侧、上行BWP的两侧。
  4. 根据权利要求1所述方法，其中，所述PUCCH资源集合配置表至少包括以下之一：NR常规终端的公共PUCCH资源集合配置表、专用PUCCH资源集合配置表。
  5. 根据权利要求4所述方法，其中，所述专用PUCCH资源集合配置表包括的物理资源单元偏移与所述NR常规终端的公共PUCCH资源集合配置表的物理资源单元偏移呈线性关系。
  6. 根据权利要求1所述方法，还包括：
    根据边缘位置信息和/或基站信令确定配置的额外偏移因子，并根据所述额外偏移因子确定所述物理资源单元偏移。
  7. 根据权利要求6所述方法，其中，所述额外偏移因子由系统信息块SIB消息或下行控制信息DCI配置，所述额外偏移因子基于加法运算或乘法运算调整所述物理资源单元偏移，所述额外偏移因子的占用比特数包括至少之一：1比特、2比特或3比特。
  8. 根据权利要求1所述方法，其中，所述PUCCH资源的OFDM符号包括至少两个部分，各所述部分的所述OFDM符号对应的PUCCH传输序列的跳频索引参数取值包括：0、1或信令指示值。
  9. 根据权利要求1所述方法，其中，所述PUCCH资源的OFDM符号包括至少两个部分，各所述部分的所述OFMD符号对应的PUCCH传输序列的初始循环偏移索引的取值包括：r PUCCHmod N CS、(r PUCCH-8)mod N CS或信令指示值，其中
    Figure PCTCN2022100526-appb-100001
    N CCE是PDCCH资源集合包含的控制信道单元CCE数目，n CCE,0是PDCCH接收的第一个控制信道单元CCE索引，Δ PRI是DCI中PUCCH资源指示域的值，N CS表示初始循环偏移集合中的索引总数目。
  10. 根据权利要求1所述方法，其中，所述PUCCH资源包括以下至少之一：公共PUCCH资源、MSG4消息对应的PUCCH资源、MSGB消息对应的PUCCH资源。
  11. 一种电子设备，所述电子设备包括：
    一个或多个处理器；
    存储器，用于存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-10中任一所述方法。
  12. 一种计算机可读存储介质，所述计算机可读存储介质存储有一个或多个程序，所述一个或多个程序被所述一个或多个处理器执行，以实现如权利要求1-10中任一所述方法。
PCT/CN2022/100526 2022-01-19 2022-06-22 一种资源配置方法、电子设备和存储介质 WO2023137972A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210062080.8A CN115843120A (zh) 2022-01-19 2022-01-19 一种资源配置方法、电子设备和存储介质
CN202210062080.8 2022-01-19

Publications (1)

Publication Number Publication Date
WO2023137972A1 true WO2023137972A1 (zh) 2023-07-27

Family

ID=85574654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/100526 WO2023137972A1 (zh) 2022-01-19 2022-06-22 一种资源配置方法、电子设备和存储介质

Country Status (2)

Country Link
CN (1) CN115843120A (zh)
WO (1) WO2023137972A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117858235A (zh) * 2024-03-06 2024-04-09 深圳国人无线通信有限公司 一种处理公共pucch资源的方法和基站

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109495966A (zh) * 2017-09-11 2019-03-19 电信科学技术研究院 用于传输下行数据的资源的确定和配置方法、终端和基站
WO2019139936A1 (en) * 2018-01-15 2019-07-18 Qualcomm Incorporated Group common control channel in ultra-reliable/low-latency communications
US20210006383A1 (en) * 2018-04-02 2021-01-07 Fujitsu Limited Resource scheduling method and apparatus, data transmission method and apparatus and communication system
CN113328841A (zh) * 2016-01-07 2021-08-31 诺基亚通信公司 用于分配确认资源的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113328841A (zh) * 2016-01-07 2021-08-31 诺基亚通信公司 用于分配确认资源的方法和装置
CN109495966A (zh) * 2017-09-11 2019-03-19 电信科学技术研究院 用于传输下行数据的资源的确定和配置方法、终端和基站
WO2019139936A1 (en) * 2018-01-15 2019-07-18 Qualcomm Incorporated Group common control channel in ultra-reliable/low-latency communications
US20210006383A1 (en) * 2018-04-02 2021-01-07 Fujitsu Limited Resource scheduling method and apparatus, data transmission method and apparatus and communication system

Also Published As

Publication number Publication date
CN115843120A (zh) 2023-03-24

Similar Documents

Publication Publication Date Title
US11323988B2 (en) Method and apparatus for transmitting a HARQ-ACK
EP3340521B1 (en) Physical downlink control channel transmission method and apparatus
US10355899B2 (en) PHICH transmission in time division duplex systems
WO2018121495A1 (en) Transmission with multiple numerologies in new radio system
CN109156018B (zh) 传输数据的方法、终端设备和网络设备
EP3780875A1 (en) Method, apparatus, and system for accessing channel in unlicensed band
US11792820B2 (en) Base station, terminal apparatus, first terminal apparatus, method, program, recording medium and system
US20230239193A1 (en) Signaling of demodulation reference signal configuration for uplink short tti transmissions
WO2016038510A1 (en) Resource allocation for mtc devices in a lte rel-13 communications system
US11153856B2 (en) Method and apparatus for transmitting uplink signal
US11595955B2 (en) Numerology options for new radio
AU2016414454A1 (en) Method and terminal device for transmitting data
WO2023137972A1 (zh) 一种资源配置方法、电子设备和存储介质
US11902215B2 (en) Method and apparatus for resource mapping in unlicensed spectrum
WO2017039496A1 (en) Network node and method for handling of downlink bandwidth in a multi-rat environment
US11343808B2 (en) Uplink data sending method and apparatus
EP4274338A1 (en) Resource mapping method and apparatus, and device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22921403

Country of ref document: EP

Kind code of ref document: A1