[go: up one dir, main page]

WO2023201675A1 - Génération de blocs de transport pour des communications sans fil - Google Patents

Génération de blocs de transport pour des communications sans fil Download PDF

Info

Publication number
WO2023201675A1
WO2023201675A1 PCT/CN2022/088372 CN2022088372W WO2023201675A1 WO 2023201675 A1 WO2023201675 A1 WO 2023201675A1 CN 2022088372 W CN2022088372 W CN 2022088372W WO 2023201675 A1 WO2023201675 A1 WO 2023201675A1
Authority
WO
WIPO (PCT)
Prior art keywords
grant
transmission
communication node
physical channel
pusch
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/CN2022/088372
Other languages
English (en)
Inventor
Shuaihua KOU
Xianghui HAN
Wei Gou
Junfeng Zhang
Peng Hao
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN202280093623.0A priority Critical patent/CN118891942A/zh
Priority to PCT/CN2022/088372 priority patent/WO2023201675A1/fr
Publication of WO2023201675A1 publication Critical patent/WO2023201675A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • This document is directed generally to physical channel transmissions in one or more slots for wireless communication.
  • a physical uplink shared channel may be transmitted over one or more slots.
  • PUSCH physical uplink shared channel
  • MAC medium access control
  • PDU MAC protocol data unit
  • a method for wireless communication includes: determining, with at least one communication node, that a transport block over a plurality of slots for a physical channel is configured for a grant; and determining, with a medium access control (MAC) layer of the at least one communication node, whether to trigger a transmission for the grant.
  • MAC medium access control
  • a device such as a network device.
  • the device may include one or more processors and one or more memories, wherein the one or more processors are configured to read computer code from the one or more memories to implement the method above.
  • a computer program product may include a non-transitory computer-readable program medium with computer code stored thereupon, the computer code, when executed by one or more processors, causing the one or more processors to implement the method above.
  • FIG. 1 shows a block diagram of an example of a wireless communication system.
  • FIG. 2 shows a flow chart of an example method for wireless communication.
  • FIG. 3 shows a diagram of an example transport block on multiple slots (TBoMS) transmission.
  • FIG. 4 shows a diagram of a second example of a TBoMS transmission.
  • FIG. 5 shows a diagram of a third example of a TBoMS transmission.
  • FIG. 6 shows a block diagram of an example protocol stack for a communication node.
  • the present description describes various embodiments of systems, apparatuses, devices, and methods for wireless communications involving scheduling signal transmission.
  • Fig. 1 shows a diagram of an example wireless communication system 100 including a plurality of communication nodes (or just nodes) that are configured to wirelessly communicate with each other.
  • the communication nodes include at least one user device 102 and at least one wireless access node 104.
  • the example wireless communication system 100 in Fig. 1 is shown as including two user devices 102, including a first user device 102 (1) and a second user device 102 (2) , and one wireless access nodes 104.
  • various other examples of the wireless communication system 100 that include any of various combinations of one or more user devices 102 and/or one or more wireless access nodes 104 may be possible.
  • a user device as described herein such as the user device 102, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, capable of communicating wirelessly over a network.
  • a user device may comprise or otherwise be referred to as a user terminal, a user terminal device, or a user equipment (UE) .
  • UE user equipment
  • a user device may be or include, but not limited to, a mobile device (such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved for long periods of time, such as appliances, other relatively heavy devices including Internet of things (IoT) , or computing devices used in commercial or industrial environments, as non-limiting examples) .
  • a mobile device such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved
  • a user device 102 may include transceiver circuitry 106 coupled to an antenna 108 to effect wireless communication with the wireless access node 104.
  • the transceiver circuitry 106 may also be coupled to a processor 110, which may also be coupled to a memory 112 or other storage device.
  • the memory 112 may store therein instructions or code that, when read and executed by the processor 110, cause the processor 110 to implement various ones of the methods described herein.
  • a wireless access node as described herein such as the wireless access node 104, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, and may comprise one or more base stations or other wireless network access points capable of communicating wirelessly over a network with one or more user devices and/or with one or more other wireless access nodes 104.
  • the wireless access node 104 may comprise a 4G LTE base station, a 5G NR base station, a 5G central-unit base station, a 5G distributed-unit base station, a next generation Node B (gNB) , an enhanced Node B (eNB) , or other similar or next-generation (e.g., 6G) base stations, in various embodiments.
  • a wireless access node 104 may include transceiver circuitry 114 coupled to an antenna 116, which may include an antenna tower 118 in various approaches, to effect wireless communication with the user device 102 or another wireless access node 104.
  • the transceiver circuitry 114 may also be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device.
  • the memory 122 may store therein instructions or code that, when read and executed by the processor 120, cause the processor 120 to implement one or more of the methods described herein.
  • two communication nodes in the wireless system 100 such as a user device 102 and a wireless access node 104, two user devices 102 without a wireless access node 104, or two wireless access nodes 104 without a user device 102-may be configured to wirelessly communicate with each other in or over a mobile network and/or a wireless access network according to one or more standards and/or specifications.
  • the standards and/or specifications may define the rules or procedures under which the communication nodes can wirelessly communicate, which, in various embodiments, may include those for communicating in millimeter (mm) -Wave bands, and/or with multi-antenna schemes and beamforming functions.
  • the standards and/or specifications are those that define a radio access technology and/or a cellular technology, such as Fourth Generation (4G) Long Term Evolution (LTE) , Fifth Generation (5G) New Radio (NR) , or New Radio Unlicensed (NR-U) , as non-limiting examples.
  • 4G Fourth Generation
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • NR New Radio
  • NR-U New Radio Unlicensed
  • the communication nodes are configured to wirelessly communicate signals between each other.
  • a communication in the wireless system 100 between two communication nodes can be or include a transmission or a reception, and is generally both simultaneously, depending on the perspective of a particular node in the communication.
  • the first node may be referred to as a source or transmitting node or device
  • the second node may be referred to as a destination or receiving node or device
  • the communication may be considered a transmission for the first node and a reception for the second node.
  • a single communication node may be both a transmitting/source node and a receiving/destination node simultaneously or switch between being a source/transmitting node and a destination/receiving node.
  • particular signals can be characterized or defined as either an uplink (UL) signal, a downlink (DL) signal, or a sidelink (SL) signal.
  • An uplink signal is a signal transmitted from a user device 102 to a wireless access node 104.
  • a downlink signal is a signal transmitted from a wireless access node 104 to a user device 102.
  • a sidelink signal is a signal transmitted from a one user device 102 to another user device 102, or a signal transmitted from one wireless access node 104 to a another wireless access node 104.
  • a first/source user device 102 directly transmits a sidelink signal to a second/destination user device 102 without any forwarding of the sidelink signal to a wireless access node 104.
  • signals communicated between communication nodes in the system 100 may be characterized or defined as a data signal or a control signal.
  • a data signal is a signal that includes or carries data, such multimedia data (e.g., voice and/or image data)
  • a control signal is a signal that carries control information that configures the communication nodes in certain ways in order to communicate with each other, or otherwise controls how the communication nodes communicate data signals with each other.
  • certain signals may be defined or characterized by combinations of data/control and uplink/downlink/sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.
  • a physical channel corresponds to a set of time-frequency resources used for transmission of a signal.
  • Different types of physical channels may be used to transmit different types of signals.
  • physical data channels (or just data channels) are used to transmit data signals
  • physical control channels (or just control channels) are used to transmit control signals.
  • Example types of physical data channels include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PSSCH physical sidelink shared channel
  • example types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals.
  • a particular type of physical channel is also used to refer to a signal that is transmitted on that particular type of physical channel, and/or a transmission on that particular type of transmission.
  • a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission.
  • a communication node transmitting or receiving a PDSCH means that the communication node is transmitting or receiving a signal on a PDSCH.
  • a control signal that a communication node transmits may include control information comprising the information necessary to enable transmission of one or more data signals between communication nodes, and/or to schedule one or more data channels (or one or more transmissions on data channels) .
  • control information may include the information necessary for proper reception, decoding, and demodulation of a data signals received on physical data channels during a data transmission, and/or for uplink scheduling grants that inform the user device about the resources and transport format to use for uplink data transmissions.
  • control information includes downlink control information (DCI) that is transmitted in the downlink direction from a wireless access node 104 to a user device 102.
  • DCI downlink control information
  • control information includes uplink control information (UCI) that is transmitted in the uplink direction from a user device 102 to a wireless access node 104, or sidelink control information (SCI) that is transmitted in the sidelink direction from one user device 102 (1) to another user device 102 (2) .
  • DCI downlink control information
  • UCI uplink control information
  • SCI sidelink control information
  • two communication nodes may communicate (including transmit and receive) a transport block over one or more slots. This transmission in one or more slots is referred to as transport block over multiple slots (TBoMS) transmission.
  • a transport block is carried by a physical channel, including a PUSCH, a PDSCH or a PSSCH.
  • a PUSCH is scheduled by an uplink grant.
  • a PSSCH is scheduled by a sidelink grant.
  • example embodiments are described herein with reference to the physical channel being a PUSCH scheduled by an uplink grant. However, all the embodiments may also be applicable to a PSSCH scheduled by a sidelink grant by using PSSCH instead of PUSCH and, correspondingly, using sidelink grant instead of uplink grant.
  • the number of slots for a TBoMS transmission may be indicated by the wireless access node 104.
  • a transport block size (TBS) may be calculated based on the total resources of the configured slots.
  • a redundancy version (RV) may be configured for the TBoMS transmission.
  • a transmission may be configured with an associated priority.
  • the priority may be a physical layer priority or a logical channel priority. For a PUSCH duration of a first uplink grant overlapping with a PUSCH duration of a second uplink grant, if the second uplink grant has higher priority and has not been de-prioritized, one or more communication nodes may determine or consider the first uplink grant as a de-prioritized uplink grant and the second uplink grant as a prioritized uplink grant.
  • one or more communication nodes in the wireless system 100 may determine or consider the first uplink grant as a de-prioritized uplink grant.
  • a hybrid automatic repeat request (HARQ) entity of a communication node in the wireless system 100 may be configured to identify a HARQ process associated with the given uplink grant.
  • HARQ hybrid automatic repeat request
  • Fig. 2 shows a flow chart of an example method 200 for wireless communication related to triggering a transmission for a physical channel.
  • at least one communication node may determine that a transport block over a plurality of slots for a physical channel is configured for a grant.
  • the at least one communication node may include at least one wireless access node 104, at least one user device 102, or a combination of at least one wireless access node 104 and at least one user device 102.
  • the physical channel may include a PUSCH, a PDSCH, or a PSSCH.
  • the grant may be or include an uplink grant.
  • the grant may be or include a sidelink grant.
  • at least one communication node may schedule a transmission.
  • the wireless access node 104 may schedule a transmission, such as a PUSCH transmission, for the user device 102.
  • the user device 102 may determine whether to actually perform the transmission after it is scheduled.
  • a medium access control (MAC) layer or entity of the at least one communication node may determine whether to trigger a transmission for the grant.
  • the MAC layer of the at least one communication node may trigger the transmission or not trigger the transmission according to the determination whether to trigger the transmission. For example, after a transmission scheduled, such as by the wireless access node 104, the MAC layer (such as the MAC layer 604 of Fig. 6 described below) of the user device 102 may determine whether to actually perform the transmission.
  • the user device 102 may perform the transmission, such as by transmitting the PUSCH for example. In addition, if the MAC layer determines not to trigger the transmission, and in turn does not trigger the transmission, then the user device 102 may not transmit the PUSCH.
  • the determination of whether to trigger a transmission for the grant may include determining that a number of slots for the grant is greater than one, and in response, may determine to trigger the transmission.
  • the at least one communication node may trigger the transmission.
  • the at least one communication node may determine to generate a MAC protocol data unit (PDU) for the uplink grant for which the TBoMS transmission is configured.
  • the uplink grant may include a dynamic uplink grant. More specifically, the at least one communication node may determine to generate a MAC PDU for the uplink grant irrespective of whether the uplink grant is determined to be a prioritized uplink grant. That is, the at least one communication node may generate the MAC PDU even after determining that the uplink grant is a de-prioritized uplink grant.
  • the uplink grant configured with TBoMS transmission may include a configured uplink grant.
  • the at least one communication node may determine to generate a MAC PDU for the configured uplink grant irrespective of whether the PUSCH of the configured uplink grant overlaps with another PUSCH of a dynamic uplink grant. That is, the at least one communication node may generate the MAC PDU even after determining that the PUSCH of the configured uplink grant overlaps with another PUSCH of the dynamic uplink grant.
  • the dynamic uplink grant may include an uplink grant received on the PDCCH or in a random access response.
  • the another PUSCH may include a PUSCH associated with a PRACH transmission.
  • the at least one communication node may set a HARQ process ID for the PUSCH of the configured uplink grant.
  • the MAC layer (or entity) of the at least one communication device may deliver the MAC PDU to a physical layer (or entity) of the at least one communication node (e.g., the physical layer entity 602 of Fig. 6 described below) , and trigger the transmission.
  • the transmission may be a new transmission or retransmission.
  • the MAC entity of the at least one communication node may generate the MAC PDU for the uplink grant.
  • the MAC entity of the at least one communication node may obtain the MAC PDU from a multiplexing and assembly entity (layer) of the at least one communication node for the transmission. For example, even after the at least one communication node may determine or consider the uplink grant as a de-prioritized uplink grant, the MAC layer may obtain the MAC PDU from the multiplexing and assembly entity. When the MAC layer obtains the MAC PDU, the MAC PDU, the uplink grant, and the HARQ information of the transport block (TB) are delivered to the identified HARQ process associated with the uplink grant. Also, the MAC entity may instruct the identified HARQ entity/process to trigger a new transmission.
  • a multiplexing and assembly entity layer
  • the MAC entity may ignore the given uplink grant. Also, for the uplink grant for which the TBoMS transmission is configured, the MAC entity may deliver the uplink grant and the HARQ entity/process information (e.g., redundancy version) of the TB to the identified HARQ process. Then, the MAC entity may instruct the identified HARQ entity/process to trigger a retransmission.
  • the MAC entity may deliver the uplink grant and the HARQ entity/process information (e.g., redundancy version) of the TB to the identified HARQ process. Then, the MAC entity may instruct the identified HARQ entity/process to trigger a retransmission.
  • Fig. 3 illustrates an example of the TBoMS transmission, where the physical channel comprises a PUSCH.
  • the TBoMS transmission includes a PUSCH transmitted in two slots, including a Slot 1 and a Slot 2.
  • the wireless access node 104 may configure PUSCH 1 to be transmitted on the two slots (i.e., Slot 1 and Slot 2) . Since the TBoMS transmission for PUSCH 1 is transmitted on Slot 1 and Slot 2, the MAC layer of the at least one communication node may obtain the MAC PDU from the multiplexing and assembly entity.
  • the MAC entity may deliver the uplink grant and the HARQ process information (e.g., redundancy version) of the TB to the HARQ process for PUSCH 1.
  • the HARQ process information e.g., redundancy version
  • a second PUSCH overlaps PUSCH 1 in slot 1.
  • the at least one communication node may determine or consider the uplink grant for PUSCH 2 as a prioritized uplink grant.
  • the at least one communication node may determine or consider the uplink grant for PUSCH 1 as a de-prioritized uplink grant.
  • the MAC entity of the at least one communication node may obtain the MAC PDU from the multiplexing and assembly entity for PUSCH 1.
  • the MAC entity may deliver the uplink grant and the HARQ process information (e.g., redundancy version) of the TB to the HARQ process of PUSCH 1.
  • PUSCH 1 corresponds to a configured uplink grant and PUSCH 2 corresponds to a dynamic uplink grant.
  • PUSCH 1 overlaps with PUSCH 2 in slot 1.
  • the MAC entity of the at least one communication node may obtain the MAC PDU from the multiplexing and assembly entity for PUSCH 1.
  • the MAC entity may deliver the uplink grant and the HARQ process information (e.g., redundancy version) of the TB to the HARQ process of PUSCH 1.
  • the MAC entity of the at least one communication node may deliver the MAC PDU to a physical (PHY) layer (or entity) of the at least one communication node and trigger a new transmission or retransmission.
  • the MAC entity may obtain the MAC PDU from the multiplexing and assembly entity for transmission, or the MAC entity may deliver the uplink grant and the HARQ process information (e.g., redundancy version) of the TB to the identified HARQ process/entity.
  • the MAC entity may obtain the MAC PDU from the multiplexing and assembly entity for transmission, or the MAC entity may deliver the uplink grant and the HARQ process information (e.g., redundancy version) of the TB to the identified HARQ process/entity.
  • the slots for the TBoMS transmission are configured (or indicated) by the wireless access node 104.
  • the wireless access node 104 may configure two slots for the PUSCH 1 transmission, as shown in Fig. 3. Accordingly, the number of slots for the TBoMS transmission is 2.
  • the MAC entity of the at least one communication node may deliver the MAC PDU to the physical layer and trigger a new transmission or retransmission for PUSCH 1.
  • the slot for the TBoMS transmission can be the slots that are actually used for transmitting the TB.
  • the MAC entity of the at least one communication node may deliver the MAC PDU to a physical (PHY) layer (or entity) of the at least one communication node and trigger a new transmission or retransmission.
  • PHY physical
  • the MAC entity may deliver the MAC PDU to the physical layer and trigger a new transmission or retransmission for PUSCH 1. If the PUSCH 1 in slot 1 is canceled due to the overlapping with PUSCH 2, then the slot that is actually used for transmitting PUSCH 1 is Slot 2.
  • the MAC layer may not deliver the MAC PDU to the physical layer and/or not trigger a new transmission or retransmission if this uplink grant is considered as de-prioritized uplink grant. If this uplink grant is considered (or determined) as prioritized grant, the MAC layer should deliver the MAC PDU to the physical layer and trigger a new transmission or retransmission for the uplink grant.
  • Fig. 4 shows a diagram of another example of a TBoMS transmission.
  • the wireless access node 104 may configure a third PUSCH 3 to be transmitted in Slot 3.
  • only one slot is used for the PUSCH 3 transmission.
  • the wireless access node may configure PUSCH 1 to be transmitted on Slot 1 and Slot 2.
  • Fig. 4 shows that the PUSCH 1 transmission in slot 2 is canceled. As a result of the cancellation, only one slot-Slot 1-is actually used for the PUSCH 1 transmission.
  • the MAC layer does not deliver the MAC PDU to the physical layer or trigger a new transmission or retransmission for PUSCH 1 or PUSCH 3.
  • the at least one communication node may prioritize and de-prioritize uplink grants according to the following: If the first PUSCH transmission in any one of the plurality of slots is canceled by a DCI indication, or is canceled by a PUCCH transmission with a higher priority, or overlaps with another PUSCH transmission corresponding to a uplink grant that has a higher or equal priority, the at least one communication node may determine or consider the first uplink grant as a de-prioritized uplink grant.
  • the at least one communication node may determine or consider the first uplink grant as a prioritized uplink grant.
  • the at least one communication node may determine or consider the first uplink grant as a de-prioritized uplink grant and the second uplink grant as a prioritized uplink grant.
  • the at least one communication node may prioritize and de-prioritize uplink grants according to the following: If the first PUSCH transmission in each of the plurality of slots is canceled by the DCI indication, or is canceled by a PUCCH transmission with higher priority, or overlaps with the another PUSCH transmission corresponding to an uplink grant that has a higher or equal priority, the at least one communication node may determine or consider the first uplink grant as a de-prioritized uplink grant.
  • the first uplink grant is considered (or determined) as a prioritized uplink grant.
  • the at least one communication node may ignore the first configured uplink grant or may not trigger a transmission for the first configured uplink grant if the first PUSCH transmission (or time domain resource, duration) in any one of the plurality of slots overlaps with a second PUSCH transmission (or time domain resource, duration) corresponding of a second dynamic uplink grant.
  • the at least one communication node may ignore the first configured uplink grant or may not trigger a transmission for the first configured uplink grant if the first PUSCH transmission (or time domain resource, duration) in each of the plurality of slots overlaps with a second PUSCH transmission (or time domain resource, duration) corresponding to a second dynamic uplink grant.
  • a first configured uplink grant may correspond to a first PUSCH.
  • a second configured uplink grant may correspond to a second PUSCH.
  • the first PUSCH overlaps with the second PUSCH.
  • the at least one communication node (for example communication node 104) may configure the first PUSCH with a higher physical layer priority and the second PUSCH with a lower physical layer priority.
  • the MAC layer of the at least one communication node (for example communication node 102) may generate the MAC PDU or trigger a transmission for the first configured grant.
  • the MAC layer of the at least one communication node may still generate the MAC PDU or trigger a transmission for the first configured uplink grant. Further, the MAC layer of the at least one communication node may generate the MAC PDU or trigger a transmission for the first configured uplink grant when the at least one communication node has enough time to cancel the second PUSCH and prepare the first PUSCH. Alternatively, when the logical channel based prioritization is not configured, the MAC layer of the at least one communication node may determine the first configured grant as a prioritized uplink grant.
  • the MAC layer of the at least one communication node may still determine the first configured grant as a prioritized uplink grant. Further, the MAC layer of the at least one communication node may determine the first configured grant as a prioritized uplink grant when the at least one communication node has enough time to cancel the second PUSCH and prepare the first PUSCH.
  • an uplink grant corresponds to a PUSCH with TBoMS transmission on a plurality of slots. If the transmission on the first slot of the plurality of slots is canceled or the first slot of the plurality of slots cannot be used for the uplink grant transmission, the MAC layer of the at least one communication node may process the uplink grant by determining a next slot (e.g., a second slot of the plurality of slots) as the first slot for the TBoMS transmission. The processing may include at least one of: determining that the uplink grant is new transmission or retransmission, MAC PDU generation, MAC PDU delivery, or triggering the determined transmission.
  • the uplink grant may include a configured uplink grant or dynamic uplink grant.
  • the MAC layer may process the uplink grant by determining or assuming the next slot (e.g., the third slot of the plurality of slots) as the first slot for the TBoMS transmission.
  • the at least one communication node may proceed in this manner until the last slot is determined or the MAC layer triggers a transmission for the uplink grant or generates a MAC PDU for the uplink grant.
  • the MAC layer of the at least one communication node may process the uplink grant slot by slot. For the first slot of the plurality of the slots, if the MAC layer of the at least one communication node does not deliver the MAC PDU to the physical layer for the uplink grant, or does not instruct the transmission for the uplink grant, the MAC layer of the at least one communication node may further process the uplink grant for the second slot of the plurality of slots. For the processing for the second slot, the MAC layer of the at least one communication node may determine or assume that the second slot is the first slot for the transmission.
  • the MAC layer of the at least one communication node may further process the uplink grant for the third slot of the plurality of slots, and so on.
  • the MAC layer of the at least one communication node may determine or assume that the third slot is the first slot for the transmission.
  • the MAC layer of the at least one communication node may not further process the uplink grant for the subsequent slots.
  • the at least one communication node may proceed in this manner until the last slot, or the MAC layer triggers a transmission for the uplink grant for a slot, or generates a MAC PDU for the uplink grant for a slot.
  • Fig. 5 shows a diagram of a third example of a TBoMS transmission.
  • the TBoMS transmission is for a PUSCH 1 transmitted over three slots, Slot 1, Slot 2, and Slot 3.
  • the MAC layer may process the uplink grant of PUSCH 1. The process includes at least one of determining that the uplink grant is a new transmission or a retransmission, MAC PDU generation, MAC PDU delivery, or triggering the determined transmission.
  • Slot 1 is not available for the PUSCH 1 transmission, for example, Slot 1 is a downlink slot or includes a downlink symbol.
  • the at least one communication node determines PUSCH 1 as configured for a de-prioritized uplink grant based on another channel (e.g., a PUSCH or a PUCCH) having a higher priority that overlaps with PUSCH 1 in Slot 1.
  • the MAC layer may not deliver the MAC PDU to the physical layer for the uplink grant for the transmission of PUSCH 1 in Slot 1 or not instruct a transmission for the uplink grant for the transmission of PUSCH 1 in Slot 1. Then the MAC layer of the at least one communication node may further process the uplink grant of PUSCH 1.
  • the MAC layer of the at least one communication node may determine that Slot 2 (i.e., the next slot) is the first slot for the PUSCH 1 transmission. On the contrary, if Slot 1 is available for the PUSCH 1 transmission and the uplink grant of PUSCH 1 is not determined as a de-prioritized uplink grant, the MAC layer of the at least one communication node may deliver the MAC PDU to the physical layer for the uplink grant for the transmission of PUSCH 1 in Slot 1 or instruct a transmission for the uplink grant for the transmission of PUSCH 1 in Slot 1. Then the MAC layer of the at least one communication node may not process the uplink grant of PUSCH 1 for Slot 2 or Slot 3.
  • Slot 2 i.e., the next slot
  • the uplink grant of PUSCH 1 is determined as a de-prioritized uplink grant since another channel with a higher priority overlaps with PUSCH 1 in Slot 2.
  • the MAC layer of the at least one communication node may not deliver the MAC PDU to the physical layer for the uplink grant for the transmission of PUSCH 1 in Slot 2 or not instruct a transmission for the uplink grant for the transmission of PUSCH 1 in Slot 2.
  • the MAC layer of the at least one communication node may further process the uplink grant of PUSCH 1.
  • the MAC layer of the at least one communication node may determine that Slot 3 (i.e., the next slot) is the first slot for the PUSCH 1 transmission.
  • the at least one communication node may determine or consider the transmission in each of the plurality of slots as configured for a separate uplink grant.
  • the MAC layer of the at least one communication node may process the uplink grant corresponding to each slot of the plurality of slots separately.
  • the separate uplink grant may have the same redundancy version (RV) .
  • Each separate uplink grant may correspond to the sum of the resource in the plurality of slots.
  • the sum of the resource in the plurality of slots may be used for determining the transport block size or MAC PDU generation for the separate uplink grant.
  • the uplink grant may include a configured uplink grant or dynamic uplink grant. For each separate uplink grant, the PUSCH transmission (or time domain resource, duration) in the corresponding slot is used for determining the overlapping.
  • the uplink grant corresponds to PUSCH 1, which is transmitted on Slot 1 and Slot 2.
  • the at least one communication node may determine or consider the corresponding uplink grant as two separate uplink grants, including a first uplink grant and a second uplink grant.
  • the first uplink grant corresponds to PUSCH 1 transmitted in Slot 1
  • the second uplink grant corresponds to PUSCH 1 transmitted in Slot 2.
  • the MAC layer may process the two uplink grants separately.
  • the PUSCH 1 duration in Slot 1 is used for determining the overlapping with other signals.
  • the PUSCH 1 duration in Slot 2 is used for determining the overlapping with other signals.
  • the two uplink grants may have the same RV for the PUSCH 1.
  • the sum of the resource in Slot 1 and Slot 2 are used for determining the transport block size or MAC PDU generation for the first uplink grant or the second uplink grant.
  • the at least one communication node may configure at least one of a PUCCH or a PUSCH with a priority.
  • the PUSCH may or not be configured with TBoMS transmission.
  • the wireless access node 104 may further configure the higher priority channel to be multiplexed with a lower priority channel.
  • a first uplink grant corresponds to the first PUSCH transmission. For a first uplink grant, if the first PUSCH overlaps with another PUSCH for which the MAC layer has triggered the transmission or the MAC layer has generated the MAC PDU, the at least one communication node may determine or consider the first uplink grant as a de-prioritized uplink grant.
  • the triggered transmission for the another PUSCH may be a new transmission or retransmission.
  • the at least one communication node may determine or consider the first uplink grant as a prioritized uplink grant.
  • the first uplink grant or the uplink grant of the other PUSCH may be configured as a grant, or received dynamically on the PDCCH, in a Random Access Response.
  • the at least one communication node may determine or consider the first uplink grant as prioritized uplink grant if no second PUSCH overlaps with the first PUSCH of the first uplink grant, where the MAC layer has triggered the transmission or generated MAC PDU for the second PUSCH.
  • a PUSCH may be configured with a TBoMS transmission on a plurality of slots.
  • the at least one communication node may use a sum of the PUSCH duration on one or more slots of the plurality of slots for a selection of the logical channels.
  • the at least one communication node may use the sum of the PUSCH duration on all the plurality of slots for the selection of the logical channels.
  • the at least one communication node may transmit a PUSCH of a TBoMS transmission on Z slots.
  • the PUSCH occupies Y symbols in the time domain.
  • the at least one communication node may use the duration of (Z*Y) symbols for the selection of the logical channels for the PUSCH.
  • the at least one communication node may use the PUSCH duration in one slot of the plurality of the slots for the selection of the logical channels. More specifically, the duration of Y symbols may be used for the selection of the logical channels for the PUSCH.
  • the at least one communication node may map the data of the selected logical channels to the PUSCH, or the data of the selected logical channels may be carried or transmitted by the PUSCH.
  • PUSCH 1 is transmitted on Slot 1 and Slot 2.
  • Slot 1 or Slot 2 suppose PUSCH 1 occupies 7 symbols.
  • LCH 0, LCH 1, and LCH 2 There are three logical channels, denoted by LCH 0, LCH 1, and LCH 2, respectively.
  • the maximum duration configured for the LCH 0, LCH 1 and LCH 2 is 0.5, 0.25 and 0.125 milliseconds, respectively. Only the logical channel with maximum duration that is larger than or equal to the PUSCH transmission duration can be selected.
  • the duration of 14 symbols (7*2) is used for the selection of the logical channels. Suppose for example that the duration of 14 symbols is equal to 0.5 milliseconds.
  • LCH 0 is selected since the maximum duration configured for LCH 0 (e.g., 0.5 ms) is equal to the duration of 14 symbols.
  • LCH 1 and LCH 2 are not selected since the maximum duration configured for LCH 1 (e.g., 0.25ms) and LCH 2 (e.g., 0.125ms) is smaller than the duration of 14 symbols.
  • the duration of PUSCH 1 in a slot is used for the selection of the logical channels.
  • the duration of PUSCH 1 in a slot is 7 symbols (equal to 0.25 ms) . Therefore, LCH 0 and LCH 1 are selected since the maximum duration configured for LCH 0 (e.g., 0.5 ms) is larger than the duration of 7 symbols and the maximum duration configured for LCH 1 (e.g., 0.25 ms) is equal to the duration of 7 symbols.
  • the LCH 2 is not selected since the maximum duration configured for LCH 2 (e.g., 0.125 ms) is smaller than 7 symbols.
  • Fig. 6 shows a block diagram of an example protocol stack 600 plurality of layers, entities or modules of a communication node (e.g., a user device 102 or a wireless access node 104) , including a physical layer (PHY) entity or module (also called herein as just PHY layer, PHY module, or PHY entity) 602, a medium-access control (MAC) layer entity or module (also called herein as just MAC layer, MAC module, or MAC entity) 604, a radio-link control (RLC) layer entity or module (also called herein as just RLC layer, RLC entity, or RLC module) 606, a package data convergence protocol (PDCP) layer entity or module (also called herein as just PDCP layer, PDCP entity, or PDCP module) 608, and a radio resource control (RRC) layer entity or module (also called herein as just RRC layer, RRC entity, or RRC module) 610.
  • PHY physical layer
  • MAC medium-access control
  • RLC radio-link
  • a module or an entity may be considered part of, or a component of, or implemented using one or more of the components of a communication node of Fig. 1, including a processor 110/120, a memory 112/122, a transceiver circuit 106/114, or the antenna 108/116.
  • the processor 110/120 such as when executing computer code stored in the memory 112/116, may perform the functions of a module or entity.
  • the functions that a module or entity performs may be defined by one or more standards or protocols, such as 5G NR for example.
  • the layer entities 602-610 in Fig. 6 may be higher (or upper) and lower layers relative to each other, with the PHY layer entity 602 being the lowest layer among the layer entities 602-210; the MAC layer entity 604 being a higher layer than the PHY layer entity 602 and lower than the other layer entities 606-610; the RLC layer entity 606 being higher than the PHY and MAC layer entities 602, 604 and lower than the PDCP and RRC layer entities 608, 610; the PDCP layer entity 608 being higher than the PHY, MAC, and RRC layer entities 602-606 and lower than the RRC layer entity 610; and the RRC layer entity 610 being the highest layer entity among the layer entities 602-610 shown in Fig. 6.
  • a communication node of the system 100 may include modules and/or layer entities other than, including fewer than or more than, those shown in Fig. 6.
  • the layer entities or modules shown in Fig. 6 may be perform various functions and communicate with each other, such as by communicating signals, messages, or data packets between each other, in order to send and receive data packets.
  • the PHY layer entity or module 602 may perform various functions, including encoding and decoding transport blocks to be transmitted to, or received from, another communication node; modulation and demodulation of data according to any of various modulation schemes or types, such as quadrature amplitude modulation (QAM) and quadrature phase shift keying (QPSK) , as non-limiting examples; channel estimation on received data to determine channel state information on one or more channels on which the communication node receives signals; signal recovery of different signals, which the transmitting communication node may transmit on multiple antenna elements.
  • QAM quadrature amplitude modulation
  • QPSK quadrature phase shift keying
  • the MAC layer entity or module 604 may perform or handle logical-channel multiplexing and demultiplexing, hybrid automatic repeat request (HARQ) retransmissions, and scheduling-related functions, including the assignment of uplink and downlink resources in both the frequency domain and the time domain. Additionally, the MAC layer entity or module 604 may determine transport formats specifying how a transport block is to be transmitted. A transport format may specify a transport-block size, a coding and modulation mode, and antenna mapping. By varying the parameters of the transport format, the MAC layer entity or module 604 can effect different data rates. The MAC layer entity or module 604 may also control distributing data from flows across different component carriers or cells for carrier aggregation.
  • HARQ hybrid automatic repeat request
  • the RLC layer entity or module 606 may perform segmentation of service data units (SDU) to suitably sized protocol data units (PDU) .
  • SDU service data units
  • PDU protocol data units
  • a data entity from/to a higher protocol layer or module is called a SDU
  • PDU protocol data units
  • the RLC layer entity or module 606 may also perform retransmission management that involves monitoring sequence numbers in PDUs in order to identify missing PDUs.
  • the RLC layer entity or module 606 may communicate status reports to enable retransmission of missing PDUs.
  • the RLC layer entity or module 606 may also be configured to identify errors due to noise or channel variations.
  • the PDCP layer entity or module 608 may perform functions including, but not limited to, Internet Protocol (IP) header compression and decompression, ciphering and deciphering, integrity protection, retransmission management, in-sequence delivery, duplicate removal, dual connectivity, and handover functions.
  • IP Internet Protocol
  • the RRC layer entity or module 610 may perform functions including mapping traffic from quality of service (QoS) flows to suitable data radio bearers (DRBs) , determining and/or controlling the determining of configurations for two communication nodes to communicate with each other, and configuring the lower layer entities or modules 202-208 according to the determined configuration.
  • QoS quality of service
  • DRBs data radio bearers
  • terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the subject matter of the disclosure may also relate to or include, among others, the following aspects:
  • a first aspect includes a method for wireless communication that includes: determining, with at least one communication node, that a transport block over a plurality of slots for a physical channel is configured for a grant; and determining, with a medium access control (MAC) layer of the at least one communication node, whether to trigger a transmission for the grant.
  • MAC medium access control
  • a second aspect includes the first aspect, and further includes: determining, with the at least one communication node, that a number of slots for the grant is greater than one; and triggering, with the MAC layer of the at least one communication node, the transmission for the grant in response to the number of slots for the physical channel being greater than one.
  • a third aspect includes any of the first or second aspects, and further includes: identifying, with the communication node, that the grant is de-prioritized, wherein the transmission for the grant is triggered after identifying that the grant is de-prioritized.
  • a fourth aspect includes any of the first through third aspects, and further includes wherein the transmission for the grant comprises a new transmission or a retransmission.
  • a fifth aspect includes any of the third or fourth aspects, and further includes: generating, with the MAC layer of the at least one communication node, a MAC protocol data unit (PDU) for the grant in response to the transmission comprising the new transmission.
  • PDU MAC protocol data unit
  • a sixth aspect includes any of the first through fifth aspects, and further includes: before triggering the transmission for the physical channel, obtaining, with the MAC layer, a MAC protocol data unit (PDU) for the grant.
  • PDU MAC protocol data unit
  • a seventh aspect includes any of the first through sixth aspects, and further includes wherein the transmission comprises a new transmission, and the method further comprising: delivering, from the MAC layer to a hybrid automatic repeat request (HARQ) entity of the at one communication node, at least one of a MAC protocol data unit (PDU) , the grant, and HARQ information of a transport block for the new transmission; and instructing, with the MAC layer, the HARQ entity to trigger the new transmission.
  • HARQ hybrid automatic repeat request
  • An eighth aspect includes any of the first through sixth aspects, and further includes wherein the transmission comprises a retransmission, the method further comprising: delivering, from the MAC layer to a hybrid repeat request (HARQ) entity of the at least one communication node, at least one of the grant and HARQ information of a transport block for the retransmission; and instructing, with the MAC layer, the HARQ entity to trigger the retransmission.
  • HARQ hybrid repeat request
  • a ninth aspect includes any of the second through eighth aspects, and further includes wherein the number of slots for the physical channel indicated by a wireless access node is used to determine whether the number of slots for the grant is greater than one.
  • a tenth aspect includes any of the second through ninth aspects, and further includes wherein the number of slots that are actually used for the transmission of the physical channel is used to determine whether the number of slots for the grant is greater than one.
  • An eleventh aspect includes any of the first through tenth aspects, and further includes: determining, with the at least one communication node, not to trigger the transmission in response to determining the grant as a de-prioritized grant, and that the number of slots for the physical channel is equal to one.
  • a twelfth aspect includes any of the first through eleventh aspects, and further includes wherein the physical channel comprises a first physical channel, the uplink grant comprises a first grant, the method further comprising: determining, with the at least one communication node, the first grant as a de-prioritized uplink grant in response to: the first physical channel in any one of the plurality of slots is cancelled by a downlink control information (DCI) indication, or is cancelled by a second physical channel having a higher priority than a priority of the first transmission, or overlaps with a third physical channel of a third grant, wherein the third grant has a priority that is higher than or equal to the priority of the first grant.
  • DCI downlink control information
  • a thirteenth aspect includes any of the first through eleventh aspects, and further includes wherein the physical channel comprises a first physical channel, the grant comprises a first grant, the method further comprising: determining, with the at least one communication node, the first grant as a de-prioritized grant in response to: the first physical channel in each of the plurality of slots is cancelled by a downlink control information (DCI) indication, or is cancelled by a second physical channel having a higher priority than a priority of the first transmission, or overlaps with a third physical channel of a third grant, wherein the third grant has a priority that is higher than or equal to the priority of the first grant.
  • DCI downlink control information
  • a fourteenth aspect includes any of the first through eleventh aspects, and further includes wherein the physical channel comprises a first physical channel, the method further comprising: determining, with the at least one communication node, the grant as de-prioritized in response to the first physical channel overlapping a second physical channel for which the MAC layer of the communication node has triggered a transmission.
  • a fifteenth aspect includes any of twelfth, thirteenth, or fourteenth aspects, and further includes: determining, with the at least one communication node, not to trigger the transmission in response to determining the grant as a de-prioritized uplink grant.
  • a sixteenth aspect includes any of the first through fifteenth aspects, and further includes wherein the physical channel comprises physical uplink shared channel (PUSCH) , a physical downlink shared channel (PDSCH) , a physical uplink control channel (PUCCH) , or a physical sidelink shared channel (PSSCH) .
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • PSSCH physical sidelink shared channel
  • a seventeenth aspect includes any of the first through sixteenth aspects, and further includes wherein the grant comprises an uplink grant or a sidelink grant.
  • An eighteenth aspect includes a wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory to implement a method of any of the first through seventeenth aspects.
  • a nineteenth aspect includes a computer program product comprising a computer-readable program medium comprising code stored thereupon, the code, when executed by a processor, causing the processor to implement a method of any of the first through seventeenth aspects.

