Method, device and medium for sequence design and resource allocation of new air interface physical uplink control channel

Abstract

The present disclosure relates to sequence design and resource allocation for a new radio physical uplink control channel (PUCCH). A user equipment (UE) may include processing circuitry configured to decode physical uplink control channel (PUCCH) configuration information received from a next-generation Node B (gNB). The configuration information includes a cell-specific base sequence hopping pattern. A PUCCH base sequence is selected from a plurality of available PUCCH base sequences based on the cell-specific base sequence hopping pattern and UCI information. A cyclic shift is applied to the PUCCH base sequence to generate a cyclically shifted PUCCH sequence. The cyclically shifted PUCCH sequence is encoded for transmission to the gNB using a PUCCH physical resource. The cyclically shifted PUCCH sequence carries UCI and is code division multiplexed (CDM) with at least one other cyclically shifted PUCCH sequence within the PUCCH physical resource.

Description

[0001] Division Statement

[0002] This application is a divisional application of the invention patent application with PCT international application number PCT / US2018 / 044563, international application date July 31, 2018, application number 201880060519.5 entering the Chinese national phase, and invention name “Sequence design and resource allocation for new air interface physical uplink control channel”.

[0003] Priority claim

[0004] This application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62 / 540,424, filed on August 2, 2017, entitled “ON THE SEQUENCE DESIGN OF NR PUCCH WITH SHORT AND LONG DURATIONS.”

[0005] This application also claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62 / 587,661, filed on November 17, 2017, entitled “RESOURCE ALLOCATION AND INDICATION FOR UPLINK PHYSICAL CONTROL CHANNEL.”

[0006] Each of the above-identified provisional patent applications is incorporated herein by reference in its entirety. Technical Field

[0007] Aspects relate to wireless communications. Some aspects relate to wireless networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks, wherein fifth-generation (5G) networks include 5G New Radio (NR) (or 5G-NR) networks and 5G-LTE networks. Other aspects relate to sequence design for NR physical uplink control channels (PUCCHs) with short and long durations. Additional aspects relate to resource allocation and indication for PUCCHs. Background Art

[0008] Mobile communications have evolved significantly from early voice systems to today's highly complex, integrated communications platforms. The use of 3GPP LTE systems has increased with the proliferation of different types of devices communicating with a variety of network devices. The penetration of mobile devices (user equipment, or UE) in modern society continues to drive demand for a variety of connected devices in many different environments. Fifth-generation (5G) wireless systems are about to be launched, expected to enable even higher speeds, connectivity, and availability. Next-generation 5G networks (or NR networks) are expected to improve throughput, coverage, and robustness, and reduce latency as well as operational and capital expenditures. 5G-NR networks will continue to develop based on 3GPP LTE-Advanced and other potential new air interface access technologies (RATs), enriching people's lives with seamless wireless connectivity solutions and delivering fast, rich content and services. As current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies can benefit from their high bandwidth.

[0009] Potential LTE operations in unlicensed spectrum include (and are not limited to) LTE operation in unlicensed spectrum via Dual Connectivity (DC) or LAA and standalone LTE systems based on DC, whereby LTE-based technologies operate solely in unlicensed spectrum without an "anchor" in the licensed spectrum, an approach known as MulteFire. MulteFire combines the performance advantages of LTE technology with the simplicity of Wi-Fi-like deployments.

[0010] In future releases and 5G systems, LTE systems are expected to have further enhanced operation in both licensed and unlicensed spectrum. Such enhanced operation may include techniques to address sequence design for short-duration and long-duration PUCCHs, as well as resource allocation and indication for PUCCHs. Summary of the Invention

[0011] According to some embodiments of the present disclosure, a method for wireless communication is provided, comprising: receiving configuration information from a base station, wherein the configuration information indicates a physical uplink control channel (PUCCH) configuration, wherein the PUCCH configuration comprises a plurality of physical resource blocks (PRBs) and 12 cyclic shifts per PRB, wherein a code division multiplexing capacity using cyclic shifts within a PRB in the plurality of PRBs is 3; determining a PUCCH resource, wherein the PUCCH resource comprises a PRB and a cyclic shift, wherein the PUCCH resource depends on whether positive or negative hybrid automatic repeat request (HARQ) confirmation information is to be transmitted and whether positive or negative scheduling request (SR) information is to be transmitted; applying the cyclic shift to a PUCCH base sequence to generate a cyclic shift PUCCH sequence; and encoding the cyclic shift PUCCH sequence using the PUCCH resource for transmission to the base station.

[0012] According to some embodiments of the present disclosure, a device is provided, including a processor, wherein the processor is configured to enable a user equipment (UE) to execute the above method according to some embodiments of the present disclosure.

[0013] According to some embodiments of the present disclosure, a computer-readable storage medium is provided, which stores instructions, wherein when the instructions are executed by one or more processors, the user equipment UE performs the above method according to some embodiments of the present disclosure.

[0014] According to some embodiments of the present disclosure, another method for wireless communication is provided, comprising: transmitting configuration information to a user equipment (UE), wherein the configuration information indicates a physical uplink control channel (PUCCH) configuration, wherein the PUCCH configuration comprises a plurality of physical resource blocks (PRBs) and 12 cyclic shifts per PRB, wherein a code division multiplexing capacity using cyclic shifts within a PRB among the plurality of PRBs is 3; and receiving a PUCCH transmission comprising PUCCH information from the UE using a PUCCH resource comprising the cyclic shift and the PRB, wherein the PUCCH resource depends on whether positive or negative hybrid automatic repeat request (HARQ) confirmation information is to be transmitted and whether positive or negative scheduling request (SR) information is to be transmitted, wherein the cyclic shift is applied to a PUCCH base sequence to generate a cyclic shifted PUCCH sequence for the PUCCH transmission.

[0015] According to some embodiments of the present disclosure, a device is provided, including a processor, where the processor is configured to cause a base station to execute the above-mentioned another method according to some embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In the accompanying drawings, which are not necessarily drawn to scale, like numbers may describe similar components in different views. Like numbers with different letter suffixes may represent different instances of similar components. The accompanying drawings generally illustrate various aspects described in this document by way of example and not limitation.

[0017] Figure 1A An architecture of a network according to some aspects is shown.

[0018] Figure 1B is a simplified diagram of an overall next generation (NG) system architecture according to some aspects.

[0019] Figure 1C An exemplary MulteFire Neutral Host Network (NUN) 5G architecture is shown in accordance with some aspects.

[0020] Figure 1DIllustrated is a functional split between the Next Generation Radio Access Network (NG-RAN) and the 5G Core Network (5GC) according to some aspects.

[0021] Figure 1E and Figure 1F A non-roaming 5G system architecture is shown in accordance with some aspects.

[0022] Figure 1G An exemplary Cellular Internet of Things (CIoT) network architecture is shown in accordance with some aspects.

[0023] Figure 1H An example service capability exposure function (SCEF) according to some aspects is shown.

[0024] Figure 1I An example roaming architecture for a SCEF is shown in accordance with some aspects.

[0025] Figure 2 Illustrative components of device 200 are shown in accordance with some aspects.

[0026] Figure 3 An exemplary interface of a baseband circuit according to some aspects is shown.

[0027] Figure 4 is a diagram of a control plane protocol stack according to some aspects.

[0028] Figure 5 is a diagram of a user plane protocol stack according to some aspects.

[0029] Figure 6 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary aspects.

[0030] Figure 7 is an illustration of an initial access procedure including PRACH preamble retransmission in accordance with some aspects.

[0031] Figure 8 is a diagram illustrating PRACH resource configuration according to some aspects.

[0032] Figure 9 is an illustration of NR PUCCH and uplink data slots with short and long durations in accordance with some aspects.

[0033] Figure 10 is an illustration of code division multiplexing (CDM) of short PUCCH and long PUCCH, where the short PUCCH is allocated in the last symbol of a slot, in accordance with some aspects.

[0034] Figure 11 is an illustration of code division multiplexing of short PUCCH and long PUCCH, where the short PUCCH is allocated near the middle of a slot, in accordance with some aspects.

[0035] Figure 12 is an illustration of cyclic shift hopping for a short PUCCH having a 2-symbol duration in accordance with some aspects.

[0036] Figure 13A and Figure 13B is an illustration of different combinations of frequency-domain and code-domain resources for a short PUCCH with 1-symbol duration in accordance with some aspects.

[0037] Figure 14 is an illustration of uplink control channels including a long PUCCH and a short PPUCCH according to some aspects.

[0038] Figure 15 is an illustration of resource configuration for a physical uplink control channel in accordance with some aspects.

[0039] Figure 16 is an illustration of resource allocation and resource transfer for a physical uplink control channel in accordance with some aspects.

[0040] Figure 17 Generally illustrated are flowcharts of example functions that may be performed in conjunction with PUCCH communications in a wireless architecture in accordance with certain aspects.

[0041] Figure 18 Generally illustrated are flowcharts of example functions that may be performed in conjunction with resource allocation and indication for PUCCH in a wireless architecture in accordance with certain aspects.

[0042] Figure 19 A block diagram of a communication device, such as an evolved Node B (eNB), a next-generation Node B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), is shown according to some aspects. DETAILED DESCRIPTION

[0043] The following description and accompanying drawings illustrate the various aspects sufficiently to enable those skilled in the art to practice the aspects. Other aspects may incorporate structural, logical, electrical, process, and other variations. Portions and features of some aspects may be included in, or substituted for, portions and features of other aspects. Aspects recited in the claims encompass all available equivalents of those claims.

[0044] Any radio link described herein may operate in accordance with any one or more of the following exemplary radio communication technologies and / or standards, including but not limited to: Global System for Mobile Communications (GSM) radio communication technology, General Packet Radio Service (GPRS) radio communication technology, Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and / or Third Generation Partnership Project (3GPP) radio communication technologies, such as Universal Mobile Telecommunications System (UMTS), Freedom of Movement Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE-A), and / or 3GPP LTE-500. Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed ​​Circuit Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Enhanced High-Speed ​​Packet Access (HSPA+), Universal Mobile Telecommunications System - Time Division Duplex (UMTS-TDD), Time Division Duplex - Code Division Multiple Access (TD-CDMA), Time Division - Synchronous Code Division Multiple Access (TD-CDMA), 3GPP Rel.8 (Pre-4G), 3GPP Rel.9, 3GPP Rel.10, 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel.12 (3rd Generation Partnership Project Release 12), 3GPP Rel.13 (3rd Generation Partnership Project Release 13), 3GPP Rel.14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel.16 (3rd Generation Partnership Project Release 16), 3GPP Rel.17 (3rd Generation Partnership Project Release 17), 3GPP Rel.18 (3rd Generation Partnership Project Release 18), 3GPP 5G or 5G-NR, 3GPP LTEExtra, LTE-Advanced Pro, LTE Licensed Assisted Access (LAA), MulteFire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Plus (Fourth Generation) (LTE Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (Third Generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Dedicated (EV-DO), Advanced Mobile Phone System (1G)), Total Access Communications System / Extended Total Access Communications System (TACS / ETACS), Digital AMPS (2G) (D-AMPS (2G)), Push to Talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Phone System (AMTS), OLT (Offentlig LandmobilTelefoni (Norwegian for public land mobile), MTD (Swedish abbreviation for Mobile Telephone System D, or Mobile Telephone System D), Public Automatic Land Mobile (Autotel / PALM), ARP (Finnish for Autoradiopuhelin, "car radio telephone"), NMT (Nordic mobile), High Capacity Version NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA) (also known as the 3GPP Universal Access Network or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, millimeter wave general standard (wireless systems operating in the 10-300 GHz band and above, such as WiGig IEEE 802.1lad, IEEE 802.1lay, etc.), technologies operating above 300 GHz and in the THz band (based on 3GPP / LTE, or IEEE 802.1lp and others), vehicle-to-vehicle (V2V) communication technology, vehicle-to-everything (V2X) communication technology, vehicle-to-infrastructure (V2I) communication technology, and infrastructure-to-vehicle (V2I) communication technology, 3GPP cellular V2X, DSRC (dedicated short-range communication) communication systems (such as intelligent transportation systems and others).

[0045] LTE and LTE-Advanced are wireless communication standards for high-speed data transmission for user equipment (UE), such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique whereby multiple carrier signals operating at different frequencies can be used to carry communications for a single UE, thereby increasing the bandwidth available to a single device. In some aspects, carrier aggregation can be used when one or more component carriers operate at unlicensed frequencies.

[0046] There is growing interest in operating LTE systems in unlicensed spectrum. Consequently, a key enhancement to LTE in 3GPP Release 13 is the ability to operate in unlicensed spectrum via Licensed Assisted Access (LAA), which leverages the flexible carrier aggregation (CA) framework introduced with LTE-Advanced to expand system bandwidth. Rel-13 LAA systems focus on downlink operation in unlicensed spectrum via CA, while Rel-14 enhanced LAA (eLAA) systems focus on uplink operation in unlicensed spectrum via CA.

[0047] The aspects described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) at 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and other frequencies, and Spectrum Access System (SAS) at 3.55-3.7 GHz and other frequencies). Applicable exemplary spectrum bands include IMT (International Mobile Telecommunications) spectrum (including 450-470 MHz, 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2500-2690 MHz, 698-790 MHz, 610-790 MHz, 3400-3600 MHz, etc.), IMT-advanced spectrum, IMT-2020 spectrum (expected to include, for example, 3600-3800 MHz, 3.5 GHz band, 700 MHz band, and bands in the range of 24.25-86 GHz), and spectrum covered by the Federal Communications Commission's "Spectrum Frontier" 5G plan (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz , 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHz and 92-94 GHz, etc.), ITS (Intelligent Transportation Systems) bands in the 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz bands, as well as bands currently allocated to WiGig (such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz), WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz); the 70.2-71 GHz band; any band between 65.88 GHz and 71 GHz; bands currently allocated to automotive radar applications, such as 76-81 GHz; and future bands including 94-300 GHz and above. Furthermore, the solution can be used on a secondary basis in frequency bands such as TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being particularly useful. In addition to cellular applications, specific applications targeting vertical markets such as PMSE (Programming and Special Events), medical, health, surgery, automotive, low latency, drones, etc. can be addressed.

[0048] The aspects described herein may also be applied to different single carrier or OFDM families (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.) by assigning OFDM carrier data bit vectors to corresponding symbol resources, and in particular to 3GPP NR (New Radio).

[0049] Figure 1A 1. The architecture of a network according to some aspects is shown. Network 140A is shown as including user equipment (UE) 101 and UE 102. UE 101 and UE 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless phone, a drone, or any other computing device that includes a wired and / or wireless communication interface.

[0050] In some aspects, either UE 101 or UE 102 may comprise an Internet of Things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, either UE 101 or UE 102 may comprise a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, a sensor network, or an IoT network. The M2M or MTC data exchange may be machine-initiated data exchange. The IoT network may include interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) utilizing short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0051] In some aspects, an NB-IoT device can be configured to operate in a single physical resource block (PRB) and can be instructed to retune to two different PRBs within the system bandwidth. In some aspects, an eNB-IoT UE can be configured to acquire system information in one PRB and then retune to a different PRB to receive or transmit data.

