WO2019192585A1

WO2019192585A1 - Resource transmission method and apparatus

Info

Publication number: WO2019192585A1
Application number: PCT/CN2019/081422
Authority: WO
Inventors: 李军; 铁晓磊; 花梦; 罗之虎; 于映辉
Original assignee: 华为技术有限公司
Priority date: 2018-04-04
Filing date: 2019-04-04
Publication date: 2019-10-10
Also published as: CN110351006A; CN110351006B

Abstract

Disclosed are a resource transmission method and device. The method comprises: a terminal sends a third message Msg3 to a network device, the Msg3 carrying information for requesting the transmission of a scheduling request (SR) resource; the terminal receives, from the network device, a resource for transmitting a dedicated SR and indication information, the indication information being used for indicating whether to allow a terminal device to send a piggybacked SR; the terminal sends the dedicated SR to the network device over the resource for transmitting the dedicated SR; the terminal determines, according to the indication information, to add the piggybacked SR to an ACK/NACK. Since the network device sends to the network device the indication information of whether to allow the sending of the piggybacked SR, if the network device indicates that the terminal is allowed to send the piggybacked SR, the network device performs blink detection on the SR in the ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device does not perform blind detection on the SR in the ACK/NACK, such that the blind detection of the network device is reduced.

Description

Resource transmission method and device

Technical field

The present application relates to the field of communications and, more particularly, to a resource transmission method and apparatus.

Background technique

Internet of Things (IoT) is a network for Machine-Type Communications (MTC). The future is mainly in smart meter reading, medical inspection and monitoring, logistics detection, industrial inspection and monitoring, automotive networking, and intelligent communities. And applications such as wearables. Due to its variety of application scenarios, from outdoor to indoor, from above ground to underground, there are many special requirements for the design of the Internet of Things.

Coverage enhancement: Many MTC terminals are in poor coverage, such as meter water meters, etc., usually installed in indoors or even basements where wireless network signals are poor. Therefore, coverage enhancement technology is needed to solve communication quality problems under poor coverage.

Support for a large number of low-rate devices: The number of MTC devices is much larger than the number of devices that people communicate with, but the transmitted packets are small and not sensitive to latency.

Very low cost: Many MTC applications require very low end equipment costs to enable large-scale deployment.

Low energy consumption: In most cases, the MTC device is powered by a battery. But at the same time, in many scenarios, MTC requires that it can be used for more than ten years without replacing the battery. This requires the MTC device to work with very low power consumption.

In order to meet these special needs, the 3rd Generation Partnership Project (3GPP) has adopted a new research topic at the GERAN #62 plenary meeting to study the support of extremely low complexity in cellular networks. And low-cost IoT approach, and at the RAN#69 meeting, the project is a narrowband Internet of Things (Narrow Band-IoT, NB-IoT) project, and has completed NB-IoT Rel-13 and Rel-14 The standard work of the version.

Rel-14 does not support the reporting function of the physical layer scheduling request SR (Scheduling Request). For the NB-IoT terminal in the connected state and the uplink synchronization state, when the uplink data arrives and there is no uplink resource, the NB-IoT terminal needs to initiate a random access procedure to request the uplink resource, resulting in a relatively large delay. Therefore, in the Rel-15WID (Work Item Description), it is explicitly proposed that the SR function needs to be supported.

Summary of the invention

The present application provides a resource transmission method and apparatus, which are beneficial for reducing blind detection of SR in a network device.

In a first aspect, the application provides a resource transmission method, including:

Sending a third message Msg3 to the network device, where the Msg3 carries information requesting the transmission scheduling request SR resource;

Receiving, by the network device, a resource and indication information for transmitting a dedicated dedicated SR, where the indication information is used to indicate whether the terminal device is allowed to send the piggybacked SR;

Transmitting the dedicated SR to the network device on a resource for transmitting the dedicated SR;

And determining to carry the piggybacked SR in the ACK/NACK according to the indication information.

