WO2017191360A1 - Utilisation d'attributions de liaison montante - Google Patents

Utilisation d'attributions de liaison montante Download PDF

Info

Publication number
WO2017191360A1
WO2017191360A1 PCT/FI2017/050321 FI2017050321W WO2017191360A1 WO 2017191360 A1 WO2017191360 A1 WO 2017191360A1 FI 2017050321 W FI2017050321 W FI 2017050321W WO 2017191360 A1 WO2017191360 A1 WO 2017191360A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource blocks
user equipment
transmission
allocated
data
Prior art date
Application number
PCT/FI2017/050321
Other languages
English (en)
Inventor
Suresh Kalyanasundaram
Klaus Ingemann Pedersen
Sheshachalam B S
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2017191360A1 publication Critical patent/WO2017191360A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies

Definitions

  • This specification relates to the utilisation of an uplink allocation by user equipment.
  • E-UTRA Advanced LTE
  • URLLC ultra-reliable low-latency communications
  • MBB mobile broadband
  • One way in which low latencies may be achieved is the allocation of a number of resource blocks to one or more user equipments (UEs) that is larger than the UE is expected to require. This process may be referred to as "over-dimensioning".
  • this specification describes a method comprising determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment and, if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused.
  • the method may comprise providing signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer.
  • the method may additionally or alternatively comprise providing signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer.
  • the signalling data may be independently decodable relative to the data transmitted in the resource blocks.
  • the method may comprise reading data from the buffer into the required number of resource blocks in a pre-defined order.
  • the pre-defined order may be upwards from a lowest-numbered allocated resource block or downwards from a highest-numbered allocated resource block.
  • the pre-defined order may start from a middle resource block of the allocated resource blocks. In such examples, the pre-defined order may be alternately, either side of the middle resource block.
  • the pre-defined order may be indicated to the user equipment via a message received from the eNodeB.
  • the message may be an uplink scheduling grant.
  • the method may comprise determining which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains.
  • this specification describes a method comprising prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.
  • the method may comprise determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block.
  • the method may further comprise performing blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment.
  • the method may alternatively or additionally comprise performing blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise.
  • the method may comprise performing blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks.
  • the method may comprise determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.
  • the method may comprise indicating to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks.
  • the order may be selected from two or more available options.
  • the method may alternatively or additionally comprise determining the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.
  • this specification describes apparatus configured to perform a method according to either of the first and second aspects.
  • this specification describes computer-readable instructions, which when executed by computing apparatus, cause the computing apparatus to perform a method according to either of the first and second aspects.
  • this specification describes apparatus comprising at least one processor, and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus: to determine a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, to utilise the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and to leave a remaining number of the allocated number of resource blocks unused.
  • the computer program code when executed by the at least one processor, may cause the apparatus to provide signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer.
  • the computer program code when executed by the at least one processor, may cause the apparatus to provide signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer.
  • the signalling data may be independently decodable relative to the data transmitted in the resource blocks.
  • the computer program code when executed by the at least one processor, may cause the apparatus to read data from the buffer into the required number of resource blocks in a pre-defined order.
  • the pre-defined order may be upwards from a lowest-numbered allocated resource block or downwards from a highest-numbered allocated resource block.
  • the pre-defined order may start from a middle resource block of the allocated resource blocks.
  • the pre-defined order may be alternately, either side of the middle resource block.
  • the pre-defined order may be indicated to the user equipment via a message, which may be an uplink scheduling grant, received from the eNodeB.
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains.
  • this specification describes apparatus comprising at least one processor and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus, prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, to determine whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block.
  • the computer program code when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment.
  • the computer program code when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise.
  • the computer program code when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks.
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.
  • the computer program code when executed by the at least one processor, may cause the apparatus to indicate to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks.
  • the computer program code when executed by the at least one processor, may cause the apparatus to select the order from two or more available options.
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.
  • this specification describes a computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least: determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused.
  • the computer-readable code stored on the medium of the seventh aspect may further cause performance of any of the operations described with reference to the method of the first aspect.
  • this specification describes a computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least: prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.
  • the computer-readable code stored on the medium of the eighth aspect may further cause performance of any of the operations described with reference to the method of the second aspect.
  • this specification describes apparatus comprising means for
  • the apparatus of the ninth aspect may further comprise means for causing performance of any of the operations described with reference to method of the first aspect.
  • this specification describes means for, prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.
  • the apparatus of the tenth aspect may further comprise means for causing performance of any of the operations described with reference to method of the second aspect.
  • Figure 1 is an example of a mobile telecommunications radio access network including plural eNodeBs (eNBs) and one or more user equipments (UEs);
  • eNBs eNodeBs
  • UEs user equipments
  • Figure 2 is a flow chart illustrating various operations which may be performed by a UE operating within the network of Figure 1;
  • Figure 3 is a flow chart illustrating various operations which may be performed by an eNB operating within the network of Figure 1;
  • Figure 4 is a schematic illustration of an example configuration of a UE which may be configured to perform various operations described with reference to Figures 1 and 2;
  • Figure 5 is a schematic illustration of an example configuration of an eNBs which may be configured to perform various operations described with reference to Figures 1 and 3;
  • Figure 6 is an illustration of a computer-readable medium upon which computer readable code may be stored.
  • Figures 7 and 8 are flow charts illustrating various operations which may, according to some examples, be performed by a UE and an eNB respectively operating within a network such as that of Figure 1. Detailed Description
  • the network l comprises one or more base stations or access points (eNodeBs, eNBs) 5-1 to 5-n (generally referred to by numeral 5). Only a small number of eNBs 5 are shown in FIG. 1, but a radio access network may typically comprise thousands of eNBs 5. Together, the eNBs 5 may provide radio coverage to one or more user equipment (UE) 4-1 to 4-n (generally referred to by numeral 4) over a wide geographical area.
  • UE user equipment
  • Each eNB 5 operates one or more cells, which are denoted in Figure 1, for illustrative purposes only, by the dashed circles 6-1 to 6-n or sectors thereof (generally referred to using numeral 6). Although most of the coverage areas of the cells are shown illustratively as circles in Figure 1, in reality, the coverage area of each cell depends on the transmission power and the directionality of the antenna (or antennas) by which the cell is operated. The coverage area of each cell may also depend on obstacles (such as buildings) which are in the vicinity of the eNB 5, carrier frequency and channel propagation characteristics etc.
  • the configuration of the coverage area of the cells 6 may be selected so as to serve UEs 4 in a particular area while not providing coverage to other areas. For instance, the
  • a configuration of a coverage area of a cell may be selected so as to provide coverage for an area in which users are commonly present while not providing coverage for areas in which users are seldom present.
  • the first cell 6-1 operated by the first cell is depicted as only a sector of a circle.
  • an eNB 5 may be configured to provide coverage (via a cell) up and down a road but not either side of the road.
  • a single eNB 5 may, in some examples, provide two or more cells.
  • a first cell 6 may be provided in a first direction from the eNB 5 while a second cell 6 may be provided in a different direction.
  • this is illustrated by the second eNB 5-1 which is shown as operating two different cells 6-2A and 6-2B.
  • the mobile telecommunications radio access network l may be, but is certainly not limited to, an Evolved Universal Terrestrial Radio Access (E-UTRA) network, which may sometimes be referred to as LTE Advanced network.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • the eNBs 4 and UEs 4 in the network 1 may be configured to communicate with one another using an OFDM -based access scheme, such as orthogonal frequency division multiple access (OFDMA) and/or single carrier frequency division multiple access (SC-FDMA).
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • OFDMA may be used for downlink communications
  • SC-FDMA single carrier frequency division multiple access
  • One or more of the UEs 4 may be configured for bi-directional communication with one or more of the eNBs 5.
  • the transmission of data from the eNB 5 to the UE 4 may be referred to as "downlink”. Transmission of data from the UE 4 to the eNB 5 may be referred to as "uplink".
  • the eNBs 5, or some other entity within the network 1, may be operable to schedule uplink timeslots (transmission time intervals) for the UEs 4 within the cell 6 operated by the eNBs 5. Scheduling information including the scheduled time slot and a number of physical resource blocks (PRBs), or simply resource blocks, allocated for the UE 4 is then communicated to the UE 4, for instance by the eNB 5 operating the cell.
  • the scheduling information may be transmitted as a message which may be referred to as an uplink scheduling grant.
  • the UE 4 comprises control apparatus 40 which is configured to control operation of other components forming part of the UE 4 thereby to enable transmission of data, via uplink, to the eNBs 5 as well as receipt of data from the eNBs 5, via downlink.
  • the control apparatus 40 may additionally be configured to cause performance of any other operations described herein with reference to the UEs 4, for instance with reference to Figure 2.
  • Example configurations of the control apparatus 40 and the UE 4 as a whole are discussed in more detail later in relation to Figure 4.
  • the eNBs 5 may comprise control apparatus 50 for enabling bi-directional communication with one or more UEs 4, including transmission of scheduling information.
  • the control apparatus 50 may additionally be configured to cause performance of any other operations described herein with reference to the eNBs 5, for instance with reference to Figure 3.
  • Example configurations of the control apparatus 50 and the eNB 5 as a whole are discussed in more detail later in relation to Figure 5.
  • the scheduling entity may take into account messages which are sent by the UE 4 to the serving eNB 5 and which indicate the amount of data that is currently present in the transmission buffer of the UE. These messages may be referred to as buffer status reports (BSRs). They may be sent periodically or in response to the occurrence of an event, for instance a particular condition being met.
  • BSRs buffer status reports
  • the transmit buffer may form part of a memory 402 (in Figure 4, it is denoted by 402-1B) of the control apparatus 40 or may form part of the transceiver circuitry405-2.
  • serving eNBs 5 may be configured, in some instances, to allocate resource blocks to a UE 4 even in the absence of a scheduling request or buffer status report being received from the UE. This may occur, for instance but not exclusively when, when the UE has particular (e.g. ultra-reliable low latency communication (URLLC)) requirements.
  • URLLC ultra-reliable low latency communication
  • the eNBs 5, or other scheduling entity may be configured to allocate more resource blocks for a particular UE 4 than are expected or estimated to be required by the UE 4 (for instance, based on the buffer status report received from that UE 4). This may be referred to as a pro-active grant.
  • a pro-active grant may enable the UE 4 to transmit more data than was indicated in the buffer status report (for instance when additional data arrives in the transmission buffer of the UE 4 after having sent a buffer status report but before performing an uplink transmission) without first having to send a new buffer status report including updated information. This may serve to reduce the latency within the network.
  • Instances in which additional resource blocks may be allocated to a UE 4 include, for example, situations in which all resource blocks in a particular shared transmission time interval would not be used if each UE 4 sharing the interval was allocated only based on their expected number of resource blocks.
  • the eNB control apparatus 50 or other scheduling entity may take into account (or use) previous information relating to, for instance, the data arrival patterns from the different UEs and/or the quality of service (QoS) of the default bearer setups at the different UEs etc. By taking such information into account, the eNB control apparatus 50 is able to allocate the additional resource blocks to those UEs 4 that are more likely to require and/or make best use of them.
  • QoS quality of service
  • URLLC ultra-reliable low latency communication
  • information regarding the number of resource blocks allocated for an uplink transmission by a UE 4 in a particular transmission time interval may be transmitted to the UE 4 as scheduling information.
  • the UE 4 may respond by transmitting data to the serving eNB 5 at the scheduled time.
  • the UE control apparatus 40 may be configured to determine a number of resource blocks that are required to transmit the data stored in the UEs transmission buffer.
  • the UE control apparatus 40 is configured to utilise the required number of resource blocks for the transmission, from the UE 4 to the eNB 5, of the data in the transmission buffer and to leave a remaining (non-zero) number of the allocated number of resource blocks unused. Put another way, the UE control apparatus 40 could be said to utilise only the required number of resource blocks of the allocated number of resource blocks to transmit the data stored in the transmission buffer.
  • no resource blocks (zero resource blocks) may be required by the UE. In such examples, no (zero) resource blocks may be used to transmit data and so all of the allocated resource blocks may be left unused.
  • Resource blocks being "left unused” may, in this context, be understood to mean that no signal is transmitted by the UE 4 during one or more portions of the transmission time interval allocated for the "unused" resource blocks. Leaving the resource blocks unused may contrast with padding the resource blocks, for instance with zeros or a padding buffer status report (a padding BSR), and then transmitting them to the eNB 5.
  • a padding buffer status report a padding BSR
  • the benefits of pro-active grants e.g. reduced latency
  • Inter-cell interference may degrade performance in neighbouring cells, and so by reducing it, performance of the overall network 1 may be improved.
  • the "used" resource blocks which include the data from the transmission buffer, may be passed as a transport block to the UE's PHY layer for transmission to the eNB 5 as a data packet.
  • the PHY layer may add CRC data as well a transmission header thereby to form the data packet.
  • the UE may be configured such that no data packet is sent when the number of resource blocks required by the UE is equal to zero.
  • the eNB control apparatus 50 may be configured to determine, upon receipt of the data packet from the UE 4 at the eNB 5 and prior to decoding the transport block of the data packet, whether all resource blocks of the number of resource blocks allocated to the UE for uplink transmission during a transmission time interval have been utilised. By determining whether or not all allocated resource blocks have been used, the eNB 5 is able to avoid the need to attempt to decode data for the "unused" resource blocks, if applicable.
  • the determination as to whether all resource blocks of the number of resource blocks allocated to the UE 4 for uplink transmission during a transmission time interval have been utilised may be performed using blind detection on the relevant uplink channel, e.g. the physical shared uplink channel (PUSCH), during the transmission time interval allocated for the UE 4.
  • An example of a suitable form of blind detection may be energy detection on the relevant resource blocks.
  • Blind detection may be similar to discontinuous transmission (DTX) detection. In the current advanced LTE standard, this process is already applied by eNBs 5 to determine whether or not physical downlink control channel (PDCCH) uplink grant transmissions were received by the relevant UE. Specifically, the eNB 5 performs energy detection in the allocated PUSCH during the allocated
  • PDCCH physical downlink control channel
  • the performance of blind detection on the uplink channel during the transmission time interval may enable the eNB 5 to determine the number and/or an identity of the resource blocks utilised by the UE 4. Put another way, it may enable the determination as to how many and/or which of the allocated resource blocks are unused by the UE.
  • the blind detection may be performed during the allocated transmission time interval based on a minimum number of resource blocks N m i n which the UE 4 is expected to utilise. This may be determined by the eNB 5 based on, for instance, one or more of the most recent buffer status report received from the UE 4, the number of bits transmitted by the UE 4 in previous uplink transmissions since the transmission of the buffer status report by the UE, and the allocated MCS for the UL transmission.
  • the blind detection during the transmission time interval may be performed based on the minimum number of resource blocks which the UE 4 is expected to utilise and a pre-defined order in which the UE 4 is required to make use of the allocated resource blocks (or, put another way, a pre-defined order in which the UE 4 is required to read data from the buffer into the resource blocks).
  • the UE 4 may be configured to utilise the resource blocks as required from the lowest numbered resource block upwards or from the highest numbered resource block downwards.
  • the UE 4 may be preconfigured to start utilising the resource blocks from the middle block of the allocation and filling them with data from the transmission buffer alternately either side of the middle resource block.
  • the eNB 5 knows the minimum number of resource blocks that the UE 4 is expected to use as well as the order in which the resource blocks are to be filled with data, the duration or number of instances for which blind detection needs to be performed in order to determine which resource blocks have been utilised can be reduced. For instance, if the resource blocks are utilised sequentially from either end, the eNB 5 may simply perform blind detection in respect of resource blocks between N m i n and the allocated number of resource blocks Naiiocated and may not need to perform blind detection in respect of the resource blocks lower than N m i n .
  • the worst-case blind detection may be performed in respect of only the seventh to eleventh resource blocks (five in total). It will therefore be understood that the worst-case number of resource blocks for which blind detection may be performed when the blocks are used sequentially from one end of the allocation may be expressed generally as Naiiocated
  • the eNB 5 may be configured to take an average of signal energy over all resource blocks in excess of the minimum expected number of resource blocks N m i n in order to determine which resource blocks have been used by the UE 4. For instance, continuing with the example in which N m i n is equal to 6, the eNB may take an average signal energy of:
  • the eNB 5 may be configured to instruct the UE 4 as to the pre-defined order in which the UE 4 is required to make use of the allocated resource blocks. For instance, this may be indicated along with the scheduling information, e.g. in the uplink scheduling grant.
  • the eNB 5 may be configured to select the order from a plurality of available pre-defined orders (e.g., left-to-right, right-to-left, from the middle alternately outwards). An indexing system for the available pre-defined orders which is known to both the eNB 5 and UE 4 may be utilised thereby to indicate the order in which the UE 4 is required to use the allocated resource blocks.
  • the selection of the order by the eNB 5 may be made so as to improve efficiency and/or performance of the network.
  • the UE 4 may be configured to transmit reference signals, which may be similar to Sounding Reference Signals (SRS), based on which the eNB 5 may perform per-resource block interference measurements. Or put another way, the eNB 5 may be able to determine the interference at times corresponding to the transmission times of each resource block. Based on this determined interference, the eNB 5 may select the pre-defined order which would result in the best performance, for instance, use of a maximum transport block size (TBS) or a minimum number of resource blocks to transmit the data in the UE's transmission buffer.
  • TBS maximum transport block size
  • the pre-defined order may only be signalled to the UE 4 in the event that the eNB 5 has allocated more than the minimum number of resource blocks (e.g. has provided a proactive UL grant).
  • the eNB 5 may be configured to perform blind detection only in the event that the eNB 5 has allocated more than the minimum number of resource blocks to the UE. In this way, the use of additional computational resources required to perform the blind detection may be avoided unless it is necessary.
  • the UE 4 may be configured to transmit signalling data that is decodable separately from the used resource blocks, thereby to indicate to the eNB 5 whether all allocated resource blocks have been used.
  • This separately decodable signalling data may be provided, for example, in the transmission header.
  • the separately decodable signalling data may take the form of a flag, for instance a single bit flag (i.e. "1" or "o") which indicates whether or not all allocated resource blocks have been utilised.
  • the signalling data may include information allowing the eNB 5 to determine which resource blocks (i.e. the identities) have been used.
  • the signalling data may indicate how many resource blocks of the allocation have been used. This, taken in combination with a known pre-defined order of use of the resource blocks, allows the eNB 5 to determine which resource blocks are used and which are unused.
  • the UE 4 may be configured to explicitly indicate which resource blocks are used and/or have been left unused.
  • the use of signalling data as described above may obviate the need for the eNB 5 to perform blind detection.
  • the order and/or identity of which resource blocks of an allocation to use may be determined and indicated to the UE 4 by the eNB 5.
  • the UE 4 may be configured to determine the order autonomously. For instance, the UE 4 may select the resource blocks to use (e.g. from lowest upwards, from highest downwards or from the middle alternatively either side) so as to obtain the largest frequency-selective scheduling gains.
  • the resource blocks of the allocation may be selected by the UE so as to minimize the number of resource blocks used.
  • the ability of the UE 4 to determine autonomously which resource blocks to use may depend on how much information regarding channel conditions is available to the UE 4-
  • the UE 4 may be unable to change the modulation and coding scheme (MCS) indicated by the eNB 5 in an uplink scheduling grant.
  • MCS modulation and coding scheme
  • the UE 4 may be configured to select, if appropriate, an MCS that is different to that indicated by the eNodeB.
  • the MCS selected by the UE may then be signalled to the eNB by the UE 4 as part of the separately decodable signalling data. This signalling data may then be decoded and utilised by eNB 5 when decoding the data carried by the utilised number of the allocated resource blocks.
  • the MCS allocated by the eNB 5 may have been selected on the basis of the over- dimensioned number of resource blocks, for instance in addition to a measured SINR for the UE. However, when a UE 4 does not require all the resource blocks that it has been allocated, the MCS selected by the eNB 5 may no longer be the most suitable. As such, the UE 4 may be configured to select an MCS which is more suitable. For instance, in some examples, the UE 4 may select the highest possible MCS and lowest number of resource blocks. Alternately, the UE 4 may select the lowest possible MCS to meet a target block error rate (BLER) while still using all the allocated resource blocks.
  • BLER target block error rate
  • the MCS selected by the UE may typically be less than or equal to the MCS indicated by the eNB, but may be selected such that all the bits in the UE's transmission buffer fit within the number of allocated resource blocks.
  • the UE 4 may thus be configured to use the lowest MCS which allows all the data in the transmission buffer to be transmitted within the allocated number of resource blocks.
  • Figure 2 is a flow chart illustrating various operations which may be performed by a UE 4 operating within the network of Figure 1. As will be appreciated, some or all of the operations illustrated in Figure 2 may correspond with or relate to operations described above with reference to Figure 1.
  • the UE control apparatus 40 determines the amount of data that is awaiting transmission in the UE transmission buffer. This amount of data is indicative of the minimum number of resource blocks N m i n ) that are expected to be required in the UE's next uplink transmission. As will be appreciated, in some examples, there may be no data for transmission and so the expected number of resource blocks may be zero.
  • the UE control apparatus 40 may cause transmission of a message, which may be referred to as a buffer status report (BSR), which includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N m i n ).
  • BSR buffer status report
  • This message may be a MAC control element, for instance an LTE MAC control element similar to LTE BSRs.
  • BSRs may be sent intermittently, for instance periodically or in response to the occurrence of certain events.
  • multiple uplink transmissions may be performed by the UE 4 between instances of transmitting a buffer status report.
  • the UE control apparatus 40 receives the uplink scheduling
  • the scheduling information includes information indicative of the allocated number of resource blocks (N a iiocated). It may also include an indication of the transmission time interval (TTI) for the allocated uplink transmission slot.
  • the scheduling information may further include an indication of the modulation and coding scheme (MCS) that should be used by the UE 4.
  • MCS modulation and coding scheme
  • the UE control apparatus 40 may proceed to operation S2.5 in which data from the transmission buffer is transferred into all of the allocated resource blocks.
  • the UE control apparatus 40 may proceed to operation S2.6.
  • the UE control apparatus 40 may determine an order in which to fill the required ones of the allocated resource blocks. As discussed above, this may be defined by the eNB 5 and indicated to the UE 4, for instance as part of the scheduling information. In other examples, the UE control apparatus 40 may determine the order autonomously, for instance to optimise performance. In other examples, the UE 4 may be pre-configured to read data into the resource blocks in a single pre-defined order. In such, examples, operation S2.6 may be omitted.
  • operation S2.7 may be performed.
  • the UE 4 transfers data from the transmission buffer into the required number of resource blocks. This may be performed in the order determined in operation S2.6 or an order which the UE 4 is preconfigured to use. Having transferred all the data in transmission buffer into the required resource blocks, the remainder of the allocated resource blocks are left unused.
  • a header and CRC information are added to the transport block created in operation S2.5 or operation S2.7 thereby to form a data packet.
  • the header may include the
  • independently decodable signalling data which may indicate one or more of: whether all allocated resource blocks have been used, how many resource blocks have been used, which resource blocks have been used, an order in which resource blocks have been used, and the coding and modulation scheme that has been used by the UE.
  • the data packet is caused to be transmitted to the eNB 5.
  • the signal energy may drop to zero (or some other relatively low value) in the frequencies corresponding to the unused resource blocks.
  • the UE control apparatus 40 may return to operation S2.1.
  • the transmission of a buffer status report may not be performed between each uplink transmission.
  • operation S2.2 may be omitted from the flow of operations depicted in Figure 2.
  • Figure 3 is a flow chart illustrating various operations which may be performed by an eNB 5 operating within the network of Figure 1. As will be appreciated, some or all of the operations illustrated in Figure 3 may correspond with or otherwise relate to operations described above with reference to Figure 1.
  • the eNB 50 may receive a message from a one of the UEs 4 it is currently serving.
  • the message which may be referred to as a buffer status report (BSR)
  • BSR buffer status report
  • This message may be a MAC control element, for instance an LTE MAC control element similar to an LTE BSR.
  • the eNB control apparatus 50 may determine whether to grant the UE 5 more uplink resource blocks that are indicated as being required by the received message, N m i n .
  • the eNB may make an estimation of N m i n using one or more of: information in a previously-received BSR, an amount of data that is scheduled to be transmitted by the UE and the estimated SINR for the UE (which may be determined based on "acks" and "nacks" passed between the UE and the eNB).
  • additional resource blocks may be allocated to a UE if, for example, all resource blocks in a particular shared transmission time interval would not be used if each UE sharing the interval was allocated only based on their expected number of resource blocks Nmin.
  • the eNB control apparatus 50 may take into account (or use) previous information relating to, for instance, the data arrival patterns from the different UEs and/or the quality of service (QoS) of the default bearer setups at the different UEs etc. By taking such information into account, the eNB control apparatus 50 is able to allocate the additional resource blocks to those UEs 4 that are more likely to require and/or make best use of them.
  • QoS quality of service
  • certain UEs in a particular cell may have default bearer setups with ultra-reliable low latency communication (URLLC) requirements.
  • the eNB control apparatus 50 may allocate an additional number of resource blocks to a particular UE even if the eNB 5 could allocate all of the resource blocks of the cell in the particular transmission time interval, based solely on the expected/ estimated resource block requirements N mm of each of the UEs 4 in the cell.
  • the allocation of additional resource blocks to UEs 4 having URLLC requirements may enable those UEs 4 to achieve those requirements.
  • the eNB control apparatus 50 may proceed to operation S3.3.
  • the eNB control apparatus 50 causes transmission to the UE 4 of scheduling information (which may be an uplink scheduling grant) which indicates an allocated number of resource blocks, Naiiocated, that is less than or equal to the number of resource blocks that is expected to be required, Nmm.
  • the scheduling information may additionally include information indicative of the transmission time interval as well as the modulation and coding scheme that is to be used by the UE 4 during the uplink.
  • control apparatus 50 may proceed to operation S3.4.
  • the eNB control apparatus 50 may, in some examples, determine an order in which the UE 4 should make use of the allocated resource blocks. As discussed above with reference to Figure 1, the order may be determined so as to maximise performance of the system.
  • the eNB control apparatus 50 causes transmission to the UE 4 of scheduling information (which may be an uplink scheduling grant) which indicates an allocated number of resource blocks, Naiiocated, that is greater than the number of resource blocks that is expected to be required, Nmm.
  • scheduling information may additionally include an indication of the order in which the UE 4 is required to use the allocated resource blocks.
  • the scheduling information may additionally include information indicative of the transmission time interval as well as the modulation and coding scheme that is to be used by the UE 4 during the uplink.
  • the eNB 5 in operation S3.6 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S3.5.
  • the eNB 5 in operation S3.7 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S3.3.
  • the eNB control apparatus 50 may proceed to operation S3.8 in which blind detection may be performed in respect of the received packet, thereby to enable the eNB 5 to determine which of the allocated resource blocks have been utilised by the UE 5.
  • the eNB control apparatus 50 may decode, separately from the transport block of the data packet, signalling information which indicates among other things whether all of the allocated resource blocks have been utilised and/or which of the allocated resource blocks have been utilised.
  • the signalling data may be included in the header of the received data packet.
  • the eNB control apparatus 50 may determine, in operation S3.9, whether the entire allocation of resource blocks has been utilised. If it is determined that all of the resource blocks have been utilised, the eNB control apparatus 50 may proceed to operation S3.11 in which the data received during all of the resources allocated resource blocks is decoded.
  • the eNB control apparatus 50 may proceed to operation S3.10 in which the resource blocks which have been used are identified. This may be performed on the basis of the blind detection or the signalling data, in conjunction with knowledge of an order in which the UE 4 has used the resource blocks of the allocation. As discussed above with respect to Figure 1, the order in which the resource blocks are used may, in some examples, be selected autonomously by the UE 4 and indicated to the eNB 5 in the separately decodable signalling information. Finally, in operation S3.11, the eNB control apparatus 50 may decode only the data received during the intervals corresponding to the used resource blocks.
  • operations S3.8 to S3.10 may not be performed, as such operations may not be necessary. Instead, after operation S3.7, the eNB control apparatus 50 may proceed directly to operation S3.11 in which data received during intervals corresponding to all resource blocks is decoded.
  • the UE control apparatus 40 determines the amount of data that is awaiting transmission in the UE transmission buffer. As will be appreciated, this amount of data (which may be zero) is indicative of the minimum number of resource blocks that are expected to be required in the UE's next uplink transmission.
  • the UE control apparatus 40 may cause transmission of a buffer status report (BSR), which includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N m i n ).
  • BSR buffer status report
  • This message may be a MAC control element, for instance an LTE MAC control element similar to LTE BSRs.
  • BSRs may be sent intermittently, for instance periodically or in response to the occurrence of certain events.
  • multiple uplink transmissions may be performed by the UE 4 between instances of transmitting a buffer status report.
  • the UE control apparatus 40 receives the uplink scheduling
  • the scheduling information includes information indicative of the allocated number of resource blocks (N a iiocated). It also includes an indication of the modulation and coding scheme (MCS), for instance in the form of an MCS index. It may also include an indication of the transmission time interval (TTI) for the allocated uplink transmission slot.
  • MCS modulation and coding scheme
  • TTI transmission time interval
  • the UE control apparatus 40 may proceed to operation S7.5 in which data from the transmission buffer is transferred into all of the allocated resource blocks in accordance with the indicated MCS. Subsequently, in operation S7.8, a header and CRC data are added to the transport block including the allocated resource blocks, thereby to form a data packet which is caused to be transmitted in operation S7.9.
  • the UE control apparatus 40 may proceed to operation S7.6.
  • the UE control apparatus 40 may select a modulation and coding scheme that is different to that indicated by the eNB.
  • the MCS indicated by the eNB (which was selected on the basis of the over-dimensioned number of resource blocks) may no longer be the most appropriate.
  • the UE 4 may select the highest possible MCS and lowest number of resource blocks. Alternately, the UE 4 may select the lowest possible MCS to meet lower target block error rate (BLER) while still using all the resource blocks allocated by the eNB in the uplink scheduling grant.
  • BLER target block error rate
  • MCS selected by the UE may be to be equal to or lower than that indicated by the eNB, but may be selected such that all the bits in the UE's transmission buffer would fit within the number of allocated resource blocks.
  • the UE 4 may be configured to use the lowest MCS which allows all the data in the transmission buffer to be transmitted within the number of resource blocks allocated by the eNB 5.
  • the UE in operation S7.7 reads the data from its buffer into the resource blocks in accordance with the determined MCS. Subsequently, in operation S7.8, a header and CRC information are added to the transport block created in operation S7.7 thereby to form a data packet.
  • the header may include the independently decodable signalling data, which indicates (for instance using an MCS index) the coding and modulation scheme that has been used by the UE 4.
  • the data packet After formation of the data packet, in operation S7.9, the data packet is caused to be transmitted to the eNB 5.
  • the UE control apparatus 40 may return to operation S7.1.
  • the transmission of a buffer status report may not be performed between each uplink transmission.
  • operation S7.2 may be omitted from the flow.
  • Figure 8 is a flow chart illustrating various operations which may be performed by an eNB within a network such as that of Figure 1 in examples in which the UE is operable to determine an alternative modulation and coding scheme (MCS) to that specified by the eNB.
  • MCS modulation and coding scheme
  • the eNB 50 may receive a message from one of the UEs 4 that it is currently serving.
  • the message which may be referred to as a buffer status report (BSR)
  • BSR buffer status report
  • This message may be a MAC control element, for instance an LTE MAC control element similar to an LTE BSR.
  • Operation S8.1 may be substantially the same as operation S3.1 and similarly to operation S3.1 may, in some examples, be omitted.
  • the eNB control apparatus 50 may determine whether to grant the UE 5 more uplink resource blocks that are indicated as being required by the received message, N m i n .
  • the eNB may make an estimate of N m i n using one or more of: information in a previously-received BSR, an amount of data that is scheduled to be transmitted by the UE and the estimated SINR for the UE, which may be determined based on "acks" and "nacks" passed between the UE and the eNB.
  • Operation S8.2 may be substantially the same as operation S3.2 described with reference to Figure 3. However, in addition to determining whether to over-provision resource blocks for a particular UE, the eNB controller (or other scheduling entity) may be determined whether to over-provision resource blocks for a particular UE.
  • the eNB control apparatus 50 may in operation S8.3 cause transmission of an uplink scheduling grant which indicates the allocated number of resource blocks such that N a iiocated> N m i n .
  • the uplink scheduling grant also indicates the MCS to be used by the UE 4 for its uplink transmission.
  • the uplink scheduling grant may additionally indicate the TTI to be used by the UE 4.
  • the eNB control apparatus 50 may in operation S8.4 cause transmission of an uplink scheduling grant which indicates the allocated number of resource blocks such that Naiiocated ⁇ N m i n .
  • the uplink scheduling grant also indicates the MCS to be used by the UE for its uplink transmission.
  • the uplink scheduling grant may additionally indicate the TTI to be used by the UE 4.
  • the eNB 5 in operation S8.5 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S8.3.
  • the eNB 5 in operation S8.9 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S8.4.
  • the eNB control apparatus 50 may proceed to operation S8.6 in which the eNB control apparatus 50 decodes, separately from the transport block of the data packet, the separately decodable signalling information.
  • the signalling information may indicate whether the UE has utilised an MCS which is different to that indicated by the eNB in the uplink grant.
  • the indication as to whether the UE has utilised a different UE may include a simple flag (e.g. 1 or o, yes or no) and/or may indicate the MCS (e.g. via an MCS index) which has been used by the UE 4.
  • the eNB controller may (in operation S8.8) decode the resource blocks of the received data packets on the basis of the new MCS utilised by the UE 4. If, on the other hand, a negative determination is reached in operation S8.7 (put another wat, it is determined that the MCS specified by eNB has been used by the UE), operation S8.10 is performed in which the resource blocks are decoded in accordance with the MCS originally specified by the eNB in the uplink grant.
  • the eNB control apparatus may subsequently proceed directly to operation S8.10 in which the resource blocks are decoded in accordance with the MCS originally specified by the eNB.
  • the decoding of signalling data similarly to operation S8.6 may be omitted (as may operation S.7). This is because, as the eNB has not allocated additional resource blocks to the UE 4, it can be confident that the MCS specified in the uplink grant has been used by the UE.
  • Figure 4 is a schematic illustration of an example configuration of one or more of the UEs 4 depicted in Figure 1, which may be used for communicating with the eNBs 5 via a wireless interface.
  • the UE 4 may be any device capable of at least sending or receiving radio signals to or from the eNBs 5 and of performing operations as described above with respect to Figures 1, 23, 7 and 8.
  • the UE 4 may communicate via an appropriate radio interface arrangement 405 of the UE 4.
  • the interface arrangement 405 may be provided for example by means of a radio part 405-2 (e.g. a transceiver) and an associated antenna arrangement 405-1.
  • the antenna arrangement 405-1 may be arranged internally or externally to the UE 4.
  • the UE 4 comprises control apparatus 40 which is operable to control the other components of the UE 4 in addition to performing any suitable combinations of the operations described in connection with UE 4 with reference to Figures 1, 2 and 3 (where applicable).
  • the control apparatus 40 may comprise processing apparatus 401 and memory 402.
  • Computer-readable code 402-2A may be stored on the memory, which when executed by the processing apparatus 401, causes the control apparatus 40 to perform any of the operations described herein in relation to the UE 4.
  • the memory may include a transmission buffer 402-1B.
  • Example configurations of the memory 402 and processing apparatus 401 will be discussed in more detail below
  • the UE 4 may be, for example, a device that does not need human interaction, such as an entity that is involved in Machine Type Communications (MTC).
  • MTC Machine Type Communications
  • the UE 4 may be a device designed for tasks involving human interaction such as making and receiving phone calls between users, and streaming multimedia or providing other digital content to a user.
  • Non-limiting examples include a smart phone, and a laptop
  • the UE 4 is a device designed for human interaction, the user may control the operation of the UE 4 by means of a suitable user input interface UII 404 such as key pad, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • UII 404 such as key pad, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • a display 403, a speaker and a microphone may also be provided.
  • the UE 4 may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • FIG. 5 is a schematic illustration of an example configuration of one or more the eNBs 5 depicted in Figure 1, which may be used for communicating with the UEs 4 via a wireless interface.
  • the eNB 5, which may be referred to a base station or access point (AP) comprises a radio frequency antenna array 501 configured to receive and transmit radio frequency signals.
  • AP access point
  • the eNB 5 in Figure 5 is shown as having an array 501 of four antennas, this is illustrative only. The number of antennas may vary, for instance, from one to many hundreds.
  • the eNB 5 further comprises radio frequency interface circuitry 503 configured to interface the radio frequency signals received and transmitted by the antenna 501 and a control apparatus 50.
  • the radio frequency interface circuitry 503 may also be known as a transceiver.
  • the apparatus 50 may also comprise an interface 509 via which, for example, it can communicate (e.g. via X2 messages) with other network elements such as the other eNBs 5.
  • the eNB control apparatus 50 may be configured to process signals from the radio frequency interface circuitry 503, control the radio frequency interface circuitry 503 to generate suitable RF signals to communicate information to the UEs 4 via the wireless communications link, and also to exchange information with other network elements 5 via the interface 509. .
  • the control apparatus 50 may comprise processing apparatus 502 and memory 504.
  • Computer-readable code 504-2A may be stored on the memory 504, which when executed by the processing apparatus 502, causes the control apparatus 50 to perform any of the operations assigned to the eNBs 5 and described with reference to any of Figures 1 to 5, 7 and 8
  • the apparatuses 4, 5 shown in each of FIGS. 4 and 5 described above may comprise further elements which are not directly involved with processes and operations in respect which this application is focussed.
  • control apparatuses 40, 50 may comprise processing apparatus 401, 502
  • the memory 402, 504 has computer readable instructions 402-2A, 504-2A stored thereon, which when executed by the processing apparatus 401, 502 causes the control apparatus 40, 50 to cause performance of various ones of the operations described with reference to Figures 1 to 5.
  • the control apparatus 40, 50 may in some instance be referred to, in general terms, as "apparatus".
  • the processing apparatus 401, 502 may be of any suitable composition and may include one or more processors 401A, 502A of any suitable type or suitable combination of types.
  • the processing apparatus 401, 502 may be a programmable processor that interprets computer program instructions 402-2A, 504-2A and processes data.
  • the processing apparatus 401, 502 may include plural programmable processors.
  • processing apparatus 401, 502 may be, for example, programmable hardware with embedded firmware.
  • the processing apparatus 401, 502 may be termed processing means.
  • the processing apparatus 401, 502 may alternatively or additionally include one or more Application Specific Integrated Circuits (ASICs).
  • ASICs Application Specific Integrated Circuits
  • processing apparatus 401, 502 may be referred to as computing apparatus.
  • the processing apparatus 401, 502 is coupled to the memory (which may be referred to as one or more storage devices) 402, 504 and is operable to read/write data to/from the memory 402, 504.
  • the memory 402, 504 may comprise a single memory unit or a plurality of memory units, upon which the computer readable instructions (or code) 402- 2A, 504-2A is stored.
  • the memory 402, 504 may comprise both volatile memory 402-1 and non-volatile memory 402-2.
  • the computer readable instructions/program code 402-2A, 504-2A may be stored in the non-volatile memory 402-2, 504-2 and may be executed by the processing apparatus 401, 502 using the volatile memory 402-1, 504-1 for temporary storage of data or data and instructions.
  • the transmission buffer 402-1B of the UE 4 may be constituted by volatile memory 402-1 of the UE control apparatus 40.
  • volatile memory examples include RAM, DRAM, and SDRAM etc.
  • non-volatile memory examples include ROM, PROM, EEPROM, flash memory, optical storage, magnetic storage, etc.
  • the memories in general may be referred to as non-transitory computer readable memory media.
  • the term 'memory' in addition to covering memory comprising both non-volatile memory and volatile memory, may also cover one or more volatile memories only, one or more non-volatile memories only, or one or more volatile memories and one or more nonvolatile memories.
  • the computer readable instructions/program code 402-2A, 504-2A may be preprogrammed into the control apparatus 20. Alternatively, the computer readable instructions 402-2A, 504-2A may arrive at the control apparatus 40, 50 via an
  • the computer readable instructions 402-2A, 504-2A may provide the logic and routines that enables the entities
  • Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic.
  • the software, application logic and/or hardware may reside on memory, or any computer media.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
  • a "memory" or “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • references to, where relevant, "computer-readable storage medium”, “computer program product”, “tangibly embodied computer program” etc., or a “processor” or “processing apparatus” etc. should be understood to encompass not only computers having differing architectures such as single/multi-processor architectures and sequencers/parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices and other devices.
  • References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device as instructions for a processor or configured or configuration settings for a fixed function device, gate array, programmable logic device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un aspect de la présente invention concerne un procédé consistant à déterminer un nombre de blocs de ressources nécessaire pour transmettre des données mémorisées dans un tampon de transmission d'un équipement d'utilisateur et, si le nombre nécessaire de blocs de ressources est inférieur à un nombre de blocs de ressources ayant été attribués à l'équipement d'utilisateur pour une transmission en liaison montante dans un intervalle de temps de transmission, à utiliser le nombre nécessaire de blocs de ressources pour une transmission depuis l'équipement d'utilisateur vers un nœud B évolué des données dans le tampon de transmission et à laisser un nombre restant du nombre attribué de blocs de ressources inutilisé.
