[go: up one dir, main page]

WO2025129985A1 - Procédé et système de transmission d'informations efficace et à faible latence - Google Patents

Procédé et système de transmission d'informations efficace et à faible latence Download PDF

Info

Publication number
WO2025129985A1
WO2025129985A1 PCT/CN2024/103535 CN2024103535W WO2025129985A1 WO 2025129985 A1 WO2025129985 A1 WO 2025129985A1 CN 2024103535 W CN2024103535 W CN 2024103535W WO 2025129985 A1 WO2025129985 A1 WO 2025129985A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink
pusch
uplink information
information
resource
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.)
Pending
Application number
PCT/CN2024/103535
Other languages
English (en)
Inventor
Xing Liu
Xianghui HAN
Junfeng Zhang
Xingguang WEI
Wei Gou
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 PCT/CN2024/103535 priority Critical patent/WO2025129985A1/fr
Publication of WO2025129985A1 publication Critical patent/WO2025129985A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0092Indication of how the channel is divided
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH

Definitions

  • This disclosure is generally directed to wireless communication systems and methods, and particularly relates to user equipment or UE facilitated, assisted, or controlled transmission resource scheduling.
  • Over-the-air radio resources are critical components in wireless communications networks. Effective communications between a wireless terminal device and a wireless access network may be achieved via efficient and low-latency resource scheduling. Traditionally network-controlled resource allocation and scheduling for uplink transmission often cannot be efficient and non-latent simultaneously.
  • This disclosure is generally directed to wireless communication systems and methods, and particularly relates to UE facilitated, assisted, or controlled transmission resource scheduling.
  • scheduling of configured uplink transmission resources may be determined or facilitated by UE within network-allocated uplink resources via an uplink information transmission rather than being controlled by the network.
  • activation and deactivation of network-allocated uplink transmission resources may also be controlled by the UE via an uplink information transmission.
  • the UE may be allowed to cancel or modify prior scheduled uplink transmission.
  • a method for uplink communication by a user equipment may include transmitting a first uplink information to a base station, the first uplink information facilitating an indication of a transmission mode for a second uplink information; and transmitting the second uplink information to the base station using the transmission mode.
  • the first uplink information is carried by at least one of: a Physical Uplink Control Channel (PUCCH) ; a Physical Uplink Shared Channel (PUSCH) ; a physical Random-Access Channel (PRACH) ; or a reference signal.
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • PRACH Physical Random-Access Channel
  • the first uplink information comprises the indication of the transmission mode.
  • the first uplink information indicates that one or more Configured-Grant PUSCHs (CG-PUSCHs) in a CG-PUSCH list are activated for transmitting the second uplink information.
  • CG-PUSCHs Configured-Grant PUSCHs
  • the transmission mode for the second uplink information comprises a set of transmission parameters for transmitting the second uplink information.
  • the CG-PUSCH configuration among a set of CG-PUSCH configurations corresponding to a first CG-PUSCH occasion after the first uplink information is activated by the UE.
  • the first uplink information indicates that one or more CG-PUSCH configurations from a list of CG-PUSCH configurations are requested to be activated for transmitting the second uplink information.
  • the downlink information comprises an acknowledgement information corresponding to the first uplink information, and the UE can transmit the second uplink information by using the resource indicated in the first uplink information.
  • the downlink information may include an activation downlink control information of one or more CG-PUSCH, and the UE can transmit the second uplink information by using resource activated by the downlink information.
  • the downlink information comprises the transmission mode of the second uplink information.
  • a method for uplink communication by a user equipment may include transmitting, by the UE, a first Scheduling Request (SR) of a first SR type on a first uplink resource to a base station to initiate an uplink service request; and transmitting, by the UE, a second SR of a second SR type on a second uplink resource to the base station subsequent to the first SR to cancel or change the uplink service request initiated by the first SR.
  • SR Scheduling Request
  • a minimum duration for a time interval between the second uplink resource and the first uplink resource is predefined or configured.
  • the second uplink resource is a first SR resource available after a predefined or configured time interval following an uplink scheduling information sent from the base station in response to the first SR.
  • a UE or access network node may include a processor and a memory, wherein the processor is configured to read code from the memory and implement any one of the methods above.
  • FIG. 8 illustrates another example UE controlled uplink resource scheduling implementation.
  • FIG. 11 illustrates an example UE assisted uplink resource scheduling implementation.
  • FIG. 14 illustrates yet another example UE assisted uplink resource scheduling implementation.
  • An example wireless communication network may include wireless terminal devices or user equipment (UE) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150.
  • the carrier network 102 may include access networks 120 and 121, and a core network 130.
  • the carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data traffic) among UEs 110, 111, and 112, between the UEs and the service applications 140, or between the UEs and the other data networks 150.
  • the access networks 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as base stations) to interact with the UEs on one side of a communication session and the core network 130 on the other.
  • WANNs wireless access network nodes
  • the core network 130 may include various network nodes configured to control communication sessions and perform network access management and traffic routing.
  • the service applications 140 may be hosted by various application servers deployed outside of but connected to the core network 130.
  • the other data networks 150 may also be connected to the core network 130.
  • the UEs may communicate with one another via the wireless access network.
  • UE 110 and 112 may be connected to and communicate via the same access network 120.
  • the UEs may communicate with one another via both the access networks and the core network.
  • UE 110 may be connected to the access network 120 whereas UE 111 may be connected to the access network 121, and as such, the UE 110 and UE 111 may communicate to one another via the access network 120 and 121, and the core network 130.
  • the UEs may further communicate with the service applications 140 and the data networks 150 via the core network 130. Further, the UEs may communicate to one another directly via side link communications, as shown by 113.
  • FIG. 2 further shows an example system diagram of the wireless access network 120 including a WANN 202 serving UEs 110 and 112 via the over-the-air interface 204.
  • the wireless transmission resources for the over-the-air interface 204 include a combination of frequency, time, and/or spatial resource.
  • Each of the UEs 110 and 112 may be a mobile or fixed terminal device installed with mobile access units such as SIM/USIM modules for accessing the wireless communication network 100.
  • the UEs 110 and 112 may each be implemented as a terminal device including but not limited to a mobile phone, a smartphone, a tablet, a laptop computer, a vehicle on-board communication equipment, a roadside communication equipment, a sensor device, a smart appliance (such as a television, a refrigerator, and an oven) , or other devices that are capable of communicating wirelessly over a network.
  • each of the UEs such as UE 112 may include transceiver circuitry 206 coupled to one or more antennas 208 to effectuate wireless communication with the WANN 120 or with another UE such as UE 110.
  • the transceiver circuitry 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage devices.
  • the memory 212 may be transitory or non-transitory and may store therein computer instructions or code which, when read and executed by the processor 210, cause the processor 210 to implement various ones of the methods described herein.
  • the WANN 202 may include transceiver circuitry 214 coupled to one or more antennas 216, which may include an antenna tower 218 in various forms, to effectuate wireless communications with the UEs 110 and 112.
  • the transceiver circuitry 214 may be coupled to one or more processors 220, which may further be coupled to a memory 222 or other storage devices.
  • the memory 222 may be transitory or non-transitory and may store therein instructions or code that, when read and executed by the one or more processors 220, cause the one or more processors 220 to implement various functions of the WANN 120 described herein.
  • Data packets in a wireless access network may be transmitted as protocol data units (PDUs) .
  • the data included therein may be packaged as PDUs at various network layers wrapped with nested and/or hierarchical protocol headers.
  • the PDUs may be communicated between a transmitting device or transmitting end (these two terms are used interchangeably) and a receiving device or receiving end (these two terms are also used interchangeably) once a connection (e.g., a radio link control (RRC) connection) is established between the transmitting and receiving ends.
  • RRC radio link control
  • Any of the transmitting device or receiving device may be either a wireless terminal device such as device 110 and 120 of FIG. 2 or a wireless access network node such as node 202 of FIG. 2. Each device may both be a transmitting device and receiving device for bi-directional communications.
  • FIG. 3 depict an example wireless access network 120 including a base station 302 and user equipment (UE) 304 that communicate with one another via over-the-air (OTA) radio communication resources 306.
  • the wireless access network 120 may be implemented as, as for example, a 2G, 3G, 4G/LTE, 5G, or 6G cellular radio access network or other types of wireless access network.
  • the base station 302 may be implemented as a 2G base station, a 3G node B, an LTE eNB, a 5G New Radio (NR) gNB, or a 6G base station or access point, as described above with respect to FIG. 2.
  • the user equipment 304 may be implemented as mobile or fixed communication devices installed with SIM modules for accessing the base station 302.
  • the user equipment 304 may include but is not limited to mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, distributed remote sensor devices, and desktop computers.
  • the wireless access network 120 may be implemented as other types of radio access networks, such as Wi-Fi, Bluetooth, ZigBee, and WiMax networks.
  • the radio communication resources 306 may include portions of licensed radio frequency bands, portions of unlicensed ration frequency bands, or portions of a mix of both licensed and unlicensed radio frequency bands.
  • the radio communication resources 306 available for carrying the wireless communication signals between the base station 302 and user equipment 304 may be further divided into physical downlink channels 310 for transmitting wireless signals from the base station 302 to the user equipment 304 and physical uplink channels 320 for transmitting wireless signals from the user equipment 304 to the base station 302.
  • the physical downlink channels 310 may further include physical downlink control channels (PDCCHs) 312 and physical downlink shared channels (PDSCHs) 314.
  • PDCCHs physical downlink control channels
  • PDSCHs physical downlink shared channels
  • the physical uplink channels 320 may further include physical uplink control channels (PUCCHs) 322 and physical uplink shared channels (PUSCHs) 324.
  • PUCCHs physical uplink control channels
  • PUSCHs physical uplink shared channels
  • the control channels PDCCHs 312 and PUCCHs 322 may be used to carry control information in forms of control messages such as downlink control information (DCI) message 316 and uplink control information (UCI) message 326.
  • DCI downlink control information
  • UCI uplink control information
  • the DCI message 316 for example, may be used for allocating PDSCH communication resources or PUSCH communication resources to the user equipment 104 besides carrying other control information (such as power control commands) .
  • the UCI message 326 may be used to carry Hybrid Automatic Repeat reQuest-acknowledgment (HARQ-ACK) feedback information transmitted by the user equipment 304 with respect to communication resource allocation from the base station 302 via the DCI message 316.
  • HARQ-ACK Hybrid Automatic Repeat reQuest-acknowledgment
  • the shared channels PDSCHs 314 and PUSCHs 324 may be allocated and used for communicating downlink data messages 318 and uplink data messages 328 between the base station 302 and the user equipment 304.
  • the communication resources 306 may include both radio frequency resources and time resources.
  • the entire accessible bandwidth of the radio frequency resource may be divided into multiple radio frequency bandwidth parts (BWPs) .
  • Each BWP may include a plurality of radio frequency physical resource block (PRB) .
  • PRB radio frequency physical resource block
  • each frequency PRB may further include a predetermined number of OFDM subcarriers with a predetermined subcarrier frequency spacing.
  • each frequency PRB may include 12 OFDM subcarriers.
  • the subcarrier frequency spacing may be provides with a plurality of configurable values which the UE may choose based on its signal processing capability.
  • the subcarrier frequency spacing may be configurable at 15 KHz, 30 KHz, 60 KHz, 120 KHz, or 240 KHz, etc.
  • the OFDM signals may be modulated onto one or more radio frequency carriers.
  • the time dimension of the communication resources 306 may be organized as frames and sub-frames of predetermined time durations.
  • the duration of a frame may be predefined at 10 ms.
  • a frame may be divided into a predetermined number of sub-frames. For example, a 10 ms frame may be divided into 10 sub-frames with each sub-frame lasting 1 ms.
  • Each sub-frame may be further divided into multiple time slots.
  • each time slot may be used for transmitting a predetermined number of OFDM symbols (e.g., 14 OFDM symbols with Normal Cyclic Prefix (CP) or 12 OFDM symbols with Extended CP) in a sequence.
  • OFDM symbols e.g., 14 OFDM symbols with Normal Cyclic Prefix (CP) or 12 OFDM symbols with Extended CP
  • the goal for any efficient mobile network such as the access network 120 above is to provide UEs and mobile terminals with data transmission service via almost ubiquitous radio access.
  • different techniques may be developed to increase the data rate and reliability of data transmissions between the network and an individual UE.
  • a same UE may support different types of services having different data transmission requirements. For example, one type of service may require a high data transmission rate, and the other type of service may instead require ultra-high transmission reliability and ultra-low latency.
  • a configured grant (CG) scheduling procedure may be defined as shown in FIG. 5.
  • some periodic uplink resources may be pre-configured shown as 502 and 504, and 604 and 606, with a periodicity of 506 and 608, respectively, via, e.g., RRC signaling.
  • the UE may select a resource from the periodic resources as pre-configured for the uplink service transmission.
  • FIG. 5 and FIG. 6 show that such configured grant scheduling implementations may be divided into two example types.
  • a Type 1 CG PUSCH is shown in FIG.
  • the uplink resource may be scheduled in manners that lower uplink data transmission latency and improved resource usage efficiency may be achieved.
  • the UE may determine a need for uplink transmission and may control an activation and usage of the uplink resource for transmitting the data.
  • the UE may inform the network its needs and the activation of the uplink resources.
  • the control of the activation and the usage of the uplink resource (e.g., configured uplink resources) may be more tailored to the UE behavior.
  • the uplink resources are not activated or deactivated, they may be used for other purposes by the network rather than being wasted.
  • the first uplink information of FIG. 7 may be carried by at least one of the following: PUCCH, PUSCH, PRACH, and reference signal. More specifically, in the case that the first uplink information is carried by a PUCCH, the first uplink information may be at least one of the following: an SR or a specific type of uplink control information (UCI) . In the case that the first uplink information is carried by a PRACH, the first uplink information may be preamble sequence. Different preamble sequences may indicate different indication information, e.g., different transmission modes of the second uplink information. For example, different PRACH preamble may be mapped to different transmission modes for the second uplink information.
  • the first uplink information may be used to indicate a time domain window, in which one or more CG-PUSCHs are activated for the transmission of the second uplink information.
  • a starting point of the time domain window may be indicated by the first uplink information as, e.g., a time domain offset from the end of the first uplink information to the starting point of the time domain window may be indicated.
  • the starting point of the time domain window may be determined according to a pre-defined offset between an end of the first uplink information and the starting point of the time domain window.
  • the starting point of the time domain window may be defined as a next symbol after the first uplink information.
  • the starting point of the time domain window may be defined as a next symbol after a time interval following the first uplink information.
  • the length of the time domain window may be indicated as a certain number of slots, subframes, half frames, or radio frames, or it can be defined as the number of PUSCH resources in accordance with a certain period. Such a length may be predefined or configured.
  • any CG-PUSCH configuration indicated by the first uplink information as being activated may be deactivated outside the indicated time window if there is no another activation command for activating the CG-PUSCH configuration before the end of the indicated time window.
  • the transmission mode as indicated by the first uplink information for the second uplink information may include transmission parameters for transmitting the second uplink information.
  • transmission parameters may include at least one of: time domain transmission resource for the second uplink information, time domain period of the transmission resource for the second uplink information, frequency domain transmission resource for the second uplink information, parameters for determining the transmission power of the second uplink information, modulation and coding mechanism of the second uplink information, spatial filtering of the second uplink information, and the like.
  • the second uplink information may be carried on a PUSCH.
  • the first uplink information may be carried on PUCCH or PUSCH.
  • the first uplink information may be implemented as an SR 802 corresponding a CG-PUSCH configuration.
  • the transmission of the first uplink information may indicate that the corresponding CG-PUSCH configuration is activated.
  • the UE can use this CG-PUSCH resource 804 for transmitting the second uplink information.
  • more than one CG-PUSCH configurations may be configured by the network.
  • different transmission resources (time/frequency/sequence resource) or values (for identifying the different transmission resources) of the first uplink information may be defined and corresponding to different CG-PUSCH configurations.
  • transmission resource 1 or value 1 may correspond to the first CG-PUSCH configuration; the transmission resource 2 or value 2 may correspond to the second CG-PUSCH configuration, and so on. If a UE selects transmission resource 1 or value 1 for transmitting the first uplink information, the first CG-PUSCH configuration among the more than one CG-PUSCH configurations may be activated.
  • the CG-PUSCH configuration above may be activated from a next CG-PUSCH occasion of the CG-PUSCH configuration after the first uplink information.
  • the CG-PUSCH configuration may be activated from the first CG-PUSCH occasion 904 after a time interval (e.g., T as shown by 906) following the first uplink information.
  • the first CG-PUSCH occasion after activation of the CG-PUSCH configuration may be located within the first UL slot after the first uplink information.
  • more than one CG-PUSCH configurations may be provided by the network.
  • there may be two CG-PUSCH configurations i.e., configuration 1 and configuration 2.
  • the CG resource periods may be P1 (1002) and P2 (1004) for configuration 1 and Configuration 2, respectively.
  • the time/frequency domain resources are showed in the figure.
  • the CG-PUSCH configuration corresponding to the first CG-PUSCH occasion after the first uplink information may be activated. For example, if the first uplink information is transmitted in slot 2, and the first CG-PUSCH occasion after the first uplink information corresponds to configuration 2, then configuration 2 may be activated.
  • the CG-PUSCH configuration corresponding to the first CG-PUSCH occasion after a time interval following the first uplink information may be activated.
  • the time interval may be defined or configured as 2 slots.
  • the first uplink information is transmitted in slot 2, the first CG-PUSCH occasion after 2 slots following the first uplink information corresponds to configuration 1.
  • configuration 1 may be activated.
  • the first uplink information may be used for deactivating one or more CG-PUSCH configurations.
  • the CG-PUSCH resources of the so deactivated CG-PUSCH configuration will not be occupied by the UE for transmitting the second uplink information after the first uplink information is transmitted.
  • one or more dedicated CG-PUSCH configurations are activated/deactivated by the UE via transmitting a first uplink information. Because the UE has a more accurate and timely understanding of whether uplink data is to arrive or is predicted to arrive, whether the CG should be activated/deactivated can be triggered by the UE to implement more efficient resource utilization.
  • the activation time window can be defined or configured as described above to further recycle the activated resources and further improve the resource utilization efficiency. The UE may determine the when the CG-PUSCH should be activated for its uplink data and for how long.
  • the time window duration which the CG-PUSCH is active may also be determined by the UE. The activation and the time window may be informed to the network by the UE via the first uplink information above.
  • the UE may first a first uplink information 1102 to the base station.
  • the first uplink information may be used to assist the network in determining a transmission mode of a second uplink information 1104 to be transmitted by the UE.
  • the UE may then receive a downlink information 1106 from the base station.
  • the downlink information 1108 may be transmitted from the base station in response to the base station receiving the first uplink information 1102.
  • the UE may further transmit the second uplink information according to the downlink information.
  • the first uplink information may be carried by at least one of the following: PUCCH, PUSCH, PRACH, and reference signal. More specifically, in the case that the first uplink information is carried by a PUCCH, the first uplink information may be at least one of the following: an SR or a specific type of uplink control information (UCI) . In the case that the first uplink information is carried by a PRACH, the first uplink information may be preamble sequence. Different preamble sequences may indicate different indication information, e.g., different transmission modes of the second uplink information. For example, different PRACH preamble may be mapped to different transmission modes for the second uplink information.
  • the first uplink information may be used to assist the network in determining a transmission mode of a second uplink information.
  • the transmission mode of the second uplink information as indicated by the first uplink information may include but is not limited to activation of one or more CG-PUSCH configurations from a list of CG-PUSCHs configurations for transmitting the second uplink information.
  • at least N bits information may be carried in the first uplink information for indicating which one or more CG-PUSCH configurations of the N CG-PUSCH configurations are requested to be activated. That is, each bit indicates activation of non-activation of one CG-PUSCH configuration.
  • the first uplink information may be used to indicate an expected transmission mode of a second uplink information.
  • the expected transmission mode may include at least one of, time domain transmission resource for the second uplink information, time domain period of the transmission resource for the second uplink information, frequency domain transmission resource for the second uplink information, parameters for determining the transmission power of the second uplink information, modulation and coding mechanism of the second uplink information, spatial filtering of the second uplink information, and the like.
  • the downlink information 1106 above transmitted by the network may include but is not limited to the transmission mode of the second uplink information.
  • the UE may transmit the second uplink information according to the transmission mode indicated by the downlink information.
  • the first uplink information may be used for assisting to deactivate one or more CG-PUSCH configurations.
  • one or more dedicated CG-PUSCH configurations will be activated by the UE via transmitting a first uplink information which carries assistance information for the network to determine the transmission mode of the second uplink information. Because the UE has a more accurate and timely understanding of whether uplink data is received or is predicted to be received, whether the CG should be activated can be triggered by the UE by the UE sending activation assistance uplink information to the network to assist the network in activating the CU-PUSCH for transmitting the uplink data or service, whereby improving efficiency of uplink transmission resource utilization.
  • This embodiment describes another method on improving resource usage efficiency while ensuring low data transmission latency.
  • the UE may predict or anticipate arrival of uplink data and schedule uplink resources with the network before actual arrival of the uplink data in order to reduce scheduling latency.
  • the UE may cancel or modify the uplink resource scheduling. Modification of the uplink resources scheduling may include but is not limited to, for example, delaying the scheduled uplink transmission resource.
  • two different SR types may be defined, e.g., a first SR type and a second SR type.
  • the UE may first send a first SR 1202 of the first SR type on a first uplink resource.
  • the UE may further send a second SR 1204 of the second SR type on a second uplink resource subsequent to the first uplink resource.
  • the second SR may be used to cancel or change an initiated service request of the first SR.
  • the UE may receive an uplink scheduling information 1304 sent by the base station.
  • the uplink scheduling information 1304 may schedule a third uplink resource 1308 for uplink data transmission.
  • the implementations above thus allow the UE the schedule the third uplink resource in anticipation of uplink data arrival but also allows the UE to cancel/release the scheduled uplink resource wen the anticipated uplink data would not be actually transmitted, thereby improve uplink resource utilization while providing reduced uplink transmission latency.
  • the second SR and the first SR may correspond to a scheduling request resource identifier (e.g., SchedulingRequestResourceId) or a scheduling request identifier (e.g., SchedulingRequestId) ) such that the pairing of their transmission and reception can be recognized or identified.
  • a scheduling request resource identifier e.g., SchedulingRequestResourceId
  • SchedulingRequestId SchedulingRequestId
  • the second uplink resource above in FIG. 13 may be the last service scheduling request resource before a period of time of the third uplink resource.
  • the second uplink resource may be the last PUCCH resource before a period of time before the third uplink resource. In either implementation here, the cancellation of the third uplink resource for uplink data transmission for the UE may need to be provided some time ahead of the scheduled third uplink resource.
  • a time domain offset may be predefined or configured between the first uplink resource above (1202, 1302, or 1402) and the second uplink resource above (1204, 1306, 1406) .
  • a time interval may be predefined or configured and the second uplink resource above (1204, 1306, 1406) may be a first scheduling request resource following the first uplink resource above (1202, 1302, or 1402) by at least the predefined or configured time interval.
  • a time interval may be predefined or configured and the second uplink resource above (1204, 1306, 1406) may be a first scheduling request resource following the uplink scheduling information (1304 or 1404) (e.g., a downlink control information (DCI) carried in a PDCCH) by at least the time interval.
  • the uplink scheduling information (1304 or 1404) e.g., a downlink control information (DCI) carried in a PDCCH
  • the second SR above (1204, 1306, 1406) may be used for requesting to delay the allocated third uplink resource (1308 or 1408) backward for a period of time.
  • the UE may have an opportunity to request a modification of the scheduling by requesting a delay of the third uplink resource (1308 or 1408) .
  • a timer e.g., sr-ProhibitTimer
  • the UE may send the second SR which represents or indicates cancellation or modification of the first SR.
  • the predefined time e.g., the timer (e.g., sr-ProhibitTimer) enabled after the first SR is sent has not expired.
  • uplink resource scheduling may be triggered by predicted data transmission needs using either UE side or network work side predictive models for reduce time delay in resource scheduling. Accuracy of the predictive models or predictive procedure may be improved via a timely feedback mechanism.
  • an SR may be sent by the UE in advance based on a prediction of the arrival time of uplink data (for example, by using rule bases algorithms or pretrained artificial intelligence algorithms or models such as the neural network or deep learning models, etc. ) .
  • a prediction of the arrival time of uplink data for example, by using rule bases algorithms or pretrained artificial intelligence algorithms or models such as the neural network or deep learning models, etc.
  • the user-plane delay in uplink transmission may be reduced.
  • the SR is sent in advance to the network in accordance with the predicted uplink data arrival time, it is possible that no uplink service actually arrives.
  • such incorrect prediction information may be fed back to the network, which may help the network adjust the prediction algorithms/models or modify a part or an entirety of the prediction procedure (for example, changing from a UE-side prediction procedure or model to a network-side prediction procedure or model) .
  • the UE may predict a reception result of the entire PDSCH in accordance with receiving a part of downlink information.
  • the partial downlink information may include at least one of the following: PDCCH, DMRS of PDCCH, DMRS of PDSCH, or one or more code blocks (CB) or code block groups (CBG) carried on the PDSCH.
  • CB code blocks
  • CBG code block groups
  • NACK non-acknowledgement
  • PDSCH is eventually decoded successfully.
  • incorrect prediction information may also be fed back to the network, which may help the network adjust the prediction algorithms/models or modify the entire prediction procedure.
  • the UE may count incorrect or correct number of times for advanced or predictive SR scheduling or HARQ-ACK transmission, or a proportion of incorrect or correct number of times to a total number of times for advanced or predictive SR scheduling or HARQ-ACK transmission within a past period of time, and report the count of proportion to the network.
  • the UE may report the error as a feedback.
  • the UE may report the result to the network as a feedback.
  • the UE may report the result to the network as a feedback.
  • the UE may report the result to the network as a feedback.
  • the reported information can be defined or included as uplink control information (UCI) , which may be carried on a PUCCH or PUSCH.
  • UCI uplink control information
  • the reported information may be defined and included as a MAC layer signaling or an RRC layer signaling, which may be carried on the PUSCH.
  • SR/HARQ-ACK can be sent in advance by using the prediction mechanism above.
  • a reporting mechanism may be defined to ensure that the prediction algorithm and overall prediction process can be adjusted in a timely manner, thereby helping reducing transmission delays.
  • 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.

Landscapes

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

Abstract

La présente divulgation concerne de manière générale des systèmes et des procédés de communication sans fil, et concerne en particulier une planification de ressources de transmission facilitée, assistée ou commandée par UE. Par exemple, la planification de ressources de transmission en liaison montante configurées peut être déterminée ou facilitée par un UE dans des ressources de liaison montante attribuées au réseau par l'intermédiaire d'une transmission d'informations en liaison montante au lieu d'être commandée par le réseau. Pour un autre exemple, l'activation et la désactivation de ressources de transmission en liaison montante attribuées au réseau peuvent également être commandées par l'UE par l'intermédiaire d'une transmission d'informations en liaison montante. Pour un autre exemple, l'UE peut être autorisé à annuler ou à modifier une transmission en liaison montante planifiée précédemment. Les divers modes de réalisation ci-dessus proposent des transmissions en liaison montante qui sont à la fois efficaces en matière d'utilisation de ressources et présentent une latence plus faible.
PCT/CN2024/103535 2024-07-04 2024-07-04 Procédé et système de transmission d'informations efficace et à faible latence Pending WO2025129985A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/103535 WO2025129985A1 (fr) 2024-07-04 2024-07-04 Procédé et système de transmission d'informations efficace et à faible latence

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/103535 WO2025129985A1 (fr) 2024-07-04 2024-07-04 Procédé et système de transmission d'informations efficace et à faible latence

Publications (1)

Publication Number Publication Date
WO2025129985A1 true WO2025129985A1 (fr) 2025-06-26

Family

ID=96136291

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/103535 Pending WO2025129985A1 (fr) 2024-07-04 2024-07-04 Procédé et système de transmission d'informations efficace et à faible latence

Country Status (1)

Country Link
WO (1) WO2025129985A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130194988A1 (en) * 2012-01-30 2013-08-01 Renesas Mobile Corporation Method and apparatus for activation and deactivation of a transmission mode
CN110035543A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 上行资源的使用方法及装置
CN115190622A (zh) * 2021-04-06 2022-10-14 华为技术有限公司 传输上行数据的方法和装置
CN116566560A (zh) * 2022-01-28 2023-08-08 大唐移动通信设备有限公司 信令传输方法、装置及存储介质
US20240147496A1 (en) * 2021-02-26 2024-05-02 Lenovo (Singapore) Pte. Ltd. Modifying l1 parameters for configured grant resource

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130194988A1 (en) * 2012-01-30 2013-08-01 Renesas Mobile Corporation Method and apparatus for activation and deactivation of a transmission mode
CN110035543A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 上行资源的使用方法及装置
US20240147496A1 (en) * 2021-02-26 2024-05-02 Lenovo (Singapore) Pte. Ltd. Modifying l1 parameters for configured grant resource
CN115190622A (zh) * 2021-04-06 2022-10-14 华为技术有限公司 传输上行数据的方法和装置
CN116566560A (zh) * 2022-01-28 2023-08-08 大唐移动通信设备有限公司 信令传输方法、装置及存储介质

