Communication of parameters of number of resource blocks (RBs) and mapping type for physical uplink control channel (PUCCH) configuration

Abstract

An apparatus and method for communicating a parameter of a number of resource blocks (RBs) 502 and a parameter of a mapping type for a physical uplink control channel (PUCCH) configuration. The apparatus 102 determines a connection status. In response to determining that the connection status is not connected, the apparatus 102 selects one of the first parameters indicating the number of RBs 502 and one of the second parameters indicating the mapping type included in a previously received configuration for transmission of the PUCCH having a predefined table including the first and second parameters. In response to determining that the connection status is connected, the apparatus 102 receives a dedicated PUCCH resource configuration (a radio resource control (RRC) message) having a third parameter indicating the number of RBs 502 and a fourth parameter indicating the mapping type. The apparatus 102 generates a PUCCH transmission in response to the selected first and second parameters or the received third and fourth parameters.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Patent Application No. 63 / 186,404, filed on May 10, 2021, in favor of Ali Ramadan Ali, entitled “APPARATUSES, METHODS, AND SYSTEMS FOR RESOURCE INDICATION FOR MULTI-RB PUCCH FORMATS 0, 1, AND / OR 4,” which is incorporated by reference in its entirety.

[0002] The subject matter disclosed herein relates generally to wireless communications, and more particularly, to communicating number of resource blocks (RBs) and mapping type parameters for a physical uplink control channel (PUCCH) configuration. [Background technology]

[0003] Two mapping options for PUCCH configuration have been discussed in several wireless communication networks, but there is no specific agreement on the supported mapping methods or on the indication / signaling procedures. Summary of the Invention [Means for solving the problem]

[0004] A method is disclosed for communicating a parameter of a number of RBs and a parameter of a mapping type for a PUCCH configuration. An apparatus and a system also perform the functions of these methods. An embodiment of the method includes determining a connection status of a UE. In some embodiments, in response to determining that the connection status is in a disconnected state, one of the first parameters indicating the number of RBs and one of the second parameters indicating the mapping type included in a previously received configuration for transmission of the PUCCH having a predefined table including the first and second parameters is selected. In some embodiments, in response to determining that the connection status is in a connected state, a dedicated PUCCH resource configuration (Radio Resource Control (RRC) message) having a third parameter indicating the number of RBs and a fourth parameter indicating the mapping type is received, and in response to the selected first and second parameters or the received third and fourth parameters, a PUCCH transmission is generated.

[0005] An apparatus for communicating a parameter of a number of RBs and a parameter of a mapping type for a PUCCH configuration includes a user equipment. In some embodiments, the apparatus includes a receiver, a transmitter, a processor, and a memory storing code executable by the processor. The code causes the processor to determine a connection status of the apparatus, and in response to determining that the connection status is unconnected, select one of the first parameters indicating the number of RBs and one of the second parameters indicating the mapping type included in a previously received configuration for transmission of the PUCCH having a predefined table including the first and second parameters, in response to determining that the connection status is connected, receive a dedicated PUCCH resource configuration (RRC message) having a third parameter indicating the number of RBs and a fourth parameter indicating the mapping type, and in response to determining that the connection status is connected, generate a PUCCH transmission in response to the selected first and second parameters or the received third and fourth parameters.

[0006] Another apparatus for communicating parameters of a number of RBs and a mapping type for a PUCCH configuration to facilitate generation of a PUCCH transmission includes a network unit. In some embodiments, the network unit includes a receiver, a transmitter, a processor, and a memory storing code executable by the processor. The code causes the processor to generate an index configured to identify a first parameter indicating a number of RBs and a second parameter indicating a mapping type included in a previously determined configuration for transmission of the PUCCH having a predefined table including the first and second parameters, transmit the index via the transmitter to a remote unit determined to be in an idle mode, receive a selection result of the first and second parameters from the remote unit via the receiver, perform an acknowledgement of the received selection result, and transmit the acknowledgement to the remote unit via the transmitter.

[0007] A more particular description of the embodiments briefly described above will be provided by reference to specific embodiments illustrated in the accompanying drawings, in which the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, with the understanding that these drawings depict only some embodiments and therefore should not be considered limiting in scope. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for communicating parameters of number of RBs and mapping type for PUCCH resource indication. [Diagram 2] FIG. 1 is a schematic block diagram illustrating an embodiment of an apparatus that can be used to communicate parameters of number of RBs and mapping type for PUCCH resource indication. [Diagram 3]FIG. 1 is a schematic block diagram illustrating an embodiment of an apparatus that can be used to communicate parameters of number of RBs and mapping type for PUCCH resource indication. [Figure 4] 1 is a schematic block diagram illustrating an embodiment of a system for communicating parameters of number of RBs and mapping type for PUCCH resource indication. [Diagram 5] 1 is a schematic block diagram illustrating an embodiment of a system for communicating parameters of number of RBs and mapping type for PUCCH resource indication. [Figure 6] FIG. 1 is a flow chart diagram illustrating one embodiment of a method for communicating parameters of number of RBs and mapping type for PUCCH resource indication. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, an apparatus, a method, or a program product. Thus, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be referred to generally herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied as one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmission. The storage devices may not embody signals. In one particular embodiment, the storage devices use signals only to access the code.

[0010] Some of the functional units described herein may be referred to as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented as a programmable hardware device such as a field programmable gate array, programmable array logic, programmable logic device, or the like.

[0011] The modules may also be implemented as code and / or software for execution by various types of processors. An identified module of code may, by way of example, include one or more physical or logical blocks of executable code, which may, by way of example, be organized as an object, procedure, or function. Nevertheless, the executable files of the identified modules need not be physically located together, but may be stored in different locations and may include entirely different instructions that, when logically combined together, comprise the modules and achieve the stated purpose of the modules.

[0012] In practice, a module of code may be a single instruction, or many instructions, and may be distributed across several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein in modules, and may be embodied in any suitable form and organized in any suitable type of data structure. The operational data may be collected as a single data set or may be distributed across different locations, including across different computer-readable storage devices. If a module or portions of a module are implemented as software, the software portions are stored on one or more computer-readable storage devices.

[0013] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0014] More specific examples of storage devices (non-exhaustive list) include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0015] The code for carrying out the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine code such as assembly language. The code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or wide area network ("WAN"), or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider).

[0016] Throughout this specification, reference to "one embodiment," "an embodiment," or similar phrases means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Thus, the phrases "in one embodiment," "in an embodiment," and similar phrases, when they appear throughout this specification, may, but do not necessarily, all refer to the same embodiment, but may mean "one or more, but not all, embodiments," unless expressly specified otherwise. The words "including," "comprising," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. An enumerated list of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The words "a," "an," and "the" also refer to "one or more" unless expressly specified otherwise.

[0017] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the description that follows, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, and the like, to provide a thorough understanding of the embodiments. However, one of ordinary skill in the art will recognize that the embodiments may be practiced without one or more of the specific details, or may be practiced with other methods, components, materials, and the like. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0018] Aspects of the embodiments are described below with reference to schematic flow chart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow chart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flow chart illustrations and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce machine such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts defined in one or more blocks of the schematic flow chart illustrations and / or schematic block diagrams.

[0019] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to function in a particular manner such that the instructions stored in the storage device produce an article of manufacture that includes instructions that implement the functions / acts defined in one or more blocks of the schematic flow chart diagrams and / or schematic block diagrams.

[0020] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps, thereby producing a computer-implemented process; thus, the code running on the computer or other programmable apparatus effects a process for implementing the functions / acts defined in one or more blocks of the flowcharts and / or block diagrams.

[0021] The schematic flow chart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flow chart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing a defined logical function(s).

[0022] It should also be noted that in some alternative embodiments, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks of the illustrated figures, or portions thereof.

[0023] Various arrow and line types may be used in the flowchart diagrams and / or block diagrams, but it is understood that they do not limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiments. By way of example, the arrows may indicate waiting or monitoring periods of indefinite duration between recited steps of the illustrated embodiments. It will also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by dedicated hardware-based systems that perform the specified functions or acts, or a combination of dedicated hardware and code.

[0024] The description of an element in each figure may refer to the element in the proceeding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0025] 1 illustrates an embodiment of a wireless communication system 100 for communicating parameters of number of RBs and mapping type for PUCCH resource indication. In one embodiment, the wireless communication system 100 includes a remote unit (device, user equipment) 102 and a network unit (gNB) 104. Although a specific number of remote units 102 and network units 104 are shown in FIG. 1, one skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0026] In one embodiment, the remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, gaming consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, the remote unit 102 includes wearable devices such as smart watches, fitness bands, optical head mounted displays, etc. Additionally, the remote unit 102 may be referred to as a subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals.

[0027] The network units 104 may be distributed across a geographical region. In some embodiments, the network units 104 may also be referred to as access points, access terminals, base, base stations, Node Bs, eNBs, gNBs, home Node Bs, relay nodes, devices, core networks, aerial servers, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the Public Switched Telephone Network, among other networks. These and other elements of the radio access network and the core network are not shown, but are generally well known to those skilled in the art.

