WO2021229319A1 - Appareil et procédés de multiplexage de requête de planification - Google Patents

Appareil et procédés de multiplexage de requête de planification Download PDF

Info

Publication number
WO2021229319A1
WO2021229319A1 PCT/IB2021/052931 IB2021052931W WO2021229319A1 WO 2021229319 A1 WO2021229319 A1 WO 2021229319A1 IB 2021052931 W IB2021052931 W IB 2021052931W WO 2021229319 A1 WO2021229319 A1 WO 2021229319A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
uplink data
data channel
uplink
channel
Prior art date
Application number
PCT/IB2021/052931
Other languages
English (en)
Inventor
Ping-Heng Kuo
Zexian Li
Matha DEGHEL
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2021229319A1 publication Critical patent/WO2021229319A1/fr

Links

Classifications

    • 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/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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 signaling, 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—Signaling for the administration of the divided path
    • 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

Definitions

  • Ultra-reliable low-latency communications is a key technology for a plethora of diverse applications, ranging from industrial automation, virtual reality, remote surgery, to connectivity enabling distributed monitoring and control of power grids.
  • URLLC has been one of the main usage scenarios since the beginning of 3rd Generation Partnership Project (3GPP) new radio (NR) design, i.e. Release (Rel)-15.
  • 3GPP 3rd Generation Partnership Project
  • NR new radio
  • two work items namely URLLC layer 1 (LI) Enhancement work item (WI) and Industrial Internet of Things (IIoT) WI, have been targeting for better support of URLLC and IIoT use cases.
  • URLLC layer 1 (LI) Enhancement work item (WI) and Industrial Internet of Things (IIoT) WI have been targeting for better support of URLLC and IIoT use cases.
  • One topic included in both WIs is intra-user equipment (UE) multiplexing and/or prioritization addressing control channel and data channel, control channel and control channel, data channel and data channel multiplexing and/or prioritization.
  • UE intra-user equipment
  • 3GPP RP-193233 considers one of the objectives of the Rel-17 WI “Enhanced Industrial Internet of Things (IoT) and URLLC support” being intra-UE multiplexing and prioritization of traffic with different priority, particularly specifying multiplexing behavior among hybrid automatic repeat request - acknowledgement (HARQ-ACK)/scheduling request (SR)/channel state information (CSI) and Physical uplink shared channel (PUSCH) for traffic with different priorities.
  • IoT Enhanced Industrial Internet of Things
  • URLLC support is intra-UE multiplexing and prioritization of traffic with different priority, particularly specifying multiplexing behavior among hybrid automatic repeat request - acknowledgement (HARQ-ACK)/scheduling request (SR)/channel state information (CSI) and Physical uplink shared channel (PUSCH) for traffic with different priorities.
  • HARQ-ACK hybrid automatic repeat request - acknowledgement
  • SR scheduling request
  • CSI channel state information
  • PUSCH Physical uplink shared channel
  • FIG. 1 illustrates an example of a method performed by a network node according to certain embodiments.
  • FIG. 2 illustrates an example of a method performed by a user equipment according to certain embodiments.
  • FIG. 3 illustrates an example of another method performed by a network node according to certain embodiments.
  • FIG. 4 illustrates an example of another method performed by a user equipment according to certain embodiments.
  • FIG. 5 illustrates an example of signal exchange between a network node and a user equipment according to certain embodiments.
  • FIG. 6 illustrates an example of a logic flow at a user equipment according to certain embodiments.
  • FIG. 7 illustrates an example of resource allocation according to certain embodiments.
  • FIG. 8 illustrates an example of another method performed by a user equipment according to certain embodiments.
  • FIG. 9 illustrates an example of another resource allocation according to certain embodiments.
  • FIG. 10 illustrates an example of another signal exchange between a network node and a user equipment according to certain embodiments.
  • FIG. 11 illustrates another example of logic flow at a user equipment according to certain embodiments.
  • FIG. 12 illustrates an example of a wireless communication network according to certain embodiment.
  • SR scheduling request
  • Physical uplink shared channel also known as an uplink data channel
  • REs dedicated resource elements
  • SR multiplexing condition also known as restriction
  • restriction is applied prior to the decision of multiplexing the SR and an uplink data channel.
  • the uplink data channel in this specification, may be PUSCH, an uplink shared channel, or an uplink channel carrying mainly data information as well as some control information.
  • the uplink data channel is not limited to carrying data information only; it may carry some control information, although what it mainly carries is data information.
  • another approach is conditional determination of resource allocation for SR multiplexing.
  • FIG. 1 illustrates an example of a method performed by a network node according to certain embodiments.
  • a network node which may be for example network entity, gNB, eNB, base station, access point, etc., transmits at least one signal including at least one indication to a user equipment (UE).
  • the at least one indication indicates at least one condition for multiplexing at least one SR into an uplink data channel.
  • the uplink data channel may be for example PUSCH, uplink shared channel, or an uplink channel carrying data information as well as control information.
  • the at least one condition may comprise one or more conditions that may be included in one or more indications. When there are multiple indications, these indications may be carried in one signal or more than one signals transmitted from the network node to the UE.
  • the one more than one signals may comprise, for example, configuration or configuration information of the at least one SR. Either of them may indicate one or more certain uplink data channels that the at least one SR, which associates with the SR configuration, may be multiplexed into.
  • each SR configuration may include one indication indicating whether the associated SR may be multiplexed with at least one PUSCH, and/or which particular PUSCH the SR may be multiplexed in. Whether or not the at least one SR may be multiplexed into a particular PUSCH may depend on the SR configuration.
  • the UE determines whether or not the at least one condition is satisfied or met or fulfilled. If the at least one condition is satisfied, or met certain criteria, the UE will multiplex the SR into the uplink data channel, and then transmit the multiplexed SR and uplink data channel to the network node.
  • the network node receives the multiplexed at least one SR in the uplink data channel.
  • the multiplexing the SR into the uplink data channel may be considered the same as the SR multiplexed on, or into, or with, or to, or onto the uplink data channel.
  • FIG. 2 illustrates an example of a method performed by a user equipment according to certain embodiments.
  • a UE receives from a network node at least one signal, which includes at least one indication that indicates at least one condition for multiplexing at least one SR in an uplink data channel.
  • the UE determines whether or not the at least one condition is satisfied, or meets certain criteria; if so, the UE multiplexes at least one SR into an uplink data channel as shown in step 230, and then, as step 240 shows, the UE transmits the at least one SR multiplexed in the uplink data channel to the network node.
  • FIG. 2 may be seen as an example with more detail of the UE behavior as in the same scenario as FIG. 1 depicts.
  • FIG. 3 illustrates an example of another method performed by a network node according to certain embodiments.
  • a network node transmits to a UE at least one signal including at least one indication, which indicates a list of SRs.
  • the list comprises one or more SRs that are allowed to be multiplexed into an uplink data channel in an uplink transmission.
  • the uplink data channel may be, for example, PUSCH, an uplink shared channel, or an uplink channel carrying mainly data information and some control information.
  • the UE determines to multiplex at least one SR, which is among the received list of SRs, into the uplink data channel, and transmits the at least one SR multiplexed in the uplink data channel.
  • the network node receives the at least one SR multiplexed in the uplink data channel from the UE.
  • FIG. 4 illustrates an example of another method performed by a user equipment according to certain embodiments.
  • a UE receives at least one signal from a network node.
  • the at least one signal includes at least one indication that indicates a list of SRs, which includes at least one SR, allowed to be multiplexed into an uplink data channel.
  • the UE multiplexes the at least one SR, which belongs to the list of SRs, into the uplink data channel.
  • the UE transmits, in step 430, the multiplexed at least one SR and the uplink data channel to the network node.
  • FIG. 4 may be considered with more detail on the UE activities as in the same scenario as FIG. 3 describes.
  • the transmission of the at least one SR may be triggered by a logical channel (LCH) or a medium access control (MAC) control element (CE) in MAC layer.
  • the at least one SR may be multiplexed into the uplink data channel such as PUSCH with different characteristics or attributes, which may be reflected by parameters or conditions of the channel.
  • multiplexing of one SR triggered by one LCH may be limited to one type of PUSCH, while multiplexing of another SR triggered by another LCH may be limited to another type of PUSCH.
  • the at least one SR may be associated to at least one uplink control channel for SR configuration.
  • the uplink control channel may be, for example, physical uplink control channel (PUCCH).
  • the at least one condition discussed above comprises at least one information related to at least one of the at least one SR, the uplink data channel or the uplink control channel for the at least one SR.
  • the at least one information may comprise criteria or criteria related information, notified to the UE, that the characteristics and/or parameters of the uplink data channel need to satisfy certain properties to be multiplexed with the at least one SR.
  • the at least one information may regard to attributes, characteristics, and/or parameters of the uplink data channel.
  • the uplink control channel for the at least one SR may be understood as PUCCH for the at least one SR, or PUCCH resource carry or to carry the at least one SR, which may be written as SR-PUCCH or PUCCH-SR in this specification.
  • the at least one information may comprise any one or more of the follows:
  • resource allocation for example number and/or patterns of REs, in the uplink data channel for control information multiplexing
  • At least another information associated with grant of the uplink data channel for example modulation and coding scheme (MCS), transmission power, hybrid automatic repeat request (HARQ) setting, etc.
  • MCS modulation and coding scheme
  • HARQ hybrid automatic repeat request
  • the at least one indication may comprise indication indicating that the at least one SR is allowable to be multiplexed with the uplink data channel or to be multiplexed into uplink data channel of a grant.
  • the at least one indication may comprise indication indicating at least one of: resource allocation, a number of REs, or a RE allocation pattern of REs for the multiplexing of the at least one SR into the uplink data channel.
  • This indication may be also known as configuration of the UE from the network node. The indication allows the UE to determine the number of REs to be reserved in the uplink data channel and/or the mapping pattern for SR multiplexed in the uplink data channel, based on SR configuration associated with an uplink control channel resource that overlaps or collides with the uplink data channel in time domain.
  • the UE may determine by itself at least one of: resource allocation, a number of REs, or an allocation pattern of REs for the multiplexing of the at least one SR into the uplink data channel based on configuration of the at least one SR associated to a PUCCH resource that overlaps or collides with PUSCH in time domain.
  • the at least one indication may comprise indication indicating whether the at least one SR is to be allocated with at least one of contiguous REs or non-contiguous REs in frequency domain or in time domain. In case frequency hopping is applied to the uplink data channel, the at least one indication may indicate whether the at least one SR will be mapped to the resource of one of the two hops or the resources from both hops. In case there are more than two hops, the at least one indication may indicate whether the at least one SR will be mapped to the resource of some or all of the hops.
  • the at least one indication may comprise indication indicating whether the at least one SR is to be multiplexed into one or more of the repetitions of one uplink data channel, in case resource for the at least one scheduling request overlaps with one or more repetitions of one uplink data channel.
  • the at least one indication may comprise indication, in case resource of the at least one SR overlaps with more than one uplink data channels, indicating whether the at least one SR is to be multiplexed into one or more of the more than one uplink data channels.
  • the at least one indication further indicates at least one carrier that the at least one SR is to be multiplexed on.
  • the at least one indication indicates allowing the UE to determine at least one of:
  • the at least one indication discussed above may be contained in one indication or in multiple indications.
  • the determination of whether or not to multiplex the at least one SR in the uplink data channel may be made based on the at least one information.
  • the at least one indication may be included in the at least one signal comprising at least one configuration of at least one of a dynamic grant (DG), radio resource control (RRC) signal for at least one of configured grant (CG) configuration, logical channel (LCH), or SR configuration.
  • DG dynamic grant
  • RRC radio resource control
  • the UE may select the SR to be multiplexed into the overlapping or colliding PUSCH based on one or more of the follows:
  • polarity of the SR for example the SR being positive or negative
  • the index of the SR configuration with a positive SR is transmitted on the PUSCH, and the resources for sending such information on the PUSCH may be selected based on these rules. In other words, the at least one of these rules may be used for determining an amount of resource for the multiplexing on PUSCH.
  • what is multiplexed on the PUSCH is the SR with the index of the SR configuration having a positive SR.
  • the positive SR refers to the case that there is SR triggered by a LCH or MAC CE and delivered to PHY ; and SR being negative refers to the case that no SR is triggered in MAC and nothing is delivered to PHY.
  • FIG. 5 illustrates an example of signal exchange between a network node and a user equipment according to certain embodiments. It demonstrates the SR multiplexing upon certain rule or condition.
  • gNB 502 a network node, transmits a configuration message to UE 504.
  • the restriction rule also known as rule or condition, serves as guidelines for the UE 504 to determine whether a SR can be multiplexed into a PUSCH.
  • the restriction rule further indicates or includes the characteristics, also known as information or attributes or parameters of a PUSCH that need to be satisfied or met in order to multiplex a SR triggered by a LCH or MAC CE into that PUSCH.
  • the PUSCH may be an uplink data channel or an uplink shared channel carrying data information mainly and some control information.
  • the characteristics or information as SR multiplexing restriction includes at least one of the following:
  • type of grant of the PUSCH for example, DG, Type-1 CG, or Type-2 CG
  • resource allocation for example number and/or patterns of REs in the uplink data channel for control information multiplexing ⁇ serving cell that the PUSCH operates in
  • UE 504 When an uplink grant for a PUSCH in step 512 is received by UE 504 from gNB 502, and UE 504 intends to transmit SR triggered by a LCH as shown in step 514.
  • UE 504 may determine, in step 516, if the triggered SR can be multiplexed into the PUSCH, based on the configured SR multiplexing restriction or condition that includes information, also called characteristics or parameters, associated to the PUSCH.
  • gNB 502 may directly indicate in the uplink grant, a list of at least one SR, triggered by different LCHs, that are allowed to be multiplexed into the grant for the PUSCH.
  • gNB 502 does not have to perform step 510, even though it may, then UE 504 determines at least one SR on the allowed SR list in step 516 and multiplex it into the PUSCH and transmits the multiplexed SR and PUSCH in step 518.
  • UE 504 may transmit the PUSCH, as in step 518, without SR multiplexing PUSCH. Alternatively, UE 504 may drop the transmission of PUSCH and transmits the PUCCH for the SR.
  • FIG. 6 illustrates an example of a logic flow at a user equipment according to certain embodiments.
  • a UE like UE 504 in FIG. 5, receives configuration of SR multiplexing restriction in step 610, and an uplink grant for PUSCH in step 612.
  • the restriction may include a set of rules, a group of conditions, information related to the PUSCH and/or PUCCH for SR, etc.
  • Steps 610 and 612 may occur in the order as in the figure, at the same time, or in a switched order with step 612 occuring prior to step 610.
  • the UE Upon reception of the grant for PUSCH and SR triggered by a LCH, the UE, in step 614, determines the resource of the PUSCH grant overlaps, also called collides or conflicts, with the PUCCH resource to carry the SR that the UE intends to transmit. As shown in step 616, the UE may consider or determine if the PUSCH meets the SR multiplexing criteria configured for the LCH, wherein the criteria include the SR multiplexing restriction or condition. If the PUSCH meets the SR multiplexing criteria, the UE will multiplex the SR into the PUSCH in step 618; otherwise, the UE will handle the transmission of the SR and/or the PUSCH by some prioritization rule in step 620.
  • FIG. 7 illustrates an example of resource allocation according to certain embodiments.
  • resource of a PUSCH need to be fit the requirement of the SR, which is allowed to be multiplexed into the PUSCH, to ensure the SR can be delivered to the network node with satisfactory reliability and/or latency.
  • the number of REs in the PUSCH or the associated resource mapping need to meet the requirement of carrying the multiplexed allowed SR onto the PUSCH.
  • Two examples of uplink resource mapping modes are illustrated in FIG.7, where demodulation reference signal (DMRS) are assumed to be front loaded, meaning allocated to the first symbol of the PUSCH.
  • DMRS demodulation reference signal
  • the resource or the REs for SR are allocated to, for example, the two contiguous physical resource blocks (PRBs) of the PUSCH resource, while in the mapping mode 2, the resource or REs for SR, for example, are allocated to or hopped across two non-contiguous PRBs of the PUSCH resource.
  • the number of REs for SR may be either more or less than shown in the two mapping modes.
  • the resource allocated in the mapping mode 1 may be one PRB which may or may not be at the first PRB of the PUSCH resource next to DMRS.
  • the resource allocation of SR in multiple PRBs of the PUSCH resource may be contiguous or non-contiguous.
  • the resource allocation of the SR can be located in the resource of one hop or in the resource of more than one hops. For example, applying mapping mode 1 in both the first hop and the second hop, in case two hops are configured for the PUSCH transmission.
  • the network node may indicate the number of REs in a PUSCH that may be used for SR multiplexing, and the associated resource mapping pattern. This indication may be conveyed in the dynamic grant, or configured in radio resource control (RRC) per CG configuration, per LCH, or per SR configuration.
  • RRC radio resource control
  • the network node and the UE have the common knowledge about which PUSCH may be used for multiplexing of at least one particular SR.
  • the network node implicitly controls the achievable reliability of SR based on restrictive mapping.
  • conditional resource allocation may be used for SR multiplexing in the PUSCH based on the resource overlap or collision between PUCCH for the SR and the PUSCH.
  • the REs allocated for SR multiplexing in the PUSCH may change based on which PUCCH or which SR configuration the REs overlaps or collides with. This is useful for a CG configuration as different CG occasions may collide with PUCCH of different SR configurations depending on their periodicities, which indicates how often the SR-PUCCH of this SR configuration is transmitted.
  • the number of REs and/or the resource mapping of a CG may be changed based on which PUCCH it conflicts with.
  • the CG is enabled to multiplex SR it overlaps or collides with, and the resource allocation may be determined in an adaptive manner.
  • FIG. 8 illustrates an example of another method performed by a user equipment according to certain embodiments.
  • a UE determines at least one of resource allocation, a number of REs, or a RE allocation pattern for multiplexing the at least one SR into the uplink data channel. The determination may be based on at least one information related to at least one of the uplink data channel or the at least one uplink control channel for the at least one SR.
  • the UE transmits to a network node or network element, the at least one SR multiplexed in the uplink data channel.
  • the network node From the network node perspective, it transmits a downlink configuration signal including resource information of at least one uplink control channel for at least one SR. Based on the resource information, UE determines the at least one uplink control channel for the at least one SR overlaps or collides with the uplink data channel, and it further determines at least one of resource allocation, a number of REs, or a RE allocation for multiplexing the at least one SR into the uplink data channel and carrying them to the network node. At the UE, the at least one SR is multiplexed in the uplink data channel and trasnmitted in the determined resource. The network node receives from the UE the at least one SR multiplexed in the uplink data channel.
  • the uplink data channel may be PUSCH or uplink shared channel mainly carrying data information and also control information.
  • the at least one uplink control channel may be a PUCCH.
  • the overlap also known as the collision or confliction, may occur in time domain or in frequency domain between the uplink control channel, which is configured to carry the at least one SR, and the uplink data channel.
  • the at least one information may comprise at least one of the follows:
  • type of grant of the uplink data channel for example, DG, Type-1 CG, or Type-2 CG
  • resource allocation for example number and/or patterns of REs, in the uplink data channel for control information multiplexing
  • content of the MAC protocol data unit of the uplink data channel for example, types and/or content of conveyed MAC CEs, LCHs of conveyed data, and/or whether any data from SRB is carried in the MAC PDU
  • the number of REs that the UE may determine is associated to the at least one information related to the uplink data channel and/or the uplink control channel that the uplink data channel is at least partially overlapping with.
  • the uplink data channel is associated to at least one CG configuration.
  • the at least one CG configuration may comprise at least one configured grant occasion that at least partially overlap with at least one uplink control channel in time domain.
  • the uplink control channel may comprise at least partial resource for the at least one SR.
  • the determination performed by the UE is based on the as least one CG configuration or configuration of the at least one uplink control channel.
  • FIG. 9 illustrates an example of another resource allocation according to certain embodiments.
  • the resource for SR multiplexing with CG PUSCH occasions may be varied depending on which SR- PUCCH, meaning PUCCH resource for carrying SR, a CG PUSCH occasion conflicts with.
  • SR-multiplexing RE set 2 For instance, if the CG for PUSCH collides with PUCCH for SR configuration 2, then more resource or REs, for example SR-multiplexing RE set 2, will be allocated into the PUSCH of the colliding CG occasion for the SR multiplexing. On the other hand, if the CG collides with PUCCH for SR configuration 1, then fewer resource or REs, for example SR-multiplexing RE Set 1, will be allocated into the PUSCH of the colliding CG occasion for the SR multiplexing. This implicitly shows SR configuration 2 is for LCHs with higher priority compared to SR configuration 1. Thus, the resource allocation for multiplexing the SR with the PUSCH may at least partially depend on the priority of the LCH that triggers the SR.
  • per-CG configuration can be provided by a network node via, for example, RRC signaling.
  • the configuration instructs UE how to determine the resource or RE allocation of each CG occasion, depending on which SR-PUCCH resource it collides with.
  • the configuration message should provide a mapping between RE allocation pattern and the SR configuration associating to the colliding PUCCH. For instance, if a CG occasion collides with PUCCH associated with SR configuration 0-7, reserve 24 REs for SR multiplexing in the PUSCH of the CG occasion; and, if a CG occasion collides with PUCCH associated with SR configuration 8-15, reserve 12 REs for SR multiplexing in the PUSCH of the CG occasion.
  • FIG. 10 illustrates an example of signal exchange between a network node and a user equipment according to certain embodiments.
  • gNB 1002 in step 1010, transmits a per-CG configuration to UE 1004.
  • the configuration is related to collision-dependent resource or RE allocation.
  • an SR triggering occurs as well as the PUCCH associated with the SR (SR-PUCCH or PUCCH-SR) configuration overlaps or collides with a CG occasion. Consequently, in step 1030, UE 1004 determines resource or RE allocation of the CG occasion based on the SR configuration associated with the colliding SR-PUCCH.
  • the resource allocation may include resource mapping or resource mapping pattern.
  • FIG. 11 illustrates another example of logic flow at a user equipment according to certain embodiments.
  • a UE receives per-CG configuration of resource allocation determination.
  • the per-CG configuration of resource allocation determination may be configured by the network node at a higher layer, for example RRC layer.
  • the UE in step 1120, processes PUSCH of a CG occasion. Then, it determines whether or not the PUSCH overlaps with any SR-PUCCH in step 1130.
  • the UE further determines, as shown in step 1140, whether or not the overlapped SR-PUCCH associates with a certain SR configuration subset. If the PUSCH, however, does not overlap with any SR-PUCCH, the UE will not reserve resource or RE in the PUSCH for SR multiplexing as in step 1160.
  • the UE reserves 24 REs in the PUSCH for SR multiplexing as in step 1150; otherwise, it reserves 12 REs instead in the PUSCH for SR multiplexing in step 1170.
  • a PUSCH may overlap with two or more PUCCHs that are configured or scheduled to convey more than one SRs. Then, a prioritization mechanism may be needed to determine which of the overlapped SR should be processed for multiplexing on the PUSCH.
  • a network node may be unable to interpret which SR, for example triggered by which LCH, should be consequently multiplexed into the PUSCH.
  • the UE may further embed information that allows the network node to identify the multiplexed SR via at least one explicit or implicit indication such as SR index, UCI, MAC CE, or PUSCH configuration. For instance, the UE may indicate which LCHs have triggered a positive SR so that the network node may allocate resources accordingly.
  • the mechanism may decide which SR of the overlapped SR-PUCCH should be dropped.
  • the UE may check which SR may be multiplexed into the PUSCH based on the received SR multiplexing restriction, rule or condition. And, it may drop the SR which is not allowed to be multiplexed into the PUSCH. If more than one SRs are allowed to be multiplexed into the PUSCH, the UE further selects the SR(s) to be multiplexed based on the SR multiplexing restriction, rule or condition, for example, which SR is triggered by the LCH with higher priority, or which SR configuration has higher or smaller index.
  • a UE determines resource allocation of an uplink data channel based on the colliding SR-PUCCH
  • the UE may select one colliding SR based on SR multiplexing condition, restriction, rule or criteria as discussed previously for multiplexing.
  • the resource allocation mapping may be decided based on the configuration of the selected one colliding SR, in accordance to the configuration from a network node regarding mapping between resource allocation and SR configurations.
  • Network node 1202 is adapted for communication over a wireless link 1204 with an apparatus, such as a mobile device or mobile terminal or a UE 1205.
  • the network node 1202 may be an access point, an access node, a base station, gNB or an eNB similar to gNB 502 of FIG. 5, gNB 1002 of FIG. 10, and the network nodes discussed with the other figures, wherein a gNB may comprise a frequency selective repeater, of any wireless network such as 5G NR, LTE, LTE-A, GSM, GERAN, WCDMA, CDMA, Wireless LAN, and the like.
  • one or more than one UE are under the control of a gNB such as network node 1202; or, a UE is under the control of more than one network node.
  • a gNB such as network node 1202
  • a UE is under the control of more than one network node.
  • the UE 1205 may be a user device similar to UE 504 in FIG. 5, UE1004 in FIG. 10 and the UEs in the other figures.
  • the reason that a UE and a network node are both illustrated here is that one convenient mechanism for carrying out examples of embodiments usually involves communication using a communication network.
  • the UE 1205 includes processing means such as at least one data processor, DP 1206, storing means such as at least one computer-readable memory, MEM 1208, for storing data 1210, at least one computer program, PROB 1211, or other set of executable instructions, communication means such as a transmitter, TX 1212, and a receiver, RX 1214, for bidirectional wireless communications with the network node 1202 via at least one antenna 1216.
  • processing means such as at least one data processor, DP 1206, storing means such as at least one computer-readable memory, MEM 1208, for storing data 1210, at least one computer program, PROB 1211, or other set of executable instructions
  • communication means such as a transmitter, TX 1212, and a receiver, RX 1214, for bidirectional wireless communications with the network node 1202 via at least one antenna 1216.
  • the network node 1202 also includes processing means such as at least one data processor, DP 1220, storing means such as at least one computer-readable memory, MEM 1222, for storing data 1224 and at least one computer program, PROG 1226, or other set of executable instructions.
  • the network node 1202 may also include communication means such as a transmitter, TX 1228, and a receiver, RX 1230, for bidirectional wireless communications with the at least one UE 1205 via at least one antenna 1232.
  • Both the UE and the network node may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies. Other configurations of these devices, for example, may be provided.
  • MIMO multiple input multiple output
  • the at least one of PROG 1226 in the network node 1202 includes a set of program instructions which, when executed by the associated DP 1220, enable the device to operate in accordance with the exemplary embodiments of the present invention, as detailed above.
  • the UE 1205 also stores software 1211 in its MEM 1208 to implement certain exemplary embodiments of this invention.
  • the exemplary embodiments of this invention may be implemented at least in part by computer software stored on MEM 1208 and 1222, which is executed by the DP 1206 of the UE 1205 and/or by the DP 1220 of the network node 1202, or by hardware, or by a combination of stored software and hardware and/or firmware.
  • Electronic devices implementing these embodiments of the invention may be one or more components of same such as the above described stored software, hardware, firmware and DP, or a system on a chip, SoC, or an application specific integrated circuit, ASCI.
  • Data processors 1220, 1206 may comprise, for example, at least one of a microprocessor, application-specific integrated chip, ASIC, field-programmable gate array, FPGA, and a microcontroller. Data processors 1220, 1206 may comprise at least one, and in some embodiments more than one, processing core. Memory 1222, 1208 may comprise, for example, at least one of magnetic, optical and holographic or other kind or kinds of memory. At least part of memory 1222, 1208 may be comprised in data processor 1220 and/or 1206. At least part of memory 1222, 1208 may be comprised externally to data processor 1220 and/or 1206.
  • the various embodiments of the UE 1205 can include, but are not limited to personal portable digital devices having wireless communication capabilities, including but not limited to smart devices, mobile devices, wireless handsets, cellular telephones, navigation devices, laptop/palmtop/tablet computers, digital cameras and music devices, and Internet appliances.
  • personal portable digital devices having wireless communication capabilities, including but not limited to smart devices, mobile devices, wireless handsets, cellular telephones, navigation devices, laptop/palmtop/tablet computers, digital cameras and music devices, and Internet appliances.
  • Various embodiments of the computer readable MEMs 1208 and 1222 include any data storage technology type which is suitable to the local technical environment, which includes but not limited to semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, removable memory, disc memory, flash memory, DRAM, SRAM, EEPROM and the like.
  • Various embodiments of the DPs 1206 and 1220 include but are not limited to general purpose computers, special purpose computers, microprocessors, digital signal processors, DSPs, and multi-core processors.
  • the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as user equipment to perform any of the processes described as in FIG. 1 to 12. Therefore, in certain embodiments, a non-transitory computer- readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.
  • an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIG. 1 through 12.
  • circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry.
  • circuitry may be a combination of hardware circuits and software, and at least one memory that work together to cause an apparatus to perform various processes or functions.
  • circuitry may be hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that include software, such as firmware for operation.
  • Software in circuitry may not be present when it is not needed for the operation of the hardware.
  • a method may comprise transmitting, from a network node to a user equipment, at least one signal including at least one indication.
  • the at least one indication may indicates at least one condition for multiplexing at least one scheduling request into an uplink data channel in an uplink transmission.
  • the method may further comprise receiving, at the network node, the at least one scheduling request multiplexed into the uplink data channel.
  • the at least one condition may comprise at least one information related to at least one of the at least one scheduling request, the uplink data channel, or an uplink control channel for the at least one scheduling request.
  • a method may comprise transmitting, from a network node to a user equipment, at least one signal including at least one indication indicating a list of scheduling requests.
  • the list may include at least one scheduling request allowed to be multiplexed into an uplink data channel in an uplink transmission.
  • the method may further comprise receiving, at the network node, the at least one scheduling request of the list multiplexed into the uplink data channel.
  • a method may comprise receiving, from a network node, at least one signal including at least one indication indicating at least one condition for multiplexing at least one scheduling request into an uplink data channel in an uplink transmission.
  • the method may further comprise determining, at a user equipment, the at least one condition for multiplexing at least one scheduling request into an uplink data channel is satisfied.
  • the method may further comprise multiplexing, at the user equipment, the at least one scheduling request into the uplink data channel.
  • the method may further comprise transmitting, to the network node, the at least one scheduling request multiplexed into the uplink data channel.
  • the at least one condition comprises at least one information related to at least one of the at least one scheduling request, the uplink data channel, or an uplink control channel for the at least one scheduling request.
  • a method may comprise receiving, from a network node, at least one signal including at least one indication indicating a list of scheduling requests.
  • the list includes at least one scheduling request allowed to be multiplexed into an uplink data channel in an uplink transmission.
  • the method may further comprise multiplexing, at a user equipment, the at least one scheduling request of the list into the uplink data channel.
  • the method may further comprise transmitting, to the network node, the at least one scheduling request of the list multiplexed into the uplink data channel.
  • transmission of the at least one scheduling request may be triggered by a logical channel or a medium access control control element in medium access control layer.
  • the at least one scheduling request may be associated to at least one uplink control channel.
  • the uplink data channel may comprise an uplink shared channel or a physical uplink shared channel.
  • the at least one uplink control channel may comprise a physical uplink control channel.
  • the at least one may comprise at least one of: grant priority of the uplink data channel, priority of logical channel related to the at least one scheduling request, type of medium access control control element related to the at least one scheduling request, configuration of the at least one scheduling request, configured grant configuration or configured grant index of the uplink data channel in case the uplink data channel is a physical uplink shared channel of configured grant, type of grant of the uplink data channel, allocated and/or granted resource of the uplink data channel, transmission duration of the uplink data channel, reliability requirement of the uplink data channel, subcarrier spacing of the uplink data channel, resource allocation in the uplink data channel for control information multiplexing, serving cell that the uplink data channel operates in, contents of the medium access control protocol data unit of the uplink data channel, at least another information associated with grant of the uplink data channel, type of at least another uplink control information to be multiplexed into the uplink data channel, or priority of at least another uplink control information to be multiplexed into the uplink data channel.
  • the at least one indication may indicate allowing the user equipment to determine at least one of: a resource allocation in an uplink data channel, a number of resource elements to be reserved in an uplink data channel, or a resource element allocation pattern for the multiplexing the at least one scheduling request into uplink data channel, based on configuration of the at least one scheduling request associated with an uplink control channel resource that overlaps with the uplink data channel at least in time domain.
  • the determination may be further based on the at least one information.
  • the at least one indication may comprise indication indicating that the at least one scheduling request is allowable to be multiplexed with the uplink data channel, in case the at least one condition is satisfied.
  • the at least one indication may comprise indication indicating at least one of resource allocation, a number of resource elements, or a resource element allocation pattern of resource elements for the multiplexing of the at least one scheduling request into the uplink data channel.
  • the at least one indication may indicate whether the at least one scheduling request is to be allocated with at least one of contiguous resource elements or non-contiguous resource elements in frequency domain or in time domain.
  • the at least one indication may indicate whether the at least one scheduling request is to be multiplexed into one or more of the one or more repetitions of one uplink data channel.
  • the at least one indication may indicate whether the at least one scheduling request is to be multiplexed into one or more of the more than one uplink data channels.
  • the at least one indication may further indicates at least one carrier that the at least one scheduling request is to be multiplexed on.
  • the at least one indication may be included in the at least one signal comprising at least one of a dynamic grant, radio resource control signal for at least one of configured grant configuration, logical channel, or scheduling request configuration.
  • a method may comprise determining, at a user equipment, in response to at least one uplink control channel for at least one scheduling request overlap with an uplink data channel, at least one of resource allocation, a number of resource elements, or a resource element allocation pattern for multiplexing the at least one scheduling request into the uplink data channel, based on at least one information related to at least one of the at least one scheduling request, the uplink data channel, or the at least one uplink control channel for the at least one scheduling request.
  • the method may further comprise transmitting, from the user equipment to a network node, the at least one scheduling request multiplexed in the uplink data channel.
  • a method may comprise transmitting, from a network node, a downlink configuration signal including resource information of at least one uplink control channel for at least one scheduling request.
  • the method may further comprise receiving, at the network node, the at least one scheduling request multiplexed in an uplink data channel.
  • the multiplexed at least one scheduling request may be received based on determination, at a user equipment, of at least one of resource allocation, a number of resource elements, or a resource element allocation pattern for multiplexing the at least one scheduling request into the uplink data channel, in response to the resource information indicating the at least one uplink control channel for the at least one scheduling request overlap with the uplink data channel.
  • the determination may be based on at least one information related to at least one of the at least one scheduling request, the uplink data channel, or the at least one uplink control channel for the at least one scheduling request.
  • the variants discussed in the following may be, but not limited, for the fifth or the sixth embodiment.
  • the uplink data channel may comprise an uplink shared channel or a physical uplink shared channel.
  • the at least one uplink control channel may comprise a physical uplink control channel.
  • the overlap may occur in time domain.
  • the at least one information may comprise at least one of: index of scheduling request configuration associated to the at least one uplink control channel for the at least one scheduling request, logical channel corresponding to scheduling request configuration associated to the at least one uplink control channel for the at least one scheduling request, format of the at least one uplink control channel for the at least one scheduling request, resource allocation of the uplink control channel for the at least one scheduling request, grant priority of the uplink data channel, priority of logical channel related to the at least one scheduling request, type of medium access control control element related to the at least one scheduling request, configuration of the scheduling request, configured grant configuration or configured grant index of the uplink data channel in case the uplink data channel is a physical uplink shared channel of configured grant, type of grant of the uplink data channel, allocated and/or granted resource of the uplink data channel, transmission duration of the uplink data channel, reliability requirement of the uplink data channel, subcarrier spacing of the uplink data channel, resource allocation in
  • the number of resource elements may be associated to the at least one information related to the uplink data channel.
  • the uplink data channel may be associated to at least one configured grant configuration.
  • the at least one configured grant configuration may comprise at least one configured grant occasion that at least partially overlap with the at least one uplink control channel in time domain.
  • the determining at least one of resource allocation, a number of resource elements, or a resource element allocation pattern for multiplexing may be based on the at least one of configured grant configuration or configuration of the at least one uplink control channel.
  • an apparatus may comprise at least one processor and at least one memory and computer program code.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to perform the method according to any of the first, second, third, fourth, fifth, and sixth embodiment, and any of their variants.
  • an apparatus may comprise means for performing the method according to any of the first, second, third, fourth, fifth, and sixth embodiment, and any of their variants.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing the method according to any of the first, second, third, fourth, fifth, and sixth embodiment, and any of their variants.
  • a computer readable medium of wireless communication storing a program of instructions, execution of which by a processor configuring an apparatus to at least perform according to any of the first, second, third, fourth, fifth, and sixth embodiment, and any of their variants.
  • a computer program comprising instructions stored thereon for performing a method according to any of the first, second, third, fourth, fifth, and sixth embodiment, and any of their variants.

