Downlink control information design for supporting single DCI scheduling for multiple cells

By designing a new DCI format and mapping relationship in a wireless communication system, concurrent scheduling of physical data channels is realized using a single DCI on multiple cells, and the problem that DCI can only be used for single cell scheduling in the prior art is solved. Improve resource utilization and flexibility.

CN119096500APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202280095372.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-28
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In existing wireless communication systems, a single downlink control information (DCI) can only be used to schedule physical data channels on one cell, and cannot schedule concurrently on multiple cells, resulting in insufficient resource utilization and poor scheduling flexibility.

Method used

Using a single DCI to schedule physical data channels on multiple cells or component carriers, by including carrier indicators, bandwidth partial indicators, frequency domain resource allocation, time domain resource allocation, send configuration indicators, antenna ports and modulation translations in the DCI field In the fields such as code scheme, a new DCI format is designed to support multi-cell scheduling, and the mapping relationship is configured through RNTI and RRC signaling.

Benefits of technology

Concurrent scheduling of physical data channels on multiple cells is realized, reducing PDCCH overhead, improving resource utilization and scheduling flexibility, and reducing DCI size.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096500A_ABST
    Figure CN119096500A_ABST
Patent Text Reader

Abstract

Physical data channels, such as PDSCH / PUSCH, may be scheduled for a given device / user equipment (UE) over multiple cells using a single data control information (DCI). Accordingly, a single DCI may be sent to a device / UE to schedule a physical data channel for the device / UE over multiple cells, such as concurrently scheduling the physical data channel for the device over multiple cells / component carriers. The single DCI may include a plurality of DCI fields for indicating desired communication parameters. Each DCI field in at least a subset of the plurality of DCI fields is for each cell of the plurality of cells or for a corresponding single cell of the plurality of cells. Whether a single DCI field is used for a given related communication parameter or multiple DCI fields may be individually determined for each of the related communication parameters to be indicated in the single DCI.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to wireless communications, including single downlink control information (DCI) scheduling for multiple cells. Background Art

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment devices or UEs) now also provide access to the Internet, email, text messaging, and navigation using a global positioning system (GPS), and are capable of operating sophisticated applications that utilize these capabilities. In addition, there are many different wireless communication technologies and wireless communication standards. Some examples of wireless communication standards include GSM, UMTS (WCDMA, TDS-CDMA), LTE, Advanced LTE (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), IEEE 802.16 (WiMAX), Bluetooth TM etc. The current telecommunication standard that goes beyond previous standards is known as the 5th generation of mobile networks or 5th generation wireless systems, referred to as 3GPP NR (also known as 5G-NR or NR-5G, 5G New Radio, also referred to as NR for short). NR provides higher capacity for a higher density of mobile broadband users while supporting device-to-device, ultra-reliable and massive machine communications, as well as lower latency and lower battery consumption than the LTE standard.

[0003] One aspect of wireless communication systems (including NR cellular wireless communication) is the use of a physical control channel to provide physical data channel scheduling information to a mobile device. At least a portion of the scheduling information is provided by downlink control information (DCI) sent on the physical control channel. Currently, a single DCI can only be used to schedule a physical data channel on one (e.g., a single) cell. Improvements in the art are expected. Summary of the invention

[0004] In particular, embodiments of methods and processes for scheduling physical data channels for a UE on multiple cells or component carriers (CCs) using a single downlink control information (DCI) during wireless communications, such as during 3GPP New Radio (NR) communications, are presented herein. Embodiments of a wireless communication system are also presented herein, the wireless communication system comprising at least a wireless communication device or user equipment device (UE) and / or a base station and / or an access point (AP) communicating with each other within the wireless communication system.

[0005] In some embodiments, a method for scheduling physical data channels on multiple cells or component carriers may include sending a single downlink control information (DCI) to a device (e.g., a UE) that schedules physical data channels, such as PDSCH or PUSCH, for the device on multiple cells or component carriers. In some embodiments, the single DCI may be used to concurrently schedule physical data channels for a device / UE on multiple cells / component carriers. The single DCI may include one or more DCI fields, wherein each DCI field in at least one subset of the DCI fields is used for each cell in the multiple cells, or a corresponding single cell in the multiple cells. The DCI field may include any one or more of the following: a virtual resource block (VRB) to physical resource block (PRB) mapping field; a PRB bundling size indicator field; a rate matching indicator field; a zero power (ZP) channel state information reference signal (CSI-RS) trigger field; a hybrid automatic repeat request (HARQ) process number field; a transmit power control (TPC) command field for a physical uplink control channel (PUCCH) for scheduling; a PUCCH resource indicator field; a physical downlink shared channel (PDSCH) to HARQ feedback timing indicator field; a sounding reference signal (SRS) request field; a code block group (CBG) transmit information (CBGTI) field; a CBG clear information (CBGFI) field; a demodulation reference signal (DMRS) sequence initialization field; a priority indicator field; a minimum applicable scheduling offset indicator field; or a secondary cell (SCell) sleep indication field.

[0006] In some embodiments, the single DCI may be defined based on a multi-carrier radio network temporary identifier, which is defined to scramble a cyclic redundancy check (CRC) of the single DCI. The single DCI may have a special format such that each DCI field is designed to indicate the scheduling of information for multiple scheduled cells, for example, such that the DCI field concurrently indicates the scheduling of information for multiple scheduled cells. The single DCI may be the result of a concatenation of individual DCIs, each corresponding to a different cell in the multiple cells.

[0007] The DCI field may include multiple carrier indicator (CI) fields, each of which corresponds to a different single cell in the multiple cells, or they may include a single CI field corresponding to each cell in the multiple cells. The mapping of the single CI field to the multiple cells may be configured by a serving base station serving the device, for example, via a radio resource control (RRC) signaling through a site. In some embodiments, the mapping may be updated via a medium access control (MAC) control element (CE). In some embodiments, the mapping of the single CI field to the multiple cells may be predetermined for each scheduled cell in the multiple cells, for example, it may be hard-coded in the 3GPP standard.

[0008] The DCI field may include multiple bandwidth part (BWP) indicator (BWPI) fields, where each BWPI field corresponds to a different single cell in the multiple cells, or they may include a single BWPI field corresponding to each cell in the multiple cells. The device may switch to the BWP indicated by the BWPI field on each cell in the multiple cells, or it may switch to the BWP indicated by the BWPI field only on a single cell. The single BWPI field may be mapped to multiple BWPs, where the mapping between the BWPI field and the BWP in each cell in the multiple cells is predetermined or configured by the serving base station, for example, via RRC signaling.

[0009] The same frequency domain resource allocation (FDRA) type may be configured for each of the multiple cells, or a different FDRA type may be configured for each of the multiple cells. Thus, the DCI field may include multiple FDRA fields, each of which corresponds to a different single cell in the multiple cells, or they may include a single FDRA field corresponding to each of the multiple cells. In some embodiments, the size of the first active BWP indicated by the FDRA field for the first cell in the multiple cells may be different from the size of the second active BWP indicated by the FDRA field for the second cell in the multiple cells. In some embodiments, when fewer bits are required to indicate the FDRA in the second BWP than in the first BWP, one or more most significant bits of the FDRA field may be discarded. Similarly, when more bits are required to indicate the FBRA in the second BWP than in the first BWP, one or more zero bits may be appended to the most significant bit.

[0010] The DCI field may include multiple time domain resource allocation (TDRA) fields, each of which corresponds to a different single cell in the multiple cells, or they may include a single TDRA field corresponding to each cell in the multiple cells. The single TDRA field may indicate the same TDRA for each cell in the multiple cells, or it may indicate the first TDRA of the first cell in the multiple cells, and the second TDRA of the second cell in the multiple cells may be derived from the first TDRA. The derivation of the second TDRA from the first TDRA may be configured via RRC (e.g., by the serving base station via RRC signaling). In some embodiments, the second TDRA may be derived via an offset of the starting symbol, and the mapping type and / or duration of the scheduled physical data channel may be the same for each cell in the multiple cells. In some embodiments, the corresponding TDRA value for each cell may be obtained from a TDRA table indexed by the value indicated in the single TDRA field.

[0011] The DCI field may include multiple transmission configuration indication (TCI) fields, each of which corresponds to a different single cell in the multiple cells, or they may include a single TCI field corresponding to each cell in the multiple cells. For each cell in the multiple cells, the device may use a TCI state index indicated by the TCI field, or a quasi-co-located (QCL) source, which is configured as the TCI state indicated by the TCI state index in the TCI field for a given cell in the multiple cells. The given cell may be determined according to a specified attribute of the given cell (e.g., a scheduled cell specified as having the smallest cell ID in the 3GPP specification), or may be determined according to an indication received by the device from a serving base station, for example, via RRC / MAC-CE / DCI signaling. The corresponding TCI state of each cell in the multiple cells may be obtained from a TCI table indexed by the value indicated in the single TCI field. In some embodiments, when the offset between the single DCI and the corresponding scheduled physical data channel is less than a specified threshold, the device may be for each of the multiple cells Use a default beam. The default beam may be defined by the TCI state of the control resource set (CORESET) with the lowest identifier (ID) in the last DCI monitoring slot, the TCI state of the CORESET with the lowest ID, or the active TCI of the corresponding scheduled physical data channel on each cell with the lowest ID. When the device cannot simultaneously receive on multiple beams configured for the device, the device may use the beam scheduled for the cell with the lowest identifier, or it may use a beam determined by the device itself (e.g., the device may be implemented to determine which beam to use in such a scenario).

