WO2019154106A1 - Grant-based uplink transmission - Google Patents

Grant-based uplink transmission Download PDF

Info

Publication number
WO2019154106A1
WO2019154106A1 PCT/CN2019/073099 CN2019073099W WO2019154106A1 WO 2019154106 A1 WO2019154106 A1 WO 2019154106A1 CN 2019073099 W CN2019073099 W CN 2019073099W WO 2019154106 A1 WO2019154106 A1 WO 2019154106A1
Authority
WO
WIPO (PCT)
Prior art keywords
suspension
indication
allocated
resource
resources
Prior art date
Application number
PCT/CN2019/073099
Other languages
English (en)
French (fr)
Inventor
Guang Liu
Original Assignee
Jrd Communication (Shenzhen) Ltd
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 Jrd Communication (Shenzhen) Ltd filed Critical Jrd Communication (Shenzhen) Ltd
Priority to CN201980011306.8A priority Critical patent/CN111801975B/zh
Publication of WO2019154106A1 publication Critical patent/WO2019154106A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • 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

Definitions

  • the following disclosure relates to systems for grant-based uplink transmission in cellular wireless systems, and in particular to resource sharing in such systems.
  • Wireless communication systems such as the third-generation (3G) of mobile telephone standards and technology are well known.
  • 3G standards and technology have been developed by the Third Generation Partnership Project (3GPP) .
  • 3GPP Third Generation Partnership Project
  • the 3 rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications.
  • Communication systems and networks have developed towards a broadband and mobile system.
  • UE User Equipment
  • RAN Radio Access Network
  • CN Core Network
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • 5G or NR new radio
  • NR is proposed to utilise an Orthogonal Frequency Division Multiplexed (OFDM) physical transmission format.
  • OFDM Orthogonal Frequency Division Multiplexed
  • Cellular wireless networks may provide a range of services to UEs such that a service suitable for the type of data being transmitted can be selected.
  • Ultra Reliable Low Latency Communication (URLLC) and some Machine Type Communication (MTC) services may require very short latency (less than 1 ms) and high reliability (packet loss rate of less than 10 -5 ) .
  • Data transmitted over such services is typically characterised by small data packets which arrive in an infrequent and sporadic manner.
  • Figure 1 shows example communications between a UE and base station (gNB) for (a) grant-based, and (b) grant-free uplink transmissions.
  • a Scheduling Request (SR) message is transmitted (step 100) .
  • the base station allocates uplink resources for the data and transmits an indication of those resources at step 101.
  • the UE then utilises those resources at step 102 to transmit the data to the base station.
  • Inerrant in such systems is a latency of at least one Round Trip Time (RTT) before transmission can be started.
  • RTT Round Trip Time
  • the round-trip latency can be avoided by using a grant-free system as shown in Figure 1 (b) .
  • uplink resources are pre-allocated such that when a packet arrives at step 103 it can be transmitted using the next available resources at step 104.
  • resources are allocated to each UE, but since there is only infrequently data for transmission the allocated resources are likely to be unused. Resource efficiency is thus poor as reserved resources are not utilised. Resources can be allocated on a shared basis, but this unavoidably leads to potential collisions between the UEs sharing the resources. The greater the degree of sharing (giving higher efficiency) the higher the probability of a collision. A collision probability of 10 -3 corresponds to channel usage of 4.5%, meaning 95.5% of resources are unused.
  • a method of uplink data transmission from a user equipment (UE) to a base station in a cellular wireless network comprising the steps of transmitting via a wireless link a scheduling request from a UE to a base station to transmit data; receiving at the base station the request and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources utilised by other UEs; and transmitting via a wireless link from the base station a downlink indication, the downlink indication comprising at least one resource indication field, each of which includes an indication of the resource used by the received scheduling request; and/or at least one suspension indication field each of which includes an indication for UEs utilising the overlapping resources to suspend transmissions.
  • the downlink indication comprising at least one resource indication field, each of which includes an indication of the resource used by the received scheduling request; and/or at least one suspension indication field each of which includes an indication for UEs utilising the overlapping resources to suspend transmissions.
  • the resource indication field may further comprise an indication of the allocated uplink resources.
  • the method may further comprise a configuration phase comprising the step of the base station allocating at least one scheduling request resource to the UE, each scheduling request resource having a corresponding resource index; and/or at least one uplink resource to the UE for data transmission.
  • the method may further comprise transmitting from the base station to the UE an indication of the scheduling request resource and/or uplink resource allocated to that UE.
  • Each allocated scheduling request resource may be allocated a scheduling request resource index, and the indications of scheduling request resources comprises the scheduling request resource index.
  • Each scheduling request resource may comprise a unique combination of time, frequency, and sequence resources.
  • At least one allocated scheduling request resource may be also allocated to a further UE which is in communication with the base station.
  • At least one allocated scheduling resource may be allocated only to the UE.
  • the indication of the allocated uplink resources may comprise an offset prior to the UE commencing uplink data transmission using the allocated resources for data transmission.
  • the indication of the allocated resources may comprise a number of repetitions of the data to be transmitted.
  • the downlink indication may comprise a plurality of resource or suspension fields, each resource or suspension field relating to a different UE.
  • the method may further comprise prior to transmitting the downlink indication, the step of the base station allocating a suspension indicator to at least one UE in communication with the base station, and transmitting that suspension indicator to the at least one UE.
  • the suspension indicator may comprise a suspension ID, wherein the suspension indication field for UEs utilising the overlapping resources comprises the suspension ID.
  • the suspension indicator may comprise a no suspension indicator.
  • the suspension indicator may be selected from a set comprising at least one suspension ID and a no suspension indicator, and wherein the suspension indication field for UEs utilising the overlapping resources comprises a suspension ID.
  • Each suspension ID may be allocated for a UE utilising overlapping resources.
  • Each resource indication field may be for a UE transmitting URLLC/MTC channels.
  • Each suspension indication field may be for one or more UEs transmitting eMBB channels.
  • the method may further comprise at the base station identifying existing resource allocations that overlap with the allocated uplink resources.
  • a method of uplink data transmission from a user equipment (UE) to a base station in a cellular wireless network comprising the steps of transmitting via a wireless link a scheduling request from the UE to a base station to transmit data; receiving at the UE a downlink indication, the downlink indication comprising at least one resource indication field, each of which includes an indication of the resource used by the received scheduling request; and/or at least one suspension indication field each of which includes an indication for UEs utilising the overlapping resources to suspend transmissions
  • the resource indication field may further comprise an indication of allocated uplink resources.
  • the method may further comprise, during a configuration phase, the step of receiving an indication of at least one scheduling request resource available to the UE for transmitting scheduling requests, each scheduling request resource having a corresponding resource index, and/or an indication of at least one uplink resource allocated to the UE for data transmission.
  • Each scheduling request resource may comprise a unique combination of time, frequency, and sequence resources.
  • At least one allocated scheduling resource may also be allocated to a further UE which is in communication with the base station.
  • At least one allocated scheduling resource may be allocated only to the UE.
  • the indication of allocated uplink resources may comprise an indication of an offset prior to the UE commencing uplink data transmission using the allocated resources.
  • the indication of allocated uplink resources may comprise an indication of the number of repetitions of the data to be transmitted.
  • the downlink indication may comprise a plurality of downlink indication fields, each downlink indication field relating to a different UE and comprising an indication of allocated resources, and an indication of UEs to suspend transmissions.
  • the method may further comprise the step of receiving a suspension indicator from the base station.
  • the suspension indicator may comprise a suspension ID, and wherein the indication for UEs utilising the overlapping resources comprises the suspension ID.
  • the suspension indicator may comprise a no suspension indicator.
  • the suspension indicator may be selected from a set comprising at least one suspension ID and a no suspension indicator, and wherein the suspension indication field comprises a suspension ID.
  • the suspension indication field may comprise at least one suspension ID allocated to UEs utilising overlapping resources.
  • the UEs utilising overlapping resources may be UEs transmitting eMBB channels.
  • a method of uplink data transmission from a user equipment (UE) to a base station in a cellular wireless network comprising the steps of receiving a suspension indicator from a base station via a wireless link, wherein the suspension indicator is selected from a set comprising at least one suspension ID and a no suspension indicator; if the suspension indicator is a suspension ID, monitoringfor downlink indication transmissions from the base station, and if a downlink indication is received comprising that suspension ID suspending uplink transmissions during resources indicated in the downlink indication; and if the suspension indicator is a no suspension indicator configuring the UE to not listen for downlink indications.
  • the suspension indicator is selected from a set comprising at least one suspension ID and a no suspension indicator
  • a method of uplink data transmission from a user equipment (UE) to a base station in a cellular wireless network comprising the steps of receiving at the base station a request from a UE to transmit data and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources utilised by other UEs; and transmitting via a wireless link from the base station a downlink indication, the downlink indication comprising at least one resource indication field, each of which includes an indication of the resource used by the received scheduling request; and/or at least one suspension indication field each of which includes an indication for UEs utilising the overlapping resources to suspend transmissions.
  • UE user equipment
  • the resource indication field may further comprise an indication of the allocated uplink resources.
  • the method may further comprise a configuration phase comprising the step of the base station allocating at least one scheduling request resource to the UE, each scheduling request resource having a corresponding resource index; and/or at least one uplink resource to the UE for data transmission.
  • the method may further comprise transmitting from the base station to the UE an indication of the scheduling request resource and/or uplink resource allocated to that UE.
  • Each allocated scheduling request resource may be allocated a scheduling request resource index, and the indications of scheduling request resources comprises the scheduling request resource index.
  • Each scheduling request resource may comprise a unique combination of time, frequency, and sequence resources.
  • At least one allocated scheduling request resource may be also allocated to a further UE which is in communication with the base station.
  • At least one allocated scheduling resource may be allocated only to the UE.
  • the indication of the allocated uplink resources may comprise an offset prior to the UE commencing uplink data transmission using the allocated resources for data transmission.
  • the indication of the allocated resources may comprise a number of repetitions of the data to be transmitted.
  • the downlink indication may comprise a plurality of resource or suspension fields, each resource or suspension field relating to a different UE.
  • the method may further comprise prior to transmitting the downlink indication, the step of the base station allocating a suspension indicator to at least one UE in communication with the base station, and transmitting that suspension indicator to the at least one UE.
  • the suspension indicator may comprise a suspension ID, and wherein the suspension indication field for UEs utilising the overlapping resources comprises the suspension ID.
  • the suspension indicator may comprise a no suspension indicator.
  • the suspension indicator may be selected from a set comprising at least one suspension ID and a no suspension indicator, and wherein the suspension indication field for UEs utilising the overlapping resources comprises a suspension ID.
  • Each suspension ID may be allocated for a UE utilising overlapping resources.
  • Each resource indication field may be for a UE transmitting URLLC/MTC channels.
  • Each suspension indication field may be for one or more UEs transmitting eMBB channels.
  • the method may further comprise at the base station identifying existing resource allocations that overlap with the allocated uplink resources.
  • the non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.
  • Figure 1 shows grant-based and grant-free communication processes
  • Figure 2 shows a grant-based protocol
  • Figure 3 shows an example of SR resource allocations
  • Figure 4 shows an example of downlink indication transmission
  • Figure 5 shows an example format for a downlink indication
  • Figure 6 shows transmissions from UEs
  • Figure 7 shows an example format for suspension IDs
  • Figure 8 shows an example communication exchange utilizing suspension IDs.
  • FIG. 2 shows grant-based communication system intended to provide efficient use of resources while managing system latency.
  • the following description is given specifically in the context of low latency (specifically URLLC) data and services, but as will be appreciated the principles, methods, and systems apply to any type of data and service in the same way.
  • URLLC low latency
  • a UE is configured with at least one set of defined resources to be utilised for transmission of SR messages relating to low latency data transmission.
  • the resources may be time, frequency, and/or sequence resources which are available to the UE for transmission of SR messages.
  • Each unique combination of time, frequency, and/or sequence is allocated an SR resource index.
  • a cyclic shift of a sequence is considered to be a different sequence to other cyclic shifts.
  • the UE is also configured with resources for transmission of the low latency data, which configuration may include, for example, details of time & frequency resources, redundancy versions, coding & modulation schemes, periodicity and DMRS.
  • the configuration information at steps 200 and 201 may be considered pre-configuration information because the configuration is set prior to knowledge of a requirement for services using the resources.
  • the UE selects resources for transmission of an SR messagefrom the allocated SR resources and transmits an SR message at step 203 using those resources.
  • the SR resources may be selected at random, or according to a pre-defined method.
  • the SR message may include the SR resource index, or another indication of the SR resources utilised.
  • the base station Upon receipt of the SR message the base station allocates appropriate uplink resources for the uplink data transmission and at step 204 transmits a downlink indication.
  • the downlink indication addresses the specific UE using the SR resource index, or the SR resource index may be indicated implicitly, for example by indicated the time, frequency, RB, or sequence.
  • the downlink indication may also include a description of the resources to be used for the uplink transmission, which indicated resources may be a subset of the resources allocated for the UE.
  • the downlink indication may also include an indication to the UE, and/or other UEs, to suspend transmissions on the resources to be used for thelow latency datatransmission to which the SR message relates.
  • the inclusion of suspension information allows the resources allocated to the UE to be re-used for other transmissions, which other transmissions are interrupted in the event the resources are requiredfor low latency data.
  • low latency data is typically characterised by infrequent transmissions of small data packets, and hence the resources will only be utilised for the low-latency data transmissions on an infrequent basis.
  • the inclusion of suspension information thus allows use of the resources for the majority of the time when the resources are not used for low-latency data transmission. A typical use of such resources is for transmission of eMBB data over PDSCH. Such transmissions may use the whole time duration of a slot and hence will likely have started prior to the resources being allocated for use for the low-latency data.
  • the UE transmits the uplink data using the indicated resources.
  • the resources may have been intended to be utilised by another UE, or a different service, those other UEs or services are suspended and hence the UE has access to the resources without any risk of conflict.
  • a UE is assigned a set, or pool, of SR resources.
  • Each SR resource may be allocated an index from #0 to #K-1.
  • Each resource is a unique combination of time, frequency, and/or sequence resources.
  • the number of resources #K is selected by the system (in particular the base station (gNB) ) according to a target collision rate for SR messages.
  • the collision rate is also dependent on the number of UEs utilising the pool of resources, and the rate at which packets arrive at the UE uplink for transmission.
  • the required collision rate can thus be achieved with 23 resources per 100 UEs, which is a significant improvement compared to the 100 resources required for a dedicated allocation for each UE.
  • the system may thus allocate resources differently for each UE depending on the anticipated behaviour of the UEs. Resources may be shared between fewer UEs which have a higher packet rate, and between more UEs with a lower packet rate, or UEs with a higher packet rate may be allocated dedicated resources.
  • Figure 3 shows an example allocation of resources to a set of 20 UEs. 5 sequences are available across 2 RBs, providing 10 unique resources, each of which is allocated a unique SR Resource index.
  • UEs #0 -#3 are determined to have a higher packet arrival rate and are thus allocated dedicated SR Resources (SR Resource Indexes #0 -#3) .
  • UEs #4 -#19 have a lower packet arrival rate and hence share a pool of SR Resources (SR Resource Indexes #4 -#19) .
  • Higher or lower packet arrival rates are related to a target collision rate, and a high target collision rate can accept a high packet arrival rate so the threshold between higher and lower packet arrival rate is also relatively high.
  • Knowledge of a UE’s packet arrival rate may be derived form a subscribed UE’s profile which is reported to the gNB when a connection is setup, or based on a UE’s past behaviour. For example a gNB may be configure dot monitor packet arrival rates to determine likely future rates. Thisis reasonable as URLLC is mainly for factory control and its service model is nearly static.
  • Figure 4 shows an example timing diagram for the downlink indication.
  • adownlink indication may include one or more SR Resource Indices, or a combination of parameters that map to the required UEs, for example a combination of RB index and sequence number.
  • the downlink indication may also include a resource description indicating the resources, typically a subset of the resources allocated at step 201 of Figure 2 above.
  • the downlink indication may also include offset and repetition parameters.
  • an SR message is transmitted at 400 and a corresponding downlink indication transmitted at 401.
  • the downlink indication includes an offset 402 of 2 and a repetition of 2.
  • the uplink data is thus first sent at the second opportunity, 403, and repeated once at 404.
  • the minimum or default offset is 1 and the use of higher values enables flexibility in scheduling.
  • the number of repetitions can be set for the particular reliability requirements of the data.
  • the downlink indication message may be structured as a set of downlink indication fields such that one message can address more than one UE, as shown in Figure 5.
  • Each downlink indication field corresponds to one UEand includes an SR resource index and optionally a data resource description.
  • a UE identifying an SR resource index in a downlink indication field used for an SR message the UE utilises the corresponding resources for its uplink transmission.
  • the downlink indication may be utilised to suspend transmissions by other UEs (or the same UE) to allow the UE with low latency data to utilise resources.
  • on-going eMBB transmissions may be interrupted.
  • Figure 6 is utilised in the following description to assist explanation.
  • 5 PDSCHs 600-604 are scheduled by 5 DCIs 610-614 to 5 eMBB UEs.
  • four low latency data transmission resources 620-623 are allocated to one or more UEs for low latency data transmission.
  • the low latency resources 620-623 will only be used occasionally, and therefore those resources can often be utilised for PDSCH transmissions 601, 602, 603 which overlap with them.
  • the gNB is aware of which PDSCHs 600-604 overlap with a low latency data transmission resource 620-623 and hence which PDSCHs may be interrupted.
  • the DCI transmitted to each UE includes a suspension indication which indicates how the UE should behave.
  • the suspension indication may be either a suspension ID or a “no suspension” indication.
  • a “no suspension” indication is transmitted to UEs with a PDSCHs which doesnot overlap with the low latency data transmission resources since even if the low latency resources are utilised there is no need for those UEs to interrupt transmissions.
  • UEs 0 and 4 thus do not need to monitor downlink indications in the relevant slot and can thus avoid wasting power by monitoring such indications.
  • each of UEs 1 -3 are allocated a unique suspension ID.
  • UEs which have been assigned a suspension ID are configured to monitor downlink indications in the relevant slot as it is possible they will receive an indication to suspend transmission of their PDSCH.
  • each UE is allocated a unique Suspension ID.
  • a common Suspension ID may be utilised for two or more UEs. For example, if the only low latency resource was 620, UEs 0, 3 and 4 would be set to no suspension, and a single Suspension ID could be allocated to UEs 1 and 2 since they will only be suspended together.
  • a gNB When transmitting a downlink indication a gNB includes the suspension ID corresponding to any UEs utilising resources which overlap with low latency resources indicated for use in the downlink indication. UEs receiving their Suspension ID are configured to extract the resource details from the downlink indication and suspend transmission during the period the resources which will be used for transmission of low latency data.
  • the low latency resources may not occupy all frequency resources being used by a UEfor PDSCH, but a UE may suspend all transmissions of the relevant channel since reprocessing the signals according to newly available resources may be difficult and would have to be done quickly. However, if such reprocessing can be performed in the available time then partial transmission may continue on frequency resourcesnot allocated for low latency transmission. In the example of Figure 6 some data transmission from UEs 1 and 3 could continue around the low latency resources.
  • Figure 8 shows example messages for the UEs and configuration of Figures 6 and 7.
  • the DCI for each UE is utilised to indicate either non suspension or a suspension ID for the corresponding UE.
  • the gNB receives an SR message for a short duration (low latency) transmission, and allocates resources 621.
  • a downlink indication is transmitted at step 802 including the resource allocation for the UE which transmitted the SR message, and also including Suspension IDs 1 and 2.
  • UEs 1 -3 have been configured in step 800 with a Suspension ID each of them listens for downlink indications and thus receives message 802.
  • UE1’s suspension ID is not included and accordingly that UE continues transmission on PDSCH.
  • UEs 2 and 3 receive their SuspensionID and hence retrieve the resource details included in the downlink indication.
  • UEs 2 and 3 then suspend transmission on PDSCH for the duration of the resources indicated in the downlink indication message, resuming transmission once the allocated time period has passed.
  • the above disclosure thus provides a system in which collisions in low latency data are avoided, but efficiency losses are mitigated by allowing use of low latency resources for other channels when they are not utilised for low latency data.
  • Messages to suspend transmissions on UEs sharing resources are transmitted in an efficient process by utilising Suspension IDs.
  • 2 bits are sufficient to indicate the Suspension ID, which compares favourably with an alternative method of utilising a UE’s RNTI which is 16 bits long.
  • any of the devices or apparatus that form part of the network may include at least a processor, a storage unit and a communications interface, wherein the processor unit, storage unit, and communications interface are configured to perform the method of any aspect of the present invention. Further options and choices are described below.
  • the signal processing functionality of the embodiments of the invention especially the gNB and the UE may be achieved using computing systems or architectures known to those who are skilled in the relevant art.
  • Computing systems such as, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc. ) , mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment can be used.
  • the computing system can include one or more processors which can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.
  • the computing system can also include a main memory, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by a processor. Such a main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor.
  • the computing system may likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for a processor.
  • ROM read only memory
  • the computing system may also include an information storage system which may include, for example, a media drive and a removable storage interface.
  • the media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW) , or other removable or fixed media drive.
  • Storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive.
  • the storage media may include a computer-readable storage medium having particular computer software or data stored therein.
  • an information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system.
  • Such components may include, for example, a removable storage unit and an interface , such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to computing system.
  • the computing system can also include a communications interface.
  • a communications interface can be used to allow software and data to be transferred between a computing system and external devices.
  • Examples of communications interfaces can include a modem, a network interface (such as an Ethernet or other NIC card) , a communications port (such as for example, a universal serial bus (USB) port) , a PCMCIA slot and card, etc.
  • Software and data transferred via a communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface medium.
  • computer program product may be used generally to refer to tangible media such as, for example, a memory, storage device, or storage unit.
  • These and other forms of computer-readable media may store one or more instructions for use by the processor comprising the computer system to cause the processor toperform specified operations.
  • Such instructions generally referred to as ‘computer program code’ (which may be grouped in the form of computer programs or other groupings) , when executed, enable the computing system to perform functions of embodiments of the present invention.
  • the code may directly cause a processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.
  • the non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory
  • the software may be stored in a computer-readable medium and loaded into computing system using, for example, removable storage drive.
  • a control module in this example, software instructions or executable computer program code
  • the processor in the computer system when executed by the processor in the computer system, causes a processor to perform the functions of the invention as described herein.
  • inventive concept can be applied to any circuit for performing signal processing functionality within a network element. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP) , or application-specific integrated circuit (ASIC) and/or any other sub-system element.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these.
  • the invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as FPGA devices.
  • the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/CN2019/073099 2018-02-08 2019-01-25 Grant-based uplink transmission WO2019154106A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201980011306.8A CN111801975B (zh) 2018-02-08 2019-01-25 基于授权的上行传输

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB1802058.6 2018-02-08
GB1802058.6A GB2570899B (en) 2018-02-08 2018-02-08 Grant-based uplink transmission

Publications (1)

Publication Number Publication Date
WO2019154106A1 true WO2019154106A1 (en) 2019-08-15

Family

ID=61731278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/073099 WO2019154106A1 (en) 2018-02-08 2019-01-25 Grant-based uplink transmission

Country Status (3)

Country Link
CN (1) CN111801975B (zh)
GB (1) GB2570899B (zh)
WO (1) WO2019154106A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126403A1 (en) 2017-01-05 2018-07-12 Motorola Mobility Llc Resource reservation
GB2572429A (en) * 2018-03-29 2019-10-02 Tcl Communication Ltd Resource allocation
WO2020031382A1 (ja) * 2018-08-10 2020-02-13 株式会社Ｎｔｔドコモ ユーザ端末

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150264712A1 (en) * 2012-07-31 2015-09-17 Ntt Docomo, Inc. Mobile station and radio base station
WO2017015910A1 (zh) * 2015-07-29 2017-02-02 华为技术有限公司 上行数据发送装置、接收装置及方法
CN106922029A (zh) * 2015-12-24 2017-07-04 华为技术有限公司 一种信道资源的调度方法及装置
US20170264402A1 (en) * 2016-03-14 2017-09-14 Samsung Electronics Co., Ltd Transmission of sounding reference signals in communication systems with carrier aggregation
CN108235436A (zh) * 2016-12-22 2018-06-29 财团法人资讯工业策进会 通信用户装置及基站

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013117014A1 (en) * 2012-02-10 2013-08-15 Nokia Siemens Networks Oy Identifying a subset of a plurality of radio resources of a downlink control channel
ES2765205T3 (es) * 2014-09-26 2020-06-08 Alcatel Lucent Asignación de recursos a un equipo de usuario para comunicaciones celulares de enlace ascendente y directas de dispositivo a dispositivo
CN107624262B (zh) * 2015-05-19 2021-09-03 瑞典爱立信有限公司 使用mac消息指配用于专用调度请求的资源的方法以及相关无线终端和基站

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150264712A1 (en) * 2012-07-31 2015-09-17 Ntt Docomo, Inc. Mobile station and radio base station
WO2017015910A1 (zh) * 2015-07-29 2017-02-02 华为技术有限公司 上行数据发送装置、接收装置及方法
CN106922029A (zh) * 2015-12-24 2017-07-04 华为技术有限公司 一种信道资源的调度方法及装置
US20170264402A1 (en) * 2016-03-14 2017-09-14 Samsung Electronics Co., Ltd Transmission of sounding reference signals in communication systems with carrier aggregation
CN108235436A (zh) * 2016-12-22 2018-06-29 财团法人资讯工业策进会 通信用户装置及基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INSTITUTE FOR INFORMATION INDUSTRY III: "Discussion on eMBB and URLLC multiplexing in UL", 3GPP TSG-RAN WG1 NR-ADHOC R1-1700586, 20 January 2017 (2017-01-20), XP051208115 *