[0052] In some aspects, either UE 101 and UE 102 may comprise an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0053] UE 101 and UE 102 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 110. RAN 110 may be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NGRAN), or some other type of RAN. UE 101 and UE 102 utilize connection 103 and connection 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces to achieve communicative coupling and may be consistent with cellular communication protocols, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a PTT-over-cellular protocol (POC), a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, or the like.

[0054] In some aspects, network 140A may include core network (CN) 120. Figure 1B 、 Figure 1C 、 Figure 1D 、 Figure 1E 、 Figure 1F and Figure 1G Various aspects of NG RAN and NG Core are discussed.

[0055] In one aspect, the UE 101 and the UE 102 may also directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0056] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection such as, for example, a connection compliant with any IEEE 802.11 protocol, according to which AP 106 may include Wi-Fi. In this example, AP 106 is shown connected to the Internet and not to the core network of the wireless system (described in further detail below).

[0057] The RAN 110 may include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may include terrestrial sites (e.g., terrestrial access points) or satellite sites that cover a geographic area (e.g., a cell). In some aspects, communication nodes 111 and 112 may be transmission / reception points (TRPs). In the case where communication nodes 111 and 112 are Node Bs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cells of the Node Bs. The RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN node 112) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0058] Either RAN node 111 or RAN node 112 may terminate the air interface protocol and may be the first point of contact for UE 101 or UE 102. In some aspects, either RAN node 111 or RAN node 112 may perform various logical functions of the RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling and mobility management. In one example, either node 111 or node 112 may be a next-generation Node B (gNB), an evolved Node B (eNB), or another type of RAN node.

[0059] According to some aspects, UE 101 and UE 102 can be configured to communicate with each other using orthogonal frequency division multiplexing (OFDM) communication signals, or to communicate with either RAN node 111 or RAN node 112 via multi-carrier communication channels based on multiple communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe for sidelink communication), although such aspects are not required. OFDM signals can include multiple orthogonal subcarriers.

[0060] In some aspects, a downlink resource grid can be used for downlink transmissions from either RAN node 111 or RAN node 112 to UE 101 or UE 102, while similar techniques can be used for uplink transmissions. This grid can be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which represents the physical resources in the downlink per time slot. This time-frequency plane representation can be used in OFDM systems, making them suitable for radio resource allocation. Each column and row of the resource grid can correspond to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain can correspond to a time slot in a radio frame. The smallest time-frequency unit in the resource grid can be represented as a resource element. Each resource grid can include multiple resource blocks, which describe the mapping of specific physical channels to resource elements. Each resource block can include a collection of resource elements; in the frequency domain, this can represent, in some aspects, the minimum amount of resources currently available for allocation. There can be multiple different physical downlink channels transmitted using such resource blocks.

[0061] The physical downlink shared channel (PDSCH) can carry user data and higher layer signaling to UE 101 and UE 102. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocation related to the PDSCH channel. It can also inform UE 101 and UE 102 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Generally, downlink scheduling (allocation of control and shared channel resource blocks to UE 102 within a cell) can be performed at either RAN node 111 or RAN node 112 based on channel quality information fed back from either UE 101 or UE 102. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of UE 101 and UE 102.

[0062] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8) can exist in LTE.

[0063] Some aspects may use the concept of resource allocation for control channel information, where the concept of resource allocation is an extension of the above concept. For example, some aspects may utilize an enhanced physical downlink control channel (EPDCCH), which uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as enhanced resource element groups (EREGs). According to some arrangements, ECCEs may have other numbers of EREGs.

[0064] RAN 110 is shown as being communicatively coupled to a core network (CN) 120 via an SI interface 113. In some aspects, CN 120 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN (e.g., as described with reference to FIG). Figure 1B-1I In this regard, the S1 interface 113 is divided into two parts: an S1-U interface 114, which carries communication data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122; and an S1 mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0065] In this regard, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 can be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 can include a database for network users, including subscription-related information to support network entities in handling communication sessions. Depending on the number of mobile subscribers, the capacity of the devices, the organization of the network, etc., CN 120 may include one or more HSSs 124. For example, HSS 124 can provide support for routing / roaming authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0066] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be the local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0067] The P-GW 123 may terminate the SGi interface for the PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also transmit data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally speaking, the application server 184 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data services, etc.). In this regard, the P-GW 123 is shown as being communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and UE 102 via the CN 120.

[0068] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In non-roaming scenarios, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic breakout, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123. The application server 184 may signal the PCRF 126 to indicate the new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 126 may configure the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Communication Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 184 .

[0069] In one example, either node 111 or node 112 may be configured to transmit antenna panel selection and receive (Rx) beam selection to UE 101, UE 102 (e.g., dynamically), which may be used by the UE for data reception on a physical downlink shared channel (PDSCH) and for channel state information reference signal (CSI-RS) measurements and channel state information (CSI) calculations.

[0070] In one example, either node 111 or node 112 may be configured to transmit antenna panel selections and transmit (Tx) beam selections to UE 101, UE 102 (e.g., dynamically), which may be used by the UE for data transmission on a physical uplink shared channel (PUSCH) and for sounding reference signal (SRS) transmission.

[0071] In some aspects, the communication network 140A can be an IoT network. One of the current enablers of IoT is narrowband IoT (NB-IoT). NB-IoT has goals such as coverage extension, reduced UE complexity, long battery life, and backward compatibility with LTE networks. In addition, NB-IoT is designed to provide deployment flexibility, allowing operators to use a small portion of their existing available spectrum to introduce NB-IoT and operate in one of three modes: (a) standalone deployment (the network operates in rebuilt GSM spectrum); (b) in-band deployment (the network operates within LTE channels); and (c) guard band deployment (the network operates within the guard band of traditional LTE channels). In some aspects, such as using further enhanced NB-IoT (FeNB-IoT), support for NB-IoT in small cells can be provided (e.g., in microcell, picocell, or femtocell deployments). One of the challenges faced by NB-IoT systems in supporting small cells is UL / DL link imbalance, where for small cells, the base station has lower available power than the macrocell, and therefore DL coverage may be affected and / or reduced. Furthermore, if reuse is used for UL transmissions, some NB-IoT UEs may be configured to transmit at maximum power, which may lead to significant inter-cell interference in dense small cell deployments.

[0072] In some aspects, UE 101 may receive configuration information 190A via, for example, higher layer signaling or other types of signaling. Configuration information 190A may include physical uplink control channel (PUCCH) related information as disclosed herein below. For example, configuration information 190A may include PUCCH related information transmitted via L1 / L2 signaling or higher layer signaling (via NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling). Examples of configuration information 190A include a candidate set of PUCCH resources, a PUCCH resource indication (e.g., as received via Downlink Control Information (DCI) or other types of PDCCH information), a cyclic shift hopping pattern, a PUCCH sequence hopping pattern, etc. In response to the configuration information, UE 101 may transmit PUCCH information 192A back to gNB 111, as described herein below.

[0073] Figure 1Bis a simplified diagram of a next generation (NG) system architecture 140B according to some aspects. Figure 1B , the NG system architecture 140B includes the RAN 110 and the 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs 128 and NG-eNBs 130. The gNBs 128 and NG-eNBs 130 may be communicatively coupled to the UE 102 via, for example, an N1 interface.

[0074] The core network 120 (e.g., a 5G core network or 5GC) may include an access and mobility management function (AMF) 132 and / or a user plane function (UPF) 134. The AMF 132 and the UPF 134 may be communicatively coupled to the gNB 128 and the NG-eNB 130 via an NG interface. More specifically, in some aspects, the gNB 128 and the NG-eNB 130 may be connected to the AMF 132 via an NG-C interface and to the UPF 134 via an NG-U interface. The gNB 128 and the NG-eNB 130 may be coupled to each other via an Xn interface.

[0075] In some aspects, gNB 128 may comprise a node that provides New Radio (NR) user plane and control plane protocol terminations to UEs and is connected to 5GC 120 via an NG interface. In some aspects, NG-eNB 130 may comprise a node that provides Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to UEs and is connected to 5GC 120 via an NG interface.

[0076] In some aspects, each of gNB 128 and NG-eNB 130 may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc.

[0077] Figure 1C An exemplary MulteFire Neutral Host Network (NUN) 5G architecture 140C is shown in accordance with some aspects. Figure 1C , the MulteFire 5G architecture 140C may include a UE 102, an NG-RAN 110, and a core network 120. The NG-RAN 110 may be a MulteFire 5G Neutral Host Network (NHN), and the core network 120 may be a MulteFire 5G Neutral Host Network (NHN).

[0078] In some aspects, MF NHN 120 may include a neutral host AMF (NH AMF) 132, a NH SMF 136, a NH UPF 134, and a local AAA proxy 151C. AAA proxy 151C may provide connectivity to a 3GPP AAA server 155C and a participating service provider AAA (PSP AAA) server 153C. NH-UPF 134 may provide connectivity to a data network 157C.

[0079] The MF NG-RAN 120 may provide similar functionality to the NG-RAN operating under the 3GPP specifications. The NH-AMF 132 may be configured to provide similar functionality to the AMF in the 3GPP 5G core network (e.g., as described in reference to FIG. Figure 1D NH-SMF 136 may be configured to provide functionality similar to that of the SMF in the 3GPP 5G core network (e.g., as described in reference Figure 1D The NH-UPF 134 may be configured to provide similar functionality to that of the UPF in the 3GPP 5G core network (e.g., as described in reference Figure 1D described above).

[0080] Figure 1D The functional division between NG-RAN and 5G Core (5GC) according to some aspects is shown. Figure 1D , which shows a more detailed diagram of the functions that may be performed by the gNB 128 and NG-eNB 130 within the NG-RAN 110, and the AMF 132, UPF 134, and SMF 136 in the 5GC 120. In some aspects, the 5GC 120 may provide access to the Internet 138 to one or more devices via the NG-RAN 110.

[0081] In some aspects, the gNB 128 and NG-eNB 130 may be configured to host the following functions: functions for radio resource management (e.g., inter-cell radio resource management 129A, radio bearer control 129B, connection mobility control 129C, radio admission control 129D, dynamic resource allocation (scheduling) 129F for UEs in uplink and downlink); IP header compression, encryption, and integrity protection of data; selection of an AMF at the UE attachment when the route to the AMF cannot be determined based on information provided by the UE; routing of user plane data to one or more UPFs; routing of control plane information to AMF; connection setup and release; scheduling and transmission of paging messages (originating from AMF); scheduling and transmission of system broadcast information (originating from AMF or operation and maintenance); measurement and measurement report configuration for mobility and scheduling 129E; transport layer packet marking in the uplink; session management; network slicing support; QoS flow management and mapping to data radio bearers; support for UEs in RRC_INACTIVE state; distribution function of non-access stratum (NAS) messages; radio access network sharing; dual connectivity; and tight interworking between NR and E-UTRA, etc.

[0082] In some aspects, the AMF 132 may be configured to host functions such as: NAS signaling termination; NAS signaling security 133A; access stratum (AS) security control; inter-core network (CN) node signaling for mobility between 3GPP access networks; idle state / mode mobility handling 133B, including mobile device, such as UE reachability (e.g., control and execution of paging retransmissions); registration area management; intra-system and inter-system mobility support; access authentication; access authorization, including checking roaming rights; mobility management control (subscription and policy); network slicing support; and / or SMF selection, among other functions.

[0083] The UPF 134 may be configured to host functionality such as: mobility anchor 135A (e.g., an anchor point for intra-RAT / inter-RAT mobility); packet data unit (PDU) processing 135B (e.g., an external PDU session point for interconnection with a data network); packet routing and forwarding; packet inspection and user plane portions of policy rule enforcement; traffic usage reporting; an uplink classifier to support routing of communication flows to the data network; a branching point to support multi-homed PDU sessions; QoS processing for the user plane, such as packet filtering, gating, UL / DL rate enforcement; uplink communication verification (SDF to QoS flow mapping); and / or downlink packet buffering and downlink data notification triggering.

[0084] The session management function (SMF) 136 may be configured to host functions such as: session management; UE IP address allocation and management 137A; selection and control of user plane functions (UPFs); PDU session control 137B, including configuring traffic steering at the UPF 134 to route traffic to the correct destination; control portions of policy enforcement and QoS; and / or downlink data notification, among other functions.

[0085] Figure 1E and Figure 1F A non-roaming 5G system architecture is shown according to some aspects. Figure 1E , which illustrates a 5G system architecture 140E in a reference point representation. More specifically, UE 102 can communicate with RAN 110 and one or more other 5G core (5GC) network entities. 5G system architecture 140E includes multiple network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM) / home subscriber server (HSS) 146. UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, internet access, or third-party services. The AMF can be used to manage access control and mobility and can also include network slice selection functionality. The SMF can be configured to set up and manage various sessions based on network policy. The UPF can be deployed in one or more configurations depending on the desired service type. The PCF can be configured to provide a policy framework using network slicing mobility management and roaming (similar to the PCRF in 4G communication systems). The UDM can be configured to store subscriber profiles and data (similar to the HSS in 4G communication systems).

[0086] In some aspects, the 5G system architecture 140E includes an IP multimedia subsystem (IMS) 168E and multiple IP multimedia core network subsystem entities, such as a call session control function (CSCF). More specifically, the IMS 168E includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162E, a serving CSCF (S-CSCF) 164E, an emergency CSCF (E-CSCF) ( Figure 1E166E. In some aspects, the I-CSCF 166E may be connected to another IP multimedia network 170E, such as an IMS operated by a different network operator.

[0087] In some aspects, the UDM / HSS 146 may be coupled to an application server 160E, which may include a telephony application server (TAS) or another application server (AS). The AS 160E may be coupled to the IMS 168E via the S-CSCF 164E and / or the I-CSCF 166E.

[0088] In some aspects, the 5G system architecture 140E may employ one or more techniques described herein to employ a unified access restriction mechanism that may be applicable to all RRC states of the UE 102, such as RRC_IDLE, RRC_CONNECTED, and RRC_IN ACTIVE states.

[0089] In some aspects, the 5G system architecture 140E can be configured to use the 5G access control mechanism techniques described herein based on access categories, which can be categorized by a minimum default set of access categories that are common across all networks. This functionality can allow public land mobile networks (PLMNs), such as visited PLMNs (VPLMNs), to protect the network from different types of registration attempts, enable acceptable services for roaming subscribers, and enable VPLMNs to control access attempts intended to receive certain basic services. It also provides more options and flexibility for individual operators by providing a set of access categories that can be configured and used in an operator-specific manner.

[0090] refer to Figure 1F , which shows a 5G system architecture 140F and a service-based representation. The system architecture 140F may be substantially similar to (or identical to) the system architecture 140E. Figure 1E In addition to the network entities shown in FIG, the system architecture 140F may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.

[0091] In some aspects, the 5G system architecture may be service-based, and the interactions between network functions may be handled by corresponding point-to-point reference points Ni (e.g., Figure 1E As shown in the figure) or is represented as a service-based interface (as shown in Figure 1F).

[0092] Reference point representation shows that there can be interaction between corresponding NF services. For example, Figure 1E 132), N10 (between UDM 146 and SMF 136), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132), N13 (between SMF 136 and PCF 148), N14 (between UDM 146 and SMF 136), N15 (between PCF 148 and AF 150), N16 (between UPF 134 and DN 152), N17 (between SMF 136 and PCF 148), N18 (between UDM 146 and AMF 132), N19 (between both UPFs 134), N20 (between UDM 146 and SMF 136), N21 (between RAN 110 and UPF 134), N22 (between SMF 136 and UPF 134), N23 (between AUSF 144 and AMF 132), N24 (between PCF 148 and AF 150), N25 (between PCF 148 and AF 150), N26 (between SMF 136 and PCF 148), N27 (between SMF 136 and PCF 148), N28 (between UDM 146 and AMF 132), N29 (between UDM 146 and SMF 136), N30 (between AMF 132 and SMF 136), 146), N14 (between two AMFs 132), N15 (if it is a non-roaming scenario, between PCF 148 and AMF 132; if it is a roaming scenario, between PCF 148 and the visited network and AMF132), N16 (between two SMFs; Figure 1E (not shown) and N22 (between AMF 132 and NSSF 142). Figure 1E Other reference points not shown are indicated.

[0093] In some aspects, such as Figure 1FAs shown, a service-based representation may be used to represent network functions within a control plane that enables other authorized network functions to access their services. In this regard, the 5G system architecture 140F may include the following service-based interfaces: Namf 158H (a service-based interface shown by AMF 132), Nsmf 158I (a service-based interface shown by SMF 136), Nnef 158B (a service-based interface shown by NEF 154), Npcf 158D (a service-based interface shown by PCF 148), Nudm 158E (a service-based interface shown by UDM 146), Naf 158F (a service-based interface shown by AF 150), Nnrf 158C (a service-based interface shown by NRF 156), Nnssf 158A (a service-based interface shown by NSSF 142), and Nausf 158G (a service-based interface shown by AUSF 144). You can also use Figure 1F Other service-based interfaces not shown (e.g., Nudr, N5g-eir, and Nudsf).

[0094] Figure 1G An exemplary CIoT network architecture according to some aspects is shown. Figure 1G , the CIoT architecture 140G may include a UE 102 and a RAN 110 coupled to multiple core network entities. In some aspects, the UE 102 may be a machine type communication (MTC) UE. The CIoT network architecture 140G may also include a mobile service switching center (MSC) 160, an MME 121, a serving GPRS support node (SGSN) 162, an S-GW 122, an IP short message gateway (IP-SM-GW) 164, a short message service center (SMS-SC) / gateway mobile service center (GMSC) interworking MSC (IWMSC) 166, an MTC interworking function (MTC-IWF) 170, a service capability exposure function (SCEF) 172, a gateway GPRS support node (GGSN) / packet GW (P-GW) 174, a charging data function (CDF) / charging gateway function (CGF) 176, a home subscriber server (HSS) / home location register (ULR) 177, a short message entity (SME) 168, an MTC authentication, authorization and accounting (MTC AAA) server 178, a service capability server (SCS) 180, and an application server (AS) 182 and an application server (AS) 184.

[0095] In some aspects, SCEF 172 can be configured to securely expose services and capabilities provided by various 3GPP network interfaces. SCEF 172 can also provide ways to discover the exposed services and capabilities, and access network capabilities through various network application programming interfaces (e.g., API interfaces facing SCS 180).

[0096] Figure 1G Various reference points between different servers, functions or communication nodes of the CIoT network architecture 140G are also shown. Some exemplary reference points related to the MTC-TWF 170 and SCEF 172 include: Tsms (reference point used by entities outside the 3GPP network to communicate with the UE, which is used for MTC via SMS), Tsp (reference point used by the SCS to communicate with the MTC-IWF related control plane signaling), T4 (reference point used between the MTC-IWF 170 and the SMS-SC 166 in the HPLMN), T6a (reference point used between the SCEF 172 and the serving MME 121), T6b (reference point used between the SCEF 172 and the serving SGSN 162), T8 (reference point used between the SCEF 172 and the SCS / AS 180 / 182), S6m (reference point used by the MTC-IWF 170 to query the HSS / HLR 177), S6n (reference point used by the MTC-AAA server 178 to query the HSS / HLR 177), and S6t (reference point used between the SCEF 172 and the SCS / AS 180 / 182). Reference point used between 172 and HSS / HLR 177).