Landscapes

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

Abstract

Selon un premier mode de réalisation, un procédé peut comprendre la réception d'au moins un signal comprenant au moins une indication indiquant au moins une condition pour multiplexer au moins une requête de planification dans un canal de données de liaison montante dans une transmission en liaison montante. Le procédé peut en outre consister à déterminer, au niveau d'un équipement utilisateur, que ladite condition pour multiplexer au moins une requête de planification dans un canal de données de liaison montante est satisfaite. Le procédé peut en outre comprendre le multiplexage, au niveau de l'équipement utilisateur, de la ou des requêtes de planification dans le canal de données de liaison montante; et la transmission de la ou des requêtes de planification multiplexées dans le canal de données de liaison montante. La ou les conditions comprennent au moins une information relative à la ou aux demandes de planification, au canal de données de liaison montante ou à un canal de commande de liaison montante pour la ou les demandes de planification.
PCT/IB2021/052931 2020-05-13 2021-04-08 Appareil et procédés de multiplexage de requête de planification WO2021229319A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063024309P 2020-05-13 2020-05-13
US63/024,309 2020-05-13

Publications (1)

Publication Number Publication Date
WO2021229319A1 true WO2021229319A1 (fr) 2021-11-18

Family

ID=75539724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/052931 WO2021229319A1 (fr) 2020-05-13 2021-04-08 Appareil et procédés de multiplexage de requête de planification

