[go: up one dir, main page]

WO2020074069A1 - Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil - Google Patents

Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil Download PDF

Info

Publication number
WO2020074069A1
WO2020074069A1 PCT/EP2018/077489 EP2018077489W WO2020074069A1 WO 2020074069 A1 WO2020074069 A1 WO 2020074069A1 EP 2018077489 W EP2018077489 W EP 2018077489W WO 2020074069 A1 WO2020074069 A1 WO 2020074069A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
user device
communication requirement
resource
sequence
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/EP2018/077489
Other languages
English (en)
Inventor
Hamidreza Shariatmadari
Zexian Li
Mikko Aleksi Uusitalo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
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
Priority to PCT/EP2018/077489 priority Critical patent/WO2020074069A1/fr
Publication of WO2020074069A1 publication Critical patent/WO2020074069A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0007—Code type
    • H04J13/0055—ZCZ [zero correlation zone]
    • H04J13/0059—CAZAC [constant-amplitude and zero auto-correlation]
    • H04J13/0062—Zadoff-Chu
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority

Definitions

  • This description relates to wireless communications.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices.
  • Signals can be carried on wired or wireless carriers.
  • LTE long-term evolution
  • E-UTRA evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • APs base stations or access points
  • eNBs evolved NodeBs
  • UEs user equipments
  • LTE has included a number of improvements or developments.
  • 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks.
  • 5G is also targeted at the new emerging use cases in addition to mobile broadband.
  • a goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security.
  • 5G NR may also scale to efficiently connect the massive Internet of Things (loT), and may offer new types of mission-critical services.
  • Ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.
  • a method includes determining, by a user device, a set of scheduling request resources allocated to the user device for
  • each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; determining a communication requirement for an uplink data transmission; transmitting, by the user device to a base station, a scheduling request via a scheduling request resource that is associated with the determined communication requirement in order to request uplink resources and indicate the associated communication requirement; and receiving, by the user device from the base station, an uplink resource grant that indicates resources allocated to the user device for uplink transmission.
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: determine, by a user device, a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement;
  • a communication requirement for an uplink data transmission determines a communication requirement for an uplink data transmission; transmit, by the user device to a base station, a scheduling request via a scheduling request resource that is associated with the determined communication requirement in order to request uplink resources and indicate the associated communication requirement; and receive, by the user device from the base station, an uplink resource grant that indicates resources allocated to the user device for uplink transmission.
  • a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system perform a method of determining, by a user device, a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; determining a communication requirement for an uplink data transmission; transmitting, by the user device to a base station, a scheduling request via a scheduling request resource that is associated with the determined communication requirement in order to request uplink resources and indicate the associated communication requirement; and receiving, by the user device from the base station, an uplink resource grant that indicates resources allocated to the user device for uplink transmission.
  • a method may include determining, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; receiving, by the base station from the user device, a scheduling request via a scheduling request resource associated with a communication requirement; determining, based on the received scheduling request, a communication requirement for the user device; determining, based on the determined communication requirement for the user device, resources to be allocated to the user device; and
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: determine, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement;
  • a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform a method of determining, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; receiving, by the base station from the user device, a scheduling request via a scheduling request resource associated with a communication requirement; determining, based on the received scheduling request, a communication requirement for the user device; determining, based on the determined communication requirement for the user device, resources to be allocated to the user device; and
  • FIG. 1 is a block diagram of a wireless network according to an example implementation.
  • FIG. 2 is a diagram illustrating operation of a system according to an example embodiment.
  • FIG. 3 is a flow chart illustrating operation of a user device according to an example embodiment.
  • FIG. 4 is a flow chart illustrating operation of a base station according to an example embodiment.
  • FIG. 5 is a block diagram of a node or wireless station (e.g., base
  • FIG. 1 is a block diagram of a wireless network 130 according to an example implementation.
  • user devices 131 , 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipments (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an evolved NodeB (eNB), next generation NodeB (gNB) or a network node.
  • AP access point
  • eNB evolved NodeB
  • gNB next generation NodeB
  • BS or AP 134 provides wireless coverage within a cell 136, including to user devices 131 , 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided.
  • BS 134 is also connected to a core network 150 via a S1 interface 151. This is merely one simple example of a wireless network, and others may be used.
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples, or any other wireless device.
  • SIM subscriber identification module
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • implementations or techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types.
  • 5G New Radio (NR) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), Internet of Things (loT), and/or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency
  • loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications MTC, or Machine to Machine communications
  • MTC Machine Type Communications
  • eMBB Enhanced mobile broadband
  • Ultra-reliable and low-latency communications URLLC is a new data service type, or new usage scenario, which may be supported for 5G New Radio (NR) systems. This enables emerging new applications and services, such as industrial automations,
  • 3GPP Rel-15 targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10 5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example.
  • BLER block error rate
  • U-Plane user/data plane
  • URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability).
  • a URLLC UE or URLLC application on a UE
  • eMBB UE or an eMBB application running on a UE.
  • the various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G, cmWave, and/or mmWave band networks, loT, MTC, eMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology.
  • wireless technologies or wireless networks such as LTE, LTE-A, 5G, cmWave, and/or mmWave band networks, loT, MTC, eMTC, eMBB, URLLC, etc.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • 5G Fifth Generation
  • cmWave Fifth Generation
  • Cellular systems such as LTE and 5G new radio (NR) defines several physical channels to separate different information types.
  • the channels are categorized as data and control channels.
  • the control channels may be utilized for link establishment, sending a scheduling request (SR), reporting the HARQ (Hybrid Automatic Repeat ReQuest) feedback (ACK/NACK feedback), and performing link adaptation for example.
  • SR scheduling request
  • UE user equipment
  • RRC radio resource control
  • a BS in response to a scheduling request (SR), may send an uplink resource grant to the UE that allocates (and identifies) time-frequency resources to the UE for the uplink transmission of data from the UE to the BS.
  • SR scheduling request
  • a BS e.g., eNB/gNB
  • a URLLC application/UE may have much shorter tolerable latency, as compared to an eMBB application or UE, for example. Or, there may be different communication requirements (e.g., different tolerable latencies) for different URLLC applications or UEs.
  • the UE may send a subsequent or a second (or retransmitted) SR to the BS.
  • the further delay caused by sending the initial or first SR, and waiting to send the second SR may create further delay that may reduce the available or remaining latency budget, for example, for such UE or application.
  • a UE There presently is no specified way for a UE to send a SR and indicate different communication (or QoS) requirement, and/or indicate whether a SR is a first (or initial) SR or a second (or retransmitted) SR.
  • Multi-bit SR has been discussed in 3GPP for carrying such information, but the concept was not agreed in 3GPP.
  • the BS presently has no way to be notified of different communication (or Quality of Service (QoS)) requirements of a UE that is
  • BS transmitting a SR, and/or whether a SR is an initial SR or a retransmitted or subsequent SR (e.g., where a retransmitted or subsequent SR may have a stricter QoS or communication requirement due to time that has elapsed from the first SR transmission).
  • a SR is an initial SR or a retransmitted or subsequent SR (e.g., where a retransmitted or subsequent SR may have a stricter QoS or communication requirement due to time that has elapsed from the first SR transmission).
  • BS is presently unable to allocate or schedule uplink resources differently for various SRs, due to a lack of information provided to the BS.
  • 5G NR employs physical uplink control channel (PUCCH) to carry different control information, such as SR (scheduling request), HARQ (Hybrid ARQ) feedback, and CQI (Channel quality information) report.
  • PUCCH physical uplink control channel
  • SR scheduling request
  • HARQ Hybrid ARQ
  • CQI Channel quality information
  • UE user equipment
  • the PUCCH resource assignments for SR transmission may be periodical, for example with the configurable periodicity of 2, 7, and n * 14 symbols with normal CP (cyclic prefix), where he ⁇ 1 , 2, 5, 10, 20, 32, 40, 64, 80 ⁇ .
  • a UE can be configured with two sets of PUCCH resources, one for URLLC traffic and one for non-URLLC traffic.
  • a plurality of orthogonal sequences may include phase-rotated sequences that are based on different phase rotations or cyclic shifts of a base (or root) sequence.
  • the base (or root) sequence may be a base (or root) Zadoff-Chu (ZC) sequence.
  • ZC sequences have zero auto correlation property. This means that a plurality of orthogonal sequences may be obtained or generated from different cyclic shifts or phase rotations of a root/base ZC sequence.
  • different orthogonal sequences may be transmitted by different UEs, e.g., to send a scheduling request (SR) to a BS.
  • a UE may transmit a SR by transmitting a sequence (assigned or allocated to the UE for SR) to a BS.
  • the UE may be allocated a sequence and/or resource block region for transmitting a scheduling request (e.g., for transmitting the phase-rotated sequence assigned to the UE).
  • a resource block region may be a region of one or more resource blocks, where each resource block may include one or more time-frequency resources.
  • a UE can be configured to be able to transmit a SR at different periodicities or intervals because the UE can only transmit the SR (phase rotation sequence) only when BS has allocated time-frequency resources for the UE to transmit its SR.
  • the BS may, for example, configure the UE to transmit a SR once per TTI (transmission time interval or subframe), or once ever 2 TTIs, or every 7 TTIs, or once every 14 TTIs, or other periodicity. Shorter periodicity requires the BS to allocate more resources for SR transmission (e.g., a URLLC UE or application may be allocated more frequent SR transmission opportunities, e.g., every 2 TTIs).
  • a problem may arise where a SR may not be received by the BS, and thus, the UE may need to retransmit a SR to the BS.
  • retransmitting the SR causes further delay for the UE (thus, consuming or using a portion of a latency budget for the UE).
  • a URLLC UE may typically have strict latency requirements (e.g., 0.5 ms, as an example, between receipt of downlink (DL) data from BS until the BS receives its transmitted UL data).
  • a URLLC UE may have a latency budget of 0.5 ms (e.g., its UL data should be received by BS within 0.5ms of when UE received DL data), for example, and the UE needs to send a SR first to obtain UL resources for UL data transmission.
  • a UE may send a SR by transmitting a sequence (e.g., a phase-rotated or cyclically shifted ZC sequence assigned to the UE for SR) to the BS.
  • 5G NR New Radio
  • a slot may be 14 symbols, and a mini- slot may be 1-13 symbols, for example.
  • a delay may occur of maybe 1 slot or 1 mini-slot duration (or more) after receiving a SR, before transmitting the UL resource grant to the UE.
  • the UE may have to wait until a next/subsequent slot or mini-slot to receive an UL grant.
  • the UE may retransmit a SR.
  • the latency budget (amount of time remaining for which the UE must deliver UL data to the BS) will then be less (e.g., now only 0.2 ms or 0.25 ms remaining of the original 0.5 ms latency budget), due to time elapsed during initial SR transmission and waiting to retransmit SR.
  • Mini-slot based operation is also known as non-slot based operation.
  • the configuration of the number of transmission opportunities may depend on different parameters, e.g., such as end-to-end latency requirements, transmission time interval (TTI), the queuing delay, delay of sending the SR and receiving allocated resource information. For instance, considering an example 0.5 ms latency target and TTI of 0.125 ms, the UE can be configured with the maximum of two transmission attempts if the SR is decoded successfully in the first attempt. However, the UE may be scheduled with the maximum of one transmission attempt if the SR is missed (not received by the BS) in the first attempt and the retransmitted SR is detected.
  • TTI transmission time interval
  • a BS e.g., eNB/gNB
  • eNB/gNB eNode B
  • the SR in LTE and current 5G NR does not carry any information regarding the communication requirements other than in 5G NR different configurations can be used for low latency services and other services.
  • additional information could help to improve URLLC performance, or performance of other UEs, applications or services that may have strict communication requirements.
  • the UE should be scheduled with shorter delay and higher reliability if the previous SR was missed, or the UE has suffered from a large queuing delay.
  • the lack of such QoS information in the SR may lead to performance degradation for scheduling and also reducing the capability of supporting URLLC in general.
  • BSs are presently unable differentiate between different communication (or QoS) requirements (e.g., maximum latency, reliability target, message size).
  • QoS communication
  • BSs are also unable to differentiate between an initial or first SR transmission (e.g., where a first communication or QoS requirement may apply) and a second or retransmitted SR (e.g., where a different communication or QoS requirement may apply).
  • the BS is unable to adapt or adjust its scheduling or allocation of UL resources in response to receiving a SR, under these various conditions.
  • the SR may be adjusted to include additional information (additional bits) regarding the communication requirement with a multi-bit approach, for instance.
  • additional bits additional bits
  • this approach might degrade the performance of SR detection due to including additional bits, thus increasing control overhead and thereby decreasing transmission efficiency.
  • this requires a new design for SR to include additional bits.
  • a set of (e.g., multiple) SR resources may be allocated to a UE, wherein each SR resource is associated with a different communication (e.g., QoS) requirement (e.g., a different maximum latency or latency target, a different reliability target, a different message size or a different data throughput target, or any combination, etc.).
  • QoS Quality of Service
  • a plurality of SR resources such as a plurality of combinations of a sequence (e.g., phase-rotated or phase-rotation sequence) and/or a resource block region, may be assigned to a UE for transmitting a SR, where each SR resource or each combination of sequence and/or resource block region may be associated with a different communication (e.g., QoS) requirement or target.
  • a sequence for different resource block regions (each different block region indicating a different communication requirement), or multiple (different) phase-rotated sequences (e.g., each different sequence indicating a different communication requirement) for the same resource block region, or a combination thereof, may be allocated to a UE for SR
  • each SR resource may be associated with a different set of a plurality of communication requirements (e.g., latency, throughput, message size, ... , or other communication or QoS requirements).
  • a first sequence may be associated with a first latency requirement, a first throughput or data rate requirement, and a first message size (as examples of a set of communication requirements associated with the first sequence)
  • a second sequence may be associated with a second latency requirement, a second throughput or data rate requirement, and a second message size (as examples of a set of communication requirements associated with the second sequence).
  • a UE may select one of a plurality of SR resources (e.g., select a different sequence and/or resource block region) associated with communication requirement of the UE, and then transmit the SR via the selected SR resource to indicate the
  • each sequence may be associated with (and may indicate, when transmitted) different communication (or QoS) requirement of the UE.
  • the UE may transmit the sequence associated with the selected communication (or QoS)
  • the BS may receive the SR (e.g., the sequence, and/or via a resource block region), and may determine the indicated communication (or QoS) requirement information (e.g., a latency budget) for the UE based on the SR resource (e.g., based on the received sequence, and/or the resource block region used to transmit the SR or sequence), and may schedule or allocate UL resources to the UE accordingly (or based on the indicated communication/QoS requirement).
  • the SR e.g., the sequence, and/or via a resource block region
  • the indicated communication (or QoS) requirement information e.g., a latency budget
  • a resource block (RB) region may include one or more resource blocks (RBs), where each RB may include a plurality of time- frequency resources.
  • a RB region may be configured to a UE via, e.g., a RRC (radio resource control) message or other downlink (DL) control message sent to the UE.
  • the resource block region can be one resource block or multiple resource blocks.
  • a RB region may be assigned to one UE only (for example in case the resource block region is used to indicate a UE identifier (or UE ID)), or a RB region may be shared by a group of UEs (in this case the UE can be identified by sequence or the combination of sequence and resource block region).
  • a UE may select a RB (one of the RBs) within the RB region that has been assigned to the UE to transmit the SR or sequence.
  • multiple sequences e.g., each sequence associated with a different communication requirement for the UE
  • different RB regions or different RBs
  • a combination thereof may be assigned to the UE to allow the UE to send a SR via the SR resource in order to identify the UE and also indicate an associated communication requirement.
  • a BS may adjust or adapt the allocation or assignment of UL resources based on the indicated communication (or QoS) requirement associated with the received SR (e.g., based on the received sequence and/or resource block region used to transmit the SR or sequence). For instance, the UE may be scheduled with shorter TTI and/or higher reliability if the previous SR was missed, or if the UE has suffered from a large queuing delay, or if the UE or transmitting application has a high priority QoS or strict communication requirement.
  • some further techniques that a BS may adjust or change its UL resource allocation or assignment to a UE for different indicated communication (or QoS) requirements may include (by way of illustrative examples):
  • the BS may schedule the UE resources with a shorter TTI for a higher priority QoS (e.g., shorter latency target), for a second or retransmitted SR (or where an initial SR from the UE was not received or the first UL resource allocation is not received at UE side or with decode failure); and the BS may use a longer TTI to schedule resources to the UE for a lower priority QoS (e.g., for a longer latency target) and/or for an initial or the first SR.
  • a higher priority QoS e.g., shorter latency target
  • a second or retransmitted SR or where an initial SR from the UE was not received or the first UL resource allocation is not received at UE side or with decode failure
  • the BS may use a longer TTI to schedule resources to the UE for a lower priority QoS (e.g., for a longer latency target) and/or for an initial or the first SR.
  • BS may determine or allocate UL resources to the UE based on slot scheduling (e.g., UL resource grant indicates UL resources for the UE have been scheduled during a next slot) for a lower priority QoS (e.g., with longer latency budget) or for an initial SR transmission, while the BS may determine or allocate UL resources for the UE based on mini- slot (also known as non-slot based operation) scheduling (e.g., UL grant indicates UL resources allocated to UE during a next mini-slot, providing quicker resource scheduling to UE) for the higher priority QoS or shorter latency target or for a second or retransmitted SR, for example.
  • slot scheduling e.g., UL resource grant indicates UL resources for the UE have been scheduled during a next slot
  • mini- slot also known as non-slot based operation
  • scheduling e.g., UL grant indicates UL resources allocated to UE during a next mini-slot, providing quicker resource scheduling to UE
  • the BS may adjust the time-frequency resources allocated to the
  • the BS may allocate or schedule to the UE more time resources and fewer frequency resources (or fewer subcarriers) for a lower priority QoS (e.g., for a longer latency target) and/or for an initial or first SR.
  • QoS Quality of Service
  • the BS may allocate or schedule the UE with fewer time resources across but more frequency resources (e.g., across more subcarriers) for a higher priority QoS (e.g., shorter latency target), for a second or retransmitted SR (or where an initial SR from the UE was not received or the first UL resource allocation is not received at UE side or with decode failure), e.g., in order to decrease the transmission time for the UE to transmit its data.
  • QoS e.g., shorter latency target
  • the BS may allocate a larger number of time resources (e.g., symbols) for transmission of a longer message for a lower priority QoS (such as where SR indicates that data throughput is important, and a higher latency is acceptable), and may schedule a shorter burst (over fewer symbols) of resources for a higher priority QoS or shorter latency communication requirement (e.g., where a short latency budget is indicated by or associated with the received SR or received sequence.).
  • QoS the BS may use other techniques to adjust it scheduling or allocation of UL resources to a UE, depending on the communication (e.g., QoS) requirement indicated or associated with the received SR.
  • the BS may adjust or configure other communication parameters or communication configuration for the UE (e.g., for the UL resource grant and/or UL
  • link adaption may be performed to improve reliability for subsequent UE UL data transmission, e.g., for a higher priority QoS or communication requirement.
  • different MCS Mobility Management Function
  • the BS may control or instruct the UE to use a more robust (or lower) MCS and/or to use a higher UE transmission power to transmit the data, for example. These adjustments may be performed independently or jointly.
  • a UE may perform a method including determining, by a user device, a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; determining a
  • the user device transmitting, by the user device to a base station, a scheduling request via a scheduling request resource that is associated with the determined communication requirement in order to request uplink resources and indicate the associated communication requirement; and receiving, by the user device from the base station, an uplink resource grant that indicates resources allocated to the user device for uplink transmission and possible updated transmission parameters (e.g., where such transmission parameters for the UE may be set or adjusted by the BS based on the communication (or QoS) requirement associated with the SR resource (e.g., sequence and/or RB region) used by the UE to transmit the SR).
  • the SR resource e.g., sequence and/or RB region
  • a BS may perform a method including determining, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; receiving, by the base station from the user device, a scheduling request via a scheduling request resource associated with a communication requirement; determining, based on the received scheduling request, a communication requirement for the user device; determining, based on the determined communication requirement for the user device, resources to be allocated to the user device and possible transmission parameters; and transmitting, by the base station to the user device, an uplink resource grant that indicates the resources allocated to the user device for uplink
  • some example techniques may include:
  • a BS/gNB configuring a set of SR resources for a UE/user device, which may include a set of phase rotation (or phase-rotated) sequences and/or RB regions for the UE for SR transmission and/or different sequences, where each SR resource of the set of SR resources may be associated with (and may be used to identify) different UE communication (or QoS) requirement.
  • These configured set of SR resources may be communicated to the UE.
  • a set of communication requirements may be defined (e.g., in advance, by the network, and/or by the BS), and each communication requirement (or QoS requirement) may be mapped to or associated (e.g., via a mapping table) with a SR resource (e.g., associated with a sequence, and/or a resource block region for transmission of a SR, and/or mapped to a combination of sequence and RB region).
  • a SR resource e.g., associated with a sequence, and/or a resource block region for transmission of a SR, and/or mapped to a combination of sequence and RB region.
  • the BS may communicate this configuration or assignment of a set of SR resources to the UE (which may include or may indicate the communication requirement/QoS requirement for each SR resource). This may be indicated or communicated by the BS to a UE via a QoS table that indicates a SR resource (e.g., a sequence and/or RB region) for each of one or more communication (or QoS) requirements (e.g., indicating a sequence index for each of a plurality of latency requirements).
  • the mapping table between QoS requirements and the SR resources can be pre-configured or dynamically informed by the BS or other network nodes.
  • the UE may determine a communication requirement for its UL data transmission (e.g., maximum latency, or packet size or other communication requirement), and then select the associated SR resource (e.g., select the associated sequence associated with the determined communication requirement /QoS requirement).
  • a communication requirement for its UL data transmission e.g., maximum latency, or packet size or other communication requirement
  • select the associated SR resource e.g., select the associated sequence associated with the determined communication requirement /QoS requirement.
  • the UE may then transmit a SR to the BS based on or via the associated SR resource (e.g., by transmitting the associated sequence and/or transmit a SR or sequence via an associated RB region)
  • the BS may receive the SR and determine the associated communication (or QoS) requirement of the UE based on the associated (and received SR), e.g., based on the received sequence and/or based on the RB region used to transmit the SR and/or sequence.
  • the BS may allocate UL resources based on the indicated communication (or QoS) requirement for the UE (associated with the SR resource used to transmit the received SR).
  • the BS may then transmit the UL resource grant to the UE, identifying the UL resources allocated to the UE for UL transmission.
  • the UE may then transmit data to the BS via the allocated UL resources.
  • Some example technical advantages of this approach may include, for example: allowing a UE to request resources for UL transmission, while indicating a communication (or QoS) requirement of the UE, without requiring additional overhead or bits, and allowing the BS to adjust or change its allocation of UL resources to a UE based on the communication (or QoS) requirement indicated by (or associated with) a received SR.
  • This may allow a BS to vary or adjust (one or more aspects of) its resource allocation and/or UL transmission parameters including for example UL transmission power, modulation/coding schemes (MCS), etc., based on the particular requirements and/or needs of each UE or application that is requesting UL resources, without increasing overhead.
  • Table 1 An example of QoS set and assigned SR sequences.
  • Table 1 is an example of a QoS set (set of QoS requirements) and assigned or associated SR sequences.
  • QoS Quality of Service
  • the set can be formed according to different parameters, such as latency, reliability, or service type, message size, or other communication requirement(s).
  • a QoS set is shown with different latency targets. Each QoS index corresponds to a specific latency target for delivering the message.
  • a different sequence (e.g., sequences S1 , S2 and S3) may be transmitted by a UE, and may be used to indicate a different communication (or QoS) requirement, such as a latency requirement or latency target.
  • QoS communication
  • each QoS index identifies an associated latency target.
  • a UE may transmit one (or more) of the sequences in order to communicate or indicate to the BS a specific QoS index, and thus, indicating to the BS an associated latency requirement.
  • QoS index Q1 is associated with (or indicates) a latency target of > 0.25 ms.
  • QoS index Q2 is associated with a latency target of less than or equal to 0.25ms, and longer than or equal to 0.125 ms); and
  • QoS index Q3 is associated with a latency target of shorter than 0.125 ms.
  • a UE may transmit sequence S1 to indicate a QoS index of Q1 (and thus indicate a latency target of longer than or equal to 0.25 ms); a UE may transmit sequence S2 to indicate a QoS index of Q2 (and thus indicate a latency target of between 0.125ms and 0.25ms); and a UE may transmit sequence S3 to indicate a QoS index of Q3 (and thus indicate a latency target of shorter than or equal to 0.125 ms).
  • an initial SR may be transmitted by transmitting sequence S1 when the UE has an initial latency budget of 0.5 ms, but after not receiving an UL resource grant, the UE may retransmit the SR by transmitting sequence S2 (e.g., based on a decreased latency budget of 0.2 ms).
  • sequences S1 and S2 may both be transmitted by the UE (e.g., via consecutive SR opportunities or resources or even on the same resource) to indicate to BS the Q3 QoS index.
  • the UE transmitting both of sequences S1 and S2 may also increase a probability of at least one of these sequences being received by the BS.
  • FIG. 2 is a diagram illustrating operation of a system according to an example embodiment.
  • a UE 210 is connected with and in communication with BS 134.
  • UE 210 sends a scheduling request (SR) to BS 134 by transmitting sequence S1 (e.g., see Table 1 ).
  • sequence S1 e.g., see Table 1
  • the latency budget may be 0.6 ms for UE 210.
  • the SR at 212 is not received by BS 134.
  • UE 210 retransmits its SR to BS 134 by transmitting sequence S2, e.g., based on a decreased latency budget of 0.2ms for the UE 210.
  • the delay caused by transmitting SR 212, and waiting, has consumed or used up 0.4 ms of the 0.6 ms latency budget for the MS.
  • BS 134 receives the sequence S2 (where sequence S2 was previously assigned to UE 210 to indicate a latency budget of shorter than or equal to 0.25ms and longer than or equal to 0.125 ms, as shown in Table 1 ). Based on the mapping shown in Table 1 , the BS 134 knows or determined the approximate latency budget (less than or equal to 0.25ms, but greater than or equal to 0.125 ms), the BS 134 allocated UL resources for the UE 210.
  • the BS 134 may use mini-slot scheduling and may allocate more frequency resources and fewer symbols (less time resources) to speed up or shorten latency for scheduling and transmission of such UL data for the UE.
  • BS 134 may have used different resource scheduling if the SR was transmitted as sequence S1 (which would have indicated a larger latency budget), for example, (e.g., slot-based scheduling may have been used).
  • the BS transmits to the UE 210 an UL resource grant, which allocates or schedules UL resources to the UE 210.
  • UE 210 transmits data to the BS 134 via the scheduled UL resources.
  • FIG. 2 illustrates the SR transmission adopting the setting listed in Table 1.
  • the UE sends the initial S1 as the indication for a SR to the gNB.
  • the SR (S1 ) (steps 212/214) is not detected by the BS 134.
  • the UE 210 discovers that the initial SR was not received by the BS, as it does not receive an UL resource grant in response.
  • the UE sends S2 as the SR indication.
  • the BS/gNB 134 detects the retransmitted SR and allocates radio resources according to the latency budget, e.g., around 0.20 ms.
  • this approach provides a better resource utilization for the URLLC services.
  • the UE can be scheduled with a moderate BLER (e.g., 10%) for the initial SR transmission round, while a more stringent BLER target is selected for the retransmission of SR if needed. This results in achieving a high spectral efficiency.
  • the UE has to be scheduled to achieve a stringent BLER target even for the initial SR
  • the proposed scheme can achieve a better SR detection.
  • the Q3 results in sending S1 and S2 simultaneously.
  • initial SR and second SR were missed, and a 2nd retransmission of SR, and so the UE transmits either S3, or transmits both S1 and S2, e.g., over different resource block regions.
  • the proposed enhanced SR can be also used to multiplex different services.
  • one SR sequence can be assigned for URLLC with a moderate latency requirement, e.g., 1 ms, while the other can be assigned for URLLC with more stringent latency requirement, e.g., 0.5 ms.
  • the UE is scheduled using 0.25ms TTI, and otherwise it is scheduled using short TTI.
  • the SR sequences can be configured for each transmit antenna to support more QoS indexes.
  • different SR sequence can be assigned for URLLC with different packet size.
  • FIG. 3 is a flow chart illustrating operation of a user device according to an example embodiment.
  • Operation 310 includes determining, by a user device, a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement.
  • Operation 320 includes determining a communication requirement for an uplink data transmission.
  • Operation 330 includes transmitting, by the user device to a base station, a scheduling request via a scheduling request resource that is associated with the determined communication requirement in order to request uplink resources and indicate the associated communication requirement.
  • operation 340 includes receiving, by the user device from the base station, an uplink resource grant that indicates resources allocated to the user device for uplink transmission.
  • Example 2 wherein the transmitting a scheduling request via a scheduling request resource that is associated with the determined communication requirement comprises performing at least one of the following: transmitting, by the user device to the base station, a sequence, which is associated with the determined communication requirement, in order to request uplink resources and indicate the associated communication requirement; transmitting, by the user device to the base station, a scheduling request or sequence via a resource block region, wherein the resource block region is associated with the determined communication requirement, in order to request uplink resources and indicate the associated communication requirement; transmitting, by the user device to the base station, a sequence via a resource block region, wherein a combination of the sequence and the resource block region are associated with the determined communication requirement, in order to request uplink resources and indicate the associated communication requirement; and transmitting, by the user device to the base station, a combination of multiple sequences, wherein the
  • combination of multiple sequences are associated with the determined communication requirement, in order to request uplink resources and indicate the associated communication requirement.
  • Example 3 According to an example embodiment of the method of any of examples 1-2 wherein the determining a set of scheduling request resources comprises: receiving, by the user device from the base station, control information indicating a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including an associated combination of a sequence, of a plurality of sequences, and a resource block region, wherein each combination of sequence and resource block region is associated with a different communication requirement.
  • Example 4 According to an example embodiment of the method of any of examples 1-3 and further comprising: transmitting, by the user device, data via the resources indicated by the received uplink resource grant.
  • Example 5 According to an example embodiment of the method of any of examples 1-4, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises at least one of: a plurality of sequences for a first resource block region, with each sequence of the plurality of sequences being associated with a different communication requirement; a first sequence for a plurality of resource block regions, wherein each resource block region is associated with a different communication requirement; and a plurality of any combination of a sequence and a resource block region, wherein each combination of sequence and resource block region is associated with a different communication requirement.
  • Example 6 According to an example embodiment of the method of any of examples 1-5, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises: a plurality of sequences for a first resource block region, wherein for the first resource block region, each of the plurality of sequences is associated with a different communication requirement.
  • Example 7 According to an example embodiment of the method of any of examples 1-6, wherein the different communication requirement comprises at least one of: a different latency target; and a different reliability target; a different message size; and a different user device or a different region or group of user devices.
  • Example 8 According to an example embodiment of the method of any of examples 1-7, wherein the transmitting comprises at least one of the following: transmitting, by the user device to a base station, a scheduling request via a first uplink control channel resource that includes a first sequence and a resource block region that are associated with a first communication requirement, in order to request uplink resources and indicate the first communication requirement; and transmitting, by the user device to a base station, a scheduling request via a second uplink control channel resource that includes a second sequence and a resource block region that are associated with a second communication requirement, in order to request uplink resources and indicate the second communication requirement.
  • Example 9 According to an example embodiment of the method of any of examples 1-8 wherein the transmitting a scheduling request comprises: transmitting, by the user device to the base station, a first scheduling request via a first combination of sequence and resource block region that are associated with a first communication requirement in order to request uplink resources and indicate the associated first communication requirement; the method further comprising: determining that an uplink resource grant has not been received in reply to the first scheduling request; determining that a second communication
  • the receiving an uplink resource grant comprises: receiving, by the user device from the base station, an uplink resource grant, in reply to the second scheduling request, that indicates time-frequency resources allocated to the user device for uplink transmission.
  • Example 10 According to an example embodiment of the method of any of examples 1-9 wherein the transmitting comprises: transmitting, by the user device to a base station, a first scheduling request via a first combination of sequence and resource block region that are associated with a first latency requirement; failing to receive an uplink resource grant within a time period after the transmitting the first scheduling request; and transmitting, by the user device to the base station subsequent to the transmitting the first scheduling request, a second scheduling request via a second combination of sequence and resource block region that are associated with a second latency requirement that is stricter or shorter than the first latency requirement.
  • Example 1 1 According to an example embodiment of the method of any of examples 1-10, wherein each sequence is based on at least one of the following: a cyclic shift of a plurality of different cyclic shifts, that is applied to a base sequence; a cyclic shift that is applied to a base sequence of a plurality of different base sequences; and a cyclic shift of a plurality, of a plurality of different cyclic shifts, that is applied to a base sequence, and the cyclic-shifted sequence is spread with an orthogonal code.
  • Example 12 According to an example embodiment of the method of any of examples 1-1 1 wherein the transmitting comprises: transmitting, by the user device to a base station, a first scheduling request via a first combination of sequence and resource block region that are associated with a first latency requirement; failing to receive an uplink resource grant after the transmitting the first scheduling request; and transmitting, by the user device to the base station subsequent to the transmitting the first scheduling request, a second scheduling request via a second combination of sequence and resource block region that are associated with a second latency requirement that is stricter or shorter than the first latency requirement.
  • Example 13 According to an example embodiment of the method of any of examples 1-12, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises at least: a first scheduling request resource allocated to the user device for transmitting a first or initial scheduling request; and a second scheduling request resource allocated to the user device for transmitting a second or subsequent scheduling request; wherein each scheduling request resource includes a different sequence and/or resource block region, associated with a different communication requirement of the user device.
  • Example 14 According to an example embodiment of the method of any of examples 1-13, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises at least: a first scheduling request resource allocated to the user device to indicate a first communication requirement of the user device; and a second scheduling request resource allocated to the user device to indicate a second communication requirement of the user device; wherein each scheduling request resource includes a different sequence and/or resource block region, associated with a different communication requirement of the user device.
  • Example 15 An apparatus comprising means for performing a method of any of examples 1-14.
  • Example 16 A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of examples 1-14.
  • Example 17 An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of examples 1 -14.
  • Example 18 An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: determine, by a user device, a set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; determine a
  • FIG. 4 is a flow chart illustrating operation of a base station according to an example embodiment.
  • Operation 410 includes determining, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement.
  • Operation 420 includes receiving, by the base station from the user device, a scheduling request via a scheduling request resource associated with a communication requirement.
  • Operation 430 includes determining, based on the received scheduling request, a
  • Operation 440 includes determining, based on the determined communication requirement for the user device, resources to be allocated to the user device. And, operation 450 includes transmitting, by the base station to the user device, an uplink resource grant that indicates the resources allocated to the user device for uplink transmission.
  • Example 20 The method of example 19 wherein the receiving a scheduling request comprises: receiving, by the base station from the user device, a sequence, which is associated with a communication requirement; receiving, by the base station from the user device, a scheduling request via a resource block region that is associated with a communication requirement; receiving, by the base station from the user device, a sequence via a resource block region, wherein the sequence and the resource block region are associated with a communication requirement.
  • Example 21 The method of any of examples 19-20 and further comprising: transmitting, by the base station to the user device, control information indicating the set of scheduling request resources allocated to the user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including an associated combination of a sequence, of a plurality of sequences, and a resource block region, wherein each combination of sequence and resource block region is associated with a different communication requirement.
  • Example 22 The method of any of examples 19-21 and further comprising: receiving, by the base station from the user device, data via the uplink resources indicated by the uplink resource grant.
  • Example 23 The method of any of examples 19-22, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises at least one of: a plurality of sequences for a first resource block region, with each sequence of the plurality of sequences is associated with a different communication requirement; a first sequence for a plurality of resource block regions, wherein each resource block region is associated with a different communication requirement; and a plurality of any combination of a sequence and a resource block region, wherein each combination of sequence and resource block region is associated with a different communication
  • Example 24 The method of any of examples 19-23, wherein the set of scheduling request resources allocated to the user device for transmitting a scheduling request comprises: a plurality of sequences, wherein each of the plurality of sequences is associated with a different communication requirement.
  • Example 25 The method of any of examples 19-24, wherein the different communication requirement comprises at least one of: a different latency target; and a different reliability target; and a different message size; and a different user device or a different region or group of user devices.
  • Example 26 The method of any of examples 19-25, wherein the
  • the communication requirement comprises a latency requirement
  • the determining resources comprises at least one of: determining uplink resources to be allocated to the user device based on slot scheduling if the determined communication requirement is a first latency requirement; and determining uplink resources to be allocated to the user device based on mini-slot scheduling if the determined communication requirement is a second latency requirement that is stricter or shorter than the first latency requirement.
  • Example 27 The method of any of examples 19-26, wherein the
  • the communication requirement comprises a latency requirement
  • the determining resources comprises at least one of: determining uplink resources, including resources over a set of resource blocks that is greater than a threshold, to be allocated to the user device if the determined communication requirement is a first latency requirement; and determining resources, including resources over a set of resource blocks that is less than the threshold, to be allocated to the user device if the determined communication requirement is a second latency requirement that is stricter or shorter than the first latency requirement.
  • Example 28 An apparatus comprising means for performing a method of any of examples 19-27.
  • Example 29 A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of examples 19-27.
  • Example 30 An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of examples 19-27.
  • Example 31 An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: determine, by a base station, a set of scheduling request resources allocated to a user device for transmitting a scheduling request, with each scheduling request resource of the set of scheduling request resources including a sequence, of a plurality of sequences, and/or a resource block region, wherein each scheduling request resource is associated with a different communication requirement; receive, by the base station from the user device, a scheduling request via a scheduling request resource associated with a communication requirement; determine, based on the received scheduling request, a communication requirement for the user device; determine, based on the determined communication requirement for the user device, resources to be allocated to the user device; and transmit, by the base station to the user device, an uplink resource grant that indicates the resources allocated to the user device for uplink transmission.
  • Example 32 The method of any of examples 1-14 and 19-27, wherein the sequence comprises a phase-rotated sequence that is based on a phase rotation or cyclic shift of a base sequence.
  • Example 33 The method of any of examples 1-14 and 19-27, wherein each scheduling request resource of the set of scheduling request resources is associated with a different set of communication requirements.
  • Example 34 The method of any of examples 19-27, 32 and 33 further comprising: setting or configuring, by the base station, one or more updated transmission parameters for the user device (or UE) based on the determined communication (or QoS) requirement; and transmitting, by the base station to the user device, the one or more updated transmission parameters.
  • each different sequence indicates or is associated with a different communication requirement for the user device; each different resource block region indicates or is associated with a different communication requirement for the UE; each different combination of sequence and resource block region indicates or is associated with a different communication requirement for the user device; and each different combination of multiple sequences indicates or is associated with a different communication requirement for the user device.
  • Example 36 The method of any of examples 1-14, and 32-35 further comprising: receiving, by the user device from the base station, one or more updated transmission parameters for the user device that were set by the base station based on the determined communication (or QoS) requirement that is associated with the scheduling request resource that was used to transmit the scheduling request; and transmitting, by the user device based on the one or more updated transmission parameters, data via the resources indicated by the received uplink resource grant.
  • FIG. 5 is a block diagram of a wireless station (e.g., AP or user device) 900 according to an example implementation.
  • the wireless station 900 may include, for example, one or two RF (radio frequency) or wireless transceivers 902A, 902B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 904 to execute instructions or software and control transmission and receptions of signals, and a memory 906 to store data and/or instructions.
  • Processor 904 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 904 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 902 (902A or 902B).
  • Processor 904 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 902, for example).
  • Processor 904 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 904 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 904 and transceiver 902 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 908 may execute software and instructions, and may provide overall control for the station 900, and may provide control for other systems not shown in FIG. 5, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 900, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 904, or other controller or processor, performing one or more of the functions or tasks described above.
  • RF or wireless transceiver(s) 902A/902B may receive signals or data and/or transmit or send signals or data.
  • Processor 904 (and possibly transceivers 902A/902B) may control the RF or wireless transceiver 902A or 902B to receive, send, broadcast or transmit signals or data.
  • the embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co- operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non- existent.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a
  • a machine-readable storage device or in a propagated signal for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network
  • 5G 5th generation mobile networks
  • CQI Channel quality indicator
  • MCS Modulation and coding scheme
  • MLD Maximum Likelihood Detector
  • PDCCH Physical downlink control channel
  • PUCCH Physical uplink control channel
  • PDU Protocol data unit
  • RLC Radio link control
  • SR Scheduling request
  • UE User equipment

