Method and device for low-latency transmission

Abstract

The present invention relates to a method and apparatus for low-latency transmission. A resource assignment can be received (1620). A first set of time-frequency resources in a subframe can be determined from the resource assignment (1630). A second set of time-frequency resources in a subframe can be determined (1640). The second set of time-frequency resources can be used for low-latency data transmission. The second set of time-frequency resources can overlap with at least a portion of the first set of time-frequency resources. Based on the determined first set of time-frequency resources and second set of time-frequency resources, a conventional delayed data transmission in a subframe can be decoded (1650). Conventional delayed transmission can have a longer delay than low-latency transmission.

Description

[0001] This application is a divisional application of an application which entered the Chinese national phase on May 4, 2018, with PCT application number PCT / US2016 / 059850, international application date November 1, 2016, Chinese application number 201680064600.1, and invention name “Method and device for low-latency transmission”. Technical Field

[0002] The present disclosure is directed to a method and apparatus for low-latency transmission. More particularly, the present disclosure is directed to wireless transmission, signaling, and frame structures of devices configured for low-latency data packets while maintaining backward compatibility with devices configured for normal-latency data packets. Background Art

[0003] Currently, users use wireless communication devices, also known as user equipment (UE), such as smart phones, cellular phones, tablet computers, selective call receivers and other wireless communication devices on long-term evolution (LTE) networks, wireless local area networks (WLAN) and other wireless communication networks. Users use these devices to download files, music, email messages and other data, as well as watch streaming videos, play streaming music, play games, browse the web and participate in other data-intensive activities.

[0004] Packet data delay is one of the performance metrics widely used in benchmark system performance testing. Packet data delay is not only important for the perceived responsiveness of the system; it is also a parameter that indirectly affects throughput. Certain types of business are sensitive to delay and require reduction in the delay of their data packets. These delay-sensitive business types can include Internet voice protocols such as for phone calls, can include games, can include motor vehicle control signals, and can include other time-sensitive business types. HTTP / TCP is the main application and transport layer protocol family used on the Internet today, and the TCP slow start period is an important part of the total transmission period of the packet flow. During TCP slow start, performance is limited by delay. Therefore, for this type of TCP-based data transactions, improving delay can improve average throughput. Delay-sensitive business types require reducing downlink and uplink packet delays, such as reducing the time it takes for devices to transmit and receive data and signals in connected mode. This is in contrast to normal delay data packets, which are used for business types such as file downloads and uploads, which are less sensitive to delay because delays have minimal impact on file transfers and normal delays are not noticeable to users.

[0005] Technical issues

[0006] In order to support delay-sensitive business types and other delay-sensitive new use cases, expand the application of LTE and other wireless communication systems to a wider range of scenarios, and enhance LTE to provide a better user-perceived experience, it is necessary to support low latency by enhancing LTE and other wireless communication systems. Unfortunately, current devices do not properly provide structures for low-latency transmission. Therefore, a method and apparatus for low-latency transmission is needed. Summary of the invention

[0007] The present invention relates to a method for low-latency transmission, comprising: transmitting resource assignment, wherein the resource assignment assigns a first set of time-frequency resources in a subframe to regular delay data transmission; transmitting low-latency data within a second set of time-frequency resources in the subframe, wherein the second set of time-frequency resources at least partially overlaps with the first set of time-frequency resources, wherein the low-latency data has a lower delay than regular delay data; and transmitting a marking signal, wherein the marking signal indicates the presence of low-latency data transmission in the subframe.

[0008] The present invention also relates to a method for low-latency transmission, comprising: receiving resource assignment; determining a first set of time-frequency resources in a subframe from the resource assignment; determining a second set of time-frequency resources in the subframe, the second set of time-frequency resources being used for low-latency data transmission, and the second set of time-frequency resources overlapping with at least a portion of the first set of time-frequency resources; and decoding regular delay data transmission in the subframe based on the determined first set of time-frequency resources and second set of time-frequency resources, wherein the regular delay transmission has a longer delay than the low-latency transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented with reference to the specific embodiments of the present disclosure shown in the accompanying drawings. These drawings depict only exemplary embodiments of the present disclosure and therefore should not be considered as limiting the scope thereof.

[0010] Figure 1 is an example illustration of a system according to a possible embodiment;

[0011] Figure 2 is an example illustration of a subframe according to a possible embodiment;

[0012] Figure 3 is an example illustration of a subframe according to a possible embodiment;

[0013] Figure 4 is an example illustration of an orthogonal frequency division multiplexing symbol according to a possible embodiment;

[0014] Figure 5 is an example illustration of a transmission time interval according to a related embodiment;

[0015] Figure 6 is an example illustration of a transport block according to a possible embodiment;

[0016] Figure 7 is an example illustration of a transport block according to a possible embodiment;

[0017] Figure 8 is an example illustration of a transport block according to a possible embodiment;

[0018] Fig. 9 is an example illustration of a subframe according to a possible embodiment;

[0019] Fig.10 is an example illustration of a subframe according to a possible embodiment;

[0020] Fig.11 is an example illustration of a subframe according to a possible embodiment;

[0021] Fig.12 is an example flow chart illustrating the operation of a device according to a possible embodiment;

[0022] Fig.13 is an example flow chart illustrating the operation of a device according to a possible embodiment;

[0023] Fig.14 is an example flow chart illustrating the operation of a device according to a possible embodiment;

[0024] Fig.15 is an example flow chart illustrating the operation of a device according to a possible embodiment;

[0025] Fig.16 is an example flow chart illustrating the operation of a device according to a possible embodiment;

[0026] Fig.17 is an example block diagram of an apparatus according to a possible embodiment;

[0027] Fig.18 is an example block diagram of a device according to a possible embodiment;

[0028] Fig.19 is an example illustration of a subframe according to a possible embodiment;

[0029] Fig. 20 is an example illustration of a subframe according to a possible embodiment;

[0030] Fig.21 is an example illustration of a subframe according to a possible embodiment;

[0031] Fig. 22 is an example illustration of a subframe according to a possible embodiment;

[0032] Fig.23 is an example flow chart illustrating the operation of the device according to possible embodiments; and

[0033] Fig.24 is an example flow chart illustrating the operation of a device according to a possible embodiment. DETAILED DESCRIPTION

[0034] Embodiments can provide methods and apparatus for low-latency transmission.

[0035] According to a possible embodiment, a higher layer configuration message can be received. Based on the higher layer configuration message, a first region of a subframe for receiving a data packet can be determined. The first region can include a first set of resource elements. The first set of resource elements can be a subset of a second set of resource elements in the first region. The first region can be used for control channel monitoring. The data packet can be mapped to at least one resource element of the first set of resource elements. The first region can be monitored by attempting to decode the data packet in the first region. Data in the data packet in the first region can be decoded.

[0036] According to another possible embodiment, a higher layer configuration message indicating a resource block set for receiving a data packet in at least one symbol of a subframe can be received. In another embodiment, the higher layer configuration message can indicate which time-frequency resources may be candidates for transmission of low-latency related transmissions. Low-latency related transmissions can include low-latency data, low-latency decoding auxiliary information, and other low-latency transmissions. The data packet can be attempted to be decoded in a first resource element set within a resource block set. The first resource element set can be in at least one symbol of a subframe. The data packet can be attempted to be decoded in at least a second resource element set within a resource block set. The second resource element set can be in at least one symbol of a subframe. The second resource element set can include at least one resource element that is not in the first resource element set. The data packet can be successfully decoded in one of the first resource element set and the second resource element set. The data payload of the decoded data packet can be delivered to the application layer.

[0037] According to another possible embodiment, a higher layer configuration can be received at the device. The higher layer configuration can be higher than the physical layer configuration. In addition to the conventional delay configuration of the conventional delay transmission mode, the higher layer configuration can also indicate the use of the low delay configuration of the low delay transmission mode to configure the device. The low delay transmission mode can have a lower delay than the conventional delay transmission mode. A packet can be received based on one of the low delay configuration and the conventional delay transmission mode in subframe n. A feedback packet can be transmitted in a subsequent subframe n+p, wherein, when the received packet is based on the low delay configuration, p<4, wherein the subsequent subframe n+p can be the pth subframe from subframe n. When the received packet is based on the conventional delay configuration, a feedback packet can be transmitted in a subsequent subframe n+4, wherein the subsequent subframe n+4 can be the 4th subframe from subframe n.

[0038] According to another possible embodiment, a resource assignment can be transmitted. The resource assignment can assign a first set of time-frequency resources in a subframe to a conventional delay data transmission. Low-latency data can be transmitted within a second set of time-frequency resources in a subframe. The second set can overlap at least partially with the first set. The low-latency data can have a lower latency than the conventional delay data. A marker signal can be transmitted. The marker signal can indicate the presence of low-latency data transmission in the subframe.

[0039] According to another possible embodiment, a resource assignment can be received. From the resource assignment, a first set of time-frequency resources in a subframe can be determined. A second set of time-frequency resources in a subframe can be determined. The second set of time-frequency resources can be used for low-latency data transmission. The second set of time-frequency resources can overlap with at least a portion of the first set of time-frequency resources. Based on the determined first set of time-frequency resources and second set of time-frequency resources, a conventional delayed data transmission in a subframe can be decoded. The conventional delayed transmission can have a longer delay than the low-latency transmission.

[0040] According to another possible embodiment, a first control channel can be transmitted in a first time portion of a subframe. A subframe can include a plurality of orthogonal frequency division multiplexing (OFDM) symbols in a time domain and a plurality of subcarriers in a frequency domain. The first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can assign a first data resource only in the first time portion of a subframe. A second control channel can be transmitted in a second time portion of a subframe. The first time portion can occupy at least one first OFDM symbol in a subframe that is different from the second time portion. The second time portion can occupy at least one second OFDM symbol in a subframe that is different from the first time portion. The second control channel can occupy a second subcarrier portion less than the plurality of subcarriers. The second control channel can assign a second data resource only in the second time portion of a subframe.

[0041] According to another possible embodiment, a first control channel can be monitored in a first time portion of a subframe. A subframe can include a plurality of orthogonal frequency division multiplexing (OFDM) symbols in a time domain and a plurality of subcarriers in a frequency domain. A first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can assign data resources only in the first time portion of a subframe. A second control channel can be monitored in a second time portion of a subframe. The first time portion can occupy at least one OFDM symbol in a subframe that is different from the second time portion. The second time portion can occupy at least one OFDM symbol in a subframe that is different from the first time portion. A second control channel can occupy a second subcarrier portion less than the plurality of subcarriers. The second control channel can assign data resources only in the second time portion of a subframe. The first control channel can be decoded. In response to decoding the first control channel, data can be received in the first time portion of a subframe. The data in the first time portion can be assigned by the first control channel. The data can be decoded.

[0042] According to some embodiments, in order to support new use cases and expand the application of long term evolution (LTE) and other wireless communications to a wider range of scenarios, and to enhance LTE to provide a better user perceived experience, it is necessary to support lower latency by enhancing LTE. These embodiments can provide new frame structures and other features to support devices that require lower latency while supporting devices with conventional latency.

[0043] Figure 11 is an example illustration of a system 100 according to a possible embodiment. The system 100 can include a first device 110 and a second device 120. Although the first device 110 is illustrated as a user equipment (UE) and the second device 120 is illustrated as a base station such as an enhanced node B (eNB), the roles can also be interchanged. In addition, the devices 110 and 120 can be the same type of device, such as a UE or a base station, and can be any other type of device capable of sending and receiving wireless communication signals. For illustrative purposes, in some embodiments, the first device 110 can be referred to as a UE and the second device 120 can be referred to as a base station, but it should be understood that in all embodiments, the first device and the second device 120 can be any transmitting and / or receiving device. The first device 110 and the second device 120 can communicate on different cells 130 and 140. The system 100 can also include another device 112, which can communicate with the second device 120 on different cells 132 and 142 in a manner similar to the first device 110. The devices 110 and 112 can be any device capable of accessing a wireless network. For example, devices 110 and 112 may be UEs, such as wireless terminals, portable wireless communication devices, fixed wireless communication devices, smart phones, cellular phones, flip phones, personal digital assistants, personal computers with cellular network access cards, selective call receivers, tablet computers, or any other devices capable of operating on a wireless network.

[0044] The communication system 100 can utilize orthogonal frequency division multiple access (OFDMA) or a next generation single carrier based FDMA architecture for uplink transmission, such as interleaved FDMA (IFDMA), localized FDMA (LFDMA), discrete Fourier transform-spread OFDM (DFT-SOFDM) using IFDMA or LFDMA. In other embodiments, the architecture may also include spread spectrum techniques such as direct sequence CDMA (DS-CDMA), multi-carrier CDMA (MC-CDMA), multi-carrier direct sequence CDMA (MC-DS-CDMA), orthogonal frequency division and code division multiplexing (OFCDM) using one-dimensional or two-dimensional spreading, or simpler time division and frequency division multiplexing / multiple access techniques. In another embodiment, the wireless communication system complies with the 3GPP Universal Mobile Telecommunications System (UMTS) LTE protocol, also known as EUTRA or its descendants, wherein the base unit transmits on the downlink using an orthogonal frequency division multiplexing (OFDM) modulation scheme, and the user terminal transmits on the uplink using a single carrier frequency division multiple access (SC-FDMA) scheme. In yet another embodiment, the wireless communication system complies with the 3GPP Universal Mobile Telecommunications System (UMTS) LTE Advanced protocol, also known as LTE-A or its descendant or its LTE version, wherein the base unit can transmit on a single or multiple downlink component carriers using an orthogonal frequency division multiplexing (OFDM) modulation scheme, and the user terminal can transmit on the uplink using a single or multiple uplink component carriers. More generally, the wireless communication system can implement some other open or proprietary communication protocols, for example, other existing and future protocols such as WiMAX. The architecture that implements the features of these embodiments can also be based on simpler time division and / or frequency division and / or space division multiplexing / multiple access technologies or a combination of these different technologies. In an alternative embodiment, the wireless communication system can utilize other communication system protocols, including but not limited to time division multiple access (TDMA) or direct sequence code division multiple access (CDMA). The communication system can be a time division duplex (TDD) or frequency division duplex (FDD) system.

[0045] In an OFDM system, or similar OFDM systems such as DFT-SOFDM and IFDMA, resource allocation is the frequency and time allocation that maps information for a particular communication device or remote unit to subcarrier resources in a set of available subcarriers, as determined by a scheduler. The allocation may, for example, depend on a frequency selective channel quality indication (CQI) or some other metric reported to the scheduler by a remote unit such as a user equipment. The channel coding rate and modulation scheme, which may be different for different portions of the subcarrier resources, are also determined by the scheduler and may also depend on the reported CQI or other metric. In a code division multiplexing network, resource allocation is the code allocation that maps information for a particular communication device or remote unit to channelization code resources in a set of available channelization codes, as determined by a scheduler.