Country Status (1)

Country Link
WO (1) WO2021229319A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180167933A1 (en) * 2016-12-13 2018-06-14 Sharp Laboratories Of America, Inc. Base stations, user equipments, and related communication methods
WO2020026305A1 (fr) * 2018-07-30 2020-02-06 株式会社Ｎｔｔドコモ Terminal utilisateur
US20200228248A1 (en) * 2019-04-02 2020-07-16 Intel Corporation Prioritization of services for control and data transmission for new radio systems
WO2020146247A2 (fr) * 2019-01-09 2020-07-16 Idac Holdings, Inc. Procédés, appareil et systèmes pour une signalisation de commande améliorée de transmissions ultra-fiables
EP3780848A1 (fr) * 2019-08-15 2021-02-17 Apple Inc. Gestion de collision d'informations de contrôle de liaison montante

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180167933A1 (en) * 2016-12-13 2018-06-14 Sharp Laboratories Of America, Inc. Base stations, user equipments, and related communication methods
WO2020026305A1 (fr) * 2018-07-30 2020-02-06 株式会社Ｎｔｔドコモ Terminal utilisateur
EP3833087A1 (fr) * 2018-07-30 2021-06-09 Ntt Docomo, Inc. Terminal utilisateur
WO2020146247A2 (fr) * 2019-01-09 2020-07-16 Idac Holdings, Inc. Procédés, appareil et systèmes pour une signalisation de commande améliorée de transmissions ultra-fiables
US20200228248A1 (en) * 2019-04-02 2020-07-16 Intel Corporation Prioritization of services for control and data transmission for new radio systems
EP3780848A1 (fr) * 2019-08-15 2021-02-17 Apple Inc. Gestion de collision d'informations de contrôle de liaison montante

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP RP-193233
NOKIA ET AL: "Intra-UE Prioritization for Resource Conflicts Involving SR", vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 15 August 2019 (2019-08-15), XP051767295, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_107/Docs/R2-1909498.zip> [retrieved on 20190815] *