Also Published As

Publication number Publication date
GB2570899A (en) 2019-08-14
CN111801975B (zh) 2023-11-10
GB2570899B (en) 2021-01-06
GB201802058D0 (en) 2018-03-28
CN111801975A (zh) 2020-10-20

Similar Documents

Publication Publication Date Title
US11653362B2 (en) Resource allocation for user equipment
EP3496500B1 (en) Random access method and device
US11395291B2 (en) Allocating transmission resources in communication networks that provide low latency services
EP3654706B1 (en) Resource determining method, and base station
CN113574948B (zh) 用于复用uci的方法和装备
JP2021501490A (ja) 制御情報送信の方法及び装置
AU2020220568B2 (en) Random access method, device, and system
US11910437B2 (en) Conflict avoidance in a cellular network
CN111316748B (zh) 减少新无线电中被寻呼用户设备的随机接入的或与之相关的改进
EP3780808A1 (en) Terminal device, base station device, and communication method
WO2020259329A1 (en) Sidelink resource allocation
CN111818647A (zh) 数据传输方法及装置
EP3451761A1 (en) Downlink control information sending method and detection method and device
WO2019154106A1 (en) Grant-based uplink transmission
WO2019095907A1 (zh) 资源映射方法、确定方法、网络侧设备及用户终端
CN108633104B (zh) 随机接入方法、用户设备、基站以及随机接入系统
WO2022078245A1 (en) Power saving for sidelink communications
EP3648527B1 (en) Method, device, and system for transmitting downlink control information
EP4236540A2 (en) Information sending and receiving method and apparatus
WO2017031643A1 (zh) 资源分配、指示及识别资源类型、接收数据的方法及装置
WO2020119628A1 (en) Management of pre-allocated resources
WO2019213977A1 (zh) 资源配置方法及装置
WO2017113979A1 (en) Cellular communication system devices
CN112602363B (zh) 动态分配寻呼和/或rach资源的方法及相关设备
WO2020025032A1 (en) Uplink transmission resource sharing

Legal Events

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

Ref document number: 19751877

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19751877

Country of ref document: EP

Kind code of ref document: A1