CN110351006B - Resource transmission method and device - Google Patents

Resource transmission method and device Download PDF

Info

Publication number
CN110351006B
CN110351006B CN201810302136.6A CN201810302136A CN110351006B CN 110351006 B CN110351006 B CN 110351006B CN 201810302136 A CN201810302136 A CN 201810302136A CN 110351006 B CN110351006 B CN 110351006B
Authority
CN
China
Prior art keywords
terminal
piggybacked
send
resource
dedicated
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
CN201810302136.6A
Other languages
Chinese (zh)
Other versions
CN110351006A (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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201810302136.6A priority Critical patent/CN110351006B/en
Priority to PCT/CN2019/081422 priority patent/WO2019192585A1/en
Publication of CN110351006A publication Critical patent/CN110351006A/en
Application granted granted Critical
Publication of CN110351006B publication Critical patent/CN110351006B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0036Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
    • H04L1/0038Blind format detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055Physical resource allocation for ACK/NACK

Landscapes

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

Abstract

The application discloses a resource transmission method and equipment. The method comprises the following steps: the terminal sends a third message Msg3 to the network equipment, wherein the Msg3 carries the information of requesting to transmit Scheduling Request (SR) resources; the terminal receives the resource and indication information which are sent by the network equipment and used for transmitting the special dedicated SR, wherein the indication information is used for indicating whether the terminal equipment is allowed to send the piggybacked SR or not; the terminal sends the dedicated SR to the network equipment on the resource for transmitting the dedicated SR; and the terminal determines that the piggybacked SR is carried in the ACK/NACK according to the indication information. Because the network device sends the indication information whether to allow the piggybacked SR to be sent to the terminal, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device may blindly detect the SR in ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device may not blindly detect the SR in ACK/NACK, thereby reducing blind detection of the network device.

Description

Resource transmission method and device
Technical Field
The present application relates to the field of communications, and in particular, to a resource transmission method and apparatus.
Background
The Internet of things (IoT) is a network facing Machine-to-Machine communication (MTC), and is mainly used in applications such as intelligent meter reading, medical detection and monitoring, logistics detection, industrial detection and monitoring, automobile networking, intelligent communities, and wearable devices in the future. Due to the fact that application scenes of the system are various and comprise from outdoor to indoor and from the ground to the underground, a plurality of special requirements are put on the design of the Internet of things.
Coverage enhancement: many MTC terminals are in an environment with poor coverage, such as an electric meter, a water meter, etc., and are usually installed indoors or in basements, etc., where wireless network signals are poor, and therefore a coverage enhancement technology is needed to solve the problem of communication quality under poor coverage.
A large number of low rate devices are supported: the number of MTC devices is much larger than the number of devices communicating between people, but the data packets transmitted are small and not sensitive to latency.
Very low cost: many MTC applications require very low terminal equipment costs to enable large-scale deployment.
Low energy consumption: in most cases, MTC devices are powered by batteries. At the same time, however, in many scenarios MTC is required to be able to be used for more than a decade without requiring battery replacement. This requires that MTC devices be able to operate with very low power consumption.
To meet these special requirements, the 3rd Generation Partnership Project (3 GPP), the 3rd 3GPP, has passed a new research topic at GERAN #62 times the conference to investigate methods for supporting very low complexity and low cost internet of things in cellular networks, and has established the narrowband internet of things (NB-IoT) topic at RAN #69 times the conference, and has completed both NB-IoT Rel-13 and Rel-14 versions of the standard work.
The 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 uplink data arrives and there is no uplink resource, the NB-IoT terminal needs to initiate a random access process to request the uplink resource, resulting in a relatively large delay. Therefore, the need to support SR function is clearly suggested in Rel-15WID (word Item description).
Disclosure of Invention
The application provides a resource transmission method and device, which are beneficial to reducing the blind detection of the SR in network equipment.
In a first aspect, the present application provides a resource transmission method, including:
sending a third message Msg3 to a network device, wherein the Msg3 carries information requesting transmission of Scheduling Request (SR) resources;
receiving resources and indication information which are sent by the network equipment and used for transmitting the special dedicated SR, wherein the indication information is used for indicating whether the terminal equipment is allowed to send the piggybacked SR or not;
transmitting the dedicated SR to the network equipment on a resource for transmitting the dedicated SR;
and determining that the piggybacked SR is carried in the ACK/NACK according to the indication information.
Because the network device sends the indication information whether to allow the piggybacked SR to be sent to the terminal, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device may blindly detect the SR in ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device may not blindly detect the SR in ACK/NACK, thereby reducing blind detection of the network device.
In one possible design, the Msg3 carries a bit indicating that SR resources are requested for transmission.
In one possible design, the Msg3 carries information requesting to transmit a dedicated SR resource and information requesting to allow a piggybacked SR to be sent. For example, the Msg3 may carry two bits, one bit is used to indicate whether to request transmission of the dedicated SR resource, and the other bit is used to indicate whether to request transmission of the piggybacked SR resource.
In one possible design, the sending the third message Msg3 to the network device includes: when uplink data need to be sent to the network equipment, the Msg3 is sent to the network equipment; correspondingly, the method further comprises the following steps: and sending the uplink data to the network equipment.
In one possible design, the execution subject of the method is a chip.
In a second aspect, the present application provides a resource transmission method, including:
sending indication information to a terminal, wherein the indication information is used for indicating whether the terminal is allowed to send the piggybacked SR or not;
receiving an ACK/NACK message sent by the terminal;
and when the indication information indicates that the terminal is allowed to send the piggybacked SR, detecting whether the SR exists in the ACK/NACK message.
Because the network device sends the indication information whether to allow the piggybacked SR to be sent to the terminal, if the network device indicates that the terminal allows the piggybacked SR to be sent, the network device may blindly detect the SR in ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device may not blindly detect the SR in ACK/NACK, thereby reducing blind detection of the network device.
In one possible design, the method further includes:
receiving a third message Msg3 sent by the terminal, wherein the Msg3 carries information requesting transmission of Scheduling Request (SR) resources;
allocating resources for transmitting dedicated SR according to the Msg 3;
sending a resource for transmitting the dedicated SR to the terminal;
and receiving the dedicated SR sent by the terminal.
In one possible design, the Msg3 carries a bit indicating that SR resources are requested for transmission.
In one possible design, before sending the indication information to the terminal, the method further includes:
and determining whether the terminal is allowed to send the piggybacked SR or not according to the detection capability.
In one possible design, the Msg3 carries information requesting to transmit a dedicated SR resource and information requesting to allow a piggybacked SR to be sent.
In one possible design, before sending the indication information to the terminal, the method further includes:
and determining whether the terminal is allowed to send piggybacked SR or not according to the Msg3 and the detection capability.
In one possible design, when the indication information indicates that the terminal is not allowed to send the piggybacked SR, whether there is an SR or not is not detected in the ACK/NACK.
In one possible design, the execution subject of the method is a chip.
In a third aspect, the present application provides a resource transfer apparatus having functionality to implement the behavior of the method example of the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or the software includes one or more modules corresponding to the above-described functions.
In a possible design, the structure of the resource transmission apparatus includes a sending unit, a receiving unit, and a determining unit, which may execute corresponding functions in the foregoing method example, for specific reference, detailed description in the method example is omitted here for further details.
In one possible design, the resource transfer device is a chip.
In a fourth aspect, the present application provides a resource transfer apparatus having functionality to implement the behavior of the method example of the second aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or the software includes one or more modules corresponding to the above-described functions.
In a possible design, the structure of the resource transmission apparatus includes a sending unit, a receiving unit, a determining unit, and a detecting unit, which may perform corresponding functions in the foregoing method example, for specific reference, detailed description in the method example is given, and details are not repeated here.
In one possible design, the resource transfer device is a chip.
In a fifth aspect, the present application provides a resource transmission apparatus, including:
a memory for storing a program;
a processor for executing the program stored in the memory, the processor being configured to perform the aspects or any of the possible implementations of the aspects when the program is executed.
Yet another aspect of the present application provides a computer-readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of the above-described aspects.
Yet another aspect of the present application provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above-described aspects.
A further aspect of the application provides a computer program which, when run on a computer, causes the computer to perform the method of the above aspects.
Drawings
Fig. 1 is a wireless communication system 100 to which an embodiment of the present application is applied;
fig. 2 is a schematic flow chart of a resource transmission method provided in an embodiment of the present application;
fig. 3 is a schematic flow chart of a resource transmission method according to another embodiment of the present application;
fig. 4 is a schematic block diagram of a resource transmission apparatus provided in an embodiment of the present application;
fig. 5 is a schematic block diagram of a resource transmission apparatus according to another embodiment of the present application;
fig. 6a is a schematic block diagram of a resource transmission apparatus according to another embodiment of the present application;
fig. 6b is a schematic block diagram of a resource transmission apparatus according to another embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
Before the embodiments of the present application are introduced, SR in the present application is introduced:
SR (scheduling request) is used for a connected terminal, and when the terminal has uplink data to send and has no uplink resource, the terminal sends an SR to the network device to request the uplink resource to send the uplink data. The SR can be divided into a Dedicated SR and a Piggybacked SR:
1. dedicated (Dedicated) SR
The network device allocates a dedicated SR resource to the terminal, and when the terminal has uplink data to send and does not have the uplink resource, the terminal can send the SR on the allocated dedicated resource, so 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, allocates resources, and the terminal transmits uplink data on the resources.
2. Piggybacked (Piggybacked) SR
The network device allocates a downlink Grant (DL Grant) to the terminal, and when the terminal has uplink data to send and does not have uplink resources, the terminal can send an SR on an acknowledgement/negative acknowledgement (ACK/NACK) resource, so the SR sent on the ACK/NACK resource is called a Piggybacked SR. After receiving the Piggybacked SR, the network device sends an uplink grant UL grant to the terminal, allocates resources, and the terminal transmits uplink data on the resources.
In the prior art, whether the terminal sends the SR on the ACK/NACK resource depends on whether the terminal has uplink data to send, if the terminal needs to send the uplink data, the terminal sends the SR on the ACK/NACK resource, and if the terminal does not need to send the uplink data, the terminal does not send the SR on the ACK/NACK resource, so that the terminals in a connected state are all allowed to send piggybacked SRs. 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 sent the SR on the ACK/NACK, the network device needs to blindly detect whether there is the SR on the ACK/NACK resource, and the network device also needs to blindly detect whether the UE sent the ACK or NACK.
Fig. 1 is a wireless communication system 100 to which an embodiment of the present application is applied. The wireless communication system 100 may 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 that coverage area.
Fig. 1 exemplarily shows one network device and two terminals, and optionally, the wireless communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that the technical solution of the present application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (LTE-a) System, a Universal Mobile Telecommunications System (UMTS), a New Radio Access Technology (NR), 5G, and the like.
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, a terminal device accessing NB-IoT (may be referred to as "NB-IoT terminal"): intelligent meter reading equipment, logistics tracking equipment, environment monitoring equipment and the like; the Terminal may further include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile Telephone), a User Equipment (UE), a handset (handset), a portable device (portable Equipment), and the like, where the Terminal may communicate with one or more core networks via a Radio Access Network (RAN), for example, the Terminal may be a Mobile phone (or referred to as a "cellular" phone), a computer with a wireless communication function, and the Terminal may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.
In this embodiment of the present application, the network device may be an access network device, for example, a network device, a Transmit and Receive Point (TRP) or an access Point, where the network device may be a network device in GSM or CDMA (BTS), a network device in WCDMA (NodeB), an evolved Node B (eNB or e-NodeB) in LTE, or a network device in NR or 5G (gbb), and this is not particularly limited in this embodiment of the present application.
The method for requesting uplink transmission resources based on the SR mechanism by the terminal is described in detail below with reference to fig. 2 and 3.
Fig. 2 is a schematic flow chart of a resource transmission method provided in an embodiment of the present application. The method shown in fig. 2 comprises:
s201, the terminal sends a third message Msg3 to the network device, wherein the Msg3 carries the information for requesting transmission of SR resources.
In an embodiment of the present application, the Msg3 carries information requesting transmission of SR resources, specifically, the Msg3 may carry a bit for indicating that SR resources are requested to be transmitted, for example, when the bit is "1", it indicates that the terminal requests SR resources from the network device, and when the bit is "0", it indicates that the terminal does not request SR resources or the terminal does not support an SR mechanism.
In another embodiment of the present application, the Msg3 carries information requesting transmission of the differentiated SR resource and information requesting permission to send the Piggybacked SR, and specifically, the Msg3 may carry two bits, one bit is used to indicate whether transmission of the differentiated SR resource is requested, and the other bit is used to indicate whether transmission of the Piggybacked SR is requested, for example, when the value of the two bits is "00", the resource not requesting transmission of the differentiated SR and the resource not requesting transmission of the Piggybacked SR are indicated, "01" indicates the resource only requesting transmission of the differentiated SR, "10" indicates the resource only requesting permission of the Piggybacked SR, and "11" indicates the resource requesting transmission of the differentiated SR and the resource requesting permission to send the Piggybacked SR.
In this 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 rrcconnectionresumerrequest, an rrcconnectionrequestablistensionrequest, and the like, where the RRCConnectionRequest includes a ue-Identity, an estinewcause, and the like, and the rrcconnectionresumerrequest includes a resumeID, a resummesuse, and the like, and the bit for indicating that the SR resource is requested to be transmitted may be included in the RRCConnectionRequest, the rrcconnectionresumerrequest, or the rrcconnectionrequestablistensionrequest.
S202, the network device allocates resources for transmitting the dedicated SR according to the Msg 3.
After receiving the Msg3, if the terminal requests to transmit SR resources, the network device determines whether resources for transmitting the dedicated SR can be allocated to the terminal, and if so, the network device allocates resources for transmitting the dedicated SR to the terminal so that the terminal sends the dedicated SR; if not, for example, the resources are insufficient, the network device does not allocate the terminal with the resources for transmitting the dedicated SR, and the terminal cannot transmit the dedicated SR at this time.
S203, the network device determines whether the terminal is allowed to send the piggybacked SR.
The network device determines whether to allow the terminal to transmit the piggybacked SR, in addition to determining whether to allocate resources for transmitting the dedicated SR.
In an embodiment of the application, the Msg3 only carries information requesting transmission of the dedicated SR resource, and the network device determines whether to allow the terminal to send the piggybacked SR or not according to a detection capability, where the detection capability may be the number of the terminals that the network device has the largest blind detection, that is, whether the network device has an SR or not for blind detection of ACK/NACK sent by how many terminals, or a performance of the network device for blind detection of ACK/NACK, where the performance may be a detection omission probability or an error detection probability or other indexes.
In another embodiment of the application, the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR, the network device determines whether to allow the terminal to send the piggybacked SR according to the Msg3 and the detection capability, the network device determines to allow the terminal to send the piggybacked SR only when the Msg3 carries the information requesting permission to send the piggybacked SR and the detection capability is sufficient, otherwise, the network device determines not to allow the terminal to send the piggybacked SR, for example, when the Msg3 carries information not to send the piggybacked SR or the detection capability of the network device is insufficient, the network device determines not to allow the terminal to send the piggybacked SR.
S204, the network equipment sends the resource and the indication information for transmitting the dedicated SR to the terminal.
Wherein, the indication information is used to indicate whether the terminal is allowed to send the piggybacked SR. Specifically, the indication information may be information of one bit, for example, when the bit is "1", the indication information indicates that the terminal is allowed to transmit the piggybacked SR, and when the bit is "0", the indication information indicates that the terminal is not allowed to transmit the piggybacked SR.
S205, the terminal sends the dedicated SR to the network device on the resource for transmitting the dedicated SR.
S206, the network equipment sends the downlink grant DL grant to the terminal.
The DL Grant indicates NPDSCH resources and resources of ACK/NACK.
S207, the network device sends Downlink data through a Narrowband Physical Downlink Shared Channel (NPDSCH).
Accordingly, the terminal receives downlink data on the NPDSCH resources.
S208, the terminal sends ACK/NACK to the network equipment.
The terminal transmits ACK/NACK on the ACK/NACK resource indicated by the DL Grant.
Specifically, the terminal determines whether the transmitted ACK/NACK carries the piggybacked SR or not according to the indication information, when the indication information indicates that the terminal allows the transmission of the piggybacked SR, the terminal may carry the piggybacked SR in the ACK/NACK transmitted to the network device, and when the indication information indicates that the terminal is not allowed to transmit the piggybacked SR, the terminal does not carry the piggybacked SR in the ACK/NACK transmitted 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 piggybacked SR, the network device may perform blind detection on SR in the received ACK/NACK, where the blind detection refers to that the network device detects whether to carry SR on ACK/NACK resources and that the terminal sends ACK or NACK, and therefore, the blind detection SR generally includes 4 states: the ACK carries the SR, the NACK carries the SR, the ACK does not carry the SR, and the NACK does not carry the SR; if the indication information indicates that the terminal is not allowed to send piggybacked SR, the network equipment does not need to blindly detect SR in the received ACK/NACK.
S209, the network device sends a downlink Grant UL Grant to the terminal.
The UL Grant indicates a resource of a Narrow-band Physical Uplink Shared Channel (NPUSCH).
S210, the terminal sends uplink data to the network equipment.
And the uplink data is sent to the network equipment through the NPUSCH.
It should be noted that, in this embodiment, the execution sequence between steps S201 to S210 is not limited.
In this embodiment, the network device sends, to the terminal, indication information indicating whether to allow sending of the piggybacked SR, so that if the network device indicates that the terminal allows sending of the piggybacked SR, the network device may blindly detect the SR in ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device may not blindly detect the SR in ACK/NACK, thereby reducing blind detection of the network device.
Fig. 3 is a schematic flowchart of a resource transmission method provided in an embodiment of the present application. In this embodiment, the terminal and the network device agree in advance, if the terminal receives the resource for transmitting the dedicated SR allocated by the network device, the terminal only sends the dedicated SR and does not send the piggybacked SR, and if the terminal does not receive the resource for transmitting the dedicated SR allocated by the network device, the terminal does not send the dedicated SR but allows sending the piggybacked SR.
Specifically, the method shown in fig. 3 includes:
s301, the terminal sends a third message Msg3 to the network device, and the Msg3 carries the information requesting to transmit the SR resources.
Specifically, when the terminal needs to send uplink data to the network device, the terminal triggers sending of a third message Msg3 to the network device, where Msg3 may carry a bit for indicating a request to transmit SR resources.
S302, the network device allocates resources for transmitting the dedicated SR according to the third message Msg 3.
In this embodiment, the network device does not send the indication information to the terminal to notify whether the terminal is allowed to send the piggybacked SR, and the network device may default that if the terminal is allocated with a resource for transmitting the dedicated SR, the terminal will not send the piggybacked SR, and if the terminal is not allocated with a resource for transmitting the dedicated SR, the terminal is allowed to send the piggybacked SR.
S303, the network device sends the resource for transmitting the dedicated SR to the terminal.
S304, the terminal sends the dedicated SR to the network equipment on the resource for transmitting the dedicated SR.
S305, the network device sends a downlink grant DL grant to the terminal.
The DL Grant indicates NPDSCH resources and resources of ACK/NACK.
S306, the network device sends downlink data through NPDSCH.
Accordingly, the terminal receives downlink data on the NPDSCH resources.
S307, the terminal sends ACK/NACK.
The terminal transmits the ACK/NACK on the ACK/NACK resource.
Since the network device sends the terminal the resource for transmitting the dedicated SR in step S303, the terminal sends ACK/NACK that does not carry piggybacked SR, that is, the terminal does not send piggybacked SR, and the network device does not blindly detect SR in the received ACK/NACK. On the contrary, if the network device does not send the resource for transmitting the dedicated SR to the terminal, the network device may blindly detect the SR in the received ACK/NACK.
And S308, the network equipment sends the downlink Grant UL Grant to the terminal.
The UL Grant indicates resources of NPUSCH.
S309, the terminal sends uplink data to the network device.
And the uplink data is sent to the network equipment through the NPUSCH.
It should be noted that, there are steps in fig. 3 and fig. 2 that describe the same, and the embodiment does not describe the same, and reference may be made to the related description in the embodiment of fig. 2; in this embodiment, the execution sequence between steps S301 to S309 is not limited.
In this embodiment, the network device does not need to send indication information to the terminal to inform whether the terminal is allowed to send the piggybacked SR, the network device defaults that if the terminal is allocated with a resource for transmitting the dedicated SR, the terminal does not send the piggybacked SR, at this time, the network device does not need to blindly detect the SR in the received ACK/NACK, if the terminal is not allocated with a resource for transmitting the dedicated SR, the terminal is allowed to send the piggybacked SR, at this time, the network device needs to blindly detect the SR in the received ACK/NACK, which reduces both the blindness of the network device and the instruction information of whether the network device is allowed to send the piggybacked SR to the terminal.
In the embodiments respectively corresponding to fig. 2 and fig. 3, when a terminal needs to send uplink data to a network device, the terminal triggers sending of a third message Msg3 to the network device to request transmission of SR resources, where Msg3 is a message in a connection state establishment process, and in the embodiment of the present application, the terminal may also request transmission of SR resources to the network device in Capability report information after the connection state establishment, for example, a request in a terminal-Capability-NB message, so that the present application provides an embodiment in which the third message Msg3 is replaced with the Capability report information in the embodiments described in fig. 2 and fig. 3, and the following briefly describes an embodiment in which the Capability report information replaces the third message Msg 3:
referring to the embodiment in fig. 2, in an embodiment of the present application, information for indicating that SR resources are requested to be transmitted is carried in capability reporting information sent by a terminal to a network device, the network device allocates resources for transmitting a differentiated SR according to the capability reporting information and determines whether the terminal is allowed to send a piggybacked SR, then the network device sends the resources for transmitting the differentiated SR and indicating information whether the terminal is allowed to send the piggybacked SR, and other steps may be described with reference to fig. 2.
Referring to the embodiment in fig. 3, in an embodiment of the present application, the capability reporting information sent by the terminal to the network device carries information for requesting transmission of SR resources, the network device allocates resources for transmitting the dedicated SR according to the capability reporting information, then the network device sends the resources for transmitting the dedicated SR to the terminal, and other steps may refer to related descriptions in fig. 3.
The resource transmission apparatus 400 provided in the embodiment of the present application will be described below with reference to fig. 4, where the resource transmission apparatus 400 includes:
a sending module 410, configured to send a third message Msg3 to the network device.
Wherein, the Msg3 carries information requesting to transmit scheduling request SR resources;
in an embodiment of the present application, the Msg3 carries a bit for indicating that SR resources are requested for transmission.
In another embodiment of the present application, the Msg3 carries information requesting to transmit the dedicated SR resource and information requesting to allow the piggybacked SR to be sent.
Further, the sending module 410 is configured to:
when uplink data need to be sent to the network equipment, the Msg3 is sent to the network equipment; and sending the uplink data to the network equipment.
A receiving module 420, configured to receive a resource and indication information, which are sent by the network device and used for transmitting a dedicated scheduled SR, where the indication information is used to indicate whether to allow the terminal device to send a piggybacked SR;
a sending module 410, configured to send the dedicated SR to the network device on a resource used for transmitting the dedicated SR;
a determining module 430, configured to determine that the ACK/NACK carries the piggybacked SR according to the indication information.
The resource transmission apparatus 500 provided in the embodiment of the present application will be described below with reference to fig. 5, where the resource transmission apparatus 500 includes:
a sending module 510, configured to send indication information to a terminal, where the indication information is used to indicate whether the terminal is allowed to send a piggybacked SR;
a receiving module 520, configured to receive an ACK/NACK message sent by the terminal;
a detecting module 530, configured to detect whether there is an SR in the ACK/NACK message 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 apparatus 500 further includes:
the receiving module 520 is further configured to receive the Msg3 sent by the terminal, where the Msg3 carries information requesting transmission of scheduling request SR resources;
an allocating module 540, configured to allocate resources for transmitting dedicated SR according to the Msg 3;
a sending module 510, configured to send a resource for transmitting the dedicated SR to the terminal;
the receiving module 520 is further configured to receive the truncated SR sent by the terminal.
In one implementation of the present application, the Msg3 carries a bit indicating that SR resources are requested for transmission.
Correspondingly, the resource transmission apparatus further includes a determining module 550, configured to determine whether to allow the terminal to send the piggybacked SR according to the detection capability.
In another implementation of the present application, the Msg3 carries information requesting to transmit the dedicated SR resource and information requesting to allow the piggybacked SR to be sent.
Correspondingly, the resource transmission apparatus further includes a determining module 550, configured to determine whether to allow the terminal to send the piggybacked SR according to the Msg3 and the detection capability.
In the above embodiment, the network device sends, to the terminal, indication information indicating whether to allow sending of the piggybacked SR, so that if the network device indicates that the terminal allows sending of the piggybacked SR, the network device may blindly detect the SR in ACK/NACK, and if the network device indicates that the terminal is not allowed to send the piggybacked SR, the network device may not blindly detect the SR in ACK/NACK, thereby reducing blind detection of the network device.
Referring to fig. 6a, a resource transmission apparatus 600 is provided for the embodiment of the present application, where the resource transmission apparatus 600 includes:
processing means 610 for processing data received by the transceiver 620;
a transceiver 620 for receiving or transmitting data.
Optionally, the communication device further includes:
the antenna 630, and the transceiver 620 specifically receive or transmit data through the antenna 630.
When the processing means 610 is implemented by software, as shown in fig. 6a, the processing means 610 includes:
a memory 612 for storing programs;
the processor 611 is configured to execute the program stored in the memory, and when the program is executed, the implementation of the foregoing method embodiment is performed, for specific please refer to the description in the foregoing method embodiment, which will not be described herein again for the execution process of the processor 611.
The memory 612 may be a physically separate unit or may be integrated with the processor 611, as shown in fig. 6 b.
The resource transmission apparatus 600 according to the embodiment of the present application may be a wireless communication apparatus such as an access point, a station, a base station, or a user terminal.
The elements and method processes of the examples described in this application may be implemented in electronic hardware, or in a combination 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 implementation. Skilled artisans may implement the described functionality in varying ways for each particular application.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice. For example, various elements or components may be combined or may be integrated into another system, or some steps may be omitted, or not performed. Furthermore, the coupling or direct coupling or communication connection between the units may be realized through some interfaces, which may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Claims (24)

1. A method for resource transmission, comprising:
sending a third message Msg3 to a network device, wherein the Msg3 carries information requesting transmission of Scheduling Request (SR) resources;
receiving resources and indication information which are sent by the network equipment and used for transmitting the special dedicated SR, wherein the indication information is used for indicating whether the terminal equipment is allowed to send the piggybacked SR or not;
transmitting the dedicated SR to the network equipment on a resource for transmitting the dedicated SR;
and determining that the piggybacked SR is carried in the ACK/NACK according to the indication information.
2. The method of claim 1, wherein the Msg3 carries a bit indicating a request to transmit SR resources.
3. The method of claim 1, wherein the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR.
4. The method of any of claims 1-3, wherein sending a third message Msg3 to the network device comprises:
when uplink data need to be sent to the network equipment, the Msg3 is sent to the network equipment;
the method further comprises the following steps:
and sending the uplink data to the network equipment.
5. A method for resource transmission, comprising:
sending indication information to a terminal, wherein the indication information is used for indicating whether the terminal is allowed to send the piggybacked SR or not;
receiving an ACK/NACK message sent by the terminal;
and when the indication information indicates that the terminal is allowed to send the piggybacked SR, detecting whether the SR exists in the ACK/NACK message.
6. The method of claim 5, further comprising:
receiving a third message Msg3 sent by the terminal, wherein the Msg3 carries information requesting transmission of Scheduling Request (SR) resources;
allocating resources for transmitting dedicated SR according to the Msg 3;
sending a resource for transmitting the dedicated SR to the terminal;
and receiving the dedicated SR sent by the terminal.
7. The method of claim 6, wherein the Msg3 carries a bit indicating a request to transmit SR resources.
8. The method of claim 7, wherein before sending the indication information to the terminal, further comprising:
and determining whether the terminal is allowed to send the piggybacked SR or not according to the detection capability.
9. The method of claim 6, wherein the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR.
10. The method of claim 9, wherein before sending the indication information to the terminal, further comprising:
and determining whether the terminal is allowed to send piggybacked SR or not according to the Msg3 and the detection capability.
11. The method of any one of claims 5-10, wherein when the indication information indicates that the terminal is not allowed to send the piggybacked SR, whether there is an SR is not detected in the ACK/NACK.
12. An apparatus for resource transmission, comprising:
a sending module, configured to send a third message Msg3 to a network device, where the Msg3 carries information requesting transmission of scheduling request SR resources;
a receiving module, configured to receive a resource and indication information, which are sent by the network device and used for transmitting a dedicated differentiated SR, where the indication information is used to indicate whether a 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 used for transmitting the dedicated SR;
and the determining module is used for determining that the piggybacked SR is carried in the ACK/NACK according to the indication information.
13. The apparatus of claim 12, wherein the Msg3 carries a bit indicating a request to transmit SR resources.
14. The apparatus of claim 12, wherein the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR.
15. The apparatus of any of claims 12-14, wherein the sending module is to:
when uplink data need to be sent to the network equipment, the Msg3 is sent to the network equipment; and
and sending the uplink data to the network equipment.
16. An apparatus for resource transmission, comprising:
the terminal comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending indication information to the terminal, and the indication information is used for indicating whether the terminal is allowed to send the piggybacked SR;
a receiving module, configured to receive an ACK/NACK message sent by the terminal;
a detecting module, configured to detect whether there is an SR in the ACK/NACK message when the indication information indicates that the terminal is allowed to send the piggybacked SR.
17. The apparatus 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 transmission of scheduling request SR resources;
an allocation module, configured to allocate a resource for transmitting a dedicated SR according to the Msg 3;
the sending module is further configured to send a resource for transmitting the dedicated SR to the terminal;
the receiving module is further configured to receive the dedicated SR sent by the terminal.
18. The apparatus of claim 17, wherein the Msg3 carries a bit indicating a request to transmit SR resources.
19. The apparatus of claim 18, further comprising:
a determining module, configured to determine whether to allow the terminal to send the piggybacked SR according to the detection capability.
20. The apparatus of claim 17, wherein the Msg3 carries information requesting transmission of a dedicated SR resource and information requesting permission to send a piggybacked SR.
21. The apparatus of claim 20, further comprising:
and the determining module is used for determining whether the terminal is allowed to send the piggybacked SR or not according to the Msg3 and the detection capability.
22. The apparatus of any one of claims 16-21, wherein the detecting module is further configured to not detect whether there is an SR in the ACK/NACK when the indication information indicates that the terminal is not allowed to send the piggybacked SR.
23. An apparatus for resource transmission, comprising:
a memory for storing a program;
a processor for executing the program stored by the memory, the processor being configured to perform the method of any of claims 1-4 or 5-11 when the program is executed.
24. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-4 or 5-11.
CN201810302136.6A 2018-04-04 2018-04-04 Resource transmission method and device Active CN110351006B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201810302136.6A CN110351006B (en) 2018-04-04 2018-04-04 Resource transmission method and device
PCT/CN2019/081422 WO2019192585A1 (en) 2018-04-04 2019-04-04 Resource transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810302136.6A CN110351006B (en) 2018-04-04 2018-04-04 Resource transmission method and device

Publications (2)

Publication Number Publication Date
CN110351006A CN110351006A (en) 2019-10-18
CN110351006B true CN110351006B (en) 2021-08-13

Family

ID=68100076

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810302136.6A Active CN110351006B (en) 2018-04-04 2018-04-04 Resource transmission method and device

Country Status (2)

Country Link
CN (1) CN110351006B (en)
WO (1) WO2019192585A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330444A (en) * 2007-06-19 2008-12-24 中兴通讯股份有限公司 Control method and apparatus for upstream data transmission of long-term evolvement system
CN101542956A (en) * 2006-11-30 2009-09-23 艾利森电话股份有限公司 Adjusting the targeted number of transmission attempts
WO2008156402A9 (en) * 2007-06-19 2010-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for scheduling resources in a telecommunication system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2008320874B2 (en) * 2007-10-30 2013-09-19 Nokia Solutions And Networks Oy Providing improved scheduling request signaling with ACK/NACK or CQI
WO2010123893A1 (en) * 2009-04-22 2010-10-28 Interdigital Patent Holdings, Inc. Method and apparatus for transmitting uplink control information for carrier aggregated spectrums
US9462607B2 (en) * 2014-08-28 2016-10-04 Intel IP Corporation Apparatus, method and system of multi-user uplink transmission

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101542956A (en) * 2006-11-30 2009-09-23 艾利森电话股份有限公司 Adjusting the targeted number of transmission attempts
CN101330444A (en) * 2007-06-19 2008-12-24 中兴通讯股份有限公司 Control method and apparatus for upstream data transmission of long-term evolvement system
WO2008156402A9 (en) * 2007-06-19 2010-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for scheduling resources in a telecommunication system

