CN113661750B - Method for transmitting data, terminal device and network device - Google Patents

Method for transmitting data, terminal device and network device Download PDF

Info

Publication number
CN113661750B
CN113661750B CN201980094840.XA CN201980094840A CN113661750B CN 113661750 B CN113661750 B CN 113661750B CN 201980094840 A CN201980094840 A CN 201980094840A CN 113661750 B CN113661750 B CN 113661750B
Authority
CN
China
Prior art keywords
pucch resource
uplink
pucch
resource group
terminal device
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.)
Active
Application number
CN201980094840.XA
Other languages
Chinese (zh)
Other versions
CN113661750A (en
Inventor
付喆
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN113661750A publication Critical patent/CN113661750A/en
Application granted granted Critical
Publication of CN113661750B publication Critical patent/CN113661750B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling

Abstract

The embodiment of the application discloses a method, terminal equipment and network equipment for transmitting data, wherein the method comprises the following steps: the terminal equipment determines target PUCCH resources from a plurality of Physical Uplink Control Channel (PUCCH) resources for transmitting Scheduling Requests (SR) according to the data quantity to be transmitted, wherein the PUCCH resources correspond to a plurality of data quantity intervals; and the terminal equipment sends the SR on the target PUCCH resource. The method, the terminal equipment and the network equipment are beneficial to reducing the service time delay in the uplink scheduling process, so that the user experience can be improved.

Description

Method for transmitting data, terminal device and network device
Technical Field
The embodiments of the present application relate to the field of communications, and more particularly, to a method, a terminal device, and a network device for transmitting data.
Background
Based on the current New Radio (New Radio) standard, when uplink data arrives at the terminal, but the terminal does not have uplink resources for data transmission, the terminal generally needs to go through 5 steps to send the uplink data to the network. Specifically: a terminal needs to send a Scheduling Request (SR) for requesting uplink resources to a network; the network does not know how much uplink resources are needed by the terminal for transmitting uplink data, so the network allocates uplink resources for the terminal to send a buffer status report (Buffer Status Report, BSR); the terminal further transmits a BSR on the allocated uplink resource; therefore, the network can acquire the data size and allocate proper uplink resources for uplink data transmission to the terminal; and finally, the terminal transmits uplink data on uplink resources allocated by the network.
The existing uplink scheduling process may cause longer service delay, thereby affecting user experience.
Disclosure of Invention
The embodiment of the application provides a method for transmitting data, terminal equipment and network equipment, which are beneficial to reducing service time delay in an uplink scheduling process, so that user experience can be improved.
In a first aspect, there is provided a method for transmitting data, the method comprising: the terminal equipment determines target PUCCH resources from a plurality of Physical Uplink Control Channel (PUCCH) resources for transmitting Scheduling Requests (SR) according to the data quantity to be transmitted, wherein the PUCCH resources correspond to a plurality of data quantity intervals; and the terminal equipment sends the SR on the target PUCCH resource.
In a second aspect, there is provided a method for transmitting data, the method comprising: the network equipment receives a scheduling request SR sent by the terminal equipment on a first physical uplink control channel PUCCH resource; the network device determines a data volume interval corresponding to the first PUCCH resource from a plurality of PUCCH resources configured for the terminal device and used for transmitting SR, wherein the plurality of PUCCH resources correspond to a plurality of data volume intervals; and the network equipment allocates a Physical Uplink Shared Channel (PUSCH) resource for transmitting data to the terminal equipment according to the data volume interval corresponding to the first PUCCH resource.
In a third aspect, a terminal device is provided for performing the method of the first aspect or implementation manner thereof.
Specifically, the terminal device comprises functional modules for performing the method of the first aspect or implementation manner thereof.
In a fourth aspect, a network device is provided for performing the method of the second aspect or implementation thereof.
In particular, the network device comprises functional modules for performing the method of the second aspect or in a realization thereof.
In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect or implementation manner.
In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementation thereof.
A seventh aspect provides a chip for implementing the method of any one of the first to second aspects or each implementation thereof.
Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method as in any one of the first to second aspects or implementations thereof described above.
In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.
In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.
In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.
According to the technical scheme, the terminal equipment is configured with a plurality of physical uplink control channel (Physical Uplink Control Channel, PUCCH) resources for transmitting the SR, each PUCCH resource corresponds to one data volume interval respectively, and the terminal equipment can select the corresponding PUCCH resource to transmit the SR according to the data volume to be transmitted, so that after receiving the SR, the network equipment can know that the terminal equipment has uplink data to be transmitted and can also know about how much data to be transmitted, and the terminal equipment is allocated with proper PUSCH transmission data. The scheme of the embodiment of the application is beneficial to shortening the uplink scheduling process, thereby reducing the influence of service time delay and improving the user experience.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments.
Drawings
Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
Fig. 2 is a schematic diagram of a conventional uplink scheduling procedure.
Fig. 3 is a schematic block diagram of a method for transmitting data provided by an embodiment of the present application.
Fig. 4 is a schematic diagram of a method for transmitting data according to an embodiment of the present application.
Fig. 5 is a schematic diagram of a method for transmitting data according to an embodiment of the present application.
Fig. 6 is a schematic diagram of a method for transmitting data according to an embodiment of the present application.
Fig. 7 is a schematic block diagram of a method for transmitting data provided by an embodiment of the present application.
Fig. 8 is a schematic block diagram of a terminal device provided in an embodiment of the present application.
Fig. 9 is a schematic block diagram of a network device provided in an embodiment of the present application.
Fig. 10 is a schematic block diagram of a communication device provided in an embodiment of the present application.
Fig. 11 is a schematic block diagram of a chip provided in an embodiment of the present application.
Fig. 12 is a schematic diagram of a communication system provided in an embodiment of the present application.
Detailed Description
The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
It should be understood that the technical solution of the embodiments of the present application may be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet Radio service (General Packet Radio Service, GPRS), long term evolution LTE systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD) systems, general mobile communication systems (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, new Radio (NR) or future 5G systems, etc.
In particular, the technical solution of the embodiments of the present application may be applied to various communication systems based on non-orthogonal multiple access technologies, such as a sparse code multiple access (Sparse Code Multiple Access, SCMA) system, a low density signature (Low Density Signature, LDS) system, etc., where, of course, SCMA systems and LDS systems may also be referred to by other names in the communication field; further, the technical solution of the embodiments of the present application may be applied to a multi-Carrier transmission system using a non-orthogonal multiple access technology, for example, an orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM), a filter bank multi-Carrier (FBMC), a general frequency division multiplexing (Generalized Frequency Division Multiplexing, GFDM), a Filtered orthogonal frequency division multiplexing (F-OFDM) system, and the like using a non-orthogonal multiple access technology.
Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network device gNB in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.
The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal device" includes, but is not limited to, a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment. An access terminal may be, but is not limited to, a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.
Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.
Alternatively, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.
It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a mobility management entity (Mobility Management Entity, MME), a Serving Gateway (S-GW), a packet data Gateway (PDN Gateway), or the like, which is not limited in the embodiments of the present application.
It should also be appreciated that the communication system 100 shown in fig. 1 may also be a Non-terrestrial communication network (Non-Terrestrial Network, NTN) system, and in particular, NTN typically provides communication services to terrestrial users by way of satellite communications. That is, the network device 110 in fig. 1 may be a satellite. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communications are not limited by the user region, for example, general land communications cannot cover areas where communication devices cannot be installed, such as oceans, mountains, deserts, etc., or communication coverage is not performed due to rarity of population, while for satellite communications, since one satellite can cover a larger ground, and the satellite can orbit around the earth, theoretically every corner on the earth can be covered by satellite communications. And secondly, satellite communication has great social value. Satellite communication can be covered in remote mountain areas, poor and backward countries or regions with lower cost, so that people in the regions enjoy advanced voice communication and mobile internet technology, and the digital gap between developed regions is reduced, and the development of the regions is promoted. Again, the satellite communication distance is far, and the cost of communication is not obviously increased when the communication distance is increased; and finally, the satellite communication has high stability and is not limited by natural disasters.
Communication satellites are classified into Low Earth Orbit (LEO) satellites, medium Earth Orbit (MEO) satellites, geosynchronous Orbit (Geostationary Earth Orbit, GEO) satellites, high elliptical Orbit (High Elliptical Orbit, HEO) satellites, and the like according to the Orbit heights. LEO and GEO are the main studies at the present stage. Wherein the LEO satellite has a height range of 500 km-1500 km and a corresponding orbit period of about 1.5 hours-2 hours. The signal propagation delay for single hop communications between users is typically less than 20ms. The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, the link loss is less, and the requirement on the transmitting power of the user terminal is not high; GEO orbit height is 35786km, rotation period around earth is 24 hours. The signal propagation delay for single hop communications between users is typically 250ms. In order to ensure the coverage of the satellite and improve the system capacity of the whole satellite communication system, the satellite adopts multiple beams to cover the ground, and one satellite can form tens or hundreds of beams to cover the ground; a satellite beam may cover a ground area of several tens to hundreds of kilometers in diameter.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
Based on the current NR standard, when a UE has uplink data to arrive, but the UE does not have uplink resources for data transmission, the UE may need to go through the following 5 steps to transmit the data to the network, as shown in fig. 2.
S201, the UE sends an SR and requests uplink resources to the gNB.
S202: the gNB receives the SR, knows that the UE needs uplink resources for transmitting uplink data, but the gNB does not know how much uplink data the UE needs to transmit, so it is common practice for the gNB to allocate PUSCH resources to the UE that are sufficient for the UE to transmit BSR.
S203: the UE transmits a BSR on the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resources allocated by the gNB, thereby informing the gNB of the size of the data amount that the UE needs to transmit.
S204: and the gNB allocates proper PUSCH resources for the UE for uplink data transmission according to the BSR information reported by the UE.
S205: and the UE transmits uplink data on the PUSCH resources allocated by the gNB.
In the current scheme, a longer time delay may be required from the time when the UE has uplink data to the time when the UE transmits the data to the network, and the time delay may affect the transmission of the service, thereby affecting the user experience.
Therefore, the embodiment of the application provides a method for transmitting data, which can reduce the time delay of the service in the uplink scheduling process, so that the user experience can be improved.
Fig. 3 shows a schematic block diagram of a method 300 for transmitting data according to an embodiment of the present application. As shown in fig. 3, the method includes some or all of the following:
s310, the terminal equipment determines target PUCCH resources from a plurality of physical uplink control channel PUCCH resources for transmitting a scheduling request SR according to the data volume to be transmitted, wherein the plurality of PUCCH resources correspond to a plurality of data volume intervals;
s320, the terminal device sends an SR on the target PUCCH resource.
Specifically, a plurality of PUCCH resources for transmitting SRs may be configured for the terminal device in a protocol-defined manner or in a network device preconfigured manner, and the plurality of PUCCH resources may correspond to a plurality of data amount intervals. When the terminal device has uplink data arrived, it can select which data volume interval is in according to the data volume to be transmitted, so as to send SR to the network device using PUCCH resource corresponding to the data volume interval. When the network device detects the SR sent by the terminal device on a certain PUCCH resource, the network device may further find out the data volume interval corresponding to the PUCCH resource receiving the SR from the correspondence between the PUCCH resource and the data volume interval, so that the network device may roughly know how much uplink data to be transmitted is available for the terminal device, and further the network device may allocate appropriate PUSCH resources for the terminal device to transmit the uplink data.
In the related art, the terminal device makes the network device acquire the uplink buffer data amount of the terminal device through the BSR, so that the network device can schedule the terminal device according to the data amount information provided by the terminal device. In order to save the cost of reporting the BSR, the BSR is sent by adopting a packet reporting mode. I.e. each uplink logical channel corresponds to one logical channel group (Logic Channel Group, LCG), a plurality of uplink logical channels may correspond to the same LCG, wherein the correspondence between LCs and LCGs may be configured by the network device. The terminal device may report BSR based on LCGs, and each terminal device may support up to 8 LCGs in the NR.
The triggering conditions of BSR are typically the following:
1. an uplink logical channel with higher priority for the UE has uplink data arriving, in which case a Regular BSR is triggered.
2. The Padding (Padding) portion of the uplink resources allocated to the UE after carrying other uplink data can carry a BSR medium access control unit (Medium Access Control Control Element, MAC CE), in which case a Padding BSR is sent out.
3. The retransmission BSR Timer retxBSR-Timer times out and there is currently at least one uplink logical channel for uplink data to be transmitted, at which time the Regular BSR is triggered.
4. The Periodic BSR Timer may trigger a Periodic BSR when the Periodic BSR-Timer expires.
If there are multiple uplink logical channels triggering a Regular BSR at the same time, each of these uplink logical channels triggers a separate Regular BSR, which is carried by the BSR MAC CE.
If a certain uplink logical channel of the terminal equipment triggers the Regular BSR, but the terminal equipment does not have uplink resources for transmitting new data or uplink resources allocated to the terminal equipment for transmitting new data cannot bear data of the uplink logical channel triggering the Regular BSR, the terminal equipment triggers the SR.
From the triggering condition of the SR, the SR is triggered based on an uplink logical channel. For each uplink logical channel of the terminal device, the network device may select whether PUCCH resources for transmitting SRs are configured for the uplink logical channel. If the network device configures PUCCH resources for transmitting SRs for an uplink logical channel in case that the SR is triggered by the uplink logical channel, the terminal device may transmit the SR on the PUCCH resources for transmitting SRs corresponding to the uplink logical channel; otherwise, the terminal device may initiate random access.
Alternatively, when all uplink logical channels of the terminal device triggering the Regular BSR are not configured with PUCCH resources for transmitting SR, the terminal device will initiate a random access procedure.
Optionally, in the embodiment of the present application, the terminal device may be configured with a plurality of PUCCH resources for transmitting SR, where the plurality of PUCCH resources may be configured to at least one uplink logical channel of the terminal device, if at least one uplink logical channel of the terminal device is configured with PUCCH resources, any one of the at least one uplink logical channel may be configured with a plurality of PUCCH resources, that is, one uplink logical channel is configured with one PUCCH resource group, and the plurality of PUCCH resources configured by the terminal device may be configured with PUCCH resources included in at least one PUCCH resource group corresponding to the at least one uplink logical channel. The plurality of PUCCH resources included in any two PUCCH resource groups may have partial PUCCH resources overlapping, may not overlap at all, or may overlap at all.
When the N uplink logical channels of the terminal device trigger the regular BSR, the terminal device may determine, according to the data amounts to be transmitted of the N uplink logical channels, a target PUCCH resource from a plurality of PUCCH resources configured for the terminal device, to be used for transmitting the SR. Specifically, the terminal device may determine, according to the data amounts to be transmitted of the N uplink logical channels, a target PUCCH resource from the at least one PUCCH resource group. The at least one resource group corresponds to at least one uplink logical channel in the N uplink logical channels, in which PUCCH resources for transmitting SRs are configured. For example, the terminal device is configured with 8 uplink logical channels, the identities of which are respectively 0-7, wherein uplink logical channels 1-3 are respectively configured with one PUCCH resource group, and the current uplink logical channels 2-5 respectively trigger the regular BSR, so that the terminal device can determine the target PUCCH resource from the two PUCCH resource groups corresponding to the uplink logical channels 2 and 3 according to the data amount to be transmitted of the uplink logical channels 2-5.
Further, the terminal device may determine at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data amounts to be transmitted of the N uplink logical channels, and then determine the target PUCCH resource from all the candidate PUCCH resources determined in the at least one PUCCH resource group. Since there may be some overlap of PUCCH resources included in different PUCCH resource groups, the candidate PUCCH resource determined from each PUCCH resource group may be one PUCCH resource, and the determined one PUCCH resource may be used as the target PUCCH resource to transmit SR. And the candidate PUCCH resources respectively determined from each PUCCH resource group may be a plurality of PUCCH resources, then the terminal device may further select one PUCCH resource from the determined plurality of PUCCH resources as the target PUCCH resource to transmit the SR.
When the terminal equipment needs to select one PUCCH resource from a plurality of candidate PUCCH resources as a target PUCCH resource, the terminal equipment can use one PUCCH resource closest to the current time in the plurality of candidate PUCCH resources as the target PUCCH resource; or, the terminal device may further determine priorities of uplink logical channels corresponding to the plurality of candidate PUCCH resources, respectively, and use one candidate PUCCH resource corresponding to the uplink logical channel with the highest priority as a target PUCCH resource; alternatively, the terminal device may also randomly select one PUCCH resource from the plurality of candidate PUCCH resources as the target PUCCH resource. It should be noted that, whether one PUCCH resource closest to the current time is selected as the target PUCCH resource or one candidate PUCCH resource corresponding to the uplink logical channel with the highest priority is selected as the target PUCCH resource is merely an example, that is, the time domain interval from the current time or the priority of the uplink logical channel may be used only as one reference for selecting the target PUCCH resource from the candidate PUCCH resources.
For taking the priority of the uplink logic channel as a reference for selecting the target PUCCH resource, before the terminal device selects at least one candidate PUCCH resource from each PUCCH resource group in at least one PUCCH resource group according to the data amount to be transmitted of the N uplink logic channels, the terminal device may rank the priority of the at least one uplink logic channel because the at least one PUCCH resource group corresponds to the at least one uplink logic channel, and optionally, the terminal device only needs to select one candidate PUCCH resource from one PUCCH resource group corresponding to the uplink logic channel with the highest priority, and takes the candidate PUCCH resource as the target PUCCH resource.
It should be noted that, for the same uplink logical channel, the data volume intervals corresponding to different PUCCH resources may overlap partially, and if the data volume to be transmitted is just in the common overlapping region of the multiple data volume intervals, the terminal device may use the multiple PUCCH resources corresponding to the multiple data volume intervals as candidate PUCCH resources. Alternatively, for the same uplink logical channel, the data volume interval corresponding to each PUCCH resource included in the corresponding one of the PUCCH resource groups is different, so that for one data volume to be transmitted, only one candidate PUCCH resource can be selected from the corresponding one of the PUCCH resource groups of the uplink logical channel. Optionally, for an uplink logical channel, the data volume interval corresponding to each PUCCH resource included in a corresponding PUCCH resource group may be divided by some thresholds, and the thresholds may be ordered in order from small to large, and combined into a data volume interval two by two. For example, assuming that one PUCCH resource group corresponding to one uplink logical channel includes M PUCCH resources, M data volume sections corresponding to the M PUCCH resources may be divided by (M-1) thresholds, respectively, th1, …, thM-1. That is, the data amount interval corresponding to PUCCH resource 1 may be [0, th 1), the data amount interval corresponding to PUCCH resource 2 may be [ th1, th 2), the data amount interval corresponding to PUCCH resource 3 may be [ th2, th 3), …, and the data amount interval corresponding to PUCCH resource M may be [ th (M-1), infinity. Optionally, for one uplink logical channel, the data amount interval corresponding to each PUCCH resource included in one corresponding PUCCH resource group may be configured by a network device, or may be predefined, which is not limited by the embodiment of the present application.
Alternatively, the terminal device may also determine the target PUCCH resource from the at least one PUCCH resource group directly according to the amount of data to be transmitted of the at least one logical channel that triggers both the Regular BSR and is configured with PUCCH resources. The embodiments of the present application are not limited thereto.
Specifically, the terminal device may determine at least one candidate PUCCH resource from each of the at least one PUCCH resource group according to the following manner.
Mode one: since at least one uplink logical channel of the terminal device is configured with PUCCH resources for transmitting SR, that is, the at least one uplink logical channel corresponds to at least one PUCCH resource group, and the at least one uplink logical channel each triggers a regular BSR separately, the terminal device may determine at least one PUCCH resource from the corresponding one PUCCH resource group according to the amount of data to be transmitted of each uplink logical channel in the at least one uplink logical channel, respectively. Optionally, when the terminal device selects at least one candidate PUCCH resource from each PUCCH resource group, the terminal device may select one PUCCH resource from all the candidate PUCCH resources to indicate an amount of data to be transmitted of an uplink logical channel corresponding to the PUCCH resource, and the network device allocates a PUSCH to the terminal device according to a data amount interval corresponding to the PUCCH resource, and the terminal device may select data of a corresponding amount of data to upload according to a need, whether the data is the data to be transmitted of the uplink logical channel corresponding to the PUCCH resource for transmitting SR or not. Alternatively, when the terminal device selects at least one candidate PUCCH resource from each PUCCH resource group, the terminal device may further determine one PUCCH resource as the target PUCCH resource from the at least one candidate PUCCH resource selected from each PUCCH resource, i.e. the terminal device may determine a corresponding one PUCCH resource as the target PUCCH resource from each PUCCH resource group. For example, assuming that a total of 3 uplink logical channels are respectively configured with one PUCCH resource group, and that the 3 uplink logical channels each individually trigger a regular BSR, the terminal device may determine, according to respective data amounts to be transmitted, one PUCCH resource from the corresponding one PUCCH resource group as a target PUCCH resource, that is, determine 3 PUCCH resources as target PUCCH resources, and the terminal device may respectively transmit SRs on the 3 PUCCH resources, and when the terminal device receives SRs on the 3 PUCCH resources, may allocate PUSCH resources for transmitting uplink data to the terminal device according to a sum of data amount intervals corresponding to the 3 PUCCH resources, respectively.
Mode two: the terminal device may sort the priorities of the N uplink logical channels, and use the data amount to be transmitted of the uplink logical channel with the highest priority as the basis for selecting the candidate PUCCH resource from each PUCCH resource group in at least one PUCCH resource group. That is, assuming that n=4, the identifiers are respectively 0 to 3, the identifier of the uplink logical channel with the highest priority is 2, the amount of data to be transmitted of the uplink logical channel is a, the at least one PUCCH resource group is 2 PUCCH resource groups, namely PUCCH resource group 1 and PUCCH resource group 2, respectively, and the terminal device may select at least one candidate PUCCH resource from PUCCH resource group 1 and at least one candidate PUCCH resource from PUCCH resource group 2, respectively, according to the amount of data to be transmitted a. Since the PUCCH resources included in the PUCCH resource group 1 may be the same as or different from the PUCCH resources included in the PUCCH resource group 2, if they are the same, the candidate PUCCH resources respectively selected from the two PUCCH resource groups may be the same; if different, the candidate PUCCH resources respectively selected from the two PUCCH resource groups may be different. At this time, for the network device, the network device only needs to allocate a suitable PUSCH for an uplink data volume interval corresponding to the PUCCH resource that receives the SR, and does not need to distinguish whether the PUSCH resource is allocated to which uplink logical channel of the terminal device, and specifically, the data to be transmitted of which uplink logical channel is transmitted may be determined by the terminal device.
Mode three: the terminal device may add the data amounts to be transmitted of the N uplink logical channels, and use the sum of the data amounts to be transmitted of the N uplink logical channels as a basis for selecting candidate PUCCH resources from each PUCCH resource group in at least one PUCCH resource group, respectively. That is, assuming that n=4, the sum of the amounts of data to be transmitted of the 4 uplink logical channels is B, the at least one PUCCH resource group is 2 PUCCH resource groups, namely PUCCH resource group 1 and PUCCH resource group 2, respectively, and the terminal device may select at least one candidate PUCCH resource from PUCCH resource group 1 and at least one candidate PUCCH resource from PUCCH resource group 2, respectively, according to the amount of data to be transmitted B. Since the PUCCH resources included in the PUCCH resource group 1 may be the same as or different from the PUCCH resources included in the PUCCH resource group 2, if they are the same, the candidate PUCCH resources respectively selected from the two PUCCH resource groups may be the same; if different, the candidate PUCCH resources respectively selected from the two PUCCH resource groups may be different. At this time, for the network device, the PUSCH allocated by the network device for the uplink data volume interval corresponding to the PUCCH resource received the SR may enable the terminal device to transmit the data to be transmitted of all the current uplink logical channels, so that the time delay in the uplink scheduling process may be greatly reduced.
Optionally, in the embodiment of the present application, the network device may configure at least one uplink Bandwidth Part (BWP) for the terminal device, and then, for any uplink BWP, the network device may separately configure a plurality of PUCCH resources for transmitting SRs. That is, the network device may configure N PUCCH resources for the uplink BWP1, and configure M PUCCH resources for the uplink BWP2, where N may be equal to or different from M. Further, the network device may configure a number to the terminal device through broadcast or radio resource control (Radio Resource Control, RRC) dedicated signaling, and the terminal device may know how many PUCCH resources per uplink logical channel are on the BWP configured by the network device as long as the number is received. For each uplink logical channel to be configured with PUCCH resources for transmitting SRs, the network device may select, from N PUCCH resources on uplink BWP1, the number of PUCCH resources broadcast by the network device to be configured with the uplink logical channel; and selecting the quantity of PUCCH resources broadcasted by the network equipment from M PUCCH resources on the uplink BWP2 to be allocated to the uplink logic channel.
When the network device broadcasts the number of PUCCH resources to the terminal devices, the number of PUCCH resources configured by each uplink logical channel of different terminal devices is the same, but the number of PUCCH resources configured by different terminal devices on one uplink BWP is not necessarily the same. For example, the number of PUCCH resources broadcast by the network device is 2.UE1 has 2 uplink Logical Channels (LCs): LC11 and LC12, LC11 configures PUCCH resource 1 and PUCCH resource 2 on one uplink BWP, and LC12 configures PUCCH resource 1 and PUCCH resource 3 on the same uplink BWP, wherein the data amount intervals corresponding to PUCCH resource 2 and PUCCH resource 3 may be the same, but may be used for allocation to different LCs of the UE. UE2 has 2 LCs: LC21 and LC22, LC21 configures PUCCH 4 and PUCCH 5 on one uplink BWP, and LC22 configures PUCCH 4 and PUCCH 5 on the same UL BWP.
Optionally, for the same uplink BWP of the terminal device, the network device configures PUCCH resources for at least one uplink logical channel and the number of PUCCH resources corresponding to each uplink logical channel in the at least one uplink logical channel may be the same or different. If the number of the PUCCH resources is the same, the network device may only need to configure one PUCCH resource for the uplink logical channel of one terminal, and the number of the PUCCH resources configured is the same for all uplink logical channels on the uplink BWP where the PUCCH resources are configured. If the number of PUCCH resources is different, the network device needs to configure the number of PUCCH resources for the uplink logical channel of one terminal.
Alternatively, for the same uplink logical channel configured with PUCCH resources of the terminal device, the number of PUCCH resources corresponding to different uplink BWP may be the same or different. That is, when the network device configures PUCCH resources for each uplink logical channel, the network device may be associated with an uplink BWP, and the network device may configure a number of PUCCH resources for one uplink logical channel, so that the terminal device may determine that the number of PUCCH resources corresponding to the uplink logical channel is the same on any BWP; the network device may also configure the number of PUCCH resources for different BWP for one uplink logical channel, respectively. The terminal device may determine the number of PUCCH resources corresponding to the uplink logical channel corresponding thereto on any one BWP, respectively.
The configuration of PUCCH resources may include the following parameters: time domain resource locations and resource indexes. Any two PUCCH resources in one PUCCH resource group corresponding to one uplink logical channel may be the same in time domain resource position and different in resource index; or the time domain resource positions are different, and the resource indexes are the same; or it may be that the time domain resource location is different from the resource index. Wherein the time domain resource locations may be characterized by a period and/or a time offset.
As apparent from the above description, the terminal device may receive configuration information transmitted by the network device, and in particular, may include at least one of configuration information of an uplink BWP, configuration information of an uplink logical channel, and configuration information of an SR. For example, the configuration information of the uplink BWP is used to indicate that at least one uplink BWP is configured for the terminal device, and for each uplink BWP, a plurality of PUCCH resources for transmitting SRs are configured. For another example, the configuration information of the uplink logical channel may refer to whether PUCCH resources for transmitting SRs are configured for each uplink logical channel of the terminal device. If the PUCCH resources configured for the uplink logical channel to transmit SR are selected, the number of PUCCH resources configured on each uplink BWP for the uplink logical channel may be N. For another example, the configuration information of the uplink logical channel may also refer to an uplink logical channel in which PUCCH resources for transmitting SRs are configured for each terminal device, where N PUCCH resources for transmitting SRs configured on the same uplink BWP in the uplink logical channel may respectively correspond to N data volume sections.
Optionally, the terminal device may further acquire first information in advance, where the first information is used for a number of multiple PUCCH resources configured for the terminal device, and/or a correspondence between PUCCH resources and a data volume interval. And the terminal equipment can determine the target PUCCH resource from the plurality of PUCCH resources through the data quantity to be transmitted. Alternatively, the first information may be predefined information, information broadcasted by a system message, or information carried in RRC signaling.
The method of the embodiment of the application is particularly suitable for NTN, so that the terminal equipment can obtain the rough uplink data transmission requirement of the terminal equipment through the SR transmission, and the scheduling of the network equipment can be obtained as soon as possible to transmit the uplink data, thereby reducing the uplink service time delay.
Three specific embodiments provided herein will be described in detail below in conjunction with fig. 4-6.
Example 1: the number of 1 SR resources configured on one uplink BWP by the uplink logical channel may be determined through network broadcasting or a predefined manner. For all terminals in a cell, if SR resources are configured for uplink logical channels of the terminals, the number of SR resources on one uplink BWP of the uplink logical channels of different terminals is the same.
1. The UE receives the system message (including UE1 and UE 2), acquires the following information:
1. in the case where the network configures PUCCH resources for transmission of SRs for an uplink logical channel, the network assigns the number n_sr=3 of PUCCH resources for transmission of SRs configured on each uplink BWP to the uplink logical channel.
2. 2 uplink data amount thresholds ul_data_th_1 and ul_data_th_2, wherein ul_data_th_1< ul_data_th_2. With these 2 threshold configurations, the uplink data amount can be divided into 3 levels (levels) according to the data amount size:
uplink data amount level 1:0< uplink data amount < = ul_data_th_1
Uplink data amount level 2: ul_data_th_1< uplink data amount < = ul_data_th_2
Uplink data volume level 3 uplink data volume > ul_data_th_2
2. UE1 and UE2 respectively receive the network RRC configuration information, configure uplink BWP related parameters, uplink logic channel related parameters and SR related parameters. Specifically:
1. for UE1 and UE2, 1 uplink BWP is configured, respectively, and the same uplink BWP is configured for these 2 UEs;
2. for UE1 and UE2, respectively configuring 3 PUCCH resources for transmitting SR on the configured uplink BWP, and respectively indicating an uplink data amount level corresponding to each PUCCH resource.
3. For UE1 and UE2, 1 uplink logical channel is configured, and 3 PUCCH resources for transmitting SR are configured for the uplink logical channel, respectively. The 3 PUCCH resources configured for each uplink logical channel for transmitting SRs are 3 PUCCH resources configured for the UE on uplink BWP in (two).
3. For UE1, if at a certain moment UE1 has uplink data arrives, a Regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers an SR. The current data size of the UE1 is in the data size range corresponding to the uplink data size level1, so that the UE transmits the SR on the PUCCH resource corresponding to the uplink data size level1 nearest to the current time.
4. The network receives the SR sent by the UE1, and according to the PUCCH resource position for receiving the SR, the network can acquire that the data volume of the UE is the uplink data volume level1, and the network allocates proper PUSCH resources for the UE according to the data volume information.
5. If at a certain moment UE1 has uplink data arrived, regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers SR. The current data size of the UE1 is in the data size range corresponding to the uplink data size level3, so the UE transmits the SR on the PUCCH resource corresponding to the uplink data size level3 nearest to the current time.
6. The network receives the SR sent by the UE1, and according to the PUCCH resource position of the received SR, the network can learn that the data volume of the UE is the uplink data volume level3, and allocates an appropriate PUSCH resource for the UE according to the data volume information.
7. For UE2, at a certain moment, when UE2 has uplink data arrived, a Regular BSR is triggered, and UE2 has no uplink resource for transmitting the initial transmission, UE2 triggers an SR. The method for UE2 to select PUCCH resources to send SR according to the current data amount is the same as UE1, for example, SR is triggered at a certain time, the current data amount of UE2 is at level3 or SR is triggered at a certain time, and the current data amount of UE2 is at level 2, which is not described herein.
A schematic of example 1 is shown in fig. 4.
Example 2: the number of SR resources configured on one uplink BWP by the uplink logical channel may be determined through network broadcasting or a predefined manner. For all terminals in a cell, if SR resources are configured for the uplink logical channels of the terminal, the number of SR resources on one uplink BWP for the uplink logical channels of different terminals may be different.
1. The UE receives the system message (including UE1 and UE 2), acquires the following information:
1. in the case where the network configures PUCCH resources for transmission of SRs for an uplink logical channel, the network assigns the uplink logical channel the number n_sr1=2 and n_sr2=3 of PUCCH resources for transmission of SRs configured on each uplink BWP.
2. 2 sets of uplink data amount threshold values:
the first set of threshold values corresponds to n_sr1=2, comprising 1 uplink data amount threshold ul_data_th_1_1. With the 1 threshold configuration, the uplink data size can be divided into 2 levels according to the data size: an upstream data amount level11 of 0< upstream data amount < = ul_data_th_1_1; uplink data amount level21 uplink data amount > ul_data_th_1_1.
The second set of thresholds corresponds to n_sr2=3, comprising 2 uplink data amount thresholds ul_data_th_1_2 and ul_data_th_2_2, wherein ul_data_th_1_2< ul_data_th_2_2. With these 2 threshold configurations, the uplink data size can be divided into 3 levels according to the data size: an upstream data amount level12 of 0< upstream data amount < = ul_data_th_1_2; uplink data amount level22 uplink data th 12 uplink data amount < = ul data th 2; uplink data amount level32 uplink data amount > ul_data_th_2_2.
2.1, the UE1 receives the network RRC configuration information, configures uplink BWP related parameters, uplink logic channel related parameters and SR related parameters. Specifically:
1. 1 uplink BWP is configured, 3 PUCCH resources for transmitting SR are configured on the uplink BWP, and an uplink data amount level corresponding to each PUCCH resource is indicated, respectively.
2. 1 uplink logic channel is configured, and 3 PUCCH resources for transmitting SR are configured for the uplink logic channel. The 3 PUCCH resources configured for each uplink logical channel for transmitting SRs are 3 PUCCH resources configured for UE1 on uplink BWP in (a) for transmitting SRs.
2.2, the UE2 receives the network RRC configuration information, configures uplink BWP related parameters, uplink logic channel related parameters and SR related parameters. Specifically:
1. 1 uplink BWP (the same uplink BWP configured by UE 1) is configured, and 2 PUCCH resources for transmitting SR are configured on the uplink BWP, and an uplink data amount level corresponding to each PUCCH resource is indicated, respectively.
2. 1 uplink logic channel is configured, and 2 PUCCH resources for transmitting SR are configured for the uplink logic channel. The 2 PUCCH resources for transmitting SRs for each uplink logical channel quality are the 2 PUCCH resources for transmitting SRs configured on the uplink BWP for the UE2 in (a).
3. For UE1, if at a certain moment UE1 has uplink data arrives, a Regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers an SR. The current data size of UE1 is in the data size range corresponding to the uplink data size level12, so UE1 transmits SR on PUCCH resource corresponding to the uplink data size level12 nearest to the current time.
4. The network receives the SR sent by the UE1, and according to the PUCCH resource position of the received SR, the network can learn that the data volume of the UE is the uplink data volume level12, and allocates an appropriate PUSCH resource for the UE according to the data volume information.
5. At a certain moment, when UE1 has uplink data arrived, a Regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers an SR. The current data size of UE1 is in the data size range corresponding to the uplink data size level32, so the UE transmits SR on the PUCCH resource corresponding to the uplink data size level32 nearest to the current time.
6. The network receives the SR sent by the UE1, and according to the PUCCH resource position of the received SR, the network can learn that the data volume of the UE is the uplink data volume level32, and allocates an appropriate PUSCH resource for the UE according to the data volume information.
7. For UE2, at a certain moment, when UE2 has uplink data arrived, a Regular BSR is triggered, and UE2 has no uplink resource for transmitting the initial transmission, UE2 triggers an SR. The method for UE2 to select PUCCH resources to send SR according to the current data amount is the same as UE1, for example, SR is triggered at a certain time, the current data amount of UE2 is at level 11 or SR is triggered at a certain time, and the current data amount of UE2 is at level 21, which is not described herein.
A schematic of example 2 is shown in fig. 5.
Example 3: the UE determines the SR resource number configured on one UL BWP for one uplink logic channel of the UE in a special RRC signaling mode. For a terminal in a cell, if SR resources are configured for the uplink logical channel of the terminal, the number of SR resources on one uplink BWP for different uplink logical channels of the terminal may be different.
1. The UE1 receives the network RRC configuration information, configures uplink BWP-related parameters, uplink logical channel-related parameters, SR-related parameters. Specifically:
1. in the case that the network configures PUCCH resources for transmitting SR for the uplink logical channel of UE1, the number n_sr_1=3 of PUCCH resources for transmitting SR configured on each uplink BWP by the uplink logical channel of the network to the UE;
2. 2 uplink data amount thresholds ul_data_th_1_1 and data_th_2_1, wherein ul_data_th_1_1< ul_data_th_2_1. With these 2 threshold configurations, the uplink data size can be divided into 3 levels according to the data size: an upstream data amount level11 of 0< upstream data amount < = ul_data_th_1_1; ul_data_th_1_1< ul_data_th_2_1; uplink data amount level31 uplink data amount > ul_data_th_2_1.
3. 1 uplink BWP is configured for the UE1, 3 PUCCH resources for transmitting SR are configured on the uplink BWP, and an uplink data amount level corresponding to each PUCCH resource is indicated, respectively.
4. 1 uplink logic channel is configured for the UE1, and 3 PUCCH resources for transmitting SR are configured for the uplink logic channel. The 3 PUCCH resources configured for each uplink logical channel for transmitting SRs are 3 PUCCH resources configured for UE1 on uplink BWP in (iii).
2. UE2 receives the network RRC configuration information, configures UL BWP-related parameters, UL logical channel-related parameters, SR-related parameters. Specifically:
1. in case that the network configures PUCCH resources for transmission of SR for the uplink logical channel of UE2, the network configures the number n_sr_2=2 of PUCCH resources for transmission of SR for each uplink BWP for the uplink logical channel
2. 1 uplink data amount threshold ul_data_th_1_2. With this threshold configuration, the uplink data amount can be divided into 2 levels according to the data amount size: an upstream data amount level12 of 0< upstream data amount < = ul_data_th_1_2; uplink data amount level22 uplink data amount > ul_data_th_1_2.
3. 1 uplink BWP is configured for the UE2, 2 PUCCH resources for transmitting SR are configured on the uplink BWP, and an uplink data amount level corresponding to each PUCCH resource is indicated, respectively.
4. 1 uplink logical channel is configured for the UE2, and 2 PUCCH resources for transmitting SR are configured for the uplink logical channel. The 2 PUCCH resources configured for each uplink logical channel for transmitting SRs are 2 PUCCH resources configured for UE2 on uplink BWP in (iii).
3. For UE1, at a certain moment, when UE1 has uplink data arrived, a Regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers an SR. The current data size of UE1 is in the data size range corresponding to the uplink data size level11, so the UE transmits SR on the PUCCH resource corresponding to the uplink data size level11 nearest to the current time.
4. The network receives the SR sent by the UE1, and according to the PUCCH resource position of the received SR, the network can learn that the data volume of the UE is the uplink data volume level11, and allocates an appropriate PUSCH resource for the UE according to the data volume information.
5. At a certain moment, when UE1 has uplink data arrived, a Regular BSR is triggered, and UE1 has no uplink resource for transmitting the initial transmission, UE1 triggers an SR. The current data size of UE1 is in the data size range corresponding to the uplink data size level31, so the UE transmits SR on the PUCCH resource corresponding to the uplink data size level31 nearest to the current time.
6. The network receives the SR sent by the UE1, and according to the PUCCH resource position of the received SR, the network can learn that the data volume of the UE is the uplink data volume level 31, and allocates an appropriate PUSCH resource for the UE according to the data volume information.
7. For UE2, at a certain moment, when UE2 has uplink data arrived, a Regular BSR is triggered, and UE2 has no uplink resource for transmitting the initial transmission, UE2 triggers an SR. The method for UE2 to select PUCCH resources to send SR according to the current data amount is the same as UE1, for example, SR is triggered at a certain time, the current data amount of UE2 is at level 12 or SR is triggered at a certain time, and the current data amount of UE2 is at level 22, which is not described herein.
A schematic of example 3 is shown in fig. 6.
Fig. 7 is a schematic block diagram of a method 400 for transmitting data according to an embodiment of the present application. As shown in fig. 7, the method 400 includes some or all of the following:
s410, the network equipment receives a scheduling request SR sent by the terminal equipment on a first physical uplink control channel PUCCH resource;
s420, the network device determines a data volume interval corresponding to the first PUCCH resource from a plurality of PUCCH resources configured for the terminal device and used for transmitting SRs, where the plurality of PUCCH resources correspond to a plurality of data volume intervals;
And S430, the network equipment allocates Physical Uplink Shared Channel (PUSCH) resources for transmitting data to the terminal equipment according to the data volume interval corresponding to the first PUCCH resources.
Optionally, in an embodiment of the present application, the method further includes: the network device sends first information to the terminal device, where the first information is used to indicate the number of the plurality of PUCCH resources and/or the correspondence between the PUCCH resources and a data volume interval.
Optionally, in an embodiment of the present application, the network device sends first information to the terminal device, including: the network device sends the first information to the terminal device through a system message or Radio Resource Control (RRC) signaling.
Optionally, in the embodiment of the present application, on the same uplink bandwidth portion BWP of the terminal device, the number of PUCCH resources corresponding to different uplink logical channels of the terminal device is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink logical channel of the terminal device on different uplink bandwidth portions BWP of the terminal device is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink bandwidth portion BWP in one uplink logical channel of different terminal devices is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink bandwidth portion BWP on one uplink logical channel of different terminal devices is different.
Optionally, in an embodiment of the present application, the method further includes: the network device sends second information to the terminal device, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
Optionally, in this embodiment of the present application, the plurality of PUCCH resources include at least one PUCCH resource group, and each PUCCH resource group in the at least one PUCCH resource group includes a PUCCH resource one-to-one corresponding to a plurality of data volume intervals, and the configuration information of the uplink logical channel is used to indicate the PUCCH resource group corresponding to at least one uplink logical channel.
Optionally, in the embodiment of the present application, indexes and/or time domain resource positions of any two PUCCH resources included in the first PUCCH resource group in the at least one PUCCH resource group are different.
Optionally, in this embodiment of the present application, the number of PUCCH resources included in the second PUCCH resource group in the at least one PUCCH resource group is M, and M data volume intervals corresponding to the second PUCCH resource group are divided by (M-1) thresholds, where M is a positive integer greater than 1.
Optionally, in an embodiment of the present application, the method is applied in a non-terrestrial communication network NTN.
It should be understood that the interactions between the network device and the terminal device described on the network side and the related characteristics, functions, etc. correspond to the related characteristics, functions of the terminal device. And related content is described in detail in the method 300, and is not described herein for brevity.
It should also be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Having described in detail the method for transmitting data according to the embodiment of the present application above, the apparatus for transmitting data according to the embodiment of the present application will be described below with reference to fig. 8 to 10, and technical features described in the method embodiment are applicable to the following apparatus embodiments.
Fig. 8 shows a schematic block diagram of a terminal device 500 of an embodiment of the present application. As shown in fig. 8, the terminal device 500 includes:
a processing unit 510, configured to determine, according to a data amount to be transmitted, a target PUCCH resource from a plurality of physical uplink control channel PUCCH resources for transmitting a scheduling request SR, where the plurality of PUCCH resources correspond to a plurality of data amount intervals;
A transceiver unit 520, configured to send an SR on the target PUCCH resource.
Optionally, in this embodiment of the present application, the plurality of PUCCH resources include at least one PUCCH resource group, and each PUCCH resource group in the at least one PUCCH resource group includes a PUCCH resource one-to-one corresponding to a plurality of data volume intervals, and the processing unit is specifically configured to: and determining the target PUCCH resource from the at least one PUCCH resource group according to the data quantity to be transmitted of N uplink logic channels triggering the conventional buffer status report BSR, wherein the at least one PUCCH resource group corresponds to at least one uplink logic channel configured with the PUCCH resource in the N uplink logic channels, and N is a positive integer.
Optionally, in the embodiment of the present application, the determining, by the processing unit, the target PUCCH resource from the at least one PUCCH resource group according to the amount of data to be transmitted of the N uplink logical channels that trigger the regular buffer status report BSR includes: determining at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data quantity to be transmitted of the N uplink logical channels; and determining the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group.
Optionally, in the embodiment of the present application, the processing unit determines, according to the data amounts to be transmitted of the N uplink logical channels, at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group, including: and determining the at least one candidate PUCCH resource from the corresponding PUCCH resource group according to the data quantity to be transmitted of each uplink logical channel in the at least one uplink logical channel.
Optionally, in the embodiment of the present application, the processing unit determines, according to the data amounts to be transmitted of the N uplink logical channels, at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group, including: and determining the at least one candidate PUCCH resource from each PUCCH resource group according to the data quantity to be transmitted of the uplink logical channel with the highest priority in the N uplink logical channels.
Optionally, in the embodiment of the present application, the processing unit determines, according to the data amounts to be transmitted of the N uplink logical channels, at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group, including: and determining the at least one PUCCH resource from each PUCCH resource group according to the sum of the data quantity to be transmitted of all uplink logical channels in the N uplink logical channels.
Optionally, in an embodiment of the present application, the determining, by the processing unit, the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group includes: and determining one PUCCH resource closest to the current time in the candidate PUCCH resources determined from the at least one PUCCH resource group as the target PUCCH resource.
Optionally, in an embodiment of the present application, the determining, by the processing unit, the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group includes: and determining the target PUCCH resource from the candidate PUCCH resources determined in one PUCCH resource group corresponding to the uplink logical channel with the highest priority in the at least one uplink logical channel.
Optionally, in this embodiment of the present application, on the same uplink bandwidth portion BWP of the terminal device, the number of PUCCH resources included in one PUCCH resource group corresponding to each uplink logical channel in the at least one uplink logical channel is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources included in a PUCCH resource group corresponding to the same uplink logical channel of the terminal device on different uplink bandwidth portions BWP of the terminal device is the same.
Optionally, in the embodiment of the present application, indexes and/or time domain resource positions of any two PUCCH resources included in the first PUCCH resource group in the at least one PUCCH resource group are different.
Optionally, in this embodiment of the present application, the number of PUCCH resources included in the second PUCCH resource group in the at least one PUCCH resource group is M, and M data volume intervals corresponding to the second PUCCH resource group are divided by (M-1) thresholds, where M is a positive integer greater than 1.
Optionally, in an embodiment of the present application, the processing unit is further configured to: and determining the plurality of PUCCH resources according to the currently activated uplink bandwidth part BWP.
Optionally, in an embodiment of the present application, the processing unit is further configured to: and acquiring first information, wherein the first information is used for indicating the number of the plurality of PUCCH resources and/or the corresponding relation between the PUCCH resources and the data volume interval.
Optionally, in an embodiment of the present application, the processing unit is specifically configured to: the first information is acquired from the following information: predefined information, system messages, or radio resource control RRC signaling.
Optionally, in an embodiment of the present application, the transceiver unit is further configured to: receiving second information sent by the network equipment, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
Optionally, in the embodiment of the present application, the terminal device is applied to a non-terrestrial communication network NTN.
It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the method of fig. 3, which is not described herein for brevity.
Fig. 9 shows a schematic block diagram of a network device 600 of an embodiment of the present application. As shown in fig. 9, the network device 600 includes:
a transceiver unit 610, configured to receive a scheduling request SR sent by a terminal device on a first physical uplink control channel PUCCH resource;
a processing unit 620, configured to determine a data volume interval corresponding to the first PUCCH resource from a plurality of PUCCH resources configured for the terminal device for transmitting SR, where the plurality of PUCCH resources correspond to a plurality of data volume intervals, and
and allocating Physical Uplink Shared Channel (PUSCH) resources for transmitting data to the terminal equipment according to the data volume interval corresponding to the first PUCCH resources.
Optionally, in an embodiment of the present application, the transceiver unit is further configured to: and sending first information to the terminal equipment, wherein the first information is used for indicating the number of the plurality of PUCCH resources and/or the corresponding relation between the PUCCH resources and the data volume interval.
Optionally, in an embodiment of the present application, the transceiver unit is specifically configured to: and sending the first information to the terminal equipment through a system message or Radio Resource Control (RRC) signaling.
Optionally, in the embodiment of the present application, on the same uplink bandwidth portion BWP of the terminal device, the number of PUCCH resources corresponding to different uplink logical channels of the terminal device is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink logical channel of the terminal device on different uplink bandwidth portions BWP of the terminal device is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink bandwidth portion BWP in one uplink logical channel of different terminal devices is the same.
Optionally, in the embodiment of the present application, the number of PUCCH resources corresponding to the same uplink bandwidth portion BWP on one uplink logical channel of different terminal devices is different.
Optionally, in an embodiment of the present application, the transceiver unit is further configured to: transmitting second information to the terminal device, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
Optionally, in this embodiment of the present application, the plurality of PUCCH resources include at least one PUCCH resource group, and each PUCCH resource group in the at least one PUCCH resource group includes a PUCCH resource one-to-one corresponding to a plurality of data volume intervals, and the configuration information of the uplink logical channel is used to indicate the PUCCH resource group corresponding to at least one uplink logical channel.
Optionally, in the embodiment of the present application, indexes and/or time domain resource positions of any two PUCCH resources included in the first PUCCH resource group in the at least one PUCCH resource group are different.
Optionally, in this embodiment of the present application, the number of PUCCH resources included in the second PUCCH resource group in the at least one PUCCH resource group is M, and M data volume intervals corresponding to the second PUCCH resource group are divided by (M-1) thresholds, where M is a positive integer greater than 1.
Optionally, in an embodiment of the present application, the network device is applied in a non-terrestrial communication network NTN.
It should be understood that the network device 600 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 600 are respectively for implementing the corresponding flow of the network device in the method of fig. 7, which is not described herein for brevity.
Fig. 10 is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application. The communication device 700 shown in fig. 10 comprises a processor 710, from which the processor 710 may call and run a computer program to implement the method in the embodiments of the present application.
Optionally, as shown in fig. 10, the communication device 700 may further comprise a memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the methods in embodiments of the present application.
Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.
Optionally, as shown in fig. 10, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
Among other things, transceiver 730 may include a transmitter and a receiver. Transceiver 730 may further include antennas, the number of which may be one or more.
Optionally, the communication device 700 may be specifically a network device in the embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 700 may be specifically a terminal device in the embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Fig. 11 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 800 shown in fig. 11 includes a processor 810, and the processor 810 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.
Optionally, as shown in fig. 11, chip 800 may also include a memory 820. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application.
Wherein the memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.
Optionally, the chip 800 may also include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.
Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to a terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
Fig. 12 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 12, the communication system 900 includes a terminal device 910 and a network device 920.
The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the above method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the above method, which are not described herein for brevity.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.
Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.
Optionally, the computer readable storage medium may be applied to a terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.
Optionally, the computer program product may be applied to a terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.
Optionally, the computer program may be applied to a terminal device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the terminal device in each method in the embodiments of the present application, which is not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (58)

1. A method for transmitting data, comprising:
the terminal equipment determines target PUCCH resources from a plurality of Physical Uplink Control Channel (PUCCH) resources for transmitting Scheduling Requests (SR) according to the data quantity to be transmitted, wherein the PUCCH resources correspond to a plurality of data quantity intervals;
the terminal equipment sends an SR on the target PUCCH resource; the terminal device determines, according to a data amount to be transmitted, a target PUCCH resource from a plurality of physical uplink control channel PUCCH resources for transmitting a scheduling request SR, where the plurality of PUCCH resources include at least one PUCCH resource group, and each PUCCH resource included in the at least one PUCCH resource group corresponds to a plurality of data amount intervals one by one, and includes:
the terminal equipment determines the target PUCCH resource from the at least one PUCCH resource group according to the data quantity to be transmitted of N uplink logic channels triggering a regular Buffer Status Report (BSR), wherein the at least one PUCCH resource group corresponds to at least one uplink logic channel configured with the PUCCH resource in the N uplink logic channels, and N is a positive integer.
2. The method according to claim 1, wherein the determining, by the terminal device, the target PUCCH resource from the at least one PUCCH resource group according to the amount of data to be transmitted of the N uplink logical channels triggering the regular buffer status report BSR, includes:
the terminal equipment determines at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data quantity to be transmitted of the N uplink logical channels;
and the terminal equipment determines the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group.
3. The method according to claim 2, wherein the determining, by the terminal device, at least one candidate PUCCH resource from each of the at least one PUCCH resource group according to the data amounts to be transmitted of the N uplink logical channels, includes:
and the terminal equipment respectively determines the at least one candidate PUCCH resource from a corresponding PUCCH resource group according to the data quantity to be transmitted of each uplink logical channel in the at least one uplink logical channel.
4. The method according to claim 2, wherein the determining, by the terminal device, at least one candidate PUCCH resource from each of the at least one PUCCH resource group according to the data amounts to be transmitted of the N uplink logical channels, includes:
And the terminal equipment respectively determines the at least one candidate PUCCH resource from each PUCCH resource group according to the data quantity to be transmitted of the uplink logical channel with the highest priority in the N uplink logical channels.
5. The method according to claim 2, wherein the determining, by the terminal device, at least one candidate PUCCH resource from each of the at least one PUCCH resource group according to the data amounts to be transmitted of the N uplink logical channels, includes:
and the terminal equipment respectively determines the at least one PUCCH resource from each PUCCH resource group according to the sum of the data quantity to be transmitted of all uplink logical channels in the N uplink logical channels.
6. The method according to any of claims 2 to 5, wherein the determining, by the terminal device, the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group comprises:
and the terminal equipment determines one PUCCH resource closest to the current time in the candidate PUCCH resources determined from the at least one PUCCH resource group as the target PUCCH resource.
7. The method according to any of claims 2 to 5, wherein the determining, by the terminal device, the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group comprises:
And the terminal equipment determines the target PUCCH resource from candidate PUCCH resources determined in one PUCCH resource group corresponding to the uplink logical channel with the highest priority in the at least one uplink logical channel.
8. The method according to any one of claims 1 to 5, wherein, on the same uplink bandwidth portion BWP of the terminal device, one PUCCH resource group corresponding to each uplink logical channel in the at least one uplink logical channel includes the same number of PUCCH resources.
9. The method according to any of claims 1 to 5, wherein the same uplink logical channel of the terminal device comprises the same number of PUCCH resources as a corresponding one PUCCH resource group on different uplink bandwidth parts BWP of the terminal device.
10. The method according to any of claims 1 to 5, wherein the index and/or time domain resource position of any two PUCCH resources comprised in a first PUCCH resource group of the at least one PUCCH resource group is different.
11. The method according to any one of claims 1 to 5, wherein a second PUCCH resource group of the at least one PUCCH resource group includes M PUCCH resources, the M data volume sections corresponding to the second PUCCH resource group are divided by (M-1) thresholds, and M is a positive integer greater than 1.
12. The method according to any one of claims 1 to 5, further comprising:
the terminal equipment determines the plurality of PUCCH resources according to the current activated uplink bandwidth part BWP.
13. The method according to any one of claims 1 to 5, further comprising:
the terminal equipment acquires first information, wherein the first information is used for indicating the number of the plurality of PUCCH resources and/or the corresponding relation between the PUCCH resources and the data volume interval.
14. The method of claim 13, wherein the terminal device obtains the first information, comprising:
the terminal equipment acquires the first information from the following information: predefined information, system messages, or radio resource control RRC signaling.
15. The method according to any one of claims 1 to 5, further comprising:
the terminal equipment receives second information sent by the network equipment, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
16. The method according to any of claims 1 to 5, characterized in that it is applied in a non-terrestrial communication network NTN.
17. A method for transmitting data, comprising:
the network equipment receives a scheduling request SR sent by the terminal equipment on a first physical uplink control channel PUCCH resource;
the network device determines a data volume interval corresponding to the first PUCCH resource from a plurality of PUCCH resources configured for the terminal device and used for transmitting SR, wherein the plurality of PUCCH resources correspond to a plurality of data volume intervals;
the network equipment allocates Physical Uplink Shared Channel (PUSCH) resources for transmitting data to the terminal equipment according to the data volume interval corresponding to the first PUCCH resources; wherein,
on the same uplink bandwidth part BWP of the terminal equipment, the number of PUCCH resources corresponding to different uplink logic channels of the terminal equipment is the same; or,
the same uplink logical channel of the terminal equipment has the same number of corresponding PUCCH resources on different uplink bandwidth parts BWP of the terminal equipment.
18. The method of claim 17, wherein the method further comprises:
the network device sends first information to the terminal device, where the first information is used to indicate the number of the plurality of PUCCH resources and/or the correspondence between the PUCCH resources and a data volume interval.
19. The method of claim 18, wherein the network device sending the first information to the terminal device comprises:
the network device sends the first information to the terminal device through a system message or Radio Resource Control (RRC) signaling.
20. The method according to any of claims 17 to 19, wherein the number of PUCCH resources corresponding to one uplink logical channel of different terminal devices in the same uplink bandwidth portion BWP is the same.
21. The method according to any one of claims 17 to 19, wherein the number of PUCCH resources corresponding to one uplink logical channel of different terminal devices in the same uplink bandwidth portion BWP is different.
22. The method according to any one of claims 17 to 19, further comprising:
the network device sends second information to the terminal device, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
23. The method of claim 22, wherein the plurality of PUCCH resources comprises at least one PUCCH resource group, each PUCCH resource group in the at least one PUCCH resource group comprises a PUCCH resource one-to-one correspondence with a plurality of data volume sections, and the configuration information of the uplink logical channel is used to indicate the PUCCH resource group corresponding to at least one uplink logical channel.
24. The method according to claim 23, wherein the index and/or time domain resource position of any two PUCCH resources included in the first PUCCH resource group in the at least one PUCCH resource group is different.
25. The method of claim 23, wherein a second PUCCH resource group of the at least one PUCCH resource group includes M PUCCH resources, the M data volume intervals corresponding to the second PUCCH resource group are divided by (M-1) thresholds, and M is a positive integer greater than 1.
26. The method according to any of the claims 17 to 19, characterized in that the method is applied in a non-terrestrial communication network NTN.
27. A terminal device, characterized in that the terminal device comprises:
a processing unit, configured to determine a target PUCCH resource from a plurality of physical uplink control channel PUCCH resources for transmitting a scheduling request SR according to a data amount to be transmitted, where the plurality of PUCCH resources correspond to a plurality of data amount intervals;
a transceiver unit, configured to send an SR on the target PUCCH resource; the plurality of PUCCH resources include at least one PUCCH resource group, each PUCCH resource group in the at least one PUCCH resource group includes a PUCCH resource one-to-one corresponding to a plurality of data volume intervals, and the processing unit is specifically configured to:
And determining the target PUCCH resource from the at least one PUCCH resource group according to the data quantity to be transmitted of N uplink logic channels triggering the conventional buffer status report BSR, wherein the at least one PUCCH resource group corresponds to at least one uplink logic channel configured with the PUCCH resource in the N uplink logic channels, and N is a positive integer.
28. The terminal device of claim 27, wherein the processing unit determines the target PUCCH resource from the at least one PUCCH resource group according to the amount of data to be transmitted for the N uplink logical channels triggering the regular buffer status report BSR, comprising:
determining at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data quantity to be transmitted of the N uplink logical channels;
and determining the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group.
29. The terminal device of claim 28, wherein the processing unit determines at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data amount to be transmitted of the N uplink logical channels, specifically including:
And determining the at least one candidate PUCCH resource from the corresponding PUCCH resource group according to the data quantity to be transmitted of each uplink logical channel in the at least one uplink logical channel.
30. The terminal device of claim 28, wherein the processing unit determines at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data amount to be transmitted of the N uplink logical channels, specifically including:
and determining the at least one candidate PUCCH resource from each PUCCH resource group according to the data quantity to be transmitted of the uplink logical channel with the highest priority in the N uplink logical channels.
31. The terminal device of claim 28, wherein the processing unit determines at least one candidate PUCCH resource from each PUCCH resource group in the at least one PUCCH resource group according to the data amount to be transmitted of the N uplink logical channels, specifically including:
and determining the at least one PUCCH resource from each PUCCH resource group according to the sum of the data quantity to be transmitted of all uplink logical channels in the N uplink logical channels.
32. The terminal device according to any of the claims 28 to 31, wherein the processing unit determining the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group comprises:
and determining one PUCCH resource closest to the current time in the candidate PUCCH resources determined from the at least one PUCCH resource group as the target PUCCH resource.
33. The terminal device according to any of the claims 28 to 31, wherein the processing unit determining the target PUCCH resource from the candidate PUCCH resources determined in the at least one PUCCH resource group comprises:
and determining the target PUCCH resource from the candidate PUCCH resources determined in one PUCCH resource group corresponding to the uplink logical channel with the highest priority in the at least one uplink logical channel.
34. The terminal device according to any of the claims 27 to 31, characterized in that on the same uplink bandwidth portion BWP of the terminal device, one PUCCH resource group corresponding to each uplink logical channel in the at least one uplink logical channel comprises the same number of PUCCH resources.
35. The terminal device according to any of the claims 27 to 31, characterized in that the same uplink logical channel of the terminal device comprises the same number of PUCCH resources as a corresponding one PUCCH resource group on different uplink bandwidth parts BWP of the terminal device.
36. The terminal device according to any of the claims 27 to 31, characterized in that the index and/or time domain resource position of any two PUCCH resources comprised in the first PUCCH resource group of the at least one PUCCH resource group is different.
37. The terminal device according to any of claims 27 to 31, wherein a second PUCCH resource group of the at least one PUCCH resource group comprises M PUCCH resources, the M data volume sections corresponding to the second PUCCH resource group are divided by (M-1) thresholds, and M is a positive integer greater than 1.
38. The terminal device of any of claims 27 to 31, wherein the processing unit is further configured to:
and determining the plurality of PUCCH resources according to the currently activated uplink bandwidth part BWP.
39. The terminal device of any of claims 27 to 31, wherein the processing unit is further configured to:
and acquiring first information, wherein the first information is used for indicating the number of the plurality of PUCCH resources and/or the corresponding relation between the PUCCH resources and the data volume interval.
40. The terminal device of claim 39, wherein the processing unit is specifically configured to:
The first information is acquired from the following information: predefined information, system messages, or radio resource control RRC signaling.
41. The terminal device according to any of the claims 27 to 31, wherein the transceiving unit is further adapted to:
receiving second information sent by the network equipment, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
42. A terminal device according to any of claims 27-31, characterized in that the terminal device is applied in a non-terrestrial communication network NTN.
43. A network device, the network device comprising:
a transceiver unit, configured to receive a scheduling request SR sent by a terminal device on a first physical uplink control channel PUCCH resource;
a processing unit configured to determine a data volume section corresponding to the first PUCCH resource from a plurality of PUCCH resources configured for the terminal device for transmitting SRs, the plurality of PUCCH resources corresponding to a plurality of data volume sections, and
according to the data volume interval corresponding to the first PUCCH resource, distributing a Physical Uplink Shared Channel (PUSCH) resource for transmitting data to the terminal equipment; wherein, on the same uplink bandwidth part BWP of the terminal device, the number of PUCCH resources corresponding to different uplink logical channels of the terminal device is the same; or alternatively
The same uplink logical channel of the terminal equipment has the same number of corresponding PUCCH resources on different uplink bandwidth parts BWP of the terminal equipment.
44. The network device of claim 43, wherein the transceiver unit is further configured to:
and sending first information to the terminal equipment, wherein the first information is used for indicating the number of the plurality of PUCCH resources and/or the corresponding relation between the PUCCH resources and the data volume interval.
45. The network device of claim 44, wherein the transceiver unit is specifically configured to:
and sending the first information to the terminal equipment through a system message or Radio Resource Control (RRC) signaling.
46. The network device according to any one of claims 43 to 45, wherein the number of PUCCH resources corresponding to one uplink logical channel of different terminal devices in the same uplink bandwidth part BWP is the same.
47. The network device according to any one of claims 43 to 45, wherein the number of PUCCH resources corresponding to one uplink logical channel of different terminal devices in the same uplink bandwidth part BWP is different.
48. The network device of any one of claims 43 to 45, wherein the transceiver unit is further configured to:
Transmitting second information to the terminal device, wherein the second information comprises at least one of the following information: configuration information of an uplink bandwidth part BWP, configuration information of an uplink logical channel, and configuration information of SR.
49. The network device of claim 48, wherein the plurality of PUCCH resources includes at least one PUCCH resource group, each of the at least one PUCCH resource group includes a PUCCH resource one-to-one correspondence to a plurality of data volume intervals, and the configuration information of the uplink logical channel is used to indicate the PUCCH resource group corresponding to at least one uplink logical channel.
50. The network device of claim 49, wherein indexes and/or time domain resource locations of any two PUCCH resources included in a first PUCCH resource group in the at least one PUCCH resource group are different.
51. The network device of claim 49, wherein a second PUCCH resource group of the at least one PUCCH resource group includes M PUCCH resources, the M data volume intervals corresponding to the second PUCCH resource group are divided by (M-1) thresholds, and M is a positive integer greater than 1.
52. A network device as claimed in any one of claims 43 to 45, wherein the network device is for use in a non-terrestrial communications network NTN.
53. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to perform the method of any of claims 1 to 16.
54. A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 17 to 26.
55. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 16.
56. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 17 to 26.
57. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 16.
58. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 17 to 26.
CN201980094840.XA 2019-08-16 2019-08-16 Method for transmitting data, terminal device and network device Active CN113661750B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/101188 WO2021031014A1 (en) 2019-08-16 2019-08-16 Method for data transmission, terminal device and network device

Publications (2)

Publication Number Publication Date
CN113661750A CN113661750A (en) 2021-11-16
CN113661750B true CN113661750B (en) 2024-01-09

Family

ID=74660405

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980094840.XA Active CN113661750B (en) 2019-08-16 2019-08-16 Method for transmitting data, terminal device and network device

Country Status (2)

Country Link
CN (1) CN113661750B (en)
WO (1) WO2021031014A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113225830B (en) * 2021-06-07 2023-05-26 维沃移动通信有限公司 Data network uplink scheduling method and device and electronic equipment
CN113783677B (en) * 2021-09-13 2022-09-16 珠海格力电器股份有限公司 Data transmission method and device, electronic equipment and storage medium
CN114786271A (en) * 2022-05-30 2022-07-22 中国联合网络通信集团有限公司 Resource management allocation method, device, equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013166670A1 (en) * 2012-05-09 2013-11-14 华为技术有限公司 Method and device for configuring resources of uplink channel
WO2019029538A1 (en) * 2017-08-11 2019-02-14 华为技术有限公司 Scheduling request transmitting method, scheduling request processing method and related device
CN110121847A (en) * 2017-01-04 2019-08-13 Oppo广东移动通信有限公司 Ascending transmission method, terminal and the network equipment

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685895B (en) * 2011-03-11 2015-02-04 华为技术有限公司 Method, system and device for scheduling uplink data
EP2837248A1 (en) * 2012-04-12 2015-02-18 Telefonaktiebolaget LM Ericsson (Publ) A user equipment, a radio base station and respective method therein for managing uplink resources within a coverage area of the radio base station
CN106550457B (en) * 2015-09-18 2019-06-07 中兴通讯股份有限公司 A kind of resource allocation methods and device
CN106922022A (en) * 2015-12-25 2017-07-04 华为技术有限公司 Scheduling up service resource method, apparatus and system
CN109413747B (en) * 2018-11-15 2023-07-11 新华三技术有限公司成都分公司 Transmission resource allocation method and device, and transmission resource request method and device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013166670A1 (en) * 2012-05-09 2013-11-14 华为技术有限公司 Method and device for configuring resources of uplink channel
CN110121847A (en) * 2017-01-04 2019-08-13 Oppo广东移动通信有限公司 Ascending transmission method, terminal and the network equipment
WO2019029538A1 (en) * 2017-08-11 2019-02-14 华为技术有限公司 Scheduling request transmitting method, scheduling request processing method and related device

Also Published As

Publication number Publication date
WO2021031014A1 (en) 2021-02-25
CN113661750A (en) 2021-11-16

Similar Documents

Publication Publication Date Title
CN113632561B (en) Resource allocation method, terminal equipment and network equipment
CN113661750B (en) Method for transmitting data, terminal device and network device
KR102635875B1 (en) Communication methods and devices used in side links
CN108702766B (en) Communication method, network equipment and terminal equipment
JP2021523615A (en) Communication method and device
CN113381848A (en) Method, equipment and system for end-to-end data transmission
CN113067693B (en) Information transmission method, terminal equipment and network equipment
CN115553005A (en) Side feedback resource configuration method, terminal equipment and network equipment
CN112291746B (en) Data transmission method and terminal equipment
CN116711439A (en) Wireless communication method, terminal equipment and network equipment
CN113439475A (en) Network node, UE and method performed therein for handling communication
CN113678531B (en) Method for multiplexing uplink logical channel and terminal equipment
CN107710819B (en) Wireless communication method, network equipment and terminal equipment
CN113711628B (en) Sidestream data transmission method, equipment, storage medium and chip
CN112205051B (en) Method and apparatus for determining transport block size, TBS
CN114846890A (en) Data packet reorganizing method, electronic equipment and storage medium
CN114830588B (en) Method, terminal and network equipment for determining effective time
WO2021163913A9 (en) Data transmission method, terminal device, and network device
CN114586454B (en) Scheduling request SR sending method and related device
CN113557758B (en) Method for reporting side-link capacity, terminal device and network device
CN114285501B (en) Wireless communication method, terminal device, network device and storage medium
CN115314098A (en) Satellite communication method and device
CN116325584A (en) Wireless communication method and terminal equipment
CN116234039A (en) Method for transmitting resource set and terminal equipment
CN114303333B (en) Wireless communication method and device, terminal device and network device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant