PDSCH processing time consideration for multi-cell PDSCH scheduling with single DCI

Abstract

The present invention describes a processing time method for simultaneous multi-cell PUSCH / PDSCH scheduling with a single DCI (Downlink Control Information) in a wireless communication system. In various methods, simultaneous scheduling of a plurality of physical downlink shared channels (PDSCHs) occurs through a single DCI transmitted via a physical downlink control channel (PDCCH), where each PDSCH of the plurality of PDSCHs is associated with a respective cell of a plurality of cells. The method also includes transmitting data to or receiving data from a user equipment (UE) based on the scheduling information, wherein the plurality of PDSCHs occur not earlier than a time offset after the PDCCH. In other aspects, a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) is received via a Physical Uplink Control Channel (PUCCH), the HARQ-ACK having been transmitted by a User Equipment (UE) in response to one of the plurality of PDSCHs, where the HARQ-ACK is transmitted not earlier than a time offset after a reference time in the one of the plurality of PDSCHs. In other aspects, transmitting data to or receiving data from a user equipment (UE) is based on the scheduling information in which the plurality of PDSCHs occur not earlier than a time offset after the PDCCH, the time offset configured to permit analog beam switching by the user equipment (UE).

Description

[0001] Cross-references

[0002] This application claims priority to U.S. non-provisional application No. 18 / 365,602, filed on August 4, 2023, entitled “PDSCH Processing Time Consideration for Multi-Cell PDSCH Scheduling with a Single DCI,” which claims the benefit of U.S. Provisional Application No. 63 / 397,088, filed on August 11, 2022, entitled “PDSCH Processing Time Consideration for Multi-CellPDSCH Scheduling with aSingle DCI,” and the contents of both applications are incorporated herein by reference in their entirety. Background Art Technical Field

[0003] Aspects generally relate to the field of wireless communications. Summary of the invention

[0004] Aspects of the approaches described herein include a method performed by a base station (BS) in a wireless communication network, the method comprising the following steps. The method comprises the following steps: simultaneously scheduling multiple physical downlink shared channels (PDSCHs) by a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The method also includes sending data to or receiving data from a user equipment (UE) based on the scheduling information, wherein the multiple PDSCHs occur at a time offset no earlier than after the PDCCH.

[0005] Aspects of the methods described herein include a base station (BS). The BS includes a radio frequency (RF) transceiver configured to transmit and receive via at least one antenna. The BS also includes a processing circuit coupled to the RF transceiver. The processing circuit is configured to simultaneously schedule multiple physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The processing circuit is further configured to send data to a user equipment (UE) or receive data from the user equipment based on the scheduling information, wherein the multiple PDSCHs occur at a time offset no earlier than after the PDCCH.

[0006] Aspects of the approaches described herein include a method performed by a base station (BS) in a wireless communication network, the method comprising the following steps. The method comprises the following steps: simultaneously scheduling multiple physical downlink shared channels (PDSCHs) by a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The method also comprises the following steps: receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) via a physical uplink control channel (PUCCH), the HARQ-ACK having been transmitted by a user equipment (UE) in response to one of the multiple PDSCHs, wherein the HARQ-ACK is transmitted no earlier than a time offset after a reference time in one of the multiple PDSCHs.

[0007] Aspects of the approaches described herein include a base station (BS) in a wireless communication network. The BS includes a radio frequency (RF) transceiver configured to transmit and receive via at least one antenna, and a processing circuit coupled to the RF transceiver. The processing circuit is configured to simultaneously schedule multiple physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The processing circuit is further configured to receive a hybrid automatic repeat request acknowledgment (HARQ-ACK) via a physical uplink control channel (PUCCH), the HARQ-ACK having been transmitted by a user equipment (UE) in response to one of the multiple PDSCHs, wherein the HARQ-ACK is transmitted no earlier than a time offset after a reference time in one of the multiple PDSCHs.

[0008] Aspects of the approaches described herein include a method performed by a base station (BS) in a wireless communication network, the method comprising the following steps. The method comprises the following steps: simultaneously scheduling multiple physical downlink shared channels (PDSCHs) by a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The method also comprises the following steps: sending data to or receiving data from a user equipment (UE) based on the scheduling information, wherein the multiple PDSCHs occur at a time offset no earlier than after the PDCCH, the time offset being configured to permit analog beam switching by the user equipment (UE).

[0009] Aspects of the approaches described herein include a base station (BS) in a wireless communication network. The BS includes a radio frequency (RF) transceiver configured to transmit and receive via at least one antenna, and a processing circuit coupled to the RF transceiver. The processing circuit is configured to simultaneously schedule multiple physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the multiple PDSCHs is associated with a corresponding cell in a plurality of cells. The processing circuit is further configured to send data to or receive data from a user equipment (UE) based on scheduling information, wherein the multiple PDSCHs occur at a time offset no earlier than after the PDCCH, and the time offset is configured to permit analog beam switching by the user equipment (UE).

[0010] The present invention is provided for the purpose of illustrating some aspects only, so as to provide an understanding of the subject matter described herein. Therefore, the above-mentioned features are only examples and should not be understood as narrowing the scope or essence of the subject matter in the present disclosure. Other features, aspects and advantages of the present disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and enable those skilled in the relevant art to make and use the present disclosure.

[0012] Figure 1 An example system for implementing simultaneous multi-cell scheduling DCI procedures between a user equipment (UE) and a base station in a wireless communication network according to some aspects of the present disclosure is illustrated.

[0013] Figure 2 A block diagram illustrating an example system of an electronic device for performing simultaneous multi-cell scheduling DCI procedures according to some aspects of the present disclosure.

[0014] Figure 3A to Figure 3D Various cell scheduling restrictions from earlier versions of the 3GPP specifications are highlighted.

[0015] Figure 4 Two processing times on a timeline for simultaneous multi-cell scheduling according to some aspects of the present disclosure are illustrated.

[0016] Figure 5 Relevant timing associated with the above six alternatives for processing time according to some aspects of the present disclosure are illustrated.

[0017] Fig. 6AA flow chart illustrating a method 600 for performing simultaneous multi-cell scheduling using a single DCI according to aspects of the present disclosure is shown.

[0018] Figure 6B A flow chart illustrating a method 630 for performing simultaneous multi-cell scheduling using a single DCI according to aspects of the present disclosure is shown.

[0019] Figure 6C A flow chart illustrating a method 660 for performing simultaneous multi-cell scheduling using a single DCI in accordance with aspects of the present disclosure is illustrated.

[0020] Figure 7 An exemplary computer system for implementing some aspects or portions thereof.

[0021] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numerals indicate identical or functionally similar elements. Additionally, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0022] Figure 1 An example system for implementing a mechanism for performing simultaneous multi-cell scheduling DCI processes according to some aspects of the present disclosure is illustrated. The example system 100 is provided for illustrative purposes only and is not intended to limit the disclosed aspects. The system 100 may include, but is not limited to, network nodes (e.g., base stations such as eNBs and gNBs) 101 and 103 and electronic devices (e.g., UEs) 105. The electronic device 105 (hereinafter referred to as UE 105) may be configured to operate based on a variety of wireless communication technologies. These technologies may include, but are not limited to, technologies based on the third generation partnership project (3GPP) standard. For example, the UE 105 may be configured to operate using the 3GPP standard. The UE 105 may include, but is not limited to: a wireless communication device, a smart phone, a laptop, a desktop computer, a tablet computer, a personal assistant, a monitor, a television, a wearable device, an Internet of Things (IoT), a communication device of a vehicle, etc. The network node 101 (referred to herein as a base station) may include a node configured to operate based on a variety of wireless communication technologies (such as, but not limited to, technologies based on the 3GPP standard).

[0023] According to some aspects, UE 105 and base station 101 and base station 103 are configured to implement a mechanism for UE 105, and UE is used to perform multi-cell scheduling DCI process. In some aspects, UE 105 is configured to perform multi-cell scheduling DCI process simultaneously. According to some aspects, UE 105 can be connected to base station 101 and base station 103 and can communicate with base station 101 and base station 103.

[0024] According to some aspects, UE 105 can perform various combinations of multi-cell scheduled DCI procedures to communicate with base station 101 and other base stations in a group of base stations.

[0025] Figure 2 A block diagram of an example system 200 of an electronic device for implementing a simultaneous multi-cell scheduling DCI process according to some aspects of the present disclosure is illustrated. System 200 can be any electronic device of system 100 (e.g., base station 101, 103, UE 105). System 200 includes a processor 210, one or more transceivers 220a to 220n, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The system shown is provided as an exemplary portion of system 200, and system 200 may include other circuits and subsystems. In addition, although the system of system 200 is illustrated as separate components, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0026] The memory 250 may include random access memory (RAM) and / or cache, and may include control logic (e.g., computer software) and / or data. The memory 250 may include other storage devices or memories, such as, but not limited to, a hard drive and / or a removable storage device / unit. According to some examples, an operating system 252 may be stored in the memory 250. The operating system 252 may manage data transfer from the memory 250 and / or one or more applications 254 to the processor 210 and / or one or more transceivers 220a to 220n. In some examples, the operating system 252 maintains one or more network protocol stacks (e.g., an Internet protocol stack, a cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, the operating system 252 includes a control mechanism and a data structure to perform the functions associated with the layer.

[0027] According to some examples, applications 254 may be stored in memory 250. Applications 254 may include applications (e.g., user applications) used by wireless system 200 and / or a user of wireless system 200. Applications in applications 254 may include applications such as, but not limited to, radio streaming, video streaming, remote control, and / or other user applications.

[0028] The system 200 may also include a communication infrastructure 240. The communication infrastructure 240 provides, for example, communication between the processor 210, one or more transceivers 220a-220n, and the memory 250. In some implementations, the communication infrastructure 240 may be a bus.

[0029] In some embodiments, processor 210, together with instructions stored in memory 250, executes operations that enable system 200 of system 100 to implement the mechanisms for multi-cell scheduling DCI procedures as described herein. Alternatively, in an embodiment, processor 210 may be "hard coded" to implement or cause implementation of the mechanisms for multi-cell scheduling DCI procedures as described herein.

[0030] According to some aspects, one or more transceivers 220a to 220n send and receive communication signals supporting a mechanism for performing a multi-cell scheduling DCI process and may be coupled to an antenna 260. Antenna 260 may include one or more antennas that may be the same or different types. One or more transceivers 220a to 220n allow the system 200 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 220a to 220n may include a processor, a controller, a radio component, a socket, a plug, a buffer, and similar circuits / devices for connecting to a network and communicating on the network. According to some examples, one or more transceivers 220a to 220n may include one or more circuits for connecting to a wired network and / or a wireless network and communicating thereon.

[0031] According to some aspects, one or more transceivers 220a-220n may include a cellular subsystem, a satellite subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TM Subsystems, each of which includes its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, one or more of the transceivers 220a to 220n may include more or fewer systems for communicating with other devices.

[0032] In some examples, one or more transceivers 220a to 220n may include one or more circuits (including a WLAN transceiver) for enabling connection and communication via a WLAN network (such as, but not limited to, a network based on the standards described in IEEE 802.11). Additionally or alternatively, one or more transceivers 220a to 220n may include one or more circuits (including a WLAN transceiver) for enabling connection and communication via a WLAN network (such as, but not limited to, a network based on the standards described in IEEE 802.11). TM Protocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low-power long-range protocols (including Bluetooth TM For example, the transceiver 220n may include a Bluetooth TM Transceiver.

[0033] Additionally, one or more transceivers 220a to 220n may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network. Cellular networks may include, but are not limited to, 3G / 4G / 5G networks such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc. For example, one or more transceivers 220a-220n may be configured to operate in accordance with one or more of Rel-15, Rel-16, Rel-17, or other versions of the 3GPP standard.

[0034] In addition, one or more transceivers 220a to 220n may include one or more circuits for connecting to and communicating with multiple cells via respective base stations of the multiple cells. Such base station type networks may include, but are not limited to, wireless communication networks, such as 3G / 4G / 5G networks, such as Universal Mobile Telecommunications System (UMTS) and Long Term Evolution (LTE). For example, one or more transceivers 220a-220n may be configured to operate in accordance with one or more of Rel-15, Rel-16, Rel-17, or other versions of the 3GPP standard.

[0035] According to some aspects, processor 210 alone or in combination with computer instructions stored in memory 250 and / or one or more transceivers 220a to 220n implements the multi-cell scheduling DCI process discussed herein. For example, transceiver 220a may be used with, for example, Figure 1 In this example, the combination of the processor 210 and the transceiver 220a and / or the transceiver 220b can perform a multi-cell scheduling DCI process (e.g., Figure 1 Base station 101 and Figure 1 Although the operations discussed herein are discussed with respect to processor 210, it is noted that processor 210 may implement these operations alone or in combination with computer instructions stored in memory 250 and / or one or more transceivers 220a to 220n.

[0036] PDSCH processing time considerations - introduction

[0037] In previous versions of the 3GPP specification, the problem of scheduling the physical downlink shared channel (PDSCH) across multiple cells has been solved. For example, in versions 15 and 16 of the 3GPP specification, such scheduling is implemented using cross-carrier scheduling (CCS) restrictions. Such restrictions ensure simplicity, but include the requirement that the P(S)Cell can only be scheduled by itself. The PCell (primary cell) is the primary cell of the MCG (primary cell group). The PSCell (primary secondary cell) is the primary cell of the SCG (secondary cell group). A further restriction in these earlier 3GPP specification versions is that for each scheduled cell, only one scheduling cell can be RRC (radio resource control) configured. In addition to this, a further restriction is that in the case where a cell is configured to be scheduled by another cell, the cell itself cannot be configured to schedule any other cell. Finally, the restrictions in these earlier specifications require that neither cross-cell group (CG) scheduling nor physical uplink control channel (PUCCH) group scheduling is supported.

[0038] Figure 3A to Figure 3D Various cell scheduling restrictions from earlier versions of the 3GPP specification are highlighted. For example, FIG. 3A illustrates that P(S)Cell 310 can be scheduled only by itself, i.e., it may not be scheduled by SCell 320. Turning to FIG. 3B , CellB 340 can schedule CellA 330, but CellA 330 may not be scheduled by another cell, such as CellC 350. FIG. 3C illustrates additional restrictions of earlier 3GPP specifications, because CellA 370 is scheduled by another cell, CellB 380, so it in turn cannot schedule cells such as CellC 360.

[0039] In Release 17 of the 3GPP specification, enhancements were introduced to provide more scheduling flexibility to the primary cell. Specifically, the enhancement allows a P(S)Cell to be scheduled by both the P(S)Cell itself and by an additional cell (e.g., a secondary cell (SCell)). In this case, the SCell configured to schedule the P(S)Cell is denoted as an sSCell. Figure 3D This enhancement is illustrated in FIG. 3 , where P(S)Cell 390 is shown as the scheduler itself. In addition, Figure 3D It is illustrated that the secondary cell SCell 395 can also schedule the P(S)Cell 390 .

[0040] Although the 3GPP Release 17 scheduling enhancements are welcome improvements, there is still a continuous demand to provide more scheduling flexibility for multi-cell scenarios. Specifically, the additional scheduling flexibility is useful for networks (NWs) where P(S)Cells coexist with LTE and PDCCH monitoring on P(S)Cells is limited due to the Long Term Evolution (LTE) Cell-Specific Reference Signal (CRS).

[0041] In existing versions of the 3GPP specification, including Releases 15, 16, and 17, a single downlink control information (DCI) can only be used to schedule PDSCH / PUSCH for one cell. According to these existing specifications, the scheduled cell is indicated by the "carrier indicator" field in the DCI. In turn, the mapping of the "carrier indicator" to the actual cell is configured by the radio resource control (RRC) via the CrossCarrierSchedulingConfig parameter. This configuration is implemented on a per-scheduled cell basis. Although the "carrier indicator" is a multi-bit field (e.g., 3 bits) that can be used to identify many different cells, only one cell can be indicated at any one time.

[0042] Future advances in cellular wireless capabilities require innovation in supporting multi-carrier enhancements, including simultaneous scheduling thereof. To support this purpose, the disclosure herein provides a method for a single DCI to simultaneously schedule channels (physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH)) for multiple cells. In formulating the method, attention is paid to the processing time required to support multi-cell PDSCH scheduling using a single DCI. Specifically, the scheduling must reflect the various processing times of the user equipment (UE) so that one or more processes can be completed, including the DCI being decoded, decoding the data in the associated PDSCH in sufficient time, so that the validity of the data can be confirmed in the HARQ-ACK in the scheduled uplink (PUCCH), and any required beam switching is completed in sufficient time to receive information about the configured beams.

[0043] These processing requirements can be broken down into three separate requirements, as follows. The first processing time requirement is to provide a sufficient time interval (or time offset) so that the UE can process the DCI information (from the PDCCH) quickly enough to identify the location of its downlink data in the PDSCH signal and prepare to decode its downloaded data. This first processing time interval is referred to as the PDSCH K0 processing time. The second processing time requirement is to provide a sufficient time interval (or time offset) so that the UE can decode its downlink data in the PDSCH signal in order to verify the downlink data and thereby prepare for the HARQ-ACK sent in the PUCCH. This second processing time requirement is referred to as the PDSCH K1 processing time. The third processing time requirement is to provide a sufficient time interval (or time offset) so that the processing to support the required beam switching can occur before reception on the desired beam.

[0044] Certain implementations of the first processing time requirement and the second processing time requirement may be provided as follows. K0 processing time (or time offset) may refer to the time interval between the end of the scheduled DCI and the start of the scheduled PDSCH. K1 processing time (or time offset) may refer to the time interval between the end of the scheduled PDSCH and the start of the PUCCH HARQ-ACK.

[0045] Figure 4 These two processing times on a timeline for simultaneous multi-cell scheduling according to some aspects of the present disclosure are illustrated. Figure 4 In the timeline shown, three signals are shown, namely DCI 410, PDSCH 420 and PUCCH HARQ-ACK 430. Figure 4 Time offsets of interest are illustrated, including: K0, which is the time offset between the end of the scheduled DCI and the start of the scheduled PDSCH. Figure 4 K1 is also illustrated, which is the time offset between the end of the scheduled PDSCH and the start of the PUCCH HARQ-ACK.The third processing time requirement associated with the PDSCH beam switching time will be further discussed in a later section of this disclosure.

[0046] PDSCHK0 Processing Time - Background

[0047] In order to more fully understand the K0 time offset restriction in a multi-cell PDSCH single DCI scheduling environment, there are two scenarios described below. Without loss of generality, the description below involves two cells, one is the scheduling cell and the other is the scheduled cell, but the same principles apply to two or more cells scheduled by a single DCI. The first scenario is that the scheduling cell and the scheduled cell have the same subcarrier spacing (SCS). The second scenario is that the scheduling cell and the scheduled cell have different SCS. Turning to the first scenario, that is, for scheduling with the same SCS (subcarrier spacing), that is, the scheduling cell (PDCCH) and the scheduled cell (PDSCH) have the same SCS. In order to address the K0 processing time in this first scenario, it is recognized that the 3GPP 38.214 specification envisions two types of mappings, Type A and Type B, each of which has associated timing implications.

[0048] As specified in the 3GPP 38.214 specification, in mapping type A, where the PDCCH and PDSCH are in the same slot, the PDCCH must be contained within the first 3 symbols within the slot. In addition, if the PDCCH scheduling the PDSCH is received in the same slot and is not contained within the first three symbols of the slot, the UE is not expected to receive the PDSCH with mapping type A in that slot.

[0049] For mapping type B, PDSCH cannot start before the start of PDCCH. As specified in the 3GPP specifications, if the first symbol of the PDCCH scheduling the PDSCH is received in a later symbol than the first symbol indicated in the PDSCH time domain resource assignment, then the UE is not expected to receive PDSCH with mapping type B in the slot.

[0050] Turning to the second scenario, where scheduling faces cells with different SCSs, i.e., the scheduling cell (PDCCH) and the scheduled cell (PDSCH) have different SCSs. In this second scenario, additional time offset is required. The relevant part of the 3GPP 38.214 specification proposes the following requirements (where μ is the subcarrier spacing in symbol units):

[0051] If μ PDCCH <μ PDSCH , then without considering the effect of the reception timing difference between the scheduling cell and the scheduled cell, if the first symbol in the PDSCH allocation including the DM-RS as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI starts at least N after the end of the PDCCH that schedules the PDSCH pdschIf the UE receives the scheduled PDSCH starting from the first symbol of the time slot in which the PDSCH of the PDCCH symbols is received, then the UE is expected to receive the scheduled PDSCH.

[0052] If μ PDCCH >μ PDSCH , without considering the influence of the reception timing difference between the scheduling cell and the scheduled cell, if the first symbol in the PDSCH allocation including the DM-RS as defined by the slot offset K0 and the start and length indicator SLIV of the scheduling DCI is not earlier than N after the end of the PDCCH that schedules the PDSCH pdsch If the UE starts from the first PDCCH symbol, it is expected that the UE will receive the scheduled PDSCH.

[0053] Table 5.5-1: N as a function of the subcarrier spacing of the scheduled PDCCH pdsch

[0054] <![CDATA[μ PDCCH ]]> <![CDATA[N pdsch [Symbol]]]> 0 4 1 5 2 10 3 14 5 56 6 112

[0055] PDSCH K0 Processing Time - Proposed Method

[0056] In view of these 3GPP timing requirements, multiple implementations are proposed for each of these situations. In the first proposed method for K0 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, a processing time requirement is defined, which refers to the time offset between the scheduling PDCCH and the scheduled PDSCH, i.e., K0. For each individual scheduled PDSCH, the K0 processing time requirement is independently determined based on two factors, specifically: (1) the mapping type, type A or type B; and (2) the value of the SCS of the scheduled PDSCH compared to the value of the SCS of the scheduling PDCCH. These two factors produce four possible combinations.

[0057] Two alternative embodiments are described in which the scheduled PDSCH and the scheduled PDCCH have the same SCS. In the first alternative embodiment, the time offset may be defined as between the end of the scheduled PDCCH and the beginning of the scheduled PDSCH. In the second alternative embodiment, the time offset may be defined as between the beginning of the scheduled PDCCH and the beginning of the scheduled PDSCH. In some embodiments, the unit of the time offset is in symbols. It should be noted that in additional embodiments, an additional time offset may be required between the scheduled PDCCH and the scheduled PDSCH. For different SCSs, the additional time offset may be different. The additional time offset may be hard-coded in the 3GPP specification, or it may be reported as a UE capability.

[0058] Turning now to the second proposed method for K0 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, a restriction on the time offset (i.e., K0) between the scheduling PDCCH and the scheduled PDSCH is defined. In this second scenario, the scheduled PDSCH and the scheduling PDCCH have different SCSs.

[0059] If for at least one scheduled PDSCH, μ_PDCCH < μ_PDSCH, ie the scheduling PDCCH has a smaller SCS than the scheduled PDSCH, all scheduled PDSCHs are subject to the time offset restriction assuming μ_PDCCH < μ_PDSCH.

[0060] If for at least one scheduled PDSCH, μ_PDCCH>μ_PDSCH, i.e., the scheduling PDCCH has a larger SCS than the scheduled PDSCH, and no scheduled PDSCH has μ_PDCCH<μ_PDSCH, all scheduled PDSCHs are subject to the time offset restriction assuming μ_PDCCH>μ_PDSCH.

[0061] In the third proposed method for K0 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, the restrictions on the time offset (i.e., K0) between the scheduling PDCCH and the scheduled PDSCH for different SCSs between the PDSCH and the PDCCH are defined as follows. In this proposed method, it should be noted that an additional time offset may be required between the scheduling PDCCH and the scheduled PDSCH. The additional time offset may be different for different SCSs. The additional time offset may be hard-coded in the 3GPP specification, or it may be reported as a UE capability.

[0062] PDSCH K1 Processing Time - Background

[0063] Turning to the 3GPP requirements for K1 processing time, the time offset limit is defined in the current 3GPP 38.214 specification as follows:

[0064] T proc.1 =(N1+d 1,1 +d2)(2048+144)2 - .T c +T ext

[0065] N1, the minimum time offset N1 is hard-coded in the 3GPP 38.214 specification

[0066] d 1,1 , additional relaxation d 1,1 Determined based on the overlap condition between PDSCH and PDCCH

[0067] Table 5.3-1: PDSCH processing time for PDSCH processing capability 1

[0068]

[0069]

[0070] Table 5.3-2: PDSCH processing time for PDSCH processing capability 2

[0071]

[0072] PDSCH K1 Processing Time - Proposed Method

[0073] In the first proposed method for K1 processing time, a single HARQ-ACK is supported when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells. In order to determine the reference point for the start of the HARQ turnaround time, i.e., the "PDSCH to HARQ_Feedback Timing Indicator", one of the following six alternatives can be used. The six alternatives are: (1) the last symbol of the scheduled PDSCH that ends latest in time; (2) the last symbol of the scheduled PDSCH that starts latest in time; (3) the last symbol of the first scheduled PDSCH; (4) the last symbol of the last scheduled PDSCH; (5) the last symbol of the scheduled PDSCH that ends earliest in time; and (6) the last symbol of the scheduled PDSCH that starts earliest in time.

[0074] Figure 5 The relevant timing associated with the above six alternatives for processing time according to some aspects of the present disclosure is illustrated. Figure 5 In Figure 5, cell A is scheduling cell B and cell C. The DCI 510 from cell A schedules PDSCH1 520 of cell B and PDSCH2 525 of cell C. PUCCH HARQ-ACK 530 is the HARQ confirmation of the UE. Figure 5 In FIG. 5 , the PDSCH to HARQ_Feedback timing indicator is shown to implement the first alternative, namely the last symbol of the scheduled PDSCH that ends latest in time.

[0075] In the second proposed method for K1 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, in order to determine N for HARQ-ACK turnaround time among all scheduled PDSCHs, 1,0 , there are four alternatives: (1) using the maximum N 1,0(2) using the earliest PDSCH; (3) using the last PDSCH; or (4) using the PDSCH as a reference PDSCH for HARQ-ACK turnaround time (e.g. Figure 5 Note that the earliest / last can be defined based on the start of PDSCH or the end of PDSCH. In addition, note that in this specification, N 1,0 The value is the PDSCH processing time determined based on the additional demodulation reference signal (DMRS) position with a 15kHz subcarrier spacing (SCS).

[0076] In the third proposed method for K1 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, in order to determine N1 for HARQ-ACK turnaround time among all scheduled PDSCHs, there are again four alternatives: (1) using the scheduled PDSCH that gives the largest N1; (2) using the earliest PDSCH; (3) using the last PDSCH; and (4) using PDSCH as the reference PDSCH for HARQ-ACK turnaround time (such as Figure 5 As shown). Note that the earliest / last can be defined based on the start of PDSCH or the end of PDSCH. In addition, note that in this specification, the N1 value is the PDSCH processing time determined based on the PDSCH processing capability reported by the UE (i.e., capability 1 or capability 2) according to the minimum subcarrier spacing (SCS) used for PDSCH, PDCCH, and uplink channels carrying HARQ-ACK.

[0077] For the fourth proposed method for K1 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, in order to determine N for HARQ-ACK turnaround time among all scheduled PDSCHs, 1,1 , again there are four alternatives: (1) using the maximum N given by 1,1 (2) using the earliest PDSCH; (3) using the last PDSCH; and (4) using the PDSCH as the reference PDSCH for HARQ-ACK turnaround time (e.g. Figure 5 As shown in FIG. 1 ). Note that the earliest / last may be defined based on the start of the PDSCH or the end of the PDSCH. In addition, note that in this specification, d 1,1 The value is a relaxation of the PDSCH processing time determined based on the number of PDSCH symbols and the overlapping condition between the PDSCH and the PDCCH.

[0078] For the fifth proposed method for K1 processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, a restriction on the time offset (ie, K1) between the scheduled PDSCH and HARQ-ACK is defined.

[0079] An additional time offset may be required between the end of the scheduled PDSCH and the start of HARQ-ACK, the time offset unit is in symbols and is different for different SCSs. This may be hard-coded in the specification or reported as a UE capability.

[0080] PDSCH beam switching time-background

[0081] As background, in addition to K0 and K1, for analog beam switching, a minimum time offset between the end of the scheduled DCI and the start of the scheduled PDSCH is also defined. The minimum time offset is reported as a UE capability in timeDurationForQCL. For cross-carrier scheduling with different SCS, when μ_PDCCH < μ_PDSCH, additional time offset relaxation is allowed, as shown below in the current 3GPP 38.214 specification:

[0082] timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCH , then additional timing delay is added to timeDurationForQCL, where d is defined in 5.2.1.5.1a-1, otherwise d is zero;

[0083]

[0084] PDSCH beam switching time-implementation plan

[0085] For the first proposed method for beam switching processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, the minimum time offset for beam switching, i.e., timeDurationForQCL, is determined. For each individual scheduled PDSCH, the minimum time offset for beam switching is determined independently based on the SCS of the scheduling PDCCH and the SCS of the scheduled PDSCH.

[0086] For the second proposed method for beam switching processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, there are two alternatives for determining the time offset relaxation d for beam switching among all scheduled PDSCHs: (1) using each PDSCH individually; and (2) using the scheduled PDSCH that gives the largest d. Note that in this specification, the time offset relaxation d is expressed in μ PDCCH When μ is 0, it is 8 PDCCH symbols. PDCCH When μ is 1, it is 8 PDCCH symbols. PDCCH If it is 2, it is 14 PDCCH symbols, otherwise it is zero.

[0087] For the third proposed method for beam switching processing time, when a single DCI is allowed to schedule multiple PDSCHs simultaneously in different cells, beam switching may require an additional time offset, the time offset unit is in symbols and is different for different SCSs. This can be hard-coded in the specification or reported as a UE capability.

[0088] Overview of a method for utilizing simultaneous multi-cell scheduling DCI processing timing

[0089] Fig. 6A A flow chart illustrating a method 600 for simultaneous multi-cell scheduling using a single DCI in a wireless network according to various aspects of the present disclosure is shown. Step 602 includes simultaneously scheduling a plurality of physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the plurality of PDSCHs is associated with a respective cell of a plurality of cells.

[0090] Step 604 includes transmitting data to or receiving data from a user equipment (UE) based on the scheduling information, wherein a plurality of PDSCHs occur in time no earlier than a time offset after the PDCCH.

[0091] Figure 6B A flow chart illustrating a method 630 for simultaneous multi-cell scheduling with a single DCI in a wireless network according to various aspects of the present disclosure is shown. Step 632 includes simultaneously scheduling a plurality of physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the plurality of PDSCHs is associated with a respective cell of a plurality of cells.

[0092] Step 634 includes receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) via a physical uplink control channel (PUCCH), the HARQ-ACK having been transmitted by a user equipment (UE) in response to one of the multiple PDSCHs, wherein the HARQ-ACK is transmitted in time no earlier than a time offset after a reference time in one of the multiple PDSCHs.

[0093] Figure 6C A flow chart illustrating a method 660 for simultaneous multi-cell scheduling with a single DCI in a wireless network according to aspects of the present disclosure is shown. Step 662 includes simultaneously scheduling a plurality of physical downlink shared channels (PDSCHs) via a single DCI sent via a physical downlink control channel (PDCCH), wherein each of the plurality of PDSCHs is associated with a respective cell of a plurality of cells.

[0094] Step 664 includes sending data to or receiving data from a user equipment (UE) based on the scheduling information, wherein a plurality of PDSCHs occur in time no earlier than a time offset after the PDCCH, the time offset being configured to allow simulated beam switching and PDCCH decoding by the user equipment (UE).

[0095] Exemplary Computer System

[0096] For example, one or more computer systems such as Figure 7 The computer system 700 shown implements various aspects. The computer system 700 may be any well-known computer capable of performing the functions described herein, such as Figure 1 Device 101, 103, 105, or Figure 2 The computer system 700 includes one or more processors (also referred to as central processing units or CPUs), such as a processor 704. The processor 704 is connected to a communication infrastructure 706 (e.g., a bus). The computer system 700 also includes a user input / output device 703, such as a monitor, a keyboard, a pointing device, etc., which communicates with the communication infrastructure 706 through a user input / output interface 702. The computer system 700 also includes a main memory or primary storage 708, such as a random access memory (RAM). The main memory 708 may include one or more levels of cache. The main memory 708 has control logic components (e.g., computer software) and / or data stored therein.

[0097] The computer system 700 may also include one or more secondary storage devices or memories 710. The secondary storage 710 may include, for example, a hard disk drive 712 and / or a removable storage device or drive 714. The removable storage drive 714 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0098] The removable storage drive 714 may interact with a removable storage unit 718. The removable storage unit 718 includes a computer usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 718 may be a floppy disk, a magnetic tape, a compact disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 714 reads from and / or writes to the removable storage unit 718 in a well-known manner.

[0099] According to some aspects, the secondary memory 710 may include other devices, tools, or other methods for allowing the computer system 700 to access computer programs and / or other instructions and / or data. Such devices, tools, or other methods may include, for example, a removable storage unit 722 and an interface 720. Examples of removable storage units 722 and interfaces 720 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and an associated socket, a memory stick and USB port, a memory card and an associated memory card slot, and / or any other removable storage unit and associated interface.

[0100] The computer system 700 may also include a communication or network interface 724. The communication interface 724 enables the computer system 700 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 728). For example, the communication interface 724 may allow the computer system 700 to communicate with the remote device 728 via a communication path 726, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic components and / or data may be sent to and from the computer system 700 via the communication path 726.