[0097] In some aspects, the CIoT UE 102 can be configured to communicate with one or more entities within the CIoT architecture 140G via the RAN 110 according to a non-access stratum (NAS) protocol and using one or more reference points (such as a narrowband air interface), for example based on one or more communication technologies (such as orthogonal frequency division multiplexing (OFDM) technology). As used herein, the term "CIoT UE" refers to a UE that is capable of CIoT optimization and can be used as part of a CIoT communication architecture.

[0098] In some aspects, the NAS protocol may support a set of NAS messages for communication between the CIoT UE 102 and the Evolved Packet System (EPS) Mobility Management Entity (MME) 121 and the SGSN 162.

[0099] In some aspects, the CIoT network architecture 140F may include a packet data network, a carrier network, or a cloud service network, having, for example, a service capability server (SCS) 180, an application server (AS) 182, or one or more other external servers or network components.

[0100] The RAN 110 may be coupled to the HS S / HLR server 177 and the AAA server 178 using one or more reference points, including, for example, an air interface based on the S6a reference point, and may be configured to authenticate / authorize the CIoT UE 102 to access the CIoT network. The RAN 110 may be coupled to the CIoT network architecture 140G using one or more other reference points, including, for example, an air interface corresponding to the SGi / Gi interface for 3GPP access. The RAN 110 may be coupled to the SCEF 172 using, for example, an air interface based on the T6a / T6b reference point for service capability exposure. In some aspects, the SCEF 172 may act as an API GW for third-party application servers such as the AS 182. The SCEF 172 may be coupled to the HS S / HLR 177 and the MTC AAA 178 server using the S6t reference point, and may further expose application programming interfaces to network capabilities.

[0101] In some examples, one or more of the CIoT devices disclosed herein, such as CIoT UE 102, CIoTRAN 110, etc., may include one or more other non-CIoT devices, or include non-CIoT devices that function as CIoT devices or have CIoT device functionality. For example, CIoT UE 102 may include a smartphone, a tablet, or include one or more other electronic devices that function as CIoT devices for specific functions while also having other additional functionality.

[0102] In some aspects, the RAN 110 may include a CIoT enhanced Node B (CIoT eNB) 111 communicatively coupled to a CIoT Access Network Gateway (CIoT GW) 195. In certain examples, the RAN 110 may include multiple base stations (e.g., CIoT eNBs) connected to the CIoT GW 195, which may include an MSC 160, an MME 121, an SGSN 162, and / or an S-GW 122. In certain examples, the internal architecture of the RAN 110 and the CIoT GW 195 may be left to implementation and need not be standardized.

[0103] As used herein, the term "circuit" may refer to, belong to, or include an application-specific integrated circuit (ASIC) or other dedicated circuit, an electronic circuit, a processor (shared, dedicated, or group), a memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the functionality. In some aspects, a circuit may be implemented in one or more software or firmware modules, or the functionality associated with a circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include a logic component that may be at least partially operated in hardware. In some aspects, the circuits and modules disclosed herein may be implemented in a combination of hardware, software, and / or firmware. In some aspects, the functionality associated with a circuit may be distributed across multiple hardware or software / firmware modules. In some aspects, a module (as disclosed herein) may include a logic component that may be at least partially operated in hardware. The aspects described herein may be implemented in a system using any appropriately configured hardware or software.

[0104] Figure 1H An exemplary service capability exposure function (SCEF) according to some aspects is shown. Figure 1H , SCEF172 can be configured to open the services and capabilities provided by the 3GPP network interface to external third-party service provider servers that host various applications. In some aspects, a 3GPP network such as the CIoT architecture 140G can open the following services and capabilities: Home Subscriber Server (HSS) 116H, Policy and Charging Rules Function (PCRF) 118H, Packet Flow Description Function (PFDF) 120H, MME / SGSN 122H, Broadcast Multicast Service Center (BM-SC) 124H, Serving Telephony Server Control Function (S-CSCF) 126H, RAN Congestion Awareness Function (RCAF) 128H, and one or more other network entities 130H. The above services and capabilities of the 3GPP network can communicate with the SCEF 172 via one or more interfaces, such as Figure 1H shown.

[0105] The SCEF 172 may be configured to expose 3GPP network services and capabilities to one or more applications running on one or more service capability servers (SCS) / application servers (AS) (such as SCS / AS 102H, 104H, ..., 106H). Each of the SCS / AGs 102H to 106H may communicate with the SCEF 172 via application programming interfaces (APIs) 108H, 110H, 112H, 114H, as shown in FIG. Figure 1H shown.

[0106] Figure 1I An exemplary roaming architecture for a SCEF according to some aspects is shown. Figure 1I, SCEF 172 may be located in HPLMN 110I and may be configured to expose 3GPP network services and capabilities such as 102I, 104I. In some aspects, 3GPP network services and capabilities (such as 106I, ..., 108I) may be located within VPLMN 112I. In this case, the 3GPP network services and capabilities within VPLMN 112I may be exposed to SCEF 172 via an interworking SCEF (IWK-SCEF) 197 within VPLMN 112I.

[0107] Figure 2 1 shows exemplary components of a device 200 according to some aspects. In some aspects, the device 200 may include application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 (coupled together at least as shown). The components of the exemplary device 200 may be included in a UE or a RAN node. In some aspects, the device 200 may include fewer components (e.g., a RAN node may not utilize application circuitry 202, but instead include a processor / controller to process IP data received from an EPC). In some aspects, the device 200 may include additional components such as (for example) memory / storage, a display, a camera, sensors, and / or input / output (I / O) interface elements. In other aspects, the components described below may be included in multiple devices (e.g., the circuitry may be separately included in multiple devices for a Cloud-RAN (C-RAN) implementation).

[0108] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors, special-purpose processors, and specialized processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to and / or include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 200. In some aspects, the processor of the application circuitry 202 may process IP data packets received from the EPC.

[0109] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuitry 206 and generate baseband signals for the transmit signal path of the RF circuitry 206. The baseband processing circuitry 204 may interact with the application circuitry 202 to generate and process baseband signals and control the operation of the RF circuitry 206. For example, in some aspects, the baseband circuitry 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or one or more other baseband processors 204D for other existing, developing, or future generations of communications (e.g., second generation (2G), sixth generation (6G), etc.). Baseband circuitry 204 (e.g., one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via RF circuitry 206. In other aspects, some or all of the functions of baseband processors 204A-D may be included in modules stored in memory 204G and executed via central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, and the like. In some aspects, the modulation / demodulation circuitry of baseband circuitry 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some aspects, the encoding / decoding circuitry of baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. Aspects of modulation / demodulation and encoder / decoder functions are not limited to these examples and, in other aspects, may include other suitable functions.

[0110] In some aspects, the baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The one or more audio DSPs 204F may include elements for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, the components of the baseband circuitry 204 may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some aspects, some or all of the components of the baseband circuitry 204 and the application circuitry 202 may be implemented together, such as, for example, on a system on a chip (SOC).

[0111] In some aspects, the baseband circuitry 204 can provide communications compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 204 can support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN), other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), and / or Wireless Personal Area Networks (WPANs). In some aspects, a baseband circuitry 204 configured to support radio communications of multiple wireless protocols can be referred to as a multi-mode baseband circuitry.

[0112] The RF circuitry 206 can communicate with a wireless network by transmitting modulated electromagnetic radiation through a non-solid medium. In various aspects, the RF circuitry 206 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. The RF circuitry 206 can include a receive signal path that can include circuitry for downconverting RF signals received from the FEM circuitry 208 and providing baseband signals to the baseband circuitry 204. The RF circuitry 206 can also include a transmit signal path that can include circuitry for upconverting baseband signals provided by the baseband circuitry 204 and providing an RF output signal to the FEM circuitry 208 for transmission.

[0113] In some aspects, the receive signal path of RF circuitry 206 may include mixer 206A, amplifier 206B, and filter 206C. In some aspects, the transmit signal path of RF circuitry 206 may include filter 206C and mixer 206A. RF circuitry 206 may also include synthesizer 206D, which synthesizes frequencies for use by mixer 206A in the receive and transmit signal paths. In some aspects, mixer 206A in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 208 based on the synthesized frequency provided by synthesizer 206D. Amplifier 206B may be configured to amplify the downconverted signal, and filter 206C may be a low-pass filter (LPF) or a band-pass filter (BPF) and configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 204 for further processing. In some aspects, the output baseband signal may optionally be a zero-frequency baseband signal. In some aspects, the mixer 206A of the receive signal path may comprise a passive mixer.

[0114] In some aspects, mixer 206A of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer 206D to generate an RF output signal for FEM circuitry 208. The baseband signal may be provided by baseband circuitry 204 and may be filtered by filter 206C.

[0115] In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may include two or more mixers and may be arranged for quadrature down conversion and up conversion, respectively. In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may be arranged for direct down conversion and direct up conversion, respectively. In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may be configured for superheterodyne operation.

[0116] In some aspects, the output baseband signal and the input baseband signal can optionally be analog baseband signals. According to some alternative aspects, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative aspects, the RF circuitry 206 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 204 can include a digital baseband interface to communicate with the RF circuitry 206.

[0117] In some dual-mode aspects, separate radio IC circuits may optionally be provided for processing signals for each spectrum.

[0118] In some aspects, synthesizer 206D may optionally be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although other types of frequency synthesizers may also be suitable. For example, synthesizer 206D may be a sigma-delta synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0119] The synthesizer 206D may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer 206A of the RF circuit 206. In some aspects, the synthesizer 206D may be a fractional-N / N+1 synthesizer.

[0120] In some aspects, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not required. Depending on the desired output frequency, the divider control input can be provided by, for example, baseband circuitry 204 or application circuitry 202. In some aspects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by application circuitry 202.

[0121] The synthesizer circuit 206D of the RF circuit 206 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on the output) to provide a fractional frequency division ratio. In some exemplary aspects, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these aspects, the delay elements may be configured to decompose the VCO cycle into Nd equal groups of phases, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help maintain the total delay to one VCO cycle through the delay line.

[0122] In some aspects, the synthesizer circuit 206D can be configured to generate a carrier frequency as the output frequency, while in other aspects, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, or four times the carrier frequency) and can be used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some aspects, the output frequency can be the LO frequency (fLO). In some aspects, the RF circuit 206 can include an IQ / polarity converter.