[0046] In LTE, a radio frame can generally include multiple subframes, which can form a cascaded subframe continuum. An example radio frame contains 10 subframes. Each subframe can correspond to a transmission time interval (TTI). An example TTI is 1 millisecond. Each subframe can consist of two time slots, each of which has a length of 0.5ms, and in view of the normal cyclic prefix length, each time slot, for example, contains 7 OFDM symbols, while if an extended cyclic prefix length is used, there are only 6 OFDM symbols. Each subframe can consist of a control region and a data region. The control region can include one or more OFDM symbols in the time domain, or one or more resource blocks in the frequency domain. In a communication system, an assigned channel can be used to send data and also for control signaling or message transceiving of the system. A control signal or message can be transmitted in a control channel (CCH) and used for forward link transmission (also known as downlink transmission) from a network or base station to a user equipment or device and reverse link transmission (also known as uplink transmission) from a user equipment or device to a network or base station. In systems such as LTE of UTRA, where a downlink control channel consists of a single decodable element (referred to as a control channel element (CCE)) or an aggregation of decodable elements (referred to as multiple control channel elements (CCEs)), a user equipment can identify a subset of CCEs intended for a specific user equipment from a large set of CCEs. In one embodiment, a user equipment can be configured to attempt to decode a low-latency packet or message transmitted in a control region. The user equipment can be configured to monitor a subset of CCEs for low-latency packets, denoted as low-latency CCEs (LL-CCEs), intended for possible low-latency data transmission to the user equipment. The subset of CCEs intended for a specific user equipment to monitor or attempt to decode at a specific CCE aggregation level L (e.g., L=1, 2, 4, or 8 CCEs) is referred to as a resource set for the user equipment at the specific CCE aggregation level L. The resource set for the user equipment can contain one or more resource subsets, wherein each resource subset can include one or more CCEs corresponding to an aggregation level, and the resource subset can correspond to a candidate downlink control channel, also known as a physical downlink control channel (PDCCH) candidate. The set of resource subsets for a specific CCE aggregation level L can correspond to a set of PDCCH candidates for aggregation level L monitored by a specific user equipment in a search space corresponding to the set of resources for the specific CCE aggregation level L. The size of the control region can be, for example, 1, 2 or 3 OFDM symbols, and can depend on the number of symbols signaled in a higher layer configuration message about a subframe, or can depend on the number of symbols signaled by a physical control format indicator channel (PCFICH), which can be transmitted in symbol 0 of each subframe control region and can consist of 4 resource element groups (REGs) distributed across frequency.Each REG can consist of 4 consecutive or nearly consecutive control resource elements and can also include up to 2 reference signals when the associated antenna port is configured. Each CCE can include 9 REGs pseudo-randomly distributed or interleaved across frequencies and OFDM control symbols in the control region based on a sub-block interleaver. The CCEs and corresponding REGs that can be used for low-latency data transmission can be the CCEs remaining after considering the PCFICH and the physical hybrid automatic repeat request (ARQ) indicator channel (PHICH) and the control channel CCE in the control region. The physical downlink control channel (PDCCH) can include, for example, 1, 2, 4 or 8 CCEs, depending on the CCE aggregation level L. PDCCH can be associated with a DCI format type. PDCCH transmits downlink control information (DCI) of a given DCI format type containing data assignments. Two or more DCI format types may have the same DCI format size or may have different DCI format sizes. The number of DCI format types assigned to the user equipment for monitoring can depend on the transmission mode assigned to the user equipment via higher layer signaling such as radio resource control (RRC) signaling, such as downlink MIMO or downlink single antenna. In the case of aggregating more than 1 CCE to form a PDCCH, the CCE can be logically continuous in terms of the position in the PDCCH candidate search space. For one or more DCI format types, the PDCCH candidate position can be the same. The data area can contain data symbols, such as QAM symbols, with each resource element (RE) having one data symbol. 12 consecutive resource elements within a time slot duration can be grouped to form a resource block (RB). A resource block can span a time slot or 7 OFDM symbols for a normal cyclic prefix length, so that two RBs (or a single RB pair) span a subframe. The number of data OFDM symbols in the first RB corresponding to the first time slot in the subframe can be reduced by the number of allocated OFDM control symbols. In one embodiment, the user equipment can attempt to decode the control channel and low-latency data transmission in the control area. The user equipment is able to identify the control channel based on a first RNTI (e.g., C-RNTI) and to identify the low-latency data packet based on a second RNTI (e.g., LL-RNTI). The aggregation level set of low-latency data packet candidates may be the same as, a subset of, or different from the aggregation level set of PDCCH candidates monitored by the UE. In some embodiments, for a particular aggregation level, the search space for low-latency data packets may be the same as the search space for PDCCH. In other embodiments, for a particular aggregation level, the search space for low-latency data packets may be a subset of the search space for PDCCH or different from (e.g., non-overlapping, partially overlapping).In some embodiments, for a specific aggregation level, the search space for low-latency data packets may be offset from the search space for PDCCH. The offset may be based on the number of PDCCH candidates for the specific aggregation level and the value of the specific aggregation level. This method can prevent blocking when multiple uplinks and / or multiple downlink scheduling permissions or assignments occur in the control region of a subframe. In some embodiments, one or more of the possible low-latency data payload sizes associated with the monitored low-latency data packet candidates may be the same as, a subset of, or different from the DCI format size associated with the monitored PDCCH candidate. In one embodiment, the user equipment may first attempt to decode the control channel candidate using its C-RNTI for a specific aggregation level and candidate, and if this attempt fails, it can attempt to decode using LL-RNTI. Alternatively, it can attempt to decode the candidate using different downlink control information (DCI) format types that may have different DCI format sizes. In another embodiment, a new DCI format type can be defined for low-latency transmission or packetization. The new DCI format type for low latency data packets may have a different DCI format size than the DCI format size of the PDCCH for normal latency data packets. The DCI format type may also be referred to as a control channel message type.

[0047] In one embodiment, some of the REs in the data area can be reserved for supporting low-latency transmission. In one embodiment, REs can be used for low-latency data packet transmission. In other embodiments, REs can also be used for tag information transmission to assist user equipment in receiving conventional delayed transmission when decoding conventional delayed packet transmission and / or low-latency packet transmission.

[0048] In some embodiments, the user equipment can monitor low-latency control channel (e.g., LL-PDCCH) candidates using DCI containing resource assignments for low-latency data packets. Low-latency data packets can be transmitted in a data area from one or more data areas in a subframe. In an embodiment, the low-latency data packet can be transmitted in a data area associated with or based on the position of a control channel containing resource assignments for low-latency data packets. The relationship between the position of the low-latency data packet and the control channel containing low-latency data resource assignments can be predetermined (e.g., each subframe area can include a control channel and a low-latency data area, and the resource elements or resource element groups of the control channel and the low-latency data area can be interleaved in the subframe area), or determined by higher layer signaling (e.g., signaling of one or more configuration parameters such as gaps or offsets, OFDM symbols, resource block indexes, etc.). In another embodiment, the position of the low-latency data packet can be included in the DCI resource assignment message of the control channel corresponding to the low-latency data packet of the user equipment. A specific user equipment can locate the low-latency control channel element (blind decoding) corresponding to each LL-PDCCH candidate it monitors. The CRC of each LL-PDCCH can be masked by a unique identifier corresponding to the user equipment that the base station attempts to schedule. A unique identifier can be assigned to the UE by the UE's serving base station. The identifier can be called a radio network temporary identifier (RNTI), and the identifier usually assigned to each UE at call admission can be a cell RNTI or C-RNTI. The UE can also be assigned a semi-persistent scheduling C-RNTI (SPS C-RNTI) or a temporary C-RNTI (TC-RNTI) or a low-latency RNTI (LL-RNTI). When a UE configured to receive a low-latency transmission decodes the LL-PDCCH, in addition to the C-RNTI (for example, in the case where the LL-PDCCH can also be used for conventional delay data packet assignment, with the same DCI format size), the UE can also apply its LL-RNTI to the PDCCH CRC in the form of a mask so that the LL-PDCCH decoding is successfully performed when the low-latency transmission control channel has been transmitted to the user equipment. When a user equipment successfully decodes an LL-PDCCH of a specific DCI format type having a CRC masked with an LL-RNTI, the user equipment can use the control information in the decoded LL-PDCCH to determine, for example, resource assignment / hybrid ARQ information and power control information for corresponding low-latency data.

[0049] In LTE, DCI format types 0 and 4 are used to schedule uplink data transmission on the physical uplink shared channel (PUSCH), while DCI format type 1A is used to schedule downlink data transmission on the physical downlink shared channel (PDSCH). Other DCI format types are also used to schedule PDSCH transmissions, including DCI formats 1, 1B, 1D, 2, 2A, 2B, 2C, and 2D, each PDSCH transmission corresponding to a different transmission mode (e.g., single antenna transmission, single-user open-loop MIMO, multi-user MIMO, single-user closed-loop MIMO, rank 1 precoding, dual-layer transmission scheme, up to 8-layer transmission scheme). In addition, there are DCI formats 3 and 3A for scheduling the transmission of joint power control information. PDCCH DCI formats 0, 1A, 3, and 3A all have the same size payload and therefore have the same coding rate. Therefore, only one blind decoding is required for all 0, 1A, 3, and 3A of each PDCCH candidate. The CRC is then masked with the C-RNTI to determine whether the PDCCH is DCI format type 0 or 1A, and if the DCI format type is 3 or 3A, a different RNTI is determined. DCI format types 0 and 1A are distinguished by the DCI type bit in the PDCCH payload itself (i.e., part of the control information on one of the control information fields). The UE will always be required to search for all DCI formats 0, 1A at each PDCCH candidate position in the UE-specific search space. There are 4 UE-specific search spaces for aggregation levels 1, 2, 4 and 8. The UE is assigned only one of the DCI format types 1, 1B, 1D, 2, 2A, 2B, 2C or 2D at a time, so that in addition to the blind decoding required for DCI format types 0, 1A and possible DCI format type 4, the UE only needs to perform an additional blind decode for each PDCCH candidate position in the UE-specific search space. When the PDCCH candidate position is located in the UE-specific search space, the PDCCH candidate position is the same for the DCI format type. There are also two 16CCE common search spaces for aggregation levels 4 and 8, respectively, which are logically or sometimes physically (when there are 32 or more control channel elements) adjacent to the UE-specific search space. In the common search space, the UE monitors DCI types 0, 1A, 3 and 3A and DCI format type 1C. DCI format type 1C is used to schedule broadcast control, which includes paging, random access response, and system information block transmission. DCI 1A can also be used for broadcast control in the common search space. DCI 0 and 1A are also used to schedule PUSCH and PDSCH in the common search space.For DCI formats 0, 1A, 3 and 3A, in the L=4 common search space, the UE needs to perform up to 4 blind decodings, and in the L=8 common search space, the UE needs to perform 2 blind decodings, and the same number of blind decodings are performed again for DCI1C because the size of DCI 1C is different from that of DCI 0, 1A, 3 and 3A.

[0050] For UE-specific search spaces with L = (1, 2, 4, 8), the UE needs to perform (6, 6, 2, 2) blind decodings respectively, where L refers to the aggregation level of the search space. Therefore, for the two DCI format sizes in the UE-specific search space and the two DCI format sizes in the common search space, the maximum total number of blind decoding attempts that the UE needs to perform on each subframe control area is 44 (= 2×(6, 6, 2, 2) + 2×(4, 2)). The base station and the UE use a hash function to find the PDCCH candidate position in each search space. The hash function is based on the UE RNTI (an identifier associated with the UE, such as C-RNTI or temporary C-RNTI), the aggregation level (L), the total number of CCEs available in the control area (Ncce), the subframe number or index, and the maximum number of PDCCH candidates in the search space. Such an approach prevents blocking when multiple control channels and / or low-latency data packets appear in the same area of ​​a subframe.

[0051] In one embodiment, a method in a base station can indicate a low-latency message resource subset corresponding to a low-latency message, and based on at least one low-latency message type (e.g., LL xyz format type) of a low-latency message sent to a UE, the base station can select the low-latency message resource subset from one of one or more candidate resource subsets in a search space within a control or data region. The low-latency message type may correspond to an identifier other than a PDCCH DCI format type. The UE can determine which resource set in the search space to use for a blind decoding attempt based at least in part on a position offset and an identifier, the position offset (in terms of the number of CCEs or aggregated CCEs or the number of candidates at an aggregation level) being associated with or determined by the low-latency message type of the low-latency message that the UE is searching for, and the identifier is associated with the UE. Therefore, each resource set located in the search space can include a candidate resource subset of a specific message type, which has a position offset relative to a resource set having a 0 offset or relative to a position of a reference resource set. The base station can use a resource subset selected from a resource set associated with the low-latency message type to transmit low-latency message information for the UE via a selected subset of resource elements. The UE can use blind decoding attempts to determine which subset of resources in the set of resources in the search space is used to transmit the low-latency message.

[0052] In one embodiment, a specific user equipment can locate the resource elements corresponding to each low-latency data channel candidate to be monitored by it (blind decoding is performed on each subframe control region). The CRC of each low-latency data channel can usually be masked by a unique identifier corresponding to the user equipment that the basic unit attempts to schedule. In other embodiments, the CRC can be masked with a public identifier of all low-latency data packets or user equipment that receives low-latency data packets. The UE can be assigned a unique identifier by the UE's serving base station. In one embodiment, the identifier can be referred to as a radio network temporary identifier (RNTI), and the identifier assigned to each UE can usually be a low-latency RNTI or LL-RNTI at call admission. The UE can also be assigned a semi-persistent scheduling C-RNTI (SPS C-RNTI) or a temporary C-RNTI (TC-RNTI) and a cell-specific C-RNTI. When the UE decodes the resource elements corresponding to the low-latency data packet, the UE can apply its LL-RNTI to the low-latency data packet CRC in the form of a mask to successfully decode. When a UE successfully decodes a low-latency data packet for it, the UE can then send the low-latency data packet to the application layer for use by appropriate services that require low-latency transmission. The UE may need to attempt to descramble the decoded packet in order to determine that the packet is for the UE. In one embodiment, all UEs are able to decode the low-latency packets, but if these UEs fail to successfully descramble the decoded packets, they may not be able to read the contents of the packets. The scrambling process of the base station before transmission allows the base station to protect the privacy of the user while allowing each user device to decode the packet.

[0053] Channel coding (e.g., convolutional coding) blind detection can be used to distinguish between PDCCH DCI formats with different sizes. For DCI formats of the same size, different masks of the scrambled CRC can be used, or alternatively, extra bits in the PDCCH payload itself can be used to distinguish between PDCCH DCI formats of the same size (e.g., DCI formats 0 and 1A). Examples include, but are not limited to, the case of broadcast control using SI-RNTI, P-RNTI, or RA-RNTI instead of C-RNTI for DCI format 1A.

[0054] In one embodiment, the UE search space can support 4 aggregation levels, including (1, 2, 4 or 8) logically consecutive CCEs for each PDCCH (candidate) hypothesis and low-latency data candidate with (6, 6, 2, 2) blind detection positions for each of the aggregation levels, respectively.

[0055] In determining the CCE position of the PDCCH or low-latency data candidate m corresponding to each aggregation level L (eg, L=(1, 2, 4, or 8)), In the method, the search space for subframe 'k' of a radio frame is given by the following equation:

[0056]

[0057] Among them, for the UE-specific search space, Y k =39827·Y k-1 mod65537w, where Y -1 =n_RNTI; n_RNTI≠0 is C-RNTI or temporary C-RNTI or LL-RNTI; N CCE,k is the total number of CCEs available in subframe k; for PDCCH candidates, m′=m; and for low-latency data candidates, m′=m+Δ(M (L) ), where Δ is based on the aggregation level L(M (L) ) is the offset of the number of PDCCH candidates to be monitored in the search space. For example, Δ = αM (L) , where α can take values ​​such as 1 / 3, 1 / 2, 1, m = 0, ..., M (L) -1, where for L = (1, 2, 4, 8), M (L) =(6, 6, 2, 2), and i=0, ..., L-1, where i spans each consecutive CCE of the PDCCH hypothesis or low-latency data.

[0058] Equation (1) can randomize the candidate hypothesis CCE positions for each aggregation level search space to minimize blocking. The UE can perform convolutional coded blind detection (CCBD) on the DCI format type for PDCCH and low-latency data at the corresponding aggregation level of the candidate hypothesis. Blind decoding can allow the base station to dynamically select the aggregation size, for example, based on channel conditions, so that a large number of CCEs do not need to be used all the time.

[0059] Figure 2 2 is an example illustration 200 of subframes n to n+4 according to possible embodiments. Subframe n can include a first region 210 such as a control region and a second region 220 such as a data region. The first region 210 can include resource elements 230. In some embodiments, a resource element (RE) can represent a single subcarrier of a single OFDM symbol period in a subframe. More generally, a resource element can be the smallest identifiable time / frequency / code / space domain resource unit within a subframe. A data packet such as a low-latency data packet or other data packet can be mapped to at least one resource element of the resource element 230. If a data packet is received in the first region 210, an acknowledgement such as a HARQ ACK can be sent in a subsequent subframe after the subframe n in which the data packet is received, such as a subframe earlier than subframe n+4.