[0101] The operations in the foregoing aspects can be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects can be performed in hardware, software, or in both hardware and software. In some aspects, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, a computer system 700, a main memory 708, an auxiliary memory 710, and removable storage units 718 and 722, as well as tangible articles embodying any combination of the foregoing. Such control logic components, when executed by one or more data processing devices (such as computer system 700), cause such data processing devices to operate as described herein.

[0102] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use the Figure 7 The various aspects of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the various aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0103] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary aspects of the present disclosure as contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0104] Although the present disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the various aspects are not limited to the software, hardware, firmware, and / or entities illustrated in the figures and / or described herein. In addition, the various aspects (whether or not explicitly described herein) have significant practicality for fields and applications beyond the examples described herein.

[0105] Various aspects have been described herein by means of functional building blocks that illustrate the specific implementation of specific functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. As long as the specified functions and relationships (or their equivalents) are properly performed, alternative boundaries may be defined. In addition, alternative aspects may use an order different from the order described herein to perform functional blocks, steps, operations, methods, etc.

[0106] References herein to "an aspect," "aspects," "exemplary aspects," or similar phrases indicate that the described aspects may include particular features, structures, or characteristics, but each aspect may not necessarily include the particular features, structures, or characteristics. Furthermore, such wordings do not necessarily refer to the same aspect. Furthermore, when particular features, structures, or characteristics are described in conjunction with an aspect, it is within the knowledge of those skilled in the relevant art to incorporate these features, structures, or characteristics into other aspects, whether or not explicitly mentioned or described herein. The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be limited only in accordance with the following claims and their equivalents.