Landscapes

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

Abstract

Selon l'invention, un procédé peut consister à déterminer, par un dispositif d'utilisateur, un ensemble de ressources de demande d'ordonnancement attribuées au dispositif d'utilisateur pour transmettre une demande d'ordonnancement, chaque ressource de demande d'ordonnancement de l'ensemble de ressources de demande d'ordonnancement contenant une séquence, d'une pluralité de séquences, et/ou une région de bloc de ressources, chaque ressource de demande d'ordonnancement étant associée à différents besoins de communication ; déterminer un besoin de communication pour une transmission de données de liaison montante ; transmettre, par le dispositif d'utilisateur à une station de base, une demande d'ordonnancement par l'intermédiaire d'une ressource de demande d'ordonnancement qui est associée au besoin de communication déterminé afin de demander des ressources de liaison montante et d'indiquer le besoin de communication associé ; et recevoir, par le dispositif d'utilisateur en provenance de la station de base, une attribution de ressource de liaison montante qui indique des ressources attribuées au dispositif d'utilisateur pour une transmission de liaison montante.
PCT/EP2018/077489 2018-10-09 2018-10-09 Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil Ceased WO2020074069A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/077489 WO2020074069A1 (fr) 2018-10-09 2018-10-09 Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/077489 WO2020074069A1 (fr) 2018-10-09 2018-10-09 Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil

Publications (1)

Publication Number Publication Date
WO2020074069A1 true WO2020074069A1 (fr) 2020-04-16

Family

ID=63840834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/077489 Ceased WO2020074069A1 (fr) 2018-10-09 2018-10-09 Transmissions de demande d'ordonnancement améliorées dans des réseaux sans fil

Country Status (1)

Country Link
WO (1) WO2020074069A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031039A1 (fr) * 2020-08-05 2022-02-10 Samsung Electronics Co., Ltd. Temps de survie dans un réseau d'accès radio
CN114979976A (zh) * 2022-05-11 2022-08-30 中国电信股份有限公司 数据处理方法、装置、设备及介质
WO2022178739A1 (fr) * 2021-02-25 2022-09-01 Qualcomm Incorporated Gestion de requête de planification (sr) pour des communications reposant sur des relais

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160066341A1 (en) * 2008-07-01 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a telecommunication system
US20170202009A1 (en) * 2014-07-17 2017-07-13 Lg Electronics Inc. Method and apparatus for requesting scheduling in wireless communication system
US20180279324A1 (en) * 2017-03-23 2018-09-27 Qualcomm Incorporated Scheduling request for one or more uplink transmissions using narrowband communications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160066341A1 (en) * 2008-07-01 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a telecommunication system
US20170202009A1 (en) * 2014-07-17 2017-07-13 Lg Electronics Inc. Method and apparatus for requesting scheduling in wireless communication system
US20180279324A1 (en) * 2017-03-23 2018-09-27 Qualcomm Incorporated Scheduling request for one or more uplink transmissions using narrowband communications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO ET AL: "Scheduling request design in NR system", vol. RAN WG1, no. Hangzhou; 20170515 - 20170519, 14 May 2017 (2017-05-14), XP051273672, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170514] *
NTT DOCOMO ET AL: "Sequence-based PUCCH vs DMRS-based PUCCH", vol. RAN WG1, no. Spokane, USA; 20170403 - 20170407, 2 April 2017 (2017-04-02), XP051243854, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170402] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031039A1 (fr) * 2020-08-05 2022-02-10 Samsung Electronics Co., Ltd. Temps de survie dans un réseau d'accès radio
WO2022178739A1 (fr) * 2021-02-25 2022-09-01 Qualcomm Incorporated Gestion de requête de planification (sr) pour des communications reposant sur des relais
CN114979976A (zh) * 2022-05-11 2022-08-30 中国电信股份有限公司 数据处理方法、装置、设备及介质
CN114979976B (zh) * 2022-05-11 2023-11-03 中国电信股份有限公司 数据处理方法、装置、设备及介质

