WO2018170924A1 - 资源调度方法、终端设备及网络设备 - Google Patents

资源调度方法、终端设备及网络设备 Download PDF

Info

Publication number
WO2018170924A1
WO2018170924A1 PCT/CN2017/078201 CN2017078201W WO2018170924A1 WO 2018170924 A1 WO2018170924 A1 WO 2018170924A1 CN 2017078201 W CN2017078201 W CN 2017078201W WO 2018170924 A1 WO2018170924 A1 WO 2018170924A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
nprach
terminal device
scheduling request
network device
Prior art date
Application number
PCT/CN2017/078201
Other languages
English (en)
French (fr)
Inventor
罗之虎
金哲
铁晓磊
陈哲
汲桐
张维良
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/078201 priority Critical patent/WO2018170924A1/zh
Priority to EP17902525.9A priority patent/EP3614758A4/en
Priority to PCT/CN2017/084222 priority patent/WO2018171023A1/zh
Priority to JP2019552461A priority patent/JP7221874B2/ja
Priority to CN202111138754.XA priority patent/CN114025414B/zh
Priority to CN201780084078.8A priority patent/CN110214464B/zh
Publication of WO2018170924A1 publication Critical patent/WO2018170924A1/zh
Priority to US16/580,911 priority patent/US11533744B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to communications technologies, and in particular, to a resource scheduling method, a terminal device, and a network device.
  • IoT Internet of Things
  • NB-IoT Narrowband Internet of Things
  • the terminal device needs to send uplink data to the network device, the random access needs to be re-initiated, and then the uplink data is sent.
  • the terminal device needs to wait for the second message of the random access procedure to send the uplink data, resulting in an increase in power consumption and delay of the terminal device.
  • the present invention provides a resource scheduling method, a terminal device, and a network device, which are used to solve the problem that the power consumption of the terminal device is increased due to the excessive request for the uplink data process in the prior art.
  • the first aspect of the present application provides a resource scheduling method, in which, after receiving a configuration message of a network device, the terminal device acquires first resource configuration information for sending a scheduling request according to the configuration message, and the first resource configuration information.
  • the device includes information for indicating an enhanced coverage level, and the terminal device sends a scheduling request to the network device on the first resource indicated by the first resource configuration information, where the scheduling request is used to request an uplink channel resource from the network device, where the terminal The device does not perform a random access procedure when transmitting the scheduling request.
  • the network device sends a configuration message to the terminal device in advance, and when the terminal device needs to send the uplink data, the terminal device sends a scheduling request to the network device on the first resource indicated by the first resource configuration information in the configuration message. That is, the network device terminal device is required to send data, and then directly send the uplink data without performing a random access process, thereby reducing power consumption and delay of the terminal device.
  • the first resource configuration information sent by the network device indicates the enhanced coverage level information, thereby indicating the enhanced coverage level corresponding to the terminal device, that is, the resource indicated by the first resource configuration information can distinguish the coverage level, thereby satisfying the NB- Requirements for terminal equipment of different coverage levels in the IoT system.
  • the method before the terminal device receives the configuration message sent by the network device, the method further includes:
  • the terminal device acquires configuration information of an NPRACH resource according to the system message
  • the NPRACH resource is a resource set of the first resource, or the subset of the NPRACH resource is a resource set of the first resource, or the NPRACH resource is used for competing random access.
  • a resource other than the resource is a resource set of the first resource, or a subset of the NPRACH resource other than the resource used for contending random access is a resource set of the first resource.
  • the terminal device further carries the uplink data to be transmitted when sending the scheduling request to the network device.
  • Data volume information In an optional manner, the terminal device further carries the uplink data to be transmitted when sending the scheduling request to the network device.
  • the terminal device sends a scheduling request to the network device in a delayed or advanced manner on the first resource, and the time amount of the delay corresponding to the scheduling request or an advanced time amount and the waiting
  • the data amount information of the transmitted uplink data has a preset correspondence relationship
  • the terminal device carries the data volume information of the uplink data to be transmitted when the scheduling request is sent to the network device by using the first resource, where the first resource includes a time domain resource, a frequency domain resource, a code resource, or a combination of the time domain resource, the frequency domain resource, and the code resource, the time domain resource, the frequency domain resource, the code resource, or the combination of the time domain resource, the frequency domain resource, the code resource, and the uplink data to be transmitted.
  • the quantity information has a preset correspondence.
  • the signal that the terminal device sends the scheduling request is a preamble in the NPRACH, and the terminal device performs the time advance TA adjustment before sending the scheduling request.
  • the second aspect of the present application provides a resource scheduling method, in which a network device first sends a configuration message to a terminal device, where the configuration message is used by the terminal device to acquire first resource configuration information for sending a scheduling request, where the first resource is used.
  • the configuration information includes information indicating an enhanced coverage level.
  • the network device receives a scheduling request sent by the terminal device on the first resource indicated by the first resource configuration information, where the scheduling request is used to request an uplink channel resource from the network device, and the terminal device does not perform random connection when sending the scheduling request. Into the process. Further, the network device allocates an uplink channel resource to the terminal device according to the scheduling request.
  • the method before the sending, by the network device, the configuration message to the terminal device, the method further includes:
  • the network device sends a system message to the terminal device, where the system message carries configuration information of an NPRACH resource;
  • the NPRACH resource is a resource set of the first resource, or the subset of the NPRACH resource is a resource set of the first resource, or the NPRACH resource is used for competing random access.
  • a resource other than the resource is a resource set of the first resource, or a subset of the NPRACH resource other than the resource used for contending random access is a resource set of the first resource.
  • the network device may determine the data volume information of the uplink data to be transmitted according to the scheduling request sent by the terminal device.
  • the network device determines, according to the amount of time delay or the amount of time delay corresponding to the scheduling request received on the first resource, the data volume of the uplink data to be transmitted.
  • the information wherein the amount of time delay or the amount of time corresponding to the scheduling request has a preset correspondence relationship with the data amount information of the uplink data to be transmitted;
  • the network device Determining, by the network device, the data volume information of the uplink data to be transmitted according to the received first resource corresponding to the scheduling request, where the first resource includes a time domain resource, a frequency domain resource, and a code resource. Or a combination of the time domain resource, the frequency domain resource, and the code resource, the time domain resource, the frequency domain resource, the code resource, or the combination of the time domain resource, the frequency domain resource, the code resource, and the uplink data to be transmitted.
  • the data amount information has a preset correspondence relationship.
  • the signal of the scheduling request received by the network device is a preamble in the NPRACH, and the terminal device performs a time advance TA adjustment before sending the scheduling request.
  • system message carries a first preset parameter and a second preset parameter
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the NPRACH resource and the first preset parameter, and the starting subcarrier location of the resource set of the first resource is based on the NPRACH resource Determining a subcarrier position and determining the second preset parameter;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of the NPRACH resource and the first preset parameter, and the starting subcarrier location of the resource set of the first resource is according to the NPRACH
  • the starting subcarrier position of the subset of resources is determined with the second preset parameter.
  • system message carries a first offset parameter and a second offset parameter
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the NPRACH resource and the first offset parameter, and the starting subcarrier location of the resource set of the first resource is based on the NPRACH resource Determining a subcarrier position and the second bias parameter determination;
  • the carrier location of the resource set of the first resource is determined according to a carrier location of the subset of the NPRACH resource and the first offset parameter, and a starting subcarrier location of the resource set of the first resource is according to the NPRACH
  • the starting subcarrier position of the subset of resources and the second biasing parameter are determined.
  • the system message carries a first preset scale factor and a second preset scale factor
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the NPRACH resource and the first preset scaling factor, and the starting subcarrier location of the resource set of the first resource is according to the NPRACH resource Determining a subcarrier position and the second preset scaling factor;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of the NPRACH resource and the first preset scaling factor, and the starting subcarrier location of the resource set of the first resource is according to the The starting subcarrier position of the subset of NPRACH resources is determined by the second preset scaling factor.
  • a third aspect of the present application provides a resource scheduling method, in which a terminal device receives a downlink control information DCI indication sent by a network device, where the DCI is used to indicate a first resource, and the first resource is used for NPUSCHformat2 transmission.
  • the time-frequency resource and further, the terminal device determines the first resource according to the DCI, and further, the terminal device sends a scheduling request to the network device on the first resource.
  • the terminal device sends a scheduling request to the network device on the first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission, that is, the terminal device can use the NPUSCH format2 to send a scheduling request, thereby saving the dedicated use.
  • the resource that dispatched the request is not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to send a scheduling request.
  • the terminal device sends a scheduling request to the network device on the first resource, including:
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource simultaneously by high-order modulation.
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource by performing phase rotation on a modulation symbol corresponding to the HARQ-ACK feedback message.
  • the terminal device transmits the scheduling request and the HARQ on the first resource by multiplying a modulation symbol or a coding bit corresponding to the HARQ-ACK feedback information by a preset orthogonal code. - ACK feedback information.
  • the preset orthogonal code is a Hadamard sequence of length 16.
  • the method further includes:
  • the terminal device When the terminal device sends a scheduling request to the network device, the data amount information of the uplink data to be transmitted is carried.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the constellation points of the high-order modulation.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the phase rotation size.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the preset orthogonal code sequence.
  • a fourth aspect of the present application provides a resource scheduling method, in which a network device first sends a DCI indication to a terminal device, where the DCI is used to indicate a first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission. Further, the network device receives the scheduling request sent by the terminal device on the first resource, and further, the network device allocates the uplink channel resource to the terminal device according to the scheduling request.
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource by using high-order modulation, and the network device determines, according to the received high-order modulated signal, whether the terminal device sends the scheduling. request.
  • the terminal device performs phase rotation on the modulation symbol corresponding to the HARQ-ACK feedback message to simultaneously transmit the scheduling request and the HARQ-ACK feedback information on the first resource, and the network device performs phase according to the received phase.
  • the rotated modulation symbol determines whether the terminal device has sent a scheduling request.
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource by multiplying the modulation symbol or the coding bit corresponding to the HARQ-ACK feedback information by the preset orthogonal code.
  • the device determines, according to the received modulation symbol multiplied by the preset orthogonal code, whether the terminal device sends the scheduling request.
  • the preset orthogonal code is a Hadamard sequence of length 16.
  • the network device determines the data volume information of the uplink data to be transmitted according to the scheduling request sent by the terminal device.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the constellation points of the high-order modulation.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the phase rotation size.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the preset orthogonal code sequence.
  • a fifth aspect of the present application provides a terminal device, which has the function of implementing the terminal device in the first aspect. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the terminal device may include a receiving module, a processing module, and a sending module, where the modules may perform corresponding functions in the foregoing methods, for example, a receiving module, configured to receive a configuration message sent by the network device; And the first resource configuration information for sending the scheduling request is obtained according to the configuration information received by the receiving module, where the first resource configuration information includes information for indicating an enhanced coverage level, and the sending module is configured to be acquired by the processing module.
  • the first resource indicated by the first resource configuration information sends a scheduling request to the network device, where the scheduling request is used to request an uplink channel resource from the network device, and the terminal device does not perform the random access procedure when sending the scheduling request.
  • the sixth aspect of the present application provides a network device, where the network device has the function of implementing the network device in the second aspect.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the network device may include a sending module, a receiving module, and a processing module, and the modules may perform corresponding functions in the foregoing methods, for example, a sending module, configured to send a configuration message to the terminal device, the configuration message And the first resource configuration information is used by the terminal device to send the scheduling request, where the first resource configuration information includes information for indicating an enhanced coverage level, and the receiving module is configured to receive, by the terminal device, the first resource configuration information.
  • a sending module configured to send a configuration message to the terminal device, the configuration message
  • the first resource configuration information is used by the terminal device to send the scheduling request, where the first resource configuration information includes information for indicating an enhanced coverage level
  • the receiving module is configured to receive, by the terminal device, the first resource configuration information.
  • the scheduling request is used to request an uplink channel resource from the network device, and the terminal device does not perform a random access process when the scheduling request is sent;
  • the processing module is configured to send, according to the scheduling request received by the receiving module, The terminal device allocates uplink channel resources.
  • the seventh aspect of the present application provides a terminal device, which has the function of implementing the terminal device in the third aspect. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the terminal device may include a receiving module, a processing module, and a sending module, where the modules may perform corresponding functions in the foregoing methods, for example, a receiving module, configured to receive a DCI indication sent by the network device, where the DCI is The first resource is used to indicate a time-frequency resource for the NPUSCH format 2 transmission; the processing module is configured to determine the first resource according to the DCI; and the sending module is configured to send a scheduling request to the network device on the first resource.
  • a receiving module configured to receive a DCI indication sent by the network device, where the DCI is The first resource is used to indicate a time-frequency resource for the NPUSCH format 2 transmission
  • the processing module is configured to determine the first resource according to the DCI
  • the sending module is configured to send a scheduling request to the network device on the first resource.
  • An eighth aspect of the present application provides a network device, which has the function of implementing the network device in the fourth aspect. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the network device may include a sending module, a receiving module, and a processing module, where the modules may perform corresponding functions in the foregoing methods, for example, a sending module, configured to send a DCI indication to the terminal device, where the DCI is used.
  • a sending module configured to send a DCI indication to the terminal device, where the DCI is used.
  • Instructing the first resource, the first resource is a time-frequency resource for the NPUSCH format 2 transmission;
  • the receiving module is configured to receive a scheduling request sent by the terminal device on the first resource;
  • the processing module is configured to send the terminal device to the terminal device according to the scheduling request Allocate upstream channel resources.
  • a ninth aspect of the present application provides a terminal device, where the terminal device includes a memory and a processor, where the memory is used to store program instructions, and the processor is configured to invoke program instructions in the memory to implement the first aspect and The method in each embodiment.
  • a tenth aspect of the present application provides a network device, where the network device includes a memory and a processor, where the memory is used to store program instructions, and the processor is configured to invoke program instructions in the memory to implement the foregoing second aspect and The method in each embodiment.
  • An eleventh aspect of the present application provides a terminal device, where the terminal device includes a memory and a processor, where the memory is used to store program instructions, and the processor is configured to invoke program instructions in the memory to implement the third aspect and The method in each of its embodiments.
  • a twelfth aspect of the present application provides a network device, where the network device includes a memory and a processor, where the memory is used to store program instructions, and the processor is configured to invoke program instructions in the memory to implement the fourth aspect and The method in each of its embodiments.
  • 1 is an example of a processing procedure when a terminal device needs to send uplink data to a network device in an existing NB-IoT system;
  • FIG. 2 is a system architecture diagram of a resource scheduling method provided by the present application.
  • FIG. 3 is an interaction flowchart of Embodiment 1 of a resource scheduling method provided by the present application
  • FIG. 4 is a schematic diagram showing distribution of NPRACH frequency domain resources in an NB-IoT carrier in an existing NB-IoT system
  • FIG. 5 is a schematic diagram of a preamble of NB-IoT random access
  • 6 is a diagram showing an example of delaying transmission of a preamble sequence in NB-IoT random access to indicate transmission of data information
  • FIG. 7 is an interaction flowchart of Embodiment 2 of a resource scheduling method provided by the present application.
  • FIG. 8 is a block diagram of a first embodiment of a terminal device according to the present application.
  • FIG. 9 is a block diagram of a first embodiment of a network device according to the present application.
  • FIG. 10 is a block diagram of a first embodiment of a terminal device according to the present application.
  • FIG. 11 is a block diagram of a first embodiment of a network device according to the present application.
  • FIG. 12 is a physical block diagram of Embodiment 1 of a terminal device provided by the present application.
  • FIG. 13 is a physical block diagram of Embodiment 1 of a network device according to the present application.
  • FIG. 14 is a physical block diagram of Embodiment 1 of another terminal device provided by the present application.
  • FIG. 15 is a physical block diagram of Embodiment 1 of another network device provided by the present application.
  • the network device in order to avoid waste of resources, if the terminal device does not need uplink data to be transmitted, the network device does not allocate uplink resources for the terminal device.
  • the terminal device needs to transmit uplink resources, it should first inform the network device that the terminal device needs to transmit uplink resources, and request the network device to allocate uplink resources for the terminal device.
  • FIG. 1 is an example of a process in which a terminal device needs to send uplink data to a network device in an existing NB-IoT system. As shown in FIG. 1 , after receiving the uplink data, the terminal device re-initiates random access.
  • the terminal device sends an access preamble to the network device.
  • the network device returns a random access response to the terminal device.
  • the terminal device After receiving the response, the terminal device initiates a Radio Resource Control (RRC) request to the network device.
  • RRC Radio Resource Control
  • the network device sends an RRC connection setup message to the terminal device.
  • the terminal device network device sends an RRC connection setup complete message.
  • the terminal device sends uplink data to the network device.
  • the terminal device needs to report the size of the uplink data to the network device at least after the S103, and send the uplink data to the network device.
  • the terminal device needs to wait for a long time and perform more operations before sending uplink data. This increases the power consumption and latency of the terminal device. Moreover, when there is an access conflict between multiple terminal devices, the terminal device may retreat or even fail, further aggravating the power consumption and delay of the terminal device.
  • the present application is based on the above problem, and provides a resource scheduling method, in which the network device sends configuration information to the terminal device in advance.
  • the terminal device needs to send uplink data
  • the terminal device sends a scheduling to the network device on the specific resource indicated by the configuration information.
  • the request informs the network device that the terminal device needs to send data, and then directly sends the uplink data without performing a random access procedure, thereby reducing power consumption and delay of the terminal device.
  • the configuration information sent by the network device includes information such as an enhanced coverage level index or the number of repetitions, and directly or indirectly indicates an enhanced coverage level corresponding to the terminal device, that is, the resource indicated by the configuration information can distinguish the coverage level, thereby satisfying the NB-
  • the IoT system requires coverage levels.
  • a network device can communicate with multiple terminal devices, where the network device can be a base station, and the terminal device can be, for example, Any terminal device that performs machine type communication such as a mobile phone or a printer.
  • the method provided by the present application is applicable to any terminal device.
  • FIG. 3 is an interaction flowchart of Embodiment 1 of a resource scheduling method provided by the present application. As shown in FIG. 3, an implementation process of the method is:
  • the network device sends a system message.
  • the network device may notify all terminal devices in the serving cell of the configuration parameters of the available resource set by using the system message, where the resource set is used by the terminal device to send a scheduling request to the network device.
  • the resource set may be a Narrowband Physical Random Access CHannel (NPRACH) resource, an NPRACH resource subset, an Narrowband Physical Uplink Shared CHannel (NPUSCH) format1 resource, an NPUSCH format1 resource subset, and an NPUSCH format2. Resource or a subset of NPUSCH format2 resources.
  • NPRACH Narrowband Physical Random Access CHannel
  • NPUSCH Narrowband Physical Uplink Shared CHannel
  • the network device may indicate, in the system message, a carrier frequency point, a number of carriers, a number of subcarriers, a starting subcarrier frequency domain position, an enhanced coverage level index, a repetition number, and a period of the NPRACH resource. , start time, preamble format, preamble transmission maximum number of attempts and other configuration information.
  • the enhanced coverage level index or the number of repetitions may be used to indicate an enhanced coverage level corresponding to the resource.
  • the present application reduces power consumption and delay of a terminal device by transmitting a scheduling request on a specific resource and does not perform a random access procedure.
  • the specific resource needs to distinguish the coverage level.
  • the foregoing NPRACH resource can be used to distinguish the coverage level. Therefore, as an optional implementation manner, the specific resource used for sending the scheduling request in the present application may use the NPRACH resource, and the inherited NPRACH resource may distinguish the coverage level.
  • NPRACH resource is used as the specific resource for sending the scheduling request, and the above conflict mechanism can be inherited. Avoid placing additional restrictions on the scheduling of network devices and maintain good backward compatibility.
  • other resources other than the NPRACH resource may also be used for the specific resource.
  • the specific resources used to send the scheduling request in the present application can be determined in the following three ways:
  • the network device may be configured in the network device and the terminal device in advance or through the message indicating which NPRACH resources are used as the specific resources, or which NPRACH resources are used as the specific resources according to the rules stipulated in the protocol, or according to the operator. Or the manufacturer-defined rule stipulates which NPRACH resources are used as the specific resources mentioned above, and does not require the network device to notify through the system message of this step.
  • the network device can notify these parameters via the system message described above. That is, the network device may indicate, in addition to the information such as the carrier frequency and the number of carriers of the NPRACH resource in the system message, the parameters corresponding to the specific resource that sends the scheduling request.
  • the network device directly indicates, by using the foregoing system message, a resource set that can be the specific resource, and does not depend on the NPRACH resource set, and the network device can indicate configuration parameters of the specific resource, including carrier location, number of carriers, number of subcarriers, in the system message, The starting subcarrier frequency domain position, the scheduling request maximum transmission number, and the like.
  • the resource determined by the mode may also be an NPRACH resource or a resource other than the NPRACH resource.
  • the network device sends a configuration message to the terminal device.
  • the configuration message is used to indicate the first resource configuration information used by the terminal device to send the scheduling request.
  • the terminal device acquires first resource configuration information used to send a scheduling request according to the foregoing configuration message.
  • the terminal device After receiving the configuration message, acquires the first resource configuration information that is carried in the first resource configuration information, where the first resource configuration information may include a carrier index, a starting subcarrier index, a scheduling request, a maximum number of transmissions, and an indication of an enhanced coverage level.
  • the information and the like, wherein the information used to indicate the enhanced coverage level may specifically be an enhanced coverage level index or a repetition number.
  • the specific resource used for sending the scheduling request directly uses the NPRACH resource.
  • the network device will all belong to the serving cell.
  • the terminal device broadcasts the NPRACH resource set, including the number of carriers, the number of subcarriers, the location of the starting subcarrier frequency domain, and the number of repetitions.
  • each terminal device learns the configuration information of the NPRACH resource set.
  • the network device determines, according to the configuration information of the specific resource that is configured in advance, the specific resource that is sent by the specific terminal device by using the scheduling request, and adopts a carrier index, a starting subcarrier index, a starting subcarrier frequency domain location, and the like. Notifying which of the carriers of the particular terminal device to use to transmit the scheduling request.
  • the NPRACH resource can distinguish the coverage level, and each group of NPRACH resources in the NPRACH resource set indicated by the system message of the network device corresponds to an enhanced coverage level, the network device according to the enhanced coverage level of the terminal device, and the pre-configured configuration information.
  • the terminal device is allocated a resource that meets its coverage requirement within the NPRACH resource set.
  • the network device may send the foregoing first resource configuration information by using an RRC message in a random access procedure, specifically, obtaining a fourth message in a contention random access procedure.
  • the terminal device sends a scheduling request to the network device on the first resource indicated by the first resource configuration information.
  • the terminal device starts a timer, and starts counting the number of times the scheduling request is transmitted.
  • the first resource refers to the foregoing subset of the specific resource that sends the scheduling request, that is, the specific resource is the resource set of the first resource.
  • the scheduling request is used to request an uplink channel resource from a network device, and the terminal device does not perform a random access procedure when transmitting the scheduling request.
  • the terminal device sends a scheduling request on the first resource determined by the foregoing steps, that is, requests the uplink channel resource from the network device, instead of requesting the uplink channel from the network device by re-initiating the random access as in the prior art. Resources.
  • the network device detects, on the first resource, the scheduling request sent by the terminal device, and if the network device detects the scheduling request, allocates an uplink channel resource to the terminal device according to the scheduling request, if the network device does not detect the scheduling request, the network The device does not perform a transfer operation.
  • the terminal device If the terminal device receives the uplink channel resource allocated by the network device when the timer is not timed out, the terminal device sends a buffer status report or uplink data on the uplink channel resource allocated by the network device, otherwise the terminal device is in the first resource. Retransmit the scheduling request on. If the number of times the scheduling request is transmitted exceeds the maximum number of transmissions requested by the scheduler, the terminal device triggers a random access procedure.
  • the configuration message is sent to the terminal device by the network device in advance.
  • the terminal device needs to send the uplink data
  • the terminal device sends the scheduling to the network device on the first resource indicated by the first resource configuration information in the configuration message.
  • the request informs the network device that the terminal device needs to send data, and then directly sends the uplink data without performing a random access procedure, thereby reducing power consumption and delay of the terminal device.
  • the first resource configuration information sent by the network device indicates the enhanced coverage level information, thereby indicating the enhanced coverage level corresponding to the terminal device, that is, the resource indicated by the first resource configuration information can distinguish the coverage level, thereby satisfying the NB- Requirements for terminal equipment of different coverage levels in the IoT system.
  • the network device may be configured in the network device and the terminal device in advance or through the message indicating which NPRACH resources are used as the specific resources, or which NPRACH resources are used as the specific resources according to the rules stipulated in the protocol, or according to the operator. Or the manufacturer-defined rule stipulates which NPRACH resources are used as the specific resources mentioned above, and does not need the network device to notify through the system message of this step.
  • FIG. 4 is a schematic diagram of distribution of NPRACH frequency domain resources in an NB-IoT carrier in the existing NB-IoT system.
  • the complete frequency domain resource set of NPRACH is A
  • each enhanced coverage level corresponds to
  • the frequency domain location of the initial subcarrier allocated to the NPRACH resource is denoted by ⁇ f
  • the number of NB-IoT carriers that NB-IoT can support is m
  • an NPRACH frequency domain in the NB-IoT carrier indicating that the UE supports multi-tone Msg3
  • i B i + C i .
  • E i E i .
  • the frequency domain resource that configures or indicates or appoints the specific resource is A i -D i or E i , it means that in each NB-IoT carrier that can send the scheduling request, the NPRACH frequency domain resource can be allocated.
  • the frequency domain resource outside the frequency domain resource that competes for random access is used as the frequency domain resource of the specific resource.
  • the frequency domain resource of the specific resource may be a subset of the NPRACH frequency domain resource by using different calculations of the foregoing A i , B i , C i , D i , E i , or
  • the above specific resources are resources other than the resources used for contending for random access in the NPRACH resources.
  • the time domain resource of the specific resource may use configuration parameters of the existing NPRACH time domain resource, such as a period, a start time of the transmission, a time offset of the relative period start time, and the like.
  • the network device can notify these parameters via the system message described above. That is, the network device may indicate, in addition to the information such as the carrier frequency and the number of carriers of the NPRACH resource in the system message, the parameter corresponding to the specific resource that sends the scheduling request.
  • the method can be applied to the NB-IoT carrier dimension, the sub-carrier dimension, or the NB-IoT carrier dimension and the sub-carrier dimension. And determining, according to the carrier location of the NPRACH resource and the parameter indicated by the system message, a carrier location corresponding to the specific resource, or determining the specific component according to a carrier location of the subset of the NPRACH resource and a parameter indicated by the system message.
  • the carrier location of the resource is determining, according to the carrier location of the NPRACH resource and the parameter indicated by the system message, a carrier location corresponding to the specific resource, or determining the specific component according to a carrier location of the subset of the NPRACH resource and a parameter indicated by the system message.
  • the NB-IoT carrier dimension and the subcarrier dimension are used, and the carrier position corresponding to the specific resource is determined according to the carrier position of the subset of the NPRACH resource and the first preset parameter indicated by the system message, according to the child of the NPRACH resource.
  • the starting subcarrier position of the set and the second preset parameter indicated by the system message determine the starting subcarrier position of the specific resource.
  • the values of the first preset parameters may be the same or different, that is, the same parameters may be used for the carrier and the subcarriers, or different parameters may be used separately.
  • the preset parameter, the first preset parameter, and the second preset parameter indicated by the system message may be an offset parameter for a subset of the NPRACH resource or the NPRACH resource, or may be an NPRACH resource or an NPRACH resource.
  • the preset parameter, the first preset parameter, and the second preset parameter are offset parameters
  • the fifth and sixth cases are taken as an example, specifically:
  • the carrier position of the specific resource is determined according to a carrier position of the NPRACH resource and a first offset parameter, and a starting subcarrier position of the specific resource is determined according to a starting subcarrier position of the NPRACH resource and a first offset parameter.
  • the carrier location of the specific resource is determined according to a carrier location of the subset of NPRACH resources and a first offset parameter, where a starting subcarrier location of the specific resource is based on a starting subcarrier location and a second biasing parameter of a subset of the NPRACH resources determine.
  • the first offset parameter and the second offset parameter are configured by a system message sent by the network device.
  • the preset parameter, the first preset parameter, and the second preset parameter are scale factors
  • the fifth and sixth cases are taken as an example, specifically:
  • the carrier location of the specific resource is determined according to a carrier location of the NPRACH resource and a first preset scaling factor, and a starting subcarrier location of the specific resource is determined according to a starting subcarrier location of the NPRACH resource and a second preset scaling factor.
  • the carrier location of the specific resource is determined according to a carrier position of a subset of the NPRACH resources and a first preset scaling factor, where a starting subcarrier location of the specific resource is based on a starting subcarrier location of the subset of NPRACH resources and a second preset
  • the scale factor is determined.
  • the first preset scale factor and the second preset scale factor are sent by the network device to send a system message configuration.
  • F i may be a frequency domain offset relative to A i , B i , C i , D i , E i starting subcarrier, or may be relative A i -B i , A i -C i , A i -D i , the frequency domain offset of the A i -E i starting subcarrier.
  • a i or B i or C i D i or E i, or the proportion of the specific ⁇ i may be configured as a resource of the frequency domain resource, or A i or B i or C i D i or E i, or in proportion ( 1- ⁇ i) above may be configured to a specific resource of frequency domain resource, or a i -B i or a i -C i or a i -D i or a i -E i accounted ⁇ i may be configured to the specific
  • the parameters can be bitmaps in addition to offset parameters and scale factors.
  • the offset parameter may be an offset relative to the NB-IoT carrier index.
  • the NB-IoT is configured with m NB-IoT carriers for initiating random access, and the carrier index is 0, 1, ..., m-1, relative
  • the offset may be an offset relative to the NB-IoT carrier index 0, an offset relative to the NB-IoT carrier index 1, and the like.
  • the carrier index I I is an integer, 0 ⁇ I ⁇ m-1, which satisfies or The NB-IoT carrier is used to send a scheduling request.
  • I is a positive integer, 1 ⁇ I ⁇ m-1, satisfied or The NB-IoT carrier is used to send a scheduling request.
  • bitmap is represented by a bitmap of length m.
  • the bits in the bitmap correspond one-to-one with the NB-IoT carrier index, the low-bit indicates the smallest index number, or the high-bit indicates the smallest index number, or is arranged according to other preset rules. This application does not impose any specific restrictions. Both the network device and the terminal device use the same preset arrangement rule.
  • the bit position 0 in the bitmap indicates that the NB-IoT carrier is configured as the frequency domain resource of the specific resource or the bit position 1 indicates that the corresponding NB-IoT carrier is configured as the frequency domain resource of the specific resource, and the number of bits 0 or 1 indicates the configuration.
  • the number of NB-IoT carriers for the above specific resources are examples of the bits 0 or 1 indicates the configuration.
  • a 16-bit bitmap can be used to configure or indicate the frequency domain resources of the specific resource.
  • the bit position 1 in the bitmap indicates that the corresponding NB-IoT carrier is configured as the frequency of the specific resource.
  • the domain resource, the low bit is located in the smallest index number, and the bitmap 1100100010100001 indicates that there are 6 NB-IoT carriers configured as the frequency domain resources of the specific resource.
  • the first offset parameter indicated in the system message of the network device that is, the offset parameter of the NB-IoT carrier dimension
  • the second offset parameter indicated in the system message of the network device that is, the offset of the subcarrier dimension
  • the parameter is F 2 .
  • F 1 represents that the carrier position of the specific resource is obtained by offsetting F 1 NB-IoT carriers on the NB-IoT carrier whose index of the NPRACH resource is 0, and F 2 represents that the starting subcarrier position of the specific resource is The starting subcarrier position in A i of the NPRACH resource is offset by F 2 subcarriers.
  • the carrier index calculated according to F1 and the subcarrier index calculated according to F2 may be sent to the terminal device.
  • the time domain resource of the specific resource may be represented by introducing a bitmap on the NPRACH time domain resource, for example, the bit size in the bitmap may be used to represent symbol granularity, slot granularity, and subframe granularity. Or NPRACH period granularity, etc., bit 1 indicates a corresponding symbol, time slot, subframe, or NPRACH period as a time domain resource of the specific resource, and bit 0 indicates that the corresponding symbol, time slot, subframe, or NPRACH period is not used as the above.
  • the time domain resource of a specific resource is just an example here, and the meaning of the bit 0 or 1 may also be opposite to the above example.
  • the network device directly indicates, by using the foregoing system message, a resource set that can be the first resource, and does not depend on the NPRACH resource, and the network device can indicate the configuration parameter of the first resource in the system message, including the number of carriers, the number of subcarriers, and the starting subcarrier. Frequency domain location, etc.
  • the network device can flexibly indicate a resource set that can be used as the first resource, and does not need to reuse the existing NPRACH resource, so that resource allocation can be performed more flexibly.
  • one or a combination of the foregoing modes may be selected to perform the first resource configuration, and the determined specific resource may be an NPRACH resource. Or, is a subset of the NPRACH resources, or is a resource other than the resource used for contending random access in the NPRACH resource, or is a resource other than the resource used for contending random access in the NPRACH resource. A subset, or a resource other than the NPRACH resource.
  • the following describes a method in which a terminal device notifies a network device of an amount of uplink data.
  • the terminal device sends a scheduling request to the network device on the first resource to request the network device to allocate the uplink channel resource.
  • the terminal device also needs to inform the network device of the size of the uplink data that needs to be transmitted, so that the network device allocates a reasonable uplink channel resource according to the information.
  • the terminal device may send a message for notifying the uplink data size to the network device after step S304.
  • the terminal device may implicitly carry the information about the uplink data amount when the scheduling request is sent in step S304, and the network device determines the data volume information of the uplink data to be transmitted according to the scheduling request.
  • the second mode can save the process that the terminal device specifically reports the uplink data amount to the network device, thereby saving wireless transmission resources. The following mainly describes the specific implementation process of the second mode.
  • the terminal device In the second mode, the terminal device carries the data volume information of the uplink data to be transmitted when the scheduling request is sent to the network device, and the network device determines the data volume information of the uplink data to be transmitted according to the scheduling request.
  • the terminal device carries the data volume information of the uplink data to be transmitted when the scheduling request is sent to the network device by using the first resource, and the network device determines the data volume information of the uplink data to be transmitted according to the first resource corresponding to the received scheduling request.
  • the first resource includes a time domain resource, a frequency domain resource, a code resource, or a combination of a time domain resource, a frequency domain resource, and a code resource.
  • the combination of the time domain resource, the frequency domain resource, the code resource or the time domain resource, the frequency domain resource, and the code resource has a preset correspondence relationship with the data volume information of the uplink data to be transmitted.
  • the time domain resource corresponding to the first resource may be corresponding to a time, a frequency domain location corresponding to the frequency domain resource, an orthogonal code corresponding to the code resource, or a combination thereof and data of the uplink data to be transmitted.
  • the amount information corresponds.
  • the terminal device determines to send according to the coverage level information indicated in the first resource configuration message.
  • the period during which the scheduling request is sent and the starting time, the period in which the terminal device sends the scheduling request is an odd period or an even period indicating the amount of information to be transmitted.
  • the first resource configuration message includes a plurality of carrier indexes, and the initial subcarrier position or index when the terminal device sends the scheduling request has a preset correspondence relationship with the data amount information of the uplink data to be transmitted.
  • the first resource configuration message includes multiple initial subcarrier indexes, and the initial subcarrier position or index when the terminal device sends the scheduling request has a preset correspondence relationship with the data amount information of the uplink data to be transmitted;
  • the first resource configuration message includes multiple carrier indexes and multiple starting subcarrier indexes, and the carrier location and the starting subcarrier position when the terminal device sends the scheduling request and the amount of data information of the uplink data to be transmitted have a pre- Set the correspondence;
  • the first resource configuration message includes multiple carrier indexes and multiple starting subcarrier indexes, and the carrier index and the starting subcarrier index when the terminal device sends the scheduling request and the amount of data of the uplink data to be transmitted have a pre- Set the correspondence.
  • the first resource configuration message includes multiple orthogonal codes, and the orthogonal code or the orthogonal code index when the terminal device sends the scheduling request has a preset correspondence relationship with the data amount information of the uplink data to be transmitted.
  • the signal that the terminal device sends the scheduling request may be a preamble of the NPRACH.
  • FIG. 5 is a schematic diagram of a preamble of NB-IoT random access.
  • the NB-IoT random access preamble is composed of a symbol group of a single subcarrier frequency hopping.
  • the preamble can be repeated multiple times according to the number of repetitions of the network configuration.
  • the frequency domain hopping of the NPRACH preamble ranges from 12 subcarriers.
  • the signal that the terminal device sends the scheduling request may be a preamble of the NPRACH or a new sequence similar to the NPRACH preamble structure, that is, the sequence is also composed of a symbol group hopped by a single subcarrier.
  • the frequency domain frequency hopping of the sequence is in the range of 12 subcarriers.
  • the sequence of the scheduling request sent by the terminal device may be a preamble sequence in the NB-IoT random access, and the terminal device has performed Timing Advance (TA) adjustment before sending the scheduling request.
  • TA Timing Advance
  • the scheduling request when the terminal device sends the scheduling request by using the preamble sequence in the NB-IoT random access on the first resource, the scheduling request may be delayed or sent in advance on the first resource, and the delay time corresponding to the sent scheduling request is sent. Quantity or advance The amount of time has a preset correspondence relationship with the data amount information of the uplink data to be transmitted, and the network device determines the uplink data to be transmitted according to the time amount of the delay corresponding to the scheduling request received on the first resource or the amount of time advanced. Data volume information.
  • FIG. 6 is an example diagram of delaying transmission of a preamble sequence in NB-IoT random access to indicate transmission of data information.
  • the terminal device may delay by 0 symbol duration, respectively.
  • 4 symbol durations, 1/2 symbol durations, and 3/4 symbol durations transmit a preamble sequence to represent a range of data amounts of uplink data to be transmitted, respectively, where the symbol duration and the duration of one symbol in the NPRACH preamble
  • the network device may determine that the uplink data that the terminal device needs to send is within a range of more than 10 bytes and less than or equal to 12 bytes, then the network device may be The terminal device allocates uplink channel resources corresponding to data larger than 10 bytes and less than or equal to 12 bytes.
  • FIG. 7 is an interaction flowchart of the second embodiment of the resource scheduling method provided by the present application.
  • the application scenario of the embodiment is that when the network device schedules uplink transmission, the terminal device has uplink data, as shown in FIG.
  • One implementation process is:
  • the terminal device receives a downlink control information (Downlink Control Information, DCI) indication sent by the network device.
  • DCI Downlink Control Information
  • the DCI is used to indicate a first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission, and the first resource is used by the terminal device to send a scheduling request.
  • the uplink physical channel in the NB-IoT system has NPRACH and NPUSCH, wherein the NPUSCH includes NPUSCH format1 and NPUSCH format2, and NPUSCH format1 is used for uplink data transmission, and NPUSCH format2 is used for carrying downlink HARQ-ACK feedback information.
  • the first resource uses an NPUSCH format2 resource.
  • the terminal device determines the first resource according to the DCI.
  • This step is an optional step.
  • the terminal device When the terminal device has uplink data, the terminal device sends a scheduling request to the network device on the first resource indicated by the DCI.
  • the network device receives and detects the scheduling request sent by the terminal device on the first resource, and the network device allocates the uplink channel resource to the terminal device, as long as the network device detects the scheduling request sent by the terminal device on the first resource; otherwise, the network device allocates the uplink channel resource to the terminal device;
  • the network device only performs the corresponding HARQ operation based on the detected HARQ-ACK feedback information. Work.
  • the terminal device sends a scheduling request to the network device on the first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission, that is, the terminal device can use the NPUSCH format2 to send a scheduling request, thereby saving special use.
  • the resource for scheduling requests is a time-frequency resource used for NPUSCH format2 transmission, that is, the terminal device can use the NPUSCH format2 to send a scheduling request, thereby saving special use.
  • this embodiment relates to a specific method for a terminal device to send a scheduling request by using an NPUSCH format2 resource.
  • the terminal device may transmit the foregoing scheduling request and the HARQ-ACK feedback information on the first resource simultaneously by high-order modulation.
  • HARQ-ACK feedback information ACK is a positive response and NACK is a negative response.
  • the terminal device may perform Quadrature Phase Shift Keying (QPSK) modulation according to the information to be sent. For example, modulation to 00 indicates that only ACK is sent, and modulation to 01 indicates that both the ACK and the scheduling request are sent. A modulation of 11 means that only NACK is transmitted, and a modulation of 10 means that both a NACK is sent and a scheduling request is sent.
  • QPSK Quadrature Phase Shift Keying
  • the terminal device may also perform phase rotation on the modulation symbol corresponding to the HARQ-ACK feedback message to simultaneously transmit the scheduling request and the HARQ-ACK feedback information on the first resource.
  • the modulation symbol constellation point of the HARQ-ACK feedback information may be added with ⁇ /2 phase rotation to indicate that both the ACK and the scheduling request are sent, and the NACK modulation symbol constellation point plus ⁇ /2 phase rotation indicates that both the NACK and the scheduling are sent. request.
  • the terminal device may also transmit the scheduling request and the HARQ-ACK on the first resource by multiplying the modulation symbol or the coding bit corresponding to the HARQ-ACK feedback information by the preset orthogonal code. Feedback.
  • the HARQ-ACK feedback information in the NB-IoT is encoded as a 16-length codeword, and the ACK information bit 1 is encoded into 16 1, NACK information bits 0, and encoded as 16 zeros.
  • the ACK coded bit is multiplied by a subsequence of a length of 16 Hadamard sequence, such as ⁇ 1, -1, 1, -1, 1, -1, 1, -1, 1, -1, 1, -1, 1, -1, 1, -1 ⁇ . That is, if the network device receives 16 codes, it means that only ACK is transmitted; if the network device receives 16 codes, it means that only NACK is transmitted. If the network detects the orthogonal code sequence ⁇ 1, -1,1,-1,1,-1,1,-1,1,-1,1,-1,1,-1,1,-1,1,-1 ⁇ means that a transmission ACK and a scheduling request are detected.
  • the terminal device may further carry data volume information of the uplink data to be transmitted when the scheduling request is transmitted by using the foregoing manners.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the constellation points of the high-order modulation, and the data volume information of the uplink data to be transmitted may be determined according to the constellation points of the high-order modulation.
  • the amount of data transmitted in the uplink is as shown in Table 2.
  • the modulation into 00 indicates that only ACK is transmitted
  • the modulation at 01 indicates the range of transmission data corresponding to the transmission ACK and the index value 0
  • the modulation to 11 indicates that only the NACK is transmitted.
  • the modulation is 10 to indicate the transmission NACK and the transmission data amount range corresponding to the index value 1.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the phase rotation size, and the data volume information of the uplink data to be transmitted may be determined according to the phase rotation size.
  • the data amount range of the data may be represented by a modulation symbol constellation point of the HARQ-NAC feedback information plus a ⁇ /2 phase rotation indicating a data amount range of the uplink data to be transmitted corresponding to the transmission NACK and the index value 1 or the index value.
  • the preset orthogonal code is a Hadamard sequence of length 16.
  • the data volume information of the uplink data to be transmitted has a preset correspondence relationship with the preset orthogonal code sequence, and the data volume information of the uplink data to be transmitted may be determined according to the preset orthogonal code.
  • a Hadamard sequence of length 16 is shown in Table 4.
  • the ACK or NACK can be multiplied by a 16-length Hadamard sequence to indicate the data amount range of the uplink data to be transmitted.
  • FIG. 8 is a block diagram of a first embodiment of a terminal device according to the present application. As shown in FIG. 8, the terminal device includes:
  • the receiving module 801 is configured to receive a configuration message sent by the network device.
  • the processing module 802 is configured to obtain, according to the configuration information received by the receiving module 801, first resource configuration information for sending a scheduling request, where the first resource configuration information includes information for indicating an enhanced coverage level.
  • the sending module 803 is configured to send, to the network device, a scheduling request, where the scheduling request is used to request an uplink channel resource from the network device, where the terminal device sends the scheduling, on the first resource indicated by the first resource configuration information acquired by the processing module 802.
  • the random access procedure is not performed when requested.
  • the terminal device is used to implement the functions of the terminal device in the first embodiment of the foregoing method, and the implementation principle and technical effects are similar, and details are not described herein again.
  • the receiving module 801 is further configured to: receive a system message sent by the network device.
  • the processing module 802 is further configured to: obtain configuration information of the NPRACH resource according to the system message.
  • the NPRACH resource is a resource set of the first resource, or the subset of the NPRACH resource is a resource set of the first resource, or the resource other than the resource used for contending random access in the NPRACH resource is the resource of the first resource.
  • the set, or a subset of the resources of the NPRACH resource other than the resources used to contend random access, is the resource set of the first resource.
  • system message carries the first preset parameter and the second preset parameter.
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the NPRACH resource and the first preset parameter, and the starting subcarrier position of the resource set of the first resource is based on the initial subcarrier position of the NPRACH resource and the second preset parameter. determine;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of the NPRACH resource and the first preset parameter, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the subset of the NPRACH resource And determining with the second preset parameter.
  • system message carries a first offset parameter and a second offset parameter.
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the NPRACH resource and the first offset parameter, and the starting subcarrier position of the resource set of the first resource is based on the starting subcarrier position and the second offset parameter of the NPRACH resource. determine;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of NPRACH resources and the first offset parameter, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the subset of NPRACH resources And the second bias parameter is determined.
  • system message carries a first preset scale factor and a second preset scale factor.
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the NPRACH resource and the first preset scaling factor, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the NPRACH resource and the second preset Scale factor determination;
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the subset of the NPRACH resource and the first preset scaling factor, and the starting subcarrier position of the resource set of the first resource is based on the starting subcarrier of the subset of the NPRACH resource
  • the position is determined by a second preset scale factor.
  • the sending module 803 is further configured to:
  • the data amount information of the uplink data to be transmitted is carried when the scheduling request is sent to the network device.
  • sending module 803 is specifically configured to:
  • the first resource includes a time domain resource, a frequency domain resource, a code resource, or a combination of a time domain resource, a frequency domain resource, and a code resource when the scheduling request is sent to the network device by using the first resource.
  • the combination of the time domain resource, the frequency domain resource, the code resource or the time domain resource, the frequency domain resource, and the code resource has a preset correspondence relationship with the data volume information of the uplink data to be transmitted.
  • the signal that the terminal device sends the scheduling request is a preamble in the NPRACH, and the terminal device performs the TA adjustment before sending the scheduling request.
  • FIG. 9 is a block diagram of a first embodiment of a network device according to the present application. As shown in FIG. 9, the network device includes:
  • the sending module 901 is configured to send, to the terminal device, a configuration message, where the configuration message is used by the terminal device to acquire first resource configuration information for sending a scheduling request, where the first resource configuration information includes information for indicating an enhanced coverage level.
  • the receiving module 902 is configured to receive a scheduling request sent by the terminal device on the first resource indicated by the first resource configuration information, where the scheduling request is used to request an uplink channel resource from the network device, and the terminal device does not perform the sending the scheduling request. Random access process.
  • the processing module 903 is configured to allocate an uplink channel resource to the terminal device according to the scheduling request received by the receiving module 902.
  • the network device is used to implement the functions of the network device in the foregoing method embodiment, and the implementation principle and technical effects are similar, and details are not described herein again.
  • the sending module 901 is further configured to: send a system message to the terminal device, where the system message carries configuration information of the NPRACH resource.
  • the NPRACH resource is a resource set of the first resource, or the subset of the NPRACH resource is a resource set of the first resource, or the resource other than the resource used for contending random access in the NPRACH resource is the resource of the first resource.
  • the set, or a subset of the resources of the NPRACH resource other than the resources used to contend random access, is the resource set of the first resource.
  • system message carries the first preset parameter and the second preset parameter.
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the NPRACH resource and the first preset parameter, and the starting subcarrier position of the resource set of the first resource is based on the initial subcarrier position of the NPRACH resource and the second preset parameter. determine;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of the NPRACH resource and the first preset parameter, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the subset of the NPRACH resource And determining with the second preset parameter.
  • system message carries a first offset parameter and a second offset parameter.
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the NPRACH resource and the first offset parameter, and the starting subcarrier position of the resource set of the first resource is based on the starting subcarrier position and the second offset parameter of the NPRACH resource. determine;
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the subset of NPRACH resources and the first offset parameter, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the subset of NPRACH resources And the second bias parameter is determined.
  • system message carries a first preset scale factor and a second preset scale factor.
  • the carrier location of the resource set of the first resource is determined according to the carrier location of the NPRACH resource and the first preset scaling factor, and the starting subcarrier location of the resource set of the first resource is based on the starting subcarrier location of the NPRACH resource and the second preset Scale factor determination;
  • the carrier position of the resource set of the first resource is determined according to the carrier position of the subset of the NPRACH resource and the first preset scaling factor, and the starting subcarrier position of the resource set of the first resource is based on the starting subcarrier of the subset of the NPRACH resource
  • the position is determined by a second preset scale factor.
  • processing module 903 is further configured to:
  • processing module 903 is specifically configured to:
  • the amount of time or the amount of time in advance has a preset correspondence relationship with the amount of data of the uplink data to be transmitted;
  • Resources, frequency domain The combination of the source and the code resources, the combination of the time domain resource, the frequency domain resource, the code resource or the time domain resource, the frequency domain resource, the code resource, and the data amount information of the uplink data to be transmitted have preset correspondence relationship.
  • the signal of the scheduling request received by the network device is a preamble in the NPRACH, and the terminal device performs the TA adjustment before sending the scheduling request.
  • FIG. 10 is a block diagram of a first embodiment of a terminal device according to the present application. As shown in FIG. 10, the terminal device includes:
  • the receiving module 1001 is configured to receive a DCI indication sent by the network device, where the DCI is used to indicate a first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission.
  • the processing module 1002 is configured to determine the first resource according to the DCI.
  • the sending module 1003 is configured to send a scheduling request to the network device on the first resource.
  • the device is used to implement the functions of the terminal device in the foregoing method embodiment 2, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • the sending module 1003 is specifically configured to:
  • the scheduling request and the HARQ-ACK feedback information are simultaneously transmitted on the first resource by high-order modulation.
  • the sending module 1003 is further specifically configured to:
  • the scheduling request and the HARQ-ACK feedback information are transmitted on the first resource by performing phase rotation on the modulation symbol corresponding to the HARQ-ACK feedback message.
  • the sending module 1003 is further specifically configured to:
  • the scheduling request and the HARQ-ACK feedback information are simultaneously transmitted on the first resource by multiplying the modulation symbol or the coded bit corresponding to the HARQ-ACK feedback information by the preset orthogonal code.
  • the preset orthogonal code is a Hadamard sequence of length 16.
  • the sending module 1003 is further configured to:
  • the data amount information of the uplink data to be transmitted is carried when the scheduling request is sent to the network device.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the constellation points of the high-order modulation.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the phase rotation size.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the preset orthogonal code sequence.
  • FIG. 11 is a block diagram of a first embodiment of a network device according to the present application. As shown in FIG. 11, the network device includes:
  • the sending module 1101 is configured to send a DCI indication to the terminal device, where the DCI is used to indicate a first resource, where the first resource is a time-frequency resource used for NPUSCH format2 transmission.
  • the receiving module 1102 is configured to receive a scheduling request sent by the terminal device on the first resource.
  • the processing module 1103 is configured to allocate an uplink channel resource to the terminal device according to the scheduling request.
  • the device is used to implement the functions of the network device in the foregoing method embodiment 2.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource simultaneously by the high-order modulation
  • the processing module 1103 is specifically configured to:
  • Determining whether the terminal device sends a scheduling request according to the received high-order modulated signal Determining whether the terminal device sends a scheduling request according to the received high-order modulated signal.
  • the terminal device performs phase rotation on the modulation symbol corresponding to the HARQ-ACK feedback message to simultaneously transmit the scheduling request and the HARQ-ACK feedback information on the first resource
  • the processing module 1103 is further configured to:
  • the terminal device transmits the scheduling request and the HARQ-ACK feedback information on the first resource by multiplying the modulation symbol or the coding bit corresponding to the HARQ-ACK feedback information by the preset orthogonal code, and the processing module 1103 Specifically also used to:
  • Whether the terminal device sends the scheduling request is determined according to the received modulation symbol multiplied by the preset orthogonal code.
  • the preset orthogonal code is a Hadamard sequence of length 16.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the constellation points of the high-order modulation.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the phase rotation size.
  • the data amount information of the uplink data to be transmitted has a preset correspondence relationship with the preset orthogonal code sequence.
  • FIG. 12 is a physical block diagram of Embodiment 1 of a terminal device according to the present application. As shown in FIG. 12, the terminal device includes:
  • the memory 1201 is configured to store program instructions, and the processor 1202 is configured to invoke program instructions in the memory 1201 to implement the functions of a terminal device in the foregoing method embodiment.
  • FIG. 13 is a physical block diagram of Embodiment 1 of a network device according to the present application. As shown in FIG. 13, the network device includes:
  • the memory 1301 is configured to store program instructions, and the processor 1302 is configured to invoke program instructions in the memory 1301 to implement the functions of a network device in the foregoing method embodiment.
  • FIG. 14 is a physical block diagram of another embodiment of a terminal device according to the present application. As shown in FIG. 14, the terminal device includes:
  • the memory 1201 is configured to store program instructions, and the processor 1202 is configured to invoke program instructions in the memory 1201 to implement the functions of the terminal device in the second embodiment of the foregoing method.
  • FIG. 15 is a physical block diagram of another embodiment of a network device according to the present application. As shown in FIG. 15, the network device includes:
  • the memory 1501 is configured to store program instructions, and the processor 1502 is configured to invoke program instructions in the memory 1501 to implement the functions of the network device in the second embodiment of the foregoing method.