Since the network device sends the terminal information indicating whether to allow the piggybacked SR to be sent, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device blindly checks the SR in the ACK/NACK if the network device indicates that the network device does not allow If the terminal sends a piggybacked SR, the network device does not blindly check the SR in the ACK/NACK, thereby reducing the blind detection of the network device.

In a possible design, the Msg3 carries a bit indicating the request to transmit the SR resource.

In a possible design, the Msg3 carries information requesting to transmit a dedicated SR resource and requesting information to allow the piggybacked SR to be sent. For example, the Msg3 can carry two bits, one bit for indicating whether to request transmission of the dedicated SR resource, and another bit for indicating whether to request to send the piggybacked SR.

In a possible design, the sending the third message Msg3 to the network device includes: when the uplink data needs to be sent to the network device, sending the Msg3 to the network device; correspondingly, the method further includes Transmitting the uplink data to the network device.

In one possible design, the method of execution of the method is a chip.

In a second aspect, the application provides a resource transmission method, including:

Sending indication information to the terminal, where the indication information is used to indicate whether the terminal is allowed to send a piggybacked SR;

Receiving an ACK/NACK message sent by the terminal;

When the indication information indicates that the terminal is allowed to send the piggybacked SR, it is detected whether there is an SR in the ACK/NACK message.

In a possible design, the above method further includes:

Receiving a third message Msg3 sent by the terminal, where the Msg3 carries information requesting a transmission scheduling request SR resource;

Allocating resources for transmitting dedicated dedicated SR according to the Msg3;

Transmitting, to the terminal, a resource for transmitting the dedicated SR;

Receiving the dedicated SR sent by the terminal.

In a possible design, before the sending the indication information to the terminal, the method further includes:

Determining whether to allow the terminal to send the piggybacked SR according to the detection capability.

In a possible design, the Msg3 carries information requesting to transmit a dedicated SR resource and requesting information to allow the piggybacked SR to be sent.

Determining whether to allow the terminal to send a piggybacked SR according to the Msg3 and the detection capability.

In a possible design, when the indication information indicates that the terminal is not allowed to send the piggybacked SR, it is not detected whether there is an SR in the ACK/NACK.

In one possible design, the method of execution of the method is a chip.

In a third aspect, the present application provides a resource transmission apparatus having a function of implementing the behavior in the example of the method of the first aspect described above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or the software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the resource transmission device includes a sending unit, a receiving unit, and a determining unit, and the units may perform corresponding functions in the foregoing method examples. For details, refer to the detailed description in the method example, which is not described herein. .

In one possible design, the resource transmission device is a chip.

In a fourth aspect, the present application provides a resource transmission device having a function of implementing the behavior in the method example of the second aspect above. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or the software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the resource transmission device includes a transmitting unit, a receiving unit, a determining unit, and a detecting unit, and the units may perform corresponding functions in the foregoing method examples. For details, refer to the detailed description in the method example, where Do not repeat them.

In one possible design, the resource transmission device is a chip.

In a fifth aspect, the application provides a resource transmission apparatus, including:

Memory for storing programs;

A processor for executing the program stored by the memory, the processor for performing any one of the possible implementations described in various aspects or aspects when the program is executed.

Yet another aspect of the present application is directed to a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another aspect of the present application provides a computer program that, when run on a computer, causes the computer to perform the methods described in the various aspects above.

DRAWINGS

Figure 1 is a wireless communication system 100 applied to an embodiment of the present application;

2 is a schematic flowchart of a resource transmission method provided by an embodiment of the present application;

3 is a schematic flowchart of a resource transmission method provided by another embodiment of the present application;

4 is a schematic block diagram of a resource transmission apparatus according to an embodiment of the present application;

FIG. 5 is a schematic block diagram of a resource transmission apparatus according to still another embodiment of the present application; FIG.

FIG. 6a is a schematic block diagram of a resource transmission apparatus according to still another embodiment of the present application;

FIG. 6b is a schematic block diagram of a resource transmission apparatus according to still another embodiment of the present application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

Before introducing the embodiment of the present application, the SR in this application is introduced:

The SR (Scheduling Request) is used to connect the terminal. When the terminal has uplink data to be sent and there is no uplink resource, the terminal sends an SR to the network device to request uplink resources to send uplink data. SR can be divided into Dedicated SR and Piggybacked SR:

1. Dedicated SR

The network device allocates a dedicated SR resource to the terminal. When the terminal has uplink data to be sent but no uplink resource, the terminal may send the SR on the allocated dedicated resource. Therefore, the SR sent on the dedicated resource is called a dedicated SR. After receiving the dedicated SR, the network device sends an uplink grant UL grant to the terminal to allocate resources, and the terminal transmits uplink data on the resource.

2, piggybacked (Piggybacked) SR

The network device allocates a downlink grant DL Grant to the terminal. When the terminal has uplink data to be sent but no uplink resource, the terminal may send the SR on the acknowledge/non-acknowledge (ACK/NACK) resource, and therefore, send the ACK/NACK resource. The SR is called Piggybacked SR. After receiving the Piggybacked SR, the network device sends an uplink grant UL grant to the terminal to allocate resources, and the terminal transmits uplink data on the resource.

In the prior art, whether the terminal sends the SR on the ACK/NACK resource depends on whether the terminal needs to send uplink data. If the uplink data needs to be sent, the terminal sends the SR on the ACK/NACK resource, if the uplink data does not need to be sent. The terminal does not send the SR on the ACK/NACK resource. Therefore, the terminal in the connected state is allowed to send the piggybacked SR. For the network device, since the network device only knows that the terminal may send the SR on the ACK/NACK, but cannot know exactly whether the terminal sends the SR on the ACK/NACK, the network device needs to blindly check on the ACK/NACK resource. There is an SR, and the network device also needs to blindly check whether the UE sends an ACK or a NACK.

FIG. 1 is a wireless communication system 100 to which an embodiment of the present application is applied. The wireless communication system 100 can include a network device 110. Network device 110 may be a device that communicates with a terminal device. Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

FIG. 1 exemplarily shows one network device and two terminals. Alternatively, the wireless communication system 100 may include multiple network devices and may include other numbers of terminals within the coverage of each network device. This example does not limit this.

Optionally, the wireless communication system 100 may further include other network entities, such as a network controller, a mobility management entity, and the like.

It should be understood that the technical solution of the present application can be applied to various communication systems, for example, a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, and a wideband code division. Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) System, Universal Mobile Telecommunication System (UMTS), New Radio Access Technology (NR), 5G, etc.

It should also be understood that, in the embodiment of the present application, the terminal may include, but is not limited to, a terminal device applied in the Internet of Things, for example, may be a terminal device in the NB-IoT (which may be referred to as an “NB-IoT terminal”). : smart meter reading equipment, logistics tracking equipment, environmental monitoring equipment, etc.; the terminal may also include but is not limited to a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile telephone (Mobile Telephone), a user equipment (User Equipment, UE), mobile phone (handset), and portable equipment, etc., the terminal device can communicate with one or more core networks via a Radio Access Network (RAN), for example, the terminal device can be Mobile phones (or "cellular" phones), computers with wireless communication capabilities, etc., can also be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices.