Similar Documents

Publication Publication Date Title
CN109392175B (zh) 调度请求的发送方法、调度请求的处理方法及相关设备
CN110225547B (zh) 一种调度请求发送、接收方法、终端及网络侧设备
US20230217445A1 (en) Sidelink communication method, terminal device and network device
JP6568944B2 (ja) 複数の時間インスタンスにおけるアップリンクリソーススケジューリング
CN106954277B (zh) 一种调度请求处理方法和装置
US20160066328A1 (en) Scheduling method, user equipment, and base station
US20200137785A1 (en) User equipment (ue) and method for managing buffer status report (bsr) for multiple-numerology operation
WO2013023684A1 (fr) Planification de communications
JP2022525732A (ja) 情報伝送方法、端末デバイス及びネットワークデバイス
EP3852461B1 (fr) Procédé d&#39;attribution de ressource et terminal
US20210298040A1 (en) Method and device for determining and configuring scheduling request resource, and storage medium
AU2019267579A1 (en) Communication method and device
CA3115860C (fr) Procede et dispositif de communication sans fil
US11678310B2 (en) Method for determining transmission resources, terminal device and network device
CN109478957A (zh) 一种控制信息传输的方法、终端设备和网络设备
EP3627929B1 (fr) Procédé d&#39;attribution de ressources, dispositif terminal, et dispositif de réseau
JP2019502278A (ja) 無線通信の方法、ネットワーク装置及び端末機器
CN111148225B (zh) 资源调度方法、装置及设备
CN112312557B (zh) 一种发送和接收调度请求的方法及通信装置
CN114391230A (zh) 上行控制信息复用传输的方法和装置
WO2022156432A1 (fr) Procédé et appareil de transmission de requête d&#39;ordonnancement
WO2021229319A1 (fr) Appareil et procédés de multiplexage de requête de planification
WO2024026756A1 (fr) Procédés et appareils de transmission améliorée sur une ressource préconfigurée
US20220393806A1 (en) Method and device for determining transmission priority
WO2023284485A1 (fr) Procédé et appareil de transmission de signal

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

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

Country of ref document: EP

Kind code of ref document: A1