Similar Documents

Publication Publication Date Title
US11889565B2 (en) Method and system for handling random access response in wireless communication system
US11871314B2 (en) Resource allocation method for V2X communication in wireless communication system and apparatus therefor
US11751245B2 (en) Method and wireless communication system for handling timer operation
US11785494B2 (en) Method and device for performing SL communication in NR V2X on basis of auxiliary information
AU2018417653B2 (en) Multi-stage sidelink control information
KR102233105B1 (ko) 상향링크 정보 처리 방법 및 장치
US10701677B2 (en) Method and apparatus for uplink resource assignment for cellular network using unlicensed bands
US11737017B2 (en) Control information utilization method and apparatus of terminal in mobile communication system
CN101999219B (zh) 执行随机接入过程的方法和装置
CA3095219A1 (fr) Procede et appareil de communication pour reception discontinue, et dispositif et systeme de communication
CN111405662B (zh) 数据传输方法、网络侧设备及用户设备
CN110830172B (zh) 非授权频段harq反馈的指示、发送方法及装置、存储介质、基站、终端
US12143986B2 (en) Information sending method and apparatus, information receiving method and apparatus, base station, terminal, and communication system
KR102734980B1 (ko) Nr 사용자 디바이스를 위한 다이나믹 프로세싱 시간 및 다이나믹 블라인드 디코딩 성능
US12273916B2 (en) Energy detection threshold value determination method and apparatus
EP3876464A1 (fr) Procédé de transmission de données dans l'internet des véhicules, terminal de transmission et dispositif côté réseau
WO2013127453A1 (fr) Canaux de contrôle pour une communication sans fil
US20240188178A1 (en) Sidelink discontinuous reception procedures
CN113491075A (zh) 在无线通信系统中发送与用户设备的波束相关的上行链路反馈信息的方法以及支持该方法的用户设备和基站
US20240039680A1 (en) Feedback Procedures for SL Power Saving UEs
WO2025129985A1 (fr) Procédé et système de transmission d'informations efficace et à faible latence
US12369222B2 (en) Discontinuous reception alignment grouping for sidelink and cellular communication
US20220232480A1 (en) Transmit Power Allocation Technique
US20240172194A1 (en) Repetition factor adaptation for mini-slot-based transport block transmission

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

Country of ref document: EP

Kind code of ref document: A1