[0012] The DCI field may include multiple antenna port (AP) fields, where each AP field corresponds to a different single cell in the multiple cells, or they may include an AP field corresponding to each cell in the multiple cells. When a single AP field is used, the device can be scheduled with the same port configuration on each of the multiple cells. When the number of bits used to indicate the AP for one scheduled physical data channel is different from the number of bits used to indicate the AP for another scheduled physical data channel, one or more most significant bits in the AP field may be padded or truncated. The single AP field may indicate a single AP configuration, and different code division multiplexing groups may be used to map to each different cell in the multiple cells.

[0013] The DCI field may include multiple coding and modulation scheme / new data indicator / redundancy version (MCS / NDI / RV) fields, where each MCS / NDI / RV field corresponds to a different single cell in the multiple cells, or they may include a single MCS / NDI / RV field corresponding to each cell in the multiple cells. When a single MCS / NDI / RV field is used, the device may be scheduled with the same transport block (TB) configuration on each cell in the multiple cells. In some embodiments, the MCS / NDI / RV for the first codeword may correspond to a first physical data channel scheduled on a first cell in the multiple cells, and the MCS / NDI / RV for the second codeword may correspond to a second physical data channel scheduled on a second cell in the multiple cells.

[0014] Note that the techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, base stations, access points, cellular telephones, portable media players, tablet computers, wearable devices, and various other computing devices.

[0015] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects, and advantages of the topics described herein will become apparent through the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 illustrates an exemplary (and simplified) wireless communication system according to some embodiments;

[0017] Figure 2illustrates an exemplary base station in communication with an exemplary wireless user equipment (UE) device according to some embodiments;

[0018] Figure 3 illustrates an exemplary block diagram of a UE according to some embodiments;

[0019] Figure 4 illustrates an exemplary block diagram of a base station according to some embodiments;

[0020] Figure 5 shows an exemplary simplified block diagram of an exemplary cellular communication circuit according to some embodiments;

[0021] Figure 6 An exemplary table showing DCI fields and the corresponding communication parameters for which they provide indication / information;

[0022] Figure 7 An exemplary table including a carrier indicator field in a DCI for scheduling physical data channels on multiple cells / component carriers using a single DCI is shown according to some embodiments;

[0023] Figure 8 An exemplary table including a bandwidth fraction indicator field in a DCI for scheduling physical data channels on multiple cells / component carriers using a single DCI is shown according to some embodiments; and

[0024] Fig. 9 shows an exemplary diagram illustrating an offset-based time-domain resource allocation DCI format for scheduling physical data channels on multiple cells / component carriers using a single DCI according to some embodiments;

[0025] Fig.10 An exemplary table including a time domain resource allocation field in a DCI for scheduling physical data channels on multiple cells / component carriers using a single DCI is shown according to some embodiments;

[0026] Fig.11 An exemplary table including a transmit configuration indication field in a DCI for scheduling physical data channels on multiple cells / component carriers using a single DCI is shown according to some embodiments; and

[0027] Fig.12 An exemplary flow chart illustrating a method of scheduling physical data channels across multiple cells according to some embodiments is shown.

[0028] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to be limited to the specific forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0029] Acronyms

[0030] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms used that may appear throughout this patent application are as follows:

[0031] 5GMM: 5G mobility management

[0032] AF: Application Function

[0033] ●AMF: Access and mobility management function

[0034] AMR: Adaptive Multi-Rate

[0035] AP: Access point

[0036] ●APN: Access Point Name

[0037] APR: Application Processor

[0038] BS: Base Station

[0039] BSSID: Basic Service Set Identifier

[0040] ●CBG: Code Block Group

[0041] ●CBRS: Citizens Broadband Radio Service

[0042] ●CBSD: Citizens Broadband Radio Service Device ●CCA: Clear Channel Assessment

[0043] ●CMR: Change Mode Request

[0044] CORESET: Control resource set

[0045] CS: Circuit Switched

[0046] ●CSI: Channel State Information

[0047] ●DCI: Downlink Control Information

[0048] DL: Downlink (from BS to UE)

[0049] DMRS: Demodulation Reference Signal

[0050] DN: Data Network

[0051] DSDS: Dual SIM Dual Standby

[0052] DYN: Dynamic

[0053] ●EDCF: Enhanced Distributed Coordination Function ●eSNPN: Equivalent Standalone Non-Public Network

[0054] ETSI: European Telecommunications Standards Institute

[0055] FDD: Frequency Division Duplex

[0056] FT: frame type

[0057] ●GAA: General Authorization Access

[0058] ●GPRS: General Packet Radio Service

[0059] GSM: Global System for Mobile Communications

[0060] GTP: GPRS Tunneling Protocol

[0061] ●HPLMN: Home Public Land Mobile Network ●IC: Within Coverage

[0062] ●IMS: Internet Protocol Multimedia Subsystem ●IOT: Internet of Things

[0063] IP: Internet Protocol

[0064] ITS: Intelligent Transportation System

[0065] LAN: Local Area Network

[0066] LBT: Listen before speaking

[0067] LCS: Location Services

[0068] LMF: Location Management Function

[0069] LPP: LTE Positioning Protocol

[0070] LQM: Link Quality Metric

[0071] LTE: Long Term Evolution

[0072] ●MCC: Mobile Country Code

[0073] MCS: Modulation and Coding Scheme

[0074] MNO: Mobile Network Operator

[0075] ●MO-LR: Mobile station calling location request ●MT-LR: Mobile station called location request ●NAS: Non-access stratum

[0076] NDI: New Data Indicator

[0077] NF: Network Function

[0078] ●NG-RAN: Next Generation Radio Access Network ●NID: Network Identifier

[0079] NMF: Network Identifier Management Function

[0080] NPN: Non-Public (Cellular) Network

[0081] NRF: Network Repository Function

[0082] NSI: Network Slicing Example

[0083] ●NSSAI: Network Slice Selection Assistance Information ●OOC: Out of Coverage

[0084] ●PAL: Priority Access Licensee

[0085] ●PDCP: Packet Data Convergence Protocol

[0086] ●PDN: Packet Data Network

[0087] ●PDU: Protocol Data Unit

[0088] PGW: PDN Gateway

[0089] ●PLMN: Public Land Mobile Network

[0090] ProSe: Proximity Services

[0091] PRS: Positioning Reference Signal

[0092] ●PSCCH: Physical Sidelink Control Channel

[0093] ●PSFCH: Physical side link feedback channel

[0094] ●PSSCH: Physical side link shared channel

[0095] PSD: Power Spectral Density

[0096] PSS: Primary Synchronization Signal

[0097] PT: Payload Type

[0098] PTRS: Phase Tracking Reference Signal

[0099] ●PUCCH: Physical Uplink Control Channel ●QBSS: Basic Service Set with Quality of Service Enhancement ●QI: Quality Indicator

[0100] RA: Registration Accepted

[0101] RAT: Radio Access Technology

[0102] RF: Radio Frequency

[0103] ●RNTI: Radio Network Temporary Identifier

[0104] ●ROHC: Robust Header Compression

[0105] RR: Registration Request

[0106] ●RRC: Radio Resource Control

[0107] RS: Reference signal

[0108] RSRP: Reference Signal Received Power

[0109] RTP: Real-time Transport Protocol

[0110] RV: Redundancy Version

[0111] RX: Receive / Receive

[0112] SAS: Spectrum Allocation Server

[0113] ●SD: Slice Descriptor

[0114] SI: System Information

[0115] SIB: System Information Block

[0116] SID: System identification number

[0117] SIM: Subscriber Identity Module

[0118] SGW: Serving Gateway

[0119] SMF: Session Management Function

[0120] ●SNPN: Independent Non-Public Network

[0121] ●SRS: Sounding Reference Signal

[0122] ●SSS: Secondary synchronization signal

[0123] SUPI: Subscription Permanent Identifier

[0124] TBS: Transport Block Size

[0125] ●TCP: Transmission Control Protocol

[0126] ●TDD: Time Division Duplex

[0127] ●TDRA: Time Domain Resource Allocation

[0128] ●TPC: Transmit Power Control

[0129] TX: Send / Send

[0130] UAC: Unified Access Control

[0131] UDM: unified data management

[0132] UDR: User Data Repository

[0133] UE: User Equipment

[0134] UI: User input

[0135] UL: Uplink (from UE to BS)

[0136] UMTS: Universal Mobile Telecommunications System

[0137] UPF: User plane function

[0138] URM: Universal Resource Management

[0139] URSP: UE routing strategy

[0140] ●USIM: User Subscriber Identity Module

[0141] Wi-Fi: Wireless local area network (WLAN) RAT based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard

[0142] WLAN: Wireless LAN

[0143] ZP: Zero Power

[0144] the term

[0145] The following is a glossary of terms that will appear in this application:

[0146] Memory medium—any of the various types of memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media, such as hard disk drives or optical storage devices; registers, or other similar types of memory elements, etc. The memory medium may also include other types of memory or a combination thereof. In addition, the memory medium may be located in a first computer system executing a program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter example, the second computer system may provide program instructions to the first computer system for execution. The term "memory medium" may include two or more memory media, which may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., embodied as a computer program) that may be executed by one or more processors.

[0147] Carrier Media—Memory media as described above, as well as physical transmission media such as a bus, network, and / or other physical transmission media that convey signals such as electrical, electromagnetic, or digital signals.

[0148] Programmable hardware element - includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can range from fine-grained (combinational logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0149] Computer system (or computer)—any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" may be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0150] User Equipment (UE) (or "UE device") - any of various types of computer system devices that perform wireless communications. Also referred to as wireless communication devices, many of which may be mobile and / or portable. Examples of UE devices include mobile phones or smart phones (e.g., iPhoneTM , based on Android TM phones) and tablets such as iPads TM 、Samsung Galaxy TM etc., gaming devices (such as Sony PlayStation TM , Microsoft XBox TM etc.), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPod TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, unmanned aerial vehicles (e.g., drones) and drone controllers, etc. Various other types of devices that include Wi-Fi communication capabilities or both cellular and Wi-Fi communication capabilities and / or other wireless communication capabilities (e.g., via short-range radio access technologies (SRAT) such as Bluetooth TM In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) capable of wireless communication and which may also be portable / mobile.

[0151] Wireless device (or wireless communication device) - any of various types of computer system devices that perform wireless communication using WLAN communication, SRAT communication, Wi-Fi communication, etc. As used herein, the term "wireless device" may refer to a UE device as defined above or a fixed device such as a fixed wireless client or a wireless base station. For example, a wireless device may be a wireless station of any type of 802.11 system, such as an access point (AP) or a client station (UE), or a wireless station of any type of cellular communication system that communicates according to a cellular radio access technology (e.g., 5G NR, LTE, CDMA, GSM), such as a base station or a cellular phone.

[0152] Communication device - any of various types of computer systems or devices that perform communication, where the communication may be wired or wireless. A communication device may be portable (or mobile), or may be stationary or fixed at a location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0153] Base Station (BS)—The term "base station" has the full breadth of its ordinary meaning and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0154] Processor – refers to various elements (e.g., circuits) or combinations of elements that are capable of performing functions in a device (e.g., in a user equipment device or in a cellular network device). Processors may include, for example: general purpose processors and associated memory, portions or circuits of individual processor cores, entire processor cores or processing circuit cores, processing circuit arrays or processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any various combinations of the above.

[0155] Channel - a medium used to convey information from a transmitter (sender) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" as used herein may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0156] Band (or frequency band)—The term "band" has the full range of its usual meaning and includes at least a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose. In addition, "band" is used to refer to any interval in the frequency domain defined by a lower frequency and a higher frequency. The term may refer to a radio frequency band or an interval of some other spectrum. A radio communication signal may occupy a frequency range that carries the signal (or the signal is carried within this frequency range). Such a frequency range is also referred to as the bandwidth of the signal. Therefore, bandwidth refers to the difference between the upper and lower frequencies in a continuous frequency band. A band may represent a communication channel, or it may be subdivided into multiple communication channels. The allocation of radio frequency ranges for different purposes is the main function of radio spectrum allocation. For example, in 5G NR, the operating bands are classified into two groups. More specifically, according to 3GPP Release 15, bands are designated for different frequency ranges (FRs) and are defined as FR1 and FR2, where FR1 covers the 410MHz-7125MHz range and FR2 covers the 24250MHz-52600MHz range.

[0157] Wi-Fi—The term "Wi-Fi" has the full scope of its usual meaning and includes at least wireless communication networks or RATs that are served by wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi". Wi-Fi (WLAN) networks are distinct from cellular networks.

[0158] Automatically—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for the action or operation to be directly specified or performed by a user input. Thus, the term "automatically" is in contrast to a user manually performing or specifying an action, wherein the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," wherein the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, wherein the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0159] Approximately - refers to a value that is close to a correct or exact value. For example, approximately can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, "approximately" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0160] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism", where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0161] Station (STA)—The term “station” herein refers to any device that has the ability to communicate wirelessly (e.g., by using the 802.11 protocol). A station may be a laptop, desktop PC, PDA, access point, or Wi-Fi phone, or any type of device similar to a UE. A STA may be fixed, mobile, portable, or wearable. Generally speaking, in wireless networking terminology, a station (STA) broadly encompasses any device that has wireless communication capabilities, and the terms station (STA), wireless client (UE), and node (BS) are therefore often used interchangeably.

[0162] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having a structure” that performs one or more tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” may be a broad statement that generally means “having a structure” that performs one or more tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently turned on. Typically, circuitry that forms a structure corresponding to “configured to” may include hardware circuitry.

[0163] Transmission scheduling - refers to the scheduling of transmissions (such as wireless transmissions). In some specific implementations of cellular radio communications, signal transmissions and data transmissions can be organized according to specified time units of a specific duration during which the transmission occurs. As used herein, the term "time slot" has the full range of its usual meaning and refers at least to the minimum (or shortest) scheduling time unit in wireless communication. For example, in 3GPP LTE, transmissions are divided into radio frames, each of which has an equal (time) duration (e.g., 10ms). The radio frames in 3GPP LTE can be further divided into a specified number (e.g., ten) of subframes, each of which has an equal duration, and the subframes are designated as the minimum (shortest) scheduling unit, or a specified time unit for transmission. Therefore, in the 3GPP LTE example, "subframe" can be regarded as an example of "time slot" as defined above. Similarly, the minimum (or shortest) scheduling time unit for 5G NR (or simply NR) transmission is called a "time slot". In different communication protocols, the minimum (or shortest) scheduling time unit may also be named differently.

[0164] Resource - The term "resource" has the full range of its usual meaning and may refer to frequency resources and time resources used during wireless communication. As used herein, a resource element (RE) refers to a specific amount or number of resources. For example, in the context of time resources, a resource element may be a time period of a specific length. In the context of frequency resources, a resource element may be a specific frequency bandwidth centered on a specific frequency or a specific amount of frequency bandwidth. As a specific example, a resource element may refer to a resource unit having 1 symbol (referenced to time resources, such as a time period of a specific length) per 1 subcarrier (referenced to frequency resources, such as a specific frequency bandwidth, which may be centered on a specific frequency). A resource element group (REG) has the full range of its usual meaning and refers to at least a specified number of consecutive resource elements. In some implementations, a resource element group may not include resource elements reserved for reference signals. A control channel element (CCE) refers to a group of a specified number of consecutive REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per a specified number of symbols. Each RB may include a specified number of subcarriers. A resource block group (RBG) refers to a unit including multiple RBs. The number of RBs within one RBG may vary according to the system bandwidth.

[0165] Bandwidth Part (BWP) - A carrier Bandwidth Part (BWP) is a contiguous set of physical resource blocks selected from a contiguous subset of common resource blocks for a given parameter set on a given carrier. For the downlink, the UE may be configured with up to a specified number of carrier BWPs (e.g., four BWPs per some specifications), with one BWP active per carrier at a given time (per some specifications). For the uplink, the UE may similarly be configured with up to a number (e.g., four) of carrier BWPs, with one BWP active per carrier at a given time (per some specifications). If the UE is configured with a supplemental uplink, the UE may additionally be configured with up to a specified number (e.g., four) of carrier BWPs in the supplemental uplink, with one carrier BWP active at a given time (per some specifications).

[0166] Multi-cell arrangement—a master node is defined as a node (radio access node) that provides a control plane connection to the core network in the case of multi-radio dual connectivity (MR-DC). The master node can be, for example, a master eNB (3GPP LTE) or a master gNB (3GPP NR). A secondary node is defined as a radio access node that does not have a control plane connection to the core network, providing additional resources to the UE in the case of MR-DC. A master cell group (MCG) is defined as a group of service cells associated with a master node, including a primary cell (PCell) and optionally one or more secondary cells (SCells). A secondary cell group (SCG) is defined as a group of service cells associated with a secondary node, including a special cell, i.e., the primary cell (PSCell) of the SCG, and optionally one or more SCells. The UE can generally apply radio link monitoring to the PCell. If the UE is configured with an SCG, the UE can also apply radio link monitoring to the PSCell. Radio link monitoring is generally applied to active BWPs, and the UE does not need to monitor inactive BWPs. The PCell is used to initiate initial access, and the UE can communicate with the PCell and SCell via carrier aggregation (CA). The currently modified capabilities mean that the UE can receive and / or transmit to and / or from multiple cells. The UE initially connects to a PCell, and once the UE is in a connected state, one or more SCells may be configured for the UE.

[0167] Core Network (CN) - The core network is defined as a part of the 3GPP system that is independent of the UE's connection technology (e.g., radio access technology, RAT). A UE can connect to the core network via a radio access network RAN, which can be RAT-specific.

[0168] Downlink Control Information (DCI) - In 3GPP communications, DCI is sent to a mobile device or UE (e.g., by a serving base station in the network) and contains a number of different fields. Each field is used to configure a portion or aspect of the scheduled communication of the device. In other words, each field in the DCI may correspond to one or more specific communication parameters that configure the corresponding aspect of the scheduled communication of the device. By decoding the DCI, the UE obtains all configuration parameters or parameter values ​​according to the fields in the DCI, thereby obtaining all information about the scheduled communication, and then performs the scheduled communication according to those parameters / parameter values.

[0169] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke the sixth paragraph of Section 112 of Title 35 of the United States Code on that component.

[0170] Figure 1 and Figure 2 —Exemplary Communication System

[0171] Figure 1 An exemplary (and simplified) wireless communication system according to some embodiments is illustrated. Note that Figure 1 The system is only one example of a possible system, and the embodiments may be implemented in any of a variety of systems as desired.

[0172] As shown, the exemplary wireless communication system includes base stations 102A to 102N, also collectively referred to as multiple base stations 102 or base stations 102. Figure 1 As shown, base station 102A communicates with one or more user equipment 106A to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE) or a UE device. Therefore, user equipment 106A to 106N are referred to as UEs or UE devices, and are also collectively referred to as multiple UEs 106 or UEs 106.

[0173] The base station 102A may be a base transceiver station (BTS) or a cell site, and may include hardware that enables wireless communication with UEs 106A to 106N. The base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN) and / or the Internet, a neutral host or various CBRS (Citizen Broadband Radio Service) deployments, and various possibilities). Thus, the base station 102A may facilitate communication between user devices 106 and / or between user devices 106 and the network 100. Specifically, the cellular base station 102A may provide UEs 106 with various communication capabilities such as voice, short message service (SMS) and / or data services. The communication area (or coverage area) of the base station 106 may be referred to as a "cell". Note that a "cell" may also refer to a logical identifier for a given wireless communication coverage area at a given frequency. In general, any independent cellular wireless coverage area may be referred to as a "cell". In such a case, the base station may be located at a specific intersection of three cells. In this uniform topology, a base station may serve three 120 degree beam width areas called cells. Moreover, for carrier aggregation, small cells, relays, etc. may all represent cells. Therefore, particularly in carrier aggregation, there may be primary cells and secondary cells that may serve at least partially overlapping coverage areas but at different corresponding frequencies. For example, a base station may serve any number of cells, and the cells served by a base station may or may not be collocated (e.g., a remote radio head). Also as used herein, with respect to a UE, a base station may sometimes be considered to represent a network, taking into account the uplink and downlink communications of the UE. Therefore, a UE communicating with one or more base stations in a network may also be interpreted as a UE communicating with the network, and may also be considered to be at least a part of a UE communicating on or through a network.

[0174] The base station 102 and the user equipment 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (WCDMA), LTE, Advanced LTE (LTE-A), LAA / LTE-U, 5G-NR (abbreviated as NR), 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. It should be noted that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Similarly, if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB". In some embodiments, the base station 102 (e.g., an eNB in ​​an LTE network or a gNB in ​​an NR network) may communicate with at least one UE that has the capability to transmit reference signals according to various embodiments disclosed herein. Depending on a given application or specific considerations, for convenience, some different RATs may be functionally grouped according to overall defining characteristics. For example, all cellular RATs may be collectively considered to represent a first (form / type) RAT, while Wi-Fi communications may be considered to represent a second RAT. In other cases, individual cellular RATs may be individually considered to be different RATs. For example, when distinguishing between cellular communications and Wi-Fi communications, "first RAT" may collectively refer to all cellular RATs considered, while "second RAT" may refer to Wi-Fi. Similarly, when applicable, different forms of Wi-Fi communications (e.g., over 2.4 GHz vs. over 5 GHz) may be considered to correspond to different RATs. In addition, cellular communications performed according to a given RAT (e.g., LTE or NR) may be distinguished from each other based on the spectrum in which those communications are performed. For example, LTE or NR communications may be performed on a primary licensed spectrum as well as on an auxiliary spectrum such as an unlicensed spectrum and / or spectrum allocated to a private network. In general, the use of various terms and expressions will always be clearly indicated in relation to the context of the various applications / implementations considered and in that context.

[0175] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., in various possibilities, a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet). Thus, the base station 102A may facilitate communication between user devices 106 and / or between user devices 106 and the network 100. Specifically, the cellular base station 102A may provide UE 106 with various communication capabilities such as voice, SMS, and / or data services. The UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using any or all of a 3GPP cellular communication standard (such as LTE or NR) or a 3GPP2 cellular communication standard (such as a cellular communication standard in the CDMA2000 family of cellular communication standards). Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as one or more cell networks, which can provide continuous or nearly continuous overlapping services to UE 106 and similar devices over a wide geographic area via one or more cellular communication standards.

[0176] Thus, although base station 102A may function as Figure 1 106A-106N, but each UE 106 may also be able to receive signals from (and possibly be within communication range of) one or more other cells (possibly provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be able to facilitate communications between user devices 106 and / or between user devices 106 and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity of service area size. For example, in Figure 1 The base stations 102A-102B illustrated in FIG. 1 may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0177] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB". In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. In addition, a gNB cell may include one or more transmit and receive points (TRPs). In addition, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0178] UE 106 may also or alternatively be configured to use WLAN, Bluetooth TM,Bluetooth TM The UE 106 may communicate with the network 100 through one or more base stations or through other devices, stations, or any apparatus not explicitly shown but considered to be part of the network 100. Therefore, the UE 106 communicating with the network may be interpreted as the UE 106 communicating with one or more network nodes that are considered to be part of the network, and may interact with the UE 106 to communicate with the UE 106, and in some cases affect at least some communication parameters and / or the use of communication resources of the UE 106.

[0179] For example, Figure 1 As shown in , at least some UEs (e.g., UE 106D and 106E) may represent vehicles that communicate with each other and with base station 102, for example, via cellular communications such as 3GPP LTE and / or 5G-NR communications. In addition, UE 106F may represent pedestrians that are communicating and / or interacting with the vehicles represented by UEs 106D and 106E in a similar manner. For example, in the context of vehicle-to-everything (V2X) communications (such as communications specified by certain versions of 3GPP standards, etc.), the disclosed Figure 1 Various embodiments of vehicles communicating in a network illustrated in FIG.

[0180] Figure 2 An exemplary user equipment 106 (e.g., one of UEs 106A to 106N) is illustrated in communication with base station 122 and access point 112 according to some embodiments. UE 106 may be a user equipment having cellular communication capabilities and non-cellular communication capabilities (e.g., Bluetooth TM, Wi-Fi, etc.), such as a mobile phone, a handheld device, a computer or a tablet computer, or almost any type of wireless device. UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may execute any method implementation in the method implementation scheme described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to execute any of the method implementation schemes described herein or any part of any of the method implementation schemes described herein. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0181] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards, such as those previously described above. In some embodiments, UE 106 may share one or more portions of a receive chain and / or a transmit chain between multiple wireless communication standards. The shared radio component may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, UE 106 may include an independent transmit chain and / or receive chain (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another alternative, UE 106 may include one or more radio components or radio circuits shared between multiple wireless communication protocols, as well as one or more radio components used exclusively by a single wireless communication protocol. For example, UE 106 may include a radio circuit for communicating using any of LTE or CDMA2000 1xRTT or NR, as well as a radio circuit for communicating using Wi-Fi and Bluetooth. TM Each of the independent radio components for communication. Other configurations are also possible.

[0182] Figure 3 —Block diagram of an exemplary UE

[0183] Figure 3A block diagram of an exemplary UE 106 according to some embodiments is illustrated. As shown, the UE 106 may include a system on chip (SOC) 300, which may include various elements / components for various purposes. For example, as shown, the SOC 300 may include a processor 302 that can execute program instructions for the UE 106, and a display circuit 304 that can perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuits or devices (such as display circuit 304, radio circuit 330, connector I / F 320 and / or display 360), which may be configured to receive addresses from the processor 302 and convert those addresses to locations in a memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table conversion or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0184] As shown, SOC 300 may be coupled to various other circuits of UE 106. For example, UE 106 may include various types of memory (e.g., including NAND flash memory 310), a connector interface 320 (e.g., for coupling to a computer system), a display 360, and wireless communication circuits (e.g., for LTE, LTE-A, NR, CDMA2000, Bluetooth TM , Wi-Fi, GPS, etc.). The UE device 106 may include at least one antenna (e.g., 335a), and may include multiple antennas (e.g., illustrated by antennas 335a and 335b) for performing wireless communications with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and the UE device 106 may include fewer or more antennas. In general, one or more antennas are collectively referred to as antennas 335. For example, the UE device 106 may use antenna 335 to perform wireless communications with the aid of radio circuitry 330. As mentioned above, in some embodiments, the UE may be configured to perform wireless communications using multiple wireless communication standards.