[0028] In one embodiment, the wireless communication system 100 is compliant with the 3GPP protocol, where the network unit 104 transmits on the DL using an Orthogonal Frequency Division Multiplexing (OFDM) modulation scheme and the remote unit 102 transmits on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as worldwide interoperability for microwave access (WiMAX), among other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0029] The network unit 104 may serve several remote units 102 in a service area, e.g., a cell or a cell sector, via wireless communication links. The network unit 104 transmits download (DL) communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0030] In various embodiments, the remote unit 102 determines its connection status and then selects or receives a number of RBs and a mapping type based on the determined connection status. The remote unit 102 generates a PUCCH transmission based on the selected number of RBs and mapping type.

[0031] In some embodiments, the network unit 104 may generate an index configured to identify a first parameter indicating the number of RBs and a second parameter indicating the mapping type included in a previously determined configuration for transmission of the PUCCH having a predefined table including the first and second parameters, and transmit the generated index to the remote unit determined to be in the idle mode. In some embodiments, the network unit 104 may receive a selection result of the first and second parameters from the remote unit, perform an acknowledgement of the received selection result, and transmit the acknowledgement to the remote unit 102.

[0032] 2 illustrates an embodiment of an apparatus 200 that can be used to communicate parameters of the number of RBs and the mapping type for a PUCCH configuration. The apparatus 200 includes an embodiment of the remote unit 102. Additionally, the remote unit 102 can include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0033] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), a co-processor, a field programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0034] Memory 204, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 204 includes a volatile computer storage medium. For example, memory 204 can include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 204 includes a non-volatile computer storage medium. For example, memory 204 can include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system and other controller algorithms running on remote unit 102.

[0035] The input device 206, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus pen, a microphone, etc. In some embodiments, the input device 206 may be integrated with the display 208, for example as a touch screen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0036] The display 208, in one embodiment, can include any known electronically controllable display or display device. The display 208 can be designed to output visual, auditory, and / or tactile signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 can include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the display 208 can include a wearable display, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the display 208 can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0037] In some embodiments, the display 208 includes one or more speakers for generating sound. For example, the display 208 can generate an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be positioned proximate the input device 206.

[0038] In one embodiment, the remote unit 102 determines a connection status of the remote unit 102 and, in response to determining that the connection status is not connected, selects one of the first parameters indicating the number of RBs and one of the second parameters indicating the mapping type included in a previously received configuration for transmission of the PUCCH having a predefined table including the first and second parameters. In some embodiments, in response to determining that the connection status is connected, the remote unit 102 receives a dedicated PUCCH resource configuration (a radio resource control (RRC) message) having a third parameter indicating the number of RBs and a fourth parameter indicating the mapping type, and generates a physical uplink control channel (PUCCH) transmission in response to the selected first and second parameters or the received third and fourth parameters.

[0039] As described herein, the transmitter 210 is used to provide UL communication signals to the network unit 104, and the receiver 212 is used to receive DL communication signals from the network unit 104. Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0040] 3 illustrates an embodiment of an apparatus 300 that can be used to communicate parameters of number of RBs and mapping type for a PUCCH configuration. The apparatus 300 includes an embodiment of the network unit 104. Furthermore, the network unit 104 can include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 can be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0041] The network unit includes a receiver, a transmitter, a processor, and a memory storing code executable by the processor, the code causing the processor to generate an index configured to identify a first parameter indicating a number of resource blocks (RBs) and a second parameter indicating a mapping type included in a previously determined configuration for transmission of a physical uplink control channel (PUCCH) having a predefined table including the first and second parameters, transmit the index to a remote unit determined to be in an idle mode, receive a selection result of the first and second parameters from the remote unit, perform an acknowledgement of the received selection result, and transmit the acknowledgement to the remote unit.

[0042] Although only one transmitter 310 and one receiver 312 are shown, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and receiver 312 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and receiver 312 may be part of a transceiver.

[0043] It should be noted that one or more embodiments described herein may be combined into a single embodiment.

[0044] In some embodiments, PUCCH formats 0, 1, 4 are designed such that they span only a single PRB. A single PRB is good enough to send a small amount of UCI information with a good peak-to-average power ratio (PAPR) on a licensed spectrum. There is no solution in the specification (PUCCH resource configuration) to handle the PSD problem of the single PRB format in the case of unlicensed spectrum.

