Apparatus and method for uplink control signaling in multi-transmitter receiver operation of new radios, and design of demodulation reference signal.
By adopting an uplink control signaling and demodulation reference signal design with multiple transmission and reception points in the new radio system, the problems of signaling complexity and low efficiency were solved, and the efficiency and flexibility of signaling were improved, meeting the needs of multiple objectives and services.
Patent Information
- Application Number
- CN202310394400.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-10-02
- Filing Date
- 2018-09-10
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2038-09-10
AI Technical Summary
Existing wireless communication systems, especially in new radio systems, suffer from complexity and inefficiency in the design of uplink control signaling and demodulation reference signals when operating with multiple transmission and reception points, making it difficult to meet the needs of multi-dimensional objectives and services.
The design employs uplink control signaling devices and demodulation reference signals in multi-transmission receiver point operation. By scheduling multiple uplink channels to carry uplink control information, and utilizing orthogonal overlay codes and frequency priority mapping techniques, signal transmission is optimized, thereby improving signaling efficiency.
It improves the signaling efficiency and flexibility of wireless communication systems in multi-transmitter/receiver operation, meeting the multi-dimensional objectives and service requirements of new radio systems.
Smart Images

Figure CN116405079B_ABST
Abstract
Description
[0001] Priority requirements
[0002] This application is a divisional application of the invention patent application with international application number PCT / CN2018 / 104847, international application date of September 10, 2018, entered the Chinese national phase on March 5, 2020, Chinese national application number 201880057797.5, entitled "Apparatus and method for uplink control signaling in multi-transmission receiving point operation of a new radio and design of demodulation reference signal".
[0003] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 556,959, filed September 11, 2017, entitled “UPLINK CONTROL SIGNALING INMULTI-TRANSMISSION RECEPTION POINT OPERATION FOR NEW RADIO”, and U.S. Provisional Patent Application Serial No. 62 / 567,178, filed October 2, 2017, entitled “DEMODULATION REFERENCE SIGNAL DESIGN FOR SHORT PHYSICAL UPLINK CONTROL CHANNEL WITH MORE THAN 2BITS UPLINK CONTROL INFORMATION”, the entire contents of which are incorporated herein by reference. Technical Field
[0004] This disclosure generally relates to the field of wireless communications, and more specifically to techniques that may be employed for the design of uplink control signaling for new radios (NR) and demodulation reference signals for short physical uplink control channels (PUCCH). Background Technology
[0005] Mobile communications have evolved from early voice systems to today's highly complex integrated communication platforms. Next-generation wireless communication systems, fifth-generation (5G) or New Radio (NR), will provide information access and data sharing anytime, anywhere for a wide range of users and applications. NR promises to be a unified network / system that can accommodate vastly different performance dimensions and services, sometimes even conflicting ones. These diverse, multi-dimensional goals of NR are driven by different services and applications. Typically, NR will evolve from 3GPP (3rd Generation Partnership Project) Advanced LTE (Long Term Evolution), with other potential New Radio Access Technologies (RATs), enriching people's lives with better, simpler, and seamless wireless connectivity solutions. NR will enable all content connected wirelessly and deliver fast, rich content and services. Attached Figure Description
[0006] Embodiments of the present disclosure will be readily understood from the following detailed description with reference to the accompanying drawings, which generally illustrate various features or embodiments of the disclosure by way of example rather than limitation. The same reference numerals may be used to identify the same or similar elements in different drawings. Flowcharts and figures provided in the process are provided for clear illustration of steps or operations and do not necessarily indicate a particular order or sequence of steps or operations.
[0007] Figure 1 The illustration shows an example architecture of a network system according to some embodiments.
[0008] Figure 2 The illustration shows example components of a device according to some embodiments.
[0009] Figure 3 An example interface of a baseband circuit system according to some embodiments is illustrated.
[0010] Figure 4 This is a diagram of a control plane protocol stack according to some embodiments.
[0011] Figure 5 This is a diagram of a user plane protocol stack according to some embodiments.
[0012] Figure 6 This is a block diagram illustrating components according to some embodiments that can read instructions from a machine-readable or computer-readable medium and implement one or more embodiments discussed herein.
[0013] Figure 7 This is a diagram illustrating an example of multiple transmit receiver points (multiple TRPs) operation according to some embodiments.
[0014] Figure 8 The illustration shows an example of scheduling multiple uplink channels to carry uplink control information (UCI) according to some embodiments.
[0015] Figure 9 The illustration shows another example of scheduling multiple uplink channels to carry UCI according to some embodiments.
[0016] Figure 10 An example of combined UCI for multiple TRPs is illustrated according to some embodiments.
[0017] Figure 11 The illustration shows an example of scheduling a single uplink channel to carry a combined UCI for multiple TRPs, according to some embodiments.
[0018] Figure 12The illustration depicts an example of scheduling multiple uplink channels to carry a combined UCI for multiple TRPs, according to some embodiments.
[0019] Figure 13 An example of an uplink channel for scheduling according to some embodiments is illustrated.
[0020] Figure 14 Another example of an uplink channel for scheduling according to some embodiments is illustrated.
[0021] Figure 15 This is a flowchart illustrating an example method that can be employed at the UE to facilitate multiple TRP operations according to some embodiments.
[0022] Figure 16 This is a block diagram illustrating an example of a network node for facilitating multiple TRP operations according to some embodiments.
[0023] Figure 17 This is a diagram illustrating Example 1700 of a short NR PUCCH according to some embodiments.
[0024] Figure 18 This is a diagram illustrating an example 1800 of a long NR PUCCH according to some embodiments.
[0025] Figure 19 This is a diagram illustrating Example 1900 of a demodulation reference signal (DM-RS) mode for a short NR PUCCH with more than 2 bits of UCI, according to some embodiments.
[0026] Figure 20 This is a flowchart illustrating an example method 2000 that can be employed at the UE to facilitate the generation of DM-RS modes according to some embodiments.
[0027] Figure 21 This is a diagram illustrating an example of frequency-priority mapping of DM-RS sequences according to some embodiments.
[0028] Figure 22 This is a diagram illustrating an example of time-priority mapping of DM-RS sequences according to some embodiments.
[0029] Figure 23 The illustration shows an example of applying an orthogonal overlay code (OCC) to a DM-RS RE within a physical resource block (PRB).
[0030] Figure 24 The illustration shows an example of applying OCC to a DM-RS RE within two PRBs. Detailed Implementation
[0031] In the following description, numerous specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of explanation and not limitation in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art, who will benefit from this disclosure, that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some cases, descriptions of known devices, circuits, and processes have been omitted to avoid unnecessary detail that would obscure the description of the various embodiments.
[0032] Throughout this disclosure, references to phrases such as "an embodiment," "embodiment," "an example," "example," etc., indicate that the described embodiment may include specific features, structures, steps, materials, or characteristics; however, each embodiment may not necessarily include specific features, structures, steps, materials, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. For the purposes of this disclosure, the phrase "A and / or B" means (A) or (B) or (A and B).
[0033] The embodiments described herein can be implemented into the system using any appropriately configured hardware and / or software. Figure 1 An example architecture of a network system 100 according to some embodiments is illustrated. System 100 is shown as including user equipment (UE) 101 and UE 102. UE 101 and 102 are illustrated 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), pager, laptop computer, desktop computer, wireless phone, or any computing device including a wireless communication interface.
[0034] In some embodiments, either UE 101 or 102 may include an Internet of Things (IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connectivity. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-class communication (MTC) to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity-based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connectivity. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.
[0035] UEs 101 and 102 can be configured to connect to, for example, a radio access network (RAN) 110, such as a communication-ground coupling RAN 110, which can be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. UEs 101 and 102 utilize connections 103 and 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 illustrated as air interfaces for implementing communication coupling and can be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, New Radio (NR) protocol, etc.
[0036] In this embodiment, UEs 101 and 102 can further exchange communication data directly via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface including one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).
[0037] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 may include wireless fidelity. Router. In this example, AP 106 is shown as being connected to the Internet without being connected to the core network of the wireless system (described in further detail below).
[0038] RAN 110 may include one or more access nodes that enable connectivity between 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., cells). 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 femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).
[0039] Either RAN node 111 or 112 can terminate the air interface protocol and can be the first point of contact for UEs 101 and 102. In some embodiments, either RAN node 111 or 112 can implement various logical functions of 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.
[0040] According to some embodiments, UEs 101 and 102 can be configured to communicate with each other or with either RAN nodes 111 and 112 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various 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 or sidelink communication), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.
[0041] In some embodiments, the downlink resource grid can be used for downlink transmissions from either RAN nodes 111 and 112 to UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this may represent the minimum amount of resources currently available for allocation. These resource blocks are used to transmit several different physical downlink channels.
[0042] The Physical Downlink Shared Channel (PDSCH) can carry user data and higher-layer signaling to UEs 101 and 102. The Physical Downlink Control Channel (PDCCH) can carry information about transmission formats and resource allocation related to the PDSCH channel. It can also inform UEs 101 and 102 about transmission formats, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 102 within the cell) can be performed at either RAN node 111 or 112 based on channel quality information fed back from either UE 101 or 102. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each of UEs 101 and 102.
[0043] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above-described concept. For example, some embodiments may utilize an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as an Enhanced Resource Element Group (EREG). In some cases, an ECCE may have a different number of EREGs.
[0044] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113. In embodiments, CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 113 is divided into two parts: S1-U interface 114, which carries service data between RAN nodes 111 and 112 and serving gateway (S-GW) 122; and S1-Mobility Management Entity (MME) interface 115, which is the signaling interface between RAN nodes 111 and 112 and MME 121.
[0045] In this embodiment, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 may be functionally similar to the control plane of a legacy 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 may include a database for network users, including subscription-related information to support network entities in handling communication sessions. CN 120 may include one or more HSS 124s, depending on the number of mobile users, device capacity, network organization, etc. For example, HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location correlation, etc.
[0046] S-GW 122 can terminate the S1 interface 113 toward RAN 110 and route data packets between RAN 110 and CN 120. Additionally, S-GW 122 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.
[0047] P-GW 123 can terminate the SGi interface toward the PDN. P-GW 123 can route data packets between EPC network 123 and external networks such as a network including application server 130 (alternatively referred to as application function (AF)) via Internet Protocol (IP) interface 125. Typically, application server 130 can be an element that provides applications using IP bearer resources to the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, P-GW 123 is shown as communicatively coupled to application server 130 via IP communication interface 125. Application server 130 can 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 UEs 101 and 102 via CN 120.
[0048] P-GW 123 may further be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 126 is the policy and charging control element of CN 120. In non-roaming scenarios, a single PCRF may exist 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 service interruptions, there may be two PCRFs associated with the UE's IP-CAN session: a local PCRF (H-PCRF) within the HPLMN and a visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). PCRF 126 may be communicatively coupled to application server 130 via P-GW 123. Application server 130 may signal PCRF 126 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 126 can provide this rule to the Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Service Flow Template (TFT) and Identifier QoS Category (QCI), thereby initiating QoS and charging as specified by the application server 130.
[0049] Figure 2 The illustration shows example components of a device 200 according to some embodiments. In some embodiments, device 200 may include at least an application circuitry system 202, a baseband circuitry system 204, a radio frequency (RF) circuitry system 206, a front-end module (FEM) circuitry system 208, one or more antennas 210, and a power management circuitry system (PMC) 212 coupled together as shown. Components of the illustrated device 200 may be included in a UE or RAN node. In some embodiments, device 200 may include fewer components (e.g., the RAN node may not utilize the application circuitry system 202, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 200 may include additional components such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry systems may be included in more than one device for a cloud RAN (C-RAN) implementation).
[0050] Application circuit system 202 may include one or more application processors. For example, application circuit system 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors (multiple) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or may include memory / storage devices and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on device 200. In some embodiments, the processor of application circuit system 202 may process IP data packets received from EPC.
[0051] The baseband circuit system 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit system 204 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuit system 206 and to generate baseband signals for the transmit signal path of the RF circuit system 206. The baseband processing circuit system 204 may interface with the application circuit system 202 to generate and process baseband signals and control the operation of the RF circuit system 206. For example, in some embodiments, the baseband circuit system 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 multiple other baseband processors 204D (e.g., second-generation (2G), sixth-generation (6G), etc.) for other existing, under development, or future generations. The baseband circuitry system 204 (e.g., one or more baseband processors 204A to 204D) can handle various radio control functions, communicating with one or more radio networks via the RF circuitry system 206. In other embodiments, some or all of the functionality of the baseband processors 204A to 204D may be included in a module stored in memory 204G and executed via a central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry system of the baseband circuitry system 204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry system of the baseband circuitry system 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functionality. Embodiments of modulation / demodulation and encoder / decoder functionality are not limited to these examples, and other suitable functionality may be included in other embodiments.
[0052] In some embodiments, the baseband circuit system 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSPs 204F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuit system may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuit system 204 and the application circuit system 202 may be implemented together, for example, on a system-on-a-chip (SoC).
[0053] In some embodiments, the baseband circuit system 204 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit system 204 can support communications with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Embodiments in which the baseband circuit system 204 is configured to support radio communications with more than one radio protocol may be referred to as a multimode baseband circuit system.
[0054] RF circuitry system 206 can use modulated electromagnetic radiation through a non-solid medium to support communication with a wireless network. In various embodiments, RF circuitry system 206 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuitry system 206 may include a receive signal path that includes circuitry for down-converting RF signals received from FEM circuitry system 208 and providing baseband signals to baseband circuitry system 204. RF circuitry system 206 may also include a transmit signal path that includes circuitry for up-converting baseband signals provided by baseband circuitry system 204 and providing RF output signals to FEM circuitry system 208 for transmission.
[0055] In some embodiments, the receive signal path of RF circuit system 206 may include mixer circuit system 206A, amplifier circuit system 206B, and filter circuit system 206C. In some embodiments, the transmit signal path of RF circuit system 206 may include filter circuit system 206C and mixer circuit system 206A. RF circuit system 206 may also include synthesizer circuit system 206D to synthesize the frequency used by mixer circuit system 206A in both the receive and transmit signal paths. In some embodiments, mixer circuit system 206A in the receive signal path may be configured to down-convert the RF signal received from FEM circuit system 208 based on the synthesized frequency provided by synthesizer circuit system 206D. Amplifier circuit system 206B may be configured to amplify the down-converted signal, and filter circuit system 206C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit system 204 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, the mixer circuitry system 206A for the received signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.
[0056] In some embodiments, the mixer circuitry 206A of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuitry 206D to generate an RF output signal for the FEM circuitry 208. The baseband signal can be provided by the baseband circuitry 204 and can be filtered by the filter circuitry 206C.
[0057] In some embodiments, the mixer circuit system 206A for the receive signal path and the mixer circuit system 206A for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit system 206A for the receive signal path and the mixer circuit system 206A for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit system 206A for the receive signal path and the mixer circuit system 206A for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit system 206A for the receive signal path and the mixer circuit system 206A for the transmit signal path may be configured for superheterodyne operation.
[0058] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit system 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuit systems, and the baseband circuit system 204 may include a digital baseband interface for communicating with the RF circuit system 206. In some dual-mode embodiments, separate radio IC circuit systems may be provided to process the signal for each spectrum, although the scope of the embodiments is not limited in this respect.
[0059] In some embodiments, the synthesizer circuit system 206D may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit system 206D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.
[0060] Synthesizer circuitry 206D can be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuitry 206A of RF circuitry 206. In some embodiments, synthesizer circuitry 206D may be a fractional N / N+1 synthesizer.
[0061] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuitry 204 or the application processor 202 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 202.
[0062] The synthesizer circuitry system 206D of the RF circuitry system 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, 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 embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.
[0063] In some embodiments, the synthesizer circuitry 206D can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with a quadrature generator and frequency divider circuitry to generate multiple signals at the carrier frequency that have multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (f LO In some embodiments, the RF circuit system 206 may include an IQ / polarity converter.
[0064] FEM circuitry 208 may include a receive signal path that includes circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 206 for further processing. FEM circuitry 208 may also include a transmit signal path that includes circuitry configured to amplify transmit signals provided by RF circuitry 206 for transmission through one or more of the one or more antennas 210. In various embodiments, amplification via the transmit or receive signal path may be performed solely in RF circuitry 206, solely in FEM 208, or in both RF circuitry 206 and FEM 208.
[0065] In some embodiments, the FEM circuitry 208 may include a TX / RX switch to switch between transmit mode operation and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include: a power amplifier (PA) to amplify the 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., through one or more of one or more antennas 210).
[0066] In some embodiments, the PMC 212 can manage the power supplied to the baseband circuitry 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 212 is typically included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.
[0067] Figure 2 PMC 212 is shown coupled only to baseband circuitry 204. However, in other embodiments, additionally or alternatively, PMC 212 may be coupled to other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208, and perform similar power management operations thereto.
[0068] In some embodiments, PMC 212 may control various power-saving mechanisms of device 200 or otherwise become part of various power-saving mechanisms of device 200. For example, if device 200 is in the RRC_Connected state, and is still connected to the RAN node as expected to receive services for short periods, it may enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 200 may power down for short intervals to save power.
[0069] If there is no data service activity during the extended period, device 200 can transition to the RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 200 enters a very low power state and performs paging, in which it periodically wakes up again to listen to the network, and then powers off again. Device 200 may not receive data in this state; to receive data, it must transition back to the RRC_Connected state.
[0070] Additional power-saving modes allow the device to be unavailable from the network for periods longer than the paging interval (ranging from seconds to hours). During this time, the device has no network access whatsoever and may experience a complete power outage. Any data sent during this period will incur a significant delay, which is assumed to be acceptable.
[0071] The processors of application circuit system 202 and baseband circuit system 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit system 204 can be used individually or in combination to execute Layer 3, Layer 2, or Layer 1 functionality, while the processor of application circuit system 204 can utilize data received from these layers (e.g., packet data) and further execute Layer 4 functionality (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As indicated herein, Layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As indicated herein, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As indicated herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.
[0072] Figure 3 The illustration shows an example interface of a baseband circuit system according to some embodiments. As discussed above, Figure 2 The baseband circuit system 204 may include processors 204A-204E and a memory 204G used by the processors. Each of the processors 204A-204E may respectively include a memory interface 304A-304E for sending / receiving data to / from the memory 204G.
[0073] The baseband circuit system 204 may further include one or more interfaces for communicatively coupling to other circuit systems / devices, such as a memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit system 204) and an application circuit system interface 314 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit system 204). Figure 2 The application circuit system 202 transmits / receives data interface), RF circuit system interface 316 (e.g., for sending / receiving data to / from...). Figure 2 The RF circuit system 206 is an interface for transmitting / receiving data, and the wireless hardware connection interface 318 is used for transmitting / receiving data to / from near field communication (NFC) components. Components (e.g.) (low energy) Interfaces for sending / receiving data to components and other communication components) and power management interface 320 (e.g., an interface for sending / receiving power or controlling signals to / from PMC 212).
[0074] Figure 4 This is an illustration of a control plane protocol stack according to some embodiments. In this embodiment, the control plane 400 is shown as a communication protocol stack between UE 101 (or alternatively, UE 102), RAN node 111 (or alternatively, RAN node 112) and MME 121.
[0075] PHY layer 401 can transmit or receive information used by MAC layer 402 on one or more air interfaces. PHY layer 401 can further perform link adaptive 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 (such as RRC layer 405). PHY layer 401 can further perform error detection on the transport channel, forward error correction (FEC) encoding / decoding on the transport channel, modulation / demodulation of the physical channel, interleaving, rate matching, mapping on the physical channel, and multiple-input multiple-output (MIMO) antenna processing.
[0076] MAC layer 402 can perform mapping between logical channels and transport channels, multiplexing MAC Service Data Units (SDUs) from one or more logical channels onto transport blocks (TBs) for transmission to the PHY via transport channels, demultiplexing MAC SDUs from the PHY to transport blocks (TBs) via transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), and logical channel prioritization.
[0077] RLC layer 403 can operate in multiple modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC layer 403 can perform the transmission of upper-layer protocol data units (PDUs), including error correction via Automatic Repeat Request (ARQ) for AM data transmission and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC layer 403 can also perform resegmentation of RLC data PDUs for AM data transmission, reordering of RLC data PDUs for UM and AM data transmission, detection of duplicate data for UM and AM data transmission, discarding of RLC SDUs for UM and AM data transmission, detection of protocol errors for AM data transmission, and RLC reconstruction.
[0078] PDCP layer 404 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order transmission of upper-layer PDUs during lower-layer reconstruction, eliminate duplicates of lower-layer SDUs during lower-layer reconstruction of radio bearers used to map to RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discarding, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).
[0079] The main services and functions of 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, establishment, maintenance, and release of RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, including security functions for key management, mobility between Radio Access Technologies (RATs), and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more Information Elements (IEs), which may each include separate data fields or data structures.
[0080] UE 101 and RAN node 111 can use the Uu interface (e.g., the LTE-Uu interface) to exchange control plane data via a protocol stack including PHY layer 401, MAC layer 402, RLC layer 403, PDCP layer 404 and RRC layer 405.
[0081] The Non-Access Stratum (NAS) protocol 406 forms the highest layer of the control plane between UE 101 and MME 121. NAS protocol 406 supports the mobility of UE 101 and the session management procedure for establishing and maintaining the IP connection between UE 101 and P-GW 123.
[0082] The S1 Application Protocol (S1-AP) layer 415 supports the functions of the S1 interface and includes the Basic Procedure (EP). The EP is the interaction unit between RAN node 111 and CN 120. S1-AP layer services can include two sets: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.
[0083] The Flow Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 414 can, in part, rely on the IP protocol supported by the IP layer 413 to ensure reliable transmission of signaling messages between the RAN node 111 and the MME 121. The L2 layer 412 and the L1 layer 411 can refer to the communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
[0084] RAN node 111 and MME 121 can use the S1-MME interface to exchange control plane data via a protocol stack including L1 layer 411, L2 layer 412, IP layer 413, SCTP layer 414 and S1-AP layer 415.
[0085] Figure 5 This is an illustration of a user plane protocol stack according to some embodiments. In this embodiment, user plane 500 is shown as a communication protocol stack between UE 101 (or alternatively, UE 102), RAN node 111 (or alternatively, RAN node 112), S-GW 122, and P-GW 123. User plane 500 may utilize at least some of the same protocol layers as control plane 400. For example, UE 101 and RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including PHY layer 401, MAC layer 402, RLC layer 403, and PDCP layer 404.
[0086] The General Packet Radio Service (GPRS) tunneling protocol for the user plane (GTP-U) layer 504 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be packets in any of IPv4, IPv6, or PPP formats. The UDP and IP Security (UDP / IP) layer 503 can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. RAN node 111 and S-GW 122 can utilize the S1-U interface to exchange user plane data via a protocol stack including L1 layer 411, L2 layer 412, UDP / IP layer 503, and GTP-U layer 504. S-GW 122 and P-GW 123 can utilize the S5 / S8a interface to exchange user plane data via a protocol stack including L1 layer 411, L2 layer 412, UDP / IP layer 503, and GTP-U layer 504. (See above regarding...) Figure 4 The NAS protocol discussed here supports the mobility and session management procedures of UE 101 to establish and maintain the IP connection between UE 101 and P-GW 123.
[0087] Figure 6 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 6 A graphical representation of hardware resource 600 is shown, which includes 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 bus 640. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 602 can be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 600.
[0088] 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.
[0089] The memory / storage device 620 may include main memory, disk storage devices, 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 devices, etc.
[0090] Communication resource 630 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 604 or one or more databases 606 via network 608. For example, communication resource 630 may include wired communication components (e.g., for communication via Universal Serial Bus (USB), cellular communication components, NFC components, etc.). Components (e.g., (Low energy consumption) (Components and other communication components are coupled).
[0091] Instructions 650 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 610 to perform any one or more of the methods discussed herein. Instructions 650 may reside wholly or partially within at least one of the processor 610 (e.g., within the processor's buffer memory), memory / storage device 620, or any suitable combination thereof. Furthermore, any portion of instructions 650 may be transferred from any combination of peripheral device 604 or database 606 to hardware resource 600. Thus, the memory of processor 610, memory / storage device 620, peripheral device 604, and database 606 are examples of computer-readable and machine-readable media.
[0092] For fifth-generation (5G) or new radio (NR) systems, high-frequency communication has attracted significant attention from the industry because it may offer wider bandwidth to support future integrated communication systems. Beamforming is likely to be a key technology for implementing high-frequency communication because its gain can compensate for severe path loss caused by atmospheric attenuation, improve the signal-to-noise ratio (SNR), and expand coverage area. By aligning the transmit beam from the network node to the target UE, radiated energy can be concentrated to achieve higher energy efficiency and mutual interference between the target UE and (multiple) other UEs can be suppressed.
[0093] When a UE is equipped with multiple antenna panels or antenna subarrays, the UE may be able to transmit / receive signals to / from multiple transmit / receive points (TRPs) simultaneously using different beams. This multi-TRP operation can facilitate an increase in the number of layers used for data transmission, thereby improving the overall system throughput.
[0094] Figure 7 This is a diagram illustrating an example 700 of a multi-TRP operation according to some embodiments. Although only two TRPs are shown in this example (i.e., TRP1 701 and TRP2 702), more than two TRPs may be involved in a multi-TRP operation.
[0095] In one example, two TRPs, 701 and 702, can reside in the same radio access network (RAN) node, for example, Figure 1 The macro RAN node 111 shown can be referred to as a base station (BS), node B (NB), evolved Node B (eNB), next-generation Node B (gNB), etc. For example, the TRP can be two transceivers or two remote heads (RHs) located at the base station and can be controlled or coordinated by a controller within the base station.
[0096] In another example, the two TRPs 701 and 702 can reside in two different network nodes. For example, TRP1 701 can be part of one base station, while TRP2 702 can be part of another. In this case, TRP1 and TRP2 are controlled or coordinated by their respective Base Station Controller (BSC) and / or a higher-level controller or coordinator. For example, coordination between TRPs can be performed via a suitable backhaul (e.g., fiber optic cable).
[0097] like Figure 7 As shown, the two TRPs 701 and 702 can simultaneously transmit signals to the UE (e.g., using different beams 703 and 704) using different beams 703 and 704 respectively. Figure 1 The UE 101) transmits downlink (DL) signals, or otherwise simultaneously receives uplink (UL) signals from the UE.
[0098] In this example, UE 101 may be equipped with two or more antenna panels or antenna subarrays. Therefore, UE 101 may be able to support multi-TRP operation by transmitting UL signals to different TRPs or receiving DL signals from different TRPs simultaneously using different beams.
[0099] DL signals or UL signals may include user data and / or control signaling. DL signals may be carried by one or more downlink channels, such as the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), etc. UL signals may be carried by one or more uplink channels, such as the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), etc. In the examples, the PDSCH, PDCCH, PUSCH, and PUCCH discussed in this disclosure may be the New Radio (NR) PDSCH, NR PDCCH, NR PUSCH, and NR PUCCH, respectively.
[0100] For example, the PDSCH can carry user data and / or higher-layer signaling to the UE. The PDCCH can carry information about the transmission format and resource allocation related to the PDSCH channel.
[0101] For multi-TRP operation in DL, it is possible to simultaneously access several TRPs (e.g., in different beam pair links (BPLs)). Figure 7 In TRP1 and TRP2, multiple PDSCHs are transmitted to increase the number of transport layers and data throughput. It should be noted that in New Radio (NR), the maximum number of supported NR PDCCHs that a UE may expect to receive in a single time slot based on each component carrier, corresponding to the scheduled PDSCH, is agreed to be 2.
[0102] For example, PUSCH can carry user data and / or uplink control channel (UCI) to TRP, and PUCCH can carry UCI to TRP.
[0103] According to some embodiments, UE 101 may include an interface configured to enable the UE to communicate with two or more TRPs. Furthermore, UE 101 may further include a processor configured to generate a UCI for each TRP, schedule one or more uplink channels to carry the UCI, such that the UCI is transmitted to the TRP individually or in combination via the interface, wherein the uplink channels may include NR PUCCH and / or NR PUSCH.
[0104] In the example, the UE's interface could be... Figure 3 The RF circuit system interface 316 can be configured to send / receive signals to / from the RF circuit system interface 316. Figure 2 The RF circuitry system 206 transmits / receives data. In the example, the UE's processor could be... Figure 2 and Figure 3 The central processing unit (CPU) is 204E.
[0105] UCI may include one or more of the following: scheduling request (SR), hybrid automatic repeat request (HARQ) acknowledgment / negative acknowledgment (ACK / NACK) feedback, channel state information (CSI) report (e.g., channel quality indicator (CQI)), precoding matrix indicator (PMI), CSI resource indicator (CRI), rank indicator (RI), beam-related information (e.g., L1-RSRP), etc.
[0106] According to some embodiments, the UCI carried by NR PUSCH or NR PUCCH may include HARQ ACK / NACK feedback and / or CSI reports. In an example, PUCCH may carry HARQ ACK / NACK feedback for (multiple) corresponding PDSCHs received from (multiple) TRPs, while PUSCH may carry (multiple) CQI reports to (multiple) TRPs.
[0107] Figure 8 The illustration depicts an example 800 of scheduling multiple uplink channels to carry UCI according to some embodiments. In this example 800, a UE (e.g., UE 101) can simultaneously receive two DL signals from two TRPs, for example, PDSCH_1 (or PDCCH_1) from a first TRP and PDSCH_2 (or PDCCH_2) from a second TRP. Therefore, the UE schedules two PUCCHs to carry UCI for the first TRP and UCI for the second TRP respectively, and these PUCCHs are multiplexed in a time-division multiplexing (TDM) manner, for example by occupying different symbols in the same time slot, e.g. Figure 8 The second-to-last and last symbols shown.
[0108] As a specific example, PUCCH_1 can carry the HARQ ACK / NACK feedback (from the first TRP) for the corresponding PDSCH_1 to the first TRP, while PUCCH_2 can carry the HARQ ACK / NACK feedback (from the second TRP) for the corresponding PDSCH_2 to the second TRP. Alternatively, PUCCH_1 can carry the HARQ ACK / NACK feedback to the first TRP, while PUCCH_2 can carry the CSI report to the second TRP.
[0109] It should be noted that any PUCCH discussed above can be replaced by PUSCH. It should also be noted that, although... Figure 8 This example only shows two PUCCHs, but a UE can schedule more than two uplink channels, for example, two PUCCHs and one PUSCH, as will be discussed later. Figure 13 and Figure 14It is described in detail. Moreover, the number of TRPs is not limited to two.
[0110] In addition, the processor of UE 101 (e.g., CPU 204E) can schedule multiple uplink channels according to resource allocation in the time domain, which can be configured by higher layers and / or dynamically configured by downlink control information (DCI) from TRP.
[0111] In the example, information about resource allocation in the time domain can be exchanged between TRPs in a semi-static or dynamic manner to facilitate coordination between TRPs. This information may include one or more of the following: frame index, slot index, symbol index, start symbol index, etc.
[0112] As an example, where there is some coordination between different TRPs, PUCCH and / or PUSCH carrying CSI reports for different TRPs can be multiplexed in a TDM manner. This would allow a UE with a single Tx beam or antenna port to transmit only one of the PUCCH and / or PUSCH at a given time instance.
[0113] As another example, the information can indicate the transmission location for each PUCCH, each PUCCH carrying HARQ ACK / NACK feedback for each corresponding PDSCH. For instance, in the case where a short PUCCH with a duration of one symbol is used for the transmission of HARQ ACK / NACK feedback, the different symbol indexes for each PUCCH can be configured by higher layers and / or dynamically indicated in the DCI from different TRPs.
[0114] Figure 9 The illustration depicts another example 900 of scheduling multiple uplink channels to carry UCI according to some embodiments. This example 900 is similar to... Figure 8 Example 800, in addition to multiplexing the two PUCCHs (i.e., PUCCH_1 and PUCCH_2) in a frequency division multiplexing (FDM) manner, occupies different frequency bands in one symbol.
[0115] Furthermore, the processor of UE 101 (e.g., CPU 204E) can schedule multiple uplink channels based on resource allocation in the frequency domain, which can be configured by higher layers and / or dynamically configured by DCI from TRP. The resource allocation in the frequency domain can be indicated by resource element indexes (REs) or subcarrier indexes, etc.
[0116] In the example, resource allocation in the frequency domain can be continuous based on semi-static or dynamic coordination among multiple TRPs. For example, as Figure 9As shown, PUCCH_1 and PUCCH_2 can occupy two consecutive subcarriers, or in other words, some consecutive REs. Without coordination between TRPs, two PUCCHs multiplexed in FDM mode can be mapped onto some discontinuous REs, which may be undesirable due to increased intermodulation distortion (IMD).
[0117] If the UE only supports one transmit (Tx) beam or antenna port, simultaneously transmitting two PUCCHs using two Tx beams may not be feasible. The UE's processor can select one of the two PUCCHs for transmission and discard the other PUCCH based on discarding rules or priority rules. This can be predefined in the 3GPP specification or configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling. Alternatively, the UE can discard PUCCHs based on the channel quality of different BPLs. For example, the UE can transmit a PUCCH on a BPL with better channel conditions and discard the other PUCCHs. In this example, the UE may discard PUCCHs depending on its specific implementation.
[0118] For carrier frequencies below or above 6 GHz, if the UE uses omnidirectional Tx beams for PUCCH transmission and there is some coordination among multiple TRPs, different TRPs can allocate contiguous resources for PUCCH in FDM mode. In this case, the UE may still be able to transmit multiple PUCCHs for a given time instance.
[0119] Figure 10 An example 1000 of a combined UCI for multiple TRPs is illustrated according to some embodiments. As mentioned above, the UE may include an interface (e.g., Figure 3 The RF circuit system interface 316 is configured to send / receive Figure 2 The RF circuitry system 206 transmits / receives data to enable the UE to communicate with multiple TRPs. In this case, the processor (e.g., CPU 204E) of the UE (e.g., UE 101) can generate a separate UCI for each of the multiple TRPs, and then combine the UCIs generated for each TRP into a combined UCI.
[0120] According to some embodiments, combined UCIs can be encoded in the form of bit sets, wherein each individual UCI for a TRP within a TRP can correspond to a subset of the bit set. For example, the UCI generated for TRP1 can be encoded as a first subset with N1 bits, and the UCI generated for TRP2 can be encoded as a second subset with N2 bits, where N1 and N2 are positive integers (e.g., 1, 2, ...). In other embodiments, combined UCIs can be encoded as... Figure 10 Other data structures besides the data structure shown.
[0121] It should be noted that the number of bits in each subset (e.g., N1, N2) can be indicated by higher-layer configuration and / or by downlink control information (DCI) from the TRP.
[0122] In some embodiments, the UE can combine HARQ ACK / NACK feedbacks from different TRPs for corresponding PDSCHs and transmit the combined HARQ ACK / NACK feedbacks on the PUCCH. In one example, if a single codeword is used for each PDSCH, 1 bit of HARQ ACK / NACK feedback can be fed back for each PDSCH. This means that in the case of two TRPs, N1 = 1 and N2 = 1, and the total number of bits for the combined HARQ ACK / NACK feedback (i.e., N1 + N2) is 2. In another example, if two codewords are used for each PDSCH, 2 bits of HARQ ACK / NACK feedback can be fed back for each PDSCH. This means that in the case of two TRPs, N1 = 2 and N2 = 2, and the total number of bits for the combined feedback (i.e., N1 + N2) is 4. In yet another example, if the transmission is based on a Block Code Group (CBG), the specific values of N1 and N2 can be configured by a higher layer.
[0123] In some embodiments, the UE may combine CSI reports for different TRPs and transmit the combined CSI reports on the PUSCH or PUCCH.
[0124] In some embodiments, the TRP index for the bit set is predefined in the 3GPP technical specification or configured by higher layers, for example, via RRC signaling.
[0125] In some embodiments, the resource index assigned to the downlink can be explicitly signaled in the DCI to indicate the resource allocation for PUCCH transmissions for HARQ ACK / NACK feedback and aperiodic CSI reporting. In the case of discontinuous transmission (DTX), the UE can reserve a fixed number of bits, e.g., all zeros, for combined HARQ ACK / NACK feedback with predefined values, regardless of whether the downlink allocation for the data channel to the TRP has been correctly decoded. Therefore, the gNB can easily identify the payload size of the PUCCH. The DCI can dynamically indicate the TRP index (or multiple indices) for which ACK / NACK for the PDSCH can be reported. Alternatively, the UE can only provide HARQ-ACK feedback for the configured TRP if the downlink allocation has been correctly decoded. Moreover, the bit set can include only the UCI bits intended for the TRP, for which a corresponding HARQ-ACK feedback is generated. In this case, the gNB can use blind detection to detect the possible payload size of the PUCCH.
[0126] Figure 11 The illustration depicts example 1100, according to some embodiments, of scheduling a single uplink channel to carry a combined UCI for multiple TRPs. The combined UCI has already been generated (e.g., Figure 10 After the bit set), the processor (e.g., CPU 204E) of the UE (e.g., UE 101) can schedule a single uplink channel, for example, Figure 1 A PUCCH is shown to carry the combined UCI. By means of Figure 3 RF circuit system interface 316 and Figure 2 In the RF circuit system 206, UE 101 can transmit the combined UCI to TRP via the scheduled PUCCH.
[0127] As an example (e.g., such as) Figure 11 As shown), if UE 101 supports multiple transmit (Tx) beams or antenna ports (APs) for UL transmission, the combined UCI can be transmitted simultaneously to each TRP via a scheduled PUCCH, for example, to TRP1 701 and TRP2 702.
[0128] As another example, a combined UCI can be transmitted to one of the TRPs (e.g., TRP1701) via a scheduled PUCCH, and then the combined UCI can be forwarded to the remaining TRPs (e.g., TRP2702). The forwarding operation can be performed with the help of some close coordination among multiple TRPs, for example, via an ideal backhaul.
[0129] For example, a UE can transmit HARQ ACK / NACK feedback for a combination of corresponding PDSCHs (e.g., PDSCH_1 and PDSCH_2) from multiple TRPs on a single PUCCH. If the UE only supports one Tx beam or antenna port, the UE can perform beam scanning on a PUCCH carrying combined HARQ ACK / NACK feedback to multiple TRPs.
[0130] For example, the UE can transmit combined CSI reports to all TRPs. If the UE only supports one Tx beam or antenna port, the UE can perform beam scanning to transmit combined CSI reports on the PUCCH or PUSCH.
[0131] Figure 12 The illustration depicts an example 1200 of scheduling multiple uplink channels to carry a combined UCI for multiple TRPs, according to some embodiments. The combined UCI has already been generated (e.g., Figure 10 After the bit set), the processor (e.g., CPU 204E) of the UE (e.g., UE 101) can schedule more than one uplink channel, for example, carrying PUCCH_1 and PUCCH_2 of combined UCI respectively, such as Figure 12 As shown.
[0132] As an example, if UE 101 supports multiple transmit (Tx) beams or antenna ports (APs) for UL transmission, combined UCIs can be transmitted simultaneously to two TRPs, such as TRP1 701 and TRP2 702, via two PUCCHs (e.g., PUCCH_1 and PUCCH_2). Furthermore, if the UE supports two Tx beams or APs, the two PUCCHs can be multiplexed in either TDM or FDM mode.
[0133] As another example, if the UE only supports one Tx beam or antenna port, the combined UCI can be transmitted to each TRP via beam scanning.
[0134] In the example, the payload size of the combined UCI (e.g., the combined HARQ ACK / NACK feedback) can be large. When scheduling a PUCCH to carry the combined UCI, the processor of UE 101 can be configured according to the payload size, or in other words... Figure 10 The PUCCH format is dynamically selected based on the total number of bits in the bit set.
[0135] In the example, the dynamic selection of PUCCH is based on downlink control information (DCI) from the TRP. Moreover, fields in the DCI can be used to indicate the resources used for PUCCH transmission from the resource set of the new PUCCH format used for higher-layer configuration.
[0136] For example, the 3GPP TS 38.211 Release 15.2.0 (“Physical Channels and Modulation”) defines the new radio (NR) PUCCH format in Table 6.3.2.1-1, as follows:
[0137] Table 6.3.2.1-1: PUCCH format.
[0138]
[0139] in, It is the length of the PUCCH transmission in units of OFDM symbols.
[0140] Figure 13 and Figure 14 The illustrations show two examples 1300 and 1400 of uplink channels for scheduling according to some embodiments. In example 1300, the scheduled uplink channel may include one PUSCH and two short PUCCHs. In example 1400, the scheduled uplink channel may include one PUSCH, one long PUCCH, and one short PUCCH. In other examples, the scheduled uplink channel may include more or fewer uplink channels than in examples 1300 or 1400, for example, scheduling one PUSCH plus one PUCCH, or scheduling only two short PUCCHs.
[0141] In some embodiments, the term "short PUCCH" may refer to a PUCCH of format 2 in Table 6.3.2.1-1 above. In other embodiments, the term "short PUCCH" may refer to a PUCCH of format 0 in Table 6.3.2.1-1 above.
[0142] In some embodiments, the long PUCCH may be a PUCCH having format 1, format 3 or format 4.
[0143] Figure 15 This is a flowchart illustrating an example method 1500 that can be employed at the UE to facilitate multiple TRP operations according to some embodiments.
[0144] According to some embodiments, a machine-readable medium may store instructions associated with method 1500, which, when executed, enable a UE to perform the steps of method 1500.
[0145] In step 1502, the UE may generate an uplink control channel (UCI) for each of the two or more TRPs communicating with the UE.
[0146] In step 1506, the UE may schedule one or more uplink channels to carry UCI, enabling it to be transmitted via an interface (e.g., for sending / receiving data to / from the UCI). Figure 2 RF circuit system 206 transmits / receives data Figure 3 The RF circuit system interface 316 transmits UCI to the TRP individually or in combination on a scheduled uplink channel, wherein the uplink channel may include the New Radio (NR) Physical Uplink Control Channel (PUCCH) and / or the NR Physical Uplink Shared Channel (PUSCH).
[0147] In an embodiment, the UCI generated in step 1502 may include hybrid automatic repeat request (HARQ) acknowledgment / negative acknowledgment (ACK / NACK) feedback and / or channel state information (CSI) report.
[0148] In an embodiment, in step 1506, the UE may schedule multiple uplink channels, each carrying a UCI generated for one of the TRPs, wherein the multiple uplink channels may be multiplexed in time division multiplexing (TDM) or frequency division multiplexing (FDM).
[0149] In an embodiment, in step 1506, the UE can schedule multiple uplink channels according to resource allocation in the time domain or frequency domain, which can be configured by a higher layer and / or dynamically configured by downlink control information (DCI) from the TRP.
[0150] As an example, information about resource allocation in the time domain can be exchanged between TRPs in a semi-static or dynamic manner. As another example, resource allocation in the frequency domain can be continuous based on semi-static or dynamic coordination between TRPs.
[0151] In an embodiment, if the uplink channels scheduled are multiplexed in an FDM manner, method 1500 may include another step 1508, wherein, if the UE only supports one transmission (Tx) beam or antenna port, the UE may select one of a plurality of uplink channels for transmission and discard the other uplink channels.
[0152] As an example, dropping can be based on drop rules or priority rules, which can be predefined in the 3GPP specification or configured by higher layers. As another example, dropping can be based on the channel quality of the uplink channel.
[0153] In an embodiment, method 1500 may include an optional step 1504 after step 1502 and before step 1506. In step 1504, the UE may combine the UCIs generated for each TRP into a bit set, where each UCI corresponds to a subset of the bit set. In an example, the number of bits in each subset may be configured by a higher layer and / or indicated by downlink control information (DCI) from the TRP. Then, in step 1506, the UE may schedule a single uplink channel to carry the bit set.
[0154] In one example, the bit set can be transmitted to one of the TRPs, which can then forward the bit set to the remaining TRPs. In another example, if the UE supports multiple transmit (Tx) beams, the bit set can be transmitted to each TRP simultaneously.
[0155] In this embodiment, after combining the UCIs generated for each TRP into a bit set in step 1504, the UE can schedule multiple uplink channels in step 1506, each uplink channel carrying the bit set. Depending on the scheduling, if the UE supports multiple transmission (Tx) beams, the bit set can be transmitted to each TRP simultaneously; or if the UE only supports a single Tx beam, the bit set can be transmitted to each TRP via beam scanning.
[0156] In an embodiment, the TRP index for the bit set can be predefined in the 3GPP technical specification or configured by a higher layer.
[0157] In an embodiment, the bit set may include only the UCI generated by the TRP for the corresponding HARQ-ACK feedback.
[0158] In an embodiment, when scheduling a PUCCH to carry the bit set, method 1500 may further include an optional step of dynamically selecting the format of the PUCCH based on downlink control information (DCI) from the TRP according to the number of bits in the bit set.
[0159] Figure 16 This is a block diagram illustrating an example of a network node for facilitating multiple TRP operations according to some embodiments.
[0160] In this embodiment, network node 1602 may have two or more TRPs (e.g., TRP1, TRP2, ... TRPN). Various embodiments of multi-TRP operation can be implemented with at least two or all TRPs in network node 1602 together with the UE, as described in reference... Figures 7 to 15 Any of those discussed.
[0161] In an embodiment, network node 1602 may include processor 1604, which may be configured to: enable two or more TRPs to communicate with the UE and receive a set of bits via one or more uplink channels, the set of bits including multiple subsets corresponding to uplink control channels (UCI) of one of the TRPs; coordinate between the two or more TRPs; and generate downlink control information (DCI) for the UE, wherein the uplink channels may include NR PUCCH and / or NR PUSCH.
[0162] In an embodiment, the DCI may include one or more of the following:
[0163] Information indicating the allocation of resources for the uplink channel in the time domain;
[0164] Information indicating the allocation of resources for the uplink channel in the frequency domain;
[0165] Information indicating the number of bits in each of the multiple subsets; and
[0166] Information indicating the format of the PUCCH carrying the bit set.
[0167] According to some embodiments, the network node may be a radio access network (RAN) node, for example, Figure 1 The macro RAN node 111 shown can also be referred to as a base station (BS), node B (NB), evolved node B (eNB), next-generation node B (gNB), etc.
[0168] In Example 1600, the TRPs can be several transceivers or remote headends (RHs) located at a base station and can be coordinated by the processor 1604. The processor 1604 can act as a central coordinator, which can communicate with each TRP to coordinate between the different TRPs.
[0169] In another example, a TRP can reside across several network nodes. For instance, TRP1 can be part of one base station, while TRP2 can be part of another. In this case, TRP1 and TRP2 are controlled or coordinated by their respective Base Station Controllers (BSCs) and / or higher-level controllers or coordinators. For example, coordination between TRPs can be performed via a suitable backhaul (e.g., fiber optic cable).
[0170] For fifth-generation (5G) or new radio (NR) communication systems, various formats have been defined for the Physical Uplink Control Channel (PUCCH) to meet the different requirements of different types of services. For example, as mentioned above, the NR PUCCH format is defined in Table 6.3.2.1-1 of the 3GPP TS 38.211 Release 15.2.0.
[0171] Figure 17 This is a diagram illustrating an example 1700 of a short NR PUCCH according to some embodiments. The short NR PUCCH can have a relatively short duration within the uplink (UL) time slot. For example, the short NR PUCCH can have format 0 or format 2, which has a duration of one or two OFDM symbols, as defined in Table 6.3.2.1-1 above.
[0172] In Example 1700, the short NR PUCCH and the NR Physical Uplink Shared Channel (NR PUSCH) can be multiplexed in a time-division multiplexing (TDM) manner, which can be used for some applications with low latency requirements.
[0173] In another example, two short NR PUCCHs and one NR PUSCH can be reused in a TDM manner.
[0174] Furthermore, to accommodate the time delays of switching from downlink (DL) to uplink (UL) and from UL to DL, as well as round-trip propagation delays, a guard period (GP) can be inserted between the NR Physical Downlink Control Channel (NR PDCCH) and the NR PUSCH.
[0175] Figure 18 This is a diagram illustrating an example 1800 of a long NR PUCCH according to some embodiments. A long NR PUCCH can have a relatively long duration within a UL time slot. For example, a long NR PUCCH can have format 1, format 3, or format 4, having a duration of 4-14 OFDM symbols (i.e., spanning any number of symbols from 4 to 14 within a time slot), as defined in Table 6.3.2.1-1 above.
[0176] In Example 1800, long NR PUCCH and NR PUSCH can be multiplexed using Frequency Division Multiplexing (FDM). Furthermore, more OFDM symbols can be allocated to the long NR PUCCH than to the short NR PUCCH, in order to improve link budget and uplink coverage of the control channel.
[0177] Similarly, considering the switching time and round-trip propagation delay, the GP can be inserted between the NR PDCCH and the NR PUCCH and NR PUSCH.
[0178] According to some embodiments, short NR PUCCH and long NR PUCCH can carry uplink control channels (UCI). UCI may include one or more scheduling requests (SR), hybrid automatic repeat request (HARQ) acknowledgment / negative acknowledgment (ACK / NACK) feedback, channel state information (CSI) reports (e.g., channel quality indicator (CQI)), precoding matrix indicator (PMI), CSI resource indicator (CRI), rank indicator (RI), beam-related information (e.g., Layer 1 reference signal received power (L1-RSRP)), etc.
[0179] In the example, for a given UE (e.g., UE 101 or UE 102), it is possible to use the same time slot (e.g., such as...) Figure 14 (As shown) A short NR PUCCH and a long NR PUCCH are multiplexed using TDM. They can be used for different types of services with different requirements. For example, the short PUCCH can carry time-critical HARQ ACK / NACK feedback, while the long PUCCH can carry CSI reports with relatively large payload sizes.
[0180] According to some embodiments, the demodulation reference signal (DM-RS) generated by the UE can be used by network nodes (e.g., gNB or TRP) for channel estimation, coherent demodulation of received data, etc. The use of a properly designed DM-RS can significantly enhance the performance of a wireless communication system. The embodiments described below provide a detailed DM-RS design for a short NR PUCCH with a UCI exceeding 2 bits.
[0181] Figure 19 This is a diagram illustrating Example 1900 of a DM-RS mode for a short NR PUCCH having more than 2 bits of UCI, according to some embodiments. For example, a short NR PUCCH having more than 2 bits of UCI can refer to an NR PUCCH of format 2 in Table 6.3.2.1-1 above. Moreover, a short NR PUCCH can span one or two symbols.
[0182] As shown in Example 1900, a short NR PUCCH can span one symbol corresponding to a resource block (RB). A given RB can have 12 resource elements (REs), where the indices of the REs can be integers from 0 to 11, i.e., RE0, RE1...RE2. 11For short NR PUCCHs carrying more than 2 bits of UCI, DM-RS and UCI can be multiplexed on the NRPUCCH in FDM mode. As an example, DM-RS can be mapped to four REs (e.g., RE1, RE4, RE7, RE...). 10 On ), while UCI can be mapped onto any remaining RE.
[0183] According to some embodiments, pseudo-noise (PN) sequences can be used to generate DM-RS.
[0184] In the example, the PN sequence used for PUSCH can be used for DM-RS of a short NR PUCCH with more than 2 bits of UCI.
[0185] Figure 20 This is a flowchart illustrating an example method 2000 that can be employed at the UE to facilitate the generation of a DM-RS mode, according to some embodiments. The method can be... Figure 1 This is accomplished by UE 101 or UE 102, especially by one or more processors (e.g., Figure 2 or Figure 3 CPU 204E) and optionally via Figure 2 or Figure 3 The memory capacity is 204G.
[0186] In step 2004, the UE can generate a PN sequence based on an initialization seed. In step 2006, the UE can generate a DM-RS sequence based on the PN sequence generated in step 2004. Then, in step 2008, the UE can map the DM-RS sequence onto physical resources allocated for transmitting short NR PUCCHs, which have a UCI of 2 bits or more.
[0187] According to some embodiments, the method 2000 may further include a step 2002 of defining an initialization seed according to one or more of the following parameters:
[0188] A time slot index or micro-time slot index used for transmitting short PUCCHs;
[0189] The symbol index or start symbol index used for transmitting short NR PUCCH;
[0190] Scrambling code identifier (ID) or, when the scrambling code ID is unavailable, the physical cell ID;
[0191] Beam ID; and
[0192] UE-specific parameters.
[0193] UE-specific parameters may include, but are not limited to, Bandwidth Part (BWP) ID, offset parameters, or UE ID including the UE's Cell Radio Network Temporary Identifier (C-RNTI).
[0194] As an example, the scrambling ID can be configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), Radio Resource Control (RRC) signaling, etc.
[0195] As another example, the scrambling code ID can be dynamically indicated by downlink control information (DCI) from network nodes (e.g., gNB or TRP).
[0196] As another example, in uplink power control, there can be multiple sets of {P0, α} depending on the service type or beampup link or waveform. Scrambling code IDs can be configured based on the index of the {P0, α} set for uplink power control and / or path loss.
[0197] Furthermore, scrambling IDs can be configured independently for different bandwidth portions (BWPs) that are being configured or are active within the system bandwidth. Alternatively, scrambling IDs can be configured independently for different types of UCIs. For example, a scrambling ID with a value of 0 can be selected for HARQ ACK / NACK feedback, while a scrambling ID with a value of 1 can be selected for CSI reports.
[0198] If the UCI carried by the short NR PUCCH is a HARQ ACK / NACK feedback from the corresponding PDSCH of the network node, then the scrambling code ID used for the transmission of the DM-RS sequence on the short NR PUCCH can be the same as the scrambling code ID used for the transmission of the DM-RS sequence on the PDSCH. Alternatively, the scrambling code ID can be dynamically switched based on the DCI from the network node. For example, a 1-bit indicator in the DCI can be used to dynamically switch between two configured scrambling code IDs.
[0199] If the UCI carried by the short NR PUCCH is a CSI report, the scrambling code ID used for transmitting DM-RS sequences on the short NR PUCCH can be configured by a higher layer via UE-specific RRC signaling. If the configured value is unavailable, the scrambling code ID can be equal to the physical cell ID.
[0200] In some embodiments, the initialization seed can be defined in step 2002 according to the following function:
[0201]
[0202] in:
[0203] c0 and c1 are constants; for example, c0 = 2. 16 Furthermore, c1 = 2, which can be predefined in the 3GPP technical specifications;
[0204] n s It is a slot index used for transmitting short NR PUCCH;
[0205] l is the symbol index or start symbol index used to transmit short NR PUCCH; and
[0206] It is the m-th scrambling code ID used to transmit short NR PUCCH.
[0207] It is important to note that This can be configured at a higher level or dynamically indicated in the DCI for PDSCH scheduling, or a combination thereof. In the example, or It can be configured by higher management.
[0208] In another example, when When the value is not configured by a higher level. (i.e., the community ID), or The function f() can be predefined in the technical specifications.
[0209] When a short NR PUCCH spans two symbols, a PN sequence for transmitting DM-RS over the short NRPUCCH can be generated independently for each symbol, for example, by including the symbol index "1" as a variable in the process of generating the PN sequence. For example, an initialization seed can be defined independently for each symbol based on its corresponding symbol index. Therefore, the function described above for generating the initialization seed can be rewritten as:
[0210]
[0211] In some embodiments, the initialization seed can be defined in step 2002 according to the following function:
[0212]
[0213] in:
[0214] c0 is constant; for example, c0 = 2. 16 This can be predefined in the 3GPP technical specifications;
[0215] n s It is a slot index used for transmitting short NR PUCCH;
[0216] l is the symbol index or start symbol index used to transmit short NR PUCCH; and
[0217] PDSCH can be scheduled by higher-level configuration or dynamically indicated in the DCI, for example, Or 1.
[0218] In some embodiments, the initialization seed can be defined in step 2002 according to the following function:
[0219]
[0220] in:
[0221] c0 is constant; for example, c0 = 2. 16 This can be predefined in the 3GPP technical specifications;
[0222] n s It is a slot index used for transmitting short NR PUCCH;
[0223] It is the m′th scrambling code ID used for the transmission of short NR PUCCH; and
[0224] n RNTI The C-RNTI of a given UE can be referred to as the temporary C-RNTI (TC-RNTI) before the UE obtains the C-RNTI, provided that the short NR PUCCH carries HARQ-ACK / NACK feedback for Msg.4 transmission in the random access channel (RACH) procedure.
[0225] After an initialization seed has been defined according to any of the above embodiments or obtained by other methods (e.g., retrieving the initialization seed directly from a memory or storage device), the UE can use the initialization seed to initialize the PN sequence generator to generate a PN sequence (in step 2004).
[0226] In the example, the UE can use a waveform based on Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) to generate the same PN sequence for the DM-RS sequence on both the short PUCCH and PUSCH.
[0227] Subsequently, the UE can generate a DM-RS sequence based on the PN sequence generated in step 2006, and then map the DM-RS sequence onto physical resources allocated for transmitting a short NR PUCCH with more than 2 bits of UCI in step 2008.
[0228] The following provides various embodiments of physical resource mapping for short NR PUCCHs with a UCI of more than 2 bits.
[0229] In one embodiment, the UE can generate a DM-RS sequence based on at least a maximum number of Physical Resource Blocks (PRBs) supported by a given subcarrier spacing within a wideband component carrier (CC). For example, if the wideband CC occupies a bandwidth of 100 MHz and the given subcarrier spacing is 15 kHz, then the maximum number of PRBs could be approximately 275. Thus, the UE can use a common PRB index (i.e., from 0 to 274) regarding the wideband CC to map the DM-RS sequence onto the physical resources allocated for transmitting short NR PUCCHs, which have a UCI greater than 2 bits.
[0230] In the example, according to the table below, a given subcarrier spacing Δf can have other values depending on μ:
[0231]
[0232]
[0233] In another embodiment, the UE can generate the DM-RS sequence based at least on the total number of PRBs supported by a given subcarrier interval within a configured bandwidth portion (BWP) (e.g., 10 MHz or 20 MHz). In this way, the UE can use a UE-specific PRB index to map the DM-RS sequence to physical resources allocated for transmitting short NR PUCCHs with more than 2 bits of UCI for a given subcarrier interval within the configured BWP.
[0234] In another embodiment, the UE may generate a DM-RS sequence based at least on the number of PRBs allocated in the frequency domain for transmission of a short PUCCH with more than 2 bits of UCI, and directly map the DM-RS sequence onto the allocated PRBs.
[0235] In the case where a short NR PUCCH spans two symbols, the DM-RS sequence can be generated based on any one of (i) the maximum number of PRBs within the wideband CC, the total number of PRBs within the configured BWP, and the number of allocated PRBs, and additionally based on (ii) the number of symbols allocated in the time domain for transmitting the short NR PUCCH (in this case, "2"). After modulation, the DM-RS sequence can be mapped onto the DM-RS RE in the allocated resources for each symbol of the short NR PUCCH transmission.
[0236] Figure 21 This is a diagram illustrating an example of frequency-priority mapping of DM-RS sequences according to some embodiments. Figure 22This is a diagram illustrating an example of time-priority mapping of DM-RS sequences according to some embodiments. In these examples, localized resources are allocated for short NRPUCCHs.
[0237] When a short NR PUCCH spans one symbol, the DM-RS sequence can be mapped to the DM-RS RE in the allocated resources in a frequency-priority mapping manner for the transmission of the short NR PUCCH, that is, mapped to the DM-RS RE of the symbol in ascending or descending frequency order.
[0238] When a short NR PUCCH spans two symbols, time-priority mapping or frequency-priority mapping can be used to map the DM-RS sequence on the DM-RS RE in the allocation resources for the transmission of the short NR PUCCH.
[0239] In the example, the choice between time-priority and frequency-priority mapping methods can be configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), and Radio Resource Control (RRC) signaling. Figure 21 When performing frequency-priority mapping, the DM-RS sequence can be mapped to the DM-RS RE of the first symbol in ascending or descending order of frequency first, and then mapped to the DM-RS RE of the second symbol in ascending or descending order of frequency only after all the DM-RS REs of the first symbol have been used up.
[0240] When using Figure 22 In time-priority mapping, the DM-RS sequence can first be mapped to the DM-RS RE of the lowest subcarrier in ascending time order (i.e., for the first symbol, then for the second symbol), and then mapped to the DM-RS RE of the second-to-last subcarrier in ascending time order.
[0241] In the example, the above mechanism can be applied to the following situations: distributed transmission for short NR PUCCHs spanning 1 or 2 symbols, or frequency hopping can be applied to the transmission of short NR PUCCHs spanning 2 symbols.
[0242] In addition, to support multi-user multiple-input multiple-output (MU-MIMO), orthogonal cover codes (OCC) can be used to enhance the design of DM-RS sequences with short NR PUCCHs having more than 2 bits of UCI.
[0243] In some embodiments, OCC can be applied to the DM-RS RE over one PRB (one symbol duration) or two PRBs (two symbol durations) to support orthogonal MU-MIMO.
[0244] Figure 23 The illustration shows an example of applying OCC to a DM-RS RE within one PRB (i.e., frequency domain OCC). In this example, a 2-bit OCC can be used to define two orthogonal DM-RS sequences. For example, OCC = [1 1] and [1 -1] can be used to support orthogonal MU-MIMO. After generating DM-RS sequences for two UEs (e.g., UE1 and UE2), [1 1] can be applied to the DM-RS sequence of UE1, and [1 -1] can be applied to the DM-RS sequence of UE2. Therefore, for UE1, the DM-RS sequence on the first RE can be multiplied by 1, and the DM-RS sequence on the second RE can be multiplied by 1; and for UE2, the DM-RS sequence on the first RE can be multiplied by 1, and the DM-RS sequence on the second RE can be multiplied by -1.
[0245] Figure 24 The illustration shows an example of applying OCC to DM-RS REs within two PRBs (i.e., time-domain OCC). In this example, a frequency mapping with the same sequence values in each symbol can be used. For example, an OCC of 2 bits in length can be applied to define two orthogonal DM-RS sequences. In one example, OCC = [1 1] and [1 -1] can be used to support orthogonal MU-MIMO. After generating DM-RSs for two UEs (e.g., UE1 and UE2), [1 1] can be applied to the DM-RS sequence of UE1, and [1 -1] can be applied to the DM-RS sequence of UE2. For UE1, the DM-RS sequence on the first symbol can be multiplied by 1, and the DM-RS sequence on the second symbol can be multiplied by 1. For UE2, the DM-RS sequence on the first symbol can be multiplied by 1, and the DM-RS sequence on the second symbol can be multiplied by 1. Note that frequency-domain OCC can also be applied in this case. Moreover, the OCC can have any suitable length.
[0246] Additionally, when OCC is applied to DM-RS sequences in the frequency or time domain, an initialization seed for generating DM-RS sequences can be defined to support orthogonal MU-MIMO, provided that the sequences have the same scrambling code ID and no UE-specific parameters (e.g., UE ID or C-RNTI).
[0247] In the example, at least some UEs transmitting at the same location can use the same UE ID or the same scrambling code ID. In other words, the DM-RS sequence used for the UEs is the same, and the OCC can be used to distinguish these UEs.
[0248] It is important to note that the OCC used for the DM-RS sequence on a short NR PUCCH can be configured by higher layers via UE-specific RRC signaling, dynamically indicated in the DCI, or a combination thereof. Alternatively, it can be determined for different UCI types. For example, for a short PUCCH carrying HARQ-ACK feedback, the OCC used for DM-RS sequence transmission can be dynamically indicated in the DCI, while for a short PUCCH carrying CSI reports, the OCC used for DM-RS sequence transmission can be configured by higher layers via RRC signaling.
[0249] According to some embodiments, a machine-readable medium may store instructions associated with any example of method 2000, which, when executed, enable the UE to perform the steps of any example of method 2000.
[0250] According to some embodiments, an apparatus may include various functional modules to perform the steps of any example of method 2000.
[0251] In some embodiments, Figure 2 , Figure 3 The electronic devices, networks, systems, chips, or components, or portions thereof, or embodiments thereof, shown in the other accompanying drawings may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein.
[0252] It should be noted that some embodiments of this disclosure are discussed in the context of 5G networks and New Radio (NR). However, those skilled in the art will understand that these embodiments may be applicable to other networks such as LTE, LTE-Advanced, or even the coexistence of LTE, LTE-Advanced, and NR.
[0253] The following are some non-limiting examples. Examples in this document may include subjects such as apparatus, user equipment, methods, means for performing method steps, and machine-readable media including instructions that, when executed by a machine such as a processor having memory, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc., cause the machine to perform the steps of a method, network node, and communication system.
[0254] Example
[0255] Example 1 is an apparatus for a user equipment (UE) comprising: an interface configured to support communication between the UE and two or more Transmitter Receiver Points (TRPs); and a processor configured to: generate an uplink control channel (UCI) for each TRP; and schedule one or more uplink channels to carry the UCI, such that the UCI is transmitted individually or in combination to the TRPs via the interface, wherein the uplink channels include a New Radio (NR) Physical Uplink Control Channel (PUCCH) and / or an NR Physical Uplink Shared Channel (PUSCH).
[0256] Example 2 may include the subject matter of Example 1, wherein the UCI includes hybrid automatic repeat request (HARQ) acknowledgment / negative acknowledgment (ACK / NACK) feedback and / or channel state information (CSI) reporting.
[0257] Example 3 may include the subject of Example 1 or 2, wherein the processor is further configured to schedule multiple uplink channels carrying a UCI generated for one of the TRPs, wherein the multiple uplink channels are multiplexed in time division multiplexing (TDM) or frequency division multiplexing (FDM).
[0258] Example 4 may include the subject of Example 3, wherein the processor is further configured to schedule multiple uplink channels based on resource allocation in the time or frequency domain, the resource allocation being configured by a higher layer and / or dynamically configured by downlink control information (DCI) from the TRP.
[0259] Example 5 may include the subject of Example 4, in which information about resource allocation in the time domain is exchanged between TRPs in a semi-static or dynamic manner; or in which resource allocation in the frequency domain is continuous based on semi-static or dynamic coordination between TRPs.
[0260] Example 6 may include the subject of Example 3, wherein the processor is further configured to: in the case of FDM mode, when the UE only supports one transmission (Tx) beam or antenna port, select one of the multiple uplink channels for transmission and discard the other uplink channels.
[0261] Example 7 may include the subject of Example 6, wherein dropping is based on dropping rules or priority rules predefined in the 3GPP specification or configured by higher layers; or wherein dropping is based on the channel quality of the uplink channel.
[0262] Example 8 may include the subject of Example 1, wherein the processor is further configured to: combine UCIs generated for each TRP in a TRP into a bit set, wherein each UCI corresponds to a subset of the bit set; and schedule a single uplink channel to carry the bit set, wherein the bit set is to be transmitted to one of the TRPs, which will forward the bit set to the remaining TRPs, or wherein, if the UE supports multiple transmission (Tx) beams, the bit set is to be transmitted simultaneously to each of the TRPs.
[0263] Example 9 may include the subject of Example 1, wherein the processor is further configured to: combine UCIs generated for each TRP in the TRP into a bit set, wherein each UCI corresponds to a subset of the bit set; and schedule multiple uplink channels carrying the bit set respectively, wherein if the UE supports multiple transmission (Tx) beams, the bit set will be transmitted simultaneously to each TRP in the TRP, or wherein if the UE supports only a single Tx beam, the bit set will be transmitted to each TRP by means of beam scanning.
[0264] Example 10 may include the subject of Example 8 or 9, wherein the TRP index of the bit set is predefined in the 3GPP specification or configured by a higher layer, or wherein the bit set includes only the UCI generated for the corresponding HARQ-ACK feedback for the TRP.
[0265] Example 11 may include the subject of Example 8 or 9, wherein the number of bits in each subset is indicated by higher-layer configuration and / or by downlink control information (DCI) from the TRP.
[0266] Example 12 may include the subject of Example 8 or 9, wherein the processor is further configured to: when scheduling a PUCCH to carry the bit set, dynamically select the format of the PUCCH based on the number of bits in the bit set and on the downlink control information (DCI) from the TRP.
[0267] Example 13 is a machine-readable medium including instructions that, when executed, cause a user equipment (UE) to: generate an uplink control channel (UCI) for each of two or more transport receiving points (TRPs) communicating with the UE; and schedule one or more uplink channels to carry the UCI, such that the UCI is transmitted individually or in combination to the TRPs via an interface, wherein the uplink channels include a New Radio (NR) Physical Uplink Control Channel (PUCCH) and / or an NR Physical Uplink Shared Channel (PUSCH).
[0268] Example 14 may include the subject matter of Example 13, wherein the UCI includes hybrid automatic repeat request (HARQ) acknowledgment / negative acknowledgment (ACK / NACK) feedback and / or channel state information (CSI) reporting.
[0269] Example 15 may include the subject of Example 13 or 14, wherein when the instruction is executed, it also causes the UE to: schedule multiple uplink channels for a UCI generated for one of the TRPs, wherein the multiple uplink channels are multiplexed in time division multiplexing (TDM) or frequency division multiplexing (FDM).
[0270] Example 16 may include the subject of Example 15, wherein the instructions, when executed, also cause the UE to: schedule multiple uplink channels according to resource allocation in the time or frequency domain, the resource allocation in the time or frequency domain being configured by a higher layer and / or dynamically configured by downlink control information (DCI) from the TRP.
[0271] Example 17 may include the subject of Example 16, wherein information about resource allocation in the time domain is exchanged between TRPs in a semi-static or dynamic manner; or wherein resource allocation in the frequency domain is continuous, based on semi-static or dynamic coordination between TRPs.
[0272] Example 18 may include the subject of Example 15, wherein the instruction, when executed, also causes the UE to: in the case of FDM mode, when the UE only supports one transmission (Tx) beam or antenna port, select one of the multiple uplink channels for transmission and discard the other uplink channels.
[0273] Example 19 may include the subject of Example 18, wherein dropping is based on dropping rules or priority rules predefined in the 3GPP specification or configured by higher layers; or wherein dropping is based on the channel quality of the uplink channel.
[0274] Example 20 may include the subject of Example 13, wherein when the instructions are executed, the UE also causes the UE to: combine UCIs generated for each TRP in the TRP into a bit set, wherein each UCI corresponds to a subset of the bit set; and schedule a single uplink channel to carry the bit set, wherein the bit set is to be transmitted to one of the TRPs in the TRPs, which will forward the bit set to the remaining TRPs, or wherein, if the UE supports multiple transmission (Tx) beams, the bit set will be transmitted simultaneously to each of the TRPs in the TRPs.
[0275] Example 21 may include the subject of Example 13, wherein when the instructions are executed, the UE also causes the UE to: combine the UCIs generated for each TRP in the TRP into a bit set, wherein each UCI corresponds to a subset of the bit set; and schedule multiple uplink channels carrying the bit set, wherein if the UE supports multiple transmission (Tx) beams, the bit set will be transmitted simultaneously to each TRP in the TRP, or wherein if the UE supports only a single Tx beam, the bit set will be transmitted to each TRP in the TRP by means of beam scanning.
[0276] Example 22 may include the subject of Example 20 or 21, wherein the TRP index of the bit set is predefined in the 3GPP specification or configured by a higher layer, or wherein the bit set includes only the UCI generated for the corresponding HARQ-ACK feedback for the TRP.
[0277] Example 23 may include the subject of Example 20 or 21, wherein the number of bits in each subset is indicated by higher-layer configuration and / or by downlink control information (DCI) from the TRP.
[0278] Example 24 may include the subject of Example 20 or 21, wherein the instruction, when executed, also causes the UE to: dynamically select the format of the PUCCH based on the number of bits in the bit set, in the case of scheduling the PUCCH to carry the bit set.
[0279] Example 25 is an apparatus for a network node having two or more Transmitter Receiver Points (TRPs), the apparatus including a processor configured to: enable the two or more TRPs to communicate with a UE and receive a set of bits via one or more uplink channels, the set of bits including multiple subsets corresponding to an uplink control channel (UCI) of one of the TRPs; coordinate between the two or more TRPs; and generate downlink control information (DCI) for the UE, wherein the uplink channels include a New Radio (NR) Physical Uplink Control Channel (PUCCH) and / or an NR Physical Uplink Shared Channel (PUSCH).
[0280] Example 26 may include the subject matter of Example 25, wherein the DCI includes one or more of the following: information indicating resource allocation in the time domain for an uplink channel; information indicating resource allocation in the frequency domain for an uplink channel; information indicating the number of bits in each of a plurality of subsets; and information indicating the format of the PUCCH carrying the bit set.
[0281] Example 27 is a user equipment (UE) that includes the subject and radio frequency (RF) circuitry of Example 1.
[0282] Example 28 is a network node that includes the subject of Example 25 or 26 and two or more Transmitter Receiver Points (TRPs).
[0283] Example 29 is a network node that includes the subject and radio frequency (RF) circuitry system of Example 25 or 26.
[0284] Example 30 is a communication system that includes the topics of Example 27 and Examples 28 or 29.
[0285] Example 31 is a method that can be adopted at the UE to facilitate multi-TRP operation, the method comprising the steps of: generating an uplink control channel (UCI) for each of two or more TRPs communicating with the UE; and scheduling one or more uplink channels to carry the UCI, such that the UCI can be transmitted to the TRP individually or in combination via an interface through the scheduled uplink channels, wherein the uplink channels may include NR PUCCH and / or NR PUSCH.
[0286] Example 32 may include the subject matter of Example 31 as well as one or more additional steps or operations discussed in this disclosure.
[0287] Example 33 is an apparatus that includes various means or functional modules for performing the method steps of Example 31 or 32.
[0288] Example 34 is a method that can be employed at a network node to facilitate multi-TRP operation, the method comprising the steps of: enabling two or more TRPs in the network node to communicate with a UE and receive a set of bits via one or more uplink channels, the set of bits comprising multiple subsets corresponding to an uplink control channel (UCI) of one of the TRPs; coordinating between the two or more TRPs; and generating downlink control information (DCI) for the UE, wherein the uplink channels include NR PUCCH and / or NR PUSCH.
[0289] Example 35 may include the subject matter of Example 34 as well as one or more additional steps or operations discussed in this disclosure.
[0290] Example 36 is an apparatus that includes various means or functional modules for performing the method steps of Example 34 or 35.
[0291] Example 37 is an apparatus for a user equipment (UE) operable to communicate with a new radio (NR) network node. The apparatus includes a processor configured to: generate a pseudo noise (PN) sequence based on an initialization seed; generate a demodulation reference signal (DM-RS) sequence based on the PN sequence; and map the DM-RS sequence onto physical resources allocated for transmitting a short physical uplink control channel (PUCCH) having more than 2 bits of uplink control channel (UCI).
[0292] Example 38 may include the subject matter of Example 37, wherein the processor is further configured to define an initialization seed based on one or more of the following parameters: a slot index or micro-slot index for transmitting short PUCCHs; a symbol index or start symbol index for transmitting short PUCCHs; a scrambling code identifier (ID) or, when the scrambling code ID is unavailable, a physical cell ID; a beam ID; and UE-specific parameters.
[0293] Example 39 may include the subject matter of Example 38, wherein UE-specific parameters include the Bandwidth Part (BWP) ID, offset parameters, or the UE ID including the UE's Cell Radio Network Temporary Identifier (C-RNTI).
[0294] Example 40 may include the subject of Example 38 or 39, wherein the scrambling ID is configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI) or Radio Resource Control (RRC) signaling, and / or dynamically indicated by downlink control information (DCI) from network nodes.
[0295] Example 41 may include the subject of Example 38 or 39, wherein the scrambling ID is configured independently for different bandwidth portions (BWP) active within the system bandwidth and / or for different types of UCI.
[0296] Example 42 may include the subject of Example 38 or 39, where, in the case of a short PUCCH spanning two symbols, the initialization seed is defined independently for each symbol based on its corresponding symbol index.
[0297] Example 43 may include the subject of Example 41, wherein the UCI carried by the short PUCCH is a Hybrid Automatic Repeat Request (HARQ) Acknowledgment / Negative Acknowledgment (ACK / NACK) feedback from the corresponding Physical Downlink Shared Channel (PDSCH) of the network node, and wherein the scrambling code ID for the DM-RS sequence on the short PUCCH is the same as the scrambling code ID for the DM-RS sequence on the PDSCH, or is dynamically switched according to the downlink control information (DCI) from the network node.
[0298] Example 44 may include the subject of Example 38 or 39, where the scrambling ID is configured based on the index of the set of {P0, α} used for uplink power control and / or path loss.
[0299] Example 45 may include the subject of Example 37, wherein the processor is also configured to generate the same PN sequence for the DM-RS sequence on both the short PUCCH and PUSCH using a waveform based on Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM).
[0300] Example 46 may include the subject of Examples 37, 38, or 39, wherein the processor is adapted to: generate a DM-RS sequence based at least on the maximum number of Physical Resource Blocks (PRBs) supported by a given subcarrier interval within a Wideband Component Carrier (CC), and map the DM-RS sequence to the physical resource using a common PRB index with respect to the Wideband CC. In an alternative example, the processor is adapted to: generate a DM-RS sequence based at least on the total number of PRBs supported by a given subcarrier interval within a configured Bandwidth Part (BWP), and map the DM-RS sequence to the physical resource using a UE-specific PRB index for a given subcarrier interval within a configured BWP. In an alternative example, the processor is adapted to: generate a DM-RS sequence based at least on the number of PRBs allocated in the frequency domain for transmitting short PUCCHs, and map the DM-RS sequence to the allocated PRBs.
[0301] Example 47 may include the subject of Example 46, where the DM-RS sequence is also generated based on the number of symbols allocated in the time domain for the transmission short PUCCH.
[0302] Example 48 may include the subject of Example 47, wherein the processor is further configured to: select one of a time-priority mapping method and a frequency-priority mapping method to map the DM-RS sequence onto the physical resource when the short PUCCH spans two symbols.
[0303] Example 49 may include the subject of Example 47, wherein the processor is further configured to employ a time-priority mapping or frequency-priority mapping method configured by higher layers via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling.
[0304] Example 50 may include the subject of Example 38 or 39, wherein the processor is further configured to apply an orthogonal coverage code (OCC) to the DM-RS sequence in the frequency domain or time domain when an initialization seed is defined with the same scrambling code ID and without the UE-specific parameters.
[0305] Example 51 may include the subject of Example 50, wherein the OCC is configured by a higher layer or dynamically indicated in the downlink control information (DCI) or a combination thereof.
[0306] Example 52 is a machine-readable medium including instructions that, when executed, enable a user equipment (UE) to communicate with a new radio (NR) network node: generate a pseudo-noise (PN) sequence based on an initialization seed; generate a demodulation reference signal (DM-RS) sequence based on the PN sequence; and map the DM-RS sequence onto physical resources allocated for transmitting a short physical uplink control channel (PUCCH) having more than 2 bits of uplink control channel (UCI).
[0307] Example 53 may include the subject of Example 52, wherein when the instruction is executed, it also causes the UE to define an initialization seed based on one or more of the following parameters: a slot index or micro-slot index for transmitting short PUCCHs; a symbol index or start symbol index for transmitting short PUCCHs; a scrambling code identifier (ID) or, when the scrambling code ID is unavailable, a physical cell ID; a beam ID; and UE-specific parameters.
[0308] Example 54 may include the subject matter of Example 53, wherein UE-specific parameters include the Bandwidth Partial (BWP) ID, offset parameters, or the UE ID including the UE's Cell Radio Network Temporary Identifier (C-RNTI). Example 55 may include the subject matter of Example 53 or 54, wherein the scrambling code ID is configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling, and / or dynamically indicated by downlink control information (DCI) from network nodes.
[0309] Example 56 may include the subject of Example 53 or 54, where the scrambling ID is configured independently for different bandwidth portions (BWP) active within the system bandwidth and / or for different types of UCI.
[0310] Example 57 may include the subject of Example 53 or 54, where, in the case of a short PUCCH spanning two symbols, the initialization seed is defined independently for each symbol based on its corresponding symbol index.
[0311] Example 58 may include the subject of Example 56, wherein the UCI carried by the short PUCCH is a Hybrid Automatic Repeat Request (HARQ) Acknowledgment / Negative Acknowledgment (ACK / NACK) feedback from the corresponding Physical Downlink Shared Channel (PDSCH) of the network node, and wherein the scrambling code ID used for the DM-RS sequence on the short PUCCH is the same as the scrambling code ID used for the DM-RS sequence on the PDSCH, or is dynamically switched according to the downlink control information (DCI) from the network node.
[0312] Example 59 may include the subject of Example 53 or 54, where the scrambling ID is configured based on the index of the set of {P0, α} used for uplink power control and / or path loss.
[0313] Example 60 may include the subject of Example 52, wherein the instruction, when executed, also causes the UE to: generate the same PN sequence for the DM-RS sequence on both the short PUCCH and PUSCH using a waveform based on Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM).
[0314] Example 61 may include the subject matter of Examples 52, 53, or 54, wherein the instructions, when executed, further cause the UE to: generate a DM-RS sequence based at least on the maximum number of Physical Resource Blocks (PRBs) supported by a given subcarrier interval within a Wideband Component Carrier (CC), and map the DM-RS sequence onto the physical resource using a common PRB index with respect to the Wideband CC. In an alternative example, the instructions, when executed, further cause the UE to: generate a DM-RS sequence based at least on the total number of PRBs supported by a given subcarrier interval within a configured Bandwidth Part (BWP), and map the DM-RS sequence onto the physical resource using a UE-specific PRB index for a given subcarrier interval within the configured BWP. In an alternative example, the instructions, when executed, further cause the UE to: generate a DM-RS sequence based at least on the number of PRBs allocated in the frequency domain for transmitting short PUCCHs, and map the DM-RS sequence onto the allocated PRBs.
[0315] Example 62 may include the subject of Example 61, wherein the DM-RS sequence is also generated based on the number of symbols allocated in the time domain for transmitting short PUCCHs.
[0316] Example 63 may include the subject of Example 62, wherein, when executed, the instruction also causes the UE to: select one of a time-priority mapping mode and a frequency-priority mapping mode to map the DM-RS sequence onto the physical resource in the case where a short PUCCH spans two symbols.
[0317] Example 64 may include the subject of Example 62, wherein when the instruction is executed, it also causes the UE to: adopt a time-priority mapping or frequency-priority mapping configured by a higher layer via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling.
[0318] Example 65 may include the subject of Example 53 or 54, wherein the instructions, when executed, also cause the UE to: apply an orthogonal coverage code (OCC) to the DM-RS sequence in the frequency or time domain when an initialization seed is defined with the same scrambling code ID and without the UE-specific parameters.
[0319] Example 66 may include the subject of Example 65, wherein the OCC is configured by a higher layer or dynamically indicated in the downlink control information (DCI) or a combination thereof.
[0320] Example 67 is a user equipment (UE) that includes the subject and radio frequency (RF) circuitry of Example 37.
[0321] Example 68 is a network node that is adapted to receive a short NR PUCCH from the UE in Example 67 and use the DM-RS derived from the short NR PUCCH for channel estimation and demodulation.
[0322] Example 69 is a communication system that includes the topics of Example 67 and Example 68.
[0323] Example 70 is a method that can be used at the UE, comprising the steps of: generating a pseudo noise (PN) sequence based on an initialization seed; generating a demodulation reference signal (DM-RS) sequence based on the PN sequence; and mapping the DM-RS sequence to physical resources allocated for transmitting a short PUCCH having a UCI of more than 2 bits.
[0324] Example 71 may include the subject matter of Example 70 as well as one or more additional steps or operations discussed in this disclosure.
[0325] Example 72 is an apparatus that includes various means or functional modules for performing the method steps of Example 70 or 71.
[0326] Example 73 is a method that can be used at a network node in Example 68, comprising the steps of: receiving a short NR PUCCH from a UE in Example 67, and using the DM-RS derived from the short NR PUCCH for channel estimation and demodulation.
[0327] Example 74 is an apparatus that includes various means or functional modules for performing the method steps of Example 73.
[0328] Example 75 may include the signal described in any of Examples 1 through 74.
[0329] The above description of the illustrated embodiments of this disclosure, including the content described in the abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise form disclosed. Although specific embodiments and examples have been described herein for illustrative purposes, various modifications may be contemplated within the scope of such embodiments and examples, as will be appreciated by those skilled in the art.
[0330] In this regard, although the disclosed subject matter has been described in conjunction with various embodiments and corresponding drawings, it is to be understood, where applicable, that other similar embodiments may be used, or modifications and additions may be made to the described embodiments to perform the same, similar, alternative, or substituted functions of the disclosed subject matter without departing from it. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted in accordance with the breadth and scope of the appended claims.
[0331] In particular, regarding the various functions performed by the aforementioned components or structures (components, devices, circuits, systems, etc.), unless otherwise indicated, the terminology used to describe such components (including references to "device") is intended to correspond to any component or structure that performs the specified function of the described component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure performing the function in the exemplary embodiments illustrated herein. Furthermore, although specific features may have been disclosed with respect to only one of several embodiments, such features may be combined with one or more other features of other embodiments, which may be desirable and advantageous for any given or particular application.
Claims
1. An apparatus for a user equipment (UE), the UE being operable to communicate with a new radio (NR) network node, the apparatus comprising: The processor is configured as follows: A pseudo-noise PN sequence is generated based on the initial seed; A demodulation reference signal DM-RS sequence is generated based on the PN sequence; as well as The DM-RS sequence is mapped to physical resources allocated for transmitting short physical uplink control channels (PUCCHs), which span one or two symbols and have more than 2 bits of uplink control information (UCI). The initialization seed is based on the following parameters: The time slot index or micro-time slot index used for transmitting the short PUCCH; The symbol index or start symbol index used for transmitting the short PUCCH; and The scrambling code identifier ID when the scrambling code identifier is available, otherwise the physical cell ID; The scrambling code ID is configured independently for different bandwidth portions (BWPs) active within the system bandwidth.
2. The apparatus of claim 1, wherein the initialization seed is further based on UE-specific parameters, wherein the UE-specific parameters include a bandwidth portion BWP ID, an offset parameter, or a UE ID including the UE's cell radio network temporary identifier (C-RNTI).
3. The apparatus of claim 1 or 2, wherein the scrambling code ID is configured by a higher layer via: NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI) or Radio Resource Control (RRC) signaling, and / or dynamically indicated by downlink control information (DCI) from the network node.
4. The apparatus of claim 1 or 2, wherein, in the case that the short PUCCH spans two symbols, the initialization seed is defined separately for each symbol according to its corresponding symbol index.
5. The apparatus of claim 1, wherein the UCI carried by the short PUCCH is a Hybrid Automatic Repeat Request (HARQ) ACK / NACK feedback for the corresponding Physical Downlink Shared Channel (PDSCH) from the network node; and The scrambling code ID used for the DM-RS sequence on the short PUCCH is the same as the scrambling code ID used for the DM-RS sequence on the PDSCH, or it is dynamically switched according to the downlink control information (DCI) from the network node.
6. The apparatus according to any one of claims 1 to 2, wherein the processor is adapted to: The DM-RS sequence is generated based at least on the maximum number of Physical Resource Blocks (PRBs) supported for a given subcarrier interval within the wideband component carrier (CC), and the DM-RS sequence is mapped onto the physical resources using a common PRB index for the wideband CC.
7. The apparatus according to any one of claims 1 to 2, wherein the processor is adapted to: generate the DM-RS sequence based at least on the total number of PRBs supported for a given subcarrier interval within a configured bandwidth portion (BWP), and map the DM-RS sequence onto the physical resource using a UE-specific PRB index for the given subcarrier interval within the configured BWP.
8. The apparatus according to any one of claims 1 to 2, wherein the processor is adapted to: generate the DM-RS sequence based at least on the number of PRBs allocated for transmitting the short PUCCH in the frequency domain, and map the DM-RS sequence onto the allocated PRBs.
9. The apparatus of claim 6, wherein the DM-RS sequence is also generated based on the number of symbols allocated in the time domain for transmitting the short PUCCH.
10. The apparatus of claim 9, wherein the processor is further configured to: When the short PUCCH spans two symbols, a frequency-priority mapping method is used to map the DM-RS sequence onto the physical resource.
11. The apparatus according to claim 1 or 2, wherein the processor is further configured to: When the same scrambling code ID is used and the initialization seed is not defined using the UE-specific parameters, the orthogonal coverage code OCC is applied to the DM-RS sequence in the frequency domain or the time domain.
12. A non-transitory machine-readable medium comprising instructions that, when executed, enable a user equipment (UE) to communicate with a new radio (NR) network node: A pseudo-noise PN sequence is generated based on the initial seed; A demodulation reference signal DM-RS sequence is generated based on the PN sequence; and The DM-RS sequence is mapped to physical resources allocated for transmitting short physical uplink control channels (PUCCHs), which span one or two symbols and have more than 2 bits of uplink control information (UCI). The initialization seed is based on the following parameters: The time slot index or micro-time slot index used for transmitting the short PUCCH; The symbol index or start symbol index used to transmit the short PUCCH; as well as Scrambling code identifier ID, or physical cell ID when the scrambling code ID is unavailable; The scrambling code ID is configured independently for different bandwidth portions (BWPs) active within the system bandwidth.
13. The non-transient machine-readable medium of claim 12, wherein the initialization seed is further based on UE-specific parameters, wherein the UE-specific parameters include a bandwidth portion BWP ID, an offset parameter, or a UE ID including the UE's cell radio network temporary identifier (C-RNTI).
14. The non-transient machine-readable medium according to claim 12 or 13, wherein the scrambling ID is configured by a higher layer via: NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI) or Radio Resource Control (RRC) signaling, and / or dynamically indicated by downlink control information (DCI) from the network node.
15. The non-transient machine-readable medium of claim 12 or 13, wherein, in the case that the short PUCCH spans two symbols, the initialization seed is defined individually for each symbol according to its corresponding symbol index.
16. The non-transitory machine-readable medium of claim 12, wherein the UCI carried by the short PUCCH is a Hybrid Automatic Repeat Request (HARQ) ACK / NACK feedback for the corresponding Physical Downlink Shared Channel (PDSCH) from the network node; and The scrambling code ID used for the DM-RS sequence on the short PUCCH is the same as the scrambling code ID used for the DM-RS sequence on the PDSCH, or it is dynamically switched according to the downlink control information (DCI) from the network node.
17. The non-transitory machine-readable medium according to any one of claims 12 or 13, wherein the instructions, when executed, further cause the UE to: The DM-RS sequence is generated based at least on the maximum number of Physical Resource Blocks (PRBs) supported for a given subcarrier interval within the wideband component carrier (CC), and the DM-RS sequence is mapped onto the physical resources using a common PRB index for the wideband CC.
18. The non-transitory machine-readable medium according to any one of claims 12 or 13, wherein the instructions, when executed, further cause the UE to: The DM-RS sequence is generated based at least on the total number of PRBs supported for a given subcarrier interval within the configured bandwidth portion (BWP), and the DM-RS sequence is mapped onto the physical resources using the configured UE-specific PRB index for the given subcarrier interval within the BWP.
19. The non-transitory machine-readable medium according to any one of claims 12 or 13, wherein the instructions, when executed, further cause the UE to: The DM-RS sequence is generated based on at least the number of PRBs allocated in the frequency domain for transmitting the short PUCCH, and the DM-RS sequence is mapped onto the allocated PRBs.
20. The non-transitory machine-readable medium of claim 17, wherein the DM-RS sequence is also generated based on the number of symbols allocated in the time domain for transmitting the short PUCCH.
21. The non-transitory machine-readable medium of claim 20, wherein the instructions, when executed, further cause the UE to: When the short PUCCH spans two symbols, a frequency-priority mapping method is used to map the DM-RS sequence onto the physical resource.
22. The non-transitory machine-readable medium according to claim 12 or 13, wherein the instructions, when executed, further cause the UE to: When the same scrambling code ID is used and the initialization seed is not defined using the UE-specific parameters, the orthogonal coverage code OCC is applied to the DM-RS sequence in the frequency domain or the time domain.
Citation Information
Patent Citations
Apparatus and method for transmitting reference signal
KR1020170083971A