[0185] As further described herein, the UE 106 (and / or the base station 102) may include hardware and software components for implementing methods for at least the UE 106 to send reference signals according to various embodiments described herein. The processor 302 of the UE device 106 may be configured to implement part or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). In addition, the processor 302 may be coupled to a processor such as a processor 102 or a processor 102. Figure 3 The other components shown and / or may interoperate with other components to implement communication through the UE 106 for sending a reference signal according to various embodiments disclosed herein. In particular, the processor 302 may be coupled to Figure 3 The other components shown in and / or may interoperate with other components to facilitate UE 106 to communicate in a manner that attempts to optimize RAT selection. Processor 302 may also implement various other applications and / or end-user applications running on UE 106.

[0186] In some embodiments, the radio circuit 330 may include a separate controller dedicated to controlling communications for various corresponding RATs and / or RAT standards. Figure 3 As shown, the radio circuit 330 may include a Wi-Fi controller 356, a cellular controller (e.g., an LTE and / or NR controller) 352, and a Bluetooth controller. TM Controller 354, and according to at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (referred to as ICs or chips) that communicate with each other and with SOC 300 (e.g., with processor 302). For example, Wi-Fi controller 356 may communicate with cellular controller 352 via a cell-ISM link or WCI interface, and / or Bluetooth TM The controller 354 may communicate with the cellular controller 352 via a cell-ISM link or the like. Although three separate controllers are illustrated within the radio circuit 330, other embodiments may have fewer or more similar controllers for various different RATs and / or RAT standards that may be implemented in the UE device 106. For example, in Figure 5 At least one exemplary block diagram illustrating some embodiments of the cellular controller 352 is shown in FIG. 1 and will be further described below.

[0187] Figure 4 —Block diagram of an exemplary base station

[0188] Figure 41 illustrates a block diagram of an exemplary base station 102 according to some embodiments. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0189] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the telephone network described above. Figure 1 and Figure 2 106. The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0190] The base station 102 may include at least one antenna 434a, and may include multiple antennas (e.g., illustrated by antennas 434a and 434b) for performing wireless communications with mobile devices and / or other devices. Antennas 434a and 434b are shown as examples, and the base station 102 may include fewer or more antennas. In general, one or more antennas that may include antenna 434a and / or antenna 434b are collectively referred to as antenna 434 or multiple antennas 434. Antenna 434 may be configured to operate as a wireless transceiver, and may be further configured to communicate with UE device 106 via radio circuit 430. Antenna 434 communicates with the radio component 430 via communication chain 432. Communication chain 432 may be a receiving chain, a transmitting chain, or both. Radio circuit 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to LTE, LTE-A, 5G-NR (NR), WCDMA, CDMA2000, etc. The processor 404 of the base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit) or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), the base station 102 may be designed as an access point (AP), in which case the network port 470 may be implemented to provide access to a wide area network and / or one or more local area networks, for example, it may include at least one Ethernet port, and the radio component 430 may be designed to communicate according to the Wi-Fi standard.

[0191] Figure 5 —Exemplary Cellular Communications Circuit

[0192] Figure 5 0 illustrates an exemplary simplified block diagram of an exemplary cellular controller 352 according to some embodiments. Note that Figure 5 The block diagram of the cellular communication circuitry of is only one example of possible cellular communication circuitry; other circuitry, such as circuitry that includes or is coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, or circuitry that includes or is coupled to fewer antennas, such as circuitry that may be shared between multiple RATs, is also possible. According to some embodiments, the cellular communication circuitry 352 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0193] The cellular communication circuitry 352 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-335b and 336 as shown. In some embodiments, the cellular communication circuitry 352 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuit 352 may include a first modem 510 and a second modem 520. The first modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured for communication according to a second RAT (e.g., such as 5GNR).

[0194] As shown, the first modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for sending and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0195] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for sending and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0196] In some embodiments, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 352 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the first modem 510, the switch 570 may be switched to a first state that allows the first modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 352 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the second modem 520, the switch 570 may be switched to a second state that allows the second modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0197] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processors 512, 522 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processors 512, 522 may be configured as programmable hardware elements, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336, the processors 512, 522 may be configured to implement part or all of the features described herein.

[0198] In addition, as described herein, the processors 512, 522 may include one or more components. Therefore, the processors 512, 522 may include one or more integrated circuits (ICs) configured to perform the functions of the processors 512, 522. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processors 512, 522.

[0199] In some embodiments, the cellular communication circuit 352 may include only one transmit / receive chain. For example, the cellular communication circuit 352 may not include the modem 520, the RF front end 540, the DL front end 560, and / or the antenna 335b. As another example, the cellular communication circuit 352 may not include the modem 510, the RF front end 530, the DL front end 550, and / or the antenna 335a. In some embodiments, the cellular communication circuit 352 may also not include the switch 570, and the RF front end 530 or the RF front end 540 may communicate with the UL front end 572 (e.g., directly).

[0200] Physical Data Channel Scheduling

[0201] In current 3GPP NR standards including Rel-15 / 16 / 17, a single DCI can be used to schedule a physical data channel (e.g., PDSCH) on only one cell, or in other words, on a single cell or component carrier. The scheduled cell is indicated by the "carrier indicator" field in the DCI. The mapping of the "carrier indicator" field value to the actual cell is configured by the radio resource control (RRC) and is performed per scheduled cell. As part of implementing multi-carrier enhancements, an agreement was reached to support enhancements to schedule physical data channels (e.g., PDSCH / PUSCH) for devices on multiple cells using a single downlink control information (DCI). This single DCI scheduling solution for physical data channels on multiple cells is expected to take into account:

[0202] • Identify the maximum number of cells that can be scheduled concurrently;

[0203] ● Considering both intra-band and inter-band carrier aggregation (CA) operations;

[0204] • Considering both frequency range 1 (FR1) and frequency range 2 (FR2); and

[0205] • Optimizing a single DCI for three or more cells for multi-cell PUSCH / PDSCH scheduling.

[0206] The motivation for scheduling multiple cells with a single DCI is to reduce PDCCH overhead, e.g., reduce DCI size. However, except for a few DCI fields such as CRC (Cyclic Redundancy Check), using a single DCI for scheduling on multiple cells (e.g., physical data channels) leads to a tradeoff between scheduling flexibility and DCI size reduction. To evaluate this issue, at least one needs to consider Figure 6 DL DCI fields shown in the table. Figure 6The various DCI fields shown in the table of each correspond to a respective communication parameter or operating parameter related to scheduling communications (e.g., physical data channel communications) for a given device (UE) on a cell (or in this case on multiple cells).

[0207] In various embodiments, the design choices for a single DCI for scheduling PDSCH (communication) on multiple cells may include specific considerations for:

[0208] ●Carrier indicator;

[0209] Bandwidth Part (BWP) indicator;

[0210] Frequency Domain Resource Allocation (FDRA);

[0211] ●Time Domain Resource Allocation (TDRA);

[0212] ● Transmit Configuration Indication (TCI);

[0213] Antenna ports; and

[0214] ● Modulation and coding scheme (MCS), new data indicator (NDI), redundancy version (RV) indication.

[0215] DCI format indication

[0216] According to the first proposal, a new DCI may be defined based on a new Radio Network Temporary Identifier (RNTI).A new RNTI (eg, MC (Multi-Carrier)-RNTI) may be defined to scramble the CRC of a DCI that schedules multiple cells concurrently.

[0217] According to the second proposal, a new DCI format may be defined for scheduling physical data channels for devices on multiple cells via a single DCI. For example, a new "DCI format 1_3" may be established. According to the new format, each DCI field in the new DCI may be designed to indicate the scheduling of information for multiple scheduled cells, such as concurrently indicating the scheduling of information for multiple scheduled cells.

[0218] According to the third proposal, existing DCI formats can be used, and the concatenation of existing DCI formats (e.g., "DCI format 1_2" or "DCI format 1_1") can be used to form a new DCI. When multiple cells are scheduled by a single DCI, the corresponding DCI field size can be independently configured for each scheduled cell. Individual DCIs corresponding to different cells (each DCI uses an existing DCI format) can then be concatenated or combined to form the final DCI.

[0219] Carrier indicator

