Resource configuration methods, electronic devices and storage media
The resource configuration method for RedCap UE optimizes PUCCH resource allocation by determining edge locations and adjusting offsets, resolving fragmentation and non-orthogonality issues to improve network capacity and maintain multiplexing capability.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2022-06-22
- Publication Date
- 2026-04-20
AI Technical Summary
The fragmentation of PUSCH resources and decreased uplink peak data rate in RedCap UE due to PUCCH resource splitting, along with non-orthogonal transmission sequences leading to reduced network capacity, are issues in RedCap technology.
A resource configuration method that determines edge location information of PUCCH resources based on base station signaling, uses a PUCCH resource set configuration table, and adjusts physical resource unit offsets to enable PUCCH transmission without frequency hopping, ensuring orthogonality and maintaining multi-user multiplexing capability.
This method reduces the impact on network performance and enhances network capacity by optimizing PUCCH resource configuration for RedCap UE, addressing fragmentation and non-orthogonality issues.
Smart Images

Figure 0007848337000033 
Figure 0007848337000034 
Figure 0007848337000035
Abstract
Description
Cross-reference to Related Applications
[0001] This application is filed based on a Chinese patent application with an application number of 202210062080.8 and an application date of January 19, 2022, claims the priority of this Chinese patent application, and all the contents of this Chinese patent application are incorporated herein by reference into this application.
Technical Field
[0002] This application relates to the field of wireless communication technologies, and particularly to resource configuration methods, electronic devices, and storage media.
Background Art
[0003] Reduced Capability (RedCap) is a new Internet of Things technology developed by the 3GPP standardization organization. It is mainly targeted at middle-end Internet of Things devices such as industrial wireless sensors, video monitoring, and wearable devices, and has characteristics such as low complexity, low cost, low power consumption, and compact size Compared with 5G enhanced mobile broadband eMBB and ultra-high reliability and low-latency communication uRLLC technologies, RedCap simplifies in terms of Bandwidth Part (BWP), number of antennas, number of Multiple Input Multiple Output (MIMO) layers, modulation order, etc., to achieve a trade-off between cost and performance.
[0004] RedCap technology needs to minimize the impact on network performance on the premise of meeting use case requirements. In the FR1 frequency band, usually NR User Equipment (UE) 's maximum supported bandwidth is 100M, but in order to achieve reduction of complexity and cost, RedCap UE 's maximum supported bandwidth is reduced to 20M. Since RedCap UE and normal NR UE share the public network, RedCap UEPhysical Uplink Control Channels located on both sides of the bandwidth : PUCCH) resources are usually NR UE Physical Uplink Share Channel : PUSCH) splits resources into multiple sub-parts, and the fragmentation problem of PUSCH resources occurs, which is a common issue in public networks. UE This leads to a decrease in the uplink peak data rate. Currently, at the 3GPP standards meeting, RedCap PUCCH frequency hopping in the initial access phase is being addressed. Disable It was decided to do so. Specifically, by adding SIB signaling to RedCap UE PUCCH frequency hopping Enable or Disable Instruct to do the following, PUCCH frequency hopping Disable RedCap UE This concentrates PUCCH resources on one side of the bandwidth, reducing PUCCH resource fragmentation problems.
[0005] In a licensed frequency spectrum, NR is typically used. UE In the initial access phase, it uses a frequency hopping scheme by default to transmit PUCCH resources to achieve greater uplink coverage and better transmission performance. However, SIB signaling is RedCap UE Frequency hopping Disable When giving instructions to do so, RedCap UE This transmits PUCCH without frequency hopping, and in this case, normal NR UE The conventional PUCCH resource configuration method for RedCap is UE It cannot be directly applied, and in order to ensure that the multi-user multiplexing capability remains unchanged, RedCap UEEach PUCCH resource set configured should also contain 16 PUCCH resources. UE and based on PUCCH non-frequency hopping transmission UE When PUCCH is transmitted by multiplexing into the same resource block, the non-orthogonality of the transmission sequence results in these two types UE This prevents the implementation of code division multiplexing, resulting in a decrease in network capacity. [Overview of the project] [Problems that the invention aims to solve]
[0006] The main objective of the embodiments of this application is to provide a resource configuration method, an electronic device, and a storage medium. [Means for solving the problem]
[0007] Embodiments of this application provide a resource configuration method. This method includes determining edge location information of a PUCCH resource based on base station signaling, determining a common PUCCH resource set in a PUCCH resource set configuration table based on the edge location information and SIB messages, and determining a PUCCH resource based on the edge location information and the physical resource unit offset corresponding to the common PUCCH resource set.
[0008] Embodiments of this application further provide an electronic device comprising one or more processors and 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 are made to implement one of the methods of the embodiments of this application.
[0009] Embodiments of the present application further provide a computer-readable storage medium. Here, one or more programs are stored in the computer-readable storage medium. When the one or more programs are executed by the one or more processors, any one of the methods in the embodiments of the present application is realized.
Brief Description of the Drawings
[0010] [Figure 1] It is a flowchart of a resource configuration method according to an embodiment of the present application. [Figure 2] It is a flowchart of another resource configuration method according to an embodiment of the present application. [Figure 3] It is a schematic structural diagram of a resource configuration device according to an embodiment of the present application. [Figure 4] It is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Modes for Carrying Out the Invention
[0011] It should be understood that the specific embodiments described herein are only used for interpreting the present application and are not for limiting the present application.
[0012] In the following description, for example, the suffixes "module", "member", or "unit" for representing elements are only used for the convenience of explaining the present application and have no inherent meaning by themselves. Therefore, "module", "member", or "unit" can be used interchangeably.
[0013] In the embodiments of the present application, RedCap UE and normal NR UE share one public network. The PUCCH resources located on both sides of the bandwidth of RedCap UE split the PUSCH resources of normal NR UE into multiple sub-parts, resulting in the fragmentation problem of PUSCH resources, so that normal NR UEThe uplink peak data rate will decrease. Usually NR UE is initial access The common PUCCH resource set configuration table 2.1 used in the initial stage is as follows.
[0014]
Table 1
[0015] JPEG0007848337000002.jpg209170
[0016] When SIB signaling instructs to perform PUCCH frequency hopping, RedCap Disable transmits PUCCH in a way that does not perform frequency hopping. At this time, the PUCCH resource configuration method for the above normal NR UE cannot be directly applied to RedCap UE And in order to ensure that the multi-user multiplexing ability remains unchanged, each PUCCH resource set configured in RedCap UE should also include 16 PUCCH resources. Note that when PUCCH based on frequency hopping transmission UE and PUCCH based on non-frequency hopping transmission UE are multiplexed on the same resource block to transmit PUCCH, due to the non-orthogonality of the transmission sequences, these two types of UE cannot achieve code division multiplexing, thus the network capacity will decrease. UE
[0017] UE Figure 1 is a flowchart of the resource configuration method according to an embodiment of the present application. The embodiment of the present application can be applied to the situation where RedCap UE transmits resource configuration. This method can be executed by a resource configuration device. This device can also be realized by software and / or hardware methods, and usually RedCap UEIt is concentrated in Figure 1. The method according to the embodiment of this application specifically includes the following steps.
[0018] In step 110, the edge location information of the PUCCH resource is determined based on base station signaling.
[0019] Here, edge position information is RedCap UE The position may be within the Bandwidth Part (BWP) of the PUCCH resource used. The edge position information may indicate the upper edge, lower edge, both sides of the uplink BWP, or one side of the uplink BWP, or both sides of the uplink BWP.
[0020] In the embodiments of this application, RedCap UE The base station signaling may indicate the edge location information of the PUCCH resource to be used. The base station signaling may determine the location of the PUCCH resource on the uplink BWP. For example, it may be the upper edge, lower edge, both sides of the uplink BWP, or the upper edge, lower edge, one side of the uplink BWP, or both sides of the uplink BWP.
[0021] In step 120, the common PUCCH resource set is determined in the PUCCH resource set configuration table based on edge location information and SIB messages.
[0022] Specifically, RedCap UE Using the determined edge location information and System Information Blocks (SIB) messages, a single common PUCCH resource set can be jointly determined in the PUCCH resource set configuration table, where the PUCCH resource set configuration table is RedCap UE Maintenance may be performed jointly by the base station and the other party.
[0023] In step 130, the PUCCH resource is determined based on edge location information and the physical resource unit offset corresponding to the common PUCCH resource set.
[0024] In the embodiments of this application, the physical resource unit offset set in the common PUCCH resource set is determined, and RedCap is selected according to this physical resource unit offset and edge position information. UE The location of the PUCCH resources used may be determined by this. For example, RedCap UE The PUCCH resource frequency domain position and parameters such as the initial cyclic shift setting used may be determined by this.
[0025] The embodiment of this application determines edge location information of PUCCH resources by base station signaling, determines a common PUCCH resource set in a PUCCH resource set configuration table using edge location information and SIB messages, determines PUCCH resources using edge location information and physical resource unit offsets corresponding to the common PUCCH resource set, and RedCap UE This PUCCH resource configuration can be implemented, reducing the impact on public network performance and improving network capacity.
[0026] Furthermore, based on the embodiments of the above application, base station signaling is the remaining minimum system information (SIB1), downlink control information (DCI), and other systems information It includes at least one of the following.
[0027] In the embodiments of this application, the remaining minimum system information (SIB1) or Downlink Control Information (DCI) via RedCap UE The location of the PUCCH resource used by the RedCap may be indicated on the uplink BWP. UESend to other systems information You may use this to indicate the edge location information of the PUCCH resource.
[0028] Furthermore, based on the embodiments of the above application, the edge position information includes at least one case of the upper edge of the uplink BWP, the lower edge of the uplink BWP, both sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or one side of the uplink BWP, or both sides of the uplink BWP.
[0029] In the embodiments of this application, edge position information may refer to the PUCCH being located on the upper edge, lower edge, both sides of the uplink BWP, or on one side of the uplink BWP, both sides of the uplink BWP, etc.
[0030] Furthermore, based on the embodiments of the above application, the PUCCH resource set configuration table is typically NR UE It includes at least one of the following: a common PUCCH resource set configuration table and a dedicated PUCCH resource set configuration table.
[0031] Specifically, the PUCCH resource set configuration table is usually NR UE This could also be a common PUCCH resource set configuration table, i.e., RedCap UE Normally, NR UE You may share the same PUCCH resource set configuration table. Alternatively, you can use RedCap. UE It may maintain a separate, dedicated PUCCH resource set configuration table. In this case, all or part of the contents of this PUCCH resource set configuration table are usually NR UE This may differ from the common resource set configuration table.
[0032] Furthermore, based on the embodiment of the above application, the physical resource unit offset included in the dedicated PUCCH resource set configuration table and the normal NR UEThe physical resource unit offset in the common PUCCH resource set configuration table exhibits a linear relationship.
[0033] In the embodiments of this application, the value of the Physical Resource Block offset (PRB offset) in the dedicated PUCCH resource set configuration table is normally NR UE The physical resource unit offset values in the common PUCCH resource set configuration table may have a linear relationship with the values in the common PUCCH resource set configuration table. In this case, the physical resource unit offsets in the dedicated PUCCH resource set configuration table are usually NR UE This may be obtained by linearly transforming the physical resource unit offset of the common PUCCH resource set configuration table. For example, typically NR UE The physical resource unit offsets in the common PUCCH resource set configuration table may be multiplied or added, and the result of the calculation may be used as the physical resource unit offset in the dedicated PUCCH resource set configuration table. To make it clear, the conversion parameters used in the linear conversion process may be indicative values or preset values. Furthermore, to make it clear, multiple physical resource unit offsets included in the dedicated PUCCH resource set configuration table may each be normally NR UE The linear relationships that fit multiple physical resource unit offsets in the common PUCCH resource set configuration table may differ. For example, the physical resource unit offsets at indices 0 to 14 in the dedicated PUCCH resource set configuration table may each be different. UE The physical resource unit offsets at indices 0 to 14 in the common PUCCH resource set configuration table conform to a multiplicative linear relationship, while the physical resource unit offset at index 15 in the dedicated PUCCH resource set configuration table conforms to a typical NR UE This may conform to an additive linear relationship between the physical resource unit offset at index 15 in the common PUCCH resource set configuration table.
[0034] Figure 2 is a flowchart of another resource configuration method according to an embodiment of the present application. The embodiment of the present application is a concrete example based on the embodiment of the above application. Referring to Figure 2, the method according to the embodiment of the present application specifically includes the following steps.
[0035] In step 210, the edge location information of the PUCCH resource is determined based on base station signaling.
[0036] In step 220, the common PUCCH resource set is determined in the PUCCH resource set configuration table based on edge location information and SIB messages.
[0037] In step 230, an additional offset coefficient for the configuration is determined based on edge location information and / or base station signaling, and the physical resource unit offset is determined based on the additional offset coefficient.
[0038] Here, the additional offset coefficient is RedCap UE But usually NR UE This may be an additional offset amount based on the physical resource units used. This additional offset coefficient is typically NR UE It may be used to perform a linear operation with the physical resource unit offset in the PUCCH resource set configuration table.
[0039] In embodiments of this application, it may be determined whether an additional offset coefficient is set by edge location information and / or base station signaling. After it is determined that an additional offset coefficient is set, this additional offset coefficient is used to RedC AP UE This may be used to determine the physical resource unit offset used by, or it may be used to perform a linear operation on the physical resource unit offset included in the common PUCCH resource set. This determination process is performed by linearly calculating the result of the physical resource unit offset in the common PUCCH resource set and an additional offset coefficient in RedCap. UE This may be the physical resource unit offset used by [the system]. For example, the sum or product of the physical resource unit offset included in the common PUCCH resource set and an additional offset coefficient may be used as the new physical resource unit offset.
[0040] In step 240, the PUCCH resource is determined based on edge location information and the physical resource unit offset corresponding to the common PUCCH resource set.
[0041] Furthermore, based on the embodiments of the above application, an additional offset coefficient is set by a System Information Block (SIB) message or Downlink Control Information (DCI). The additional offset coefficient adjusts the physical resource unit offset based on an addition or multiplication operation. The number of bits occupied by the additional offset coefficient includes at least one of 1 bit, 2 bits, or 3 bits.
[0042] Specifically, RedCap UE The additional offset coefficient used may be set by an SIB message or downlink control information (DCI). The additional offset coefficient may be used to perform multiplication or addition operations with the physical resource unit PRB. The result of this operation may be the physical resource unit offset used by RedCap. The additional offset coefficient may occupy 1, 2, or 3 bits.
[0043] Furthermore, based on the embodiments of the above application, the OFDM symbol of the PUCCH resource includes at least two parts. The frequency hopping index parameter value of the PUCCH transmission sequence corresponding to the OFDM symbol of each part includes 0, 1, or a value indicated by signaling.
[0044] In the embodiments of this application, an orthogonal frequency division multiplexing (OFMD) symbol occupied by a PUCCH resource configured in RedCap may include at least two parts. The frequency hopping index parameter of the PUCCH transmission sequence corresponding to the OFDM symbol in each part may be 0, 1, or a value indicated by signaling. The value of the frequency hopping index parameter may indicate whether the PUCCH transmission sequence performs frequency hopping.
[0045] JPEG0007848337000003.jpg74170
[0046] JPEG0007848337000004.jpg48170
[0047] Furthermore, based on the embodiments of the above application, the PUCCH resource includes at least one of a common PUCCH resource, a PUCCH resource corresponding to an MSG4 message, and a PUCCH resource corresponding to an MSGB message.
[0048] JPEG0007848337000005.jpg85170
[0049] Furthermore, a new field, Additional_PRBoffset, may be defined in the SIB or DCI. This field may represent an additional offset coefficient. If the field Additional_PRBoffset is not set, RedCap UE Normally, NR UE The common PUCCH resource set configuration table 2.1 is used by default.
[0050] JPEG0007848337000006.jpg60170
[0051] JPEG0007848337000007.jpg121170
[0052] JPEG0007848337000008.jpg78170
[0053] JPEG0007848337000009.jpg82170
[0054] JPEG0007848337000010.jpg64170
[0055] JPEG0007848337000011.jpg74170
[0056] Furthermore, a new field, Additional_PRBoffset, may be defined in the SIB or DCI. This field may represent an additional offset coefficient. If the field Additional_PRBoffset is not set, RedCap UE Normally, NR UE The common PUCCH resource set configuration table 2.1 is used by default.
[0057] JPEG0007848337000012.jpg74170
[0058] JPEG0007848337000013.jpg110170
[0059] JPEG0007848337000014.jpg115170
[0060] JPEG0007848337000015.jpg65170
[0061] JPEG0007848337000016.jpg84170
[0062] Furthermore, based on the embodiments of the above application, a new field Additional_PRBoffset is defined in the SIB or DCI to represent an additional offset coefficient. If the field Additional_PRBoffset is not set, RedCap UE Normally, NR UEThe common PUCCH resource set configuration table 2.2 is used by default.
[0063] JPEG0007848337000017.jpg69170
[0064] Table 2.2: RedCap UE Common PUCCH resource set configuration during the initial access phase [Table 2]
[0065] Here, in Table 2.2, RedCap UE The physical resource unit offset PRB_offset used by is typically NR UE The result may be obtained by linear processing of the physical resource unit offsets in the common PUCCH resource set configuration table 2.1 used by the system. This linear processing may include multiplication or addition.
[0066] JPEG0007848337000019.jpg107170
[0067] JPEG0007848337000020.jpg102170
[0068] JPEG0007848337000021.jpg69170
[0069] In one exemplary embodiment, PUCCH frequency hopping is enabled. UE PUCCH frequency hopping is disabled. UE When a PUCCH is transmitted within the same resource block, there are two types UE The sequence transmitted by is non-orthogonal, which leads to a reduction in network capacity. Based on the embodiments of the above application, the basic sequence and cyclic shift are further processed to enable different types UEBy implementing code division multiplexing, the multi-user multiplexing capability can be enhanced. Specifically, the low PAPR sequence transmitted in the PUCCH resource is represented as follows:
[0070] JPEG0007848337000022.jpg67170
[0071] JPEG0007848337000023.jpg89170
[0072] JPEG0007848337000024.jpg73170
[0073] JPEG0007848337000025.jpg67170
[0074] JPEG0007848337000026.jpg48170
[0075] In the case of PUCCH frequency hopping transmission, different frequencies are transmitted within different time periods under the same frequency domain resources. UE It could be a PUCCH sequence, and the corresponding initial cycle prefix is also different. PUCCH frequency hopping is disabled in RedCap. UE For this purpose, the initial cycle prefix corresponding to PUCCH transmissions at different time intervals under the same frequency domain resource is constant, and there are multiple normal ones with different initial cyclic shifts. NR UE It is difficult to maintain orthogonality simultaneously with PUCCH transmission. For this reason, this embodiment uses RedCap. UE By dividing the OFDM symbol for PUCCH transmission into multiple sub-parts and setting a different initial cyclic shift for each of these sub-parts, NR UE We propose to achieve code division multiplexing with respect to this.
[0076] JPEG0007848337000027.jpg109170
[0077] JPEG0007848337000028.jpg63170
[0078] RedCap UE For PUCCH transmission, the RRC signaling PUCCH-ConfigCommon is used to configure PUCCH resource information during the initial access phase. Here, the scramble identifier parameter hoppingId, the power control parameter p0-nominal, the group frequency hopping parameter pucch-GroupHopping, and the common PUCCH resource index parameter pucch-ResourceCommon are all typically used to meet the needs of frequency division multiplexing or uplink overlay reinforcement. NR UE It may be shared with or configured independently.
[0079] Figure 3 is a schematic diagram of the structure of a resource configuration device according to an embodiment of this application, and can perform the method according to any embodiment of this application, and comprises a functional module and beneficial effects corresponding to the execution of the method. This device may be implemented by software and / or hardware. Specifically, it comprises a position determination module 301, a resource set module 302, and a resource configuration module 303.
[0080] The location determination module 301 is used to determine the edge location information of PUCCH resources based on base station signaling.
[0081] The resource set module 302 is used to determine the common PUCCH resource set in the PUCCH resource set configuration table based on the edge location information and the SIB message.
[0082] The resource configuration module 303 is used to determine the PUCCH resource based on the edge location information and the physical resource unit offset corresponding to the common PUCCH resource set.
[0083] The embodiment of this application comprises a location determination module that determines edge location information of PUCCH resources based on base station signaling, a resource set module that determines a common PUCCH resource set in a PUCCH resource set configuration table using edge location information and SIB messages, and a resource configuration module that determines a PUCCH resource using edge location information and a physical resource unit offset corresponding to the common PUCCH resource set, thereby enabling RedCap UE This PUCCH resource configuration can be implemented to reduce the impact on the performance of the public network and improve network capacity.
[0084] Furthermore, based on the embodiments of the above application, base station signaling in the device is the remaining minimum system information (SIB1), downlink control information (DCI), and other systems information It includes at least one of the following.
[0085] Furthermore, based on the embodiments of the above application, the edge position information in the device includes at least one case of the upper edge of the uplink BWP, the lower edge of the uplink BWP, both sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or one side of the uplink BWP, or both sides of the uplink BWP.
[0086] Furthermore, based on the embodiments of the above application, the PUCCH resource set configuration table in the device is typically NR UE It includes at least one of the following: a common PUCCH resource set configuration table and a dedicated PUCCH resource set configuration table.
[0087] Furthermore, based on the embodiment of the above application, the physical resource unit offset included in the dedicated PUCCH resource set configuration table in the device and the normal NR UE The physical resource unit offset in the common PUCCH resource set configuration table exhibits a linear relationship.
[0088] Furthermore, the invention further comprises an offset coefficient module for determining an additional offset coefficient configured based on edge location information and / or base station signaling, based on the embodiments of the above application, and for determining the physical resource unit offset based on the additional offset coefficient.
[0089] Furthermore, based on the embodiments of the above application, an additional offset coefficient in the offset coefficient module is set by a scheduling message SIB or downlink control information (DCI). The additional offset coefficient adjusts the physical resource unit offset based on an addition or multiplication operation. The number of bits occupied by the additional offset coefficient includes at least one of 1 bit, 2 bits, or 3 bits.
[0090] Furthermore, based on the embodiments of the above application, the OFDM symbol of the PUCCH resource includes at least two parts. The frequency hopping index parameter value of the PUCCH transmission sequence corresponding to the OFDM symbol of each part includes 0, 1, or a value indicated by signaling.
[0091] JPEG0007848337000029.jpg33170
[0092] Furthermore, based on the embodiments of the above application, the PUCCH resource includes at least one of a common PUCCH resource, a PUCCH resource corresponding to an MSG4 message, and a PUCCH resource corresponding to an MSGB message.
[0093] Figure 4 is a schematic diagram of the structure of an electronic device according to an embodiment of this application. This electronic device comprises a processor 40, a memory 41, an input device 42, and an output device 43. The number of processors 40 in the electronic device may be one or more. In Figure 4, one processor 40 is used as an example. The processor 40, memory 41, input device 42, and output device 43 in the electronic device may be connected by a bus or by other means, and in Figure 4, they are connected by a bus as an example.
[0094] Memory 41 may be used as a computer-readable storage medium to store software programs. The computer can execute programs and modules, for example, modules corresponding to the apparatus in the embodiment of this application (location determination module 301, resource set module 302, and resource configuration module 303). The processor 40 executes various functions and data processing of the electronic device by running the software programs, instructions, and modules stored in memory 41, that is, realizes the above method.
[0095] Memory 41 mainly includes a program storage area and a data storage area. Here, the program storage area can store the operating system and application programs necessary for at least one function. The data storage area can store data created in accordance with the use of the electronic device, etc. Memory 41 may also include high-speed random access memory or non-volatile memory. For example, it may be at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory device. In some examples, memory 41 may further include memory installed remotely from the processor 40. These remote memories may be connected to the electronic device via a network. Examples of the above network include, but are not limited to, the Internet, a corporate intranet, a local area network, a mobile communication network, and combinations thereof.
[0096] The input device 42 may be used to receive input numerical or character information and to generate key signal inputs 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.
[0097] Embodiments of this application further provide a storage medium including computer executable instructions. The computer executable instructions are used to execute a resource configuration method when executed by a computer processor, and this method is Determining the edge location information of PUCCH resources based on base station signaling, Based on the aforementioned edge location information and SIB messages, a common PUCCH resource set is determined in the PUCCH resource set configuration table, The PUCCH resource is determined based on the edge location information and the physical resource unit offset corresponding to the common PUCCH resource set. Includes.
[0098] As will be clear to any professional in the field from the above description of the embodiments, this application may be implemented by software and necessary general-purpose hardware. While it may certainly be implemented by hardware, in many cases the former is a more preferred embodiment. With this understanding, the portion of the proposed technology of this application that substantially contributes to or to the prior art may be embodied in the form of a software product. This computer software product may be stored on a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk, or optical disk, and may include some instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in each embodiment of this application.
[0099] It should be noted that, in the embodiments of the above-described apparatus, the units and modules included are merely distinguished by their functional logic and are not limited to the above classifications. They only need to be able to realize the corresponding function. Furthermore, the specific names of each functional unit are merely for the purpose of making them easily distinguishable from one another and are not intended to limit the scope of protection of this application.
[0100] As those skilled in the art will understand, all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.
[0101] In hardware embodiments, the distinctions between functional modules / units referred to in the above description do not necessarily correspond to distinctions between physical assemblies. For example, a single physical assembly may have multiple functions, or a single function or step may be performed by the cooperation of several physical assemblies. Some or all physical assemblies may be implemented as software executed by a processor, such as a central processor, digital signal processor, or microprocessor; or as hardware; or as an integrated circuit, such as a dedicated integrated circuit. Such software may be distributed on computer-readable media, which may include computer storage media (or non-temporary media) and communication media (or temporary media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and fixed media implemented in any method or technique for storing information (e.g., computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other media that can be used to store desired information and can be accessed by a computer. Furthermore, as traders should be aware, communication media generally include computer-readable instructions, data structures, program modules or other data in modulated data signals such as carriers or other transmission mechanisms, and may also include any information distribution media.
[0102] Although some embodiments of this application have been described above with reference to the drawings, this is not intended to limit the scope of the rights of this application. Any modifications, equivalent substitutions, and improvements that a person skilled in the art can make without departing from the scope and substance of this application should all fall within the scope of the rights of this application.
Claims
【Request Item 1】
2. The edge location information indicates the lower edge of the uplink bandwidth portion (UL BWP), and determining the PUCCH resource includes determining the PUCCH resource in ascending order of physical resource blocks (PRBs) from the lower edge of the UL BWP, or The edge position information indicates the upper edge of the UL BWP, and determining the PUCCH resource includes determining the PUCCH resource in descending order of the PRB from the upper edge of the UL BWP. The method according to claim 1.
3. The edge location information is received in base station signaling, and the base station signaling includes at least one of the remaining minimal system information (SIB1), downlink control information (DCI), and other system information. The method according to claim 1.
4. The edge position information includes at least one case of the upper edge of the uplink BWP, the lower edge of the uplink BWP, both sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or one side of the uplink BWP, or both sides of the uplink BWP. The method according to claim 1.
5. The PUCCH resource includes at least one of the following: a common PUCCH resource, a PUCCH resource corresponding to an MSG4 message, or a PUCCH resource corresponding to an MSGB message. The method according to claim 1.
6. The aforementioned additional offset coefficient is configured to adjust the physical resource block offset based on an addition or multiplication operation. The method according to claim 1.
7. The aforementioned additional offset coefficient includes at least one of 4, 6, 8, 9, 10, 2, -4, or 0. The method according to claim 1.
8.
9. The edge location information indicates the lower edge of the uplink bandwidth portion (UL BWP), and the PUCCH resource is determined in ascending order of physical resource blocks (PRBs) from the lower edge of the UL BWP, or The aforementioned edge position information indicates the upper edge of the UL BWP, and the PUCCH resource is determined in descending order of the PRB from the upper edge of the UL BWP. The method according to claim 8.
10. The edge location information is transmitted in base station signaling, and the base station signaling includes at least one of the remaining minimal system information (SIB1), downlink control information (DCI), and other system information. The method according to claim 8.
11. The edge position information includes at least one of the upper edge of the uplink BWP, the lower edge of the uplink BWP, both sides of the uplink BWP, or the upper edge of the uplink BWP, the lower edge of the uplink BWP, or one side of the uplink BWP, or both sides of the uplink BWP. The method according to claim 8.
12. The aforementioned additional offset coefficient is configured to adjust the physical resource block offset based on an addition or multiplication operation. The method according to claim 8.
13. The aforementioned additional offset coefficient includes at least one of 4, 6, 8, 9, 10, 2, -4, or 0. The method according to claim 8.
14.
15. One or more processors, An electronic device comprising 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 are made to implement the method described in claim 8. electronic equipment.
16. A computer-readable storage medium that stores one or more programs and, when the one or more programs are executed by one or more processors, realizes the method according to claim 1.