Landscapes

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

Abstract

本发明实施例提供一种资源调度方法、终端设备及网络设备，该方法中，终端设备在接收网络设备的配置消息后，根据配置消息获取用于发送调度请求的第一资源配置信息，该第一资源配置信息中包括用于指示增强覆盖等级的信息，进而，终端设备在该第一资源配置信息所指示的第一资源上向网络设备发送调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送所述调度请求时不执行随机接入过程。该方法中，终端设备在配置消息中的第一资源配置信息所指示的第一资源上向网络设备发送调度请求，即告知网络设备终端设备需要发送数据，进而直接发送上行数据，而不需要执行随机接入过程，从而减少终端设备的功耗和时延。

Description

资源调度方法、终端设备及网络设备 技术领域
本申请涉及通信技术，尤其涉及一种资源调度方法、终端设备及网络设备。
背景技术
物联网(IoT，Internet of things)是“物物相连的互联网”。它将互联网的用户端扩展到了任何物品与物品之间，进行信息交换和通信。IoT具有覆盖增强、支持大量低速率设备、非常低的成本以及低能量消耗等特殊需求。窄带物联网(Narrowband Internet of Things，NB-IoT)系统通过提供一系列方法来满足IoT的这些特殊需求。
现有技术中，在NB-IoT系统中，当终端设备需要向网络设备发送上行数据时，需要重新发起随机接入，之后再发送上行数据。
但是，使用现有技术中的方法，终端设备需要等到随机接入过程的第二条消息之后才能发送上行数据，导致终端设备的功耗和时延的增加。
发明内容
本申请提供一种资源调度方法、终端设备及网络设备，用于解决现有技术中请求上行数据过程过长所导致的终端设备功耗及时延增加的问题。
本申请第一方面提供一种资源调度方法，在该方法中，终端设备在接收网络设备的配置消息后，根据配置消息获取用于发送调度请求的第一资源配置信息，该第一资源配置信息中包括用于指示增强覆盖等级的信息，进而，终端设备在该第一资源配置信息所指示的第一资源上向网络设备发送调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送所述调度请求时不执行随机接入过程。
该方法中，由网络设备预先向终端设备发送配置消息，当终端设备有上行数据需要发送时，终端设备在配置消息中的第一资源配置信息所指示的第一资源上向网络设备发送调度请求，即告知网络设备终端设备需要发送数据，进而直接发送上行数据，而不需要执行随机接入过程，从而减少终端设备的功耗和时延。
进而，网络设备发送的第一资源配置信息中指示了增强覆盖等级信息，从而指示了终端设备对应的增强覆盖等级，即，第一资源配置信息所指示的资源可以区分覆盖等级，从而满足NB-IoT系统中不同覆盖等级的终端设备的要求。
在一种可选方式中，所述终端设备接收网络设备发送的配置消息之前，还包括：
所述终端设备接收所述网络设备发送的系统消息；
所述终端设备根据所述系统消息获取NPRACH资源的配置信息；
其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
在一种可选方式中，终端设备在向网络设备发送调度请求时还携带待传输的上行数据 的数据量信息。
在一种可选方式中，终端设备在所述第一资源上延时或提前向所述网络设备发送调度请求，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；或者，
所述终端设备通过所述第一资源向所述网络设备发送调度请求时携带所述待传输的上行数据的数据量信息，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
在一种可选方式中，终端设备发送调度请求的信号为NPRACH中的前导码，终端设备发送调度请求前执行过时间提前TA调整。
本申请第二方面提供一种资源调度方法，该方法中，网络设备首先向终端设备发送配置消息，该配置消息用于终端设备获取用于发送调度请求的第一资源配置信息，该第一资源配置信息中包括用于指示增强覆盖等级的信息。进而，网络设备接收终端设备在第一资源配置信息所指示的第一资源上发送的调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送该调度请求时不执行随机接入过程。进而，网络设备根据调度请求向终端设备分配上行信道资源。
在一种可选方式中，所述网络设备向终端设备发送配置消息之前，还包括：
所述网络设备向所述终端设备发送系统消息，所述系统消息中携带NPRACH资源的配置信息；
其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
在一种可选方式中，网络设备可以根据终端设备发送的调度请求确定待传输的上行数据的数据量信息。
在一种可选方式中，所述网络设备根据在所述第一资源上所接收的所述调度请求对应的延时的时间量或提前的时间量确定所述待传输的上行数据的数据量信息，其中，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；
或者，
所述网络设备根据所接收的所述调度请求对应的所述第一资源确定所述待传输的上行数据的数据量信息，其中，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
在一种可选方式中，网络设备接收的调度请求的信号为NPRACH中的前导码，终端设备发送调度请求前执行过时间提前TA调整。
在一种可选方式中，所述系统消息中携带第一预设参数和第二预设参数；
所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起 始子载波位置与所述第二预设参数确定；
或者，
所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
在一种可选方式中，所述系统消息中携带第一偏置参数和第二偏置参数；
所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置和所述第二偏置参数确定；
或者，
所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置和所述第二偏置参数确定。
在一种可选方式中，所述系统消息中携带第一预设比例因子和第二预设比例因子；
所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设比例因子确定；
或者，
所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设比例因子确定。
本申请第三方面提供一种资源调度方法，在该方法中，终端设备接收网络设备发送的下行控制信息DCI指示，所述DCI用于指示第一资源，所述第一资源为用于NPUSCHformat2传输的时频资源，进而，终端设备根据DCI确定所述第一资源，进而，终端设备在所述第一资源上向所述网络设备发送调度请求。
该方法中，终端设备在第一资源上向网络设备发送调度请求，该第一资源为用于NPUSCH format2传输的时频资源，即终端设备可以利用NPUSCH format2来发送调度请求，从而节省专门用于调度请求的资源。
在一种可选方式中，所述终端设备在所述第一资源上向所述网络设备发送调度请求，包括：
所述终端设备通过高阶调制将所述调度请求与HARQ-ACK反馈信息同时在所述第一资源上传输。
在一种可选方式中，所述终端设备通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转同时在所述第一资源上传输所述调度请求以及HARQ-ACK反馈信息。
在一种可选方式中，所述终端设备通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在所述第一资源上传输所述调度请求以及HARQ-ACK反馈信息。
在一种可选方式中，所述预设正交码为长度为16的哈达玛序列。
在一种可选方式中，还包括：
所述终端设备向所述网络设备发送调度请求时携带待传输的上行数据的数据量信息。
在一种可选方式中，所述待传输的上行数据的数据量信息与所述高阶调制的星座点具有预设对应关系。
在一种可选方式中，所述待传输的上行数据的数据量信息与所述相位旋转大小具有预设对应关系。
在一种可选方式中，所述待传输的上行数据的数据量信息与所述预设正交码序列具有预设对应关系。
本申请第四方面提供一种资源调度方法，该方法中，网络设备首先向终端设备发送DCI指示，该DCI用于指示第一资源，该第一资源为用于NPUSCH format2传输的时频资源。进而，网络设备接收终端设备在第一资源上发送的调度请求，进而，网络设备根据调度请求向终端设备分配上行信道资源。
在一种可选方式中，终端设备通过高阶调制将调度请求与HARQ-ACK反馈信息同时在第一资源上传输，网络设备根据接收到的高阶调制后的信号确定终端设备是否发送了调度请求。
在一种可选方式中，终端设备通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息，网络设备根据接收到的进行相位旋转的调制符号确定终端设备是否发送了调度请求。
在一种可选方式中，终端设备通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息，网络设备根据接收到的乘以预设正交码之后的调制符号确定终端设备是否发送了调度请求。
在一种可选方式中，上述预设正交码为长度为16的哈达玛序列。
在一种可选方式中，网络设备根据终端设备发送的调度请求确定待传输的上行数据的数据量信息。
在一种可选方式中，上述待传输的上行数据的数据量信息与高阶调制的星座点具有预设对应关系。
在一种可选方式中，上述待传输的上行数据的数据量信息与相位旋转大小具有预设对应关系。
在一种可选方式中，上述待传输的上行数据的数据量信息与所述预设正交码序列具有预设对应关系。
本申请第五方面提供一种终端设备，该终端设备具有实现第一方面中终端设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该终端设备可以包括接收模块、处理模块以及发送模块，这些模块可以执行上述方法中的相应功能，例如：接收模块，用于接收网络设备发送的配置消息；处理模块，用于根据接收模块接收的配置信息获取用于发送调度请求的第一资源配置信息，该第一资源配置信息中包括用于指示增强覆盖等级的信息；发送模块，用于在处理模块获取的第一资源配置信息所指示的第一资源上向网络设备发送调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送该调度请求时不执行随机接入过程。
本申请第六方面提供一种网络设备，该网络设备具有实现第二方面中网络设备的功 能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该网络设备可以包括发送模块、接收模块以及处理模块，这些模块可以执行上述方法中的相应功能，例如：发送模块，用于向终端设备发送配置消息，该配置消息用于终端设备获取用于发送调度请求的第一资源配置信息，第一资源配置信息中包括用于指示增强覆盖等级的信息；接收模块，用于接收终端设备在第一资源配置信息所指示的第一资源上发送的调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送该调度请求时不执行随机接入过程；处理模块，用于根据接收模块接收的调度请求向终端设备分配上行信道资源。
本申请第七方面提供一种终端设备，该终端设备具有实现第三方面中终端设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该终端设备可以包括接收模块、处理模块以及发送模块，这些模块可以执行上述方法中的相应功能，例如：接收模块，用于接收网络设备发送的DCI指示，该DCI用于指示第一资源，第一资源为用于NPUSCH format2传输的时频资源；处理模块，用于根据DCI确定第一资源；发送模块，用于在第一资源上向网络设备发送调度请求。
本申请第八方面提供一种网络设备，该网络设备具有实现第四方面中网络设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该网络设备可以包括发送模块、接收模块以及处理模块，这些模块可以执行上述方法中的相应功能，例如：发送模块，用于向终端设备发送DCI指示，该DCI用于指示第一资源，该第一资源为用于NPUSCH format2传输的时频资源；接收模块，用于接收终端设备在第一资源上发送的调度请求；处理模块，用于根据调度请求向终端设备分配上行信道资源。
本申请第九方面提供一种终端设备，该终端设备包括存储器以及处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，实现上述第一方面及其各实施方式中的方法。
本申请第十方面提供一种网络设备，该网络设备包括存储器以及处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，实现上述第二方面及其各实施方式中的方法。
本申请第十一方面提供一种终端设备，该终端设备包括存储器以及处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，实现上述第三方面及其各实施方式中的方法。
本申请第十二方面提供一种网络设备，该网络设备包括存储器以及处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，实现上述第四方面及其各实施方式中的方法。
附图说明
图1为现有NB-IoT系统中终端设备需要向网络设备发送上行数据时的处理过程的一个示例；
图2为本申请提供的资源调度方法的系统架构图；
图3为本申请提供的资源调度方法实施例一的交互流程图；
图4为现有NB-IoT系统中一个NB-IoT载波内NPRACH频域资源的分布示意图；
图5为NB-IoT随机接入的前导码示意图；
图6为延时发送NB-IoT随机接入中的前导码序列来表示传输数据信息的示例图；
图7为本申请提供的资源调度方法实施例二的交互流程图；
图8为本申请提供的一种终端设备实施例一的模块结构图；
图9为本申请提供的一种网络设备实施例一的模块结构图；
图10为本申请提供的另一种终端设备实施例一的模块结构图；
图11为本申请提供的另一种网络设备实施例一的模块结构图；
图12为本申请提供的一种终端设备实施例一的实体框图；
图13为本申请提供的一种网络设备实施例一的实体框图；
图14为本申请提供的另一种终端设备实施例一的实体框图；
图15为本申请提供的另一种网络设备实施例一的实体框图。
具体实施方式
应当理解，本文中使用的术语“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在各种通信系统中，为避免资源浪费，如果终端设备没有上行数据需要传输，网络设备就不会为该终端设备分配上行资源。当终端设备有上行资源需要传输时，首先应该告知网络设备终端设备需要传输上行资源，请求网络设备为该终端设备分配上行资源。
在现有的NB-IoT系统中，当终端设备需要向网络设备发送上行数据时，需要重新发起随机接入，之后再发送上行数据。图1为现有NB-IoT系统中终端设备需要向网络设备发送上行数据时的处理过程的一个示例，如图1所示，当终端设备接收到上行数据之后，重新发起随机接入，具体过程包括：
S101、终端设备向网络设备发送接入前导码。
S102、网络设备向终端设备返回随机接入响应。
S103、终端设备接收到响应之后再向网络设备发起无线资源控制(Radio Resource Control，RRC)请求。
S104、网络设备向终端设备发送RRC连接建立消息。
S105、终端设备网络设备发送RRC连接建立完成消息。
S106、终端设备向网络设备发送上行数据。
其中，终端设备至少需要在S103之后才能向网络设备上报上行数据的大小，以及向网络设备发送上行数据。
即，现有技术中，终端设备需要等待较长时间、执行较多操作后才能发送上行数据， 这会增加终端设备的功耗和时延。并且，当有多个终端设备发生接入冲突时，终端设备可能会发生退避甚至失败，进一步加剧终端设备的功耗和时延。
本申请基于上述问题，提出一种资源调度方法，由网络设备预先向终端设备发送配置信息，当终端设备有上行数据需要发送时，终端设备在配置信息所指示的特定资源上向网络设备发送调度请求，即告知网络设备终端设备需要发送数据，进而直接发送上行数据，而不需要执行随机接入过程，从而减少终端设备的功耗和时延。
并且，网络设备发送的配置信息中包括增强覆盖等级索引或重复次数等信息，直接或间接指示了终端设备对应的增强覆盖等级，即，配置信息所指示的资源可以区分覆盖等级，从而满足NB-IoT系统对于覆盖等级的要求。
图2为本申请提供的资源调度方法的系统架构图，如图2所示，在NB-IoT系统中，网络设备可以同多个终端设备进行通信，网络设备可以为基站，终端设备例如可以为手机、打印机等任意的进行机器类通信的终端设备。本申请所提供的方法，对于任意的终端设备都适用。
图3为本申请提供的资源调度方法实施例一的交互流程图，如图3所示，该方法的一种执行过程为：
S301、网络设备发送系统消息。
网络设备可以通过系统消息向服务小区内的所有终端设备通知可用的资源集合的配置参数，该资源集合用于终端设备向网络设备发送调度请求。例如该资源集合可以是上行随机接入信道(Narrowband Physical Random Access CHannel，NPRACH)资源、NPRACH资源子集、上行数据信道(Narrowband Physical Uplink Shared CHannel，NPUSCH)format1资源、NPUSCH format1资源子集、NPUSCH format2资源或者NPUSCH format2资源子集。例如，当该资源集合为NPRACH资源时，网络设备可以在系统消息中指示NPRACH资源的载波频点，载波数，子载波数，起始子载波频域位置，增强覆盖等级索引、重复次数，周期，起始时刻，前导码格式，前导码传输最大尝试次数等配置信息。其中，增强覆盖等级索引或重复次数可用于表示资源对应的增强覆盖等级。
如前所述，本申请通过在特定资源上发送调度请求并且不执行随机接入过程来减少终端设备的功耗及时延，基于NB-IoT系统的覆盖增强的特点，该特定资源需要区分覆盖等级，而上述的NPRACH资源是可以区分覆盖等级的，因此，作为一种可选的实施方式，本申请中用于发送调度请求的特定资源可以使用NPRACH资源，继承NPRACH资源可以区分覆盖等级的特点，以有效平衡资源和性能；而且NPRACH和上行数据之间有冲突解决机制，即NPRACH与上行数据冲突时，上行数据会推迟发送，使用NPRACH资源作为发送调度请求的特定资源，可以继承上述冲突机制，避免对网络设备的调度施加额外的限制，可以很好保持后向兼容。使用NPRACH资源前需要确定具体使用NPRACH资源中的哪些载波和哪些子载波，其中，可以根据当前NPRACH资源的配置来直接使用NPRACH资源中的一部分载波和子载波，或者，也可以根据一定的参数来计算出需要使用NPRACH资源中的哪些载波和子载波。另外，该特定资源也可以使用NPRACH资源外的其他资源。
因此，可选地，本申请中对于用于发送调度请求的特定资源可以通过以下三种方式来确定：
第一种方式：
根据当前NPRACH资源的配置直接确定将NPRACH资源的哪些资源作为上述特定资源。
在这种方式中，可以预先在网络设备以及终端设备中配置或通过消息指示使用哪些NPRACH资源为上述特定资源，或者按照协议中制定的规则约定使用哪些NPRACH资源为上述特定资源，或者按照运营商或厂家自定义的规则约定使用哪些NPRACH资源为上述特定资源，不需要网络设备通过本步骤的系统消息来通知。
第二种方式：
设置一些参数，根据当前NPRACH资源集合和这些参数，确定将NPRACH资源的哪些资源作为上述特定资源。
在这种方式中，网络设备可以通过上述系统消息通知这些参数。即，网络设备除了在系统消息中指示NPRACH资源的载波频点，载波数等信息外，还可以指示确定发送调度请求的特定资源所对应的这些参数。
第三种方式：
网络设备直接通过上述系统消息指示可作为上述特定资源的资源集合，而不依赖NPRACH资源集合，网络设备可以在系统消息中指示上述特定资源的配置参数，包括载波位置、载波数、子载波数、起始子载波频域位置、调度请求最大传输次数等。
由于网络设备直接通过系统消息指示上述特定资源的配置参数，因此这种方式所确定出的资源也可能是NPRACH资源，也可能是NPRACH资源之外的资源。
上述三种方式的具体实现方法将在本实施例之后进行具体描述。
S302、网络设备向终端设备发送配置消息。
其中，该配置消息用于指示终端设备用于发送调度请求的第一资源配置信息。
S303、终端设备根据上述配置消息，获取用于发送调度请求的第一资源配置信息。
当终端设备接收到上述配置消息后，获取其中携带的第一资源配置信息，第一资源配置信息中可以包括载波索引，起始子载波索引，调度请求最大传输次数，以及用于指示增强覆盖等级的信息等，其中，用于指示增强覆盖等级的信息具体可以为增强覆盖等级索引或重复次数。
以步骤S301中所描述的三种方式中的第一种方式为例，用于发送调度请求的特定资源直接使用NPRACH资源，则首先，在S301的系统消息中，网络设备会向服务小区内所有的终端设备广播NPRACH资源集合，包括载波数、子载波数、起始子载波频域位置以及重复次数等。各终端设备接收到系统消息后，就获知了NPRACH资源集合的配置信息。进而，网络设备根据预先配置的上述特定资源的配置信息，确定一个特定终端设备发送上述调度请求所对应的特定资源，并通过载波索引、起始子载波索引、起始子载波频域位置等信息通知该特定的终端设备使用哪些载波中的哪些子载波来发送调度请求。
其中，NPRACH资源可以区分覆盖等级，网络设备的系统消息所指示的NPRACH资源集合中的每一组NPRACH资源对应一种增强覆盖等级，网络设备根据终端设备的增强覆盖等级，以及预先配置的配置信息，在NPRACH资源集合内为终端设备分配满足其覆盖要求的资源。
在一种可选的实施方式中，网络设备具体可以通过竞争随机接入过程中的RRC消息来发送上述第一资源配置信息，具体为竞争随机接入过程中得到第四条消息。
S304、当上行数据到达时，终端设备在第一资源配置信息所指示的第一资源上向网络设备发送调度请求，同时，终端设备启动定时器，开始对调度请求传输的次数进行计数。
该第一资源即是指前述的发送调度请求的特定资源的子集，即，该特定资源为第一资源的资源集合。
该调度请求用于向网络设备请求上行信道资源，并且，终端设备在发送所述调度请求时不执行随机接入过程。
具体地，终端设备在经过前述步骤所确定的第一资源上发送调度请求，即向网络设备请求上行信道资源，而不需要像现有技术一样通过重新发起随机接入来向网络设备请求上行信道资源。
S305、网络设备在上述第一资源上检测上述终端设备发送的调度请求，如果网络设备检测到调度请求，则根据上述调度请求向终端设备分配上行信道资源，如果网络设备没有检测到调度请求，网络设备不进行传输操作。
S306、如果在定时器未超时时，终端设备接收到网络设备分配的上行信道资源，则终端设备在网络设备分配的上行信道资源上发送缓存状态报告或者上行数据，否则终端设备在上述第一资源上重新传输调度请求。如果调度请求传输的次数超过调度器请求传输的最大传输次数，终端设备触发随机接入过程。
本实施例中，由网络设备预先向终端设备发送配置消息，当终端设备有上行数据需要发送时，终端设备在配置消息中的第一资源配置信息所指示的第一资源上向网络设备发送调度请求，即告知网络设备终端设备需要发送数据，进而直接发送上行数据，而不需要执行随机接入过程，从而减少终端设备的功耗和时延。
进而，网络设备发送的第一资源配置信息中指示了增强覆盖等级信息，从而指示了终端设备对应的增强覆盖等级，即，第一资源配置信息所指示的资源可以区分覆盖等级，从而满足NB-IoT系统中不同覆盖等级的终端设备的要求。
以下具体描述前述的确定用于发送调度请求的上述特定资源的三种方式。
第一种方式：
根据当前NPRACH资源的配置直接确定将NPRACH资源的哪些资源作为上述特定资源。
在这种方式中，可以预先在网络设备以及终端设备中配置或通过消息指示使用哪些NPRACH资源为上述特定资源，或者按照协议中制定的规则约定使用哪些NPRACH资源为上述特定资源，或者按照运营商或厂家自定义的规则约定使用哪些NPRACH资源为上述特定资源，，不需要网络设备通过本步骤的系统消息来通知。
具体地，图4为现有NB-IoT系统中一个NB-IoT载波内NPRACH频域资源的分布示意图，如图4所示，假设NPRACH的频域资源全集为A，每一种增强覆盖等级对应的分配给NPRACH资源的起始子载波的频域位置记为Δf，NB-IoT可以支持的NB-IoT载波数为m，一个NB-IoT载波内的NPRACH频域资源为Ai,i＝0,…,m-1，则有
Figure PCTCN2017078201-appb-000001
一个NB-IoT载波内表示UE支持single-tone Msg3的NPRACH频域资源记为Bi，i＝0,…,m-1， 一个NB-IoT载波内表示UE支持multi-tone Msg3的NPRACH频域资源记为Ci，i＝0,…,m-1，一个NB-IoT载波内表示基于竞争随机接入的NPRACH频域资源记为Di，i＝0,…,m-1，其中Di＝Bi+Ci。一个NB-IoT载波内除了基于竞争随机接入之外的NPRACH频域资源记为Ei，i＝0,…,m-1，则有Di+Ei＝Ai。
预先在网络设备以及终端设备中配置或通过消息指示使用哪些NPRACH频域资源为上述特定资源的频域资源时，或者按照协议中制定的规则约定使用哪些NPRACH频域资源为上述特定资源的频域资源时，或者按照运营商或厂家自定义的规则约定使用哪些NPRACH频域资源为上述特定资源的频域资源时，可以直接指示或约定Ai，Bi，Ci，Di，Ei，Ai-Bi，Ai-Ci，Ai-Di，Ai-Ei来表示上述特定资源的频域资源，其中i＝0,…,m-1或i＝1,…,m-1。例如，配置或指示或约定上述特定资源的频域资源为Ai-Di或者Ei，则代表在每个可发送调度请求的NB-IoT载波中，可以将NPRACH频域资源中除分配用于竞争随机接入的频域资源之外的频域资源作为上述特定资源的频域资源。
在一些可选的实施方式中，可以通过对上述Ai，Bi，Ci，Di，Ei的不同计算，使得上述特定资源的频域资源为NPRACH频域资源的子集，或者，上述特定资源为NPRACH资源中除用于竞争随机接入的资源之外的资源。
另外，在这种方式中，上述特定资源的时域资源可以使用现有NPRACH时域资源的配置参数，例如周期、发送的起始时刻、相对周期起始时刻的时间偏置等。
第二种方式：
设置一些参数，在当前NPRACH资源集合上通过这些参数进行计算，确定出将NPRACH资源的哪些资源作为上述特定资源。
在这种方式中，网络设备可以通过上述系统消息通知这些参数。即，网络设备除了在系统消息中指示NPRACH资源的载波频点，载波数等信息外，还可以指示确定发送调度请求的特定资源所对应的参数。
其中，这种方式可以应用在NB-IoT载波维度，也可以应用在子载波维度，或者同时应用在NB-IoT载波维度以及子载波维度。并且，可以根据NPRACH资源的载波位置与通过系统消息所指示的参数来确定上述特定资源对应的载波位置，也可以根据NPRACH资源的子集的载波位置与通过系统消息所指示的参数来确定上述特定资源的载波位置。
具体可以分为以下几种情况：
1、应用在NB-IoT载波维度，根据NPRACH资源的载波位置与通过系统消息所指示的预设参数来确定上述特定资源对应的载波位置。
2、应用在NB-IoT载波维度，根据NPRACH资源的子集的载波位置与通过系统消息所指示的预设参数来确定上述特定资源对应的载波位置。
3、应用在子载波维度，根据NPRACH资源的起始子载波位置与通过系统消息所指示的预设参数来确定上述特定资源对应的起始子载波位置。
4、应用在子载波维度，根据NPRACH资源的子集的起始子载波位置与通过系统消息所指示的预设参数来确定上述特定对应的起始子载波位置。
5、应用在NB-IoT载波维度以及子载波维度，根据NPRACH资源的载波位置与通过系统消息所指示的第一预设参数来确定上述特定资源对应的载波位置，根据NPRACH资 源的起始子载波位置与通过系统消息所指示的第二预设参数确定上述特定资源的起始子载波位置。
6、应用在NB-IoT载波维度以及子载波维度，根据NPRACH资源的子集的载波位置与通过系统消息所指示的第一预设参数来确定上述特定资源对应的载波位置，根据NPRACH资源的子集的起始子载波位置与通过系统消息所指示的第二预设参数确定上述特定资源的起始子载波位置。
在上述第5种以及第6中情况中，第一预设参数的值可以相同，也可以不同，即可以对载波以及子载波使用相同的参数，也可以分别使用不同的参数。
上述通过系统消息所指示的预设参数、第一预设参数以及第二预设参数具体可以为针对NPRACH资源或NPRACH资源的子集的偏置参数，或者，也可以为针对NPRACH资源或NPRACH资源的子集的比例因子等。
当预设参数、第一预设参数以及第二预设参数为偏置参数时，以上述第5及第6种情况为例，具体为：
上述特定资源的载波位置根据NPRACH资源的载波位置和第一偏置参数确定，上述特定资源的起始子载波位置根据NPRACH资源的起始子载波位置和第一偏置参数确定。
或者，
上述特定资源的载波位置根据NPRACH资源的子集的载波位置和第一偏置参数确定，上述特定资源的起始子载波位置根据NPRACH资源的子集的起始子载波位置和第二偏置参数确定。
其中，第一偏置参数和第二偏置参数通过网络设备发送的系统消息配置。
当预设参数、第一预设参数以及第二预设参数为比例因子时，以上述第5及第6种情况为例，具体为：
上述特定资源的载波位置根据NPRACH资源的载波位置与第一预设比例因子确定，上述特定资源的起始子载波位置根据NPRACH资源的起始子载波位置与第二预设比例因子确定。
或者，
上述特定资源的载波位置根据NPRACH资源的子集的载波位置与第一预设比例因子确定，上述特定资源的起始子载波位置根据NPRACH资源的子集的起始子载波位置与第二预设比例因子确定。
其中，第一预设比例因子和第二预设比例因子通过网络设备发送系统消息配置。
以下继续结合图4所示的NPRACH资源划分来介绍上述过程的示例。
1、子载波维度
假设偏置参数为Fi,i＝0,…,m-1。Fi可以是相对于Ai，Bi，Ci，Di，Ei起始子载波的频域偏置，也可以是相对Ai-Bi，Ai-Ci，Ai-Di，Ai-Ei起始子载波的频域偏置。
假设比例因子为αi,i＝0,…,m-1。Ai或Bi或Ci或Di或Ei中占比αi可以配置为的上述特定资源的频域资源，或者Ai或Bi或Ci或Di或Ei中占比(1-αi)可以配置为上述特定资源的频域资源，或者Ai-Bi或Ai-Ci或Ai-Di或Ai-Ei中占比αi可以配置为上述特定资源的频域资源，或者Ai-Bi或Ai-Ci或Ai-Di或Ai-Ei中占比(1-αi)可以配置为上述特定资源的频域资源，其中i＝0,…,m-1或i＝1,…,m-1。
2、NB-IoT载波维度
在NB-IoT载波维度，参数除了可以为偏置参数和比例因子外，还可以为位图。
偏置参数：
偏置参数可以是相对NB-IoT载波索引的偏置，例如，NB-IoT配置了m个NB-IoT载波，用于发起随机接入，载波索引为0,1,…,m-1，相对偏置可以是相对NB-IoT载波索引0的偏置，相对NB-IoT载波索引1的偏置等。
比例因子：
假设比例因子为β，载波索引I，I为整数，0≤I≤m-1，满足
Figure PCTCN2017078201-appb-000002
Figure PCTCN2017078201-appb-000003
Figure PCTCN2017078201-appb-000004
或
Figure PCTCN2017078201-appb-000005
的NB-IoT载波用于发送调度请求。或者I为正整数，1≤I≤m-1，满足
Figure PCTCN2017078201-appb-000006
Figure PCTCN2017078201-appb-000007
Figure PCTCN2017078201-appb-000008
或
Figure PCTCN2017078201-appb-000009
的NB-IoT载波用于发送调度请求。
位图：
假设用长度为m的位图来表示，位图中比特位与NB-IoT载波索引一一对应，低比特位表示最小索引号，或者高比特位表示最小索引号，或者按照其它预设规则排列，本申请不作具体限制。网络设备和终端设备均使用同一预设排列规则。位图中比特位置0表示对应NB-IoT载波配置为上述特定资源的频域资源或者比特位置1表示对应NB-IoT载波配置为上述特定资源的频域资源，比特0或比特1的数量表示配置为上述特定资源的NB-IoT载波数量。假设NB-IoT支持16个NB-IoT载波，可以用16比特的位图来配置或指示上述特定资源的频域资源，位图中比特位置1表示对应NB-IoT载波配置为上述特定资源的频域资源，低比特位于最小索引号对应，则位图1100100010100001表示有6个NB-IoT载波配置为上述特定资源的频域资源。
以下给出在上述第5种情况下，使用偏置参数作为参数的具体示例：
假设网络设备的系统消息中指示的第一偏置参数，即NB-IoT载波维度的偏置参数为F1，网络设备的系统消息中指示的第二偏置参数，即子载波维度的偏置参数为F2。其中，F1代表上述特定资源的载波位置是在NPRACH资源的索引为0的NB-IoT载波上偏置F1个NB-IoT载波得到，F2代表上述特定资源的起始子载波位置是在NPRACH资源的Ai中的起始子载波位置上偏移F2个子载波得到。
当网络设备向终端设备发送配置信息时，就可以将根据F1计算得出的载波索引，以及根据F2计算得出的子载波索引发送给终端设备。
另外，在这种方式中，上述特定资源的时域资源可以通过在NPRACH时域资源上引入位图来表示，例如，可以用位图中的比特位表示符号粒度、时隙粒度、子帧粒度或者NPRACH周期粒度等，比特位1表示对应的符号、时隙、子帧或者NPRACH周期作为上述特定资源的时域资源，比特位0表示对应的符号、时隙、子帧或者NPRACH周期不作为上述特定资源的时域资源，这里只是示例，比特位0或1对应含义也可以和上述示例相反。
第三种方式：
网络设备直接通过上述系统消息指示可作为第一资源的资源集合，而不依赖NPRACH资源，网络设备可以在系统消息中指示第一资源的配置参数，包括载波数、子载波数、起始子载波频域位置等。
该方法中，网络设备可以灵活指示可以作为第一资源的资源集合，而不需要重用现有的NPRACH资源，因此可以更加灵活的进行资源分配。
以上列出了确定特定资源的一些可选实施方式，在具体实施过程中，可以根据需要选择上述各方式中的一种或其组合来进行第一资源配置，所确定的特定资源可以为NPRACH资源，或者，为NPRACH资源的子集，或者，为NPRACH资源中除用于竞争随机接入的资源之外的资源，或者，为NPRACH资源中除用于竞争随机接入的资源之外的资源的子集，或者为NPRACH资源之外的资源。
以下介绍终端设备向网络设备通知上行数据量的方法。
在图3所示的步骤S304中，终端设备在第一资源上向网络设备发送调度请求，以请求网络设备分配上行信道资源。除此之外，终端设备还需要向网络设备告知需要传输的上行数据的大小，以使网络设备根据该信息分配合理地上行信道资源。一种可选的实施方式中，终端设备可以在步骤S304之后再向网络设备发送一条用于通知上行数据大小的消息。另一种可选的实施方式中，终端设备可以在步骤S304中发送调度请求时隐含携带上行数据量的信息，网络设备再根据调度请求确定待传输的上行数据的数据量信息。其中，第二种方式下可以节省终端设备专门向网络设备上报上行数据量的过程，因此可以节省无线传输资源。以下主要描述第二种方式的具体实施过程。
在第二种方式中，终端设备在向网络设备发送调度请求时携带待传输的上行数据的数据量信息，网络设备根据调度请求确定待传输的上行数据的数据量信息。
具体地，可以通过下述两种方法来实施：
(1)通过资源类型隐含携带待传输的上行数据的数据量信息
终端设备通过第一资源向网络设备发送调度请求时携带待传输的上行数据的数据量信息，网络设备根据所接收的调度请求对应的第一资源确定待传输的上行数据的数据量信息。
其中，第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合。时域资源、频域资源、码资源或者时域资源、频域资源、码资源的组合与待传输的上行数据的数据量信息具有预设对应关系。
具体地，可以将第一资源对应的时域资源对应一种时刻，频域资源对应的一种频域位置，码资源对应的一种正交码，或者其组合与待传输的上行数据的数据量信息对应。
例如，针对时域资源，终端设备根据第一资源配置消息中指示的覆盖等级信息确定发 送调度请求的周期和起始时刻，终端设备发送调度请求的周期为奇数周期或者偶数周期指示传输信息量。
针对频域资源，
第一资源配置消息中包含多个载波索引，终端设备发送调度请求时的起始子载波位置或索引与待传输的上行数据的数据量信息具有预设对应关系；
或者，第一资源配置消息中包含多个起始子载波索引，终端设备发送调度请求时的起始子载波位置或索引与待传输的上行数据的数据量信息量具有预设对应关系；
或者，第一资源配置消息中包含多个载波索引和多个起始子载波索引，终端设备发送调度请求时的载波位置和起始子载波位置与待传输的上行数据的数据量信息量具有预设对应关系；
或者，第一资源配置消息中包含多个载波索引和多个起始子载波索引，终端设备发送调度请求时的载波索引和起始子载波索引与待传输的上行数据的数据量信息量具有预设对应关系。
针对码资源，第一资源配置消息中包含多个正交码，终端设备发送调度请求时的正交码或正交码索引与待传输的上行数据的数据量信息量具有预设对应关系。
上述时域资源和频域资源的组合，频域资源和码资源的组合，时域资源和码资源的组合，以及时域资源，频域资源和码资源的组合与待传输的上行数据的数据量信息量具有预设对应关系。
(2)通过延时或提前发送调度请求隐含携带待传输的上行数据的数据量信息
在一种可选的实施方式中，终端设备发送调度请求的信号可以为NPRACH的前导码。
图5为NB-IoT随机接入的前导码示意图，如图5所示，NB-IoT随机接入前导码由单个子载波跳频的符号组组成。一个前导码是由4个符号组组成，每个符号组包括一个循环前缀和5个符号，5个符号中每个符号的时长都相同，为8192Ts，其中Ts为时间单元满足Ts＝1/(15000×2048)秒，一个循环前缀的时长可以和一个符号的时长可以相同，可以不同。在实际传输时，前导码根据网络配置的重复次数可以重复多次。
NPRACH前导码的频域跳频的范围是在12个子载波内。一个NB-IoT载波的带宽是180kHz，一个NPRACH前导码占用一个子载波，子载波带宽是3.75kHz，因此一个NB-IoT载波最多可以支持180/3.75＝48个NPRACH前导码。
在一种可选的实施方式中，终端设备发送调度请求的信号可以为NPRACH的前导码或者为类似NPRACH前导结构的新序列，即该序列也是由由单个子载波跳频的符号组组成。一个前导码是由4个符号组组成，每个符号组包括一个循环前缀和5个符号，5个符号中每个符号的时长都相同，为8192Ts，其中Ts为时间单元满足Ts＝1/(15000×2048)秒，一个循环前缀的时长可以和NPRACH前导码的循环前缀时长相同或者不同。序列的频域跳频的范围是在12个子载波内。
本实施例中，终端设备发送的调度请求的序列可以是NB-IoT随机接入中的前导码序列，并且，在发送调度请求之前，终端设备已经执行过时间提前(Timing Advance，TA)调整。
进而，终端设备在第一资源上使用NB-IoT随机接入中的前导码序列发送调度请求时，可以在第一资源上延时或提前发送调度请求，发送的调度请求对应的延时的时间量或提前 的时间量与待传输的上行数据的数据量信息具有预设对应关系，网络设备根据在第一资源上所接收的调度请求对应的延时的时间量或提前的时间量确定待传输的上行数据的数据量信息。
示例性地，图6为延时发送NB-IoT随机接入中的前导码序列来表示传输数据信息的示例图，如图6所示，终端设备可以分别通过延时0个符号时长、1/4个符号时长、1/2个符号时长以及3/4个符号时长发送前导码序列来分别表示一个待传输的上行数据的数据量的范围，这里的符号时长和NPRACH前导码中一个符号的时长相同，为8192Ts，其中Ts为时间单元满足Ts＝1/(15000×2048)秒。
假设延时符号与待传输的上行数据的数据量范围的对应关系如表1所示，则当终端设备在第一资源上延时1/4个符号时长向网络设备发送调度请求后，网络设备检测到该调度请求延时了1/4个符号时长，则网络设备可以确定出该终端设备需要发送的上行数据在大于10字节且小于或者等于12字节的范围以内，则网络设备可以为该终端设备分配大于10字节且小于或等于12字节的数据对应的上行信道资源。
表1
延时符号 待传输的上行数据的数据量范围(字节)
0个符号时长 0<待传输的上行数据的数据量<＝10
1/4个符号时长 10<待传输的上行数据的数据量<＝12
1/2个符号时长 12<待传输的上行数据的数据量<＝14
3/4个符号时长 14<待传输的上行数据的数据量<＝17
需要说明的是，图6中仅示出了前导码序列的一个符号组，其他符号组的延时策略与其保持一致。
图7为本申请提供的资源调度方法实施例二的交互流程图，该实施例的应用场景是当网络设备调度上行传输期间，终端设备有上行数据到达，如图7所示，该方法的另一种执行过程为：
S701、终端设备接收网络设备发送的下行控制信息(Downlink Control Information，DCI)指示。
上述DCI用于指示第一资源，该第一资源为用于NPUSCH format2传输的时频资源，同时第一资源用于终端设备发送调度请求。
NB-IoT系统中的上行物理信道有NPRACH和NPUSCH，其中，NPUSCH包括NPUSCH format1以及NPUSCH format2，NPUSCH format1用于上行数据传输，NPUSCH format2用于承载下行HARQ-ACK反馈信息。
本实施例中，第一资源使用NPUSCH format2资源。
S702、终端设备根据上述DCI确定第一资源。
本步骤为可选步骤。
S702、当终端设备有上行数据到达时，终端设备在上述DCI指示的第一资源上向网络设备发送调度请求。
进而，网络设备在第一资源上接收并检测上述终端设备发送的调度请求，只要网络设备在第一资源上检测到上述终端设备发送的调度请求，则网络设备向终端设备分配上行信道资源；否则，网络设备只会根据检测到的HARQ-ACK反馈信息，执行相应的HARQ操 作。
本实施例中，终端设备在第一资源上向网络设备发送调度请求，该第一资源为用于NPUSCH format2传输的时频资源，即终端设备可以利用NPUSCH format2来发送调度请求，从而节省专门用于调度请求的资源。
在上述实施例的基础上，本实施例涉及终端设备使用NPUSCH format2资源发送调度请求的具体方法。
在一种可选的方式中，终端设备可以通过高阶调制将上述调度请求与HARQ-ACK反馈信息同时在第一资源上传输。HARQ-ACK反馈信息中ACK为肯定应答，NACK为否定应答。
可选地，终端设备可以根据要发送的信息进行正交相移键控(Quadrature Phase Shift Keying，QPSK)调制，例如，调制成00表示只发送ACK，调制成01表示既发送ACK又发送调度请求，调制成11表示只发送NACK，调制成10表示既发送NACK又发送调度请求。
在另一种可选的方式中，终端设备也可以通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息。
可选地，可以用HARQ-ACK反馈信息的调制符号星座点加π/2相位旋转表示既发送ACK又发送调度请求，用NACK调制符号星座点加π/2相位旋转表示既发送NACK又发送调度请求。
在另一种可选的方式中，终端设备也可以通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息。
可选地，例如NB-IoT中HARQ-ACK反馈信息编码后为16长的码字，ACK的信息比特1，编码后为16个1，NACK的信息比特0，编码后为16个0。ACK编码比特乘以一个长度为16的哈达玛序列中的一个子序列，比如{1，-1，1，-1，1，-1，1，-1，1，-1，1，-1，1，-1，1，-1}。即，若网络设备接收到的编码为16个1，则表示仅传输ACK；若网络设备接收到的编码为16个0，则表示仅传输NACK，若网路检测到正交码序列{1，-1，1，-1，1，-1，1，-1，1，-1，1，-1，1，-1，1，-1}，则表示检测到传输ACK和调度请求。
进一步地，终端设备还可以在通过上述几种方式传输调度请求时携带待传输的上行数据的数据量信息。
(1)通过高阶调制将上述调度请求与HARQ-ACK反馈信息同时在第一资源上传输时
可选地，待传输的上行数据的数据量信息与高阶调制的星座点具有预设对应关系，根据高阶调制的星座点可以确定出待传输的上行数据的数据量信息。
例如，通过QPSK调制，假设上行传输的数据量如表2所示，调制成00表示仅发送ACK，调制成01表示发送ACK以及索引值0对应的传输数据量范围，调制成11表示仅发送NACK，调制成10表示发送NACK以及索引值1对应的传输数据量范围。
表2
索引 传输数据量(字节)
0 0<传输数据量<＝32
1 32<传输数据量<＝64
(2)通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转同时在所述第一资源上传输所述调度请求以及HARQ-ACK反馈信息时
可选地，待传输的上行数据的数据量信息与相位旋转大小具有预设对应关系，根据相位旋转大小可以确定出待传输的上行数据的数据量信息。
例如，假设上行传输的数据量如表3所示，可以用HARQ-ACK反馈信息的调制符号星座点加π/2相位旋转表示发送＝ACK以及索引值0或索引值0对应的待传输的上行数据的数据量范围，可以用HARQ-NAC反馈信息的调制符号星座点加π/2相位旋转表示发送NACK以及索引值1或索引值对应的待传输的上行数据的数据量范围。
表3
索引 传输数据量(字节)
0 0<传输数据量<＝32
1 32<传输数据量<＝64
(3)通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在所述第一资源上传输所述调度请求以及HARQ-ACK反馈信息时
可选地，上述预设正交码为长度为16的哈达玛序列。
可选地，待传输的上行数据的数据量信息与预设正交码序列具有预设对应关系，根据预设正交码可以确定出待传输的上行数据的数据量信息。
例如，长度为16的哈达玛序列如表4所示，可以将ACK或NACK乘以16长的哈达玛序列，表示待传输的上行数据的数据量范围。
表4
Figure PCTCN2017078201-appb-000010
Figure PCTCN2017078201-appb-000011
图8为本申请提供的一种终端设备实施例一的模块结构图，如图8所示，该终端设备包括：
接收模块801，用于接收网络设备发送的配置消息。
处理模块802，用于根据接收模块801接收的配置信息获取用于发送调度请求的第一资源配置信息，该第一资源配置信息中包括用于指示增强覆盖等级的信息。
发送模块803，用于在处理模块802获取的第一资源配置信息所指示的第一资源上向网络设备发送调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送该调度请求时不执行随机接入过程。
该终端设备用于实现前述方法实施例一中终端设备的功能，其实现原理和技术效果类似，此处不再赘述。
另一实施例中，接收模块801还用于：接收所述网络设备发送的系统消息。
处理模块802还用于：根据系统消息获取NPRACH资源的配置信息。
其中，NPRACH资源为第一资源的资源集合，或者，NPRACH资源的子集为第一资源的资源集合，或者，NPRACH资源中除用于竞争随机接入的资源以外的资源为第一资源的资源集合，或者，NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为第一资源的资源集合。
另一实施例中，系统消息中携带第一预设参数和第二预设参数。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置与第一预设参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置与第二预设参数确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置与第一预设参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
进一步地，系统消息中携带第一偏置参数和第二偏置参数。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置和第一偏置参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置和第二偏置参数确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置和第一偏置参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置和第二偏置参数确定。
进一步地，系统消息中携带第一预设比例因子和第二预设比例因子。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置与第一预设比例因子确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置与第二预设比例因子确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置与第一预设比例因子确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置与第二预设比例因子确定。
另一实施例中，发送模块803还用于：
向网络设备发送调度请求时携带待传输的上行数据的数据量信息。
进一步地，发送模块803具体用于：
在第一资源上延时或提前向网络设备发送调度请求，调度请求对应的延时的时间量或提前的时间量与待传输的上行数据的数据量信息具有预设对应关系；
或者，
通过第一资源向网络设备发送调度请求时携带待传输的上行数据的数据量信息，第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，时域资源、频域资源、码资源或者时域资源、频域资源、码资源的组合与待传输的上行数据的数据量信息具有预设对应关系。
另一实施例中，终端设备发送调度请求的信号为NPRACH中的前导码，终端设备发送调度请求前执行过TA调整。
图9为本申请提供的一种网络设备实施例一的模块结构图，如图9所示，该网络设备包括：
发送模块901，用于向终端设备发送配置消息，该配置消息用于终端设备获取用于发送调度请求的第一资源配置信息，第一资源配置信息中包括用于指示增强覆盖等级的信息。
接收模块902，用于接收终端设备在第一资源配置信息所指示的第一资源上发送的调度请求，该调度请求用于向网络设备请求上行信道资源，终端设备在发送该调度请求时不执行随机接入过程。
处理模块903，用于根据接收模块902接收的调度请求向终端设备分配上行信道资源。
该网络设备用于实现前述方法实施例一中网络设备的功能，其实现原理和技术效果类似，此处不再赘述。
另一实施例中，发送模块901还用于：向终端设备发送系统消息，该系统消息中携带NPRACH资源的配置信息。
其中，NPRACH资源为第一资源的资源集合，或者，NPRACH资源的子集为第一资源的资源集合，或者，NPRACH资源中除用于竞争随机接入的资源以外的资源为第一资源的资源集合，或者，NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为第一资源的资源集合。
另一实施例中，系统消息中携带第一预设参数和第二预设参数。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置与第一预设参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置与第二预设参数确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置与第一预设参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
进一步地，系统消息中携带第一偏置参数和第二偏置参数。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置和第一偏置参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置和第二偏置参数确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置和第一偏置参数确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置和第二偏置参数确定。
进一步地，系统消息中携带第一预设比例因子和第二预设比例因子。
第一资源的资源集合的载波位置根据NPRACH资源的载波位置与第一预设比例因子确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的起始子载波位置与第二预设比例因子确定；
或者，
第一资源的资源集合的载波位置根据NPRACH资源的子集的载波位置与第一预设比例因子确定，第一资源的资源集合的起始子载波位置根据NPRACH资源的子集的起始子载波位置与第二预设比例因子确定。
另一实施例中，处理模块903还用于：
根据终端设备发送的调度请求确定待传输的上行数据的数据量信息。
进一步地，处理模块903具体用于：
根据在所述第一资源上所接收的所述调度请求对应的延时的时间量或提前的时间量确定所述待传输的上行数据的数据量信息，其中，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；
或者，
根据所接收的所述调度请求对应的所述第一资源确定所述待传输的上行数据的数据量信息，其中，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资 源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
另一实施例中，网络设备接收的调度请求的信号为NPRACH中的前导码，终端设备发送调度请求前执行过TA调整。
图10为本申请提供的另一种终端设备实施例一的模块结构图，如图10所示，该终端设备包括：
接收模块1001，用于接收网络设备发送的DCI指示，该DCI用于指示第一资源，第一资源为用于NPUSCH format2传输的时频资源。
处理模块1002，用于根据DCI确定第一资源。
发送模块1003，用于在第一资源上向网络设备发送调度请求。
该装置用于实现前述方法实施例二中终端设备的功能，其实现原理和技术效果类似，此处不再赘述。
另一实施例中，发送模块1003具体用于：
通过高阶调制将调度请求与HARQ-ACK反馈信息同时在第一资源上传输。
另一实施例中，发送模块1003具体还用于：
通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转同时在第一资源上传输调度请求以及HARQ-ACK反馈信息。
另一实施例中，发送模块1003具体还用于：
通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息。
进一步地，上述预设正交码为长度为16的哈达玛序列。
另一实施例中，发送模块1003还用于：
向网络设备发送调度请求时携带待传输的上行数据的数据量信息。
进一步地，上述待传输的上行数据的数据量信息与高阶调制的星座点具有预设对应关系。
进一步地，上述待传输的上行数据的数据量信息与相位旋转大小具有预设对应关系。
进一步地，上述待传输的上行数据的数据量信息与所述预设正交码序列具有预设对应关系。
图11为本申请提供的另一种网络设备实施例一的模块结构图，如图11所示，该网络设备包括：
发送模块1101，用于向终端设备发送DCI指示，该DCI用于指示第一资源，该第一资源为用于NPUSCH format2传输的时频资源。
接收模块1102，用于接收终端设备在第一资源上发送的调度请求。
处理模块1103，用于根据调度请求向终端设备分配上行信道资源。
该装置用于实现前述方法实施例二中网络设备的功能，其实现原理和技术效果类似，此处不再赘述。
另一实施例中，终端设备通过高阶调制将调度请求与HARQ-ACK反馈信息同时在第一资源上传输，处理模块1103具体用于：
根据接收到的高阶调制后的信号确定终端设备是否发送了调度请求。
另一实施例中，终端设备通过对HARQ-ACK反馈消息对应的调制符号进行相位旋转，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息，处理模块1103具体还用于：
根据接收到的进行相位旋转的调制符号确定终端设备是否发送了调度请求。
另一实施例中，终端设备通过将HARQ-ACK反馈信息对应的调制符号或编码比特乘以预设正交码，以同时在第一资源上传输调度请求以及HARQ-ACK反馈信息，处理模块1103具体还用于：
根据接收到的乘以预设正交码之后的调制符号确定终端设备是否发送了调度请求。
进一步地，上述预设正交码为长度为16的哈达玛序列。
另一实施例中，
根据终端设备发送的调度请求确定待传输的上行数据的数据量信息。
进一步地，上述待传输的上行数据的数据量信息与高阶调制的星座点具有预设对应关系。
进一步地，上述待传输的上行数据的数据量信息与相位旋转大小具有预设对应关系。
进一步地，上述待传输的上行数据的数据量信息与所述预设正交码序列具有预设对应关系。
图12为本申请提供的一种终端设备实施例一的实体框图，如图12所述，该终端设备包括：
存储器1201和处理器1202。
存储器1201用于存储程序指令，处理器1202用于调用存储器1201中的程序指令，实现上述方法实施例一种终端设备的功能。
图13为本申请提供的一种网络设备实施例一的实体框图，如图13所述，该网络设备包括：
存储器1301和处理器1302。
存储器1301用于存储程序指令，处理器1302用于调用存储器1301中的程序指令，实现上述方法实施例一种网络设备的功能。
图14为本申请提供的另一种终端设备实施例一的实体框图，如图14所述，该终端设备包括：
存储器1201和处理器1202。
存储器1201用于存储程序指令，处理器1202用于调用存储器1201中的程序指令，实现上述方法实施例二中终端设备的功能。
图15为本申请提供的另一种网络设备实施例一的实体框图，如图15所述，该网络设备包括：
存储器1501和处理器1502。
存储器1501用于存储程序指令，处理器1502用于调用存储器1501中的程序指令，实现上述方法实施例二中网络设备的功能。