[0045] In various embodiments, a signaling procedure is provided for indicating the number of RBs and the RB mapping type for enhanced PUCCH formats 0 / 1 / 4 or other existing or new PUCCH formats in unlicensed bands under PSD limitations. The procedure includes: 1. Indicating the number of RBs and the type of mapping before a radio resource control (RRC) connection; 2. Indicating the number of RBs and mapping type for a dedicated PUCCH configuration for an RRC connected UE; and / or 3. Indicating Dynamic Downlink Control Information (DCI) indications to enable / disable / update PUCCH RB configuration Includes.

[0046] In various embodiments, a PUCCH transmission design based on combining long sequences with frequency domain repetition is provided to achieve a trade-off between multiplexing gain and coverage gain.

[0047] In a first embodiment, the number of RBs and mapping type are indicated before RRC connection. The UE is pre-configured with multiple PUCCH resource sets with a table including the number of RBs used to improve the coverage of PUCCH transmissions carrying message (Msg)4 / MsgB positive / negative acknowledgement (ACK / NACK) information during initial access. The number of RBs is based on the available RBs and supported SCS in the initial bandwidth part (BWP) and the number of cyclic shifts per PUCCH resource. In one embodiment, for UEs before receiving a dedicated PUCCH configuration, the table (Rel16.5.0 Table 9.2.1-1 [TS38.213]) is modified to include the number of RBs required per SCS value. In addition to the local restrictions in terms of PSD restrictions and the SCS to be used for initial access, the number of initial cyclic shifts also influences the required number of RBs in the PUCCH resource set. The required number of RBs in the modified table is also based on the PRB offset, such that the number of RBs is reduced for larger PRB offsets. In an alternative embodiment, the UE is pre-configured with only the maximum number of RBs per SCS {120kHz_maxNofRBs, 480kHz_maxNofRBs, 960kHz_maxNofRBs}, and the UE selects the corresponding number of RBs based on the configured SCS. Another additional parameter in the modified table is the PRB mapping type, which is based on the number of PRBs, such that when the number of RBs is large, long sequences are used, while when the number of RBs is small, long sequences or repetitions are used to avoid PAPR increase. Table 1 shows the modified PUCCH resource set prior to PUCCH resource configuration. [Table 1]

[0048] RB mapping type 0 represents a single sequence, while 1 represents repetition.

[0049] In system information block 1 (SIB1), an index of this table, identifying the number of RBs, RB mapping type, etc., is signaled to the UE as part of PUCCH-ConfigCommon. [Table 2]

[0050] As an example, index 3 of pucch-ResourceCommon, along with other PUCCH configuration elements, instructs the UE that for 120 kHz, 8 RBs and long sequences should be used, for 480 kHz, 4 RBs and repetition should be used, and for 960 kHz, 1 RB should be used.

[0051] In another embodiment, because the number of RBs required to satisfy a particular PSD limit varies based on the power class of the UE as well as the UE antenna gain, multiple numbers of RBs are defined in the PUCCH resource configuration table, where these different numbers correspond to different power classes of the UE and / or potential UE antenna gain configurations.

[0052] In some embodiments, the PRB offsets are also indicated as a set for each index in Table 1 and Table 2, where the PRB offset value to be applied can vary depending on the number of RBs, the RB mapping type, or some combination thereof.

[0053] In some embodiments, further indexes may also be added to the table to allow different combinations of number of symbols, number of RBs, and / or RB mapping types for each PUCCH format.

[0054] In some embodiments, an additional RB mapping type may be indicated, e.g., RB mapping type 2, which may apply a combination of a long sequence (covering more than one RB) and a repetition of the long sequence, which may essentially be a combination of RB mapping type 1 and RB mapping type 2. [Table 3]

[0055] In one embodiment, as shown in FIG. 4, the gNB 104 includes in the SIB1 message 404 an index to find a specific location in a previously defined PUCCH resource configuration table. Under the situation where the UE 102 is in an idle state, the UE 102 selects a parameter stored in the previously defined PUCCH resource configuration table based on the index in the SIB1 message 404. The UE 102 sends the selection result in Msg3 410 back to the gNB 104. In Msg4 412, the gNB 104 returns an acknowledgement of the selection result included in Msg3 410 to the UE 102. In PUCCH 414, the UE 102 generates a PUCCH transmission using the selected resource based on the acknowledgement Msg4 412 from the gNB 104.

[0056] In one embodiment, the UE 102 autonomously selects the number of RBs corresponding to the power class and / or antenna gain and reports the selection in Msg3 410. The gNB 104 may indicate the validity of the UE 102 selection in the DCI of Msg4 412, for example by including an indicator for the number of RBs. In general, the gNB 104 indication in Msg4 412 may override the selection included in Msg3 410, and in such case the UE 102 applies the indication in Msg4 412 to the transmission of the corresponding ACK / NACK.