[0060] According to this possible embodiment, the device can receive a higher layer configuration message, wherein the higher layer can be higher than the physical layer. The higher layer message can be a dedicated mode RRC (radio resource control) message sent to the device. In some embodiments, it can be sent to all devices in the cell by broadcasting a system information message. The device can determine the first area of ​​the subframe for receiving the data packet based on the higher layer configuration message. In one embodiment, the first area in the subframe can correspond to a set of time domain resources in the subframe, such as an OFDM symbol duration. In another embodiment, the first area of ​​the subframe can correspond to a set of frequency domain resources in the subframe, such as a resource block (RB), wherein each resource block can include an OFDM subcarrier set. In another embodiment, the first area of ​​the subframe can correspond to a set of resource elements (REs). In yet another embodiment, the first area of ​​the subframe can correspond to a set of control channel elements (CCEs), wherein each control channel element can correspond to a set of resource elements or a set of resource element groups (REGs) within the subframe. The first area can include a first set of REs, wherein the first set of REs can be a subset of a second set of REs in the first area. In some embodiments, the second set of resource elements can correspond to all resource elements in the first area of ​​the subframe where the device can expect to receive a control channel. The control channel can be a channel such as a physical downlink control channel (PDCCH) or an enhanced physical downlink control channel (EPDCCH). In some other embodiments, the second set of resource elements can correspond to all resource elements in the first region of the subframe where the device can expect to receive the control channel and confirmation signaling. The control channel can be a channel such as a PDCCH and an EPDCCH. Confirmation signaling can be a channel such as a physical hybrid ARQ indicator channel (PHICH). In some other embodiments, the second set of resource elements can correspond to all resource elements in the first region of the subframe. The first region can be used for control channel monitoring. The data packet can be mapped to (or transmitted on) at least one RE in the first set of REs. The device can monitor the first region, wherein the monitoring can include attempting to decode the data packet in the first region. Attempting to decode can include blind decoding by the device. The device can decode data in the data packet in the first region. In one embodiment, the device can monitor the first set of REs in the first region, wherein the monitoring can include attempting to decode the data packet in the first set of REs in the first region. Attempting to decode can include blind decoding by the device. The device can decode at least one data packet in at least some REs in the first set of REs in the first region.

[0061] In some embodiments, the higher layer message can include a list of possible candidate resource elements or REGs that are also used as control channel elements, on which the device can attempt to receive low latency data. The base station can reserve a set of REGs for low latency transmission, but these REGs may be reused for PDCCH transmission in the event that there is no low latency data to be transmitted or if other scheduling priorities do not permit the transmission of low latency data in this subframe.

[0062] In some embodiments, the device can monitor the second RE set in the first area of ​​the subframe for control channel signaling, and also monitor the first RE set for low-latency data packet transmission, which can be a subset of the second RE set. Both the first RE set and the second RE set can belong to the first area of ​​the subframe. The first area can be the control area of ​​the subframe. As a result of monitoring, if the device decodes the control signaling in the first area of ​​the subframe, the device can use downlink control information (DCI) to determine the PDSCH resource assignment. The device can use the PDSCH resource assignment to receive the payload of the data packet (e.g., a conventional delay data packet), and then can pass it to a higher layer such as an application layer. As a result of monitoring, if the device decodes the payload of the low-latency data packet in the first area of ​​the subframe, the device can pass the low-latency data packet to a higher layer such as an application layer. The low-latency data packet can have a more stringent packet delivery delay requirement than the conventional delay data packet.

[0063] According to a related embodiment, it is possible to configure the device via higher layer signaling to monitor low latency (LL) data packets with a low latency downlink control information (DCI) format (e.g., DCI format LL1). The low latency DCI format can also be referred to as a low latency data information format (LDI format). The device can also be configured with a higher layer with a transmission mode, and based on the transmission mode, the device can monitor the control signaling assigned to PDSCH data using the transmission of one or more DCI formats (e.g., DCI formats 1A, 1, 2, 2A, 2B, 2C). The device can monitor low latency data packets with a low latency DCI format in the control region of a subframe. For the control region, up to 3 or more OFDM symbols can be used. Alternatively, up to 8 or more RBs in a subframe can be used for the control region.

[0064] Fig.191 is an example illustration of a subframe 1900 according to a possible implementation of the embodiment. The subframe 1900 can include a first region 1910 such as a control region and a second region 1920 such as a data region. The first set of REs for LL data monitoring can be further organized into a plurality of control channel elements (CCEs) 1930 and 1940, wherein each CCE 1930 and 1940 can include a plurality of resource elements. For low-latency data and control signaling for assigning PDSCH data assignments, the device can monitor the same control channel element (CCE) in the control region. More generally, assuming a first DCI format (e.g., DCI format LL1) and a first CCE aggregation level set, the device can monitor a first CCE set created by organizing a first set of REs for low-latency data, and assuming a second DCI format (e.g., DCI format 1A, 1, 2, 2A, 2B, 2C) and a second set of CCE aggregation levels, the device can monitor a second set of CCEs created by organizing a second set of REs for assigning PDCCH data assignments. Depending on the assumed DCI format and aggregation level, monitoring can attempt to decode low-latency data or control channels. "Monitoring" or "attempting to decode" can also be blind decoding. The first CCE set can be a subset of the second CCE set. Alternatively, the first CCE set can be the same as the second CCE set. Using the first set as a subset of the second set can reduce the blind decoding complexity of the device. Similarly, the first CCE aggregation level set can be the same as the second CCE aggregation level set, or the first CCE aggregation level set can be a subset of the second CCE aggregation level set, such as aggregation levels L = 2, 4, 8 for monitoring LL data transmission, and L = 1, 2, 4, 8 for monitoring control channels. Reducing the aggregation level used to monitor LL data packets can also reduce the UE blind decoding complexity. The CCE size used to monitor LL data packets can be different from the CCE size used to monitor control channels. For example, for monitoring LL data, a CCE size of 72 REs (or 18 REGs, each REG having 4 data REs) can be used, while for monitoring control channels, a CCE size of 36 REs (or 9 REGs, each REG having 4 data REs) can be used. The DCI format size of the low-latency DCI format can be the same as one of the DCI format sizes used for control channel monitoring. For example, DCI format LL1 can have the same size as DCI format 1A, and DCI format LL2 can have the same size as one of the transmission mode specific DCI formats. For example, if the device is configured with transmission mode 2, DCI format LL2 will have the same size as DCI format 1, and if the device is configured with transmission mode 10, DCI format LL2 will have the same size as DCI format 2D. Data transmission in the control region is particularly suitable for small data packet sizes, such as 8 to 500 bits.

[0065] In some embodiments, based on a cyclic redundancy check (CRC) mask with different CRC masks, the LL data information (LDI or LL DCI) monitored in the first region can be distinguished from the DCI of the control channel monitored in the same region. This is particularly applicable when the DCI format size of the low-latency DCI format is the same as one of the DCI format sizes used for control channel monitoring. During blind decoding (or monitoring) of a control channel containing a DCI assigned by PDSCH data, the device may assume that the CRC of the DCI is encoded or scrambled with a device-specific identifier such as a cell radio network temporary identifier (C-RNTI) or a public identifier such as a paging radio network temporary identifier (P-RNTI). During blind decoding (or monitoring) of a LL data packet, the device may assume that the CRC of the payload of the LL data packet is encoded with a specific identifier associated with LL data monitoring, such as a low-latency radio network temporary identifier (LL-RNTI). The specific identifier can be indicated to the device via a higher layer (e.g., RRC) message. More generally, the device is capable of performing control channel monitoring in a first region of a subframe, the device is capable of determining successful decoding of a control channel (e.g., a PDCCH) or a DCI associated with the control channel using a first identifier (e.g., assuming that the CRC of the DCI is encoded using a C-RNTI, using a cyclic redundancy check (CRC)), and the device is capable of determining successful decoding of a data payload of a data packet (e.g., an LL data packet) in the first region using a second identifier (e.g., assuming that the CRC of the data payload is encoded using a LL-RNTI, using a cyclic redundancy check (CRC)).

[0066] The CCE or RE group in the second set of REs monitored by the device for control signaling can be associated with a control channel such as a PDCCH or EPDCCH. In some embodiments, the CCE or RE group in the first set monitored by the device for LL data can be associated with a separate physical channel (e.g., LL-PDSCH) for receiving low-latency data. In some cases, the RE group in the first set monitored by the device for LL data can be referred to by a name other than "CCE", such as a low-latency channel element (LCE). In some embodiments, the CCE monitored by the device for LL data can still be associated with a control channel such as a PDCCH or EPDCCH, but the information decoded on the CCE (i.e., DCI or LDI) is associated with a data channel such as a PDSCH.

[0067] In some embodiments, in response to a LL data packet decoded in the first region of subframe n, feedback (e.g., ACK or NACK) in response to the decoded LL data can be sent in a subframe earlier than subframe n+4, such as subframe n+2. In this embodiment, the device can be configured with a low-latency transmission mode or low-latency feature via a higher layer. The first region can be a control region corresponding to the first 1 to 3 OFDM symbols of a 1ms TTI. Since this region is located at the beginning of the subframe, the LL data sent therein can be decoded earlier. For example, when the device receives 3 OFDM symbols of a 1ms TTI (if LL data is sent in the control region), decoding can begin, rather than after the device receives all 14 OFDM symbols thereof (if LL data is to be sent in a conventional manner, such as using a PDSCHRB spanning to the end of the subframe assigned by DCI in the PDCCH / EPDCCH). Due to the benefits of this early decoding, the device can transmit feedback early, such as in the second half of subframe n+2 or subframe n+1. If the payload of the LL data is small, such as about 100 bits or so, the control channel decoder implemented in the device can also complete decoding as early as possible with the smaller payload.

[0068] According to a possible implementation, a new resource allocation design supporting low-latency packet transmission can be defined using a first region such as a control channel region of an LTE subframe, and can be used for normal or conventional control channel delayed packet transmission. The device can be configured with a first set of REs in the control channel region, and then the device can use the first set of REs to blindly decode data packets. In combination with a legacy frame structure, such as a frame structure of LTE version 8, downlink latency can be reduced in a variety of ways, wherein a legacy transmission time interval (TTI) can have a duration of 1ms, a legacy subframe can be 1ms, and a legacy time slot can be 0.5ms. The system 100 can run at least two different TTI durations simultaneously, a legacy TTI duration of 1ms and at least one new TTI duration, such as 0.5ms. These embodiments can provide faster processing times and faster hybrid automatic repeat request (HARQ) feedback transmissions, such as where a HARQ confirmation (HARQ-ACK) can be sent faster than 4 TTIs later, such as earlier than subframe n+4 after subframe n. For example, ACK / NACK can be sent in subframe n+2 instead of n+4. These embodiments can also provide faster channel quality indicator (CQI) transmission, reduce TTI duration for packet transmission, such as using a TTI of 0.5 ms, and reduce TTI duration for feedback transmission, such as using a TTI of 0.5 ms. For time division duplex (TDD), uplink ACK / NACK resources can be assigned on a timing basis every n+2 or n+4 for the physical downlink shared channel (PDSCH) in subframe n.

[0069] In LTE, in the downlink, the UE may be configured with a transmission mode in a plurality of transmission modes for PDSCH reception, such as transmission modes 1 to 10 in Release 12 LTE. The transmission mode can be associated with one or more PDSCH transmission schemes. The PDSCH transmission scheme may be, for example, a single antenna port transmission, transmit diversity, closed-loop spatial multiplexing, open-loop spatial multiplexing, large delay cyclic delay diversity, dual antenna port or multi-antenna port transmission scheme. Some transmission schemes support the transmission of only a single transport block in a TTI (such as a subframe), while other transmission schemes support the transmission of up to two transport blocks in a TTI. The reference signal or pilot signal associated with the transmission scheme for PDSCH demodulation may be a common reference signal (CRS) or a UE-specific or dedicated demodulation reference signal (DM-RS). The transmission scheme may be associated with a downlink control information (DCI) format of a given payload size including resource assignments and other control information for decoding the PDSCH. The DCI format may be transmitted on a PDCCH (Physical Downlink Control Channel) or EPDCCH (Enhanced PDCCH) including CRC (Cyclic Redundancy Check) bits that may be scrambled by a specific C-RNTI configured for the device. Similarly, on the uplink, the UE may be configured with a transmission mode in a plurality of transmission modes for PUSCH (Physical Uplink Shared Channel) transmission, such as transmission modes 1 to 2 in Release 12 of LTE. PUSCH transmission schemes may include single antenna port and closed-loop spatial multiplexing transmission schemes.

[0070] In one embodiment, the device can be configured with a low-latency transmission mode, such as a low-latency downlink control information format, where a transmit (Tx) HARQ ACK can be sent in subframe n+2 instead of n+4, there may be a transport block (TB) size limit, there may be a timing advance (TA) limit that can limit the configuration of smaller latency to small (smaller) cells, there may be dedicated PDSCH resources, such as in semi-pending scheduling (SPS), where ACK / NACK feedback can be similar to Release 8, such as dynamic ACK / NACK based on control channel element (CCE) index, and there may be a small maximum code block (CB) size, such as 1500 bits instead of 6144 bits, which can improve pipelining and / or reduce complexity. The maximum code block (CB) size can correspond to a channel payload size that can be channel coded for transmission on a specific physical channel such as PDSCH before the information payload is split into multiple code blocks. A transport block can include one or more code blocks.

[0071] For example, the device may be configured with a low-latency transmission mode or low-latency feature via a higher layer. In such a case, the device may be required to transmit HARQ feedback faster than a Release 8 device, such as a downlink (DL) grant for a PDSCH received in subframe n, which may require the device to transmit the corresponding HARQ-ACK feedback in subframe n+2 instead of subframe n+4. This may mean that the device's processing time for PDSCH can be reduced from 3-TA to 1-TA. To ensure that the complexity of the device is not adversely affected by this shortened processing time, restrictions may be imposed on the TB size and / or the TA value supported by the device for low-latency operation. For extremely short transport blocks, dedicated PDCCH resource functions such as in semi-persistent scheduling (SPS) are assigned directly to the PDSCH. This allows the device to start detecting and decoding the PDSCH earlier and send uplink feedback faster.

[0072] According to the relevant embodiment, the device can be configured with a low-latency DCI format that can cooperate with any transmission mode. Up to 3 or more orthogonal frequency multiplexing (OFDM) symbols can be used for the control region. Data can be sent on the control channel element (CCE) for small data packets. In response to the data on the physical downlink control channel (PDCCH), ACK can be sent in subframe n+2. In this embodiment, the device can be configured with a low-latency transmission mode or a low-latency feature via a higher layer. For small packets, the PDSCH that usually occupies the entire 1ms TTI can be sent on the CCE including the PDCCH or the control region instead. Since the control region can occur in the first 1 to 3 OFDM symbols of the 1ms TTI, the data sent on the CCE can be decoded earlier, such as after the device receives 3 OFDM symbols of the 1ms TTI, rather than after the device receives all 14 OFDM symbols. Due to the benefits of this early decoding, the device can transmit uplink feedback early in time slot 2 such as subframe n+2 or subframe n+1. Typical payloads that can be sent may be around 100 bits or so, and they can take advantage of the control channel decoder implemented in the device. PDSCH data can be distinguished from DCI based on a cyclic redundancy check (CRC) mask with a different CRC. This allows for reduced complexity, no changes to the existing PDSCH structure such as TTI duration, RS, mapping, etc., only the HARQ timing can be modified, and low-latency small packets can be transmitted over the PDCCH structure.