Claims (34)

  1. 一种资源调度方法，其特征在于，包括：
    终端设备接收网络设备发送的配置消息；
    所述终端设备根据所述配置消息获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    终端设备在所述第一资源配置信息所指示的第一资源上向网络设备发送调度请求，所述调度请求用于向网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接入过程。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备接收网络设备发送的配置消息之前，还包括：
    所述终端设备接收所述网络设备发送的系统消息；
    所述终端设备根据所述系统消息获取NPRACH资源的配置信息；
    其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
  3. 根据权利要求2所述的方法，其特征在于，所述系统消息中携带第一预设参数和第二预设参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
  4. 根据权利要求3所述的方法，其特征在于，所述系统消息中携带第一偏置参数和第二偏置参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置和所述第二偏置参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置和所述第二偏置参数确定。
  5. 根据权利要求3所述的方法，其特征在于，所述系统消息中携带第一预设比例因子和第二预设比例因子；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源 的起始子载波位置与所述第二预设比例因子确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设比例因子确定。
  6. 根据权利要求1-5任一所述的方法，其特征在于，还包括：
    所述终端设备向所述网络设备发送调度请求时携带待传输的上行数据的数据量信息。
  7. 根据权利要求6所述的方法，其特征在于，所述终端设备向所述网络设备发送调度请求时携带待传输的上行数据的数据量信息包括：
    所述终端设备在所述第一资源上延时或提前向所述网络设备发送调度请求，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；或者，
    所述终端设备通过所述第一资源向所述网络设备发送调度请求时携带所述待传输的上行数据的数据量信息，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
  8. 根据权利要求1-7任一所述的方法，其特征在于，所述终端设备发送调度请求的信号为NPRACH中的前导码，所述终端设备发送调度请求前执行过时间提前TA调整。
  9. 一种资源调度方法，其特征在于，包括：
    网络设备向终端设备发送配置消息，所述配置消息用于所述终端设备获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    所述网络设备接收所述终端设备在所述第一资源配置信息所指示的第一资源上发送的调度请求，所述调度请求用于向所述网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接入过程；
    所述网络设备根据所述调度请求向所述终端设备分配上行信道资源。
  10. 根据权利要求9所述的方法，其特征在于，所述网络设备向终端设备发送配置消息之前，还包括：
    所述网络设备向所述终端设备发送系统消息，所述系统消息中携带NPRACH资源的配置信息；
    其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
  11. 根据权利要去10所述的方法，其特征在于，所述系统消息中携带第一预设参数和第二预设参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
  12. 根据权利要求11所述的方法，其特征在于，所述系统消息中携带第一偏置参数和第二偏置参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置和所述第二偏置参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置和所述第二偏置参数确定。
  13. 根据权利要求11所述的方法，其特征在于，所述系统消息中携带第一预设比例因子和第二预设比例因子；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设比例因子确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设比例因子确定。
  14. 根据权利要求9-13任一所述的方法，其特征在于，还包括：
    所述网络设备根据所述终端设备发送的调度请求确定待传输的上行数据的数据量信息。
  15. 根据权利要求14所述的方法，其特征在于，
    所述网络设备根据在所述第一资源上所接收的所述调度请求对应的延时的时间量或提前的时间量确定所述待传输的上行数据的数据量信息，其中，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；
    或者，
    所述网络设备根据所接收的所述调度请求对应的所述第一资源确定所述待传输的上行数据的数据量信息，其中，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
  16. 根据权利要求9-15任一所述的方法，其特征在于，所述网络设备接收的所述调度请求的信号为NPRACH中的前导码，所述终端设备发送调度请求前执行过时间提前TA调整。
  17. 一种终端设备，其特征在于，包括：
    接收模块，用于接收网络设备发送的配置消息；
    处理模块，用于根据接收模块接收的配置信息获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    发送模块，用于在处理模块获取的所述第一资源配置信息所指示的第一资源上向网络设备发送调度请求，所述调度请求用于向网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接入过程。
  18. 根据权利要求17所述的终端设备，其特征在于，所述接收模块还用于：
    接收所述网络设备发送的系统消息；
    所述处理模块还用于：
    根据所述系统消息获取NPRACH资源的配置信息；
    其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
  19. 根据权利要求18所述的终端设备，其特征在于，所述系统消息中携带第一预设参数和第二预设参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
  20. 根据权利要求19所述的终端设备，其特征在于，所述系统消息中携带第一偏置参数和第二偏置参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置和所述第二偏置参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置和所述第二偏置参数确定。
  21. 根据权利要求19所述的终端设备，其特征在于，所述系统消息中携带第一预设比例因子和第二预设比例因子；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设比例因子确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH 资源的子集的起始子载波位置与所述第二预设比例因子确定。
  22. 根据权利要求17-21任一所述的终端设备，其特征在于，所述发送模块还用于：
    向所述网络设备发送调度请求时携带待传输的上行数据的数据量信息。
  23. 根据权利要求22所述的终端设备，其特征在于，所述发送模块具体用于：
    在所述第一资源上延时或提前向所述网络设备发送调度请求，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；
    或者，
    通过所述第一资源向所述网络设备发送调度请求时携带所述待传输的上行数据的数据量信息，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
  24. 根据权利要求17-23任一所述的终端设备，其特征在于，所述终端设备发送调度请求的信号为NPRACH中的前导码，所述终端设备发送调度请求前执行过时间提前TA调整。
  25. 一种网络设备，其特征在于，包括：
    发送模块，用于向终端设备发送配置消息，所述配置消息用于所述终端设备获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    接收模块，用于接收所述终端设备在所述第一资源配置信息所指示的第一资源上发送的调度请求，所述调度请求用于向所述网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接入过程；
    处理模块，用于根据所述接收模块接收的调度请求向所述终端设备分配上行信道资源。
  26. 根据权利要求25所述的网络设备，其特征在于，所述发送模块还用于：
    向所述终端设备发送系统消息，所述系统消息中携带NPRACH资源的配置信息；
    其中，所述NPRACH资源为所述第一资源的资源集合，或者，所述NPRACH资源的子集为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源为所述第一资源的资源集合，或者，所述NPRACH资源中除用于竞争随机接入的资源以外的资源的子集为所述第一资源的资源集合。
  27. 根据权利要求26所述的网络设备，所述系统消息中携带第一预设参数和第二预设参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设参数确定。
  28. 根据权利要求27所述的网络设备，其特征在于，所述系统消息中携带第一偏置 参数和第二偏置参数；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置和所述第二偏置参数确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置和所述第一偏置参数确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置和所述第二偏置参数确定。
  29. 根据权利要求27所述的网络设备，其特征在于，所述系统消息中携带第一预设比例因子和第二预设比例因子；
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的起始子载波位置与所述第二预设比例因子确定；
    或者，
    所述第一资源的资源集合的载波位置根据所述NPRACH资源的子集的载波位置与所述第一预设比例因子确定，所述第一资源的资源集合的起始子载波位置根据所述NPRACH资源的子集的起始子载波位置与所述第二预设比例因子确定。
  30. 根据权利要求25-28任一所述的网络设备，其特征在于，所述处理模块还用于：
    根据所述终端设备发送的调度请求确定待传输的上行数据的数据量信息。
  31. [根据细则91更正 08.05.2017]
    根据权利要求30所述的网络设备，其特征在于，所述处理模块具体用于：
    根据在所述第一资源上所接收的所述调度请求对应的延时的时间量或提前的时间量确定所述待传输的上行数据的数据量信息，其中，所述调度请求对应的延时的时间量或提前的时间量与所述待传输的上行数据的数据量信息具有预设对应关系；
    或者，
    根据所接收的所述调度请求对应的所述第一资源确定所述待传输的上行数据的数据量信息，其中，所述第一资源包括时域资源、频域资源、码资源，或者时域资源、频域资源、码资源的组合，所述时域资源、频域资源、码资源或者所述时域资源、频域资源、码资源的组合与所述待传输的上行数据的数据量信息具有预设对应关系。
  32. 根据权利要求25-31任一所述的网络设备，其特征在于，所述网络设备接收的所述调度请求的信号为NPRACH中的前导码，所述终端设备发送调度请求前执行过时间提前TA调整。
  33. 一种终端设备，其特征在于，包括：存储器和处理器；
    所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，执行下述方法：
    接收网络设备发送的配置消息，
    根据所述配置消息获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    在所述第一资源配置信息所指示的第一资源上向网络设备发送调度请求，所述调度请求用于向网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接 入过程。
  34. 一种网络设备，其特征在于，包括：存储器和处理器；
    所述存储器用于存储程序指令，所述处理器用于调用所述存储器中的程序指令，执行下述方法：
    向终端设备发送配置消息，所述配置消息用于所述终端设备获取用于发送调度请求的第一资源配置信息，所述第一资源配置信息中包括用于指示增强覆盖等级的信息；
    接收所述终端设备在所述第一资源配置信息所指示的第一资源上发送的调度请求，所述调度请求用于向所述网络设备请求上行信道资源，所述终端设备在发送所述调度请求时不执行随机接入过程；
    根据所述调度请求向所述终端设备分配上行信道资源。