[0057] In another embodiment, the UE 102 may autonomously select the number of RBs and the mapping type during the attachment procedure. The UE 102 in RRC connected mode is instructed by parameters for PUCCH configuration using a UE-specific PUCCH resource configuration RRC message. The gNB 104 associates each PUCCH resource ID with both the number of RBs and the mapping type. In one embodiment, the number of RBs and the corresponding RB mapping type may be determined based on the PSD limit of the region, the available RBs in the BWP, the configured SCS, the number of cyclic shifts per PUCCH resource set, and the number of connected UEs in the cell.

[0058] In another embodiment, the gNB 104 configures the UE 102 with the number of RBs based on the UE transmission power headroom report (PHR) and beamforming gain. There are two values ​​in the PUCCH resource configuration for PUCCH formats 0 / 1 / 4: nrofPRBs, which starts from a single RB up to the maximum number of RBs, and mappType, which has values ​​of 0 and 1, where 0 represents a long sequence for both PUCCH formats 0 / 1 and a long DFT spanning those RBs for PUCCH format 4, while 1 represents a frequency domain repetition of a single RB over the number of configured RBs. Essentially, the repetition factor is equal to the number of PRBs when no explicit indication of the repetition factor is indicated and the sequence length / DFT length is equal to 12. In some embodiments, the repetition factor can be explicitly indicated. In one example, a longer sequence can be used for a larger number of RBs, while repetition can be configured for a smaller number of RBs. [Table 4]

[0059] In another embodiment, two fields may be inserted in the DCI to separately indicate the number of RBs and the mapping type of the corresponding PUCCH resource, which is done in the case of a dedicated PUCCH resource configuration that occurs when the UE 102 is determined to be connected to a gNB 104.

[0060] In a third embodiment, an indication of combined RB mapping type is provided. The UE 102 in RRC connected mode is indicated with the parameters required for multi-RB enhanced PUCCH formats 0 / 1 / 4 using a UE-specific PUCCH resource configuration RRC message. The gNB 104 associates each PUCCH resource identifier (ID) with a number of RBs and a mapping type. In addition to these two parameters, the UE 102 is instructed to combine both mapping options to achieve a certain trade-off between coverage gain and UE multiplexing gain. It has been observed that the long sequence mapping option, where PUCCH formats 0 / 1 are generated with a sequence of length equal to the number of configured RBs, is a better candidate for improving the coverage of PUCCH transmissions because this mapping option provides better maximum isotropic loss (MIL) resistance compared to frequency domain repetition due to its lower PAPR. On the other hand, frequency domain repetition of PUCCH formats 0 / 1 / 4 provides better opportunities for FDM multiplexing of UEs and can achieve more multiplexing gain than the long sequence option. In scenarios where the UE 102 is located at the cell edge, the coverage of the PUCCH transmission becomes a bottleneck for the UE 102 to reach the gNB 104 with sufficient power. Therefore, the long sequence option or long DFT is selected for mapping the PUCCH PRBs, while in scenarios where a large number of UEs 102 are connected to the network, frequency domain repetition can avoid resource starvation of the cell. However, scenarios with medium coverage and medium multiplexing requirements can benefit from a combination of both options. The number of RBs as well as the combination factor indicating the length of the sequence and the number of repetitions to be applied are signaled to the UE 102 using the RRC dedicated PUCCH configuration shown below. [Table 5]

[0061] In one embodiment, the parameter nrofFreqRepetitions signaled in the dedicated PUCCH resource set configuration controls the combination option between long sequence / long DFT and frequency domain repetition for PUCCH resource mapping. The sequence length for generating PUCCH format 0 / 1 or the DFT length for generating PUCCH format 4 is determined by the UE based on SeqL=nrofPRBs / nrofFreqRepetitions as shown in Figure 5. If the number of repetitions is equal to the number of RBs, only the repetition type is used, while if the number of repetitions is 1, only the long sequence or long DFT covering all RBs is used. In an alternative embodiment, the UE is instructed by the number of repetitions and the number of RBs in each repetition, so the number of RBs is a multiplication of both.