[0220] According to the first proposal, multiple "carrier indicator" fields may be included in the DCI format. Each "carrier indicator" may correspond to a different scheduled cell.

[0221] According to the second proposal, a single "carrier indicator" field may be used to map to multiple scheduled cells. The network (e.g., via a serving base station) may configure the mapping of the "carrier indicator" field to the list of scheduled cells. The network configuration may be based on RRC. Potentially, the mapping configured by the network may be changed via MAC-CE. The mapping may also be predetermined, for example, hard-coded in a specification (e.g., a 3GPP specification) for each specific number ("N") of scheduled cells, where N>=1. Figure 7 An exemplary configuration is illustrated in the table of FIG.

[0222] BWP indicator

[0223] According to a first proposal, multiple "BWP indicators" may be included in the DCI format, wherein each "BWP indicator" corresponds to a different scheduled cell.

[0224] According to the second proposal, a single "BWP indicator" may be included in the DCI format. In the first option, the UE may switch to the BWP indicated by the "BWP indicator" field for all scheduled cells (in other words, for each scheduled cell). In the second option, the UE may switch to the BWP indicated by the "BWP indicator" field only on one of the scheduled (e.g., RRC configured) cells.

[0225] According to the third proposal, a single "BWP indicator" may be mapped to multiple BWPs. The mapping between the "BWP indicator" and the BWP in each scheduled cell may be RRC configured or predetermined, for example, hard-coded in the specification (eg, in the 3GPP specification). Figure 8 An exemplary configuration is illustrated in the table of FIG.

[0226] FDRA (Frequency Domain Resource Allocation)

[0227] According to the first proposal, at least two options are available for all cells scheduled by a single DCI. In the first option, the same allocation type can be configured for all cells, for example, one of resourceAllocation ENUMERATED{resourceAllocationType0, resourceAllocationType1, dynamicSwitch}. In the second option, different resource allocation types can be configured for each cell.

[0228] According to the second proposal, multiple “frequency domain resource allocation” DCI fields may be included in the DCI format, wherein each “frequency domain resource allocation” DCI field corresponds to a different scheduled cell.

[0229] According to the third proposal, a single "frequency domain resource allocation" DCI field may be included in the DCI format. In each scheduled cell, the UE may be scheduled with the same FDRA for the PDSCH. In this case, DCI size alignment may be considered, for example, when the size of the active BWP of different component carriers (CCs) is different. In other words, the size of the active BWP of one CC or cell may be different from the size of the active BWP of the second CC or cell, which may be taken into account with respect to how the FDRA DCI field is implemented. If the second CC or cell requires fewer bits in indicating the FDRA for the second CC or cell via a single FDRA DCI field, truncation may be applied, for example, the most significant bit (MSB) may be discarded. If the second CC or cell requires a higher number of bits in terms of FDRA indication, additional bits may be appended, for example, zeros may be appended to the MSB.

[0230] TDRA (Time Domain Resource Allocation)

[0231] According to the first proposal, multiple “time domain resource allocation” DCI fields may be included in the DCI format, wherein each “time domain resource allocation” DCI field corresponds to a different scheduled cell.

[0232] According to the second proposal, a single "time domain resource allocation" DCI field may be configured / included in the DCI format, and the UE may be scheduled with the same TDRA for PDSCH in all scheduled CCs. In this case, a single TDRA DCI field (or TDRA field) may correspond to each scheduled cell.

[0233] According to the third proposal, when a single TDRA field is used, a second TDRA can be derived from a first TDRA configured via RRC (e.g., in the case of two cells / CCs). For example, the second TDRA can be derived via an offset of the starting symbol. In other words, the second TDRA can be derived from the difference between the starting symbol of the PDSCH scheduled on the first CC or cell and the starting symbol of the PDSCH scheduled on the second CC or cell (e.g., a value between 5.1 and 5.2). Therefore, the following may be the same between all scheduled CCs (e.g., all concurrently scheduled CCs):

[0234] ● mapping type, eg, mappingType ENUMERATED{typeA,typeB}; and

[0235] ● Duration of the PDSCH, eg, number of symbols.

[0236] Fig. 9 This concept is illustrated in the exemplary diagram of FIG.

[0237] According to the fourth proposal, a single TDRA DCI field may correspond to each scheduled cell, and the network may configure a TDRA table. In the TDRA table, for each "time domain resource allocation" code point or value of the TDRA DCI field, there may be a corresponding TDRA for each scheduled cell according to the table, for example, Fig.10 An exemplary code segment for configuring the TDRA table may be:

[0238]

[0239] TCI (Transmit Configuration Indicator)

[0240] According to the first proposal, multiple TCI fields may be included in the DCI format, each TCI field corresponding to a different scheduled cell.

[0241] According to the second proposal, a single TCI field may be included in the DCI format. Multiple TCI states may be configured for each CC or cell. Each TCI state may be configured with different QCL sources in different CCs. Therefore, in the first option, the UE may use the same TCI state index for each scheduled cell. In the second option, the UE may use the same QCL source for each scheduled cell, where the QCL source is configured as the TCI state indicated by the TCI state index in the TCI field for one of the scheduled cells. The scheduled cell for determining the QCL source for all scheduled cells may be specified (e.g., specified as the scheduled cell with the smallest cell ID in the 3GPP specification), or configured / indicated by the network (e.g., by the serving base station) via RRC / MAC-CE / DCI.

[0242] According to the third proposal, for a single DCI used to configure a physical data channel for a UE on three (3) different cells, the network may configure a mapping of TCI code points to TCI states (or a mapping of TCI field values ​​to TCI states) for each scheduled cell, as in, for example, Fig.11 as shown in the table.

[0243] According to the fourth proposal, when the offset between the DCI and the corresponding (scheduled) PDSCH is less than a specified threshold, the UE may use a default beam for each carrier. The default beam may be defined by one of the following:

[0244] ●TCI status of the CORESET with the lowest ID in the last DCI monitoring slot;

[0245] ●The TCI status of the CORESET with the lowest ID; or

[0246] • The active TCI for the PDSCH on each carrier with the lowest ID.

[0247] The fifth proposal may apply when multiple TCI fields are used or when a single TCI field is used. According to the fifth proposal, in the case where the multiple beams configured for the UE exceed the UE capabilities, for example, the UE cannot receive on the configured multiple beams simultaneously, the UE may use the beam of the scheduled cell with the lowest ID, or the UE may determine which beam to use based on a specific UE-based implementation (for example, the individual implementation of the UE may determine which beam the UE is to use in such a scenario).

[0248] Antenna Port

[0249] According to the first proposal, a fixed solution can be designed to handle the configuration of antenna ports. In the first option, multiple "antenna port" fields can be included in the DCI format, each "antenna port" field corresponding to a corresponding scheduled cell. In the second option, a single "antenna port" field can be introduced in the DCI format, where the UE is scheduled with the same port configuration on all CCs. If the antenna port bit width (the number of bits used to indicate the antenna port) is different for each PDSCH, for example due to mapping type A or type B, bit padding and / or bit truncation can be used at the MSB.

[0250] According to the second proposal, a single antenna port configuration may be signaled, where each CDM (code division multiplexing) group is used to map to a different (corresponding) scheduled cell / CC. For example, for up to three (3) CDM groups, the following mapping may be established:

[0251] ● The antenna ports in the first CDM group may correspond to the PDSCH of the first scheduled cell;

[0252] ● The antenna ports in the second CDM group may correspond to the PDSCH of the second scheduled cell;

[0253] and

[0254] • The antenna ports in the third CDM group may correspond to the PDSCH of the third scheduled cell.

[0255] Modulation and coding scheme / new data indicator / redundancy version indication

[0256] According to the first proposal, a fixed solution can be designed to handle the transport block (TB) configuration. In the first option, multiple MCS / NDI / RV fields can be included in the DCI format, each MCS / NDI / RV field corresponding to a corresponding different scheduled cell. For example, the MCS / NDI / RV of the PDSCH on each scheduled cell can be indicated independently. In the second option, a single MCS / NDI / RV field can be included in the DCI format, where the UE is scheduled with the same TB configuration on all scheduled CCs (or on all scheduled cells).

[0257] According to the second proposal, when a single DCI is used to schedule PDSCHs of multiple (e.g., two) cells, corresponding MCS / NDI / RV values ​​can be used for corresponding codewords of corresponding PDSCHs from different carriers / cells. For example, when a single DCI is used to schedule PDSCHs on two cells, the MCS / NDI / RV for the first codeword can correspond to the PDSCH on the first cell, and the MCS / NDI / RV for the second codeword can correspond to the PDSCH on the second cell. It should be noted that the 3GPP specification allows scheduling up to two codewords (because of more than 4 layers of MIMO operation), and each codeword can have its own corresponding MCS / NDI / RV indication. Therefore, when only two cells are scheduled and only one codeword is required for each cell, no additional MCS / NDI / RV indication is required.