[0107] As described above, various aspects of the present technology may include collecting and using data available from various sources, thereby (for example) improving or enhancing functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0108] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and measures that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with the privacy policies and procedures of other entities. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

[0109] Regardless of the foregoing, the present disclosure also contemplates that users selectively block aspects of the use or access to personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, the present technology may be configured to allow users to selectively participate in "opt-in" or "opt-out" of collecting personal information data at any time during or after (for example) registration for a service. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[0110] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting the collection of data and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0111] Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed aspects, the present disclosure also contemplates that various aspects may be implemented without access to such personal information data. That is, various aspects of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A method for sending downlink control information (DCI), the method comprising: scheduling a plurality of physical downlink shared channels (PDSCHs) simultaneously through a single DCI transmitted via a physical downlink control channel (PDCCH), wherein each of the plurality of PDSCHs is associated with a respective cell of the plurality of cells; and Data is transmitted to or received from a user equipment (UE) based on the scheduling information, wherein the plurality of PDSCHs occur in time no earlier than a time offset after the PDCCH.

2. The method according to claim 1, wherein a subcarrier spacing (SCS) associated with the PDCCH is equal to an SCS of at least one of the plurality of PDSCHs, and Wherein the time offset is measured between an end of the PDCCH and a start of the at least one PDSCH of the plurality of PDSCHs.