PCT/CN2017/078201 2017-03-24 2017-03-24 资源调度方法、终端设备及网络设备 WO2018170924A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
PCT/CN2017/078201 WO2018170924A1 (zh) 2017-03-24 2017-03-24 资源调度方法、终端设备及网络设备
EP17902525.9A EP3614758A4 (en) 2017-03-24 2017-05-12 RESOURCE PLANNING METHOD, TERMINAL DEVICE AND NETWORK DEVICE
PCT/CN2017/084222 WO2018171023A1 (zh) 2017-03-24 2017-05-12 资源调度方法、终端设备及网络设备
JP2019552461A JP7221874B2 (ja) 2017-03-24 2017-05-12 リソーススケジューリング方法、端末デバイス、およびネットワークデバイス
CN202111138754.XA CN114025414B (zh) 2017-03-24 2017-05-12 资源调度方法、终端设备及网络设备
CN201780084078.8A CN110214464B (zh) 2017-03-24 2017-05-12 资源调度方法、终端设备及网络设备
US16/580,911 US11533744B2 (en) 2017-03-24 2019-09-24 Resource scheduling method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/078201 WO2018170924A1 (zh) 2017-03-24 2017-03-24 资源调度方法、终端设备及网络设备

Publications (1)

Publication Number Publication Date
WO2018170924A1 true WO2018170924A1 (zh) 2018-09-27