[0123] The FEM circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 210 and / or amplify the received signals and provide an amplified version of the received signals to the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206, which may be performed by one or more of the one or more antennas 210. In various aspects, amplification by the transmit signal path or the receive signal path may be performed partially or entirely in the RF circuitry 206, partially or entirely in the FEM circuitry 208, or performed in both the RF circuitry 206 and the FEM circuitry 208.

[0124] In some aspects, the FEM circuitry 208 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 208 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 208 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 206); and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 210).

[0125] In some aspects, the PMC 212 can manage the power provided to the baseband circuitry 204. The PMC 212 can control power source selection, voltage scaling, battery charging, and / or DC-to-DC conversion. In some aspects, the PMC 212 can be included when the device 200 is capable of being powered by a battery, such as when the device is included in a UE. The PMC 212 can increase power conversion efficiency while providing beneficial implementation size and heat dissipation characteristics.

[0126] Figure 2 PMC 212 is shown coupled to baseband circuitry 204. In other aspects, PMC 212 may additionally or alternatively be coupled to or perform similar power management operations for other components, such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM circuitry 208.

[0127] In some aspects, the PMC 212 can control or otherwise participate in various power saving mechanisms of the device 200. For example, if the device 200 is in the RRC Connected state, in which the device remains connected to a RAN node because the device anticipates receiving communications soon, the device may enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 200 may be powered down for short intervals to conserve power.

[0128] According to some aspects, if there is no data communication activity for an extended period of time, the device 200 can transition to the RRC Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The device 200 enters a very low power state and performs paging, during which the device periodically wakes up to listen to the network and then powers down again. The device 200 can transition back to the RRC_Connected state to receive data.

[0129] An additional power saving mode can disable the device from using the network for a period exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device 200 may not be able to access the network in some way and may be powered off. Any data sent during this period will be delayed (possibly significantly), and it is assumed that the delay is acceptable.

[0130] The processor of application circuitry 202 and the processor of baseband circuitry 204 can be used to execute elements of one or more instances of a protocol stack. For example, the processor of baseband circuitry 204 can be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 202 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which is described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which are described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which is described in further detail below.

[0131] Figure 3 2 shows an exemplary interface of the baseband circuit 204 according to some aspects. As discussed above, Figure 2 The baseband circuit 204 may include processors 204A to 204E and a memory 204G utilized by the processors. Each of the processors 204A to 204E may include a memory interface 304A to 304E, respectively, for sending / receiving data to / from the memory 204G.

[0132] The baseband circuit 204 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); an application circuit interface 314 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); Figure 2 RF circuit interface 316 (for example, for sending / receiving data to / from the application circuit 202); Figure 2 an interface for sending / receiving data to / from the RF circuit 206); a wireless hardware connection interface 318 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 320 (eg, an interface for sending / receiving power or control signals to / from PMC212).

[0133] Figure 4 4 is an illustration of a control plane protocol stack according to some aspects. In one aspect, the control plane 400 is shown as a communication protocol stack between the UE 102, the RAN node 128 (or alternatively, the RAN node 130), and the AMF 132.

[0134] In some aspects, the PHY layer 401 may transmit or receive information used by the MAC layer 402 over one or more air interfaces. The PHY layer 401 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., the RRC layer 405). In some aspects, the PHY layer 401 may further perform error detection for transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0135] In some aspects, the MAC layer 402 may perform mapping between logical channels and transport channels, multiplexing MAC service data units (SDUs) from one or more logical channels to transport blocks (TBs) delivered to the PHY via transport channels, demultiplexing MAC SDUs from transport blocks (TBs) delivered from the PHY via transport channels to one or more logical channels, multiplexing MAC SDUs to TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0136] In some aspects, the RLC layer 403 can operate in multiple modes of operation, including transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The RLC layer 403 can perform transmission of upper layer protocol data units (PDUs), error correction via automatic repeat request (ARQ) for AM data transmission, and segmentation and reassembly of RLC SDUs for UM and AM data transmission. The RLC layer 403 can also maintain sequence numbers independent of sequence numbers in the PDCP for UM and AM data transmission. In some aspects, the RLC layer 403 can also resegment RLC data PDUs for AM data transmission, detect duplicate data for AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0137] In some aspects, the PDCP plane 404 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-sequence delivery of upper layer PDUs when re-establishing lower layers, perform reordering and deduplication of lower layer SDUs, perform PDCP PDU routing for split bearer scenarios, perform retransmission of lower layer SDUs, encrypt and decrypt control plane and user plane data, perform integrity protection and integrity verification on control plane and user plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0138] In some aspects, the main services and functions of the RRC layer 405 may include broadcasting system information (e.g., included in a master information block (MIB) or system information block (SIB) related to the non-access stratum (NAS)); broadcasting system information related to the access stratum (AS); paging initiated by the 5GC 120 or NG-RAN 110, establishment, maintenance and release of an RRC connection between a UE and an NG-RAN (e.g., RRC connection paging, RRC connection establishment, RRC connection addition, RRC connection modification and RRC connection release, also used for carrier aggregation and dual connectivity in NR or between E-UTRA and NR); establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); security functions including key management, mobility functions including handover and context transfer, control of UE cell selection and reselection and cell selection and reselection, and inter-radio access technology (RAT) mobility; and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more information elements (TEs), each of which may include a separate data field or data structure. In some aspects, the RRC layer 405 may also perform QoS management functions, detection and recovery of radio link failures, and NAS message transmission between the NAS 406 in the UE and the NAS 406 in the AMF 132.

[0139] In some aspects, the following NAS messages may be transmitted during corresponding NAS procedures, as shown in Table 1 below:

[0140]

[0141] Table 1

[0142] In some aspects, when the same message is used for multiple procedures, a parameter (e.g., registration type or TAU type) may be used that indicates the specific purpose of the procedure, for example, registration type = "initial registration", "mobility registration update", or "periodic registration update".

[0143] The UE 101 and the RAN node 128 / 130 may exchange control plane data via a protocol stack utilizing an NG radio interface (e.g., an LTE-Uu interface or an NR radio interface), which includes a PHY layer 401, a MAC layer 402, an RLC layer 403, a PDCP layer 404, and an RRC layer 405.

[0144] like Figure 4 As shown, the non-access stratum (NAS) protocol 406 forms the highest layer of the control plane between the UE 101 and the AMF 132. In various aspects, the NAS protocol 406 supports the mobility of the UE 101 and session management procedures to establish and maintain IP connectivity between the UE 101 and the UPF 134. In some aspects, the UE protocol stack may include one or more upper layers located above the NAS layer 406. For example, the upper layers may include an operating system layer 424, a connection manager 420, and an application layer 422. In some aspects, the application layer 422 may include one or more clients that may be used to perform various application functions, including providing interfaces to and communicating with one or more external networks. In some aspects, the application layer 422 may include an IP Multimedia Subsystem (IMS) client 426.

[0145] The NG Application Protocol (NG-AP) layer 415 may support the functionality of the N2 and N3 interfaces and include Primary Procedures (EPs). The EP is the unit of interaction between the RAN nodes 128 / 130 and the 5GC 120. In certain aspects, the NG-AP layer 415 services may include two groups: UE-associated services and non-UE-associated services. These services perform a number of functions, including but not limited to: UE context management, PDU session management, and management of corresponding NG-RAN resources (e.g., data radio bearers [DRBs]), UE capability indication, mobility, NAS signaling transmission, and configuration transmission (e.g., for transmitting SON information).

[0146] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 414 may ensure reliable transmission of signaling messages between the RAN nodes 128 / 130 and the AMF 132 based in part on the IP protocol supported by the IP layer 413. The L2 layer 412 and the L1 layer 411 may refer to communication links (e.g., wired or wireless) used by the RAN nodes 128 / 130 and the AMF 132 to exchange information.

[0147] The RAN node 128 / 130 and the AMF 132 may exchange control plane data using the N2 interface via a protocol stack including an L1 layer 411 , an L2 layer 412 , an IP layer 413 , an SCTP layer 414 , and an S1-AP layer 415 .

[0148] Figure 5is an illustration of a user plane protocol stack according to some aspects. In this aspect, user plane 500 is shown as the communication protocol stack between UE 102, RAN node 128 (or alternatively, RAN node 130), and UPF 134. User plane 500 may utilize at least some of the same protocol layers as control plane 400. For example, UE 102 and RAN node 128 may utilize the NR radio interface to exchange user plane data via a protocol stack that includes PHY layer 401, MAC layer 402, RLC layer 403, PDCP layer 404, and Service Data Adaptation Protocol (SDAP) layer 416. In some aspects, SDAP layer 416 may perform mapping between Quality of Service (QoS) flows and Data Radio Bearers (DRBs) and marking DL and UL packets with QoS Flow IDs (QFIs). In some aspects, IP protocol stack 513 may be located above SDAP 416. User Datagram Protocol (UDP) / Transmission Control Protocol (TCP) stack 520 may be located above IP stack 513. A Session Initiation Protocol (SIP) stack 522 may be located above the UDP / TCP stack 520 and may be used by the UE 102 and the UPF 134 .

[0149] The General Packet Radio Service (GPRS) Tunneling Protocol for User Plane (GTP-U) layer 504 may be used to carry user data within the 5G core network 120 and between the radio access network 110 and the 5G core network 120. For example, the transmitted user data may be packets in IPv4, IPv6, or PPP format. The UDP and IP Security (UDP / IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN nodes 128 / 130 and the UPF 134 may utilize the N3 interface to exchange user plane data via a protocol stack that includes the L1 layer 411, the L2 layer 412, the UDP / IP layer 503, and the GTP-U layer 504. As described above with respect to Figure 4 As discussed, the NAS protocol supports the mobility of UE 101 and session management procedures to establish and maintain IP connectivity between UE 101 and UPF 134.

[0150] Figure 6 is a block diagram illustrating components that can read instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some exemplary aspects. Figure 6A schematic diagram of hardware resources 600 is shown, including one or more processors (or processor cores) 610, one or more memory / storage devices 620, and one or more communication resources 630, each of which can be communicatively coupled via a bus 640. For aspects utilizing node virtualization (e.g., NFV), a hypervisor 602 can be executed to provide an execution environment for one or more network slices and / or sub-slices to utilize the hardware resources 600.

[0151] Processor 610 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 612 and processor 614.

[0152] The memory / storage device 620 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 620 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0153] The communication resources 630 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 via the network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Components (e.g. Low power consumption), components and other communication components.

[0154] The instructions 650 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside entirely or partially within at least one of the processors 610 (e.g., within a cache memory of the processor), the memory / storage device 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the database 606. Thus, the memory of the processor 610, the memory / storage device 620, the peripheral devices 604, and the database 606 are examples of computer-readable and machine-readable media.

[0155] Figure 7 is a diagram of an initial access procedure 700 including PRACH preamble retransmission according to some aspects. Figure 7 , the initial access procedure 700 may begin at operation 702, at which time initial synchronization may occur. For example, the UE 101 may receive a primary synchronization signal and a secondary synchronization signal to achieve initial synchronization. In some aspects, the initial synchronization at operation 702 may be performed using one or more SS blocks received in an SS burst set. At operation 704, the UE 101 may receive system information, such as one or more system information blocks (SIBs) and / or a master information block (MIB).

[0156] At operations 706 through 714, a random access procedure may occur. More specifically, at operation 706, a PRACH preamble transmission may occur as message 1 (Msg1). At operation 710, UE 101 may receive a random access response (RAR) message, which may be a random access procedure message 2 (Msg2). In Msg2, node (e.g., gNB) 111 may respond with a random access radio network temporary identifier (RA-RNTI), which may be calculated based on the preamble resources (e.g., time and frequency allocation).

[0157] In some aspects, the UE 101 may be configured to, when a RAR is not received or detected within a preconfigured or predefined time window, perform one or more retransmissions of the PRACH preamble at operation 708. The PRACH preamble retransmissions may be performed with a power ramp as described herein below to increase the transmission power until a random access response is received.

[0158] At operation 712, UE 101 may transmit a random access procedure message 3 (Msg3), which may include a radio resource control (RRC) connection request message. At operation 714, UE 101 may receive a random access procedure message 4 (Msg4), which may include an RRC connection setup message and carry a cell radio network temporary identifier (CRNTI) for subsequent communications between UE 101 and node 111.

[0159] In some aspects, the UE 101 may be configured to perform uplink (UL) beam switching during retransmission of configuration data such as a PRACH preamble. In some aspects, when the UE has multiple analog beams and beam correspondence between transmission and reception is not available, the UE may need to change the transmit beam to retransmit the PRACH or increase the transmit power of the PRACH retransmission. In some aspects, when the UE changes the Tx beam, its power ramp counter may remain unchanged (i.e., the UE uses the same or similar power for the PRACH transmission as compared to the previous PRACH transmission). In some aspects, when the UE does not change the Tx beam, its power ramp counter may increase (e.g., incremented by 1), and the UE may be configured to increase the power of the PRACH retransmission.

[0160] In some aspects, when a UE is configured for multi-beam operation, it may receive synchronization signals (SS) from multiple antennas in a base station, where the base station may be configured to use beam scanning to generate the SS. In some aspects, when the UE detects a synchronization signal from a beam, there may be a PRACH resource associated with the beam of the detected synchronization signal. In this regard, the UE may be configured to use the PRACH resource to transmit a PRACH preamble. Depending on the beam of the detected synchronization signal, the UE may use different PRACH resources for different PRACH sequences.

[0161] Figure 8 816. FIG2 is an illustration of a PRACH resource configuration according to some aspects. In some aspects, a base station (e.g., a gNB or node 111) may transmit a synchronization signal burst set 802, which may include multiple synchronization signals (or SS blocks), such as 806, 808, and 810. The base station may use multiple synchronization signal blocks (SS blocks) for each downlink transmission beam. In some aspects, for each downlink transmission beam, there may be one PRACH resource subset configured by system information. For example, UE 101 may be configured with a PRACH resource set 804, which may include PRACH resource subsets 812, 814, ..., 816. Each PRACH resource subset may include time and frequency information for transmitting PRACH-related information, such as a PRACH preamble. In some aspects, there may be a one-to-one or many-to-one correlation between synchronization signal blocks 806, ..., 810 and PRACH resource subsets 812, ..., 816.

[0162] In some aspects, downlink control information carried by a PDCCH may be monitored in one or more control resource sets (CORESETs). A CORESET represents the time-frequency resources configured for a UE to monitor for potential transmissions of a PDCCH carrying downlink control information (DCI). In this regard, a CORESET may be defined as a set of resource element groups (REGs) having one or more symbol durations according to a given numerology, during which the UE 101 may attempt to (e.g., blindly) decode downlink control information (DCI). A UE is configured with PDCCH monitoring opportunities and is expected to monitor the PDCCH in the CORESET associated with a particular PDCCH monitoring opportunity configuration. In the frequency domain, a CORESET may be contiguous or non-contiguous; in the time domain, a CORESET may be configured with one or a group of contiguous OFDM symbols. Furthermore, for large carrier bandwidths, the maximum CORESET duration (in time) may be, for example, 2 symbols, while for narrow carrier bandwidths, the maximum CORESET duration (in time) may be, for example, 3 symbols. In addition, time-first or frequency-first REG-to-control channel element (CCE) mapping can be supported for NR PDCCH.