[0073] Figure 33 is an example illustration of a subframe 300 according to a possible embodiment of the present invention. The subframe 300 can include an OFDM symbol 310 configured for low-latency transmission, a resource block 320 configured for low-latency transmission, a first resource element set 330 such as a first low-latency channel element (LCE0) which can also be referred to as a data channel element (DCE), and a second resource element set 340 such as a second LCE1. The resource blocks configured for low-latency transmission can be centralized physical resource blocks, centralized virtual resource blocks, or distributed virtual resource blocks. Centralized virtual resource blocks (VRBs) can be directly mapped to physical resource blocks, while distributed virtual resource blocks can be mapped to physical resource blocks in a predetermined manner, so that continuous distributed resource blocks are mapped to non-continuous physical resource blocks, and the positions of non-continuous physical resource blocks in each time slot are different. The resource blocks configured for low-latency transmission can be defined according to resource block groups (RBGs), centralized VRBs in one or more RBG subsets, or distributed VRBs. RBGs can be a set of continuous centralized virtual resource blocks (VRBs). The resource block group size (P) can be a function of the system bandwidth. RBG subset p, where 0≤p<P, can include every Pth RBG starting from RBG p. LCE can generally include multiple REs, and the REs corresponding to the LCE do not have to be continuous in the time domain or frequency domain. LCEs can also be dispersed among multiple RBs, or even dispersed among multiple resource block groups (RBGs) including multiple RBs. In one embodiment, the LCE may include REs in RBGs in one or more OFDM symbols configured for low-latency data packet transmission. In another embodiment, the LCE may include REs in one or more centralized VRB subsets of P RBG subsets in one or more OFDM symbols. The centralized VRB subsets may correspond to VRBs in different RBGs. In another embodiment, the LCE may include REs in distributed VRB subsets in one or more OFDM symbols. Distributed VRB subsets may be continuous VRBs, so they are mapped to distributed physical RBs. A single symbol configured for low-latency packet transmission can include multiple LCEs in different RBs configured for low-latency packet transmission in the symbol. The low-latency data packet can be on any one of the symbols configured for low-latency packet transmission, such as a subset of symbols, and can also be on a subset of RBs configured for low-latency packet transmission. In some cases, all OFDM symbols and RBs in a subframe may potentially be used for low-latency transmission, and separate configuration signaling may not be necessary. In such a case, OFDM symbol 310 can be all OFDM symbols in a subframe. Similarly, RB 320 can be all RBs in a subframe. Some of OFDM symbol 350 can include a common reference signal on some of the REs in symbol 350, such as a pilot RE.

[0074] In one embodiment, similar to the control channel structure described above with respect to search space and aggregation level, a UE such as a device can be configured via higher layer signaling to monitor low latency (LL) data packets having one or more low latency data information (LDI) formats in an LCE subset of a specific LCE aggregation level L (e.g., L=1, 2, 4, or 8 LCEs). The aggregated LCE set in the LCE subset of the specific LCE aggregation level L can correspond to a low latency data candidate set of aggregation level L monitored by a specific device in a search space corresponding to the LCE subset of the specific LCE aggregation level. The device can monitor a low latency data candidate set of a given aggregation level for low latency data packets, where monitoring means attempting to decode each of the low latency data candidates in the set according to all monitored LDI formats. The device can determine the successful decoding of the data payload of the low latency data packet corresponding to the low latency data candidate by using an identifier associated with the UE, such as a C-RNTI or LL-RNTI of a cyclic redundancy check (CRC) of a masked or scrambled data payload. In some embodiments, a hash function can be used to find a low latency data candidate position in each search space. The hash function can be based on the UERNTI (an identifier associated with the UE, such as C-RNTI or LL-RNTI), the aggregation level (L), the total number of available LCEs (Nlce), the number or index of OFDM symbols, and the maximum number of low-latency data candidates in the search space. In determining the LCE position corresponding to each aggregation level L (e.g., L = (1, 2, 4, or 8)) low-latency data candidate m In the method, the LCE position of the search space for OFDM symbol 'k' of a subframe is given by the following equation:

[0075]

[0076] in,

[0077] - For UE-specific search space, Y k =39827·Y k-1 mod65537w, where Y -1 =n_RNTI;

[0078] - For example, n_RNTI≠0 is C-RNTI or temporary C-RNTI or LL-RNTI; N LCE，k is the total number of LCEs available for OFDM symbol k;

[0079] -m=0,…,M (L) -1, where M (L) is the number of low-latency data candidates monitored in the search space at aggregation level L; and

[0080] - i = 0, ..., L-1, where i spans each consecutive LCE of the low-latency data hypothesis.

[0081] Figure 4 4 is an example diagram of an OFDM symbol 400 according to a possible embodiment of the present invention. The OFDM symbol can be one of the OFDM symbols configured for low-latency transmission in a subframe. The OFDM symbol 400 can include LCE0, LCE1 and LCE2 of LCE and other elements. Moreover, the OFDM symbol 400 can have a bandwidth of RBs configured for low-latency transmission, such as 12 RBs, 100 RBs and other numbers of RBs. LCE resources can optionally be used for tag transmission, which can serve as the type of control signal. For example, the tag transmission can be an indication channel indicating whether the OFDM symbol is used for low-latency service. The tag can also provide information indicating RE or RE set (e.g., RBG, RB or LCE). The tag transmission can be sent as a broadcast transmission common to multiple devices. For devices that do not receive low-latency transmission in the subframe but have allocations for other data transmissions, the tag transmission can indicate which REs in its allocation are used for low-latency transmission, so that the device can ignore these REs, make them invalid (null), or otherwise not use them.

[0082] Figure 5 5 is an example illustration of a transmission time interval (TTI) 500 according to a related possible embodiment. TTI 500 shows a mixture of legacy and low-latency allocations in a legacy TTI. For example, the new TTI can be 2 symbols longer in duration. The legacy TTI 500 can include low-latency control information C and low-latency data D. For example, C1 can be control information for a first device, and D1 can be data for a first device, etc. The areas shown, such as C1, D1, can also have only data without control information. Low-latency data and control information can coexist with legacy allocations, such as in a 1ms legacy TTI. The legacy allocation can be truncated 510 to accommodate a short TTI.

[0083] According to one of these possible embodiments, a device such as device 110 can receive a higher layer configuration message indicating a set of resource blocks (RBs) for receiving a data packet in at least one symbol of a subframe. The higher layer can be higher than the physical layer. The device can attempt to decode the data packet in a first set of REs within the set of RBs, such as those corresponding to a first low latency channel element (LCE0). The first set of REs can be in at least one symbol of the subframe. The device can attempt to decode the data packet in at least a second set of REs within the set of RBs, such as those corresponding to a second LCE1. The second set of REs can be in at least one symbol of the subframe, wherein the second set of REs can include at least one RE that is not in the first set of REs. The device can successfully decode a data packet in one of the first set of REs and the second set of REs. The device can pass a data payload of the decoded data packet to an application layer.

[0084] For example, according to a possible implementation, in PDSCH, such as the data area of ​​a conventional LTE subframe, the device can be configured with a low-latency transmission mode. The device can search for small packets in subframe n in the search space in the PDSCH area, and can provide ACK in subsequent subframes n+m. As another example, the device can be configured with a low-latency transmission mode or a low-latency feature via a higher layer. For small packets, PDSCH can be sent on a data channel element (DCE) such as LCE in the PDSCH area. For small packet transmission, it may not be necessary to send an additional control channel associated with it. For example, in order to send a packet of 100 bits, a DCI format with a length of 40 to 50 bits will mean 50% overhead. The decoder can decode small packets faster because the payload may be smaller. Due to the benefits of this early decoding, the device can transmit uplink feedback earlier, such as in subframe n+2. The typical payload that can be sent can be about 100 bits or so, and can utilize the control channel decoder implemented in the device, such as utilizing a CRC mask with a different CRC and using a search space similar to the search space defined for the control channel and described above. This can provide reduced complexity while minimally changing or not changing the existing PDSCH structure, such as TTI duration, reference signal (RS), mapping, etc., can only modify the HARQ timing, can transmit low-latency small packets through PDSCH small RB assignments, and the device can blindly decode multiple PDSCH candidates to detect PDSCH.

[0085] According to one embodiment, a device such as base station device 120 can transmit a resource assignment, which can assign a first set of time-frequency resources in a subframe for conventional delayed data transmission. For example, the first set of time-frequency resources can be a set of RBs in a subframe. The DCI of a control channel such as a PDCCH or EPDCCH can be used to transmit the resource assignment. The device can transmit low-latency data within a second set of time-frequency resources in a subframe. For example, the second set of time-frequency resources can be a set of REs mapped to one or more OFDM symbols and one or more RBs in a subframe. Low-latency data can have a lower latency than conventional delayed data. The second set can overlap at least partially with the first set. The device can transmit a marker signal, wherein the marker signal can indicate the presence of low-latency data transmission in the subframe.

[0086] According to another related embodiment, a device such as device 110 (such as a user equipment) can receive a resource assignment. The device can determine a first set of time-frequency resources in a subframe from the resource assignment; for example, the first set of time-frequency resources can be a set of RBs in a subframe. The resource assignment can be transmitted using a DCI of a control channel such as a PDCCH or an EPDCCH. The device can determine a second set of time-frequency resources in a subframe. For example, the second set of time-frequency resources can be a set of REs mapped to one or more OFDM symbols and one or more RBs in a subframe. The second set of time-frequency resources can be used for low-latency data transmission and can overlap with at least a portion of the first set of time-frequency resources. The device can receive a regular delay data transmission in a subframe. The device can decode a regular delay data transmission in a subframe based on the determined first set of time-frequency resources and the second set of time-frequency resources, wherein the regular delay transmission can have a longer delay than the low-latency transmission. The device can determine the second set of time-frequency resources by receiving a marker signal. Alternatively, the device can determine the second set of time-frequency resources by decoding the low-latency transmission.

[0087] According to a possible implementation, in order to support conventional delayed transmission in the same subframe as low-delay transmission, a tag can be emitted, wherein the tag can indicate which RE is used for low-delay transmission in the subframe. This information can be used to determine which log likelihood ratios (LLRs) should be set to zero when decoding conventional delayed transmission. Different users such as devices and / or UEs can receive conventional delayed transmission and low-delay transmission in the same subframe. Alternatively, if the user is configured to receive these two types of transmissions, the same user can receive conventional delayed transmission and low-delay transmission in the same subframe. Alternatively, some users can be configured to receive conventional delayed transmission in a first subframe set and be configured to receive low-delay transmission in a second subframe set. The first subframe set can be a subset of the second subframe set. Conventional delayed transmission can be transmitted in one or more RBs in a subframe. RBs for conventional delayed transmission can be assigned via resource assignment and indicated using a control channel. Since the same subframe can be used for both normal delay transmission and low latency (LL) transmission, the REs used for LL transmission and any tag transmission may not be used for normal delay transmission. The REs used for LL transmission and any tag transmission can belong to the RBs allocated for normal delay transmission.

[0088] A tag can be sent at a predefined or preconfigured position in a subframe. A possible position of a tag transmission can be indicated to a user equipment via a higher layer (e.g., RRC) signaling. If some OFDM symbols in a subframe are configured for low-latency transmission, in some embodiments, a tag signal can be sent only on those OFDM symbols. For example, a tag signal can be sent in OFDM symbol 310. A user equipment that attempts to receive other transmissions except low-latency transmission in the same subframe can decode the tag to determine the RE for low-latency transmission. For example, the user equipment can determine the OFDM symbol 310 configured for low-latency transmission. In each such OFDM symbol, such as OFDM symbol 400, low-latency transmission can be performed in some REs. RE can be further organized as LCE or DCE or CCE. For example, as shown in OFDM symbol 400, low-latency transmission can be performed on resources or REs corresponding to LCE0, LCE1, and LCE2. Although OFDM symbol 400 shows that LCE is created from RE in one symbol, it is also possible to create LCE by using RE in multiple adjacent OFDM symbols or multiple non-adjacent OFDM symbols. In some embodiments, a subset of LCE in each OFDM symbol configured for LL transmission (e.g., LCE0 in OFDM symbol 400) can be used for tag transmission. In general, a base station can use only a portion of RE in OFDM symbols and RBs configured for low-latency transmission in a subframe. The base station can use tag transmission to signal information indicating RE for LL transmission in each specific subframe. For example, tag transmission can indicate which LCE in an OFDM symbol is used for LL transmission. Alternatively, tag transmission can indicate which RB or RBG of an OFDM symbol is used for LL transmission. Tag transmission in one OFDM symbol can indicate RE / LCE / DCE / CCE / RB / RBG for low-latency transmission in other OFDM symbols of the subframe.

[0089] Fig.212 is an example illustration 2100 of a first subframe 2110 and a second subframe 2112 according to a possible embodiment. The first subframe can include a control region 2121, low-latency data 2240, and a normal-latency data region 2250. The second subframe 2112 can include a control region 2122, including a tag 2130. A tag transmission 2130 in one subframe 2112 (e.g., subframe n+1) can indicate the RE / LCE / DCE / CCE / RB / RBG used for low-latency transmission in an OFDM symbol of another subframe 2121 (e.g., subframe n). In such a case, the tag transmission 2130 in subframe n+1 2112 can be sent in the first few OFDM symbols (e.g., symbols in the control region 2122) to reduce decoding latency for a device receiving the tag 2130. When the tag 2130 is transmitted using a symbol in the control region 2122, the information transmitted using the tag 2130 can be transmitted using a control channel such as PDCCH or PHICH commonly used in the control region. If the PDCCH is used for tag transmission, the tag transmission can be distinguished from other control channel transmissions by using a CRC mask (e.g., tag-RNTI) specific to the tag transmission. If the PHICH is used for tag transmission, one or more of the PHICH groups can be preconfigured or predefined for tag transmission.

[0090] Considering the implementation complexity and decoding delay of the device (e.g., user equipment) receiving the marked transmission, it may be useful to transmit the mark in each OFDM symbol configured for LL transmission in the subframe. However, since the device (e.g., base station or eNB) transmitting the mark may not actually transmit LL transmission in all configured OFDM symbols configured for LL transmission, it may be useful (from the perspective of reducing overhead alone) to transmit the mark only in the OFDM symbols actually used for LL transmission in the subframe. In such a case, transmitting the mark signal may implicitly indicate the presence of LL transmission, while not transmitting the mark signal may implicitly indicate the absence of LL transmission. In other cases, where the mark is transmitted in each OFDM symbol configured for LL transmission, the presence or absence of LL transmission can be explicitly indicated by the mark transmission (e.g., by using one bit or one code point).

[0091] Fig. 202000 is an example diagram of a subframe according to another possible embodiment. The subframe 2000 can include a control region 2010, a data region 2020, a tag 2030, a low-latency data resource element 2040, and a conventional delayed data region 2050. According to this embodiment, the tag transmission 2030 can be sent by puncturing the RB assigned to the conventional delayed transmission 2050. For example, a PDSCH RB set in a subframe can be assigned to a user. Some REs within the OFDM symbol (e.g., the last OFDM symbol) of one or more of these RBs can be used for tag transmission. If multiple users are assigned PDSCH RBs in the same subframe, a separate tag transmission for each user can be sent within the RB assigned to each user. The tag transmission can be sent by puncturing the PDSCH assignment of the user. The puncturing can be similar to the LTE mechanism of transmitting ACK / NACK and rank indicator (RI) bits by puncturing the PUSCH assignment. The signature may be transmitted using a predefined mapping within the user assigned RBs, such as on the last symbol and high end of the user assigned RB index.

[0092] The information payload transmitted can be identified using a marker such as 13 bits or 6 bits, and the other bits can be used to identify the resource block groups (RBGs) that are punctured within a user's allocation such as a device. This can be optimized by grouping the allocated RBGs and identifying only the top, middle, or other groups within the user allocation as punctured.

[0093] The information payload of the marker transmission can indicate which OFDM symbols within the RB assigned to the user are used for LL transmission. For example, this can be done using 13 bits or 6 bits, each bit corresponding to one or more OFDM symbols. The payload bits of the marker transmission can be used to identify the resource block group (RBG) containing the LL transmission within the RB assigned to the user for receiving conventional delayed transmissions. The payload can be further optimized by grouping the assigned RBs into RBGs and identifying only the top, middle, or other groupings containing LL transmissions.