Landscapes

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

Abstract

L'invention concerne de manière générale une communication sans fil qui comprend : au moins un nœud de communication qui détermine qu'un bloc de transport sur une pluralité de créneaux pour un canal physique est configuré pour une autorisation et une couche de commande d'accès au support (MAC) de l'au moins un nœud de communication déterminant s'il faut déclencher une transmission pour l'autorisation.
PCT/CN2022/088372 2022-04-22 2022-04-22 Génération de blocs de transport pour des communications sans fil Ceased WO2023201675A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280093623.0A CN118891942A (zh) 2022-04-22 2022-04-22 无线通信的传输块生成
PCT/CN2022/088372 WO2023201675A1 (fr) 2022-04-22 2022-04-22 Génération de blocs de transport pour des communications sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/088372 WO2023201675A1 (fr) 2022-04-22 2022-04-22 Génération de blocs de transport pour des communications sans fil

Publications (1)

Publication Number Publication Date
WO2023201675A1 true WO2023201675A1 (fr) 2023-10-26

Family

ID=88418827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/088372 Ceased WO2023201675A1 (fr) 2022-04-22 2022-04-22 Génération de blocs de transport pour des communications sans fil

Country Status (2)

Country Link
CN (1) CN118891942A (fr)
WO (1) WO2023201675A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021063575A1 (fr) * 2019-10-01 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Mappage entre des canaux logiques et des configurations d'octrois configurés (cg)
US20210195623A1 (en) * 2018-12-04 2021-06-24 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method, apparatus and terminal for processing scheduling request
CN113273286A (zh) * 2021-04-07 2021-08-17 北京小米移动软件有限公司 一种时域资源分配的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210195623A1 (en) * 2018-12-04 2021-06-24 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method, apparatus and terminal for processing scheduling request
WO2021063575A1 (fr) * 2019-10-01 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Mappage entre des canaux logiques et des configurations d'octrois configurés (cg)
CN113273286A (zh) * 2021-04-07 2021-08-17 北京小米移动软件有限公司 一种时域资源分配的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Corrections to 5G V2X with NR Sidelink", 3GPP DRAFT; R2-2006704, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911615 *

