Patent Application
20230075748
The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for NBIoT HARQ related enhancement in non-terrestrial network (NTN).
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplex (FDD), Frequency Division Multiple Access (FDMA), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM or Flash Memory), Compact Disc Read-Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), Personal Digital Assistant (PDA), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Synchronous Dynamic RAM (SDRAM), Static RAM (SRAM), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic LED (OLED), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Time-Division Duplex (TDD), Time Division Multiplex (TDM), User Entity/Equipment (Mobile Terminal) (UE), Uplink (UL), Universal Mobile Telecommunications System (UMTS), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Downlink Control Channel (PDCCH), Downlink control information (DCI), single DCI (S-DCI), transmission reception point (TRP), multiple TRP (multi-TRP or M-TRP), frequency range 2 (FR2), Quasi Co-Location (QCL), channel state information reference signal (CSI-RS), CSI-RS Resource Indicator (CRI), Code Division Multiplexing (CDM), Transmission Configuration Indication (TCI), Sounding Reference Signal (SRS), Control Resource Set (CORESET), Synchronization Signal (SS), reference signal (RS), non-terrestrial networks (NTN), terrestrial network (TN), Transport Block (TB), Internet-of-Things (IoT), Narrowband Internet-of-Things (NB-IoT or NBIoT), NBIoT PUSCH (NPUSCH), NBIoT PDCSH (NPDSCH), NBIoT PDCCH (NPDCCH), Machine-Type Communication (MTC), MTC PDCCH (MPDCCH), receiver and transmitter distance (RTD), Hybrid Automatic Repeat reQuest (HARQ), uplink control information (UCI), modulation and coding scheme (MCS), Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), new data indicator (NDI).
In Release 13 NBIoT, a downlink TB is mapped to NSF subframes and transmitted with NRep repetitions. NSF and NRep are indicated by ISF (resource assignment index) and IRep (transmission repetition number index) in DCI format N1 separately. The relationship of NSF and ISF is shown in Table 1. The relationship of NRep and IRep is shown in Table 2. The scheduling delay of the NPDCCH and corresponding PDSCH (e.g. NPDSCH) is k0. k0 is determined by IDelay (scheduling delay index) (3 bits in DCI) and Rmax (the configured maximal transmission repetitions of control signal (e.g. NPDCCH)). The scheduling delay index (IDelay) is indicated in DCI format N1 with 3 bits. The configured maximal transmission repetitions of control signal (Rmax) is transmitted by RRC signaling. The relationship of scheduling delay (k0) and the scheduling delay index (IDelay) and the configured maximal transmission repetitions of control signal (Rmax) is shown in Table 3.
Table 1 indicates the number of subframes (NSF) for NPDSCH depending on resource assignment index (ISF).
Table 2 indicates the number of repetitions (NRep) for NPDSCH depending on transmission repetition number index (IRep).
Table 3 indicates the scheduling delay k0 depending on the scheduling delay index (IDelay) and the configured maximal transmission repetitions of control signal (Rmax).
The long receiver and transmitter distance (RTD) in NTN has an impact on HARQ timing, number of HARQ processes, link level enhancement. The existing NR timing definitions involving DL-UL timing interaction may not hold when there is a large offset in the UE's DL and UL frame timing in NTN. This disclosure targets the enhancement on link level, coverage, scheduling timing, HARQ disabling, UCI feedback, etc, in non-terrestrial network (NTN).
Methods and apparatuses for NBIoT HARQ related enhancement in NTN are disclosed.
In one embodiment, a method comprises transmitting a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and transmitting or receiving a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
In one embodiment, the third number of time may be is determined by at least one of the resource assignment index (ISF), a scaling factor (KSF) and the type of network. The second number of transmission repetitions may be determined by at least one of the transmission repetition number index (IRep), a scaling factor (KRep) and the type of network. The control signal may be configured with a fourth number of maximal transmission repetitions, and the fourth number of maximal transmission repetitions may be determined by a scaling factor (Kmax). The first number of time slots may be determined by the scheduling delay index (IDelay) and a scaling factor (KDelay), especially when the scaling factor (KRep) is configured. Each of the above-identified scaling factors (KSF, KRep, Kmax, KDelay,) can be determined by at least one of the type of network, HARQ disabling indication, broadcast signal and RRC signal.
In another embodiment, the second number of transmission repetitions may be determined by the transmission repetition number index (IRep0) and an extension index (KRepExt). The The extension index (KRepExt) may be indicated by the NDI or a part of the HARQ resource indication of the control signal.
In some embodiment, the second number of transmission repetitions may be determined by the transmission repetition number index (IRep0) and an index offset (KRepOff). The first number of time slots may be determined by the scheduling delay index (IDelay0) and an index offset (KDelayOff). Each of the above-identified index offset (KRepOff, KDelayOff) may be determined by at least one of the type of network, HARQ disabling indication, broadcast signal and RRC signal.
In some embodiment, a HARQ disabling of the data signal may be indicated by a state of the MCS index, and MCS of the data signal is indicated by one of the NDI and the HARQ resource indication or a combination of the NDI and the HARQ resource indication of the control signal. In another embodiment, the method further comprises receiving a BPSK repetition sequence with phase shift or a QPSK repetition sequence indicating a downlink transmission indication and ACK or NACK of the data signal. The downlink transmission indication may indicate whether or not a DL decoding probability is larger than a preconfigured threshold in the last fifth number of time periods. The fifth number of time periods may be a minimum value of a predefined time period configured in RRC signaling or broadcast signaling and a time period of two ACK/NACK transmission intervals.
In one embodiment, a method comprises receiving a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and transmitting or receiving a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
In another embodiment, a remote unit comprises a receiver and a transmitter, wherein the receiver is configured to receive a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and the transmitter or the receiver is configured to transmit or receive a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
In yet another embodiment, a base unit comprises a transmitter and a receiver, wherein the transmitter is configured to transmit a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and the transmitter or the receiver is configured to transmit or receive a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit”, “module” or “system”. Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code”. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Certain functional units described in this specification may be labeled as “modules”, in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash Memory), portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Reference throughout this specification to “one embodiment”, “an embodiment”, or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment”, “in an embodiment”, and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof mean “including but are not limited to”, unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a”, “an”, and “the” also refer to “one or more” unless otherwise expressly specified.
Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.
Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.
The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
The first embodiment relates to link level enhancement for NBIoT or eMTC.
According to a first sub-embodiment, NBIoT downlink or uplink resource mapping for a particular transport block (i.e. a TB is mapped to several consecutive valid subframes) is determined by, in addition to the existing resource assignment index (e.g. ISF), a scaling factor KSF in order to compensate path loss of long distance of satellite. The scaling factor KSF is separately configured depending on network type (e.g. NTN or TN). In other words, NBIoT downlink (or uplink) resource mapping is determined by the network type (e.g., TN or NTN). The networks type may be indicated by higher layer signaling.
For example, in the case of NPDCCH scheduling NPDSCH, a downlink TB can be mapped to KSF×NSF subframes and transmitted with NRep repetitions. NSF and NRep are indicated in DCI format N1 by ISF and IRep (see Table 1 and Table 2). KSF is configured by higher layer, e.g. by broadcast signaling. So, KSF may be common for all UEs within the NTN network, or within the TN network. For example, for NTN network with HARQ, KSF is set to 2; for NTN network without HARQ, KSF is set to 4; and for TN network, KSF is set to 1.
According to a second sub-embodiment, downlink or uplink NBIoT transmission repetition number (i.e. how many repetitions of the TB are transmitted) is determined by, in addition to the existing transmission repetition number index (e.g. IRep), a scaling factor KRep in order to compensate path loss of long distance of satellite. The scaling factor KRep is separately configured depending on network type (e.g. NTN or TN). In other words, NBIoT transmission repetition number is determined by the network type (e.g., TN or NTN). The networks type may be indicated by higher layer signaling.
For example, in the case of NPDCCH scheduling NPDSCH, a downlink TB can be mapped to NSF subframes and transmitted with KRep×NRep repetitions. NSF and NRep are indicated in DCI format N1 by ISF and IRep (see Table 1 and Table 2). KRep is configured by higher layer. For example, for NTN network with HARQ, KRep is set to 2; for NTN network without HARQ, KRep is set to 4; and for TN network, KRep is set to 1.
According to a third sub-embodiment, the table of the number of repetitions (e.g. NRep) is extended to compensate path loss of long distance of satellite, especially for NTN network without HARQ. Table 4 indicates an example of the extended table of the number of repetitions.
With reference to Table 2, the NRep can be indicated by IRep with four (4) bits since there are only 16 possible values for IRep in Table 2. When the number of repetitions (e.g. NRep) table is extended as illustrated in Table 4, new indication method is necessary.
A first new indication method is to use extension repetition indication. For example, 5 bits can be used to indicate the repetition number. Among the 5 bits, 16 states of the 5 bits are indicated by existing transmission repetition number index (referred to as IRep0 in this embodiment); and extra 1 bit (extension index KRepExt) can use the field “NDI” or part of the the field “HARQ-ACK resource” to indicate. The field “NDI” is new data indicator and occupies 1 bit. The field “HARQ-ACK resource” is used to indicate the time and frequency resource for ACK or NACK of the downlink data, and occupies 4 bits in DCI format N1. The field “NDI” or one bit of the field “HARQ-ACK resource” can be used to indicate the extension index (KRepExt).
A second new indication method is to use existing transmission repetition number index (referred to as IRep0 in this embodiment) to indicate 4 bits, and to configure a repetition index offset KRepOff to indicate an offset from IRep0. That is, the index IRep to indicate the repetition number is calculated by IRep=IRep0+KRepOff. IRep0 is indicated by DCI format N1 (see IRep in Table 2). KRepOff is configured by higher layer. For example, for NTN network with HARQ, KRepOff is set to 2; for NTN network without HARQ, KRepOff is set to 4; and for TN network, KRepOff is set to 0.
In view of the above, the NBIoT transmission repetition number is determined by an extension repetition indication or by a repetition index offset KRepOff in addition to existing transmission repetition number index.
The above third sub-embodiment is described with reference to the downlink TB (e.g. NPDCCH scheduling NPDSCH). It is apparent that the same extension applies to the uplink TB (e.g. NPDCCH scheduling NPUSCH).
The second embodiment relates to coverage enhancement for NBIoT or eMTC (i.e. NPDCCH or MPDCCH).
The NPDCCH maximum repetition Rmax is adjusted by a scaling factor Kmax. The scaling factor Kmax is separately configured depending on network type (e.g. NTN or TN). In other words, maximum repetition is determined by the network type (e.g., TN or NTN).
For example, the maximum repetitions of the NPDCCH is determined by Kmax×Rmax. Kmax is configured by higher layer. For example, for NTN network with or without HARQ, Kmax is set to 2; and for TN network, Kmax is set to 1. Accordingly, the NPDCCH blind detection candidates are derived by Kmax×Rmax. The configured maximal transmission repetitions of control signal (Rmax) contained in Table 3 should also be updated to Kmax×Rmax. For example, the conditions “Rmax<128” and “Rmax≥128” should be updated to “Kmax×Rmax<128” and “Kmax×Rmax≥128”. Downlink gap scheduling activation condition should also be updated to e.g. Kmax×Rmax>Ngap,threshold. If the condition is met, an additional DL gap is inserted in NPDCCH and NPDSCH transmissions.
For NPDCCH transmission, the locations of starting subframe k are given by k=kb where kb is the bth consecutive NB-IoT DL subframe from subframe k0, excluding subframes used for transmission of SI messages, and b=u·R, and
and where
For NPDCCH UE-specific search space, G is given by the higher layer parameter npdcch-StartSF-USS, αoffset is given by the higher layer parameter npdcch-Offset-USS, Kmax=2 for NTN with or without HARQ, Kmax=1 for TN.
Table 5 illustrates NPDCCH UE-specific search space candidates.
In Table 5, the first column criterion is Rmax·Kmax. In addition, when Rmax·Kmax>=8, the candidate R is Rmax·Kmax/8, Rmax·Kmax/4, Rmax·Kmax/2 and Rmax·Kmax, respectively. That is, the scaling factor Kmax is considered.
The third embodiment relates to scheduling timing enhancement.
Due to the long RTD in NR NTN, an existing offset Koffset is introduced to compensate the scheduling delay k0. That is, delay=k0+Koffset.
According to the third embodiment, an extra scaling factor KDelay is further introduced to scale the time offset due to increase of transmission repetition number for NBIoT over satellite. The scaling factor KDelay is separately configured depending on network type (e.g. NTN or TN). In other words, the scheduling delay is determined by the network type (e.g., TN or NTN).
For example, delay=KDelay×k0+Koffset. KDelay is configured by higher layer. For example, for NTN network with HARQ, KDelay is set to 2; for NTN network without HARQ, KDelay is set to 4; and for TN network, KDelay is set to 1. Koffset is used for compensating the long receiver and transmitter distance (RTD) between eNB and UE in NTN.
In addition, the scheduling delay is preferably compensated in the same way as the repetition number NRep. For example, KDelay may be configured when the scaling factor KRep is configured. More preferably, KDelay may be configured with the same value as KRep.
Alternatively, instead of introducing the scaling factor KDelay, the scheduling delay k0 table may be extended in a similar way to the extended repetition table as illustrated in Table 4. A delay index offset KDelayOff can be configured to indicate an offset from existing scheduling delay index IDelay.
Table 5 indicates an example of extended table of the scheduling delay.
For example, the index IDelay to indicate the repetition number is calculated by IDelay=IDelay0+KDelayOff. IDelay0 (see IDelay in Table 3) is indicated in DCI format N1. KDelayOff is configured by higher layer. For example, for NTN network with HARQ, KDelayOff is set to 2; for NTN network without HARQ, KDelayOff is set to 4; and for TN network, KDelayOff is set to 0.
The third embodiment is described with reference to downlink (i.e. NPDCCH scheduling NPDSCH). It is apparent that the same extension applies to uplink (i.e. NPDCCH scheduling NPUSCH).
The fourth embodiment relates to HARQ disabling enhancement.
Due to long RTD in NTN, HARQ disabling is necessary. According to the fourth embodiment, one of unused states of “Modulation and coding scheme” (MCS) field can be used to indicate HARQ disabling. Since the MCS field is used to indicate HARQ disabling, the modulation and coding scheme (MCS) cannot be indicated by the MCS field. On the other hand, as HARQ is disabled, the HARQ related field(s) are unnecessary. Therefore, for example, one of the “NDI” field and the “HARQ-ACK resource” field or a combination of the two fields may be used to indicate the modulation and coding scheme (MCS). In this way, no scheduling flexibility loss is caused.
The fifth embodiment relates to UCI feedback enhancement.
When HARQ feedback and other lower layer feedbacks are disabled, network may have to rely on RLC feedbacks or other higher layer feedbacks, which could lead to a waste of bandwidth. According to the fifth embodiment, a BPSK modulation repetition sequence with sequence element phase shift (each sequence element with two phases for its constellation along with their phase shifts (e.g. clockwise of 90° to another two phases)) is used to indicate a downlink transmission indication and ACK or NACK of the data signal. The downlink transmission indication indicates the DL transmission disruption and requesting DL scheduling change. For example, the downlink transmission indication may indicate whether or not a DL decoding probability is larger than a preconfigured threshold in a last predetermined number of time periods.
For example, two phases of the BPSK modulation repetition sequence element are 45° and 225°, and their 90° clockwise phase shifts are 135° and 315°. Therefore, four different phases can be used to indicate four different situations: ACK of the data signal and positive downlink transmission indication; ACK of the data signal and negative downlink transmission indication; NACK of the data signal and positive downlink transmission indication; and NACK of the data signal and negative downlink transmission indication.
Alternatively, a QPSK modulation repetition sequence (with four phases, e.g., 45°, 135°, 225° and 315°) may be used to indicate the downlink transmission indication and ACK or NACK of the data signal.
The downlink transmission indication indicates whether or not a DL decoding probability is larger than a preconfigured threshold in the last X time periods. The X time periods are a minimum value of {X0, a time period of two ACK/NACK transmission intervals}, in which X0 is configured in RRC signaling or broadcast signaling.
The method 200 may include 202 transmitting a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and 204 transmitting or receiving a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
The method 300 may include 302 receiving a control signal, the control signal includes at least one of a transmission repetition number index, a scheduling delay index, a resource assignment index, a NDI, a HARQ resource indication, and a MCS index; and 304 transmitting or receiving a data signal based on the control signal, the data signal starts at the end of the control signal plus a first number of time slots, the data signal includes a second number of transmission repetitions of a third number of time durations.
Referring to
The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.
In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.
The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and the like.
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2020/075189 | 2/14/2020 | WO |