Family

ID=63584014

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/078201 WO2018170924A1 (zh) 2017-03-24 2017-03-24 资源调度方法、终端设备及网络设备
PCT/CN2017/084222 WO2018171023A1 (zh) 2017-03-24 2017-05-12 资源调度方法、终端设备及网络设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/084222 WO2018171023A1 (zh) 2017-03-24 2017-05-12 资源调度方法、终端设备及网络设备

Country Status (5)

Country Link
US (1) US11533744B2 (zh)
EP (1) EP3614758A4 (zh)
JP (1) JP7221874B2 (zh)
CN (2) CN114025414B (zh)
WO (2) WO2018170924A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190223190A1 (en) * 2017-03-24 2019-07-18 Lg Electronics Inc. Method and nb wireless device for determining whether or not to transmit sr
CN110175824A (zh) * 2019-05-22 2019-08-27 上海盛付通电子支付服务有限公司 用于进行资源配置的设备及资源配置方法
WO2020097805A1 (en) * 2018-11-13 2020-05-22 Nokia Shanghai Bell Co., Ltd. Uplink data resource pre-configuration
CN111586859A (zh) * 2019-02-16 2020-08-25 华为技术有限公司 资源配置的方法和装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200029580A (ko) * 2017-08-09 2020-03-18 엘지전자 주식회사 랜덤 접속 과정을 수행하는 방법 및 이를 위한 장치
WO2020020335A1 (zh) * 2018-07-27 2020-01-30 Oppo广东移动通信有限公司 随机接入的方法和装置
EP4040816A1 (en) * 2018-09-17 2022-08-10 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Communication method, terminal device and network device
CN112583562B (zh) * 2019-09-30 2022-08-26 华为技术有限公司 数据传输的方法与装置
CN113873538A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种模型数据传输方法及通信装置
CN115278918A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 通信方法及装置
US20230239883A1 (en) * 2022-01-27 2023-07-27 Qualcomm Incorporated Techniques for granting resources for network coding procedures

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150181624A1 (en) * 2012-06-27 2015-06-25 Lg Electronics Inc. Method and terminal for random access to small cell
US20160316491A1 (en) * 2015-04-27 2016-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Robust selection of prach repetition level for mtc enhanced coverage

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101796749B (zh) * 2007-09-14 2014-05-14 Lg电子株式会社 在无线通信系统中传送控制信息的方法
KR101387537B1 (ko) * 2007-09-20 2014-04-21 엘지전자 주식회사 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법
US9215729B2 (en) * 2008-07-01 2015-12-15 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a telecommunications system
US9392591B2 (en) * 2009-05-15 2016-07-12 Alcatel Lucent Method for synchronization and signaling of occupied bands in orthogonal frequency division multiplexing (OFDM) transmissions
CN102215595A (zh) * 2010-04-07 2011-10-12 北京三星通信技术研究有限公司 一种上行调度请求传输方法
CN101980575B (zh) * 2010-10-14 2013-04-24 华为技术有限公司 随机接入的处理方法和终端
KR101776873B1 (ko) * 2011-01-11 2017-09-11 삼성전자 주식회사 이동통신 시스템에서 역방향 전송 출력 결정 방법 및 장치
EP2560448A1 (en) * 2011-08-18 2013-02-20 Fujitsu Limited Scheduling request enabled uplink transmission
CN103548405A (zh) * 2012-03-16 2014-01-29 华为技术有限公司 调度请求资源配置方法、设备及系统
CN103906176B (zh) * 2012-12-27 2018-11-09 华为技术有限公司 一种接入站点的方法、装置及系统
US20170238252A1 (en) * 2014-10-24 2017-08-17 Nokia Technologies Oy Enabling power efficient dual connectivity with reduced delay impact
US10455600B2 (en) 2015-04-08 2019-10-22 Lg Electronics Inc. Method for transmitting and receiving data in wireless communication system and apparatus for the same
US10200177B2 (en) * 2015-06-12 2019-02-05 Comcast Cable Communications, Llc Scheduling request on a secondary cell of a wireless device
CN106413092B (zh) * 2015-07-22 2019-07-05 普天信息技术有限公司 上行资源分配方法及装置
CN107734652B (zh) * 2016-08-10 2020-01-21 电信科学技术研究院 一种sPUCCH传输的方法、终端及基站
US10454659B2 (en) * 2017-02-28 2019-10-22 Qualcomm Incorporated Narrowband time-division duplex frame structure for narrowband communications
US10674522B2 (en) * 2017-03-23 2020-06-02 Qualcomm Incorporated Scheduling request for one or more uplink transmissions using narrowband communications
US11159929B2 (en) * 2017-03-24 2021-10-26 Apple Inc. Scheduling request for further enhanced narrowband internet of things (feNB-IoT)
JP2020501441A (ja) * 2017-03-24 2020-01-16 エルジー エレクトロニクス インコーポレイティド Ｓｒの送信可否を決定する方法及びｎｂ無線機器

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150181624A1 (en) * 2012-06-27 2015-06-25 Lg Electronics Inc. Method and terminal for random access to small cell
US20160316491A1 (en) * 2015-04-27 2016-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Robust selection of prach repetition level for mtc enhanced coverage

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Scheduling request design for NR", 3GPP TSG RAN WG1 MEETING #88, R1-1702234, 17 February 2017 (2017-02-17), XP051221142 *
SAMSUNG: "On NR scheduling request", 3GPP TSG RAN WG1 MEETING #88, R1-1702993, 17 February 2017 (2017-02-17), XP051221793 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190223190A1 (en) * 2017-03-24 2019-07-18 Lg Electronics Inc. Method and nb wireless device for determining whether or not to transmit sr
EP3509239A4 (en) * 2017-03-24 2019-11-06 LG Electronics Inc. -1- METHOD AND NARROWBAND WIRELESS DEVICE FOR DETERMINING OR NOT TRANSMITTING A PLANNING REQUEST
US10873956B2 (en) 2017-03-24 2020-12-22 Lg Electronics Inc. Method and NB wireless device for determining whether or not to transmit SR
EP3923498A1 (en) * 2017-03-24 2021-12-15 LG Electronics Inc. Method and nb wireless device for determining whether or not to transmit sr
US11671295B2 (en) 2017-03-24 2023-06-06 Lg Electronics Inc. Method and NB wireless device for determining whether or not to transmit SR
WO2020097805A1 (en) * 2018-11-13 2020-05-22 Nokia Shanghai Bell Co., Ltd. Uplink data resource pre-configuration
CN113016206A (zh) * 2018-11-13 2021-06-22 上海诺基亚贝尔股份有限公司 上行链路数据资源预配置
CN113016206B (zh) * 2018-11-13 2023-04-25 上海诺基亚贝尔股份有限公司 上行链路数据资源预配置的设备、方法、装置和存储介质
CN111586859A (zh) * 2019-02-16 2020-08-25 华为技术有限公司 资源配置的方法和装置
CN111586859B (zh) * 2019-02-16 2023-10-24 华为技术有限公司 资源配置的方法和装置
CN110175824A (zh) * 2019-05-22 2019-08-27 上海盛付通电子支付服务有限公司 用于进行资源配置的设备及资源配置方法

Also Published As

Publication number Publication date
JP2020512758A (ja) 2020-04-23
US20200022173A1 (en) 2020-01-16
CN110214464B (zh) 2021-10-15
CN110214464A (zh) 2019-09-06
WO2018171023A1 (zh) 2018-09-27
CN114025414B (zh) 2024-04-12
EP3614758A4 (en) 2020-05-27
EP3614758A1 (en) 2020-02-26
CN114025414A (zh) 2022-02-08
JP7221874B2 (ja) 2023-02-14
US11533744B2 (en) 2022-12-20

Similar Documents

Publication Publication Date Title
WO2018170924A1 (zh) 资源调度方法、终端设备及网络设备
US10979194B2 (en) Resource indication method, user equipment, and network device
AU2020260378B2 (en) Resource indication method and related device and system
US20190319762A1 (en) Grant-Free Transmission Method, Terminal, and Network Device
KR20200050848A (ko) Nr v2x 시스템에서 harq 피드백 절차 수행 방법 및 그 장치
CN106413105B (zh) 一种资源传输的指示方法、装置、网络侧设备及终端
EP3554118B1 (en) Grant-free transmission method, terminal device and network device
US11039448B2 (en) Resource scheduling method and apparatus
WO2017028051A1 (zh) 一种信息的传输方法和基站以及用户设备
TW201803382A (zh) 傳輸數據的方法、終端設備和網絡設備
EP3742850B1 (en) Uplink control information sending method, uplink control information receiving method, apparatus, and system
CN105659678B (zh) 一种上行数据的传输方法及相关设备
US20230164787A1 (en) Uplink control information transmission method and device
WO2018145302A1 (zh) 无线通信方法、终端设备和网络设备
CN110536426B (zh) 一种信息指示方法、装置及计算机可读存储介质
WO2018072180A1 (zh) 传输上行数据的方法、网络侧设备和终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17902089

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17902089

Country of ref document: EP

Kind code of ref document: A1