Also Published As

Publication number Publication date
CN118891942A (zh) 2024-11-01

Similar Documents

Publication Publication Date Title
US12335972B2 (en) 5G NR data delivery for flexible radio services
US12167445B2 (en) Method for indicating the allocated resources for a HARQ message in a random access procedure for a low-complexity, narrowband terminal
JP7248661B2 (ja) 通信方法、通信装置、およびデバイス
US11115982B2 (en) Telecommunications apparatuses and methods
WO2020068973A1 (fr) Procédés, dispositifs et systèmes de support de l'harq sur v2x
JP7699257B2 (ja) 端末、通信方法及び集積回路
KR20220146499A (ko) 비면허 스펙트럼에서의 신뢰가능 harq-ack 송신
US11997047B2 (en) Method and device for determining priority of HARQ feedback in NR V2X
US11234218B2 (en) Descriptor channel designs for uplink channels in a shared radio frequency spectrum band
CN110447283B (zh) 无线通信网络中的网络节点和方法
WO2020069111A1 (fr) Sélection et réservation de ressources associées à un véhicule sur toute liaison latérale
JP7562845B2 (ja) 無線通信システムにおける物理サイドリンクフィードバックチャネルの送受信方法及びその装置
CN108347309B (zh) 反馈信息接收方法、发送方法、装置及系统
KR20220085783A (ko) Harq 프로세스/엔티티 기반 업링크 다중화
EP4057708B1 (fr) Procédé et dispositif de réalisation d'une procédure de priorisation dans nr v2x
US20240389130A1 (en) Communications device, infrastructure equipment and methods for addressing acknowledgement collisions
US20230089446A1 (en) Beam state updating in wireless communication
JP2024535000A (ja) 無線通信システムにおける予約リソースの衝突に関連する情報を送受信するための方法及び装置
WO2021165215A1 (fr) Dispositif de communication, équipement d'infrastructure et procédés de gestion de collisions de liaison montante
JP7662877B2 (ja) 端末装置、通信方法及び集積回路
WO2023201675A1 (fr) Génération de blocs de transport pour des communications sans fil
US20250374280A1 (en) Methods, communications devices, and infrastructure equipment
WO2025148034A1 (fr) Configurations temporelles et de numéro de paquet de données pour des communications sans fil

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280093623.0

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22937911

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 26.03.2025)