[0062] As shown in FIG. 5, a combination of long sequences and frequency domain repetition is presented. Two fields are included in the DCI to indicate the number of RBs and the number of repetitions of the corresponding PUCCH resource. Group 504 indicates when the number of repetitions is equal to 1. Group 506 indicates when the number of repetitions is equal to 2. Group 508 indicates when the number of repetitions is equal to 4. Group 510 indicates when the number of repetitions is equal to the number of RBs, i.e., 8. The UE 102 may be dynamically instructed in the DCI to enable or disable the combination mapping alternative. In such a case, the UE 102 is explicitly indicated by the type of RB mapping. In one embodiment, the mapping type and / or repetition factor for the PUCCH format may be indicated through a PUCCH resource indicator (PRI) field in the DCI. This may be done by including a new column field in the table, where a specific mapping type, number of PRBs, and / or repetition factor may be signaled for each PUCCH resource.

[0063] In some embodiments, another mapping type, namely mapping type 2, is indicated, where a long sequence / long DFT combination (multiple of 12) is used and the long sequence / long DFT is repeated over multiple PRBs. In this case, the number of PRBs, the mapping type, and the repetition factor can be indicated. The number of PRBs indicates the number of PRBs for one repetition, also called the sequence length / DFT length. The mapping type can be 2. The repetition factor indicates the number of times the long sequence / long DFT is repeated. Thus, the total PRB allocation can be determined by the number of PRBs multiplied by the repetition factor. In an alternative embodiment, the number of PRBs indicates the total number of PRBs required to transmit the long sequence / long DFT over multiple repetitions. In this case, the length of the sequence (or the number of PRBs per repetition) can be determined by dividing the number of PRBs by the repetition factor.

[0064] In one embodiment, the measured reference signal received power (RSRP) from SSB / CSI-RS can be used to identify the coverage, which results in the selection of the mapping type, number of resource blocks, repetition factor, sequence length, etc. In a scenario where the UE is located at the cell edge, the coverage of the PUCCH transmission will be a bottleneck for this UE to reach the gNB with sufficient power. Therefore, the long sequence option or long DFT is selected for mapping the PUCCH PRB, while in a scenario where a large number of UEs are connected to the network, frequency domain repetition can avoid resource starvation of the cell. However, scenarios with medium coverage and medium multiplexing requirements can benefit from a combination of both options.

[0065] Referring to FIG. 6, a process 600 implemented by a UE is presented. In block 602, a connection state / status of the UE is determined. If the connection state determination determines that the UE is in a disconnected or idle state, an index is received using SIB1 in block 604. The index identifies a location in a previously defined table associated with a PUCCH configuration parameter. In block 606, a first parameter associated with a number of RBs and a second parameter associated with a mapping type are identified in the table based on the index. If the connection state determination determines that the UE is in a connected state, in block 608, a third parameter indicating the number of RBs and a fourth parameter indicating one or more mapping types are received as part of a dedicated RRC message (dedicated PUCCH resource configuration). In block 610, uplink communication is generated based on the identified first, second, third, or fourth parameters, as appropriate.

[0066] In one embodiment, another method implemented in a UE includes receiving a configuration for transmission of PUCCH, the configuration including an indication of a number of resource blocks, one or more mapping types. The method then receives a PUCCH resource configuration to be used in RRC connected mode and a common PUCCH resource configuration to be used in RRC idle mode / at initial access. The method then selects one of these PUCCH resource configurations depending on the SCS and the measured RSRP.

[0067] In one embodiment, for an idle mode UE, the number of PRBs and mapping type are predefined based on a PUCCH resource configuration table, and an index into the table is indicated to the UE using a common PUCCH RRC configuration in SIB1.

[0068] In one embodiment, parameters of multiple RBs in a PUCCH resource configuration correspond to different SCSs.

[0069] In one embodiment, the RB mapping type parameter in the PUCCH resource configuration table includes three values ​​corresponding to three values ​​of the number of RBs, where when the number of RBs is large, long sequences are used, while when the number of RBs is small, repetition is used.

[0070] In one embodiment, two sets of values, one for each of the three SCSs, are added to the table, with each set representing the number of RBs and corresponding RB mapping for one UE power class category.

[0071] In one embodiment, the number of PRBs and mapping type are signaled to the UE using an RRC dedicated PUCCH resource configuration for RRC connected UEs. Two additional parameters are inserted into the RRC PUCCH resource configuration: nrofPRBs, whose value is between 1 and the maximum number of RBs for the configured SCS, and mappType, whose value is 0 or 1.

[0072] In one embodiment, the UE is instructed to apply a combination of PRB mapping types, where one additional parameter is inserted into the RRC UE dedicated PUCCH resource configuration message indicating the number of repetitions to be performed with the long sequence, where the sequence length for PUCCH generation is the ratio of the number of RBs to the number of repetitions.