[0094] A marker transmission may be sent only if the LL transmission overlaps with a resource assignment for a user scheduled with a particular modulation set of modulation and coding scheme (MCS) levels. For example, if the LL transmission overlaps only with those resource assignments with low MCS levels (e.g., those corresponding to QPSK modulation and low coding rates such as <0.8), then no marker signal may be transmitted. If the LL transmission overlaps with resource assignments with high MCS levels (e.g., those corresponding to 64QAM or higher modulation), then a marker signal can be transmitted. In another example, no marker may be used for low MCS, such as MCS<10.

[0095] According to a possible implementation, a device (e.g., user equipment 110) can receive a subframe with both conventional delay transmission and low delay transmission. The device can be configured to receive both conventional delay transmission and low delay (LL) transmission in the same subframe. Alternatively, although the subframe can contain both conventional delay transmission and low delay transmission, the device can be configured to decode only conventional delay transmission. However, even if the device only decodes conventional delay transmission, it may be useful for the device to consider the presence of LL data transmission in the subframe to more accurately decode conventional delay data transmission. Therefore, the device can receive resource assignment. The device can determine a first time-frequency resource set from the resource assignment. For example, the first time-frequency resource set can be an RE corresponding to a PDSCH RB assigned to the device for receiving data transmission. The data transmission can be a conventional delay data transmission. The device can receive resource assignment on a control channel such as PDCCH / EPDCCH. The device can determine a second time-frequency resource set in a subframe. The second time-frequency resource set can overlap at least a portion of the first time-frequency resource set, and the second time-frequency resource set can be used for low delay (LL) data transmission. For example, the device may be assigned RB1, RB2, RB3, RB4, RB5 in both 0.5 ms slots of a 1 ms subframe for receiving conventional delayed transmissions. Each RB may span all OFDM symbols in a slot. The LL transmission may span RB3, RB4, RB5, RB6, RB7, and RB8 in the frequency domain and OFDM symbols 4 and 5 of the first slot of the subframe in the time domain. The device may then determine RB3, RB4, and RB5 and the REs within OFDM symbols 4 and 5 of the first slot of the subframe as a second set of time-frequency resources.

[0096] Then, the device can decode the conventional delayed data transmission in the subframe based on the first time-frequency resource set and the second time-frequency resource set. For the example given above, when decoding data for conventional delayed data transmission, the device can adjust the log-likelihood ratio (LLR) value of the bit corresponding to the conventional delayed data transmission of the RE in OFDM symbols 4 and 5 mapped to RB3, RB4 and RB5 and the first time slot of the subframe to a low value. For example, the device can set the LLR value of these bits to zero. This can increase the probability that the device correctly decodes the data transmission assigned on PDSCH RB1, RB2, RB3, RB4 and RB5. If the MCS level used for data transmission corresponds to a level with a higher order modulation and a higher coding rate (for example, modulation is 64QAM or higher and the code rate is 0.7 or higher), such an operation may be useful. If the MCS level used for data transmission corresponds to a level with a lower order modulation and a lower coding rate (e.g., modulation is 16QAM or lower and the coding rate is less than 0.7), the device can skip the steps of determining a second set of resources and adjusting the LLR value, and instead directly attempt to decode regular data transmission based on the resource assignment.

[0097] In some embodiments, the device may receive a marker signal. The device may use the marker signal to determine the second set of time-frequency resources. The device may determine the position of the marker signal based on the predetermined position of the marker signal. For example, the device may determine from RRC signaling that LL transmission is expected in RB3 to RB8 and RB91 to RB96 in the frequency domain of each subframe and OFDM symbols 4 and 5 of the first time slot and OFDM symbols 0, 1, 4 and 5 of the second time slot in the time domain.

[0098] Fig. 22 2 is an example illustration of a subframe 2200 according to a possible embodiment. The subframe 2200 can include a control region 2210, a data region 2220, a tag 2230, a low-latency data 2240, and a normal-latency data region 2250. For a subframe in which a device receives a resource assignment, the device can then determine that a tag signal can be present in RB0 to RB2 in OFDM symbols 4 and 5 of the first time slot and OFDM symbols 0, 1, 4, and 5 of the first time slot of the second time slot in the time domain of the subframe. In this example, a possible location of the tag signal can be a predefined set of RBs (e.g., RB0 to RB2) in each OFDM symbol configured for LL transmission. In another example, where LCEs are used for LL transmission, the device can look for a tag signal in REs corresponding to one or more predefined LCEs (e.g., transmitting a tag in LCE0 in an OFDM symbol where there may be LCEs for LL transmission).

[0099] After receiving the marker signal, by decoding the information payload in the marker signal, the device can determine that there are REs for LL transmission, and the device can further determine which of those REs overlap with REs assigned to the device for receiving conventional delay data transmission. Thus, the device can determine a second set of time-frequency resources in the subframe, the second set of time-frequency resources is used for low-latency data transmission, and based on the marker signal, the second set of time-frequency resources overlaps with at least a portion of the first set of time-frequency resources.

[0100] In some embodiments, the device may be able to receive both conventional transmissions and low-latency (LL) transmissions in the same subframe. For example, RB1, RB2, RB3, RB4, and RB5 may be assigned to the device in both 0.5ms time slots of a 1ms subframe for receiving conventional delayed transmissions. The REs corresponding to these RBs can be considered as a first set of time-frequency resources. The device can successfully decode LL transmissions across RB3, RB4, RB5, RB6, RB7, and RB8 in the frequency domain and OFDM symbols 4 and 5 of the first time slot of the subframe in the time domain. The REs on which the LL transmission is decoded can be considered as a third set of time-frequency resources. The device can then determine the second set of time-frequency resources as time-frequency resources belonging to both the first set of time-frequency resources and the third set of time-frequency resources. For example, RB3, RB4, and RB5 and the REs within OFDM symbols 4 and 5 of the first time slot of the subframe can be considered as a second set of time-frequency resources. The device can then decode conventional delayed data transmissions by setting LLR=0 for bits mapped to the second set of time-frequency resources.

[0101] In such an embodiment, a separate marker signal transmission may not be required. In addition, in such an embodiment, it is also possible to make it possible to decode the LL transmission by a device (i.e., non-low-delay device) configured to decode conventional delayed transmissions. For example, all LL transmissions can use the same CRC mask, and can be blindly decoded by both low-delay devices and non-low-delay devices. However, each data payload of each low-delay transmission can be scrambled, so that even if non-low-delay devices can decode LL transmissions, they will not descramble the data payload bits, thereby ensuring the privacy of the LL data payload. Non-low-delay devices can attempt to decode only those LL allocations that can overlap with their PDSCH resource allocations, so as to perform conventional delayed data transmission. If the LL allocation is successfully decoded, the non-low-delay device can determine the overlapping REs with its conventional delay assignment, and such as by erasing the LLR values ​​corresponding to the overlapping REs in the bit by zeroing those LLR values.

[0102] According to a possible embodiment, a device can receive a higher layer configuration. The higher layer configuration can be higher than the physical layer configuration. In addition to the conventional delay configuration of the conventional delay transmission mode, the higher layer configuration can also indicate the use of the low delay configuration of the low delay transmission mode to configure the device. The low delay transmission mode can have a lower delay than the conventional delay transmission mode. A packet can be received based on the low delay configuration in subframe n and one of the conventional delay transmission modes. The device can transmit a feedback packet in a subsequent subframe n+p, wherein p<4 when the received packet is based on the low delay configuration. The subsequent subframe n+p can be the pth subframe from subframe n. When the received packet is based on the conventional delay configuration, the device can transmit a feedback packet in a subsequent subframe n+4. The subsequent subframe n+4 can be the 4th subframe from subframe n.

[0103] According to a possible implementation, in LTE, code block (CB) segmentation can be used to segment a large transport block into smaller blocks, and these small blocks are CRC encoded, turbo compiled, rate matched, scrambled and mapped to modulation symbols respectively. In order to improve pipeline efficiency, a single modulation symbol or RE may not contain bits from different code blocks. The code blocks of a given transport block (TB) can be mapped according to frequency priority mapping as shown in TB 600. TB 600 can assume that the transport block is segmented into 4 code blocks occupying a subframe. Assuming two common reference signal (CRS) ports (50RB system bandwidth) for OFDM symbols 0 to 13 in 1 millisecond TTI, symbol #{0,5,7,12} can have REs for CRS. Therefore, OFDM symbols other than {0,5,8,12} can have 12*50=600 REs for data, while {0,5,7,12} can have 8*50=400 REs. Typically, based on the signal / channel (CRS, CSI-RS, CSI-IM, DRS, DMRS, PBCH, etc.), the number of REs per any given OFDM symbol or per any given resource block can be variable.

[0104] For channel estimation delay, if the device needs to demodulate PDSCH based on CRS, for 1ms TTI, CRS channel estimation may not start until symbol 5 (~6*71us=420us), resulting in a delay of 0.42ms. This may mean that for code block 0 in TB 600, the log likelihood ratio (LLR) cannot be generated until symbol 5, such as after CB0 is fully received. That is, symbol 3 fully receives the RE corresponding to CB0, and after receiving symbol 5, the I / Q values ​​of symbols 0 to 4 wait for symbol durations 4 and 5, and CRS channel estimation can be performed, and then LLRs for generating CB0 can be generated to start the turbo decoding process. Early decoding can be started with only the CRS in symbol 0. Typically, all CRSREs in a given subframe can be used for PDSCH demodulation. Moreover, it is not assumed here that cross-subframe channel estimation is performed on CRS. For DMRS-based channel estimation, the device may have to wait, at least until symbol 7 for performing DMRS-based channel estimation. Typically, DMRS in both time slots can be used to improve channel estimation. In order to achieve possible improvements, more demodulation pilots can be introduced to help early decoding, and pilots for channel estimation can be received no later than the corresponding data. Moreover, demodulation pilots can be introduced at an early position. For example, DMRS can be transmitted in symbols 0, 1 and symbols 7, 8. This can reduce the DMRS channel estimation delay by nearly 420us. In addition, channel state information reference signals (CSI-RS) and channel state information interference measurements (CSI-IM) may be required mainly for feedback purposes. Thus, these reference signals can be transmitted at flexible locations, where the device complexity can depend on the time between measuring CSI and reporting CSI.

[0105] Figure 7 is an example illustration of a transport block 700 according to a possible embodiment. Figure 8800 is an example diagram of a transport block 800 according to a possible embodiment. Transport blocks 700 and 800 can have 13 code blocks and can occupy a 1ms subframe, where the vertical dimension is frequency and the horizontal dimension is time. Transport block 700 can include code blocks CB0 to CB12 that occupy an integer number of OFDM symbols. Transport block 800 can include code blocks CB0 to CB12, each of which can occupy one or more OFDM symbols. LTE can implement a pipeline decoder using transmitter and receiver operations based on code blocks. If a transport block (TB) of more than 6120 bits (with TB CRC, 6144 bits) is to be transmitted, the transport block can be divided into multiple code blocks, each of which can have an attached CRC, can be turbo coded, can be rate matched, and can be mapped to a modulation symbol. This can allow a pipeline implementation because each code block can be processed independently and sequentially, which reduces complexity. HARQ feedback and retransmission can usually be performed at the transport block level.

[0106] In LTE, a transport block size (TBS) of 75376 bits corresponding to a 5 / 6, 64QAM, 100RB allocation can be partitioned into 13 code blocks, each of size 5824 bits (= (75376+(13+1)*24) / 13, with 14 24-bit CRCs). Transport block 700 shows that the CB is mapped to a 1ms TTI. The mapping can be based on the total number of REs available in the assigned resource blocks, such as in all assigned OFDM symbols. The available number of REs may be affected by the amount of signals / channels such as CRS, CSI-RS, CSI-IM, DRS, PSS / SSS, etc. present in the assigned resource blocks. Thus, a transport block may appear as transport block 800, where each code block may span one or more OFDM symbols.

[0107] A device configured with a low-latency transmission mode such as a low-latency DCI format can transmit HARQ ACK in n+2 instead of n+4, can have a TB size restriction, can have a TA restriction that may limit the configuration of smaller delays for small (smaller) cells, and can have dedicated PDSCH resources, such as in SPS. ACK / NACK feedback can be similar to Release 8, such as dynamic ACK / NACK based on control channel CCE index or SPS. The device can be configured with a low-latency transmission mode or low-latency features via a higher layer. In this case, the device may be required to transmit HARQ feedback faster than a Release 8 device. For example, for a downlink grant for a PDSCH received in subframe n, the device may be required to transmit the corresponding HARQ-ACK feedback in subframe n+2 instead of subframe n+4. This may mean that the device's processing time for PDSCH can be reduced from 3-TA to 1-TA. To ensure that the complexity of the device is not adversely affected by this shortened processing time, restrictions may be imposed on the transport block size and / or the timing advance value supported by the device for low-latency operation. For very short transport blocks, dedicated PDCCH resource functions such as in semi-persistent scheduling (SPS) can be assigned directly to the PDSCH. This allows devices to start detecting and decoding PDSCH earlier and send uplink feedback faster. This reduces complexity while keeping existing PDSCH structures such as TTI duration, RS, mapping unchanged or minimally changed, only HARQ timing can be modified, and the decoder can be relaxed to a certain extent via TA / TB restrictions. To support low-latency operation, devices can be configured with transmission modes that use restricted transport block sizes, restricted timing adjustments, dedicated PDSCH resources such as in SPS, and smaller maximum CB sizes such as 1500 bits instead of 6144 bits used in LTE Release 13. To minimize conflicts in the uplink, devices can be configured with extended UL ACK / NACK areas at the slot level or symbol level based on the length of the TTI being used.

[0108] Fig. 9 9 is an illustration of a legacy or conventional 1 ms uplink subframe 900 according to a possible embodiment. Subframe 900 can include two time slots 910 and 920. Fig.10 is an example illustration of a 1 ms uplink subframe 1000 and at least one 0.2 ms uplink subframe 1010 overlaid on the 1 ms subframe 1000 according to a possible embodiment. Fig.111 is an example illustration of a 1 ms subframe 1100 according to a possible embodiment. Subframe 1100 illustrates another potential frame structure for the uplink, where subframe 1100 can include two symbols 1110 and 1120, assigning resource elements 1130 and 1140 to the device for uplink feedback transmission in a multi-carrier cluster format. One symbol 1130 can be used for pilot, and one symbol 1140 can be used for ACK / NACK.

[0109] Fig.12 is an example flow chart 1200 illustrating the operation of a wireless communication device, such as a first device, according to a possible embodiment. At 1210, the flow chart 1200 can start. At 1220, a higher layer configuration message can be received. The higher layer can be above the physical layer.

[0110] At 1230, based on a higher layer configuration message, a first region of a subframe for receiving a data packet can be determined. The first region can be a first time-frequency region in a series of regions. For example, the first region can be a first time region of a subframe, wherein the first region can include up to 4 multi-carrier symbols. For example, the multi-carrier symbol can be an OFDM symbol, and the subframe can include up to 14 OFDM symbols. Moreover, the subframe can be one of 10 subframes in a frame. The first region can include a first set of resource elements. The resource elements in the first set of resource elements can be used for low-latency data packets, can be used for control signals, and / or can be used for other purposes. The first set of resource elements can be a subset of a second set of resource elements in the first region. The number of resource elements in the first set can be less than the number of resource elements in the second set. The first region can be used for control channel monitoring. For example, the first region can be a control region, including at least one physical downlink control channel including a control channel element. Data packets can be transmitted on one or more of the control channel elements including the resource elements in the first set of resource elements. Moreover, the data packet can be mapped to at least one resource element of the first set of resource elements.

[0111] The data packets in the first region can be low-delay data packets, which have a lower maximum allowed delay than the normal-delay data packets in the second region. The first region can be used to transmit a control signal for decoding the normal-delay data packets in the second region. For example, the normal-delay data packets can be legacy data packets.

[0112] At 1240, the first region can be monitored. For example, control channel monitoring can be performed in the first region. Monitoring can include attempting to decode data packets in the first region. For example, monitoring can imply, such as including, blindly decoding data packets.