Also Published As

Publication number Publication date
CN110351006A (en) 2019-10-18
WO2019192585A1 (en) 2019-10-10

Similar Documents

Publication Publication Date Title
CN110167035B (en) Beam management method, terminal, network device and storage medium
JP6604524B2 (en) Method and terminal for data transmission
US20160337086A1 (en) Method for configuring physical uplink channel, base station and user equipment
US20200137785A1 (en) User equipment (ue) and method for managing buffer status report (bsr) for multiple-numerology operation
JP2016530761A (en) Uplink control signaling for FDD-TDD joint carrier aggregation
JP2019510387A (en) Service transmission method and apparatus
EP3595367A1 (en) Method and device for transmitting indication information
US11882556B2 (en) Transmission of physical uplink channels and signals for new radio beamformed system
CN116326057A (en) HARQ feedback for NR side-chain communication in unlicensed spectrum
CN109600852B (en) Resource indication method, communication device and network equipment
EP3331294A1 (en) Method of allocating radio resource and device utilizing same
US11082982B2 (en) Methods devices, and systems, for allocation of uplink resources for wireless data transmission
WO2021035580A1 (en) Sidelink cbg-based harq feedback and associated retransmissions over reserved resources
CN110351006B (en) Resource transmission method and device
CN112470416A (en) Wireless communication method, terminal equipment and network equipment
CN115835345A (en) HARQ process allocation method, device, base station and storage medium
US11178682B2 (en) Method for requesting uplink transmission resource, terminal, and network device
CN113285789B (en) Resource indication method and device of auxiliary link control information and terminal equipment
US20210112389A1 (en) Access mechanism for single purpose operation
JP2021100250A (en) Method and terminal for data transmission
CN114223159A (en) Transmission of higher layer ACK/NACK
WO2019192002A1 (en) Information transmission method, terminal device, and network device
EP4149069A1 (en) Method and device for transmitting physical downlink control channel and storage medium
US20240187995A1 (en) Method and apparatus for pusch transmission with repetitions
CN115516878A (en) Location enhancement mechanism

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