[0258] According to the third proposal, differential MCS can be used, for example, when the corresponding channel qualities of different cells are not highly correlated. In this case, the reference MCS and the differential MCS can be signaled. In some embodiments, the reference MCS can be the MCS of the PDSCH of one of the cells. In some embodiments, the differential MCS can be applied to the PDSCH of other cells and can have a different (e.g., narrower) bit width than the reference MCS. In addition, the reference MCS can be used for the scheduled cell with the smallest serving cell index.

[0259] Scheduling physical data channels across multiple cells using a single DCI

[0260] When a single DCI is used to schedule physical data channels on multiple cells or component carriers, implementing a single DCI field versus multiple DCI fields for relevant communication parameters may be based on a desired tradeoff between scheduling flexibility and DCI size reduction. Thus, when a single DCI field is used, the same field may be applied to all scheduled cells for a UE, and when multiple DCI fields are used, a different corresponding DCI field in the multiple DCI fields may be applied to each corresponding scheduled cell. Whether to use a single DCI field or multiple DCI fields may be determined independently for each of at least the following fields / communication parameters:

[0261] VRB to PRB mapping;

[0262] ●PRB bundling size indicator;

[0263] ●Rate matching indicator;

[0264] ZP CSI-RS triggering;

[0265] HARQ process number;

[0266] ● TPC commands for scheduled PUCCH;

[0267] ●PUCCH resource indicator;

[0268] ●PDSCH to HARQ feedback timing indicator;

[0269] SRS request;

[0270] ●CBG send information (CBGTI), CBG clear information (CBGFI);

[0271] ●DMRS sequence initialization;

[0272] ●Priority indicator;

[0273] ● a minimum applicable scheduling offset indicator; and

[0274] ●SCell sleep indication.

[0275] Exemplary method for scheduling physical data channels over multiple cells

[0276] Fig.12An exemplary flow chart of a method for scheduling physical data channels on multiple cells or component carriers via a single DCI according to some embodiments is shown. A single downlink control information (DCI) may be sent to a device (e.g., a UE) to schedule physical data channels (e.g., PDSCH and / or PUSCH) for the device / UE on multiple cells / component carriers (1202). In some embodiments, a single DCI may concurrently schedule physical data channels for a device / UE on multiple cells / component carriers. Each DCI field in a single DCI may be used for each cell in a plurality of cells or for a corresponding single cell in a plurality of cells. A device may receive and decode a single DCI (1204) and may then communicate on multiple cells based on communication parameters / parameter values ​​obtained from each DCI field when decoding the DCI (1206).

[0277] Various implementations of scheduling physical data channels for UEs on multiple cells / component carriers via a single DCI

[0278] Some embodiments may include a method for scheduling physical data channels across multiple cells, the method comprising: sending a single downlink control information (DCI) to a device, the single downlink control information (DCI) scheduling physical data channels for the device across the multiple cells, wherein the single DCI includes one or more DCI fields, and each DCI field in at least a subset of the one or more DCI fields is used for each cell in the multiple cells, or a corresponding single cell in the multiple cells.

[0279] The one or more DCI fields may include one or more of the following: a virtual resource block (VRB) to physical resource block (PRB) mapping field; a PRB bundling size indicator field; a rate matching indicator field; a zero power (ZP) channel state information reference signal (CSI-RS) trigger field; a hybrid automatic repeat request (HARQ) process number field; a transmit power control (TPC) command field for a physical uplink control channel (PUCCH) for scheduling; a PUCCH resource indicator field; a physical downlink shared channel (PDSCH) to HARQ feedback timing indicator field; a sounding reference signal (SRS) request field; a code block group (CBG) transmit information (CBGTI) field; a CBG clear information (CBGFI) field; a demodulation reference signal (DMRS) sequence initialization field; a priority indicator field; a minimum applicable scheduling offset indicator field; or a secondary cell (SCell) sleep indication field.

[0280] In some embodiments, the single DCI is defined based on a multi-carrier radio network temporary identifier, the multi-carrier radio network temporary identifier is defined to scramble a cyclic redundancy check (CRC) of the single DCI.

[0281] In some embodiments, the single DCI has a special format in which each of the one or more DCI fields is designed to indicate scheduling of information for multiple scheduled cells.

[0282] In some embodiments, the single DCI is the result of a concatenation of individual DCIs, each individual DCI corresponding to a different cell among the plurality of cells.

[0283] In some embodiments, the one or more DCI fields include multiple carrier indicator (CI) fields, where each CI field corresponds to a different individual cell of the multiple cells.

[0284] In some embodiments, the one or more DCI fields include a single carrier indicator (CI) field corresponding to each cell in the plurality of cells.

[0285] In some embodiments, the mapping of the single CI field to the multiple cells is configured by a serving base station serving the device.

[0286] In some embodiments, the mapping is configured by the serving base station via radio resource control (RRC).

[0287] In some embodiments, the mapping is updated via a Medium Access Control (MAC) Control Element (CE).

[0288] In some embodiments, the mapping of the single CI field to the multiple cells may be predetermined for each scheduled cell in the multiple cells.

[0289] In some embodiments, the one or more DCI fields include a plurality of bandwidth part (BWP) indicator (BWPI) fields, wherein each BWPI field corresponds to a different single cell of the plurality of cells.

[0290] In some embodiments, the one or more DCI fields include a single bandwidth part (BWP) indicator (BWPI) field corresponding to each cell in the plurality of cells.

[0291] In some embodiments, the method further includes switching, by the device, to a BWP indicated by the BWPI field on each of the plurality of cells.

[0292] In some embodiments, the method further includes switching, by the device, to a BWP indicated by the BWPI field only on a single cell of the plurality of cells.

[0293] In some embodiments, the one or more DCI fields include a single bandwidth part (BWP) indicator (BWPI) field that maps to multiple BWPs.

[0294] In some embodiments, the mapping between the BWPI field and the BWP in each of the plurality of cells is predetermined or configured by a serving base station via radio resource control (RRC).

[0295] In some implementations, the same frequency domain resource allocation type is configured for each of the multiple cells.

[0296] In some implementations, a different frequency domain resource allocation type is configured for each of the multiple cells.

[0297] In some embodiments, the one or more DCI fields include multiple frequency domain resource allocation (FDRA) fields, where each FDRA field corresponds to a different single cell among the multiple cells.

[0298] In some embodiments, the one or more DCI fields include a single frequency domain resource allocation (FDRA) field corresponding to each cell in the plurality of cells.

[0299] In some embodiments, a size of a first active bandwidth part (BWP) indicated by the FDRA field for a first cell in the plurality of cells is different than a size of a second active BWP indicated by the FDRA field for a second cell in the plurality of cells.

[0300] In some embodiments, when fewer bits are required to indicate the FDRA in the second BWP than in the first BWP, one or more most significant bits of the FDRA field are discarded, and when more bits are required to indicate the FDRA in the second BWP than in the first BWP, one or more zero bits are appended to the most significant bits.

[0301] In some embodiments, the one or more DCI fields include a plurality of time domain resource allocation (TDRA) fields, wherein each TDRA field corresponds to a different single cell of the plurality of cells.

[0302] In some embodiments, the one or more DCI fields include a single time domain resource allocation (TDRA) field corresponding to each cell in the plurality of cells.

[0303] In some embodiments, the TDRA field indicates the same TDRA for each of the plurality of cells.

[0304] In some embodiments, the TDRA field indicates a first TDRA of a first cell in the plurality of cells, and wherein a second TDRA of a second cell in the plurality of cells is derived from the first TDRA.

[0305] In some embodiments, deriving the second TDRA from the first TDRA is configured via radio resource control (RRC).

[0306] In some embodiments, the second TDRA is derived via an offset of the starting symbol.

[0307] In some implementations, one or more of the following are the same for each cell in the plurality of cells: a mapping type; or a duration of a scheduled physical data channel.

[0308] In some embodiments, the corresponding TDRA value for each cell in the plurality of cells is obtained from a TDRA table indexed by the value indicated in the single TDRA field.

[0309] In some embodiments, the one or more DCI fields include a plurality of transmission configuration indication (TCI) fields, wherein each TCI field corresponds to a different single cell of the plurality of cells.

[0310] In some embodiments, the one or more DCI fields include a single transmit configuration indication (TCI) field corresponding to each cell in the plurality of cells.

[0311] In some embodiments, for each cell in the multiple cells, the device uses one of: a TCI state index indicated by the TCI field; or a quasi-co-located (QCL) source, which is configured to be the TCI state indicated by the TCI state index in the TCI field for a given cell in the multiple cells.

[0312] In some embodiments, the given cell is determined based on one of: a specified attribute of the given cell; or an indication received by the device from a serving base station.

[0313] In some embodiments, the corresponding TCI state of each cell in the plurality of cells is obtained from a TCI table indexed by the value indicated in the single TCI field.

[0314] In some embodiments, when an offset between the single DCI and a corresponding scheduled physical data channel is less than a specified threshold, the device uses a default beam for each of the multiple cells.