[0073] In one embodiment, the UE is instructed in the DCI to enable or disable a combination of PRB mappings, and in such cases the UE is explicitly instructed in the DCI with the mapping type to use for the corresponding PUCCH resource.

[0074] A long sequence of multiple RBs is used, and the sequence is repeated multiple times. For example, if the number of configured RBs is 15 and the number of repetitions is 3, a sequence of length 5 RBs is repeated 3 times in frequency. In Rel16, only one RB is used for PUCCH formats 0 and 1.

[0075] In one embodiment, a method implemented in a UE includes determining a connection status of the UE; in response to determining that the connection status is not connected, selecting one of the first parameters indicating a number of RBs and one of the second parameters indicating a mapping type included in a previously received configuration for transmitting a PUCCH having a predefined table including first and second parameters; in response to determining that the connection status is connected, receiving a dedicated PUCCH resource configuration (RRC message) having a third parameter indicating the number of RBs and a fourth parameter indicating the mapping type; and in response to determining that the connection status is connected, generating a PUCCH transmission in response to the selected first and second parameters or the received third and fourth parameters.

[0076] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes receiving a table index value for a previously received PUCCH configuration included in SIB1, and selecting one of the first parameters and one of the second parameters from the table in response to the received table index value.

[0077] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes determining an SCS associated with a synchronization raster previously identified by the UE, and selecting one of the first parameters and one of the second parameters according to the determined SCS.

[0078] In various embodiments, selecting one of the first parameters and one of the second parameters from the table further includes receiving a measured RSRP in the CSI / RS and selecting one of the first parameters and one of the second parameters responsive to the measured RSRP.

[0079] In one embodiment, the second parameter includes three values ​​corresponding to different values ​​of the number of RBs, and when the number of RBs is greater than a threshold amount, the first sequence is used, and when the number of RBs is less than the threshold amount, the repetition sequence is used.

[0080] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes determining a power class category of the UE and selecting one of the first parameters and one of the second parameters according to the power class category, wherein the table includes two sets of values, one for three different SCSs, each set representing a number of RBs and corresponding RB mapping for one of the UE power class categories.

[0081] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes selecting a number of RBs and a mapping type based on an associated power class and the determined SCS.

[0082] In various embodiments, the method further includes sending the selected first, second, third, or fourth parameter in a message 3 (Msg3).

[0083] In one embodiment, the method further includes receiving an indication of the validity of the number of selected RBs and mapping type in a message 4 (Msg4) having a DCI.

[0084] In some embodiments, the third parameter has a value between 1 and the determined maximum number of RBs for the SCS, and the fourth parameter has a value of 0 or 1.

[0085] In some embodiments, the method further includes applying a combination of mapping types, wherein the dedicated PUCCH resource configuration includes a fifth parameter representing a number of repetitions to be performed with the first sequence, and a length of the first sequence for PUCCH generation is a ratio of the number of RBs to the number of repetitions.

[0086] In various embodiments, the method further includes receiving an indication to enable or disable a combination of mapping types, in which case the UE is explicitly instructed in the DCI with the mapping type to use for the corresponding PUCCH resource.

[0087] In one embodiment, an apparatus comprises a receiver, a transmitter, a processor, and a memory storing code executable by the processor, the code being for: determining a connection status of the apparatus; in response to determining that the connection status is not connected, selecting one of the first parameters indicating a number of RBs and one of the second parameters indicating a mapping type included in a previously received configuration for transmitting a PUCCH having a predefined table including first and second parameters; in response to determining that the connection status is connected, receiving a dedicated PUCCH resource configuration (RRC message) having a third parameter indicating the number of RBs and a fourth parameter indicating the mapping type; and in response to determining that the connection status is connected, generating a PUCCH transmission in response to the selected first and second parameters or the received third and fourth parameters. In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes receiving a table index value for a previously received PUCCH configuration included in SIB1, and selecting one of the first parameters and one of the second parameters from the table in response to the received table index value.

[0088] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes determining a subcarrier spacing (SCS) associated with a synchronization raster previously identified by the device, a power class category of the device, or a combination thereof, and selecting one of the first parameters and one of the second parameters in response to the determined SCS, the determined power class category, or one of the combinations thereof.

[0089] In some embodiments, selecting one of the first parameters and one of the second parameters from the table further includes receiving a measured RSRP in the CSI / RS and selecting one of the first parameters and one of the second parameters responsive to the measured RSRP.

[0090] In one embodiment, a network unit comprises a receiver, a transmitter, a processor, and a memory storing code executable by the processor, the code being for generating an index configured to identify a first parameter indicating a number of RBs and a second parameter indicating a mapping type included in a previously determined configuration for transmitting a PUCCH having a predefined table including the first and second parameters, transmitting the index to a remote unit determined to be in an idle mode, receiving a selection result of the first and second parameters from the remote unit, performing an acknowledgement of the received selection result, and transmitting the acknowledgement to the remote unit.

[0091] The embodiments may be embodied in other specific forms. The embodiments described herein are to be considered in all respects as merely illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0092] 100 Wireless communication system 102 Remote unit (device, user equipment), UE 104 Network Unit (gNB) 200 equipment 202 Processor 204 Memory 206 Input Devices 208 Display 210 Transmitter 212 Receiver 300 equipment 302 Processor 304 Memory 306 Input Devices 308 Display 310 Transmitter 312 Receiver 404 SIB1 Message 410 Msg3 412 Msg4 414 PUCCH 502 Resource Blocks (RB) 504 Group 506 Group 508 Group 510 Group 600 processes

Claims

1. A method performed by a user equipment (UE), comprising: Determining a first set of parameters or a second set of parameters, the first set of parameters and the second set of parameters are based on a connection status of the UE; the first set of parameters indicating a first number of resource blocks and a first format for a physical uplink control channel (PUCCH) transmission; the second set of parameters indicating a second number of resource blocks and a second format for the PUCCH transmission; performing the PUCCH transmission based on the first set of parameters or the second set of parameters; A method comprising:

2. A step of receiving a system information block 1 (SIB1); identifying the first number of resource blocks or the second number of resource blocks based on the received SIB1; The method of claim 1, further comprising: Selecting the first set of parameters or the second set of parameters based on a subcarrier spacing associated with a synchronization raster. The method of claim 1, further comprising: Selecting the first set of parameters or the second set of parameters based on a reference signal received power (RSRP). The method of claim 1, further comprising:

5. The method of claim 1, further comprising: identifying a power class category of the UE; selecting the first set of parameters or the second set of parameters based on the power class category of the UE; The method of claim 1, further comprising:

6. The method of claim 5, further comprising: receiving an instruction to enable or disable a format for the PUCCH transmission, the instruction being received in downlink control information (DCI); The method of claim 1, further comprising:

7. A user equipment (UE), comprising: At least one memory; at least one processor coupled to said at least one memory; and wherein the at least one processor causes the UE to: Determining a first set of parameters or a second set of parameters, the first set of parameters and the second set of parameters are based on a connection status of the UE; the first set of parameters indicating a first number of resource blocks and a first format for a physical uplink control channel (PUCCH) transmission; determining a second set of parameters indicating a second number of resource blocks and a second format for the PUCCH transmission; performing the PUCCH transmission based on the first set of parameters or the second set of parameters; The UE is configured to:

8. The at least one processor, in the UE, receiving a system information block 1 (SIB1); identifying the first number of resource blocks or the second number of resource blocks based on the received SIB1; The UE of claim 7, further configured to:

9. The at least one processor, in the UE, selecting the first set of parameters or the second set of parameters based on a subcarrier spacing associated with a synchronization raster; The UE of claim 7, further configured to:

10. The at least one processor, in the UE, selecting the first set of parameters or the second set of parameters based on a reference signal received power (RSRP); The UE of claim 7, further configured to:

11. The at least one processor, in the UE, Identifying a power class category of the UE; and selecting the first set of parameters or the second set of parameters based on the power class category of the UE; The UE of claim 7, further configured to:

12. The at least one processor, in the UE, receiving an instruction to enable or disable a format for the PUCCH transmission, the instruction being received in downlink control information (DCI); The UE of claim 7, further configured to:

13. A base station, At least one memory; at least one processor coupled to said at least one memory; and wherein the at least one processor is configured to cause the base station to: receiving a physical uplink control channel (PUCCH) transmission from a user equipment (UE) based on the first set of parameters or the second set of parameters; the first set of parameters and the second set of parameters are based on a connection status of the UE; the first set of parameters indicating a first number of resource blocks and a first format for the PUCCH transmission; receiving the second set of parameters indicating a second number of resource blocks and a second format for the PUCCH transmission; A base station configured to:

14. A method performed by a base station, comprising: receiving a physical uplink control channel (PUCCH) transmission from a user equipment (UE) based on the first set of parameters or the second set of parameters; the first set of parameters and the second set of parameters are based on a connection status of the UE; the first set of parameters indicating a first number of resource blocks and a first format for the PUCCH transmission; the second set of parameters indicating a second number of resource blocks and a second format for the PUCCH transmission. A method comprising:

Images