In this embodiment, the network device may be an access network device, for example, may be a network device, a Transmit and Receive Point (TRP) or an access point, and the network device may be a network device in GSM or CDMA ( Base Transceiver Station (BTS), which may also be a network device (NodeB) in WCDMA, or an evolved Node B (eNB or e-NodeB) in LTE, or an NR or 5G network device. (gNB), the embodiment of the present application does not specifically limit this.

The method for requesting uplink transmission resources of the terminal based on the SR mechanism is described in detail below with reference to FIG. 2 and FIG. 3.

FIG. 2 is a schematic flowchart of a resource transmission method provided by an embodiment of the present application. The method shown in Figure 2 includes:

S201. The terminal sends a third message Msg3 to the network device, where the Msg3 carries information requesting to transmit the SR resource.

When the terminal needs to send the uplink data to the network device, the terminal sends the Msg3 to the network device. In an embodiment of the present application, the Msg3 carries information for requesting to transmit the SR resource. Specifically, the Msg3 may carry one for the Msg3. Indicates a bit that requests to transmit an SR resource. For example, when the bit is "1", it indicates that the terminal requests the SR resource from the network device. When the bit is "0", it indicates that the terminal does not request the SR resource or the terminal does not support. SR mechanism.

In another embodiment of the present application, the Msg3 carries information requesting to transmit a dedicated SR resource and information requesting to send a piggybacked SR. Specifically, the Msg3 may carry two bits, and one bit is used to indicate whether to request transmission. A dedicated SR resource, another bit is used to indicate whether to request to send a piggybacked SR. For example, when the value of two bits is "00", it means that the resource of the dedicated SR is not requested to be transmitted and the Piggybacked SR is not requested to be sent. "01" indicates that only the request is sent. The resource of the dedicated SR is transmitted, "10" means that only the Piggybacked SR is allowed to be requested, "11" means that the resource for requesting the transmission of the dedicated SR and the request to allow the Piggybacked SR to be transmitted.

In the present application, the uplink data may be status report information or alarm information of the terminal, and the third message Msg3 is a message in the connection state establishment process, and generally includes an RRCConnectionRequest, an RRCConnectionResumeRequest, an RRCConnectionReestablishmentRequest, etc., wherein the RRCConnectionRequest includes ue-Identity, The establishmentCause or the like, the RRCConnectionResumeRequest includes a resumeID, a resumeCause, etc., and the above-mentioned bits for indicating that the SR resource is requested to be transmitted may be included in the RRCConnectionRequest, the RRCConnectionResumeRequest, or the RRCConnectionReestablishmentRequest.

S202. The network device allocates, according to the Msg3, a resource for transmitting the dedicated SR.

After receiving the Msg3, the network device determines whether the terminal requests to transmit the SR resource, and determines whether the resource for transmitting the dedicated SR can be allocated to the terminal, and if yes, the network device allocates the resource for transmitting the dedicated SR. The terminal is configured to enable the terminal to perform the transmission of the dedicated SR; if not, for example, if the resource is insufficient, the network device does not allocate the resource for transmitting the dedicated SR to the terminal, and the terminal cannot perform the transmission of the dedicated SR.

S203. The network device determines whether the terminal is allowed to send the piggybacked SR.

In addition to determining whether to allocate resources for transmitting the dedicated SR, the network device determines whether the terminal is allowed to send the piggybacked SR.

In an embodiment of the present application, the Msg3 only carries information requesting to transmit a dedicated SR resource, and the network device determines, according to the detection capability, whether the terminal is allowed to send a piggybacked SR, where the detection capability may be that the network device is most blindly detected. The number of terminals, that is, the network device needs to blindly check the number of ACK/NACKs sent by the terminal with or without SR, or the performance of the network device blindly checking ACK/NACK. The performance may be missed detection or misdetection probability or other indicators. .

In another embodiment of the application, the Msg3 carries information requesting to transmit the dedicated SR resource and requesting to send information of the piggybacked SR, and the network device determines, according to the Msg3 and the detection capability, whether the terminal is allowed to send the piggybacked SR, only in the When the Msg3 carries the information requesting permission to send the piggybacked SR and the detection capability is sufficient, the network device determines that the terminal is allowed to send the piggybacked SR. Otherwise, the network device determines that the terminal is not allowed to send the piggybacked SR. For example, the Msg3 carries the When the information of the piggybacked SR is sent or the detection capability of the network device is insufficient, the network device determines that the terminal is not allowed to send the piggybacked SR.

S204. The network device sends, to the terminal, resources and indication information for transmitting the dedicated SR.

The indication information is used to indicate whether the terminal is allowed to send a piggybacked SR. Specifically, the indication information may be one-bit information. For example, when the bit is “1”, the indication information indicates that the terminal is allowed to send a piggybacked SR. When the bit is “0”, the indication information indicates that the terminal is not allowed to send. Piggybacked SR.

S205. The terminal sends the dedicated SR to the network device on the resource used for transmitting the dedicated SR.

S206. The network device sends a downlink authorization DL grant to the terminal.

The DL Grant indicates resources of the NPDSCH resource and the ACK/NACK.

S207. The network device sends downlink data by using a Narrowband Physical Downlink Shared Channel (NPDSCH).

Accordingly, the terminal receives downlink data on the NPDSCH resource.

S208. The terminal sends an ACK/NACK to the network device.

The terminal transmits an ACK/NACK on the ACK/NACK resource indicated by the DL Grant.

Specifically, the terminal determines, according to the indication information, whether the piggybacked SR is carried in the sent ACK/NACK, and when the indication information indicates that the terminal allows the piggybacked SR to be sent, the terminal may carry the piggybacked SR in the ACK/NACK sent to the network device. When the indication information indicates that the terminal is not allowed to send the piggybacked SR, the terminal does not carry the piggybacked SR in the ACK/NACK sent to the network device.

It should be noted that when the network device sends the indication information to the terminal, if the indication information indicates that the terminal is allowed to send the piggybacked SR, the network device blindly checks the SR in the received ACK/NACK, and the so-called blind detection refers to the network device. The ACK/NACK resource is detected to carry the SR, and the terminal sends the ACK or the NACK. Therefore, the blind detection SR generally includes four states: the ACK carries the SR, the NACK carries the SR, and the ACK does not carry the SR and the NACK. Carrying the SR; if the indication information indicates that the terminal is not allowed to send the piggybacked SR, the network device does not need to blindly check the SR in the received ACK/NACK.

S209. The network device sends a downlink grant UL Grant to the terminal.

The UL Grant indicates resources of a Narrow-band Physical Uplink Shared Channel (NPUSCH).

S210. The terminal sends uplink data to the network device.

The uplink data is sent to the network device through the NPUSCH.

It should be noted that the order of execution between steps S201-S210 in this embodiment is not limited.

In this embodiment, the network device sends the terminal information to the terminal whether to allow the piggybacked SR to be sent. Therefore, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device blindly checks the SR in the ACK/NACK. If the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device does not blindly check the SR in the ACK/NACK, and reduces the blind detection of the network device.

FIG. 3 is a schematic flowchart of a resource transmission method provided by an embodiment of the present application. In this embodiment, the terminal and the network device pre-arrange that if the terminal receives the resource allocated by the network device for transmitting the dedicated SR, the terminal only sends the dedicated SR, and does not send the piggybacked SR, if the terminal does not receive the network device. The allocated resource for transmitting the dedicated SR, the terminal does not send the dedicated SR, but allows the piggybacked SR to be sent.

Specifically, the method shown in FIG. 3 includes:

S301. The terminal sends a third message Msg3 to the network device, where the Msg3 carries information requesting to transmit the SR resource.

Specifically, when the terminal needs to send the uplink data to the network device, the terminal sends a third message Msg3 to the network device, where the Msg3 can carry a bit indicating the request to transmit the SR resource.

S302. The network device allocates, according to the third message Msg3, a resource for transmitting the dedicated SR.

In this embodiment, the network device does not send an indication message to the terminal to inform whether the terminal is allowed to send a piggybacked SR, and the network device may default to the terminal if the resource for transmitting the dedicated SR is allocated to the terminal, the terminal does not send piggybacked SR, if the terminal is not allocated a resource for transmitting the dedicated SR, the terminal is allowed to send a piggybacked SR.

S303. The network device sends a resource for transmitting the dedicated SR to the terminal.

S304. The terminal sends the dedicated SR to the network device on the resource used for transmitting the dedicated SR.

S305. The network device sends a downlink authorization DL grant to the terminal.

The DL Grant indicates resources of the NPDSCH resource and the ACK/NACK.

S306. The network device sends downlink data by using the NPDSCH.

Accordingly, the terminal receives downlink data on the NPDSCH resource.

S307. The terminal sends an ACK/NACK.

The terminal transmits an ACK/NACK on the ACK/NACK resource.

Since the network device sends a resource for transmitting the dedicated SR to the terminal in step S303, the terminal sends an ACK/NACK that does not carry the piggybacked SR, that is, the terminal does not send the piggybacked SR, and the network device does not receive. Blind SR in ACK/NACK. Conversely, if the network device does not send a resource for transmitting the dedicated SR to the terminal, the network device blindly checks the SR in the received ACK/NACK.

S308. The network device sends a downlink authorized UL Grant to the terminal.

The UL Grant indicates the resources of the NPUSCH.

S309. The terminal sends uplink data to the network device.

The uplink data is sent to the network device through the NPUSCH.

It should be noted that the same steps are described in FIG. 3 and FIG. 2. For the same steps, which are not described in this embodiment, reference may be made to the related description in the embodiment of FIG. 2; in this embodiment, between steps S301-S309 The order of execution is not limited.

In this embodiment, the network device does not need to send an indication message to the terminal to inform whether the terminal is allowed to send a piggybacked SR, and the network device does not send the piggybacked SR by default if the terminal allocates resources for transmitting the dedicated SR. At this time, the network device does not need to blindly check the SR in the received ACK/NACK. If the terminal is not allocated resources for transmitting the dedicated SR, the terminal is allowed to send the piggybacked SR, and the network device needs to receive the ACK/ The SR is blindly checked in the NACK, which reduces the blind detection of the network device, and reduces the instruction information that the network device sends to the terminal whether to allow the terminal to send the piggybacked SR.

In the embodiment corresponding to FIG. 2 and FIG. 3 respectively, when the terminal needs to send uplink data to the network device, the terminal triggers sending a third message Msg3 to the network device to request to transmit the SR resource, where Msg3 is a message during the connection state establishment process. In the embodiment of the present application, the terminal may also request the network device to transmit the SR resource in the capability report information after the connection state is established, for example, in the terminal-capability-NB information, therefore, the present application provides FIG. 2 The third message Msg3 in the embodiment described in FIG. 3 is replaced with an embodiment of capability reporting information. The following describes an embodiment of the capability reporting information replacing the third message Msg3:

Referring to the embodiment in FIG. 2, in an embodiment of the present application, the capability report information sent by the terminal to the network device carries information for indicating that the SR resource is requested to be transmitted, and the network device allocates the information according to the capability report for transmitting the dedicated SR. And determining whether the terminal is allowed to send the piggybacked SR, and then the network device sends the terminal with the resource for transmitting the dedicated SR and the indication information indicating whether the terminal is allowed to send the piggybacked SR. For other steps, refer to the related description in FIG. 2 .

Referring to the embodiment in FIG. 3, in an embodiment of the present application, the capability report information sent by the terminal to the network device carries information for requesting transmission of the SR resource, and the network device allocates the information for transmitting the dedicated SR according to the capability report information. The resource is then sent by the network device to the terminal for transmitting the dedicated SR. For other steps, reference may be made to the related description in FIG.

The resource transmission device 400 provided by the embodiment of the present application is described below with reference to FIG. 4, and the resource transmission device 400 includes:

The sending module 410 is configured to send a third message Msg3 to the network device.

The Msg3 carries information requesting a transmission scheduling request SR resource;

In an embodiment of the present application, the Msg3 carries a bit indicating the request to transmit the SR resource.

In another embodiment of the present application, the Msg3 carries information requesting to transmit the dedicated SR resource and requesting information to allow the piggybacked SR to be sent.

Further, the sending module 410 is configured to:

When the uplink data needs to be sent to the network device, the Msg3 is sent to the network device; and the uplink data is sent to the network device.

The receiving module 420 is configured to receive, by the network device, a resource for transmitting a dedicated dedicated SR, and indication information, where the indication information is used to indicate whether the terminal device is allowed to send the piggybacked SR;

The sending module 410 is further configured to send the dedicated SR to the network device on the resource used for transmitting the dedicated SR;

The determining module 430 is configured to determine, according to the indication information, that the piggybacked SR is carried in the ACK/NACK.

The resource transmission device 500 provided by the embodiment of the present application is described below with reference to FIG. 5, and the resource transmission device 500 includes:

The sending module 510 is configured to send, to the terminal, indication information, where the indication information is used to indicate whether the terminal is allowed to send a piggybacked SR;

The receiving module 520 is configured to receive an ACK/NACK message sent by the terminal;

The detecting module 530 is configured to detect, in the ACK/NACK message, whether there is an SR when the indication information indicates that the terminal is allowed to send the piggybacked SR.

Further, when the indication information indicates that the terminal is not allowed to send the piggybacked SR, the detecting module 530 does not detect whether there is an SR in the ACK/NACK.

Further, the resource transmission device 500 further includes:

The receiving module 520 is further configured to receive Msg3 sent by the terminal, where the Msg3 carries information requesting a transmission scheduling request SR resource;

An allocating module 540, configured to allocate, according to the Msg3, a resource for transmitting a dedicated dedicated SR;

The sending module 510 is further configured to send, to the terminal, a resource for transmitting the dedicated SR;

The receiving module 520 is further configured to receive the dedicated SR sent by the terminal.

In one implementation of the present application, the Msg3 carries a bit indicating the request to transmit the SR resource.

Correspondingly, the resource transmission device further includes a determining module 550, configured to determine, according to the detection capability, whether the terminal is allowed to send the piggybacked SR.

In another implementation of the present application, the Msg3 carries information requesting transmission of the dedicated SR resource and requesting permission to send information of the piggybacked SR.

Correspondingly, the resource transmission device further includes a determining module 550, configured to determine, according to the Msg3 and the detection capability, whether the terminal is allowed to send the piggybacked SR.

In the above embodiment, the network device sends the terminal information to the terminal whether to allow the piggybacked SR to be sent. Therefore, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device blindly checks the SR in the ACK/NACK. If the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device does not blindly check the SR in the ACK/NACK, and reduces the blind detection of the network device.

Referring to FIG. 6a, a resource transmission device 600 is provided in the embodiment of the present application. The resource transmission device 600 includes:

The processing device 610 is configured to process data received by the transceiver 620.

The transceiver 620 is configured to receive or send data.

Optionally, the communication device further includes:

The antenna 630, the transceiver 620 receives or transmits data through the antenna 630.

When the processing device 610 is implemented by software, as shown in FIG. 6a, the processing device 610 includes:

a memory 612, configured to store a program;

The processor 611 is configured to execute the program stored in the memory. When the program is executed, the implementation in the foregoing method embodiment is performed. For details, refer to the description in the foregoing method embodiment, and the processing is not performed here. The execution process of the device 611 will be described in detail.

The memory 612 may be a physically separate unit or may be integrated with the processor 611, as shown in FIG. 6b.

The resource transmission device 600 in the embodiment of the present application may be a wireless communication device such as an access point, a station, a base station, or a user terminal.

The unit and method processes of the examples described in the embodiments of the present application can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. The skilled person can use different methods for each particular application to implement the described functionality.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division, and the actual implementation may have another division manner. For example, multiple units or components may be combined or integrated into another system, or some steps may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection of the various units to each other may be through some interfaces, which may be in electrical, mechanical or other form.

The units described as separate components may or may not be physically separate, and may be located in one place or on multiple network elements.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Claims

A resource transmission method, comprising:

Sending a third message Msg3 to the network device, where the Msg3 carries information requesting the transmission scheduling request SR resource;

Receiving, by the network device, a resource and indication information for transmitting a dedicated dedicated SR, where the indication information is used to indicate whether the terminal device is allowed to send the piggybacked SR;

Transmitting the dedicated SR to the network device on a resource for transmitting the dedicated SR;

And determining to carry the piggybacked SR in the ACK/NACK according to the indication information.
The method of claim 1 wherein said Msg3 carries a bit indicating a request to transmit an SR resource.
The method according to claim 1, wherein said Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to transmit a piggybacked SR.
The method according to any one of claims 1-3, wherein the sending the third message Msg3 to the network device comprises:

When the uplink data needs to be sent to the network device, sending the Msg3 to the network device;

The method further includes:

Sending the uplink data to the network device.
A resource transmission method, comprising:

Sending indication information to the terminal, where the indication information is used to indicate whether the terminal is allowed to send a piggybacked SR;

Receiving an ACK/NACK message sent by the terminal;

When the indication information indicates that the terminal is allowed to send the piggybacked SR, it is detected whether there is an SR in the ACK/NACK message.
The method of claim 5, further comprising:

Receiving a third message Msg3 sent by the terminal, where the Msg3 carries information requesting a transmission scheduling request SR resource;

Allocating resources for transmitting dedicated dedicated SR according to the Msg3;

Transmitting, to the terminal, a resource for transmitting the dedicated SR;

Receiving the dedicated SR sent by the terminal.
The method according to claim 6, wherein said Msg3 carries a bit for indicating a request to transmit an SR resource.
The method according to claim 7, wherein before the sending the indication information to the terminal, the method further includes:

Determining whether to allow the terminal to send the piggybacked SR according to the detection capability.
The method according to claim 6, wherein the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR.
The method according to claim 9, wherein before the sending the indication information to the terminal, the method further includes:

Determining whether to allow the terminal to send a piggybacked SR according to the Msg3 and the detection capability.
The method according to any one of claims 5 to 10, wherein, when the indication information indicates that the terminal is not allowed to send the piggybacked SR, whether the SR is detected in the ACK/NACK is not detected.
A resource transmission device, comprising:

a sending module, configured to send, to the network device, a third message Msg3, where the Msg3 carries information requesting a transmission scheduling request SR resource;

a receiving module, configured to receive, by the network device, a resource and indication information for transmitting a dedicated dedicated SR, where the indication information is used to indicate whether the terminal device is allowed to send a piggybacked SR;

The sending module is further configured to send the dedicated SR to the network device on a resource for transmitting the dedicated SR;

And a determining module, configured to determine, according to the indication information, that the piggybacked SR is carried in the ACK/NACK.
The apparatus according to claim 12, wherein said Msg3 carries a bit for indicating a request to transmit an SR resource.
The apparatus according to claim 12, wherein said Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to transmit a piggybacked SR.
The device according to any one of claims 12-14, wherein the transmitting module is configured to:

Transmitting the Msg3 to the network device when the uplink data needs to be sent to the network device;

Sending the uplink data to the network device.
A resource transmission device, comprising:

a sending module, configured to send, to the terminal, indication information, where the indication information is used to indicate whether the terminal is allowed to send a piggybacked SR;

a receiving module, configured to receive an ACK/NACK message sent by the terminal;

And a detecting module, configured to detect, in the ACK/NACK message, whether there is an SR when the indication information indicates that the terminal is allowed to send the piggybacked SR.
The device of claim 16 further comprising:

The receiving unit is further configured to receive a third message Msg3 sent by the terminal, where the Msg3 carries information requesting a transmission scheduling request SR resource;

An allocation module, configured to allocate, according to the Msg3, a resource for transmitting a dedicated dedicated SR;

The sending module is further configured to send, to the terminal, a resource for transmitting the dedicated SR;

The receiving module is further configured to receive the dedicated SR sent by the terminal.
The apparatus according to claim 17, wherein said Msg3 carries a bit for indicating a request to transmit an SR resource.
The device of claim 18, further comprising:

And a determining module, configured to determine, according to the detecting capability, whether the terminal is allowed to send the piggybacked SR.
The apparatus according to claim 17, wherein said Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to transmit a piggybacked SR.
The device of claim 20, further comprising:

And a determining module, configured to determine, according to the Msg3 and the detection capability, whether the terminal is allowed to send a piggybacked SR.
The apparatus according to any one of claims 16 to 21, wherein, when the indication information indicates that the terminal is not allowed to send the piggybacked SR, the detecting module is further configured to not in the ACK/NACK. Check if there is an SR.
A resource transmission device, comprising:

Memory for storing programs;

a processor for executing the program stored by the memory, the processor for performing the steps of any of claims 1-4 or 5-11 when the program is executed.
A computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1-4 or 5-11.