[0113] At 1250, data in a data packet in the first region can be decoded. The data packet can be a low latency data packet having a lower latency than a normal data packet. Moreover, a first identifier can be used to determine successful decoding of a control channel in the first region. The first identifier can be a cell radio network temporary identifier (C-RNTI) received in a higher layer configuration message. A second identifier can also be used to determine successful decoding of data in the data packet in the first region. The second identifier can be a low latency radio network temporary identifier (low latency-RNTI) received in a higher layer configuration message.

[0114] At 1260, in response to successful decoding of the low-latency data packet, an acknowledgment can be transmitted in a subframe having a first offset from a subframe in which the low-latency data packet was received. The first offset can be different from a second offset of the normal-latency data packet. For example, the first offset can be 2, and transmitting the acknowledgment can include transmitting a hybrid automatic repeat request acknowledgment in a subframe n+2 having a first offset of two subframes from a subframe n in which the low-latency data packet was received. At 1270, decoded data from the data packets in the first region can be delivered to the application layer. At 1270, flowchart 1200 can end.

[0115] A variation of the above embodiment can include receiving a higher layer configuration message, which is higher than the physical layer. As described below, a higher layer configuration message can be received before a subframe. A first region of a subframe for receiving a low-latency data packet can be determined based on a higher layer configuration message. The first region can be a control region of a certain number of first symbols in a subframe. For example, the first region can be a control region of a physical downlink control channel including a control channel element. Low-latency data packets can be transmitted on one or more control channel elements. Low latency can refer to the rate at which data can be correctly received. For example, low latency can refer to the amount of time from the time when a packet arrives at a base station to the time when the packet is received at a UE. Delay can also refer to a round-trip delay, such as the time from the time when a base station sends a packet to the time when the base station receives confirmation that a user equipment has received the packet.

[0116] The first region can be used to assign a control channel for resource allocation for a normal delay data packet in a second region following the first region in a subframe. A low delay data packet can have a lower maximum allowed delay than a normal delay data packet. The first region can also be used for a low delay data packet.

[0117] In response to receiving a higher layer configuration, low latency data packets can be monitored in the first region. Monitoring can include attempting to decode the low latency data packets in the first region. For example, monitoring can imply blind decoding of data packets. Attempting to decode data packets can include blind decoding of data packets.

[0118] Data in a low-latency data packet in a first region can be successfully decoded. In response to the successful decoding of the low-latency data packet, an acknowledgment can be transmitted in a subframe having a first offset from a subframe in which the low-latency data packet was received, wherein the first offset can be different from a second offset of a normal delay data packet. For example, the first offset can be 2, and transmitting the acknowledgment can include transmitting a hybrid automatic repeat request acknowledgment in a subframe n+2 having a first offset of two subframes from a subframe n in which the low-latency data packet was received. Decoded data from the successfully decoded low-latency data packet in the first region can be passed to a higher layer above the physical layer.

[0119] A transport block can be used that can include the number of information bits decoded from data resource elements in a resource block allocated to the device, excluding a reference signal in the assigned resource block. Similarly, a transport block can be the number of information bits encoded by a base station and sent on data resource elements in a resource block allocated to the device. Data packets can be mapped to transport blocks. If the transport block size exceeds the maximum code block size, the transport block can be segmented into more than one code block. Packets can be used in higher layers, and resource elements in resource blocks corresponding to the packets can be sent on the physical layer. A transmission time interval can indicate the duration of a data allocation. For example, a transmission time interval can include one or more subframes.

[0120] Fig.13 1300 is an example flow chart illustrating the operation of a wireless communication device such as device 100 according to a possible embodiment. Flow chart 1300 can provide for finding data packets at different locations. The low-latency data packet can be on any one of the symbols configured for low-latency packet transmission, such as a subset of the symbols. The low-latency data packet can also be on a subset of the resource blocks configured for low-latency packet transmission.

[0121] At 1310, flow chart 1300 can start. At 1320, a higher layer configuration message can be received. The higher layer configuration message can indicate a set of resource blocks for receiving data packets in at least one symbol of a subframe. The at least one symbol can be outside a control region of the subframe. The higher layer configuration message can also indicate a set of candidate symbols in the subframe to which at least one symbol belongs, the set of candidate symbols being less than all symbols in the subframe. The higher layer configuration message can further indicate a position of at least one symbol of the subframe.

[0122] At 1330, a data packet can be attempted to be decoded in a first resource element set within a resource block set. Attempting to decode may mean monitoring and / or blind decoding. The first resource element set can be in at least one symbol of a subframe. The first resource element set need not be the first absolute resource element in the resource block set. The first resource element set can be a first low-latency channel element (LCE0) including a first resource element set within a resource block set. The LCE can include resource elements in an orthogonal frequency division multiplexing symbol configured for low-latency transmission in a resource block configured for low-latency transmission. The LCE can also be dispersed between multiple resource blocks, or even between multiple resource block groups (RBGs) including multiple consecutive resource blocks. Moreover, a single symbol configured for low-latency packet transmission can include multiple LCEs in different resource blocks configured for low-latency packet transmission in a symbol. The first resource element set can further be a subset of resource elements for control channel monitoring in a subframe, wherein the control channel can assign resources for data in a second region of the subframe. For example, the first resource element set can be in the control region of the subframe.

[0123] At 1340, decoding of the data packet can be attempted in at least a second set of resource elements within a set of resource blocks. The first set of resource elements and the second set of resource elements can each be in a channel element comprising a plurality of resource elements that are not necessarily adjacent to each other in time and / or frequency. The second set of resource elements can be in at least one symbol of a subframe. The second set of resource elements can include at least one resource element that is not in the first set of resource elements. The second set of resource elements can be a second low latency channel element (LCE1) comprising at least a second set of resource elements within a set of resource blocks.

[0124] The first number of resource elements in the first resource element set can be based on a first aggregation level. The second number of resource elements in the second resource element set can be based on a second aggregation level that is higher than the first aggregation level. The second resource element set can include the first resource element set and additional resource elements. The first resource element set can also be resource elements that are different from the resource elements in the second resource element set. The number of additional resource elements can be the same as the first number of resource elements in the first resource element set. For example, the aggregation level can be doubled, such as an aggregation level of 2. The number of additional resource elements can also be greater than the first number of resource elements, such as aggregation levels of 4 and 8.

[0125] At 1350, the data packet can be successfully decoded in one of the first resource element set and the second resource element set. At 1360, in response to successfully decoding the first packet, ACK can be transmitted. The subframe can be a first subframe, and ACK can be transmitted in a time-frequency resource in a second subframe having a first offset from the first subframe. For example, the second subframe can be n+2 after the first subframe n. According to a possible embodiment, a higher layer configuration message can indicate a resource block set for receiving a low-latency data packet in at least one symbol of a subframe, and the higher layer is higher than the physical layer. The data packet can be a low-latency data packet. Control information can be attempted to be decoded in the subframe, such as in a control region of a subframe. The control information can be assigned to resources for receiving a normal-latency data packet, wherein the normal-latency data packet can have a longer delay than the low-latency data packet. In response to decoding the normal-latency data packet, ACK / NACK can be transmitted in a third subframe having a second offset from the first subframe, wherein the second offset is greater than the first offset. At 1370, the data payload of the decoded data packet can be delivered to the application layer. At 1380, flowchart 1300 can end.

[0126] Fig.14 1400 is an example flowchart illustrating the operation of a wireless communication device such as device 100 according to a possible embodiment. At 1410, flowchart 1400 can start. At 1420, a higher layer configuration can be received at the device. The higher layer configuration can be higher than the physical layer configuration. In addition to the conventional delay configuration of the conventional delay transmission mode, the higher layer configuration can also indicate that the device is configured using the low delay configuration of the low delay transmission mode. The low delay transmission mode can have a lower delay than the conventional delay transmission mode. The transmission block of the low delay configuration can be smaller than the transmission block of the conventional delay configuration. The code block size of the grouping based on the low delay configuration in the subframe can be smaller than the code block size of the grouping based on the conventional delay configuration. For example, the code block size can be smaller than the conventional delay code block size of 6144 bits. Moreover, the maximum timing advance value of the low delay configuration can be smaller than the maximum timing advance value of the conventional delay configuration.

[0127] At 1430, a packet can be received based on one of a low latency configuration and a conventional latency transmission mode in subframe n. A packet based on a low latency configuration can be received on dedicated resources on a physical downlink shared channel (PDSCH). For example, for very short transport blocks, a dedicated PDSCH resource such as in a semi-persistent scheduling (SPS) can be directly assigned to the device. This can allow the device to start detecting and decoding the PDSCH early and send uplink feedback faster because no control channel is required, which can avoid the delay of using control channel transmission.

[0128] At 1440, it is possible to determine whether the received packet is based on a low-latency configuration or based on a conventional delay transmission. For example, based on receiving a packet on a given transport bearer, the packet can be identified as being based on a low-latency configuration. The transport bearer can be an IP packet stream with a certain quality of service (QoS) between a packet gateway and a device. For example, there is an Internet Voice Protocol (VoIP) bearer requiring a QoS with a minimum bit rate guarantee, a file transfer protocol (FTP) bearer requiring a best-effort QoS with a non-guaranteed bit rate, a web browsing bearer with a best-effort QoS, and other types of bearers. Low-latency data packets can have low-latency bearers, such as games, VoIP, and other applications requiring lower latency. Based on the packet being received from a certain cell, the packet can also be identified as being based on a low-latency configuration. For example, when multiple packets are received from a certain cell, the packet can be identified as a low-latency packet. In particular, packets can be received from different cells, such as by carrier aggregation, and the device can be configured to receive low-latency packets from one or more of the different cells.

[0129] At 1450, if the packet is based on a low latency configuration, a feedback packet can be transmitted in a subsequent subframe n+p, where p<4. The subsequent subframe n+p can be the pth subframe from subframe n. For example, the feedback packet can be a hybrid automatic repeat request confirmation sent in a subsequent subframe n+2 two subframes after the first subframe n in response to receiving a packet based on a low latency configuration in the first subframe n. The hybrid automatic repeat request confirmation can be transmitted in a time portion of a subframe including at least two symbols, where resource elements are assigned to the device for uplink feedback transmission. One of the at least two symbols can be used for a pilot symbol, and another of the at least two symbols can be used for a hybrid automatic repeat request confirmation.

[0130] At 1460, if the packet is based on a normal delay configuration, a feedback packet can be transmitted in a subsequent subframe n+4 when the received packet is based on a normal delay configuration. The subsequent subframe n+4 can be the 4th subframe from subframe n. At 1470, flowchart 1400 can end.

[0131] Fig.15 1500 is an example flow chart illustrating the operation of a wireless communication device such as device 120 according to a possible embodiment. The method can be performed in a base station such as an eNB, and / or can also be performed in any other device, such as a UE in a point-to-point network, an access point, or any other device capable of transmitting data. Flowchart 1500 describes, among other things, different features of signaling the presence and / or location of a low-latency data transmission. Therefore, all features are not required, as some features may be redundant. At 1510, flow chart 1500 can begin.

[0132] At 1520, higher layer signaling can be transmitted in the subframe. The higher layer can be a layer higher than the physical layer. The higher layer signaling can indicate a set of OFDM symbols that can transmit low-latency data, a set of resource blocks that can transmit low-latency data, a set of OFDM symbols that can transmit a marker signal, and / or a set of resource elements that can transmit a marker signal. The set can include only one symbol or block, or may even be zero, such as a null set.

[0133] At 1530, a resource assignment can be transmitted. The resource assignment can assign a first set of time-frequency resources in a subframe to regular delayed data transmission. The subframe can be located after a subframe in which higher layer signaling is transmitted.

[0134] At 1540, normal delay data can be transmitted in resources within the first set of time-frequency resources that do not transmit low-latency data. For example, normal delay data can be transmitted within at least some of the first set of time-frequency resources that do not transmit low-latency data.

[0135] At 1550, low-latency data can be transmitted within a second set of time-frequency resources in a subframe. The second set can overlap at least partially with the first set. The low-latency data can have a lower latency than conventional latency data. The low-latency data within the second set of time-frequency resources may or may not occupy all resources in the second set.

[0136] At 1560, a marker signal can be transmitted. The marker signal can indicate the presence of low-latency data transmission in the subframe. A higher layer can indicate the location where the marker can be transmitted, such as which of different candidate marker locations is being used. The marker signal can be transmitted in a subframe immediately following the subframe that includes the time-frequency resources. A control channel can be transmitted as the marker signal in the immediately following subframe. The control channel can indicate the presence of low-latency data transmission in the subframe that includes the time-frequency resources. The marker signal can also be transmitted in a subframe that transmits low-latency data on a second set of time-frequency resources.

[0137] The second time-frequency resource set can include at least one OFDM symbol set in a subframe, and the marker signal can be transmitted in at least one OFDM symbol in the OFDM symbol set. For example, the marker signal can indicate a third time-frequency resource set, which includes at least the time-frequency resources within at least one OFDM symbol for transmitting low-latency data. The marker signal can also indicate the time-frequency resources within at least one OFDM symbol for transmitting low-latency data. The marker signal can additionally indicate at least some of the time-frequency resources within at least one OFDM symbol for transmitting low-latency data. The marker signal can be transmitted in a low-latency channel element (LCE), which can include a third time-frequency resource set within the second time-frequency resource set. The third time-frequency resource set can be within at least one OFDM symbol.

[0138] The second time-frequency resource set can be at least one OFDM symbol set in a subframe, and the marker signal can be transmitted in all OFDM symbols of the OFDM symbol set. The first time-frequency resource set can be a resource block set in a subframe, and the marker signal can be transmitted in at least one resource block of the resource block set. For example, the marker signal can be transmitted in the last symbol of at least one resource block of the resource block set. The marker signal can also indicate the presence or absence of low-latency data transmission in the subframe. At 1570, flowchart 1500 can end.

[0139] Fig.16 16 is an example flow chart 1600 illustrating the operation of a wireless communication device such as device 110 according to a possible embodiment. Flow chart 1600 describes, among other things, different features for determining the presence and / or location of a low-latency data transmission. Therefore, all features are not required, as some features may be redundant. At 1610, flow chart 1600 can begin.

[0140] At 1615, higher layer signaling can be received in a subframe, where the higher layer can be a layer higher than the physical layer. The higher layer signaling can indicate a set of OFDM symbols that can transmit low-latency data, a set of resource blocks that can transmit low-latency data, a set of OFDM symbols that can transmit a marker signal, and / or a set of resource elements that can transmit a marker signal. The set can be just one symbol or block, and / or can be zero, such as a null set.

[0141] At 1620, a resource assignment can be received. At 1625, a modulation and coding scheme (MCS) value can be determined from the resource assignment. At 1630, a first set of time-frequency resources in a subframe can be determined from the resource assignment. The subframe can be a first subframe. The first set of time-frequency resources can include a set of resource blocks in the subframe.

[0142] At 1635, a marker signal can be received. The marker signal can be received in at least one resource block of a resource block set. The marker signal can also be received in a second subframe immediately following the first subframe. The marker signal can also be received in a first subframe comprising a first set of time-frequency resources. For example, the marker signal can be received in at least one OFDM symbol of the first subframe. A control channel can be received as the marker signal in the second subframe. The control channel can indicate the presence of low-latency data transmission in the first subframe. The marker signal can also indicate the presence or absence of low-latency data transmission in the subframe.

[0143] At 1640, a second time-frequency resource set in a subframe can be determined. The second time-frequency resource set can be used for low-latency data transmission and can overlap with at least a portion of the first time-frequency resource set. The second time-frequency resource set can be determined based on the received marker signal. The second time-frequency resource set can include at least one OFDM symbol set in a subframe, and the marker signal can be received in all OFDM symbols in the OFDM symbol set. The marker signal received at 1635 can also indicate a third time-frequency resource set. The third time-frequency set can include at least time-frequency resources within at least one OFDM symbol for receiving low-latency data.

[0144] According to a possible implementation, the low-latency data transmission can be successfully decoded on the third time-frequency resource set in the subframe.Then, the second time-frequency resource set can be determined as a time-frequency resource belonging to both the first time-frequency resource set and the third time-frequency resource set.

[0145] At 1645, a log-likelihood ratio (LLR) value can be adjusted. The adjusted LLR value can be a bit value corresponding to a conventional delayed data transmission and mapped to a second set of time-frequency resources. Adjusting the LLR value can include adjusting a soft bit value. The LLR value can be set to zero. The LLR value can be adjusted only when the MCS value exceeds an MCS threshold. For example, the MCS threshold can correspond to 3 / 4 of a 16QAM rate. If the MCS determined from the resource assignment is less than the threshold, the device may not adjust the LLR value.

[0146] At 1650, based on the determined first time-frequency resource set and the second time-frequency resource set, it is possible to decode the conventional delayed data transmission in the subframe. Conventional delayed transmission can have a longer delay than low-delay transmission. Conventional delayed data transmission can be intended for the device. Low-delay data transmission may or may not be intended for the device. It is possible to decode the conventional delayed transmission in the subframe based on the adjusted LLR. It is also possible to decode the conventional delayed transmission based on the bits corresponding to the conventional delayed data transmission and mapped to the second time-frequency resource set that are set to zero. When the MCS value is less than the threshold, the conventional delayed data can be decoded without considering the second resource set. For example, it is possible to receive conventional delayed data in resources within the first time-frequency resource set where low-delay data is not transmitted, and then the conventional delayed data can be decoded. As another example, it is possible to receive conventional delayed data in resources within at least some of the first time-frequency resource set where low-delay data is not received. It is possible to receive conventional delayed data in at least some of the resources within the first time-frequency resource set. For example, the device can determine the MCS value from the resource assignment, and if the MCS is less than the MCS threshold, it can not look up the flag and / or skip the step of determining the second set of resources, and can decode the regular delayed data without considering the second set of resources. At 1655, flowchart 1600 can end.

[0147] It should be understood that, although specific steps are shown in the figures, various additional or different steps can be performed according to the embodiment, and one or more of the specific steps can be rearranged, repeated or completely deleted according to the embodiment. Moreover, some of the steps performed can be repeated on a continuing or continuous basis while other steps are performed. In addition, different steps can be performed by different elements or in a single element of the disclosed embodiments.

[0148] Fig.17 1 is an example block diagram of an apparatus 1700, such as device 110, according to a possible embodiment. The apparatus 1700 can include a housing 1710, a controller 1720 within the housing 1710, audio input and output circuitry 1730 coupled to the controller 1720, a display 1740 coupled to the controller 1720, a transceiver 1750 coupled to the controller 1720, an antenna 1755 coupled to the transceiver 1750, a user interface 1760 coupled to the controller 1720, a memory 1770 coupled to the controller 1720, and a network interface 1780 coupled to the controller 1720. The elements of the apparatus 1700 can perform the methods and processes of the devices and apparatus described in the embodiments of the present disclosure.

[0149] Display 1740 can be a viewfinder, a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma display, a projection display, a touch screen, or any other device that displays information. Transceiver 1750 can include a transmitter and / or a receiver. Audio input and output circuit 1730 can include a microphone, a speaker, a transducer, or any other audio input and output circuit. User interface 1760 can include a keypad, a keyboard, a button, a touch pad, a joystick, a touch screen display, another additional display, or any other device that is beneficial to providing an interface between a user and an electronic device. Network interface 1780 can be a universal serial bus port, an Ethernet port, an infrared transmitter / receiver, a USB port, an IEEE1394 port, a WLAN transceiver, or any other interface that can connect the device to a network or a computer and can transmit and receive data communication signals. Memory 1770 can include random access memory, read-only memory, optical memory, flash memory, removable memory, a hard drive, a cache, or any other memory that can be coupled to a wireless communication device.

[0150] Device 1700 and / or controller 1720 may implement any operating system, such as Microsoft or Android TMor any other operating system. For example, the device operating software can be written in any programming language, such as C, C++, Java or Visual Basic. The device software can also run on an application framework, such as frame, Framework or any other application framework. Software and / or operating system may be stored in memory 1770 or anywhere else on device 1700. Device 1700 and / or controller 1720 may also use hardware to implement the operations of the present disclosure. For example, controller 1720 may be any programmable processor. Embodiments of the present disclosure may also be implemented on general or special-purpose computers, programmed microprocessors or microprocessors, peripheral integrated circuit elements, application-specific integrated circuits or other integrated circuits, hardware / electronic logic circuits such as discrete element circuits, programmable logic devices such as programmable logic arrays, field programmable gate arrays, and the like. In general, controller 1720 may be any controller or one or more processor devices capable of operating an electronic device and implementing embodiments of the present disclosure.

[0151] According to a possible embodiment, the transceiver 1750 can receive a higher layer configuration message, wherein the higher layer can be higher than the physical layer. The controller 1720 can determine the first area of ​​the subframe for receiving the data packet based on the higher layer configuration message. The data packet in the first area can be a low-delay data packet, which has a maximum delay lower than the normal delay data packet in the second area. For example, the data packet includes a low-delay data packet with a delay lower than the normal data packet. The first area can be used to transmit a control signal for decoding the normal delay data packet in the second area. The first area can be the first time area of ​​the subframe, wherein the first area can include up to 4 multi-carrier symbols. The first area can be a control area including at least one physical downlink control channel including a control channel element. Data packets can be received on one or more of the control channel elements including the resource elements in the first resource element set.

[0152] The first region can include a first set of resource elements. The first set of resource elements can be a subset of a second set of resource elements in the first region, wherein the first region can be used for control channel monitoring. The number of resource elements in the first set can be less than the number of resource elements in the second set. A data packet can be mapped to at least one resource element of the first set of resource elements.

[0153] The controller 1720 can monitor the first area. The monitoring can include attempting to decode the data packet in the first area. For example, the controller 1720 can perform control channel monitoring in the first area. The controller 1720 can decode the data in the data packet in the first area. The controller 1720 can pass the decoded data from the data packet in the first area to the application layer. For example, the controller 1720 can use the first identifier to determine the successful decoding of the control channel in the first area, and can use the second identifier to determine the successful decoding of the data in the data packet in the first area. The first identifier can be a cell radio network temporary identifier (C-RNTI) received in a higher layer configuration message, and the second identifier can be a low latency radio network temporary identifier (low latency-RNTI) received in a higher layer configuration message.

[0154] In response to successfully decoding the low latency data packet, the transceiver 1750 can transmit an acknowledgment in a subframe having a first offset from a subframe in which the low latency data packet was received. The first offset can be different from a second offset for normal latency data packets. For example, the first offset can be 2, and transmitting the acknowledgment can include transmitting a hybrid automatic repeat request acknowledgment in a subframe n+2 having a first offset of two subframes from a subframe n in which the low latency data packet was received.

[0155] According to another related embodiment, the transceiver 1750 can receive a higher layer configuration message indicating a set of resource blocks for receiving a data packet in at least one symbol of a subframe. The higher layer can be higher than the physical layer. The at least one symbol can be outside the control region. The higher layer configuration message can also indicate a set of candidate symbols in the subframe. The at least one symbol can belong to the set of candidate symbols. The set of candidate symbols can be less than all symbols in the subframe.

[0156] Controller 1720 can attempt to decode the data packet in a first set of resource elements (LCE0) within a set of resource blocks, the first set of resource elements being in at least one symbol of a subframe. The first set of resource elements can be a subset of resource elements monitored by a control channel in a subframe. The control channel can assign resources for data in a second region of the subframe.

[0157] The controller 1720 can attempt to decode the data packet in at least a second set of resource elements (LCE1) within the set of resource blocks. The second set of resource elements can be in at least one symbol of the subframe. The second set of resource elements can include at least one resource element that is not in the first set of resource elements. The first number of resource elements in the first set of resource elements can be based on a first aggregation level. The second number of resource elements in the second set of resource elements can be based on a second aggregation level that is higher than the first aggregation level. Moreover, the second set of resource elements can include the first set of resource elements and additional resource elements. The number of additional resource elements can be the same as the first number of resource elements in the first set of resource elements.

[0158] The controller 1720 can successfully decode the data packet in one of the first set of resource elements and the second set of resource elements. The subframe can be a first subframe, and the transceiver 1750 can transmit an ACK in time-frequency resources in a second subframe having a first offset from the first subframe in response to decoding the first packet in response to successfully decoding the data packet.

[0159] Moreover, a higher layer configuration message can indicate a resource block set for receiving a low-delay data packet in at least one symbol of a subframe, wherein the higher layer can be higher than the physical layer. The data packet can be a low-delay data packet, and the controller 1750 can attempt to decode control information in the subframe. The control information can be assigned to resources for receiving normal-delay data packets, wherein the normal-delay data packets have a longer delay than the low-delay data packets. The controller 1750 can decode the normal-delay data packets, and then the transceiver can transmit ACK / NACK in the third subframe with the second offset from the first subframe in response to decoding the normal-delay data packets, wherein the second offset is greater than the first offset. The controller 1720 can pass the data payload of the decoded data packets to the application layer.

[0160] According to another related embodiment, the transceiver 1750 can receive a higher layer configuration. The higher layer configuration can be higher than the physical layer configuration. The higher layer configuration indicates that in addition to the regular delay configuration of the regular delay transmission mode, the low delay configuration of the low delay transmission mode can also be used to configure the device 1700. The low delay transmission mode can have a lower delay than the regular delay transmission mode.

[0161] The transceiver 1750 can receive packets based on one of the low-latency configuration and the regular delay transmission mode in subframe n. The code block size of the packet based on the low-latency configuration in the subframe can be smaller than the code block size of the packet based on the regular delay configuration. The maximum timing advance value of the low-latency configuration can be smaller than the maximum timing advance value of the regular delay configuration.

[0162] The controller 1720 can identify the packet as being based on a low-latency configuration based on receiving a packet on a given transport bearer. The controller 1720 can identify the packet as being in a low-latency configuration based on receiving a packet from a specific cell. The controller 1720 can also identify the packet as being based on a low-latency configuration based on other characteristics of the packet and / or surrounding transmissions. The transport block of the low-latency configuration can be smaller than the transport block of the conventional delay configuration. The packet based on the low-latency configuration can be received on a dedicated resource on a physical downlink shared channel (PDSCH).

[0163] The transceiver 1750 can transmit a feedback packet in a subsequent subframe n+p, wherein p<4 when the received packet is based on a low latency configuration. The subsequent subframe n+p can be the pth subframe from subframe n. The feedback packet can be a hybrid automatic repeat request confirmation sent in a subsequent subframe n+2 two subframes after the first subframe n in response to receiving a packet based on a low latency configuration in the first subframe n. The hybrid automatic repeat request confirmation can be transmitted in a time portion of a subframe including at least two symbols, wherein resource elements are assigned to the device for uplink feedback transmission. One symbol of the at least two symbols can be used for a pilot symbol, and another symbol of the at least two symbols can be used for a hybrid automatic repeat request confirmation. When the received packet is based on a conventional delay configuration, the transceiver 1750 can transmit a feedback packet in a subsequent subframe n+4, wherein the subsequent subframe n+4 can be the 4th subframe from subframe n.

[0164] According to another possible embodiment, the transceiver 1750 can receive a resource assignment. The controller 1720 can determine a first set of time-frequency resources in a subframe from the resource assignment. The controller 1720 can determine a second set of time-frequency resources in a subframe. The second set of time-frequency resources can be used for low-latency data transmission. The second set of time-frequency resources can overlap at least a portion of the first set of time-frequency resources. The transceiver 1750 can receive a conventional delayed data transmission in a subframe. The controller 1720 can decode a conventional delayed data transmission in a subframe based on the determined first set of time-frequency resources and the second set of time-frequency resources, wherein the conventional delayed transmission can have a longer delay than the low-latency transmission.

[0165] According to another possible embodiment, the transceiver 1750 can monitor the first control channel in the first time portion of the subframe. The combination of the transceiver 1750 and the controller 1720 can also be regarded as monitoring the control channel in the subframe, because the transceiver 1750 can receive the subframe, and the controller 1720 can attempt to decode the control channel. The subframe can include a plurality of OFDM symbols in the time domain and a plurality of subcarriers in the frequency domain. The first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can only assign data resources in the first time portion of the subframe. The transceiver can monitor the second control channel in the second time portion of the subframe. The first time portion can occupy at least one OFDM symbol in the subframe that is different from the second time portion. The second time portion can also occupy at least one OFDM symbol in the subframe that is different from the first time portion. The second control channel can occupy a second subcarrier portion less than the plurality of subcarriers. The second control channel can only assign data resources in the second time portion of the subframe. The controller 1720 can decode the first control channel. In response to decoding the first control channel, the transceiver 1750 can receive data in a first time portion of the subframe. The data in the first time portion can be assigned by the first control channel. The controller 1720 can decode the data.

[0166] Fig.18 18 is an example block diagram of a device 1800, such as device 120, according to a possible embodiment. Device 1800 may include a controller 1810, a memory 1820, a database interface 1830, a transceiver 1840, an input / output (I / O) device interface 1850, a network interface 1860, and a bus 1870. For example, device 1800 can implement any operating system, such as Microsoft UNIX or LINUX. For example, the device operating software can be written in any programming language, such as C, C++, Java or Visual Basic. The device software can run on an application framework, for example, server, framework or any other application framework.

[0167] The transceiver 1840 can establish a data connection with the device 110. The controller 1810 can be any programmable processor. The embodiments of the present disclosure can also be implemented on a general or special purpose computer, a programmed microprocessor or microprocessors, peripheral integrated circuit components, application specific integrated circuits or other integrated circuits, hardware / electronic logic circuits such as discrete element circuits, programmable logic devices such as programmable logic arrays, field programmable gate arrays, etc. In general, the controller 1810 can be any controller or one or more processor devices capable of operating a device and implementing the embodiments of the present disclosure.

[0168] Memory 1820 can include volatile and non-volatile data storage devices, including one or more electrical, magnetic or optical memories, such as random access memory (RAM), cache, hard disk drive or other memory devices. Memory 1820 can have cache to accelerate access to specific data. Memory 1820 can also be connected to compact disk-read only memory (CD-ROM), digital video disk-read only memory (DVD-ROM), DVD read-write input, tape drive, thumb drive or other removable memory devices that allow media content to be uploaded directly to the system. Data can be stored in memory 1820 or in a separate database. For example, controller 1810 can use database interface 1830 to access a database.

[0169] I / O device interface 1850 can be connected to one or more input and output devices, which may include keyboard, mouse, touch screen, monitor, microphone, voice recognition device, speaker, printer, disk drive or any other device or device combination that accepts input and / or provides output. Network connection interface 1860 can be connected to communication equipment, modem, network interface card, transceiver or any other device that can transmit signal to network and receive signal from network. The components of equipment 1800 can be connected via bus 1870, can be wirelessly linked, or can be connected by other means. Any element in equipment 1800 can perform the method and process of equipment and device described in the disclosed embodiment. For example, equipment 1800 and / or controller 1810 can generate signal, and transceiver 1840 can transmit the signal received by equipment 110.

[0170] According to a possible embodiment, the transceiver 1840 can transmit a resource assignment. The resource assignment can assign a first set of time-frequency resources in a subframe to a conventional delayed data transmission. The transceiver 1840 can transmit low-latency data within a second set of time-frequency resources in a subframe. The second set can overlap at least partially with the first set, wherein the low-latency data has a lower latency than the conventional delayed data. The transceiver 1840 can transmit a marker signal indicating that there is a low-latency data transmission in the subframe. The controller 1810 can also generate a resource assignment, configure the low-latency data for transmission, and generate a marker signal.

[0171] According to a possible embodiment, the controller 1810 can configure the first control channel and the second control channel. The transceiver 1840 can transmit the first control channel in the first time portion of the subframe. The subframe can include a plurality of OFDM symbols in the time domain and a plurality of subcarriers in the frequency domain. The first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can assign the first data resource only in the first time portion of the subframe. The transceiver 1840 can transmit the second control channel in the second time portion of the subframe. The second control channel can occupy a second subcarrier portion less than the plurality of subcarriers. The first time portion can occupy at least one first OFDM symbol in the subframe that is different from the second time portion. The second time portion can also occupy at least one second OFDM symbol in the subframe that is different from the first time portion. The second control channel can assign the second data resource only in the second time portion of the subframe.

[0172] The controller 1810 can also configure a third control channel. The transceiver 1840 can transmit the third control channel. The third control channel can occupy at least one third OFDM symbol in a third time portion different from the first time portion and the second time portion in the subframe. The third control channel can assign a third data resource in a fourth time portion different from the third time portion.

[0173] Fig.23 2300 is an example flow chart illustrating the operation of a wireless communication device such as device 120 according to a possible embodiment. For example, flow chart 2300 can be performed in a base station such as an eNB, and / or can also be performed in any other device, such as a UE in a point-to-point network, an access point, or any other device capable of transmitting data. At 2310, flow chart 2300 can start.

[0174] At 2320, a first control channel can be transmitted in a first time portion of a subframe, such as in C2, D2 of the TTI 500 described above. The subframe can include a plurality of OFDM symbols in the time domain and a plurality of subcarriers in the frequency domain. The first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can assign a first data resource only in the first time portion of the subframe.

[0175] At 1530, a second control channel can be transmitted in a second time portion of the subframe, such as in C1, D1, C3, D3, C4, D4, C5, D5 and / or C6, D6 of the above-mentioned TTI 500. The first time portion can occupy at least one first OFDM symbol in the subframe that is different from the second time portion. The second time portion can occupy at least one second OFDM symbol in the subframe that is different from the first time portion. For example, the second time portion can occupy an OFDM symbol in the subframe that is mutually exclusive with the OFDM symbol occupied by the first time portion. The second control channel can occupy a second subcarrier portion that is less than the plurality of subcarriers. The first subcarrier portion and the second subcarrier portion can be configured by a layer higher than the physical layer. The second control channel can assign a second data resource only in the second time portion of the subframe.

[0176] At 2330, a third control channel can be transmitted. The third control channel can occupy at least one third OFDM symbol in a third time portion of the subframe that is different from the first time portion and the second time portion, such as the legacy control portion of the TTI 500 described above, and the third control channel assigns third data resources in a fourth time portion that is different from the third time portion, such as the legacy allocation portion of the TTI 500 described above. The fourth time portion can include the first time portion and the second time portion. According to a possible implementation, the subframe can include a starting OFDM symbol, and the third time portion can include a starting OFDM symbol in the subframe.

[0177] At 2350, data can be transmitted in a first data resource in a first time portion. The first time portion can overlap with a fourth time portion. The data can correspond to a first control channel. For example, a low-latency data packet can be transmitted in a first data resource in a first time portion, and the low-latency data packet can have a shorter delay than a normal-latency data packet transmitted in a third data resource in a fourth time portion. At 2360, flow chart 2300 can end.

[0178] Fig.24 16 is an example flow chart 1600 illustrating the operation of a wireless communication device such as device 110 according to a possible embodiment. For example, the method can be performed in a device such as a UE, and / or can also be performed in any other device capable of receiving data. At 2410, flow chart 2400 can start.

[0179] At 2420, a first control channel can be monitored in a first time portion of a subframe, such as in C2, D2 of TTI 500 described above. The subframe can include a plurality of OFDM symbols in the time domain and a plurality of subcarriers in the frequency domain. The first control channel can occupy a first subcarrier portion less than the plurality of subcarriers. The first control channel can assign data resources only in the first time portion of the subframe.

[0180] At 2430, a second control channel can be monitored in a second time portion of the subframe, such as in C1, D1, C3, D3, C4, D4, C5, D5 and / or C6, D6 of the above-mentioned TTI 500. The second time portion can appear before or after the first time portion in the time domain. The first time portion can occupy at least one OFDM symbol in the subframe that is different from the second time portion. The second time portion can occupy at least one OFDM symbol in the subframe that is different from the first time portion. For example, the second time portion can occupy an OFDM symbol in the subframe that is mutually exclusive with the OFDM symbol occupied by the first time portion. The second control channel can also occupy a second subcarrier portion that is less than the plurality of subcarriers. The first subcarrier portion and the second subcarrier portion can be configured by a layer higher than the physical layer. The second control channel can assign data resources only in the second time portion of the subframe.

[0181] At 2440, a third control channel can be monitored. The third control channel can occupy at least one third OFDM symbol in a third time portion of the subframe that is different from the first time portion and the second time portion, such as the legacy control portion of the TTI 500 described above. The subframe can include a starting OFDM symbol, and the third time portion can include the starting OFDM symbol in the subframe. The third control channel can assign a third data resource in a fourth time portion that is different from the third time portion, such as the legacy allocation portion of the TTI 500 described above. The fourth time portion can include the first time portion and the second time portion.

[0182] At 2450, a first control channel can be decoded. At 2460, in response to decoding the first control channel, data can be received in a first time portion of a subframe. The data in the first time portion can be assigned by the first control channel. The data in the first time portion of the subframe can be located on a subcarrier different from the first control channel. For example, data can be received in a first data resource in a first time portion, wherein the first time portion can overlap with a fourth time portion, and wherein the data can correspond to the first control channel. As another example, a low-latency data packet can be received in a first data resource in a first time portion, wherein the low-latency data packet in the first data resource in the first time portion has a shorter delay than a normal-latency data packet in a third data resource in the fourth time portion. At 2470, data can be decoded. At 2480, flowchart 2400 can end.

[0183] These embodiments can be implemented using computer executable instructions such as program modules executed by electronic devices such as general-purpose computers, but this is not necessary. Generally speaking, program modules can include routine programs, objects, components, data structures, and other program modules that perform specific tasks or implement specific abstract data types. Program modules can be based on software and / or can be based on hardware. For example, program modules can be stored on computer-readable storage media, such as hard disks, flash drives, optical drives, solid-state drives, CD-ROM media, thumb drives, and other computer-readable storage media that provide non-transient storage in addition to temporary propagation signals. In addition, these embodiments can be practiced in a network computing environment with many types of computer system configurations, including personal computers, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network personal computers, minicomputers, mainframe computers, and other computing environments.

[0184] The method of the present disclosure can be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, integrated circuits, hardware electronic or logic circuits such as discrete element circuits, programmable logic devices, etc. In general, any device that has a finite state machine capable of implementing the flow chart shown in the accompanying drawings can be used to implement the processor functions of the present disclosure.

[0185] Although the present disclosure has been described using specific embodiments of the present disclosure, it is apparent that many alternatives, modifications and variations will be apparent to those skilled in the art. For example, the various components of these embodiments may be interchanged, added or replaced in other embodiments. Moreover, all elements of each of the accompanying drawings are not necessary for the operation of the embodiments of the present disclosure. For example, a person of ordinary skill in the field of the embodiments of the present disclosure will be able to form and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as described herein are intended to be illustrative rather than limiting. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0186] In this document, relational terms such as "first", "second" and the like can be used only to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The phrase "at least one" followed by a list is defined to represent one, some or all of the elements in the list, but not necessarily all of them. The term "include" or any other variation thereof is intended to cover non-exclusive inclusions, such as processes, methods, products or devices including a list of elements not only including those elements, but also including other elements that are not explicitly listed or inherent to such processes, methods, products or devices. Without further constraints, the elements followed by terms such as "a / an" do not exclude the presence of other identical elements in the processes, methods, products or devices including the elements. Moreover, the term "another" is defined as at least the second or more. The terms "include", "have" and the like used herein are defined as "include". In addition, the background technology section is written as the inventor's personal understanding of the context of some embodiments when submitting this application, and includes any problems that the inventor himself recognizes in the prior art and / or problems encountered in the inventor's own work.

Claims

1. A method performed by a base station, comprising: transmitting a resource assignment that assigns a first set of time-frequency resources in a subframe for data transmission; transmitting data within a second set of time-frequency resources in the subframe, the second set of time-frequency resources at least partially overlapping with the first set of time-frequency resources; as well as transmitting a flag signal, the flag signal indicating which of the first time-frequency resource sets in the subframe the UE will not use, Transmitting the marker signal further includes transmitting the marker signal in the subframe for transmitting low-latency data on the second set of time-frequency resources.

2. The method according to claim 1, in, The subframes include a first subframe, and Transmitting the marker signal further includes transmitting the marker signal in a second subframe immediately following the first subframe.

3. The method according to claim 2, wherein: Transmitting the marker signal in the second subframe includes transmitting a control channel as the marker signal in the second subframe, the control channel indicating that low-latency data transmission exists in the first subframe.

4. The method according to claim 1, in, The second set of time-frequency resources includes at least a set of orthogonal frequency division multiplexing symbols in the subframe, and Transmitting the marker signal further comprises transmitting the marker signal in at least one orthogonal frequency division multiplexing symbol of the orthogonal frequency division multiplexing symbol set.

5. The method according to claim 4, wherein The flag signal indicating the presence of low-latency data transmission in the subframe indicates a time-frequency resource within the at least one orthogonal frequency division multiplexing symbol for transmitting low-latency data.

6. The method according to claim 4, wherein: The flag signal indicating the presence of low-latency data transmission in the subframe indicates at least some of the time-frequency resources within the at least one orthogonal frequency division multiplexing symbol in which low-latency data is transmitted.

7. The method according to claim 4, wherein: Transmitting the marker signal further includes transmitting the marker signal in a low-latency channel element, wherein the low-latency channel element includes a third set of time-frequency resources within the second set of time-frequency resources.

8. The method according to claim 7, wherein: The third set of time-frequency resources is within the at least one orthogonal frequency division multiplexing symbol.

9. The method according to claim 1, in, The second set of time-frequency resources includes at least a set of orthogonal frequency division multiplexing symbols in the subframe, and Transmitting the marker signal further includes transmitting the marker signal in all orthogonal frequency division multiplexing symbols of the orthogonal frequency division multiplexing symbol set.

10. The method according to claim 1, in, The first time-frequency resource set includes a resource block set in the subframe, and Transmitting the marker signal further includes transmitting the marker signal in at least one resource block in the resource block set.

11. The method according to claim 1, in, The subframe is a first subframe; wherein the method further comprises transmitting higher layer signaling in a subframe earlier than the first subframe, wherein the higher layer comprises a layer higher than a physical layer, and wherein the higher layer signaling indicates at least one of the following: An OFDM symbol set capable of transmitting low-latency data, A set of resource blocks capable of transmitting low-latency data, a set of orthogonal frequency division multiplexing symbols capable of transmitting a marker signal, and A set of resource elements that can transmit a tag signal.

12. The method according to claim 1, further comprising: Normal delay data is transmitted in resources within the first time-frequency resource set in which low delay data is not transmitted.

13. The method according to claim 1, further comprising: Normally delayed data is transmitted in at least some of the resources within the first set of time-frequency resources.

14. The method according to claim 1, wherein The flag signal indicating the presence of low-latency data transmission in the subframe indicates the presence or absence of low-latency data transmission in the subframe.

15. A method performed by a user equipment (UE), comprising: receiving resource assignments; determining a first set of time-frequency resources in a subframe from the resource assignment; Determine a second set of time-frequency resources in the subframe, where the second set of time-frequency resources is used for data transmission, and the second set of time-frequency resources overlaps with at least a portion of the first set of time-frequency resources; as well as decoding the data transmission in the subframe based on the determined first set of time-frequency resources and second set of time-frequency resources, The method further comprises: receiving a flag signal, the flag signal indicating which one of the first time-frequency resource sets in the subframe will not be used by the UE, Wherein, receiving the marker signal further includes receiving the marker signal in the subframe for transmitting low-latency data on the second set of time-frequency resources.

16. The method according to claim 15, further comprising: adjusting a log-likelihood ratio value of bits corresponding to normal delayed data transmission and mapped to the second set of time-frequency resources, The decoding further comprises decoding the normally delayed data transmission in the subframe based on the adjusted log-likelihood ratio.

17. The method according to claim 15, further comprising: setting the log-likelihood ratio values ​​of the bits corresponding to the normal delayed data transmission and mapped to the second set of time-frequency resources to zero, The decoding of the normally delayed data transmission further comprises decoding the normally delayed data transmission based on the zeroed bits corresponding to the normally delayed data transmission and mapped to the second set of time-frequency resources.

18. The method according to claim 15, further comprising: determining a modulation and coding scheme value from the resource assignment; as well as adjusting a log-likelihood ratio value of bits corresponding to normal delayed data transmission and mapped to the second set of time-frequency resources only when the modulation and coding scheme value exceeds a modulation and coding scheme threshold, Wherein, decoding the normally delayed data transmission further comprises decoding the normally delayed data transmission based on the adjusted log-likelihood ratio.

19. The method according to claim 15, wherein Determining a second set of time-frequency resources includes determining the second set of time-frequency resources based on the marker signal.

20. The method of claim 19, further comprising: determining a modulation and coding scheme value from the resource assignment, The decoding includes decoding the normal delay data without considering the second time-frequency resource set when the modulation and coding scheme value is less than a threshold.

21. The method according to claim 15, wherein Receiving the marker signal in the second subframe includes receiving a control channel as the marker signal in the second subframe, the control channel indicating the presence of low-latency data transmission in the first subframe.

22. The method according to claim 15, wherein Receiving the marker signal further includes receiving the marker signal in the subframe including the first set of time-frequency resources.

23. The method according to claim 22, wherein Receiving the marker signal further includes receiving the marker signal in at least one orthogonal frequency division multiplexing symbol of the subframe.

24. The method according to claim 22, in, The first time-frequency resource set includes a resource block set in the subframe, and Receiving the marker signal further includes receiving the marker signal in at least one resource block in the resource block set.

25. The method according to claim 15, wherein The flag signal indicates the presence or absence of low-latency data transmission in the subframe.

26. The method according to claim 15, in, The subframe is a first subframe; wherein the method further comprises receiving higher layer signaling in a subframe earlier than the first subframe, wherein the higher layer comprises a layer higher than a physical layer, and wherein the higher layer signaling indicates at least one of the following: An OFDM symbol set capable of transmitting low-latency data, A set of resource blocks capable of transmitting low-latency data, a set of orthogonal frequency division multiplexing symbols capable of transmitting a marker signal, and A set of resource elements that can transmit a tag signal.

27. The method of claim 15, further comprising: Normal delay data is received in resources within a first set of time-frequency resources in which low delay data is not transmitted.

28. The method of claim 15, further comprising: Normal delay data is received in at least some of the resources within the first set of time-frequency resources.

29. The method of claim 15, further comprising: successfully decoding the low-latency data transmission on a third set of time-frequency resources in the subframe, Determining the second time-frequency resource set further includes determining the second time-frequency resource set as time-frequency resources belonging to both the first time-frequency resource set and the third time-frequency resource set.

30. A base station, comprising: a controller configured to control operation of the device; as well as a transceiver coupled to the controller, the transceiver being configured to: transmitting a resource assignment, the resource assignment assigning a first set of time-frequency resources in a subframe for data transmission, transmitting data within a second set of time-frequency resources in the subframe, the second set of time-frequency resources at least partially overlapping with the first set of time-frequency resources, and transmitting a flag signal, the flag signal indicating which of the first time-frequency resource sets in the subframe the UE will not use, Transmitting the marker signal further includes transmitting the marker signal in the subframe for transmitting low-latency data on the second set of time-frequency resources.

31. A user equipment (UE), comprising: a transceiver configured to receive a resource assignment; a controller coupled to the transceiver, the controller being configured to: determining a first set of time-frequency resources in a subframe from the resource assignment, and determining a second set of time-frequency resources in the subframe, where the second set of time-frequency resources is used for data transmission and overlaps with at least a portion of the first set of time-frequency resources; wherein the transceiver is configured to receive data transmission in the subframe, and The controller is configured to decode the data transmission in the subframe based on the determined first set of time-frequency resources and second set of time-frequency resources, The transceiver is further configured to: receive a flag signal, the flag signal indicating which of the first time-frequency resource sets in the subframe the UE will not use, The transceiver is further configured to: receive the marker signal in the subframe for transmitting low-latency data on the second set of time-frequency resources.

Images