Similar Documents

Publication Publication Date Title
US10225826B2 (en) Transmission of uplink control information for multiple control channel format lengths
EP3665989B1 (fr) Gestion dynamique de ressources de signalisation de commande de liaison montante dans un réseau sans fil
US20180324786A1 (en) Resource determination for uplink control channel for wireless networks
US11399382B2 (en) Enabling uplink transmission during downlink subframe based on preemption of data transmission in wireless network
US11452124B2 (en) Uplink channel scheduling to retain channel occupancy for unlicensed wireless spectrum
CN107852313B (zh) 下行链路控制信息接收方法和用户设备以及下行链路控制信息发送方法和基站
JP6693565B2 (ja) 無線通信システムにおける短い送信時間間隔に基づく通信のための方法
JP6895958B2 (ja) １セグメントｐｕｃｃｈフォーマット
US20190173623A1 (en) Reallocation of control channel resources for retransmission of data in wireless networks based on communications mode
US20180324861A1 (en) Method and apparatus for identifying uplink signal transmission timing in wireless communication system
WO2017074437A1 (fr) Procédures pour rapporter un état de mémoire tampon
US11723052B2 (en) Adjusting a repetition operation of uplink control information associated with multiple transmission reception points
WO2020074069A1 (fr) Transmissions de demande d&#39;ordonnancement améliorées dans des réseaux sans fil
JP7333853B2 (ja) Ｐｕｓｃｈ伝送を処理するデバイス
US11974265B2 (en) Use of priority mismatch indication for uplink transmission for wireless networks
EP3777431B1 (fr) Indication de rétroaction pour une transmission continue dans des réseaux sans fil
US10880053B2 (en) Wireless device, a network node and methods therein for handling transmissions in a wireless communications network
US11502892B2 (en) Modulation adjustment for 16-QAM in narrowband IoT
JP6915721B2 (ja) ユーザ装置及び基地局による方法
WO2021006884A1 (fr) Communications ultra-fiables à faible latence 5g nouvelle radio dans le spectre des ondes millimétriques

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: 18785919

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: 18785919

Country of ref document: EP

Kind code of ref document: A1