[0163] In some aspects, the physical antenna elements of a transmission reception point (TRP), gNB, and UE may be divided into antenna subarrays, where an antenna array may include multiple subarrays. In some aspects, the physical antenna elements of an antenna subarray may be virtualized to antenna ports using analog beamforming. Analog beamforming may be used to improve the performance of the communication link between the TRP and the UE. Analog beamforming at the TRP and at the UE may be trained by transmitting a series of reference signals with different beamformings. In some aspects, the UE may also train receive beamforming. The optimal analog beamforming at the UE may depend on the beamforming at the TRP, and vice versa. In some aspects, each subarray may have a different analog beamforming, which may be controlled by antenna weights.

[0164] In some aspects, multiple optimal Tx / Rx beam combinations can be established at the TRP / gNB and UE for possible communications. The optimal Tx beam on one antenna subarray can be reused on another antenna subarray. The optimal Rx beam at the UE can be the same. In terms of spatial channel parameters, reference signals transmitted on antenna ports using the same beam (using the same or different panels) are quasi-co-located (or "QCL") with each other.

[0165] Figure 9 is an illustration of NR PUCCH and uplink data slots with short duration and long duration according to some aspects. Figure 9, a PUCCH with a short duration is transmitted in time slot 902, and a PUCCH with a long duration is transmitted in time slot 912. For the NR PUCCH with a short duration in time slot 902, the NR PUCCH 910 and the physical uplink shared channel (PUSCH) (or uplink data) 908 are multiplexed in a time division multiplexing (TDM) manner, which may be useful for low-latency applications.

[0166] For the NR PUCCH 918 with a long duration within the time slot 912, multiple OFDM symbols may be allocated to the NR PUCCH to improve the link budget and uplink coverage for control channel communication. More specifically, for the uplink (UL) data time slot portion, the NR PUCCH 918 and the PUSCH 920 may be multiplexed in a frequency division multiplexing (FDM) manner. In some aspects and as Figure 9 As shown, in order to accommodate the downlink (DL) to UL and UL to DL switching time and round-trip propagation delay, a guard period (GP) (906 and 916) is inserted between the NR physical downlink control channel (NR PDCCH 904 and 914) and the NR PUSCH 908 or the NR PUCCH 918 with a long duration.

[0167] In some aspects, the short PUCCH 910 may span one or two symbols, while the long PUCCH 918 may span any number of symbols, such as from 4 to 14 symbols within a slot. In some aspects associated with 5G-NR communications, for a given UE, the short PUCCH 910 and the long PUCCH 918 may be multiplexed in a TDM manner in the same slot (e.g., as Figure 14 For example, the long PUCCH 918 may be used to carry a relatively large payload (e.g., a channel state information (CSI) report), while the short PUCCH 910 may be used to carry time-sensitive information, including hybrid automatic repeat request-acknowledgement (HARQ-ACK) information and scheduling request (SR) information, as part of uplink control information (UCI).

[0168] In some aspects, a sequence-based approach can be used for NR PUCCHs with short durations that carry up to 2 bits of UCI payload. Specifically, for this option, independent resources in the frequency or code domain can be allocated to carry HARQ-ACK feedback information, where the independent resources correspond to different cyclically shifted versions of the same base sequence (e.g., Zadoff-Chu sequences or computer-generated sequences are potential candidates for the base sequence), and these different cyclically shifted versions are orthogonal in frequency (i.e., associated with zero cross-correlation). In this sequence-based option, the receiving gNB can perform energy detection to distinguish between HARQ-ACK or SR information in the received PUCCH, resulting in reduced receiver complexity.

[0169] The techniques disclosed herein are associated with the sequence design of NR PUCCH with short duration and long duration. More specifically, the techniques disclosed herein below include: mechanisms for multiplexing short PUCCH and long PUCCH carrying up to 2 bits of UCI in a code division multiplexing (CDM) manner, sequence design of short PUCCH with 2-symbol duration carrying up to 2 bits of UCI, and sequence design of short PUCCH with 1-symbol duration carrying up to 2 bits of UCI (from single and multiple UE perspectives, HARQ-only, SR-only, and simultaneous HARQ and positive SR transmissions).

[0170] Multiplexing short PUCCH and long PUCCH carrying up to 2 bits of UCI in CDM mode

[0171] In some aspects, a sequence-based structure can be used for PUCCHs with short durations that carry up to 2 bits of UCI payload, such as for 1 or 2 bits of HARQ-ACK feedback or SR information. In this case, short and long PUCCHs from the same or different UEs can be multiplexed in the same physical resources in a CDM manner, which can allow for more efficient operation from a system-level perspective. Figure 10 is an illustration of code division multiplexing (CDM) of short PUCCH and long PUCCH, wherein the short PUCCH is allocated in the last symbol of a slot, according to some aspects. Figure 10 , the long PUCCH may be transmitted using frequency hopping within slot 1000. More specifically, a first portion 1002A of the long PUCCH may occupy symbols 0 through 6, and a second portion 1002B may be frequency-hopped and transmitted at a different frequency in symbols 7 through 13. The short PUCCH 1004 may be code-division multiplexed with the long PUCCH and transmitted in the same symbol, such as the last symbol of the long PUCCH transmission (i.e., symbol 13).

[0172] In order to achieve CDM-based multiplexing of short PUCCH and long PUCCH carrying up to 2 bits of UCI in the same physical resources, in one aspect of the present disclosure, the same set of sequences may be used to transmit demodulation reference signals (DM-RS) and / or UCI for long PUCCH and short PUCCH. In addition, in some aspects, when short PUCCH and long PUCCH are multiplexed in a CDM manner, some sequences in this set of sequences may be allocated for transmitting DM-RS and / or UCI for long PUCCH, while the remaining sequences may be allocated for transmitting UCI for short PUCCH.

[0173] In some aspects, the short PUCCH may be transmitted in the last one or two symbols within a slot that includes a long PUCCH transmission. In addition, for symbol-based data transmission, such as for ultra-reliable low-latency communication (URLLC), a short PUCCH carrying 1 or 2 bits of HARQ-ACK feedback or SR may be transmitted in the middle of a slot to meet strict delay requirements. In this case, the short PUCCH may be transmitted in any one or two symbols within a slot.

[0174] Figure 11 is an illustration of code division multiplexing of short PUCCH and long PUCCH according to some aspects, where the short PUCCH is allocated in the middle of a slot. Figure 11 , the long PUCCH may be transmitted using frequency hopping within slot 1100. More specifically, a first portion 1102A of the long PUCCH may occupy symbols 0 through 6, and a second portion 1102B may be frequency-hopped and transmitted at a different frequency in symbols 7 through 13 of slot 1100. The short PUCCH 1104 may be code division multiplexed with the long PUCCH and transmitted in the same symbols, such as symbols 4 through 5 of the long PUCCH transmission 1102A.

[0175] In some aspects, Zadoff-Chu or computer-generated sequences can be used for the sequences of short and long PUCCH. To multiplex short and long PUCCH in a CDM manner, the same base sequence can be used for transmission of short and long PUCCH in the same time slot. In addition, different cyclic shifts can be applied to the transmission of short and long PUCCH in the same resources.

[0176] In some aspects associated with short PUCCH and long PUCCH communications, sequence hopping may be employed to randomize inter-cell interference. For short PUCCH and long PUCCH multiplexed in a CDM manner, the same sequence hopping pattern may be employed regardless of the starting and ending positions of the short PUCCH and long PUCCH. In this regard, in some aspects, the same cell-specific (sequence) hopping pattern may be applied to sequence hopping (e.g., for selecting a base sequence) for transmission of short PUCCH and long PUCCH, where the cell-specific hopping may vary per symbol and / or per time slot to randomize inter-cell interference. Additionally, the cell-specific hopping pattern for base sequence selection may be communicated to the UE via higher layer signaling or other types of configuration information signaling.

[0177] In some aspects, when Zadoff-Chu or computer-generated sequences are used for the base sequence for short PUCCH and long PUCCH, cyclic shift hopping (e.g., using a cyclic shift hopping sequence) may be employed. The cyclic shift hopping sequence may be communicated via higher layer signaling and may be defined as a function of one or more of the following parameters: physical cell ID or virtual cell ID, symbol index, subslot index, and slot index. In some aspects, the subslot index may be used when a slot having a 14-symbol duration is further divided into two subslots, each having 7 symbols.

[0178] In some aspects, a slot index may be used for long PUCCH with or without frequency hopping. More specifically, for frequency hopping, the switching point may be located in the middle of the long PUCCH transmission duration, rather than in the middle of the slot duration. Given that the switching points may not be aligned between different UEs, a single slot index may be used for the generation of cell-specific cyclic shift values.

[0179] In some aspects, the cell-specific cyclic shift hopping pattern in ns slots and 1st symbol may be given by:

[0180]

[0181] Where c0 and c1 are constants that may be predefined in the wireless specification or configured by higher layers via Multicast Channel Scheduling Information (MSI), Remaining Minimum System Information (RMSI), System Information Block (SIB), or Radio Resource Control (RRC) signaling. sym UL is the number of symbols in a slot. For example, c0=c1=16. Function c(·) is a pseudo-random function that may be defined in the NR specification. In some aspects, the above summation may be performed for i=0 to 6.

[0182] In some aspects, the symbol and / or slot index may be defined according to a reference numerology (e.g., 15 KHz for carrier frequencies below 6 GHz or 120 KHz for carrier frequencies above 6 GHz) or the numerology used for transmission of a synchronization signal (SS) block or a physical broadcast channel (PBCH) or RMSI. Alternatively, the symbol and / or subslot index and / or slot index may be defined according to the numerology configured within a bandwidth part (BWP).

[0183] In some aspects, when one slot duration (7 or 14 symbols) is configured in a UE-specific manner to multiplex long PUCCH for different slot durations in the same physical resources, the cell-specific cyclic shift hopping pattern may be aligned between slot durations of 7 and 14 symbols. In one option, for long PUCCH with a 7-symbol slot duration, the cell-specific cyclic shift hopping pattern including symbol indices may be generated according to a 14-symbol slot duration.

[0184] In some aspects, such as in an LTE communication system, UEs that share the same cyclic shift (CS) pattern or the same orthogonal cover code (OCC) with a target UE will be rotated in the next time slot, with the aim of dispersing the near-far effect caused by a strongly hostile UE to other UEs. For a 5G-NR based communication system, the CS and OCC reorganization mechanism may be disabled to allow beam scanning operation by using the same OCC within one time slot. In one aspect, whether the CS and OCC reorganization mechanism is enabled or disabled may be predefined in the 5G-NR specification or configured by a higher layer via MSI, RMSI, SIB or RRC signaling. For example, for carrier frequencies above 6 GHz, the CS and OCC reorganization mechanism may be disabled. On the other hand, in the case where frequency hopping is applied to a long PUCCH, the CS and OCC reorganization mechanism may be enabled.

[0185] In some aspects, the cyclic shift value used for transmission of short PUCCH and / or long PUCCH may be determined based on a value or a combination thereof configured by higher layers or dynamically indicated in downlink control information (DCI), or a value calculated according to a cyclic shift hopping pattern as described above, or any combination thereof.

[0186] Sequence design for short PUCCH with 2-symbol duration carrying up to 2 bits of UCI

[0187] In some aspects, a sequence selection-based approach can be used for short PUCCH that carries up to 2 bits of UCI payload. Furthermore, short PUCCH can span 1 or 2 symbols within a slot. Additionally, cell-specific and / or UE-specific cyclic shift hopping patterns can be defined to randomize inter-cell and / or intra-cell interference during PUCCH transmission.

[0188] In some aspects, for a short PUCCH with a 2-symbol duration, a cyclic shift offset may be applied in different symbols. Furthermore, the cyclic shift offset may be predefined in the 5G-NR specification or configured by higher layers via MSI, RMSI, system information block (SIB), or RRC signaling. In some aspects, when the cyclic shift offset is configured via UE-specific RRC signaling, intra-cell interference randomization may be achieved for a short PUCCH with a 2-symbol duration.

[0189] In some aspects, the cyclic shift value for the (l-1)th symbol and the lth symbol of the short duration PUCCH may be the following formula:

[0190] and

[0191] where n cs (l–1) and n cs (l) are the cyclic shift values ​​for the (l-1)th symbol and the lth symbol (which may be the penultimate symbol or the last symbol), respectively. nPuccH is the cyclic shift value, which is configured by higher layers via UE-specific RRC signaling or dynamically indicated in the DCI, or a combination of the two. Δ CS is the cyclic shift offset. is the number of subcarriers in a resource block, i.e.

[0192] Figure 12 is an illustration of cyclic shift hopping for a short PUCCH with a 2-symbol duration according to some aspects. Figure 12 , the short PUCCH 1200 may include PUCCH transmissions 1202 and 1204 in two frequency hopping symbols. Figure 12 As shown, the first short duration PUCCH transmission 1202 may be based on a cyclic shift value of 3. In addition, due to the cyclic shift offset Δ CS is 3, so the cyclic shift value for the second short PUCCH transmission 1204 may be equal to 6.

[0193] In some aspects, a cell-specific hopping pattern may be applied to sequence generation for short PUCCH with 2-symbol duration that carries up to 2-bit UCI payload. As described herein, this functionality may allow for multiplexing of short and long PUCCH in a CDM manner.

[0194] In one example, the cyclic shift value of the lth symbol for PUCCH transmission may be given by the following formula:

[0195]

[0196] where n PN (n S ,l) is used for n s Cell-specific cyclic shift hopping pattern for slot and 1st symbol. As discussed herein, slot index and symbol index may be defined according to reference numerology used for transmission of SS blocks or RMSI or numerology configured within a bandwidth portion.

[0197] In some aspects, a combination of a cell-specific cyclic shift hopping pattern and a UE-specific cyclic shift hopping pattern may be applied for sequence generation for a short PUCCH with a 2-symbol duration that carries a maximum of 2-bit UCI payload.

[0198] In one example, the cyclic shift values ​​for the (l–1)th symbol and the lth symbol may be defined by the following formula:

[0199]

[0200] As discussed herein, Δ CS is the cyclic shift offset, which can be configured through UE-specific RRC signaling.

[0201] In some aspects, the cyclic shift hopping pattern may be predefined (e.g., in the 5G-NR specification) or defined as a function of one or more of the following parameters: physical cell ID, virtual cell ID, cyclic shift value configured by higher layer signaling (or indicated by DCI) or a combination thereof, symbol / slot / frame index, frequency resource index, and UE ID (e.g., cell radio network temporary identifier (C-RNTI)).

[0202] In some aspects, the cyclic shift value for the (I-1)th symbol and the Ith symbol in a PUCCH transmission may be defined by the following formula:

[0203]

[0204] and

[0205]

[0206] Where f(n RNTI ) is defined as a function of C-RNTI. For example, f(n RNTI )=0 or 1, depending on C-RNTI.

[0207] Sequence design for short PUCCH with 1-symbol duration carrying up to 2 bits of UCI

[0208] In some aspects, a sequence selection-based approach may be used for a 1-symbol short PUCCH that carries up to 2 bits of UCI payload (e.g., 1 or 2 bits of HARQ-ACK feedback and / or SR information). Furthermore, the 1-symbol short PUCCH may span multiple physical resource blocks (PRBs), where one PRB may include 12 frequency subcarriers in 5G-NR communications. Independent resources may be allocated in the frequency and / or code domains to carry only HARQ, only SR, or both HARQ and SR feedback using the 1-symbol short PUCCH for a single UE or multiple UEs multiplexed within a slot, where the independent resources may correspond to one of the following:

[0209] (a) different cyclically shifted versions of the same base sequence (e.g., Zadoff-Chu or computer-generated sequences are potential candidates for the base sequence), which are orthogonal in frequency (i.e., zero cross-correlation) and mapped on the same PRB; and

[0210] (b) The same sequence (ie, the base sequence as described above) or a set of sequences mapped on different PRBs (different cyclic shifted versions of the base sequence).

[0211] In some aspects, frequency domain and code domain resources may be indicated via a single resource index that is configured by higher layers via UE-specific RRC signaling or dynamically indicated in the DCI, or a combination of both. Various combinations of frequency domain and code domain resources may be configured by higher layers to allocate N in a time slot. PUCCH independent resources for 1-symbol short PUCCH transmission.

[0212] In one aspect, the number of independent resources N PUCCH It can be defined by the following formula: N PUCCH =N f *N c , where N f is the number of PRBs allocated to the 1-symbol PUCCH, and Nc is the number of cyclic shift values ​​of the base sequence allocated to each PRB (ie, the number of orthogonal sequences).

[0213] Figure 13A and Figure 13B is an illustration of different combinations of frequency and code domain resources for a short PUCCH with 1 symbol duration according to some aspects. More specifically, Figure 13A and Figure 13B shows the allocated resource index N PUCCH = Two different ways of 24 independent PUCCH resources.

[0214] See also Figure 13A, diagram 1300 shows the determination of a PUCCH resource index 1308 based on frequency domain resources 1302 and code domain resources 1304. More specifically, the PUCCH resource index 1308 may be determined based on two PRBs 1306 and twelve cyclic shift values ​​1304 (or N f =2;N C =12) The PUCCH resource index 1308 is determined to be N PUCCH =24.

[0215] See also Figure 13B , diagram 1310 shows the determination of a PUCCH resource index 1318 based on frequency domain resources 1312 (e.g., PRBs) and code domain resources 1314 (e.g., different cyclic shift values ​​for cyclically shifting a base sequence). More specifically, the PUCCH resource index 1318 may be determined based on four PRBs 1316 and six cyclic shift values ​​1314 (or N f =4;N C =6) Determine the PUCCH resource index 1318 as N PUCCH =24.

[0216] In some aspects, four independent resources (ie, N PUCCH =4) to support simultaneous 1-bit HARQ-ACK transmission and SR transmission for a single UE. The following four resources can be configured for a single UE:

[0217] (a) The first resource may be configured for 1-bit HARQ-ACK-only transmission (i.e., indicating negative SR);

[0218] (b) The second resource may be configured for 1-bit HARQ-NAK transmission only (i.e., indicating negative SR);

[0219] (c) The third resource may be configured for simultaneous 1-bit HARQ-ACK transmission and positive SR transmission; and

[0220] (d) A fourth resource may be configured for simultaneous 1-bit HARQ-NAK transmission and positive SR transmission. In some aspects, this resource may be reused for SR-only transmission (i.e., no HARQ and SR multiplexing), or for simultaneous 1-bit HARQ and SR transmissions when the UE loses a DL grant (i.e., DTX (discontinuous transmission) for HARQ) but still needs to transmit a positive SR in the same time slot. Alternatively, an additional independent resource may be configured for SR-only transmission. In this case, a total of five resources may be configured for a given UE to support 1-bit HARQ-ACK feedback, SR, and 1-bit HARQ-ACK along with SR transmission.

[0221] In some aspects, multiple UEs can be multiplexed in the same time slot using CDM and / or FDM by allocating independent resources to each UE for simultaneous SR or 1-bit HARQ and / or 1-bit HARQ and positive SR transmission. PUCCH =4, so for N PUCCH The UE multiplexing capacity of >4 will be In order to effectively utilize resources, N PUCCH Configured as an integer multiple of 4, where the value of the integer will be configured by higher layers, depending on the required UE multiplexing capacity. Figure 13A and Figure 13B As shown, N PUCCH = 24 A maximum of 6 UEs can be multiplexed for simultaneous 1-bit HARQ and SR transmissions in the same time slot. Alternatively, when 5 resources are configured for a given UE to support 1-bit HARQ-ACK feedback, SR, and 1-bit HARQ-ACK together with SR transmission, for N PUCCH The UE multiplexing capacity of >5 will be

[0222] In some aspects, eight independent resources (ie, N PUCCH =8) to support simultaneous 2-bit HARQ-ACK transmission and SR transmission for a single UE. The following eight resources can be configured for a single UE:

[0223] (a) Four resources may be configured for 2-bit HARQ-only transmission (i.e., indicating negative SR), where the four resources are used to transmit ACK-ACK, ACK-NAK, NAK-ACK, and NAK-NAK bits;

[0224] (b) Three resources can be configured for 2-bit HARQ and positive SR transmission, where the 2-bit HARQ consists of at least one ACK bit, i.e., ACK-ACK or ACK-NAK or NAK-ACK;

[0225] (c) The last resource can be configured for simultaneous 2-bit HARQ and positive SR transmission, where none of the HARQ bits are ACKs, i.e., HARQ can be NAK-NAK or DTX. Similar to the 1-bit case, this resource can be reused for SR-only transmission (i.e., no HARQ and SR multiplexing). Alternatively, an additional independent resource can be configured for SR-only transmission. In this case, a total of nine resources can be configured for a given UE to support 2-bit HARQ-ACK feedback, SR, and 2-bit HARQ-ACK along with SR transmission.

[0226] In some aspects, multiple UEs can be multiplexed in the same time slot using CDM and / or FDM by allocating independent resources to each UE for simultaneous transmission of SR only or 2-bit HARQ-ACK only and / or 2-bit HARQ-ACK and positive SR. Due to the simultaneous 2-bit HARQ-ACK and SR transmission for a single UE, the minimum N PUCCH =8, so for N PUCCH The multiplexing capacity of UEs >8 will be In order to effectively utilize resources, N PUCCH Configured as an integer multiple of 8, where the value of the integer will be configured by higher layers, depending on the required UE multiplexing capacity. Figure 13A and Figure 13B As shown, N PUCCH = 24 A maximum of 3 UEs can be multiplexed for simultaneous 2-bit HARQ-ACK and SR transmissions in the same time slot. Alternatively, when 9 resources are configured for a given UE to support 2-bit HARQ-ACK feedback, SR, and 2-bit HARQ-ACK along with SR transmission, for N PUCCH The UE multiplexing capacity of >9 will be

[0227] Figure 14 is an illustration of uplink control channels including long duration PUCCH (long PUCCH) and short duration PUCCH (short PUCCH) according to some aspects. Figure 14 , which shows a time slot 1400 that may include a short PUCCH 1408 and a long PUCCH 1406. Both the long-duration PUCCH and the short-duration PUCCH can be used by the UE to carry UCI to the NR gNB. Multiple DFT-s-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) waveform symbols can be assigned to the long PUCCH 1406 to improve the link budget and uplink coverage of the control channel. More specifically, the long PUCCH 1406 can be multiplexed with the UL data channel (i.e., PUSCH 1410) in a frequency division multiplexing (FDM) manner. The short PUCCH 1408 can be multiplexed with the PUSCH 1410 in a time division multiplexing (TDM) manner and can use one or two symbols. To accommodate DL-to-UL and UL-to-DL switching time and round-trip propagation delay, a guard period (GP) 1404 may be inserted between the NR physical downlink control channel (NR PDCCH) 1402 and the PUSCH 1410.

[0228] The duration of the long PUCCH 1406 may vary depending on the presence and duration of other physical channels. Figure 14In the time slot, the PDCCH 1402 and the short PUCCH 1408 each have a symbol duration. In other aspects, the short PUCCH 1408 may not exist in the time slot, so that the duration of the long PUCCH 1406 can be comparable to Figure 14 In other aspects, the PDCCH 1402 or the short PUCCH 1408 may have two symbols, then the duration of the long PUCCH 1406 may become longer than Figure 14 The duration shown is short. In addition, Figure 14 Compared to the slot 1400 in FIG. 1 , the duration of the slot can be reduced by half, resulting in half the symbols in the slot. Thus, the duration of the long PUCCH 1406 can be correspondingly reduced based on the reduced number of symbols. The structure of the long PUCCH 1406 based on UCI and DMRS (demodulation reference signal) helps the receiver recover the received signal and detect UCI. The structure can be designed so that the performance and resource efficiency of the long PUCCH are robust during variations in the duration of the long PUCCH.

[0229] The following table shows different formats of PUCCH based on the length (in OFDM symbols) and the UCI bits carried by the PUCCH.

[0230] PUCCH format Short / Long Length (in OFDM symbols) UCI digits 0 short 1～2 ≤2 1 long 4～14 ≤2 2 short 1～2 >2 3 long 4～14 >2,<N 4 long 4～14 >2

[0231] The technology disclosed herein involves allocating and indicating resources to UEs on which they can transmit their PUCCHs without colliding with other PUCCHs transmitted in the same time slot. The resources used for PUCCH transmission include one or a combination of the following: a physical resource block (PRB) comprising a set of subcarriers, a cyclic shift index of the base sequence used, and an index of the orthogonal cover code (OCC) applied to the corresponding PUCCH. The technology disclosed herein can be applied to any of the PUCCH formats provided in the table above.

[0232] Candidate sets of PUCCH resources can be preconfigured to each UE via RRC signaling and a field in the PDCCH's Downlink Control Information (DCI). This field in the DCI indicates (for each UE) which set of preconfigured candidate resource sets to use for the corresponding PUCCH transmission. The number of preconfigured candidate resource sets is limited due to the overhead of this DCI field (which increases with the number of preconfigured resource sets) and the increased RRC configuration overhead. This limited configuration can lead to an increased probability of PUCCH resource collisions between UEs and potential loss of corresponding UCI at the gNB receiver, especially when many UEs are scheduled to transmit PUCCH in the same timeslot. The techniques disclosed herein can be used to overcome these drawbacks.

[0233] In some aspects, the index of the control channel element (CCE) (for a PDCCH carrying DCI indicating a PUCCH resource) provides an offset to the indicated resource. The corresponding UE transmits its PUCCH on the resource determined by applying the offset to the resource indicated by the DCI field. Other types of DL resources related to PDCCH transmissions, such as control resource sets (CORESETs), may also be used to enable providing an offset to the indicated PUCCH resource and adjusting the resource for the corresponding UE. By using the offset in the configured PUCCH resources, potential collisions with other PUCCH transmissions can be avoided. More specifically, by adjusting the resource index by selecting the CCE for the corresponding PDCCH for each UE, the use of the offset enables the gNB to avoid collisions between PUCCHs from different UEs, even in the case where pre-configured PUCCH resources overlap between different UEs.

[0234] Figure 15 is an illustration of resource configuration for a physical uplink control channel according to some aspects. Figure 15 , which shows PUCCH transmission 1500 by multiple UEs (e.g., 1502, 1504, 1506, and 1508) with uplink system bandwidth. Figure 15 As shown, each of UEs 1502 to 1508 may be configured with an UL carrier (resource block or RB) that may occupy a portion or the entire system bandwidth. Figure 15 , the UL carriers for UE#1 and UE#4 are configured in the lower half or upper half of the UL system bandwidth, and the UL carriers for UE#2 and UE#3 are configured with the full system bandwidth.

[0235] Within the configured UL carrier, it is assumed that each UE 1502 to 1508 is pre-configured with four candidates for RBs through (for example) higher layer signaling. Each candidate resource may consist of a single or multiple RBs. For example, a PUCCH that may be configured to carry tens of UCI bits (such as NR PUCCH formats 2 and 3) may require multiple RBs, and therefore some candidates may consist of multiple RBs to support the corresponding PUCCH transmission carrying tens of UCI bits. On the other hand, a candidate resource may consist of a single physical resource block (or PRB), which may be useful for a PUCCH format that carries 1 or 2 UCI bits. Although for illustrative purposes in Figure 15 Only four UEs are shown in FIG, but many more UEs (e.g., hundreds of UEs) can be served within the UL system bandwidth. In such a scenario, there is a greater likelihood that the configured resources will overlap between UEs. Consequently, when multiple UEs transmit PUCCH in the same timeslot, this can increase the probability of resource collisions.

[0236] In some aspects, the DCI carried on the PDCCH may indicate which of the configured candidates is to be used for the corresponding PUCCH transmission of the UE. Figure 15 In the exemplary illustration of , four candidate resources are configured for each UE, so two bits may be configured for the DCI field to indicate which resource among the four candidates will be used in the corresponding PUCCH transmission.

[0237] In some aspects, in addition to RB indices, the pre-configured candidate resources may include other resources, such as sequence indices and symbol indices. The aspects disclosed herein apply regardless of whether the pre-configured set of candidate resources includes only a single type of resource (e.g., only PRBs) or multiple types of resources (e.g., PRB indices, sequence indices, and symbol indices).

[0238] Figure 16 is an illustration of resource allocation and resource transfer for a physical uplink control channel according to some aspects. More specifically, Figure 16 An exemplary communication scheme 1600 for avoiding PUCCH resource collisions between UEs 1602, 1604, 1610, and 1612 is shown. Figure 16 In the example, it is assumed that UE#1 to UE#4 are instructed via DCI to transmit their PUCCHs on RB#1c, RB#2b, RB#3d, and RB#4d, respectively. Since the RB selection for the corresponding UE may also consider the scheduling of data and control channels for UEs other than UE#1 to UE#4, it may happen that the RBs indicated for PUCCH transmission may overlap between UEs. For example, and as Figure 16 As shown, PUCCH transmissions (1606) on RB#1c and RB#2b for UE#1 and UE#2 will collide over a portion of the frequency region. Additionally, PUCCH transmissions (1614) on RB#3d and RB#4d for UE#3 and UE#4 will collide over a portion of the frequency region.

[0239] In some aspects, to avoid resource conflicts and reduce the burden on the gNB scheduler to select non-conflicting resources for each UE to transmit PUCCH, an additional scheme may be employed to shift the RBs used for a UE's PUCCH transmission to RBs that do not conflict with PUCCH transmissions from other UEs. In one aspect, the DL CCE used by the PDCCH carrying DCI for the corresponding UE may be used to provide an offset for shifting the RBs based on the following formula:

[0240] RB_{idx,PUCCH}=RB_{idx,explicit}+CCE_{idx,start}, where RB_{idx,explicit} is the index of the RB indicated (selected) by the DCI for PUCCH transmission of the UE among the pre-configured candidate RBs, CCE_{idx,start} is the index of the starting CCE resource used to carry the DCI for the UE, and RB_{idx,PUCCH} is the index of the RB actually used for PUCCH transmission due to shifting.

[0241] For example and Figure 16 As shown, RB#2b' (1608) for UE#2 can be obtained by adding the index of the starting CCE for the UE's PDCCH as an offset to RB#2b. The index of the ending CCE for the PDCCH can be used in place of CCE_{idx, start} in the above formula, and this variation can be similarly applied to the scheme disclosed hereafter. Similarly, the asset can be applied to RB#4d (1614) to obtain a new non-colliding RB for PUCCH transmission by UE 1612, namely RB#4d' (1616).

[0242] In some aspects, to relax the restrictions on selecting CCEs for a UE, a modulo operation may be applied to the CCE index as follows:

[0243] RB_{idx,PUCCH}=RB_{idx,explicit}+modulo(CCE_{idx,start},K), where K is a constant that can be fixed or configured through L1 / L2 signaling or higher layer signaling via NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling. Due to the modulo operation, different CCE indices can result in the same offset value, and the gNB can flexibly select CCE resources for PDCCH transmission for each UE, which is particularly useful when many UEs are scheduled in a timeslot.

[0244] In some aspects, a modulo operation may be applied to the entire formula as shown below to enable shifting in a wraparound manner within the UL bandwidth:

[0245] RB_{idx,PUCCH}=modulo(RB_{idx,explicit}+modulo(CCE_{idx,

[0246] start},K),M),

[0247] Where M is a constant that can be fixed or configured by the L1 / L2 signaling or higher layer signaling mentioned above, or equal to the number of PRBs for a given UE that includes the UL carrier or UL bandwidth portion, which is configured within the UL carrier. Figure 16 In the example, the cyclic shift RB for UE#4, i.e., RB#4d', may be obtained by adding the index of the starting CCE of the PDCCH for the UE as an offset to RB#4d and then applying a modulo operation to the result (1616). For cyclic shift operations within the UL carrier bandwidth of the UE, M may be less than or equal to the maximum index of a PRB within the UL bandwidth of UE#4.

[0248] In some aspects, when the index of the first RB within the UL carrier of UE #4 is a non-zero value (e.g., P), this value may be added to the modulo operation as shown in the following formula:

[0249] RB_{idx,PUCCH}=modulo(RB_{idx,explicit}+modulo(CCE_{idx,

[0250] start},K),M)+P.

[0251] In some aspects, P may be a parameter configured in a CORESET-specific manner or an index of the first RB for a UL BWP, or a combination of both.

[0252] In some aspects, indices of other types of PDCCH resources, such as the CORESET and PRB used for the corresponding PDCCH transmission, may be used instead of the CCE index in the preceding formula.

[0253] In some aspects, in the case of NR PUCCH formats 0, 1, 2, 3, and 4, a constant amplitude zero autocorrelation (CAZAC) sequence and / or an orthogonal cover code (OCC) may include a PUCCH resource. By applying different cyclic shifts of the sequence and / or OCC between UEs, PUCCHs from different UEs may be multiplexed on the same RB. The aforementioned scheme of providing an offset to a PUCCH resource according to the index of the PDCCH resource may be applied to cyclic shift indices, OCC indices, starting symbol indices, and other types of PUCCH resources. That is, for all the above formulas, the RB index may be replaced with an index corresponding to a cyclic shift, OCC, or starting symbol, or any corresponding PUCCH resource, as provided below as an example of a cyclic shift index:

[0254] CS_{idx,PUCCH}=modulo(CS_{idx,explicit}+modulo(CCE_{idx,

[0255] start},K),M),

[0256] Where CS_{idx,explicit} is the index of the cyclic shift indicated (selected) by the DCI for the PUCCH transmission of the UE in the pre-configured candidate cyclic shift values, CCE_{idx,start} is the index of the starting CCE resource of the PDCCH for carrying the DCI for the UE, and CS_{idx,PUCCH} is the index of the cyclic shift of the sequence, which is used for PUCCH transmission as a result of the shift. In this case, M can be determined considering the range of cyclic shift values, which is 12 when the sequence length is 12.

[0257] In some aspects, a parameter may be specified that combines one or more of the starting RB index, the starting CS index, and the OCC index. Furthermore, the aforementioned techniques may be directly applied to determine the value of this parameter, as shown in the following formula (the other formulas provided above may also be similarly extended for combined resource indexes):

[0258] n_{idx,PUCCH}=n_{idx,explicit}+modulo(CCE_{idx,start},K), where n_{idx,PUCCH} is a resource index for a combination of one or more of the starting RB index, starting CS index, OCC index, and / or other PUCCH resources. Based on this parameter, the starting RB index, starting CS index, and / or OCC index may be derived accordingly. For example, the following formula may be used: n_{idx,PUCCH}=c0*RB_{idx,PUCCH}+c1*CS_{idx,PUCCH}+c2*OCC_{idx,PUCCH}, where c0, c1, and c2 are constants that may be predefined in the 5G-NR specification, and OCC_{idx,PUCCH} is the index of the OCC actually used for PUCCH transmission. In some aspects, a modulo operation may be applied to determine the starting RB index, starting CS index, and / or OCC index to ensure that the starting RB index is within the configured UL BWP, the starting CS index is within the maximum number of CSs, and the OCC index is within the maximum number of OCCs.

[0259] In some aspects, the techniques disclosed herein may be applied to all PUCCH formats or some PUCCH formats, such as NRPUCCH formats 0 and 2, with which more UEs can be scheduled than with other formats and multiple UEs can be multiplexed on the same PRB. In addition, the aforementioned techniques may be applicable to situations when the PUCCH resource set configuration is not available at the UE from RRC signaling. Specifically, the exact value in the above n_{idx,PUCCH} formula may be indicated by the DCI from a set of values ​​configured, for example, by NR RMSI. In addition, the aforementioned techniques may be applied to situations where a single resource set is configured or indicated to the UE by higher layer or L1 signaling, without the need to pre-configure a candidate set of resources.

[0260] Figure 17 Generally, a flow chart illustrating exemplary functions according to some aspects that may be performed in conjunction with PUCCH communications in a wireless architecture is shown. Figure 17 , exemplary method 1700 may begin at operation 1702, in which a processing circuit of a UE decodes physical uplink control channel (PUCCH) configuration information received from a next generation Node B (gNB). The configuration information may include a cell-specific base sequence hopping pattern. At operation 1704, a PUCCH base sequence may be selected from a plurality of available PUCCH base sequences based on the cell-specific base sequence hopping pattern and based on uplink control information available at the UE. At operation 1706, a cyclic shift may be applied to the PUCCH base sequence to generate a cyclic shifted PUCCH sequence. At operation 1708, the cyclic shifted PUCCH sequence may be encoded for transmission to a gNB (e.g., 111) using a PUCCH physical resource. The cyclic shifted PUCCH sequence may be configured to carry UCI and may be code division multiplexed (CDM) with at least one other cyclic shifted PUCCH sequence within the PUCCH physical resource (e.g., as combined with Figure 10 and Figure 11 shown and discussed).

[0261] Figure 18 Generally, a flow chart illustrating example functions that may be performed in conjunction with resource allocation and indication for PUCCH in a wireless architecture is shown in accordance with some aspects. Figure 18 Example method 1800 may begin at operation 1802, where configuration information including a pre-configured candidate set of physical uplink control channel (PUCCH) resources may be decoded. For example, UE 101 may receive information regarding the pre-configured candidate set of PUCCH resources, the resources including one or more of: at least one index of a resource block resource, a cyclic shift index, and an OCC index, and the starting symbol index is higher layer signaling, such as RRC signaling.

[0262] At operation 1804, downlink control information (DCI) signaling is decoded, wherein the DCI signaling includes a PUCCH resource indicator for selecting a PUCCH resource set from a pre-configured candidate set. More specifically, the UE 101 may be configured to receive an explicit indication via a PDCCH as to which of the candidate sets is used for the corresponding PUCCH transmission. At operation 1806, an offset may be determined based on a resource index of a physical downlink control channel (PDCCH) resource used to transmit the DCI signaling. More specifically, the UE 101 may implicitly obtain or determine an additional offset from a resource index for the corresponding PDCCH information (such as a CCE, CORESET, and PRB index associated with the PDCCH transmission) to adjust the indicated resource index.

[0263] At operation 1808, uplink control information (UCI) is encoded for transmission on a PUCCH resource from the selected PUCCH resource set, wherein the index of the PUCCH resource is based on the PUCCH resource indicator and the determined offset. More specifically, the UE 101 may apply the offset to the PUCCH resource index explicitly indicated by RRC and / or DCI signaling, and may calculate the index of the resource to be used for PUCCH transmission. The UE may then transmit the PUCCH on the adjusted PUCCH resource.

[0264] Figure 19 A block diagram of a communication device, such as an evolved Node B (eNB), a next-generation Node B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), is shown in accordance with some aspects. In alternative aspects, the communication device 1900 can operate as a standalone device or can be connected (e.g., networked) to other communication devices.

[0265] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of device 1900, the tangible entity including hardware (e.g., simple circuits, gates, logic components, etc.). The relationship between circuit components can change flexibly over time. The circuit includes components that can perform specified operations when operated (individually or in combination). In one example, the hardware of the circuit can be invariably designed to perform a specific operation (e.g., hard-wired). In one example, the hardware of the circuit can include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) to encode instructions for a specific operation, the physical components including a machine-readable medium that is physically modified (e.g., magnetically, electrically, or removably placed invariant aggregate particles).

[0266] When the physical components are connected, the basic electrical characteristics of the hardware components change, such as from an insulator to a conductor, or vice versa. The instructions enable embedded hardware (e.g., an execution unit or a loading mechanism) to create circuit components in the hardware via variable connections to perform certain portions of specific operations during operation. Thus, in one example, the machine-readable medium element is part of the circuit, or is communicatively coupled to other components of the circuit when the device is operating. In one example, any of the physical components can be used in more than one component of more than one circuit. For example, during operation, an execution unit can be used in a first circuit of a first circuit system at one point in time and reused by a second circuit in the first circuit system, or reused by a third circuit in the second circuit system, at a different time. The following are additional examples of these components relative to device 1900.

[0267] In some aspects, device 1900 can operate as a standalone device or can be connected (e.g., networked) to other devices. In a networked deployment, communication device 1900 can operate as a server communication device, a client communication device, or both in a server-client network environment. In one example, communication device 1900 can act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. Communication device 1900 can be a UE, an eNB, a PC, a tablet, a STB, a PDA, a mobile phone, a smartphone, a web appliance, a network router, a switch, or a bridge, or any communication device capable of executing (sequentially or otherwise) an instruction specifying an action to be taken by the communication device. In addition, although only one communication device is shown, the term "communication device" should also be construed to include any collection of communication devices that individually or collectively execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein (such as cloud computing software as a service (SaaS)) and other computer cluster configurations.

[0268] Examples as described herein may include a logical unit or multiple components, modules or mechanisms, or may operate on a logical unit or multiple components, modules or mechanisms. A module is a tangible entity (e.g., hardware) that can perform a specified operation and can be configured or arranged in a certain way. In one example, a circuit can be arranged as a module in a specified manner (e.g., internally or relative to an external entity such as other circuits). In one example, all or part of one or more computer systems (e.g., independent computer systems, client computer systems or server computer systems) or one or more hardware processors can be configured by firmware or software (e.g., instructions, application parts or applications) to operate to perform a module of a specified operation. In one example, the software may reside on a communication device readable medium. In one example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operation.

[0269] Thus, the term "module" should be understood to encompass a tangible entity, i.e., an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any of the operations described herein. Considering an example where modules are temporarily configured, each module need not be instantiated at any one time. For example, if the modules include a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as corresponding different modules at different times. The software may configure the hardware processor accordingly, for example, to constitute a particular module at one instance in time and to constitute a different module at a different instance in time.

[0270] The communication device (e.g., UE) 1900 may include a hardware processor 1902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1904, a static memory 1906, and a mass storage device 1907 (e.g., a hard disk, a tape drive, a flash memory, other block or storage device), some or all of which may be in communication with each other via an interconnection link (e.g., a bus) 1908.

[0271] The communication device 1900 may also include a display device 1910, an alphanumeric input device 1912 (e.g., a keyboard), and a user interface (UI) navigation device 1914 (e.g., a mouse). In one example, the display device 1910, the input device 1912, and the UI navigation device 1914 may be a touch screen display. The communication device 1900 may further include a signal generating device 1918 (e.g., a speaker), a network interface device 1920, and one or more sensors 1921, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 1900 may include an output controller 1928, such as a serial (e.g., universal serial bus (USB)) connection, a parallel connection, other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0272] The storage device 1907 may include a communication device-readable medium 1922 on which is stored one or more sets of data structures or instructions 1924 (e.g., software) embodied or utilized by any one or more of the techniques or functionality described herein. In some aspects, the processor 1902, main memory 1904, static memory 1906, and / or registers of the mass storage 1907 may (in whole or at least in part) be or include the device-readable medium 1922 on which is stored one or more sets of data structures or instructions 1924 embodied or utilized by any one or more of the techniques or functionality described herein. In one example, one or any combination of the hardware processor 1902, main memory 1904, static memory 1906, or mass storage 1916 may constitute the device-readable medium 1922.

[0273] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." Although the communication device-readable medium 1922 is shown as a single medium, the term "communication device-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 1924.

[0274] The term "communication device-readable medium" may include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 1924) for execution by the communication device 1900 and causing the communication device 1900 to perform any one or more of the techniques disclosed herein, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of communication device-readable media may include solid-state memory, as well as optical and magnetic media. Specific examples of communication device-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device-readable medium may include non-transitory communication device-readable media. In some examples, the communication device-readable medium may include communication device-readable media that is not a transient propagating signal.

[0275] The instructions 1924 may also be transmitted or received in a communication network 1926 via the network interface device 1920 using a transmission medium, using any of a number of transmission protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Exemplary communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of protocols known as The IEEE 802.16 series of standards is called ), IEEE 802.15.4 series of standards, Long Term Evolution (LTE) series of standards, Universal Mobile Telecommunications System (UMTS) series of standards, peer-to-peer (P2P) networks, and the like. In one example, the network interface device 1920 may include one or more physical jacks (e.g., Ethernet, coaxial cable, or telephone jacks) or one or more antennas to connect to the communication network 1926. In one example, the network interface device 1920 may include multiple antennas to perform wireless communications using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) technology. In some examples, the network interface device 1920 may perform wireless communications using multi-user MIMO technology.

[0276] The term "transmission medium" should be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 1900, and includes digital or analog communication signals or other intangible media to facilitate communication of such software. In this regard, in the context of this disclosure, a transmission medium is a device-readable medium.

[0277] Additional Notes and Examples :