3. The method of claim 1, wherein a subcarrier spacing (SCS) associated with the PDCCH and the SCS of at least one of the multiple PDSCHs are different, and maintaining the time offset between the PDCCH and the at least one of the multiple PDSCHs further comprises maintaining the time offset between the PDCCH and all of the multiple PDSCHs. The method of claim 1 , wherein the time offset is measured in symbols.

5. The method of claim 1, wherein the time offset is between an end of the PDCCH and a start of a scheduled PDSCH.

6. The method of claim 1, wherein the time offset is between a start of the PDCCH and a start of a scheduled PDSCH.

7. The method of claim 1, wherein the time offset comprises an additional time interval, the additional time interval being based on a capability of the UE.

8. The method of claim 7, wherein the additional time interval is based on a value of the SCS.

9. The method of claim 7, wherein the additional time interval is reported by the UE.

10. The method of claim 7, wherein the additional time interval is defined in a wireless specification.

11. A base station (BS) in a wireless communication network, the BS comprising: a radio frequency (RF) transceiver configured to transmit and receive via at least one antenna; and a processing circuit coupled to the RF transceiver, the processing circuit being configured to cause the BS to: scheduling a plurality of physical downlink shared channels (PDSCHs) simultaneously through a single DCI transmitted via a physical downlink control channel (PDCCH), wherein each of the plurality of PDSCHs is associated with a respective cell of the plurality of cells; and Data is transmitted to or received from a user equipment (UE) based on the scheduling information, wherein the plurality of PDSCHs occur in time no earlier than a time offset after the PDCCH.

12. The BS according to claim 11, wherein a subcarrier spacing (SCS) associated with the PDCCH is equal to an SCS of at least one of the plurality of PDSCHs, and Wherein the time offset is measured between an end of the PDCCH and a start of the at least one PDSCH of the plurality of PDSCHs.

13. A BS according to claim 11, wherein a subcarrier spacing (SCS) associated with the PDCCH and the SCS of the at least one PDSCH among the multiple PDSCHs are different, and maintaining the time offset between the PDCCH and the at least one PDSCH among the multiple PDSCHs also includes maintaining the time offset between the PDCCH and all PDSCHs among the multiple PDSCHs. The BS of claim 11 , wherein the time offset is measured in units of symbols.

15. The BS of claim 11, wherein the time offset is between an end of the PDCCH and a start of a scheduled PDSCH.

16. The BS of claim 11, wherein the time offset is between a start of the PDCCH and a start of a scheduled PDSCH.

17. The BS of claim 11, wherein the time offset comprises an additional time interval, the additional time interval being based on a capability of a UE.

18. The BS of claim 17, wherein the additional time interval is based on a value of the SCS. The BS of claim 17 , wherein the additional time interval is reported by the UE.

20. The BS of claim 17, wherein the additional time interval is defined in a wireless specification.

Images