[0315] In some embodiments, the default beam is defined by one of: the TCI state of the control resource set (CORESET) with the lowest identifier (ID) in the last DCI monitoring timeslot; the TCI state of the CORESET with the lowest ID; or the active TCI of the corresponding scheduled physical data channel on each cell with the lowest ID.

[0316] In some embodiments, when the device cannot concurrently receive on multiple beams configured for the device, the device uses one of: a beam scheduled for a cell with a lowest identifier among the multiple cells; or a beam determined by the device.

[0317] In some embodiments, the one or more DCI fields include multiple antenna port (AP) fields, where each AP field corresponds to a different individual cell of the multiple cells.

[0318] In some embodiments, the one or more DCI fields include a single antenna port (AP) field corresponding to each cell in the plurality of cells.

[0319] In some embodiments, the device is scheduled with the same port configuration on each of the plurality of cells.

[0320] In some embodiments, when the number of bits used to indicate the AP for one scheduled physical data channel is different from the number of bits used to indicate the AP for another scheduled physical data channel, one or more most significant bits in the AP field are padded or truncated.

[0321] In some embodiments, the single AP field indicates a single AP configuration, and wherein a different code division multiplexing group is used to map to each different cell in the plurality of cells.

[0322] In some embodiments, the one or more DCI fields include multiple Coding and Modulation Scheme / New Data Indicator / Redundancy Version (MCS / NDI / RV) fields, where each MCS / NDI / RV field corresponds to a different single cell among the multiple cells.

[0323] In some embodiments, the one or more DCI fields include a single Coding and Modulation Scheme / New Data Indicator / Redundancy Version (MCS / NDI / RV) field corresponding to each cell in the plurality of cells.

[0324] In some embodiments, the device is scheduled with the same transport block (TB) configuration on each of the plurality of cells.

[0325] In some embodiments, the MCS / NDI / RV for the first codeword corresponds to a first physical data channel scheduled on a first cell among the multiple cells, and the MCS / NDI / RV for the second codeword corresponds to a second physical data channel scheduled on a second cell among the multiple cells.

[0326] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0327] Embodiments of the present invention may be implemented in any of a variety of forms. For example, in some embodiments, the present invention may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, one or more custom-designed hardware devices such as ASICs may be used to implement the present invention. In other embodiments, one or more programmable hardware elements such as FPGAs may be used to implement the present invention.

[0328] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory storage element) may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any method implementation of the method embodiments described herein, or any combination of the method implementations described herein, or any subset of any method implementation of the method embodiments described herein, or any combination of such subsets.

[0329] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a group of processors) and a memory medium (or a memory element), wherein the memory medium stores program instructions, wherein the processor is configured to read and execute these program instructions from the memory medium, wherein these program instructions are executable to implement any method implementation in the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any method implementation in the method implementations described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0330] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method for scheduling physical data channels on multiple cells, the method comprising: Sending a single downlink control information (DCI) to a device, the single downlink control information (DCI) scheduling a physical data channel for the device on multiple cells, wherein the single DCI includes one or more DCI fields, wherein each DCI field in at least a subset of the one or more DCI fields is used Each cell of the plurality of cells, or A corresponding single cell among the plurality of cells.

2. The method of claim 1 , wherein the one or more DCI fields include one or more of: Virtual Resource Block (VRB) to Physical Resource Block (PRB) mapping field; PRB bundle size indicator field; Rate Match Indicator field; Zero power (ZP) channel state information reference signal (CSI-RS) trigger field; Hybrid Automatic Repeat Request (HARQ) process number field; The transmit power control (TPC) command field of the physical uplink control channel (PUCCH) used for scheduling; PUCCH resource indicator field; Physical Downlink Shared Channel (PDSCH) to HARQ Feedback Timing Indicator field; Sounding Reference Signal (SRS) request field; Code Block Group (CBG) Transmit Information (CBGTI) field; CBG clearing information (CBGFI) field; Demodulation Reference Signal (DMRS) sequence initialization field; a priority indicator field; Minimum applicable scheduling offset indicator field; or Secondary cell (SCell) sleep indication field.

3. The method of claim 1, wherein the single DCI is defined based on a multi-carrier radio network temporary identifier, and the multi-carrier radio network temporary identifier is defined to scramble a cyclic redundancy check (CRC) of the single DCI.

4. The method of claim 1, wherein the single DCI has a special format in which each of the one or more DCI fields is designed to indicate scheduling of information for multiple scheduled cells. 5 . The method of claim 1 , wherein the single DCI is a result of concatenating individual DCIs, each individual DCI corresponding to a different cell among the plurality of cells.

6. The method of claim 1, wherein the one or more DCI fields include a single carrier indicator (CI) field corresponding to each of the multiple cells, wherein mapping of the single CI field to the multiple cells is configured by a serving base station serving the device.

7. The method of claim 1, wherein the one or more DCI fields include a single bandwidth part (BWP) indicator (BWPI) field corresponding to each of the plurality of cells, wherein the method further comprises switching, by the device, to: a BWP indicated by the BWPI field on each of the plurality of cells; or The BWP indicated by the BWPI field is only on a single cell among the plurality of cells.

8. The method according to claim 1, wherein the single DCI configures the same frequency domain resource allocation type for each of the multiple cells, or configures a different frequency domain resource allocation type for each of the multiple cells.

9. The method of claim 1 , wherein the one or more DCI fields include a single frequency domain resource allocation (FDRA) field corresponding to each of the multiple cells, wherein a size of a first active bandwidth part (BWP) indicated by the FDRA field for a first cell in the multiple cells is different from a size of a second active BWP indicated by the FDRA field for a second cell in the multiple cells.

10. The method of claim 9, wherein when fewer bits are required to indicate the FDRA in the second BWP than to indicate the FDRA in the first BWP, one or more most significant bits of the FDRA field are discarded, and wherein when more bits are required to indicate the FBRA in the second BWP than to indicate the FDRA in the first BWP, one or more zero bits are appended to the most significant bits.

11. The method of claim 1 , wherein the one or more DCI fields include a single time domain resource allocation (TDRA) field corresponding to each cell in the plurality of cells, wherein the TDRA field indicates: the same TDRA for each cell in the plurality of cells; or A first TDRA of a first cell among the plurality of cells, and a second TDRA of a second cell among the plurality of cells are derived from the first TDRA.

12. The method of claim 1 , wherein the one or more DCI fields include a single time domain resource allocation (TDRA) field corresponding to each of the multiple cells, wherein the corresponding TDRA value for each of the multiple cells is obtained from a TDRA table indexed by a value indicated in the single TDRA field.

13. The method of claim 1 , wherein the one or more DCI fields include a single transmit configuration indication (TCI) field corresponding to each of the plurality of cells, wherein for each of the plurality of cells, the device uses one of: The TCI state index indicated by the TCI field; or A quasi-co-located (QCL) source is configured for a TCI state indicated by the TCI state index in the TCI field for a given cell among the plurality of cells.

14. The method of claim 13, wherein the given cell is determined according to one of: a specified attribute of the given cell; or An indication is received by the device from a serving base station.

15. The method of claim 1, wherein the one or more DCI fields include a single transmit configuration indication (TCI) field corresponding to each of the multiple cells, wherein the corresponding TCI state of each of the multiple cells is obtained from a TCI table indexed by a value indicated in the single TCI field.

16. The method of claim 1 , wherein the one or more DCI fields include a single antenna port (AP) field corresponding to each of the multiple cells, wherein when the number of bits used to indicate the AP for one scheduled physical data channel is different from the number of bits used to indicate the AP for another scheduled physical data channel, one or more most significant bits in the AP field are padded or truncated.

17. The method of claim 1, wherein the one or more DCI fields include a single coding and modulation scheme / new data indicator / redundancy version (MCS / NDI / RV) field corresponding to each of the plurality of cells, wherein the device is scheduled with the same transport block (TB) configuration on each of the plurality of cells.

18. The method of claim 1, wherein the one or more DCI fields include a single coding and modulation scheme / new data indicator / redundancy version (MCS / NDI / RV) field corresponding to each cell in the plurality of cells, wherein the MCS / NDI / RV for a first codeword corresponds to a first physical data channel scheduled on a first cell in the plurality of cells, and wherein the MCS / NDI / RV for a second codeword corresponds to a second physical data channel scheduled on a second cell in the plurality of cells.

19. An apparatus configured to cause a user equipment (UE) to perform any one of the methods according to claims 1 to 18.

20. A user equipment (UE), the user equipment (UE) comprising: a radio circuit configured to enable the UE to perform wireless communications; and The apparatus of claim 19, the apparatus being communicatively coupled to the radio circuit.

21. A non-transitory memory element storing instructions executable by a processor to cause a user equipment (UE) to perform any of the methods according to claims 1 to 18.

Citation Information

Cited By

  • Methods and apparatuses for scheduling multiple fragmented spectrums with a single dci

    WO2025194909A1