[0278] Example 1 is an apparatus of a next generation Node B (gNB), the apparatus comprising: a processing circuit configured to: encode a base sequence hopping pattern for transmission within a cell of the gNB; decode physical uplink control channel (PUCCH) information, wherein the PUCCH information comprises long duration PUCCH information and short duration PUCCH information multiplexed within the same physical resources, and wherein the long duration PUCCH information and the short duration PUCCH information are associated with a base sequence selected from a plurality of available base sequences using the base sequence hopping pattern; and determine uplink control information (UCI) based on the short duration PUCCH information and the long duration PUCCH information; and a memory coupled to the processing circuit, the memory configured to store the base sequence hopping pattern.

[0279] In Example 2, the subject matter of Example 1 includes, wherein the long duration PUCCH information is received from a first user equipment (UE) within the cell, and the short duration PUCCH information is received from a second UE within the cell.

[0280] In Example 3, the subject matter of Examples 1-2 includes, wherein the base sequence hopping pattern is configured to vary on one or both of a symbol basis and a slot basis.

[0281] In Example 4, the subject matter of Examples 1 to 3 includes wherein the processing circuit is further configured to: encode a cyclic shift hopping pattern for transmission within the cell, the cyclic shift hopping pattern being used to further randomize a PUCCH sequence.

[0282] In Example 5, the subject matter of Example 4 includes wherein the short duration PUCCH information is associated with a first base sequence among a plurality of base sequences and the long duration PUCCH information is associated with a second base sequence among a plurality of base sequences, the first base sequence and the second base sequence being randomized by a cyclic shift hopping pattern.

[0283] In Example 6, the subject matter of Examples 4 to 5 includes, wherein the cyclic shift hopping pattern is based on one or more of: a physical cell ID of the cell; a virtual cell ID of the cell; a symbol index of a PUCCH resource; and a time slot index of a PUCCH resource.

[0284] In Example 7, the subject matter of Examples 1 to 6 includes, wherein the long duration PUCCH information and the short duration PUCCH information are code division multiplexed (CDM) within the same physical resources.

[0285] In Example 8, the subject matter described in Example 7 includes, wherein the physical resource is a time slot comprising 7 or 14 symbols, and wherein the long duration PUCCH information and the short duration PUCCH information are code division multiplexed within one or two symbols of the symbols of the time slot.

[0286] In Example 9, the subject matter of Examples 1 to 8 includes transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry.

[0287] Example 10 is an apparatus of a user equipment (UE), the apparatus comprising: a processing circuit, wherein, to configure the UE for transmitting uplink control information (UCI), the processing circuit is configured to: decode physical uplink control channel (PUCCH) configuration information received from a next generation node B (gNB), the configuration information comprising a cell-specific base sequence hopping pattern; select a PUCCH base sequence from a plurality of available PUCCH base sequences based on the cell-specific base sequence hopping pattern and the UCI information; apply a cyclic shift to the PUCCH base sequence to generate a cyclic shifted PUCCH sequence; and encode the cyclic shifted PUCCH sequence for transmission to the gNB using a PUCCH physical resource, wherein the cyclic shifted PUCCH sequence carries the UCI and is code division multiplexed (CDM) with at least another cyclic shifted PUCCH sequence within the PUCCH physical resource; and a memory coupled to the processing circuit, the memory being configured to store the cell-specific base sequence hopping pattern.

[0288] In Example 11, the subject matter of Example 10 includes wherein the PUCCH configuration information further includes a cyclic shift hopping pattern, and the processing circuit is further configured to: apply a cyclic shift to a PUCCH base sequence based on the cyclic shift hopping pattern to generate a cyclic shifted PUCCH sequence.

[0289] In Example 12, the subject matter of Example 11 includes, wherein the cyclic shift hopping pattern is based on one or more of: a physical cell ID of a cell of the gNB including the UE; a virtual cell ID of the cell; a symbol index of a PUCCH resource; and a time slot index of a PUCCH resource.

[0290] In Example 13, the subject matter of Examples 10 to 12 includes wherein the cyclically shifted PUCCH sequence carries one or two bits of UCI, and wherein the UCI includes one or both of hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback information and a scheduling request (SR).

[0291] In Example 14, the subject matter of Examples 10 to 13 includes wherein the cyclically shifted PUCCH sequence is a long duration PUCCH sequence, and the at least another cyclically shifted PUCCH sequence is a short duration PUCCH sequence originating from a second UE.

[0292] In Example 15, the subject matter of Examples 10 to 14 includes wherein the cyclically shifted PUCCH sequence is a short-duration PUCCH sequence, and the at least another cyclically shifted PUCCH sequence is a long-duration PUCCH sequence originating from a second UE.

[0293] In Example 16, the subject matter of Examples 10 to 15 includes, wherein the cell-specific base sequence hopping pattern is configured to vary on one or both of a symbol basis and a slot basis.

[0294] In Example 17, the subject matter of Examples 10 to 16 includes, wherein the processing circuit is further configured to: encode short-duration PUCCH information to carry one or two bits of UCI information within one or two symbols of a PUCCH physical resource, wherein the short-duration PUCCH information includes a first PUCCH sequence for PUCCH information to be transmitted in a first symbol of the two symbols, the first PUCCH sequence being generated by applying a first cyclic shift to a PUCCH base sequence.

[0295] In Example 18, the subject matter of Example 17 includes, wherein the processing circuit is further used to: decode the PUCCH configuration information to obtain a cyclic shift offset value, wherein the short duration PUCCH information includes a second PUCCH sequence for PUCCH information to be transmitted in a second symbol of the two symbols, and the second PUCCH sequence is generated by applying a first cyclic shift having an offset based on the cyclic shift offset value to a PUCCH base sequence.

[0296] In Example 19, the subject matter of Examples 11 to 18 includes, wherein the processing circuit is further configured to: encode the short-duration PUCCH information to carry one or two bits of UCI information within two symbols of the PUCCH physical resource, wherein the short-duration PUCCH information is based on applying a cyclic shift to a second PUCCH base sequence from a plurality of available PUCCH base sequences, the cyclic shift being based on a cyclic shift hopping pattern.

[0297] In Example 20, the subject matter of Example 19 includes, wherein the cyclic shift hopping pattern is one or both of: a cell-specific hopping pattern; and a UE-specific hopping pattern.

[0298] In Example 21, the subject matter of Examples 10 to 20 includes, wherein the processing circuit is further configured to: decode the PUCCH configuration information to obtain a plurality of independent PUCCH resources, the plurality of independent PUCCH resources being used to transmit UCI via a short-duration PUCCH having a one-symbol duration.

[0299] In Example 22, the subject matter of Example 21 includes, wherein the UCI comprises a single bit, and the plurality of independent PUCCH resources comprises: a first PUCCH resource configured for 1-bit hybrid automatic repeat request acknowledgement (HARQ-ACK) transmission only and indicating a negative scheduling request (SR); a second PUCCH resource configured for 1-bit hybrid automatic repeat request not acknowledgement (HARQ-NACK) transmission only indicating a negative SR; a third PUCCH resource configured for simultaneous 1-bit HARQ-ACK and positive SR transmission; a fourth PUCCH resource configured for simultaneous 1-bit HARQ-NAK and positive SR transmission; and a fifth PUCCH resource configured for SR-only transmission.

[0300] In Example 23, the subject matter of Examples 21 to 22 includes, wherein the UCI includes two bits, and the multiple independent PUCCH resources include: a first set of four PUCCH resources, the first set being configured for 2-bit HARQ-only transmission and indicating negative SR, wherein the first set of four PUCCH resources is used to transmit ACK-ACK, ACK-NAK, NAK-ACK and NAK-NAK bits; a second set of three PUCCH resources, the second set being configured for 2-bit HARQ and positive SR transmission, wherein the 2-bit HARQ transmission includes at least one ACK bit consisting of one of the following: ACK-ACK transmission, ACK-NAK transmission and NAK-ACK transmission; an eighth PUCCH resource, the eighth PUCCH resource being configured for simultaneous 2-bit HARQ and positive SR transmission, wherein none of the HARQ bits is an ACK bit; and a ninth PUCCH resource, the ninth PUCCH resource being configured for SR-only transmission.

[0301] In Example 24, the subject matter of Examples 10 to 23 includes transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry.

[0302] Example 25 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions being used to configure the one or more processors to cause the UE to: decode configuration information comprising a preconfigured candidate set of physical uplink control channel (PUCCH) resources; decode downlink control information (DCI) signaling, the DCI signaling comprising a PUCCH resource indicator for selecting a PUCCH resource set from the preconfigured candidate set; determine an offset based on a resource index of a physical downlink control channel (PDCCH) resource used to transmit the DCI signaling; and encode uplink control information (UCI) for transmission on PUCCH resources from the selected PUCCH resource set, wherein the index of the PUCCH resource is based on the PUCCH resource indicator and the determined offset.

[0303] In Example 26, the subject matter of Example 25 includes, wherein the resource index of the PDCCH resource includes one of: an index of a control channel element (CCE) used for transmission of the DCI signaling; an index of a control resource set (CORESET) associated with the DCI signaling; and a PRB index of a physical resource block (PRB) used for transmission of the DCI signaling.

[0304] In Example 27, the subject matter of Examples 25 to 26 includes, wherein the instructions further cause the UE to: decode second configuration information including at least one UE-specific constant value; and determine the offset further based on the at least one UE-specific constant value.

[0305] In Example 28, the subject matter of Example 27 includes, wherein the configuration information and the second configuration information are received via higher layer signaling, wherein the higher layer signaling includes one of: minimum system information (MSI) signaling; remaining minimum system information (RMSI) signaling; other system information (OSI) signaling; and radio resource control (RRC) signaling.

[0306] In Example 29, the subject matter of Examples 27-28 includes, wherein the instructions further cause the UE to: apply the determined offset to additional PUCCH configuration information received via second configuration information and associated with the selected PUCCH resource set.

[0307] In Example 30, the subject matter of Example 29 includes, wherein the additional PUCCH configuration information includes at least one of: a starting cyclic shift index for shifting the PUCCH resources; an orthogonal cover code (OCC) index; and a combined resource index, the combined resource index including a starting PRB index, a starting cyclic shift index, and an OCC index for PUCCH transmission.

[0308] In Example 31, the subject matter of Examples 25 to 30 includes, wherein the UCI comprises one or both of hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback information and a scheduling request (SR).

[0309] Example 32 is at least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any one of Examples 1 to 31.

[0310] Example 33 is an apparatus comprising means for implementing any one of Examples 1 to 31.

[0311] Example 34 is a system for implementing any one of Examples 1 to 31.

[0312] Example 35 is a method for implementing any one of Examples 1 to 31.

[0313] Although an aspect has been described with reference to specific exemplary aspects, it will be apparent that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Accordingly, the description and drawings should be regarded as having illustrative and non-restrictive meanings. The drawings forming a part hereof show specific aspects of the practical subject matter in an illustrative and non-restrictive manner. The aspects shown are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other aspects may be utilized and derived from this disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, this specific embodiment has no restrictive meaning, and the scope of the various aspects is limited only by the appended claims and the full scope of equivalents to which such claims are authorized.

[0314] Such aspects of the subject matter of the present invention may be referred to herein individually and / or collectively, solely for convenience, and are not intended to voluntarily limit the scope of this patent application to any single aspect or inventive concept if more than one is actually disclosed. Thus, although specific aspects are shown and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the specific aspects shown. This disclosure is intended to cover any and all modifications or variations of various aspects. Combinations of the above aspects and other aspects not specifically described herein will be apparent to those skilled in the art upon reviewing the above description.

[0315] An abstract of the specification of the present invention is provided to allow the reader to quickly ascertain the nature of the technical disclosure. The abstract is provided with the understanding that the technical disclosure will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the above detailed description, it can be seen that various features are concentrated in a single aspect for the purpose of simplifying the disclosure. The present method disclosed should not be interpreted as reflecting an intention that the claimed aspects require more features than are expressly recited in each claim. On the contrary, as reflected in the following claims, the inventive subject matter lies in less than all the features of a single disclosed aspect. Accordingly, the following claims are hereby incorporated into the detailed description, with each claim standing independently as a separate aspect.

Claims

1. A method for wireless communication, comprising: receiving configuration information from a base station, wherein the configuration information indicates a physical uplink control channel (PUCCH) configuration, wherein the PUCCH configuration includes a plurality of physical resource blocks (PRBs) and 12 cyclic shifts per PRB, wherein a code division multiplexing capacity using cyclic shifts within a PRB in the plurality of PRBs is 3; determining a PUCCH resource, wherein the PUCCH resource comprises a PRB and a cyclic shift, wherein the PUCCH resource depends on whether positive or negative hybrid automatic repeat request (HARQ) acknowledgment information is to be transmitted and whether positive or negative scheduling request (SR) information is to be transmitted; Applying the cyclic shift to a PUCCH base sequence to generate a cyclically shifted PUCCH sequence; and The cyclically shifted PUCCH sequence is encoded using the PUCCH resource for transmission to the base station.

2. The method of claim 1, wherein the duration of the PUCCH configuration comprises two symbols.

3. The method of claim 1, wherein the PUCCH transmission includes 2-bit HARQ acknowledgment information.

4. The method of claim 1, wherein the PUCCH transmission includes 2 bits of HARQ acknowledgement and scheduling request information.

5. An apparatus for wireless communication, comprising a processor, wherein the processor is configured to enable a user equipment (UE) to perform the method according to any one of claims 1 to 4. The apparatus of claim 5 , further comprising a radio operatively coupled to the processor.

7. A computer-readable storage medium storing instructions, wherein the instructions, when executed by one or more processors, cause a user equipment (UE) to perform the method according to any one of claims 1 to 4.

8. A method for wireless communication, comprising: Transmitting configuration information to a user equipment (UE), wherein the configuration information indicates a physical uplink control channel (PUCCH) configuration, wherein the PUCCH configuration includes a plurality of physical resource blocks (PRBs) and 12 cyclic shifts per PRB, wherein a code division multiplexing capacity using cyclic shifts within a PRB in the plurality of PRBs is 3; as well as A PUCCH transmission including PUCCH information is received from the UE using a PUCCH resource including a cyclic shift and a PRB, wherein the PUCCH resource depends on whether positive or negative hybrid automatic repeat request (HARQ) acknowledgment information is to be transmitted and whether positive or negative scheduling request (SR) information is to be transmitted, wherein the cyclic shift is applied to a PUCCH base sequence to generate a cyclically shifted PUCCH sequence for the PUCCH transmission.

9. The method of claim 8, wherein the duration of the PUCCH configuration comprises two symbols.

10. The method of claim 8, wherein the PUCCH transmission includes 2-bit HARQ acknowledgment information.

11. The method of claim 8, wherein the PUCCH transmission includes 2 bits of HARQ acknowledgement and scheduling request information.

12. An apparatus for wireless communication, comprising a processor, wherein the processor is configured to cause a base station to perform the method according to any one of claims 8 to 11.

Images