PCT/FI2017/050321 2016-05-02 2017-04-28 Utilisation d'attributions de liaison montante WO2017191360A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201641015271 2016-05-02
IN201641015271 2016-05-02

Publications (1)

Publication Number Publication Date
WO2017191360A1 true WO2017191360A1 (fr) 2017-11-09

Family

ID=58739065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2017/050321 WO2017191360A1 (fr) 2016-05-02 2017-04-28 Utilisation d'attributions de liaison montante

Country Status (1)

Country Link
WO (1) WO2017191360A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193147A1 (fr) * 2022-04-06 2023-10-12 Oppo广东移动通信有限公司 Procédé et appareil d'exclusion de ressources, dispositif, support de stockage et produit-programme
WO2024097133A1 (fr) * 2022-11-04 2024-05-10 Apple Inc. Sélection de ressources de domaine temporel

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012022369A1 (fr) * 2010-08-16 2012-02-23 Nokia Siemens Networks Oy Rapport d'état de mémoire tampon vide provenant d'un équipement utilisateur dans des transmissions de liaison montante
WO2015099585A1 (fr) * 2013-12-23 2015-07-02 Telefonaktiebolaget L M Ericsson (Publ) Signaler des attributions de planification de liaison montante ignorées

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012022369A1 (fr) * 2010-08-16 2012-02-23 Nokia Siemens Networks Oy Rapport d'état de mémoire tampon vide provenant d'un équipement utilisateur dans des transmissions de liaison montante
WO2015099585A1 (fr) * 2013-12-23 2015-07-02 Telefonaktiebolaget L M Ericsson (Publ) Signaler des attributions de planification de liaison montante ignorées

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL: "Latency improvement comparison", 3GPP DRAFT; R2-094825 (LATENCY IMPROVEMENTS COMPARISON), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Shenzhen, China; 20090818, 18 August 2009 (2009-08-18), XP050352833 *
NOKIA NETWORKS: "Latency Reduction Rel-10 discussion recaps", vol. RAN WG2, no. Fukuoka, Japan; 20150525 - 20150529, 15 May 2015 (2015-05-15), XP050970677, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_90/Docs/> [retrieved on 20150515] *
T-MOBILE: "UL resource pre-allocation to reduce U-Plane RTT latency", 3GPP DRAFT; R2-092894_PRE-ALLOCATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. San Francisco, USA; 20090427, 27 April 2009 (2009-04-27), XP050340700 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193147A1 (fr) * 2022-04-06 2023-10-12 Oppo广东移动通信有限公司 Procédé et appareil d'exclusion de ressources, dispositif, support de stockage et produit-programme
WO2024097133A1 (fr) * 2022-11-04 2024-05-10 Apple Inc. Sélection de ressources de domaine temporel

Similar Documents

Publication Publication Date Title
US11595973B2 (en) Method for processing uplink control information and terminal
EP3809781B1 (fr) Procédés et appareil permettant de planifier en liaison montante
KR102341820B1 (ko) 무선 통신 시스템에서 채널 액세스를 위한 장치 및 방법
US20190281491A1 (en) Quality of service (qos) congestion control handling
EP4050811A1 (fr) Procédé et appareil pour la configuration d&#39;un faisceau par défaut pour la communication coopérative en réseau
CN106507494B (zh) 基于分组的m2m通信上行半静态调度方法
EP3861807B1 (fr) Procédés de sélection de ressources pour transmission multi-flux de liaison latérale dans des systèmes de communication sans fil et appareils associés
EP4113921A1 (fr) Transmission d&#39;information de commande de liaison montante (uci)
CN110140407B (zh) 用于发送下行链路控制信息的方法和设备
CN112237047B (zh) 传输块大小的配置
EP3606231B1 (fr) Procédé et appareil de transmission sans planification
US11051324B2 (en) Multi-bit scheduling request
US20220132469A1 (en) Receiver assisted sidelink resource allocation using an adaptive threshold
EP3143804B1 (fr) Transmission discontinue pour un noeud de réseau de téléphone mobile
US20210345346A1 (en) Resource allocation method and device
CN116349334A (zh) 用于侧链路传输的资源分配技术，以及基于侧链路通信可靠性的资源分配技术之间的动态选择
WO2021080486A1 (fr) Programmation semi-persistante pour services multiples
WO2018127100A1 (fr) Procédé de contrôle de puissance de liaison montante et appareil de communication
JP2022540974A (ja) 通信方法、通信デバイス及びコンピュータプログラム
CN109792692B (zh) 针对短tti的上行链路功率优先化
WO2017191360A1 (fr) Utilisation d&#39;attributions de liaison montante
WO2013139259A1 (fr) Procédé et système de codage de transmission dans un système d&#39;accès à multiplexage par répartition orthogonale de la fréquence (ofdm)
EP3932134B1 (fr) Dispositif de communication, équipement d&#39;infrastructure et procédés associés
WO2018002424A1 (fr) Procédés et appareils relatifs à des émissions en liaison montante
US20240064564A1 (en) Congestion Control for Sidelink Transmissions

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17724599

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17724599

Country of ref document: EP

Kind code of ref document: A1