WO2020057421A1 - 资源调度方法及设备 - Google Patents

资源调度方法及设备 Download PDF

Info

Publication number
WO2020057421A1
WO2020057421A1 PCT/CN2019/105481 CN2019105481W WO2020057421A1 WO 2020057421 A1 WO2020057421 A1 WO 2020057421A1 CN 2019105481 W CN2019105481 W CN 2019105481W WO 2020057421 A1 WO2020057421 A1 WO 2020057421A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
pdcch
pdsch
channel
scheduling information
Prior art date
Application number
PCT/CN2019/105481
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 华为技术有限公司
Publication of WO2020057421A1 publication Critical patent/WO2020057421A1/zh

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the present application relates to the field of communications, and in particular, to a method and a device for resource scheduling.
  • the first device sends control instructions (set points) to the second device, and receives the device status (actual value) of the second device reported by the second device after executing the control instructions.
  • the device status has a corresponding relationship with the control instruction, and the reporting of the device status needs to be executed after the control instruction is issued.
  • a wireless communication technology such as a new air interface (NR).
  • a first device such as a base station gNB in an NR system, may issue two downlink control information (downlink control information (DCI)) carried on a physical downlink control channel (PDCCH) to issue control instructions.
  • DCI downlink control information
  • the wireless resources are scheduled separately from the device status report.
  • a physical uplink shared channel (PUSCH) for device status reporting is scheduled through DCI0, such as one or more PUSCH symbols
  • a physical downlink shared channel for control instruction delivery is scheduled through DCI1.
  • channel, PDSCH such as one or more PDSCH symbols.
  • the above-mentioned PUSCH and PDSCH are independently scheduled, which may cause the scheduled PUSCH to precede the PDSCH in the time domain, thereby causing the second device to fail to report the device of the second device on the PUSCH according to the execution result of the control instruction carried by the PDSCH. Status. That is, the independently scheduled PDSCH and PUSCH may collide, resulting in poor communication reliability between the first device and the second device.
  • the embodiments of the present application provide a resource scheduling method and device to solve the problem of poor communication reliability between the first device and the second device in the prior art.
  • a resource scheduling method includes: a first device delivering scheduling information of a downlink channel and scheduling information of an uplink channel to a second device. Then, the first device sends a downlink data packet to the second device on the downlink channel. After that, the first device receives the uplink data packet reported by the second device on the uplink channel.
  • the uplink channel is located behind the downlink channel in the time domain.
  • a resource scheduling method includes: the second device receives scheduling information of a downlink channel and scheduling information of an uplink channel issued by the first device. Then, the second device receives the downlink data packet sent by the first device on the downlink channel. After that, the second device reports the uplink data packet to the first device on the uplink channel.
  • the uplink channel is located behind the downlink channel in the time domain.
  • downlink data packets sent by the first device and uplink data packets reported by the second device must appear in pairs, and downlink data packets sent must be reported.
  • Specific requirements before uplink data packets are to uniformly schedule uplink and downlink channels for downlink data packets and uplink data packets, and the scheduled uplink channels are located after the downlink channels in the time domain to avoid downlink data packets and uplink data in the above scenarios, respectively.
  • the problem that the downlink channel and the uplink channel independently scheduled by the data packets cannot meet specific requirements and conflicts can improve the reliability of communication between the first device and the second device.
  • resource scheduling method provided by the first aspect and the resource scheduling method provided by the second aspect are the method flow performed by the requester and the responder in the industrial control scenario, artificial intelligence and other scenarios in this order.
  • the resource scheduling method provided in this application is not limited to the foregoing scenario.
  • the resource scheduling method provided in this application can be applied to any communication scenario in which the sent data packet and the reply data packet have a corresponding relationship in content, and the reply data packet is located behind the sent data packet in the time domain.
  • one party sends an operation instruction, and the other party executes the operation instruction and returns an execution result.
  • one party sends a service request, and the other party responds to the service request.
  • a downlink channel includes a physical downlink shared channel PDSCH, and scheduling information of the downlink channel includes an index of the PDSCH.
  • the PDSCH index can also be used to determine the resource configuration type, start symbol, and number of symbols of the PDSCH.
  • the PDSCH index and PDSCH scheduling information may be pre-stored locally on the second device, such as a correspondence table of resource configuration types, start time slots, start symbols, and number of symbols of the PDSCH.
  • the second device may The index of the received PDSCH queries the PDSCH scheduling information. Since the correspondence between the PDSCH index and the PDSCH scheduling information is the prior art, this application will not repeat them here.
  • the uplink channel usually includes the physical uplink shared channel PUSCH, and the scheduling information of the uplink channel includes one of the following uplink scheduling information:
  • Uplink scheduling information 1 a first index of the PUSCH; wherein the first index is used to determine a resource configuration type, a starting slot, a starting symbol, and a number of symbols of the PUSCH.
  • the second device may determine the PUSCH according to the correspondence between the first index and the scheduling information of the PUSCH pre-stored locally on the second device.
  • Resource allocation type, start time slot, start symbol, and number of symbols For example, a correspondence table of the first index and the scheduling information of the PUSCH pre-stored locally may be pre-stored locally on the second device.
  • the correspondence relationship table may include a correspondence relationship between the first index and a resource configuration type, a starting time slot, a starting symbol, and a number of symbols of the PUSCH.
  • the PUSCH may contain one or more consecutive symbols, and the resource allocation type may be one of type A (type A) and type B (type b).
  • the start symbol refers to the first one included in the PUSCH.
  • the starting slot refers to the slot where the first symbol included in the PUSCH is located, and the number of symbols refers to the number of symbols included in the PUSCH.
  • Uplink scheduling information 2 a second index and a starting slot of the PUSCH; wherein the second index is used to determine a resource configuration type, a starting symbol, and a number of symbols of the PUSCH.
  • the starting slot of the PUSCH can be configured separately, for example, by RRC signaling, and the other three scheduling information of the PUSCH still pass the index mode, that is, according to the second index and the scheduling of the PUSCH pre-stored locally on the second device.
  • the correspondence of the information is determined. Since the second index is similar to the first index, this application will not repeat them.
  • Uplink scheduling information 3 resource allocation type, starting time slot, starting symbol, and number of symbols of the PUSCH.
  • a correspondence table between the first index or the second index and the scheduling information of the PUSCH may also be pre-stored locally on the first device.
  • the first device may first determine the scheduling information of the PUSCH according to the correspondence relationship table, and then directly send the determined scheduling information to the second device through a form such as RRC signaling.
  • the names of the aforementioned PUSCH, PDSCH, PDCCH, and PUCCH may be different, which is not limited in this application.
  • the scheduling information of the PDSCH may include a start slot of the PDSCH. Therefore, in a possible design method, the time domain position of the PDSCH can be used as a reference to determine the time domain position of the PUSCH.
  • PUSCH and PDSCH can satisfy the first preset condition in the time domain.
  • the first preset condition may be:
  • n PDSCH is the start time slot of PDSCH
  • n PUSCH is the start time slot of PUSCH
  • ⁇ PDSCH is the frame format indication of PDSCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • K 2 is the preamble between PUSCH and PDSCH.
  • the uplink channel may also include a physical uplink control channel PUCCH. Therefore, in another possible design method, the time domain position of the PUSCH can also be used as a reference to determine the time domain position of the PUSCH.
  • PUSCH and PUCCH satisfy the second preset condition in the time domain.
  • the second preset condition may be:
  • n PUSCH is the start time slot of PUSCH
  • n PUCCH1 is the start time slot of PUCCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • ⁇ PUCCH1 is the frame format indication of PUCCH
  • K 3 is the preamble between PUSCH and PUCCH.
  • the PDSCH and the first PDCCH satisfy a third preset condition in the time domain.
  • the third preset condition may be:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PDSCH is the start time slot of the PDSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PDSCH is the frame format indication of the PDSCH
  • K 0 is the PDSCH and the first time slot.
  • the PUSCH and the first PDCCH satisfy a fourth preset condition in the time domain.
  • the fourth preset condition may be:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PUSCH is the start time slot of the PUSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PUSCH is the frame format indication of the PUSCH
  • K 4 is the PUSCH and the first time slot.
  • the scheduled uplink channel PUSCH is located behind the scheduled downlink channel PDSCH in the time domain, Can meet the needs of the above specific scenarios.
  • the following three methods can be used to transmit the scheduling information of the uplink channel:
  • Transmission mode one corresponds to uplink scheduling information one.
  • the first device delivering the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device may be specifically implemented as:
  • the first device sends the PDSCH index and the PUSCH index to the second device on the first PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as:
  • the second device receives the index of the PDSCH and the first index of the PUSCH issued by the first device on the first PDCCH.
  • PDSCH and PUSCH may be dynamically scheduled jointly on the first PDCCH.
  • the DCI format carried by the first PDCCH may include two Time domain resource assignment fields at the same time, which are respectively used to carry the index of the PDSCH and the first index of the PUSCH.
  • the second transmission mode corresponds to the second uplink scheduling information.
  • the first device sends the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device, which may be specifically implemented as the following step 1 and step 2:
  • Step 1 The first device sends the first radio link control RRC signaling to the second device, where the first RRC signaling carries a starting time slot of the PUSCH;
  • Step 2 The first device sends the PDSCH index and the second PUSCH index to the second device on the first PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as step three and step four:
  • Step 3 The first device sends the first radio link control RRC signaling to the second device, where the first RRC signaling carries a starting time slot of the PUSCH;
  • Step 4 On the first PDCCH, the second device receives the index of the PDSCH and the second index of the PUSCH issued by the first device.
  • the second index of the PUSCH carried by the first PDCCH is only used to determine the resource configuration type, starting symbol, and number of symbols of the PUSCH, and the starting slot of the PUSCH is determined by the first RRC Signalling bearer.
  • Transmission method three corresponds to three phases of uplink scheduling information.
  • the first device sends the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device, which may be specifically implemented as step 5 and step 6:
  • Step 5 The first device sends the PDSCH index to the second device on the first PDCCH.
  • Step 6 The first device sends the second RRC signaling to the second device.
  • the second RRC signaling carries a resource configuration type, starting time slot, number of symbols, and starting symbol of the PUSCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as step 7 and step 8:
  • Step 7 The second device receives the index of the PDSCH issued by the first device on the first PDCCH.
  • Step 8 The second device receives the second RRC signaling issued by the first device.
  • the second RRC signaling carries the resource configuration type, starting time slot, number of symbols, and starting symbol of the PUSCH.
  • the existing protocol stipulates that the DCI format carried by the PDCCH only includes a Time domain resource assignment field.
  • the first device may also directly issue the PUSCH scheduling information through the second RRC signaling.
  • scheduling information of the downlink channel and scheduling information of the uplink channel may also be separately delivered through two different PDCCHs.
  • the first device sending the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device may include steps 9 and 10:
  • Step 9 The first device sends scheduling information of the downlink channel to the second device on the first physical downlink control channel PDCCH.
  • Step 10 The first device sends the scheduling information of the uplink channel to the second device on the second PDCCH. There is a preset binding relationship between the third PDCCH and the second PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may include steps 11 and 12:
  • Step 11 The second device receives scheduling information of the downlink channel issued by the first device on the first physical downlink control channel PDCCH.
  • Step 12 The second device receives, on the second PDCCH, scheduling information of an uplink channel issued by the first device. There is a preset binding relationship between the third PDCCH and the second PDCCH.
  • the second device receives one on the one PDCCH.
  • scheduling information another scheduling information can be targetedly received on another PDCCH that has a binding relationship, to avoid the situation that the scheduling information of the downlink channel and the uplink channel need to be blindly detected in all possible resource sets. Effectively reducing the calculation amount of receiving the scheduling information of the downlink channel and the uplink channel, thereby improving the efficiency of the second device receiving the uplink and downlink scheduling information, and further improving the efficiency of communication between the first device and the second device.
  • the preset binding relationship between the second PDCCH and the first PDCCH may include one of the following: the search space to which the second PDCCH belongs (serch space) and the search space to which the first PDCCH belongs have a corresponding relationship; the second PDCCH belongs to the control
  • the resource set (control resource set, CORESET) corresponds to the CORESET to which the first PDCCH belongs; the bandwidth part (BWP) to which the second PDCCH belongs corresponds to the BWP to which the first PDCCH belongs; and the core carrier to which the second PDCCH belongs (core carrier) , CC) has a corresponding relationship with the CC to which the first PDCCH belongs.
  • the second device can also detect PDSCH scheduling information and PUSCH scheduling information on two CORESETs, two BWPs, or two CCs in a binding relationship, which is not described in the embodiment of this application .
  • search space CORESET, BWP, and CC can all be regarded as a representation manner of a resource or a resource set that may be used to carry the scheduling information of the downlink channel or the scheduling information of the uplink channel.
  • the names of the wireless communication systems may be different, which is not limited in the embodiments of the present application.
  • the uplink data packet has a corresponding relationship with the downlink data packet. It can be understood that the content carried by the uplink data packet is the execution result reported by the second device after completing the instruction or task carried by the downlink data packet.
  • the second device may also report indication information to indicate whether the reported uplink data packet is valid.
  • the second device may encapsulate one or more bits of indication information in a media access control (MAC) layer protocol data unit (PDU). For example, you can use the binary number 1 to indicate valid, and the binary number 0 to indicate invalid.
  • MAC media access control
  • the second device may also directly map the foregoing bits and execution results to the physical resources of the downlink channel to complete the report.
  • the second device may not report separate indication information, but report a preset sequence of values to indicate that the uplink data packet is invalid.
  • a preset value such as all 0 or all 1 indicates that the uplink data packet is invalid. It can be understood that if the uplink data packet does not include the above-mentioned preset numerical sequence, it can be regarded as valid.
  • the second device may also report uplink data packets and indication information on different uplink channels.
  • an uplink data packet is reported on the PUSCH, and indication information is reported on the PUCCH.
  • the indication information may be acknowledgement / non-acknowledgement (ACK / NACK).
  • Method 1 PUCCH is located before PUSCH in the time domain.
  • the second device feeds back NACK on the PUCCH, and it is no longer necessary to report uplink data packets on subsequent PUSCH (because there are no uplink data packets actually) to reduce the second device. The amount of data reported.
  • the first device may also reschedule the PUSCH to other devices to improve the radio resource utilization of the first device and reduce the amount of demodulation calculation of invalid uplink data packets.
  • the second device feeds back an ACK on the PUCCH.
  • the first device can confirm that the PUSCH received later is valid, and at the same time as receiving the PUSCH, the PUSCH can be demodulated to reduce the amount of data that the first device needs to buffer, thereby reducing the The storage cost of a device.
  • Method 2 PUCCH is located after PUSCH in the time domain. Specifically, the second device reports an uplink data packet on the PUSCH, and reports ACK / NACK on a subsequent PUCCH.
  • the first device needs to buffer the uplink data packet it receives on the PUSCH, and after the first device receives the indication information on the PUCCH, it determines whether to demodulate the received uplink data packet. For example, if the indication information is ACK, the received uplink data packet is demodulated; otherwise, it is directly discarded to reduce unnecessary demodulation workload.
  • a first device including: a sending module configured to send scheduling information of a downlink channel and scheduling information of an uplink channel to a second device, and send a downlink data packet to the second device on the downlink channel.
  • the receiving module is configured to receive an uplink data packet reported by a second device on an uplink channel.
  • the uplink channel is located behind the downlink channel in the time domain.
  • the downlink channel includes a physical downlink shared channel PDSCH, and scheduling information of the downlink channel includes an index of the PDSCH.
  • the uplink channel includes a physical uplink shared channel PUSCH, and the scheduling information of the uplink channel includes one of the following: a first index of the PUSCH; wherein the first index is used to determine a resource configuration type, a starting slot, a starting symbol, and a symbol number of the PUSCH The second index and starting slot of the PUSCH; wherein the second index is used to determine the resource configuration type, starting symbol, and number of symbols of the PUSCH; the resource configuration type, starting slot, starting symbol, and Number of symbols.
  • the PUSCH and PDSCH satisfy the first preset condition in the time domain:
  • n PDSCH is the start time slot of PDSCH
  • n PUSCH is the start time slot of PUSCH
  • ⁇ PDSCH is the frame format indication of PDSCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • K 2 is the preamble between PUSCH and PDSCH.
  • the uplink channel may further include a physical uplink control channel PUCCH.
  • PUCCH physical uplink control channel
  • n PUSCH is the start time slot of PUSCH
  • n PUCCH1 is the start time slot of PUCCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • ⁇ PUCCH1 is the frame format indication of PUCCH
  • K 3 is the preamble between PUSCH and PUCCH.
  • the sending module is further configured to send a PDSCH index and a PUSCH index to the second device on the first physical downlink control channel PDCCH.
  • the PDSCH and the first PDCCH satisfy a third preset condition in the time domain:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PDSCH is the start time slot of the PDSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PDSCH is the frame format indication of the PDSCH
  • K 0 is the PDSCH and the first time slot.
  • the sending module is further configured to send the first radio link control RRC signaling to the second device, and send the PDSCH index and the PUSCH to the second device on the first PDCCH.
  • the first RRC signaling carries a start time slot of the PUSCH.
  • the sending module is further configured to send the second RRC signaling to the second device, and send the PDSCH index to the second device on the first PDCCH.
  • the second RRC signaling carries the resource configuration type, starting time slot, number of symbols, and starting symbol of the PUSCH.
  • the sending module is further configured to send downlink channel scheduling information to the second device on the first physical downlink control channel PDCCH, and to the second device on the second PDCCH. Scheduling information for the uplink channel.
  • the preset binding relationship between the second PDCCH and the first PDCCH may include one of the following: the search space to which the second PDCCH belongs corresponds to the search space to which the first PDCCH belongs; the control resource set CORESET to which the second PDCCH belongs and CORESET and The CORESET to which the first PDCCH belongs has a corresponding relationship; the BWP to which the second PDCCH belongs has a corresponding relationship to the BWP to which the first PDCCH belongs; the core carrier CC to which the second PDCCH belongs has a corresponding relationship to the CC to which the first PDCCH belongs.
  • a second device including: a receiving module, configured to receive scheduling information of a downlink channel and scheduling information of an uplink channel issued by the first device, and receive downlink information issued by the first device on a downlink channel. data pack.
  • a sending module configured to report an uplink data packet to a first device on an uplink channel.
  • the uplink channel is located behind the downlink channel in the time domain.
  • the downlink channel includes a physical downlink shared channel PDSCH, and scheduling information of the downlink channel includes an index of the PDSCH.
  • the uplink channel includes a physical uplink shared channel PUSCH, and the scheduling information of the uplink channel includes one of the following: a first index of the PUSCH; wherein the first index is used to determine a resource configuration type, a starting slot, a starting symbol, and a symbol number of the PUSCH; The second index and starting slot of the PUSCH; wherein the second index is used to determine the resource configuration type, starting symbol, and number of symbols of the PUSCH; the resource configuration type, starting slot, starting symbol, and Number of symbols.
  • the PUSCH and PDSCH satisfy the first preset condition in the time domain:
  • n PDSCH is the start time slot of PDSCH
  • n PUSCH is the start time slot of PUSCH
  • ⁇ PDSCH is the frame format indication of PDSCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • K 2 is the preamble between PUSCH and PDSCH.
  • the uplink channel may further include a physical uplink control channel PUCCH.
  • PUCCH physical uplink control channel
  • n PUSCH is the start time slot of PUSCH
  • n PUCCH1 is the start time slot of PUCCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • ⁇ PUCCH1 is the frame format indication of PUCCH
  • K 3 is the preamble between PUSCH and PUCCH.
  • the receiving module is further configured to receive an index of the PDSCH issued by the first device on the first physical downlink control channel PDCCH.
  • the PDSCH and the first PDCCH satisfy a third preset condition in the time domain:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PDSCH is the start time slot of the PDSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PDSCH is the frame format indication of the PDSCH
  • K 0 is the PDSCH and the first time slot.
  • the receiving module is further configured to receive, on the first PDCCH, an index of the PDSCH and a first index of the PUSCH issued by the first device.
  • the receiving module is further configured to receive the first radio link control RRC signaling issued by the first device, and receive, on the first PDCCH, the index and sum of the PDSCH issued by the first device.
  • the first RRC signaling carries a start time slot of the PUSCH.
  • the receiving module is further configured to receive the second RRC signaling issued by the first device, and receive the index of the PDSCH issued by the second device on the first PDCCH;
  • RRC signaling carries the PUSCH resource configuration type, starting time slot, number of symbols, and starting symbols.
  • the receiving module is further configured to receive, on the first physical downlink control channel PDCCH, scheduling information of the downlink channel issued by the first device, and on the second PDCCH, receive the first device downlink The uplink channel scheduling information.
  • the preset binding relationship between the second PDCCH and the first PDCCH may include one of the following: the search space to which the second PDCCH belongs corresponds to the search space to which the first PDCCH belongs; the control resource set CORESET to which the second PDCCH belongs and CORESET and The CORESET to which the first PDCCH belongs has a corresponding relationship; the BWP to which the second PDCCH belongs has a corresponding relationship to the BWP to which the first PDCCH belongs; the core carrier CC to which the second PDCCH belongs has a corresponding relationship to the CC to which the first PDCCH belongs.
  • a first device in a fifth aspect, includes: a processor, a communication interface, and a memory; wherein the memory is used to store computer-executable instructions, the processor is connected to the memory through a bus, and when the first device is running, the processor executes the computer-executable memory-executable computer-executable An instruction to cause the first device to execute the resource scheduling method according to the first aspect.
  • a second device includes a processor, a communication interface, and a memory; wherein the memory is used to store computer-executable instructions, the processor is connected to the memory through a bus, and when the second device is running, the processor executes the computer-executable memory-stored computer-executable An instruction to cause the second device to execute the resource scheduling method according to the second aspect.
  • a communication system includes the first device and the second device.
  • a readable storage medium which stores a program or an instruction, and when the program or the instruction is run on a computer, causes the computer to execute the resource scheduling method according to the first aspect.
  • a readable storage medium which stores a program or an instruction, and when the program or the instruction is run on a computer, causes the computer to execute the resource scheduling method according to the second aspect.
  • a computer program product which is special in that the computer program code includes computer program code that, when the computer program code runs on a computer, causes the computer to execute the resource scheduling method according to the first aspect.
  • a computer program product which is special in that it includes computer program code, and when the computer program code runs on a computer, causes the computer to execute the resource scheduling method according to the second aspect.
  • the names of the various unit modules in the communication device do not constitute a limitation on the communication device itself. In actual implementation, these unit modules may appear under other names. As long as the function of each unit module is similar to the embodiment of the present application, it belongs to the scope of the claims of the present application and its equivalent technology.
  • FIG. 1 is a schematic diagram of a scenario in which a resource scheduling method and a device according to an embodiment of the present application are applied;
  • FIG. 1 is a schematic diagram of a scenario in which a resource scheduling method and a device according to an embodiment of the present application are applied;
  • FIG. 2 is a schematic flowchart of a resource scheduling method according to an embodiment of the present application.
  • FIG. 3A is a first schematic diagram of a starting time slot of a PUSCH scheduled by a resource scheduling method according to an embodiment of the present application
  • FIG. 3B is a second schematic diagram of a start slot of a PUSCH scheduled by a resource scheduling method according to an embodiment of the present application.
  • FIG. 3C is a third schematic diagram of a starting time slot of a PUSCH scheduled by a resource scheduling method according to an embodiment of the present application.
  • FIG. 4A is a first schematic diagram of a PUSCH scheduling information delivery method according to an embodiment of the present application.
  • FIG. 4B is a second schematic diagram of a method for transmitting scheduling information of a PUSCH provided by an embodiment of the present application.
  • FIG. 4C is a third schematic diagram of a PUSCH scheduling information delivery method according to an embodiment of the present application.
  • FIG. 4D is a fourth schematic diagram of a PUSCH scheduling information delivery method according to an embodiment of the present application.
  • 5A is a schematic diagram of a search space provided by an embodiment of the present application.
  • FIG. 5B is a schematic diagram of CC, BWP, CORESET, and search space according to an embodiment of the present application
  • FIG. 6A is a first schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • 6B is a second schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • FIG. 6C is a third schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • 6D is a fourth schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • FIG. 6E is a fifth schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • FIG. 6F is a sixth schematic diagram of a method for reporting instruction information provided by an embodiment of the present application.
  • FIG. 7 is a first structural schematic diagram of a first device according to an embodiment of the present application.
  • FIG. 8 is a first schematic structural diagram of a second device according to an embodiment of the present application.
  • FIG. 9 is a second schematic structural diagram of a first device according to an embodiment of the present application.
  • FIG. 10 is a third structural schematic diagram of a first device according to an embodiment of the present application.
  • FIG. 11 is a second schematic structural diagram of a second device according to an embodiment of the present application.
  • FIG. 12 is a third schematic structural diagram of a second device according to an embodiment of the present application.
  • the resource scheduling method provided in the embodiment of the present application may be applied to the communication system shown in FIG. 1, and the communication system may be a 5th generation (5G) mobile communication system, such as an NR system, and may also be a 4th generation ( 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, may also be other actual mobile communication systems, next-generation wireless fidelity (Wi-Fi) systems.
  • 5G 5th generation
  • 4G 4th generation
  • LTE long term evolution
  • Wi-Fi next-generation wireless fidelity
  • the communication system may include a first device 11 and a second device 12.
  • the first device 11 is mainly used to send downlink data packets to the second device 12, receive uplink data packets reported by the second device 12, and send scheduling information of downlink channels used for transmitting downlink data packets and transmission Scheduling information for the uplink channel of the uplink data packet.
  • the second device 12 is mainly used to receive the downlink data packet issued by the first device 11 and report the uplink data packet to the first device 11 as well as receive scheduling information of the downlink channel for transmitting the downlink data packet and be used for Scheduling information for an uplink channel transmitting uplink data packets.
  • the uplink data packet and the downlink data packet usually appear in pairs.
  • FIG. 1 is only an exemplary architecture diagram.
  • the communication system may further include other functional units, such as multiple second devices, which are not limited in the embodiments of the present application. .
  • the above first device 11 may be a base station, such as a gNB in an NR system, an evolved node (eNB) in an LTE system, an access point (AP) in a Wi-Fi system, or the like. It is a control device that supports at least one wireless communication standard such as NR, LTE, Wi-Fi, such as computers and servers used to control other devices in industrial control scenarios and artificial intelligence scenarios, which is not limited in this embodiment of the present application.
  • a base station such as a gNB in an NR system, an evolved node (eNB) in an LTE system, an access point (AP) in a Wi-Fi system, or the like.
  • eNB evolved node
  • AP access point
  • Wi-Fi Wireless Fidelity
  • the second device 12 may be a terminal, such as a user equipment (UE) in a NR system and / or an LTE system, a mobile phone, and a non-access point site in a Wi-Fi system, etc., or may support NR and LTE.
  • UE user equipment
  • LTE Long Term Evolution
  • Wi-Fi and other controlled devices of wireless communication standards such as machines and remote terminals used to perform specific tasks according to control instructions of other devices in industrial control scenarios and artificial intelligence scenarios.
  • downlink refers to a transmission direction sent by a network device and received by a terminal
  • uplink refers to a transmission direction sent by a terminal and received by a network device.
  • a network device may be a control device, and a terminal may be a controlled device.
  • Downlink may be the transmission direction sent by the control device and received by the controlled device
  • Uplink may be the transmission direction of the controlled device.
  • a network device may be a server and a terminal may be a remote client.
  • Downlink may be a transmission direction sent by the server and received by the remote client
  • Uplink may be a remote client transmission and the server receiving Transmission direction.
  • the resource scheduling method provided in the embodiment of the present application may be applicable to any communication scenario in which a sent data packet and a reply data packet have a corresponding relationship in content, and the reply data packet is located behind the sent data packet in the time domain.
  • one party sends an operation instruction, and the other party executes the operation instruction and returns an execution result.
  • one party sends a service request, and the other party responds to the service request.
  • the resource scheduling method includes S201-S206:
  • the first device delivers scheduling information of a downlink channel and scheduling information of an uplink channel to a second device.
  • the second device receives scheduling information of the downlink channel and scheduling information of the uplink channel issued by the first device.
  • the uplink channel is located behind the downlink channel in the time domain.
  • a downlink channel includes a physical downlink shared channel PDSCH, and scheduling information of the downlink channel includes an index of the PDSCH.
  • the PDSCH index can also be used to determine the resource configuration type, start symbol, and number of symbols of the PDSCH.
  • a correspondence table between the PDSCH index and all PDSCH scheduling information may be pre-stored locally on the second device, such as a correspondence table of resource configuration types, start time slots, start symbols, and number of symbols of the PDSCH.
  • the second device may The received PDSCH index queries the PDSCH scheduling information. Since the correspondence between the PDSCH index and the PDSCH scheduling information is the prior art, it will not be described in detail in this embodiment of the present application.
  • the uplink channel may include a physical uplink shared channel PUSCH.
  • PUSCH scheduling information may also include PUSCH index, resource configuration type, starting time slot, and starting number. Symbols and number of symbols.
  • Table 1 shows the 16 types of resource allocation schemes for PUSCH in the extended cyclic prefix (ECP) scenario.
  • ECP extended cyclic prefix
  • columns 1 to 5 are the PUSCH index, the resource configuration type, and the preset slot offset from the PDSCH (used to use the PDSCH starting slot as a reference to determine the starting of the PUSCH Start time slot), the start symbol, and the number of symbols.
  • the preset time slot offset between PUSCH and PDSCH can be determined according to Table 2.
  • Table 2 shows the correspondence between the preset slot offset between the PUSCH and the PDSCH and the frame format indication of the PUSCH.
  • the time domain resources of the PUSCH may be determined according to one of the above uplink scheduling information one to three.
  • the PUSCH may include one or more consecutive symbols, and the resource allocation type may be one of type A (type A) and type B (type B).
  • the starting symbol refers to the first symbol included in the PUSCH.
  • the start slot refers to the slot where the first symbol included in the PUSCH is located, and the number of symbols refers to the number of symbols included in the PUSCH.
  • the type A and type B of the resource configuration type are the prior art, they are not described in the embodiment of the present application.
  • each time slot contains 12 symbols, and it is assumed that time slot 5 is the starting time slot. It is explained in detail how to determine the scheduled PUSCH resources according to Table 1 and Table 2.
  • An example of the behavior is a row with an index of 1 in Table 1 and a frame format of 2 in Table 2.
  • the frame format is indicated as 2, and the corresponding j is equal to 2. That is, the preset slot offset between PUSCH and PDSCH in Table 1 is 2, and the starting slot of PUSCH is slot 7. (PDSCH start slot +2).
  • the resource allocation type of the PUSCH is type A, the starting symbol is symbol 0, and the number of symbols is 8, that is, the last symbol is symbol 7. It can be known from the foregoing analysis that the scheduled PUSCH resources are symbols 0 to 7 of slot 7, and the resource configuration type is type A.
  • An example of the behavior is a row with an index of 14 in Table 1 and a frame format indication of 0 in Table 2.
  • the frame format indication is 0, and its corresponding j is equal to 1. That is, the preset slot offset between PUSCH and PDSCH in Table 1 is 1.
  • the starting slot of PUSCH is slot 6. (PDSCH start slot +1).
  • the resource allocation type of the PUSCH is type B, the starting symbol is symbol 8, and the number of symbols is 4, that is, the last symbol is symbol 11. It can be known from the above analysis that the scheduled PUSCH resources are symbols 8 to 11 of slot 6 and the resource configuration type is type B.
  • Tables 1 and 2 may be stored in a storage space of the first device and / or the second device in a form of a configuration file, an electronic form, or the like.
  • the first device may send the index, resource configuration type, start time slot, start symbol, and number of symbols in the scheduling information of the PUSCH to the second device in different ways.
  • the uplink channel scheduling information includes one of the following uplink scheduling information:
  • Uplink scheduling information 1 the first index of the PUSCH.
  • the first index may be the index shown in the first column in Table 1.
  • the second device may query the local pre-stored correspondence shown in Table 1 and Table 2 according to the first index to obtain the PUSCH corresponding to the first index. Resource allocation type, start time slot, start symbol, and number of symbols.
  • Uplink scheduling information 2 PUSCH second index and starting time slot.
  • the second index may be the index shown in the first column in Table 1.
  • the second device may query the local pre-stored correspondence shown in Table 1 and Table 2 according to the second index to obtain the PUSCH resource configuration type, Starting symbol and number of symbols.
  • Uplink scheduling information 3 resource allocation type, starting time slot, starting symbol, and number of symbols of the PUSCH.
  • a correspondence table between the first index shown in Table 1 and Table 2 and the scheduling information of the PUSCH may also be pre-stored locally on the first device.
  • the first device may first determine PUSCH scheduling information according to the correspondence table, and then directly send the determined scheduling information to the second device through a form such as RRC signaling, instead of issuing the first corresponding to the PUSCH scheduling information.
  • Index or secondary index may be pre-stored locally on the first device.
  • the names of the above-mentioned PUSCH, PDSCH, PDCCH, and PUCCH may be different, which is not limited in the embodiments of the present application.
  • the starting time slot of the PUSCH may be determined by using one of the following timing relationships, respectively:
  • the scheduling information of the PDSCH may include a start slot of the PDSCH. Therefore, in a possible design method, the starting time slot of the PDSCH can be determined as a reference to determine the starting time slot of the PUSCH.
  • the PUSCH and the PDSCH can satisfy the first preset condition in the time domain.
  • the first preset condition may be:
  • n PDSCH is the start time slot of PDSCH
  • n PUSCH is the start time slot of PUSCH
  • ⁇ PDSCH is the frame format indication of PDSCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • K 2 is the preamble between PUSCH and PDSCH.
  • the uplink channel may also include a physical uplink control channel PUCCH. Therefore, in another possible design method, the starting time slot of the PUSCH can also be determined as a reference to determine the starting time slot of the PUSCH.
  • the PUSCH and PUCCH satisfy the second preset condition in the time domain.
  • the second preset condition may be:
  • n PUSCH is the start time slot of PUSCH
  • n PUCCH1 is the start time slot of PUCCH
  • ⁇ PUSCH is the frame format indication of PUSCH
  • ⁇ PUCCH1 is the frame format indication of PUCCH
  • K 3 is the preamble between PUSCH and PUCCH.
  • the starting time slot of the PDCCH of the PUSCH scheduling information may also be sent as a reference to determine the starting time slot of the PUSCH.
  • the scheduling information of the PUSCH is delivered on the first PDCCH (ie, PDCCH1 shown in FIG. 3C), and then the PUSCH and the first PDCCH satisfy the following preset conditions in the time domain:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PUSCH is the start time slot of the PUSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PUSCH is the frame format indication of the PUSCH
  • K 4 is the PUSCH and the first time slot.
  • the start time slots of the PUSCH determined according to the foregoing three timing relationships are all located after the corresponding PDSCH.
  • the PDSCH and the first PDCCH satisfy a third preset condition in the time domain.
  • the third preset condition may be:
  • n PDCCH1 is the start time slot of the first PDCCH
  • n PDSCH is the start time slot of the PDSCH
  • ⁇ PDCCH1 is the frame format indication of the first PDCCH
  • ⁇ PDSCH is the frame format indication of the PDSCH
  • K 0 is the PDSCH and the first time slot.
  • K 0 ⁇ K 4 needs to be satisfied to ensure that the PUSCH is located behind the PDSCH in the time domain.
  • FIG. 3A to FIG. 3C respectively show a timing relationship between a start slot of a PUSCH and a PDSCH, a PUCCH, and a PDCCH which are referenced, and there is no limitation on a manner of sending PUSCH scheduling information.
  • the PDSCH scheduling information is all delivered on one PDCCH (such as the first PDCCH in FIGS. 4A to 4D).
  • the PUSCH scheduling information can be delivered in one of the following four delivery modes:
  • the first device delivering the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device may be specifically implemented as:
  • the first device sends the PDSCH index and the PUSCH index to the second device on the first PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as:
  • the second device receives the index of the PDSCH and the first index of the PUSCH issued by the first device on the first PDCCH.
  • the DCI format carried by the first PDCCH may include two Time domain resource assignment fields, which are respectively used to carry an index of the PDSCH and a first index of the PUSCH.
  • the first device sends the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device, which may be specifically implemented as the following steps 1 and 2:
  • Step 1 The first device sends the first radio link control RRC signaling to the second device, where the first RRC signaling carries a starting time slot of the PUSCH;
  • Step 2 The first device sends the PDSCH index and the second PUSCH index to the second device on the first PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as step three and step four:
  • Step 3 The first device sends the first radio link control RRC signaling to the second device, where the first RRC signaling carries a starting time slot of the PUSCH;
  • Step 4 On the first PDCCH, the second device receives the index of the PDSCH and the second index of the PUSCH issued by the first device.
  • the start slot of the PUSCH is carried on the first RRC signaling, and the index of the PDSCH and the second index of the PUSCH are carried on the first PDCCH.
  • step 1 and step 3 may be performed first, then step 2 and step 4 may be performed, and step 2 and step 4 may be performed first, and then step 1 and step 3 may be performed, which is not limited in the embodiment of the present application.
  • RRC signaling is a prior art, this embodiment of the present application will not go into details.
  • the second index of the PUSCH carried by the first PDCCH is only used to determine the resource configuration type, starting symbol, and number of symbols of the PUSCH, and the starting slot of the PUSCH is carried by the first RRC signaling .
  • the first device sends the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device, which can be specifically implemented as step 5 and step 6:
  • Step 5 The first device sends the PDSCH index to the second device on the first PDCCH.
  • Step 6 The first device sends the second RRC signaling to the second device.
  • the second RRC signaling carries a resource configuration type, starting time slot, number of symbols, and starting symbol of the PUSCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may be specifically implemented as step 7 and step 8:
  • Step 7 The second device receives the index of the PDSCH issued by the first device on the first PDCCH.
  • Step 8 The second device receives the second RRC signaling issued by the first device.
  • the second RRC signaling carries the resource configuration type, starting time slot, number of symbols, and starting symbol of the PUSCH.
  • step 5 and step 7 may be performed first, then step 6 and step 8 may be performed, or step 6 and step 8 may be performed first, and then step 5 and step 7 may be performed, which is not limited in the embodiment of the present application.
  • the resource configuration type, starting slot, number of symbols, and starting symbol of the PUSCH are all carried on the second RRC signaling, and the index of the PDSCH is carried on the first PDCCH.
  • the first device may issue the PDSCH index corresponding to the PDSCH scheduling information through the first PDCCH, and pass the PUSCH scheduling information through the second RRC signaling. Issued.
  • the existing protocol stipulates that the DCI format carried by the PDCCH only includes a Time domain resource assignment field.
  • the scheduling information of the PUSCH is directly delivered through the second RRC signaling, and there is no need to change the relevant provisions of the DCI format of the existing protocol, and conflicts with the existing protocol can be avoided.
  • the scheduling information of the downlink channel and the scheduling information of the uplink channel may also be separately delivered through two different PDCCHs. Therefore, the first device sending the scheduling information of the downlink channel and the scheduling information of the uplink channel to the second device may include step 9 and step 10:
  • Step 9 The first device sends scheduling information of the downlink channel to the second device on the first physical downlink control channel PDCCH.
  • Step 10 The first device sends the scheduling information of the uplink channel to the second device on the second PDCCH. There is a preset binding relationship between the first PDCCH and the second PDCCH.
  • the second device receiving the scheduling information of the downlink channel and the scheduling information of the uplink channel issued by the first device may include steps 11 and 12:
  • Step 11 The second device receives scheduling information of the downlink channel issued by the first device on the first physical downlink control channel PDCCH.
  • Step 12 The second device receives, on the second PDCCH, scheduling information of an uplink channel issued by the first device.
  • the downlink channel may be PDSCH
  • the uplink channel may be PUSCH
  • the uplink channel may also be PUSCH and PUCCH, which are not limited in the embodiment of the present application.
  • the first PDCCH carries an index of a PDSCH
  • the second PDCCH carries a first index of a PUSCH.
  • the second device may determine the PDSCH according to the correspondence table between the PDSCH index and the PDSCH scheduling information that is locally stored in the second device, and the correspondence table between the first index of the PUSCH and the scheduling information of the PUSCH. Scheduling information and PUSCH scheduling information.
  • the second device receives one on the one PDCCH.
  • scheduling information another scheduling information can be targetedly received on another PDCCH that has a binding relationship, to avoid the situation that the scheduling information of the downlink channel and the uplink channel need to be blindly detected in all possible resource sets. Effectively reducing the calculation amount of receiving the scheduling information of the downlink channel and the uplink channel, thereby improving the efficiency of the second device receiving the uplink and downlink scheduling information, and further improving the efficiency of communication between the first device and the second device.
  • the preset binding relationship between the second PDCCH and the first PDCCH may include one of the following:
  • the search space to which the second PDCCH belongs corresponds to the search space to which the first PDCCH belongs
  • the control resource set CORESET to which the second PDCCH belongs corresponds to the CORESET to which the first PDCCH belongs;
  • the BWP to which the second PDCCH belongs is corresponding to the BWP to which the first PDCCH belongs;
  • the core carrier CC to which the second PDCCH belongs corresponds to the CC to which the first PDCCH belongs.
  • the scheduling information of the PDSCH may be carried in an even-numbered search space such as the search space 0, 2, 6, ... 12, and the scheduling information of the PUSCH may be carried in the search space 1, 3, 5 ... 13
  • an odd-numbered search space and starting from search space 0 there is a binding relationship between an adjacent even-numbered search space and an odd-numbered search space, that is, search space 0 is bound to search space 1, and search space 2 and search Space 3 is bound, and so on.
  • search space 0 is bound to search space 1
  • search space 2 and search Space 3 is bound, and so on.
  • the second device detects the PDSCH scheduling information in the search space 0, such as the PDSCH index, it only needs to detect the PUSCH scheduling information in the search space 1, instead of in the search space 3-13. Detecting PUSCH scheduling information in an odd-numbered search space can effectively reduce the workload of receiving PDSCH scheduling information and PUSCH scheduling information, thereby improving the efficiency of receiving PDSCH scheduling information and PUSCH scheduling information.
  • FIG. 5B shows an inclusion relationship among the search space, CORSET, BWP, and CC provided in the embodiment of the present application.
  • the first device may configure multiple CCs for the second device, each CC may be configured with multiple BWPs, each BWP may be configured with multiple CORSETs, and each CORSET may be configured with multiple search spaces, FIG. 5B N, M, K, and L in the sequence are the number of scheduled CC, BWP, CORSET, and search space.
  • the search space, CORSET, BWP, and CC can be understood as resource sets of different granularities.
  • the first device can configure a binding relationship between two different resource sets of the same granularity for the second device.
  • the second device can also detect PDSCH scheduling information and PUSCH scheduling information on two CORESETs, two BWPs, or two CCs in a binding relationship.
  • the second device may detect the scheduling information of the PDSCH and the scheduling information of the PUSCH on the BWP0 and BWP1 where the binding relationship exists.
  • search space CORESET, BWP, and CC can all be regarded as a representation manner of a resource or a resource set that may be used to carry the scheduling information of the downlink channel or the scheduling information of the uplink channel.
  • the names of the wireless communication systems may be different, which is not limited in the embodiments of the present application.
  • the first device sends a downlink data packet to the second device on the downlink channel.
  • the second device receives a downlink data packet sent by the first device on a downlink channel.
  • the first device and the second device can transmit downlink data packets on the downlink channels scheduled in the above S201 and S202.
  • the downlink data packet may carry a control instruction for controlling the second device.
  • the first device may be a master device, such as a computer in a control center
  • the second device may be a controlled device, such as a machine on a production line
  • a downlink data packet may carry a device for controlling the above-mentioned machine. Control instructions for equipment actions, such as process flow.
  • the downlink data packet may also carry a control instruction for controlling a remote terminal.
  • the first device may be a network device, such as a server
  • the second device may be a remote terminal
  • the downlink data packet may carry a preset task used to indicate that the remote terminal needs to be completed.
  • the second device reports the uplink data packet to the first device on the uplink channel.
  • the first device receives an uplink data packet reported by the second device on an uplink channel.
  • the uplink data packet corresponds to the downlink data packet. It can be understood that the content carried by the uplink data packet is the execution result reported by the second device after completing the instruction or task carried by the downlink data packet.
  • the second device may also report indication information to indicate whether the reported uplink data packet is valid.
  • the second device may encapsulate one or more bits of indication information in a media access control (MAC) layer protocol data unit (PDU).
  • MAC media access control
  • PDU media access control layer protocol data unit
  • "valid" may indicate that the second device successfully received the downlink data packet (such as the PDSCH demodulation was successful).
  • the uplink data packet reported by the second device is made based on the downlink data packet, and its content is truly valid.
  • the foregoing indication information may be encapsulated in any bit in the MAC layer PDU, such as the last bit in the MAC layer PDU header.
  • the second device may also directly map the foregoing instruction information and execution result to the physical resources of the downlink channel to complete reporting.
  • the above-mentioned indication information may be padded before the uplink data packet, and reported after physical layer resource mapping is completed, or as shown in FIG. 6C, after the PUSCH carrying the uplink data packet, Piggyback carries the PUCCH carrying the instruction information and reports it after completing the physical layer resource mapping.
  • one or more preset numerical sequences are defined to indicate that the uplink data packet is invalid.
  • a preset value such as all 0 or all 1 indicates that the uplink data packet is invalid. It can be understood that if the uplink data packet does not include the above-mentioned preset numerical sequence, it can be regarded as valid.
  • the execution result and its indication information may also be reported separately on different uplink channels.
  • the indication information may be reported on the PUCCH.
  • acknowledgement / non-acknowledgement (ACK / NACK) indication information is reported on the PUCCH, and uplink data packets are reported on the PUSCH.
  • ACK / NACK and execution results may be reported separately in any of the following ways.
  • the PUCCH is located before the PUSCH in the time domain.
  • the second device feeds back a NACK on the PUCCH, and no longer needs to send an uplink data packet on the subsequent PUSCH (because there are actually no uplink data packets to be reported), Reduce the amount of data reported by the second device.
  • the first device may also reschedule the PUSCH to other devices to improve the radio resource utilization of the first device and reduce the amount of demodulation calculation of invalid uplink data packets.
  • the second device feeds back an ACK on the PUCCH.
  • the first device can confirm that the PUSCH received later is valid, and at the same time as receiving the PUSCH, the PUSCH can be demodulated to reduce the amount of data that the first device needs to buffer, thereby reducing the The storage cost of a device.
  • the PUCCH is located after the PUSCH in the time domain.
  • the second device reports an uplink data packet on the PUSCH, and reports ACK / NACK on a subsequent PUCCH.
  • the first device needs to buffer the uplink data packet it receives on the PUSCH, and after the first device receives the indication information on the PUCCH, it determines whether to demodulate the received uplink data packet. Exemplarily, if the indication information is ACK, the received uplink data packet is demodulated; otherwise, it is directly discarded to reduce unnecessary demodulation workload.
  • the first device when the first device learns that the uplink data packet reported by the second device is invalid, it can also stop receiving the PUCCH and PUSCH reported by the second device, and dispatch the radio resources corresponding to the PUCCH and PUSCH to other devices Use to improve wireless resource utilization.
  • a downlink data packet issued by a first device and an uplink data packet reported by a second device must appear in pairs, and a downlink data packet must be issued.
  • Specific requirements before reporting uplink data packets uniform scheduling of uplink and downlink channels for downlink data packets and uplink data packets, and the scheduled uplink channels are located behind the downlink channels in the time domain, which can avoid separate downlink data in the above specific scenarios.
  • the problem that the downlink channel and the uplink channel independently scheduled by the packet and the uplink data packet cannot meet specific requirements and conflicts can improve the reliability of communication between the first device and the second device.
  • FIG. 7 shows a possible structural diagram of a first device involved in the foregoing method embodiment.
  • the first device 700 includes a sending module 701 and a receiving module 702.
  • the sending module 701 is configured to send scheduling information of a downlink channel and scheduling information of an uplink channel to a second device.
  • the uplink channel is located behind the downlink channel in a time domain.
  • the sending module 701 is further configured to send a downlink data packet to a second device on a downlink channel;
  • the receiving module 702 is configured to receive an uplink data packet reported by a second device on an uplink channel.
  • the first device 700 corresponds completely to the first device in the foregoing method embodiment, and a corresponding unit of the first device 700 is configured to perform a corresponding step performed by the first device in the foregoing method embodiment.
  • the sending module 701 in the first device is configured to execute the steps sent by the first device in the method embodiment, such as executing S201 or S203 in FIG. 2.
  • the receiving module 702 is configured to execute the steps received by the first device in the method embodiment, such as executing S206 in FIG. 2.
  • the sending module 701 and the receiving module 702 may constitute a transceiver unit and have functions of receiving and sending at the same time.
  • the receiving module 702 may be a receiver.
  • the sending module 701 may be a transmitter.
  • the receiver and transmitter can be integrated to form a transceiver.
  • FIG. 8 shows a possible structural diagram of a second device involved in the foregoing method embodiment.
  • the second device 800 includes a sending module 801 and a receiving module 802.
  • the receiving module 802 is configured to receive scheduling information of a downlink channel and scheduling information of an uplink channel issued by a first device; wherein the uplink channel is located behind the downlink channel in a time domain;
  • the receiving module 802 is further configured to receive a downlink data packet delivered by a first device on a downlink channel;
  • a sending module 801 is configured to report an uplink data packet to a first device on an uplink channel.
  • the second device 800 corresponds completely to the second device in the foregoing method embodiment, and a corresponding unit of the second device 800 is configured to perform a corresponding step performed by the second device in the foregoing method embodiment.
  • the sending module 801 in the second device is configured to execute the steps sent by the second device in the method embodiment, such as executing S205 in FIG. 2.
  • the receiving module 802 is configured to execute the steps received by the second device in the method embodiment, such as executing S202 or S204 in FIG. 2.
  • the sending module 801 and the receiving module 802 may constitute a transceiver unit and have functions of receiving and sending at the same time.
  • the receiving module 802 may be a receiver.
  • the sending module 801 may be a transmitter.
  • the receiver and transmitter can be integrated to form a transceiver.
  • FIG. 9 shows another possible structure diagram of the first device involved in the foregoing method embodiment.
  • the first device 900 includes a processor 901 and a communication interface 902.
  • the processor 901 is configured to control and manage the actions of the first device.
  • the processor 901 is configured to control the communication interface 902 to support communication between the first device and other network entities.
  • the first device may further include a memory 903 and a bus 904.
  • the memory 903 is configured to store program code and data of the first device.
  • the processor 901 may be a processor or a controller in the first device, and the processor or the controller may implement or execute various exemplary logical blocks, modules, and circuits described in combination with the disclosure of the present application.
  • the processor or controller may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication interface 902 may be a transceiver, a transceiver circuit, or a communication interface in the first device.
  • the memory 903 may be a memory in the first device, etc.
  • the memory may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk, or a solid state memory. Hard disk; the memory may also include a combination of the above types of memory.
  • the bus 904 may be an extended industry standard architecture (EISA) bus or the like.
  • the bus 904 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10 shows another schematic structural block diagram of a first device 900 applicable to an embodiment of the present application.
  • the first device 900 includes: one or more processors 901, one or more transceivers 905, and one or more memories 903.
  • the processor 901 is used to control the transceiver 905 to send and receive signals
  • the memory 903 is used to store a computer program
  • the processor 901 is used to call and run the computer program from the memory 903 to execute the resource scheduling method provided by the embodiment of the present application, and each Corresponding processes and / or operations performed by the first device in the embodiment.
  • FIG. 11 shows still another possible structural diagram of the second device involved in the foregoing embodiment.
  • the second device includes: a processor 1101 and a communication interface 1102.
  • the processor 1101 is configured to control and manage the action of the second device.
  • the processor 1101 is configured to control the communication interface 1102 to support communication between the second device and other network entities.
  • the receiving module 802 and the sending module 801 are executed.
  • the second device may further include a memory 1103 and a bus 1104.
  • the memory 1103 is configured to store program code and data of the second device.
  • the processor 1101 may be a processor or a controller in a second device, and the processor or the controller may implement or execute various exemplary logical blocks, modules, and circuits described in combination with the disclosure of the present application.
  • the processor or controller may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication interface 1102 may be a transceiver, a transceiver circuit, a communication interface, or the like in the second device.
  • the memory 1103 may be a memory in the second device, etc.
  • the memory may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk, or a solid state memory. Hard disk; the memory may also include a combination of the above types of memory.
  • the bus 1104 may be an EISA bus or the like.
  • the bus 1104 can be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only a thick line is used in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • FIG. 12 shows another schematic structural block diagram of a second device 1100 applicable to an embodiment of the present application.
  • the second device 1100 includes: one or more processors 1101, one or more transceivers 1105, and one or more memories 1103.
  • the processor 1101 is configured to control the transceiver 1105 to send and receive signals
  • the memory 1103 is configured to store a computer program
  • the processor 1101 is configured to call and run the computer program from the memory 1103 to execute the resource scheduling method provided by the embodiment of the present application, Corresponding processes and / or operations performed by the first device in the embodiment.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores computer instructions.
  • the computer instructions When the computer instructions are run on a computer, the computer executes the resource scheduling method and the resource scheduling method provided in the embodiments of the present application and the method. Corresponding operations and / or processes performed by the first device or the second device in each embodiment.
  • the present application also provides a computer program product.
  • the computer program product includes computer program code.
  • the computer program code When the computer program code is run on a computer, the computer causes the computer to execute the resource scheduling method provided by the embodiments of the present application and the methods provided by the first embodiment. Corresponding operations and / or processes performed by a device or a second device.
  • the present application also provides a chip, including a processor.
  • the processor is configured to read and run a computer program stored in the memory to execute the resource scheduling method provided in the embodiments of the present application and corresponding operations and / or processes performed by the first device or the second device in each embodiment.
  • the chip may further include a memory, which is connected to the processor through a circuit or a wire, and the processor is configured to read and execute a computer program in the memory.
  • the memory may be a memory inside the chip or a memory located outside the chip and connected to the chip through a circuit or a wire, which is not limited in the embodiment of the present application.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is configured to receive data and / or information to be processed, and the processor obtains the data and / or information from the communication interface and processes the data and / or information.
  • the communication interface may be a transceiver or an input / output interface.
  • An embodiment of the present application provides a communication system.
  • the communication system may include a first device and a second device, and is configured to execute a resource scheduling method provided by the embodiment of the present application.
  • a resource scheduling method provided by the embodiment of the present application.
  • the processor in the embodiment of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and special-purpose integrations.
  • Circuit application specific integrated circuit, ASIC
  • ready-made programmable gate array field programmable gate array, FPGA
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access Access memory
  • double SDRAM double SDRAM
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced SDRAM
  • SLDRAM synchronous connection dynamic random access memory Fetch memory
  • direct RAMbus RAM direct RAMbus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware (such as a circuit), firmware, or any other combination.
  • the above embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like, including one or more sets of available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium.
  • the semiconductor medium may be a solid state drive.
  • At least one means one or more, and “multiple” means two or more.
  • At least one or more of the following or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • at least one (a) of a, b, or c can be expressed as: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • first and second are used to distinguish different objects, or to distinguish different processes on the same object, rather than to describe a specific order of the objects.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be construed as more preferred or more advantageous than other embodiments or designs. Rather, the use of the words "exemplary” or “for example” is intended to present the relevant concept in a concrete manner.
  • the size of the sequence numbers of the above processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not deal with the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

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

Abstract

本申请公开了一种资源调度方法及设备，涉及通信领域，能够解决工业控制、人工智能等场景下，第一设备为第二设备独立调度下行信道和上行信道，可能导致上行信道在时域上位于下行信道之前，第二设备无法根据下行信道下发的下行数据包，在上行信道上上报上行数据包，从而导致第一设备与第二设备通信的可靠性较差的问题。该方法包括：第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息；其中，所述上行信道在时域上位于所述下行信道之后；所述第一设备在所述下行信道上向所述第二设备下发下行数据包；所述第一设备在所述上行信道上接收所述第二设备上报的上行数据包。

Description

资源调度方法及设备
本申请要求于2018年09月20日提交国家知识产权局、申请号为201811102163.5、申请名称为“资源调度方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种资源调度方法及设备。
背景技术
在某些特定应用场景中，如工业控制4.0，通常要求发送的数据包与接收的数据包成对出现。示例性地，如图1所示，第一设备向第二设备下发控制指令(set points)，并接收第二设备在执行上述控制指令之后上报的第二设备的设备状态(actual value)。其中，设备状态与控制指令具有对应关系，且上报设备状态需要在下发控制指令之后执行。可以理解，上述控制过程可以通过无线通信技术，如新空口(new radio，NR)实现。
示例性地，第一设备，如NR系统中的基站gNB，可以通过物理下行控制信道(physical downlink control channel，PDCCH)承载的两个下行控制信息(downlink control information，DCI)，为控制指令下发和设备状态上报分别调度无线资源。例如，通过DCI0调度用于设备状态上报的物理上行共享信道(physical uplink shared channel，PUSCH)，如一个或多个PUSCH符号，通过DCI1调度用于控制指令下发的物理下行共享信道(physical downlink shared channel，PDSCH)，如一个或多个PDSCH符号。
然而，上述PUSCH和PDSCH均是独立调度的，可能导致调度的PUSCH在时域上位于PDSCH之前，从而导致第二设备无法根据PDSCH承载的控制指令的执行结果，在PUSCH上上报第二设备的设备状态的情况。也就是说，独立调度的PDSCH和PUSCH可能冲突，从而导致第一设备与第二设备通信的可靠性较差。
发明内容
本申请的实施例提供一种资源调度方法及设备，以解决现有技术中存在的第一设备与第二设备之间的通信可靠性较差的问题。
为达到上述目的，本申请提供如下技术方案：
第一方面，提供一种资源调度方法。该资源调度方法包括：第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息。然后，第一设备在下行信道上向第二设备下发下行数据包。之后，第一设备在上行信道上接收第二设备上报的上行数据包。其中，上行信道在时域上位于下行信道之后。
第二方面，提供一种资源调度方法。该资源调度方法包括：第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息。然后，第二设备在下行信道上 接收第一设备下发的下行数据包。之后，第二设备在上行信道上向第一设备上报上行数据包。其中，上行信道在时域上位于下行信道之后。
本申请提供的资源调度方法，能够根据工业控制、人工智能等场景下第一设备下发的下行数据包与第二设备上报的上行数据包必须成对出现，且下发下行数据包必须在上报上行数据包之前的特定需求，为下行数据包和上行数据包统一调度上行信道和下行信道，且调度的上行信道在时域上位于下行信道之后，以避免上述场景下分别为下行数据包和上行数据包独立调度的下行信道和上行信道不能满足特定需求而冲突的问题，能够提高第一设备与第二设备通信的可靠性。
需要说明的是，第一方面提供的资源调度方法和第二方面提供的资源调度方法，依次为工业控制场景、人工智能等场景下请求方和响应方所执行的方法流程。
可以理解，本申请提供的资源调度方法并不仅限于上述场景。事实上，本申请提供的资源调度方法可以适用于发送的数据包与回复的数据包在内容上具有对应关系、且回复的数据包在时域上位于发送的数据包之后的任何通信场景。例如，一方发送操作指令，另一方执行所述操作指令并回复执行结果。又例如，一方发送业务请求，另一方响应该业务请求。
示例性地，以NR为例，下行信道包括物理下行共享信道PDSCH，下行信道的调度信息包括PDSCH的索引。
需要说明的是，除起始时隙之外，PDSCH的索引还可以用于确定PDSCH的资源配置类型、起始符号和符号个数。示例性地，可以在第二设备本地预存PDSCH的索引与PDSCH的调度信息，如PDSCH的资源配置类型、起始时隙、起始符号和符号个数的对应关系表，第二设备可以根据接收到的PDSCH的索引查询PDSCH的调度信息。鉴于PDSCH的索引与PDSCH的调度信息的对应关系为现有技术，本申请不再赘述。
与下行信道相对应，上行信道通常包括物理上行共享信道PUSCH，上行信道的调度信息包括如下之一的上行调度信息：
上行调度信息一：PUSCH的第一索引；其中，第一索引用于确定PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
示例性地，与PDSCH的调度信息的传输类似，第二设备在接收到PUSCH的第一索引后，可以根据第一索引与在第二设备本地预存的PUSCH的调度信息的对应关系，确定PUSCH的资源配置类型、起始时隙、起始符号和符号个数。例如，可以在第二设备本地预存第一索引与在其本地预存的PUSCH的调度信息的对应关系表。该对应关系表可以包括：第一索引与PUSCH的资源配置类型、起始时隙、起始符号和符号个数的对应关系。其中，在时域上，PUSCH可以包含一或多个连续符号，资源配置类型可以为类型A(type A)和类型B(type B)中的一种，起始符号是指PUSCH包含的首个符号，起始时隙是指PUSCH包含的首个符号所在时隙，符号个数是指PUSCH包含的符号的个数。
上行调度信息二：PUSCH的第二索引和起始时隙；其中，第二索引用于确定PUSCH的资源配置类型、起始符号和符号个数。
示例性地，PUSCH的起始时隙可以单独配置，如通过RRC信令配置，而PUSCH的其他3个调度信息仍然通过索引方式，即根据第二索引与在第二设备本地预存的 PUSCH的调度信息的对应关系确定。鉴于第二索引与第一索引类似，本申请不再赘述。
上行调度信息三：PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
示例性地，也可以在第一设备本地预存上述第一索引或第二索引与PUSCH的调度信息的对应关系表。第一设备可以首先根据该对应关系表确定PUSCH的调度信息，然后将确定的调度信息通过诸如RRC信令等形式直接下发给第二设备。
需要说明的是，对于不同制式的无线通信系统，上述PUSCH、PDSCH、PDCCH和PUCCH的名称可能不同，本申请对此不做限定。
示例性地，PDSCH的调度信息可以包括PDSCH的起始时隙。因此，在一种可能的设计方法中，可以PDSCH的时域位置作为参考确定PUSCH的时域位置。例如，PUSCH与PDSCH在时域上可以满足第一预设条件。其中，第一预设条件可以为：
Figure PCTCN2019105481-appb-000001
其中，n PDSCH为PDSCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDSCH为PDSCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 2为PUSCH与PDSCH之间的预设时隙偏移量。
实际应用中，上行信道还可以包括物理上行控制信道PUCCH。因此，在另一种可能的设计方法中，也可以PUCCH的时域位置作为参考确定PUSCH的时域位置。例如，PUSCH与PUCCH在时域上满足第二预设条件。其中，第二预设条件可以为：
Figure PCTCN2019105481-appb-000002
其中，n PUSCH为PUSCH的起始时隙，n PUCCH1为PUCCH的起始时隙，μ PUSCH为PUSCH的帧格式指示，μ PUCCH1为PUCCH的帧格式指示，K 3为PUSCH与PUCCH之间的预设时隙偏移量。
可选地，PDSCH与第一PDCCH在时域上满足第三预设条件。其中，第三预设条件可以为：
Figure PCTCN2019105481-appb-000003
其中，n PDCCH1为第一PDCCH的起始时隙，n PDSCH为PDSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PDSCH为PDSCH的帧格式指示，K 0为PDSCH与第一PDCCH之间的预设时隙偏移量。
可选地，PUSCH与第一PDCCH在时域上满足第四预设条件。其中，第四预设条件可以为：
Figure PCTCN2019105481-appb-000004
其中，n PDCCH1为第一PDCCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 4为PUSCH与第一PDCCH之间的预设时隙偏移量。
需要说明的是，根据上述第一预设条件、第二预设条件、第三预设条件和第四预设条件可知：调度的上行信道PUSCH均在时域上位于调度的下行信道PDSCH之后， 可以满足上述特定场景下的需求。
针对上述3种上行调度信息，可以分别采用如下3种方式传输上行信道的调度信息：
传输方式一
传输方式一与上行调度信息一相对应。示例性地，第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为：
第一设备在第一PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第一索引。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为：
第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第一索引。
示例性地，可以在第一PDCCH上联合动态调度PDSCH和PUSCH。其中，第一PDCCH承载的DCI格式可以同时包含两个Time domain resource assignment字段，分别用于承载PDSCH的索引和PUSCH的第一索引。
传输方式二
传输方式二与上行调度信息二相对应。示例性地，第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为如下步骤一和步骤二：
步骤一、第一设备向第二设备下发第一无线链路控制RRC信令；其中，第一RRC信令承载有PUSCH的起始时隙；
步骤二、第一设备在第一PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第二索引。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤三和步骤四：
步骤三、第一设备向第二设备下发第一无线链路控制RRC信令；其中，第一RRC信令承载有PUSCH的起始时隙；
步骤四、第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第二索引。
需要说明的是，与第一索引不同，第一PDCCH承载的PUSCH的第二索引只用于确定PUSCH的资源配置类型、起始符号和符号个数，而PUSCH的起始时隙由第一RRC信令承载。
传输方式三
传输方式三与上行调度信息三相对应。示例性地，第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤五和步骤六：
步骤五、第一设备在第一PDCCH上，向第二设备下发PDSCH的索引；
步骤六、第一设备向第二设备下发第二RRC信令；其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤七和步骤八：
步骤七、第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引；
步骤八、第二设备接收第一设备下发的第二RRC信令；其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
现有协议规定：PDCCH承载的DCI格式只包含一个Time domain resource assignment字段。为了避免与现有协议冲突，还可以由第一设备确定PUSCH的调度信息后，通过第二RRC信令直接下发。
此外，为了避免与现有协议冲突，在另一种可能的设计方法中，下行信道的调度信息和上行信道的调度信息也可以通过2个不同的PDCCH分别下发。示例性地，第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以包括步骤九和步骤十：
步骤九、第一设备在第一物理下行控制信道PDCCH上，向第二设备下发下行信道的调度信息。
步骤十、第一设备在第二PDCCH上，向第二设备下发上行信道的调度信息。其中，第三PDCCH与第二PDCCH之间存在预设绑定关系。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以包括步骤十一和步骤十二：
步骤十一、第二设备在第一物理下行控制信道PDCCH上，接收第一设备下发的下行信道的调度信息。
步骤十二、第二设备在第二PDCCH上，接收第一设备下发的上行信道的调度信息。其中，第三PDCCH与第二PDCCH之间存在预设绑定关系。
可选地，为了提高下行信道的调度信息和上行信道的调度信息的接收效率，第二PDCCH与第一PDCCH之间通常存在预设绑定关系，以便第二设备在上述一个PDCCH上接收到一个调度信息时，可以在存在绑定关系的另一个PDCCH上有针对性地接收另一个调度信息，以避免下行信道和上行信道的调度信息均需要在所有可能的资源集合中盲检的情况，能够有效降低接收下行信道和上行信道的调度信息的计算量，从而提高第二设备接收上下行调度信息的效率，进而提高第一设备与第二设备通信的效率。
其中，第二PDCCH与第一PDCCH之间的预设绑定关系，可以包括如下之一：第二PDCCH所属搜索空间(serch space)与第一PDCCH所属搜索空间具有对应关系；第二PDCCH所属控制资源集合(control resource set，CORESET)与第一PDCCH所属CORESET具有对应关系；第二PDCCH所属带宽部分(bandwidth part，BWP)与第一PDCCH所属BWP具有对应关系；第二PDCCH所属核心载波(core carrier，CC)与第一PDCCH所属CC具有对应关系。
可以理解，与搜索空间类似，第二设备也可以在存在绑定关系的两个CORESET、或两个BWP或两个CC上检测PDSCH的调度信息和PUSCH的调度信息，本申请实施例不再赘述。
需要说明的是，上述搜索空间、CORESET、BWP和CC均可以视为一种可能用于承载上述下行信道的调度信息或上行信道的调度信息的资源或资源集合的表述方式，且对于不同制式的无线通信系统，上述名称可能不同，本申请实施例对此不做限定。
在一种可能的设计方法中，上行数据包与下行数据包具有对应关系，可以理解为 上行数据包承载的内容是第二设备完成下行数据包承载的指令或任务之后上报的执行结果。
可选地，为了便于第一设备接收上行数据包的效率，第二设备还可以上报指示信息，用于指示上报的上行数据包是否有效。
可选地，第二设备可以在媒体接入控制(media accesscontrol，MAC)层协议数据单元(protocol data unit，PDU)中封装一或多比特(bit)指示信息。例如，可以用二进制数字1表示有效，用二进制数字0表示无效。
可选地，第二设备也可以将上述比特位与执行结果直接映射至下行信道的物理资源上完成上报。
可选地，第二设备还可以不上报单独的指示信息，而是上报一个预设数值序列来表示上行数据包无效。例如，以全0或全1等预设数值表示上行数据包无效。可以理解，若上行数据包不包含上述预设数值序列，则可以视为上行数据包有效。
可选地，第二设备还可以在不同的上行信道上分别上报上行数据包和指示信息。例如，在PUSCH上报上行数据包，在PUCCH上上报指示信息。其中，指示信息可以为确认/非确认(acknowledgement/non-acknowledgement，ACK/NACK)。
方式一：PUCCH在时域上位于PUSCH之前。一方面，当对应的PDSCH解调失败时，第二设备在PUCCH上反馈NACK，且不再需要在随后的PUSCH上上报上行数据包(因为实际上不存在上行数据包)，以减少第二设备上报的数据量。相应地，第一设备接收到NACK后，也可以将该PUSCH重新调度给其他设备使用，以提高第一设备的无线资源利用率，且可以降低无效的上行数据包的解调计算量。
另一方面，当对应的PDSCH解调成功时，第二设备在PUCCH上反馈ACK。相应地，第一设备接收到ACK后，可以确认之后收到的PUSCH有效，并可以在接收到PUSCH的同时，即可对PUSCH解调，以减少第一设备需要缓存的数据量，从而降低第一设备的存储成本。
方式二：PUCCH在时域上位于PUSCH之后。具体地，第二设备在PUSCH上上报上行数据包，且在随后的PUCCH上上报ACK/NACK。相应地，第一设备需要先缓存其在PUSCH接收到的上行数据包，当第一设备在PUCCH上接收到指示信息后，再确定是否对接收到的上行数据包进行解调。例如，若指示信息为ACK，则对接收到的上行数据包解调，否则，直接丢弃，以减少不必要的解调工作量。
第三方面，提供一种第一设备，包括：发送模块，用于向第二设备下发下行信道的调度信息和上行信道的调度信息，以及在下行信道上向第二设备下发下行数据包。接收模块，用于在上行信道上接收第二设备上报的上行数据包。其中，上行信道在时域上位于下行信道之后。
示例性地，下行信道包括物理下行共享信道PDSCH，下行信道的调度信息包括PDSCH的索引。上行信道包括物理上行共享信道PUSCH，上行信道的调度信息包括如下之一：PUSCH的第一索引；其中，第一索引用于确定PUSCH的资源配置类型、起始时隙、起始符号和符号个数；PUSCH的第二索引和起始时隙；其中，第二索引用于确定PUSCH的资源配置类型、起始符号和符号个数；PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
在一种可能的设计中，PUSCH与PDSCH在时域上满足第一预设条件：
Figure PCTCN2019105481-appb-000005
其中，n PDSCH为PDSCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDSCH为PDSCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 2为PUSCH与PDSCH之间的预设时隙偏移量。
可选地，上行信道还可以包括物理上行控制信道PUCCH。在另一种可能的设计中，PUSCH与PUCCH在时域上满足第二预设条件：
Figure PCTCN2019105481-appb-000006
其中，n PUSCH为PUSCH的起始时隙，n PUCCH1为PUCCH的起始时隙，μ PUSCH为PUSCH的帧格式指示，μ PUCCH1为PUCCH的帧格式指示，K 3为PUSCH与PUCCH之间的预设时隙偏移量。
在一种可能的设计中，发送模块，还用于在第一物理下行控制信道PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第一索引。其中，PDSCH与第一PDCCH在时域上满足第三预设条件：
Figure PCTCN2019105481-appb-000007
其中，n PDCCH1为第一PDCCH的起始时隙，n PDSCH为PDSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PDSCH为PDSCH的帧格式指示，K 0为PDSCH与第一PDCCH之间的预设时隙偏移量。
在另一种可能的设计中，发送模块，还用于向第二设备下发第一无线链路控制RRC信令，以及在第一PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第二索引。其中，第一RRC信令承载有PUSCH的起始时隙。
在另一种可能的设计中，发送模块，还用于向第二设备下发第二RRC信令，以及在第一PDCCH上，向第二设备下发PDSCH的索引。其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
在另一种可能的设计中，发送模块，还用于在第一物理下行控制信道PDCCH上，向第二设备下发下行信道的调度信息，以及在第二PDCCH上，向第二设备下发上行信道的调度信息。其中，第二PDCCH与第一PDCCH之间的预设绑定关系，可以包括如下之一：第二PDCCH所属搜索空间与第一PDCCH所属搜索空间具有对应关系；第二PDCCH所属控制资源集合CORESET与第一PDCCH所属CORESET具有对应关系；第二PDCCH所属带宽部分BWP与第一PDCCH所属BWP具有对应关系；第二PDCCH所属核心载波CC与第一PDCCH所属CC具有对应关系。
第四方面，提供一种第二设备，包括：接收模块，用于接收第一设备下发的下行信道的调度信息和上行信道的调度信息，以及在下行信道上接收第一设备下发的下行数据包。发送模块，用于在上行信道上向第一设备上报上行数据包。其中，上行信道在时域上位于下行信道之后。
示例性地，下行信道包括物理下行共享信道PDSCH，下行信道的调度信息包括PDSCH的索引。上行信道包括物理上行共享信道PUSCH，上行信道的调度信息包括如下之一：PUSCH的第一索引；其中，第一索引用于确定PUSCH的资源配置类型、起始时隙、起始符号和符号个数；PUSCH的第二索引和起始时隙；其中，第二索引用于确定PUSCH的资源配置类型、起始符号和符号个数；PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
在一种可能的设计中，PUSCH与PDSCH在时域上满足第一预设条件：
Figure PCTCN2019105481-appb-000008
其中，n PDSCH为PDSCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDSCH为PDSCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 2为PUSCH与PDSCH之间的预设时隙偏移量。
可选地，上行信道还可以包括物理上行控制信道PUCCH。在另一种可能的设计中，PUSCH与PUCCH在时域上满足第二预设条件：
Figure PCTCN2019105481-appb-000009
其中，n PUSCH为PUSCH的起始时隙，n PUCCH1为PUCCH的起始时隙，μ PUSCH为PUSCH的帧格式指示，μ PUCCH1为PUCCH的帧格式指示，K 3为PUSCH与PUCCH之间的预设时隙偏移量。
在一种可能的设计中，接收模块，还用于在第一物理下行控制信道PDCCH上，接收第一设备下发的PDSCH的索引。其中，PDSCH与第一PDCCH在时域上满足第三预设条件：
Figure PCTCN2019105481-appb-000010
其中，n PDCCH1为第一PDCCH的起始时隙，n PDSCH为PDSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PDSCH为PDSCH的帧格式指示，K 0为PDSCH与第一PDCCH之间的预设时隙偏移量。
在一种可能的设计中，接收模块，还用于在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第一索引。
在另一种可能的设计中，接收模块，还用于接收第一设备下发的第一无线链路控制RRC信令，以及在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第二索引。其中，第一RRC信令承载有PUSCH的起始时隙。
在另一种可能的设计中，接收模块，还用于接收第一设备下发的第二RRC信令，以及在第一PDCCH上，接收第二设备下发的PDSCH的索引；其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
在另一种可能的设计中，接收模块，还用于在第一物理下行控制信道PDCCH上，接收第一设备下发的下行信道的调度信息，以及在第二PDCCH上，接收第一设备下发的上行信道的调度信息。其中，第二PDCCH与第一PDCCH之间的预设绑定关系， 可以包括如下之一：第二PDCCH所属搜索空间与第一PDCCH所属搜索空间具有对应关系；第二PDCCH所属控制资源集合CORESET与第一PDCCH所属CORESET具有对应关系；第二PDCCH所属带宽部分BWP与第一PDCCH所属BWP具有对应关系；第二PDCCH所属核心载波CC与第一PDCCH所属CC具有对应关系。
第五方面，提供一种第一设备。该第一设备包括：处理器、通信接口和存储器；其中，存储器用于存储计算机可执行指令，处理器与存储器通过总线连接，当该第一设备运行时，处理器执行存储器存储的计算机可执行指令，使得该第一设备执行如第一方面所述的资源调度方法。
第六方面，提供一种第二设备。该第二设备包括：处理器、通信接口和存储器；其中，存储器用于存储计算机可执行指令，处理器与存储器通过总线连接，当该第二设备运行时，处理器执行存储器存储的计算机可执行指令，使得该第二设备执行如第二方面所述的资源调度方法。
第七方面，提供一种通信系统，该通信系统包括上述第一设备和第二设备。
第八方面，提供一种可读存储介质，存储有程序或指令，当程序或指令在计算机上运行时，使得计算机执行如第一方面所述的资源调度方法。
第九方面，提供一种可读存储介质，存储有程序或指令，当程序或指令在计算机上运行时，使得计算机执行如第二方面所述的资源调度方法。
第十方面，提供一种计算机程序产品，其特种在于，包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行如第一方面所述的资源调度方法。
第十一方面，提供一种计算机程序产品，其特种在于，包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行如第二方面所述的资源调度方法。
本申请的实施例中，上述通信设备内各个单元模块的名称对该通信设备本身不构成限定，在实际实现中，这些单元模块可以以其他名称出现。只要各个单元模块的功能和本申请的实施例类似，即属于本申请权利要求及其等同技术的范围之内。
附图说明
图1为本申请实施例提供的资源调度方法及设备所应用的场景示意图；
图2为本申请实施例提供的资源调度方法的流程示意图；
图3A本申请实施例提供的资源调度方法所调度的PUSCH的起始时隙的示意图一；
图3B本申请实施例提供的资源调度方法所调度的PUSCH的起始时隙的示意图二；
图3C本申请实施例提供的资源调度方法所调度的PUSCH的起始时隙的示意图三；
图4A本申请实施例提供的PUSCH的调度信息的下发方式的示意图一；
图4B本申请实施例提供的PUSCH的调度信息的下发方式的示意图二；
图4C本申请实施例提供的PUSCH的调度信息的下发方式的示意图三；
图4D本申请实施例提供的PUSCH的调度信息的下发方式的示意图四；
图5A本申请实施例提供的搜索空间的示意图；
图5B本申请实施例提供的CC、BWP、CORESET和搜索空间的示意图；
图6A为本申请实施例提供的指示信息的上报方式的示意图一；
图6B为本申请实施例提供的指示信息的上报方式的示意图二；
图6C为本申请实施例提供的指示信息的上报方式的示意图三；
图6D为本申请实施例提供的指示信息的上报方式的示意图四；
图6E为本申请实施例提供的指示信息的上报方式的示意图五；
图6F为本申请实施例提供的指示信息的上报方式的示意图六；
图7为本申请实施例提供的第一设备的结构示意图一；
图8为本申请实施例提供的第二设备的结构示意图一；
图9为本申请实施例提供的第一设备的结构示意图二；
图10为本申请实施例提供的第一设备的结构示意图三；
图11为本申请实施例提供的第二设备的结构示意图二；
图12为本申请实施例提供的第二设备的结构示意图三。
具体实施方式
下面结合附图对本申请实施例提供的资源调度方法及设备进行详细地描述。
本申请实施例提供的资源调度方法可以应用于图1所示的通信系统中，该通信系统可以为第五代(5th generation，5G)移动通信系统，如NR系统，还可以为第四代(4th generation，4G)移动通信系统，如长期演进(long term evolution，LTE)系统，还可以为其他实际的移动通信系统，下一代无线保真(wireless fidelity，Wi-Fi)系统，本申请实施例不予限制。
如图1所示，该通信系统可以包含：第一设备11和第二设备12。其中，第一设备11主要用于向第二设备12下发下行数据包，接收第二设备12上报的上行数据包，以及下发用于传输下行数据包的下行信道的调度信息和用于传输上行数据包的上行信道的调度信息。相应地，第二设备12主要用于接收第一设备11下发的下行数据包，并向第一设备11上报上行数据包，以及接收用于传输下行数据包的下行信道的调度信息和用于传输上行数据包的上行信道的调度信息。其中，上行数据包与下行数据包通常成对出现。例如，在工业控制场景下，下行数据包用于携带控制第二设备12的控制指令，上行数据包用于携带第二设备12在执行上述控制指令后的设备状态。需要说明的是，图1仅为示例性架构图，除图1中所示功能单元之外，该通信系统还可以包括其他功能单元，如多个第二设备，本申请实施例对此不作限定。
上述第一设备11可以是基站，如NR系统中的gNB、LTE系统中的演进型节点(evolved Node B，eNB)、Wi-Fi系统中的接入点(access point，AP)等，也可以是支持NR、LTE、Wi-Fi等至少一种无线通信制式的控制设备，如工业控制场景和人工智能场景下用于控制其他设备的计算机、服务器等，本申请实施例对此不作限定。
上述第二设备12可以为终端，如NR系统和/或LTE系统中的用户设备(user equipment，UE)、手机，以及Wi-Fi系统中非接入点站点等，也可以是支持NR、LTE、Wi-Fi等至少一种无线通信制式的受控设备，如工业控制场景和人工智能场景下用于根据其他设备的控制指令执行具体任务的机器、远程终端等。
在无线通信系统中，“下行”是指网络设备发送、终端接收的传输方向，“上行”是指终端发送、网络设备接收的传输方向。例如，在工业控制场景下，网络设备可以为控制设备，终端可以为受控设备，“下行”可以是控制设备发送、受控设备接收的传输方向，“上行”可以是受控设备发送、控制设备接收的传输方向。又例如，在人工智能场景下，网络设备可以为服务器，终端可以为远程客户端，“下行”可以是服务器发送、 远程客户端接收的传输方向，“上行”可以是远程客户端发送、服务器接收的传输方向。
本申请实施例提供的资源调度方法可以适用于发送的数据包与回复的数据包在内容上具有对应关系、且回复的数据包在时域上位于发送的数据包之后的任何通信场景。例如，一方发送操作指令，另一方执行所述操作指令并回复执行结果。又例如，一方发送业务请求，另一方响应该业务请求。
下面以NR系统为例，详细说明本申请实施例提供的资源调度方法及设备。
为了提高第一设备与第二设备通信的可靠性，本申请实施例提供一种资源调度方法。如图2所示，该资源调度方法包括S201-S206：
S201、第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息。
S202、第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息。
其中，上行信道在时域上位于下行信道之后。
示例性地，以NR为例，下行信道包括物理下行共享信道PDSCH，下行信道的调度信息包括PDSCH的索引。
需要说明的是，除起始时隙之外，PDSCH的索引还可以用于确定PDSCH的资源配置类型、起始符号和符号个数。示例性地，可以在第二设备本地预存PDSCH的索引与PDSCH的全部调度信息，如PDSCH的资源配置类型、起始时隙、起始符号和符号个数的对应关系表，第二设备可以根据接收到的PDSCH的索引查询PDSCH的调度信息。鉴于PDSCH的索引与PDSCH的调度信息的对应关系为现有技术，本申请实施例不再赘述。
与PDSCH相对应，上行信道可以包括物理上行共享信道PUSCH。与PDSCH的调度信息包括PDSCH的索引、资源配置类型、起始时隙、起始符号和符号个数类似，PUSCH的调度信息也可以包括PUSCH的索引、资源配置类型、起始时隙、起始符号和符号个数。
表1示出了扩展循环前缀(extended cyclic prefix，ECP)场景下PUSCH的16种资源分配方案。如表1所示，第1至5列依次为PUSCH的索引、资源配置类型、与PDSCH之间的预设时隙偏移量(用于以PDSCH的起始时隙为参考，确定PUSCH的起始时隙)、起始符号和符号个数。其中，PUSCH与PDSCH之间的预设时隙偏移量可以根据表2确定。表2示出了PUSCH与PDSCH之间的预设时隙偏移量，与PUSCH的帧格式指示之间的对应关系。
在本申请实施例中，可以根据上述上行调度信息一至三中之一，确定PUSCH的时域资源。示例性地，PUSCH可以包含一或多个连续符号，资源配置类型可以为类型A(type A)和类型B(type B)中的一种，起始符号是指PUSCH包含的首个符号，起始时隙是指PUSCH包含的首个符号所在时隙，符号个数是指PUSCH包含的符号的个数。鉴于资源配置类型的类型A和类型B为现有技术，本申请实施例不再赘述。
下面以ECP场景下，每个时隙包含12个符号，假定时隙5为起始时隙，详细说明如何根据表1和表2，确定调度的PUSCH资源。
示例一
以表1中索引为1的行和表2中帧格式指示为2的行为例。如表2所示，帧格式指示为2，其对应的j等于2，即表1中PUSCH与PDSCH之间的预设时隙偏移量为2， 即PUSCH的起始时隙为时隙7(PDSCH起始时隙+2)。如表1所示，PUSCH的资源配置类型为类型A，起始符号为符号0，符号个数为8个，即最后一个符号为符号7。由上述分析可知，调度的PUSCH资源为时隙7的符号0至符号7，资源配置类型为类型A。
表1
Figure PCTCN2019105481-appb-000011
表2
帧格式指示 j
0 1
1 1
2 2
3 3
示例二
以表1中索引为14的行和表2中帧格式指示为0的行为例。如表2所示，帧格式 指示为0，其对应的j等于1，即表1中PUSCH与PDSCH之间的预设时隙偏移量为1，可知PUSCH的起始时隙为时隙6(PDSCH起始时隙+1)。如表1所示，PUSCH的资源配置类型为类型B，起始符号为符号8，符号个数为4个，即最后一个符号为符号11。由上述分析可知，调度的PUSCH资源为时隙6的符号8至符号11，资源配置类型为类型B。
在本申请实施例中，表1和表2可以采用配置文件、电子表格等形式存储在第一设备和/或第二设备的存储空间中。第一设备可以采用不同方式，向第二设备下发PUSCH的调度信息中的索引、资源配置类型、起始时隙、起始符号和符号个数。
具体地，上行信道的调度信息包括如下之一的上行调度信息：
上行调度信息一：PUSCH的第一索引。
其中，第一索引可以是表1中第1列所示的索引，第二设备可以根据第一索引查询其本地预存的如表1和表2所示的对应关系，获取第一索引对应PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
上行调度信息二：PUSCH的第二索引和起始时隙。其中，第二索引可以是表1中第1列所示的索引，第二设备可以根据第二索引查询其本地预存的如表1和表2所示的对应关系，获取PUSCH的资源配置类型、起始符号和符号个数。
上行调度信息三：PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
示例性地，也可以在第一设备本地预存如表1和表2所示的第一索引与PUSCH的调度信息的对应关系表。第一设备可以首先根据该对应关系表确定PUSCH的调度信息，然后将确定的调度信息通过诸如RRC信令等形式直接下发给第二设备，而不再下发PUSCH的调度信息对应的第一索引或第二索引。
需要说明的是，对于不同制式的无线通信系统，上述PUSCH、PDSCH、PDCCH和PUCCH的名称可能不同，本申请实施例对此不做限定。
在本申请实施例中，PUSCH的起始时隙可以分别采用如下时序关系之一确定：
时序关系一
示例性地，PDSCH的调度信息可以包括PDSCH的起始时隙。因此，在一种可能的设计方法中，可以PDSCH的起始时隙作为参考确定PUSCH的起始时隙。示例性地，如图3A所示，PUSCH与PDSCH在时域上可以满足第一预设条件。其中，第一预设条件可以为：
Figure PCTCN2019105481-appb-000012
其中，n PDSCH为PDSCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDSCH为PDSCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 2为PUSCH与PDSCH之间的预设时隙偏移量，为自然数。
时序关系二
实际应用中，上行信道还可以包括物理上行控制信道PUCCH。因此，在另一种可能的设计方法中，也可以PUCCH的起始时隙作为参考确定PUSCH的起始时隙。示例性地，如图3B所示，PUSCH与PUCCH在时域上满足第二预设条件。其中，第二预设条件可以为：
Figure PCTCN2019105481-appb-000013
其中，n PUSCH为PUSCH的起始时隙，n PUCCH1为PUCCH的起始时隙，μ PUSCH为PUSCH的帧格式指示，μ PUCCH1为PUCCH的帧格式指示，K 3为PUSCH与PUCCH之间的预设时隙偏移量。
时序关系三
在另一种可能的设计方法中，还可以下发PUSCH的调度信息的PDCCH的起始时隙作为参考确定PUSCH的起始时隙。示例性地，如图3C所示，假定PUSCH的调度信息在第一PDCCH(即图3C所示的PDCCH1)下发，则PUSCH与第一PDCCH在时域上满足如下预设条件：
Figure PCTCN2019105481-appb-000014
其中，n PDCCH1为第一PDCCH的起始时隙，n PUSCH为PUSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PUSCH为PUSCH的帧格式指示，K 4为PUSCH与第一PDCCH之间的预设时隙偏移量。
需要说明的是，根据上述三种时序关系确定的PUSCH的起始时隙，均位于对应的PDSCH之后。示例性地，如图3A-图3C所示，PDSCH与第一PDCCH在时域上满足第三预设条件。其中，第三预设条件可以为：
Figure PCTCN2019105481-appb-000015
其中，n PDCCH1为第一PDCCH的起始时隙，n PDSCH为PDSCH的起始时隙，μ PDCCH1为第一PDCCH的帧格式指示，μ PDSCH为PDSCH的帧格式指示，K 0为PDSCH与第一PDCCH之间的预设时隙偏移量。
需要说明的是，对于图3C所示的时序关系三，需要满足K 0＜K 4，以确保的PUSCH在时域上位于PDSCH之后。
可以理解，图3A-图3C分别示出了PUSCH的起始时隙与其作为参考的PDSCH、PUCCH和PDCCH之间的时序关系，并没有限定PUSCH的调度信息的下发方式。
示例性地，如图4A-图4D所示，PDSCH的调度信息均是在一个PDCCH(如图4A-图4D中的第一PDCCH)下发的。相应地，PUSCH的调度信息，可以分别采用如下4种下发方式之一下发：
下发方式一
第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为：
第一设备在第一PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第一索引。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为：
第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第一索引。
示例性地，如图4A所示，第一PDCCH承载的DCI格式可以同时包含两个Time domain resource assignment字段，分别用于承载PDSCH的索引和PUSCH的第一索引。
下发方式二
第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为如下步骤一和步骤二：
步骤一、第一设备向第二设备下发第一无线链路控制RRC信令；其中，第一RRC信令承载有PUSCH的起始时隙；
步骤二、第一设备在第一PDCCH上，向第二设备下发PDSCH的索引和PUSCH的第二索引。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤三和步骤四：
步骤三、第一设备向第二设备下发第一无线链路控制RRC信令；其中，第一RRC信令承载有PUSCH的起始时隙；
步骤四、第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引和PUSCH的第二索引。
示例性地，如图4B所示，PUSCH的起始时隙承载于第一RRC信令，而PDSCH的索引和PUSCH的第二索引承载于第一PDCCH。
需要说明的是，可以先执行步骤一和步骤三，再执行步骤二和步骤四，也可以先执行步骤二和步骤四，再执行步骤一和步骤三，本申请实施例对此不做限定。鉴于RRC信令为现有技术，本申请实施例不再赘述。
此外，与第一索引不同，第一PDCCH承载的PUSCH的第二索引只用于确定PUSCH的资源配置类型、起始符号和符号个数，而PUSCH的起始时隙由第一RRC信令承载。
下发方式三
第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤五和步骤六：
步骤五、第一设备在第一PDCCH上，向第二设备下发PDSCH的索引。
步骤六、第一设备向第二设备下发第二RRC信令；其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以具体实现为步骤七和步骤八：
步骤七、第二设备在第一PDCCH上，接收第一设备下发的PDSCH的索引。
步骤八、第二设备接收第一设备下发的第二RRC信令；其中，第二RRC信令承载有PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
需要说明的是，可以先执行步骤五和步骤七，再执行步骤六和步骤八，也可以先执行步骤六和步骤八，再执行步骤五和步骤七，本申请实施例对此不做限定。
示例性地，如图4C所示，PUSCH的资源配置类型、起始时隙、符号个数和起始符号均承载于第二RRC信令，而PDSCH的索引承载于第一PDCCH。
可以理解，第一设备可以在统一确定PDSCH的调度信息和PUSCH的调度信息之 后，将PDSCH的调度信息对应的PDSCH的索引通过第一PDCCH下发，而将PUSCH的调度信息通过第二RRC信令下发。
现有协议规定：PDCCH承载的DCI格式只包含一个Time domain resource assignment字段。在本申请实施例中，PUSCH的调度信息是通过第二RRC信令直接下发，不需要改变现有协议DCI格式相关规定，可以避免与现有协议冲突。
为了避免与现有协议冲突，在另一种可能的设计方法中，下行信道的调度信息和上行信道的调度信息也可以通过2个不同的PDCCH分别下发。因此，第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，可以包括步骤九和步骤十：
步骤九、第一设备在第一物理下行控制信道PDCCH上，向第二设备下发下行信道的调度信息。
步骤十、第一设备在第二PDCCH上，向第二设备下发上行信道的调度信息。其中，第一PDCCH与第二PDCCH之间存在预设绑定关系。
相应地，第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，可以包括步骤十一和步骤十二：
步骤十一、第二设备在第一物理下行控制信道PDCCH上，接收第一设备下发的下行信道的调度信息。
步骤十二、第二设备在第二PDCCH上，接收第一设备下发的上行信道的调度信息。
在上述步骤九至步骤十二中，下行信道可以是PDSCH，上行信道可以是PUSCH，上行信道也可以是PUSCH和PUCCH，本申请实施例不做限定。示例性地，如图4D所示，第一PDCCH承载有PDSCH的索引，第二PDCCH承载有PUSCH的第一索引。第二设备在接收到上述索引时，可以根据第二设备本地预存的PDSCH的索引与PDSCH的调度信息的对应关系表，以及PUSCH的第一索引与PUSCH的调度信息的对应关系表，分别确定PDSCH的调度信息和PUSCH的调度信息。
可选地，为了提高下行信道的调度信息和上行信道的调度信息的接收效率，第二PDCCH与第一PDCCH之间通常存在预设绑定关系，以便第二设备在上述一个PDCCH上接收到一个调度信息时，可以在存在绑定关系的另一个PDCCH上有针对性地接收另一个调度信息，以避免下行信道和上行信道的调度信息均需要在所有可能的资源集合中盲检的情况，能够有效降低接收下行信道和上行信道的调度信息的计算量，从而提高第二设备接收上下行调度信息的效率，进而提高第一设备与第二设备通信的效率。
其中，第二PDCCH与第一PDCCH之间的预设绑定关系，可以包括如下之一：
第二PDCCH所属搜索空间与第一PDCCH所属搜索空间对应；
第二PDCCH所属控制资源集合CORESET与第一PDCCH所属CORESET对应；
第二PDCCH所属带宽部分BWP与第一PDCCH所属BWP对应；
第二PDCCH所属核心载波CC与第一PDCCH所属CC对应。
示例性地，如图5A所示，PDSCH的调度信息可能承载于搜索空间0、2、6…12等偶数编号的搜索空间中，PUSCH的调度信息可能承载于搜索空间1、3、5…13等奇数编号的搜索空间中，且从搜索空间0开始，相邻的偶数编号的搜索空间与奇数编号的搜索空间存在绑定关系，即搜索空间0和搜索空间1绑定，搜索空间2和搜索空间 3绑定，以此类推。当第二设备在搜索空间0上检测到PDSCH的调度信息时，如检测到PDSCH的索引，则只需要在搜索空间1上检测PUSCH的调度信息即可，而不需要在搜索空间3-13中的奇数编号的搜索空间中检测PUSCH的调度信息，可以有效降低接收PDSCH的调度信息和PUSCH的调度信息的工作量，从而可以提高接收PDSCH的调度信息和PUSCH的调度信息的效率。
图5B示出了本申请实施例提供的上述搜索空间、CORSET、BWP和CC之间的包含关系。如图5B所示，第一设备可以为第二设备配置多个CC，每个CC可配置多个BWP，每个BWP中可配置多个CORSET，每个CORSET可配置多个搜索空间，图5B中的N、M、K和L依次为调度的CC、BWP、CORSET和搜索空间的个数。其中，搜索空间、CORSET、BWP和CC可以理解为不同粒度的资源集合，第一设备可以为第二设备配置同一粒度上的两个不同的资源集合之间的绑定关系。
可以理解，与搜索空间类似，第二设备也可以在存在绑定关系的两个CORESET、或两个BWP或两个CC上检测PDSCH的调度信息和PUSCH的调度信息。例如，第二设备可以在存在绑定关系的BWP 0和BWP 1上检测PDSCH的调度信息和PUSCH的调度信息。
需要说明的是，上述搜索空间、CORESET、BWP和CC均可以视为一种可能用于承载上述下行信道的调度信息或上行信道的调度信息的资源或资源集合的表述方式，且对于不同制式的无线通信系统，上述名称可能不同，本申请实施例对此不做限定。
S203、第一设备在下行信道上向第二设备下发下行数据包。
S204、第二设备在下行信道上接收第一设备下发的下行数据包。
其中，第一设备和第二设备可以在上述S201和S202中调度的下行信道上传输下行数据包。示例性地，下行数据包可以携带用于控制第二设备的控制指令。例如，在工业控制场景下，第一设备可以为主控设备，如控制中心中的计算机，第二设备可以为受控设备，如生产线上的机器设备，下行数据包可以携带有用于控制上述机器设备动作的控制指令，如工艺流程。
示例性地，下行数据包也可以携带用于控制远程终端的控制指令。例如，在人工智能场景下，第一设备可以为网络设备，如服务器，第二设备可以为远程终端，下行数据包可以携带有用于指示上述远程终端需要完成的预设任务。
S205、第二设备在上行信道上向第一设备上报上行数据包。
S206、第一设备在上行信道上接收第二设备上报的上行数据包。
在一种可能的设计方法中，上行数据包与下行数据包对应，可以理解为上行数据包承载的内容是第二设备完成下行数据包承载的指令或任务之后上报的执行结果。
在本申请实施例中，为了提高第一设备接收上行数据包的效率，如图6A-图6F所示，第二设备还可以上报指示信息，用于指示上报的上行数据包是否有效。
可选地，如图6A所示，第二设备可以在媒体接入控制(media accesscontrol，MAC)层协议数据单元(protocol data unit，PDU)中封装一或多比特(bit)指示信息。例如，可以用二进制数字1表示有效，用二进制数字0表示无效。其中，“有效”可以表示，第二设备成功接收到了下行数据包(如PDSCH解调成功)，换句话说，第二设备上报的上行数据包是根据下行数据包做出的，其内容真实有效。可以理解，上述指示信 息可以封装于MAC层PDU中的任一比特位，如可以封装于MAC层PDU头部中的最后一个比特位。
可选地，如图6B和图6C所示，第二设备也可以将上述指示信息与执行结果直接映射至下行信道的物理资源上完成上报。例如，如图6B所示，可以将上述指示信息填充(padding)于上行数据包之前，并在完成物理层资源映射后上报，或者如图6C所示，也可以在承载上行数据包的PUSCH之后捎带(piggyback)承载指示信息的PUCCH，并在完成物理层资源映射后上报。
可选地，还可以不上报单独的指示信息，而是如图6D所示，定义一或多个预设数值序列来表示上行数据包无效。例如，以全0或全1等预设数值表示上行数据包无效。可以理解，若上行数据包不包含上述预设数值序列，则可以视为上行数据包有效。
可选地，还可以将执行结果及其指示信息在不同的上行信道上分别上报。示例性地，如图6E和图6F所示，当下行信道包括PDSCH，且上行信道包括PUSCH和PUCCH时，可以在PUCCH上上报指示信息。例如，在PUCCH上上报确认/非确认(acknowledgement/non-acknowledgement，ACK/NACK)指示信息，在PUSCH上上报上行数据包。具体地，可以采用如下任一方式分别上报ACK/NACK和执行结果。
方式一
示例性地，如图6E所示，PUCCH在时域上位于PUSCH之前。
可选地，当对应的PDSCH解调失败时，第二设备在PUCCH上反馈NACK，且不再需要在随后的PUSCH上发送上行数据包(因为实际上不存在需要上报的上行数据包)，以减少第二设备上报的数据量。相应地，第一设备接收到NACK后，也可以将该PUSCH重新调度给其他设备使用，以提高第一设备的无线资源利用率，且可以降低无效的上行数据包的解调计算量。
可选地，当对应的PDSCH解调成功时，第二设备在PUCCH上反馈ACK。相应地，第一设备接收到ACK后，可以确认之后收到的PUSCH有效，并可以在接收到PUSCH的同时，即可对PUSCH解调，以减少第一设备需要缓存的数据量，从而降低第一设备的存储成本。
方式二
示例性地，如图6F所示，PUCCH在时域上位于PUSCH之后。
具体地，第二设备在PUSCH上上报上行数据包，且在随后的PUCCH上上报ACK/NACK。相应地，第一设备需要先缓存其在PUSCH接收到的上行数据包，当第一设备在PUCCH上接收到指示信息后，再确定是否对接收到的上行数据包进行解调。示例性地，若指示信息为ACK，则对接收到的上行数据包解调，否则，直接丢弃，以减少不必要的解调工作量。
可以理解，与方式一相同，当第一设备获知第二设备上报的上行数据包无效时，也可以停止接收第二设备上报的PUCCH和PUSCH，并将PUCCH和PUSCH对应的无线资源调度给其他设备使用，以提高无线资源利用率。
本申请实施例提供的资源调度方法，能够根据工业控制、人工智能等场景下第一设备下发的下行数据包与第二设备上报的上行数据包必须成对出现，且下发下行数据包必须在上报上行数据包之前的特定需求，为下行数据包和上行数据包统一调度上行 信道和下行信道，且调度的上行信道在时域上位于下行信道之后，可以避免上述特定场景下分别为下行数据包和上行数据包独立调度的下行信道和上行信道不能满足特定需求而冲突的问题，能够提高第一设备与第二设备通信的可靠性。
以上结合图2-图6F详细说明了本申请实施例的资源调度方法。以下结合图7-图11详细说明上述方法实施例所涉及的第一设备和第二设备。
图7示出了上述方法实施例中所涉及的第一设备的一种可能的结构示意图。如图7所示，第一设备700包括：发送模块701和接收模块702。
其中，发送模块701，用于向第二设备下发下行信道的调度信息和上行信道的调度信息；其中，上行信道在时域上位于下行信道之后。
发送模块701，还用于在下行信道上向第二设备下发下行数据包；
接收模块702，用于在上行信道上接收第二设备上报的上行数据包。
可选地，第一设备700和上述方法实施例中的第一设备完全对应，第一设备700的相应单元用于执行上述方法实施例中由第一设备执行的相应步骤。例如，第一设备中的发送模块701用于执行方法实施例中第一设备发送的步骤，如执行图2中S201或S203等。接收模块702用于执行方法实施例中第一设备接收的步骤，如执行图2中S206。
可选地，发送模块701和接收模块702可以组成收发单元，同时具有接收和发送的功能。其中，接收模块702可以是接收器。发送模块701可以是发射器。接收器和发射器可以集成在一起组成收发器。
图8示出了上述方法实施例中所涉及的第二设备的一种可能的结构示意图。如图8所示，第二设备800包括：发送模块801和接收模块802。
其中，接收模块802，用于接收第一设备下发的下行信道的调度信息和上行信道的调度信息；其中，上行信道在时域上位于下行信道之后；
接收模块802，还用于在下行信道上接收第一设备下发的下行数据包；
发送模块801，用于在上行信道上向第一设备上报上行数据包。
可选地，第二设备800和上述方法实施例中的第二设备完全对应，第二设备800的相应单元用于执行上述方法实施例中由第二设备执行的相应步骤。例如，第二设备中的发送模块801用于执行方法实施例中第二设备发送的步骤，如执行图2中的S205。接收模块802用于执行方法实施例中第二设备接收的步骤，如执行图2中的S202或S204。
可选地，发送模块801和接收模块802可以组成收发单元，同时具有接收和发送的功能。其中，接收模块802可以是接收器。发送模块801可以是发射器。接收器和发射器可以集成在一起组成收发器。
图9示出了上述方法实施例中所涉及的第一设备的另一种可能的结构示意图。如图9所示，第一设备900包括：处理器901和通信接口902。处理器901用于对第一设备的动作进行控制管理，例如，处理器901用于控制通信接口902来支持第一设备与其他网络实体的通信，例如，执行上述接收模块702、发送模块701执行的步骤。此外，第一设备还可以包括存储器903和总线904，存储器903用于存储第一设备的程序代码和数据。
其中，上述处理器901可以是第一设备中的处理器或控制器，该处理器或控制器可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。该处理器或控制器可以是中央处理器，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等。
通信接口902可以是第一设备中的收发器、收发电路或通信接口等。
存储器903可以是第一设备中的存储器等，该存储器可以包括易失性存储器，例如随机存取存储器；该存储器也可以包括非易失性存储器，例如只读存储器，快闪存储器，硬盘或固态硬盘；该存储器还可以包括上述种类的存储器的组合。
总线904可以是扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线904可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
参见图10，图10示出了适用于本申请实施例的第一设备900的另一种示意性结构框图。如图10所示，第一设备900包括：一个或多个处理器901，一个或多个收发器905，一个或多个存储器903。处理器901用于控制收发器905收发信号，存储器903用于存储计算机程序，处理器901用于从存储器903中调用并运行该计算机程序，以执行本申请实施例提供的资源调度方法，以及各实施例中由第一设备执行的相应流程和/或操作。
图11示出了上述实施例中所涉及的第二设备的又一种可能的结构示意图。该第二设备包括：处理器1101和通信接口1102。处理器1101用于对第二设备的动作进行控制管理，例如，处理器1101用于控制通信接口1102来支持第二设备与其他网络实体的通信，例如，执行上述接收模块802、发送模块801执行的步骤。此外，第二设备还可以包括存储器1103和总线1104，存储器1103用于存储第二设备的程序代码和数据。
其中，上述处理器1101可以是第二设备中的处理器或控制器，该处理器或控制器可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。该处理器或控制器可以是中央处理器，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等。
通信接口1102可以是第二设备中的收发器、收发电路或通信接口等。
存储器1103可以是第二设备中的存储器等，该存储器可以包括易失性存储器，例如随机存取存储器；该存储器也可以包括非易失性存储器，例如只读存储器，快闪存储器，硬盘或固态硬盘；该存储器还可以包括上述种类的存储器的组合。
总线1104可以是EISA总线等。总线1104可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类 型的总线。
参见图12，图12示出了适用于本申请实施例的第二设备1100的另一种示意性结构框图。如图12所示，第二设备1100包括：一个或多个处理器1101，一个或多个收发器1105，一个或多个存储器1103。处理器1101用于控制收发器1105收发信号，存储器1103用于存储计算机程序，处理器1101用于从存储器1103中调用并运行该计算机程序，以执行本申请实施例提供的资源调度方法，以及各实施例中由第一设备执行的相应流程和/或操作。
此外，本申请还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机指令，当该计算机指令在计算机上运行时，使得计算机执行本申请实施例提供的资源调度方法及其各实施例中由第一设备或第二设备执行的相应操作和/或流程。
本申请还提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当该计算机程序代码在计算机上运行时，使得计算机执行本申请实施例提供的资源调度方法及其各实施例中由第一设备或第二设备执行的相应操作和/或流程。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请实施例提供的资源调度方法及其各实施例中由第一设备或第二设备执行的相应操作和/或流程。可选地，该芯片还可以包括存储器，该存储器与该处理器通过电路或电线连接，处理器用于读取并执行该存储器中的计算机程序。可选地，该存储器可以是该芯片内部的存储器，也可以是位于该芯片外部，且与该芯片通过电路或电线连接的存储器，本申请实施例对此不做限定。
进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收需要处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。示例性地，该通信接口可以是收发器、输入输出接口。
本申请实施例提供一种通信系统，该通信系统可以包括第一设备和第二设备，用于执行本申请实施例提供的资源调度方法。对于第一设备和第二设备的描述具体可以参见上述方法实施例和装置实施例中的相关描述，此处不再赘述。
应理解，在本申请实施例中的处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态 随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件(如电路)、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本申请实施例中术语“和/或”，仅仅用于描述关联对象的关联条件，表示可以存在三种条件，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的条件，但也可能表示的是一种“和/或”的条件，具体可参考前后文进行理解。
本申请实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
本申请实施例中，“第一”和“第二”等是用于区别不同的对象，或者用于区别对同一对象的不同处理，而不是用于描述对象的特定顺序。
本申请实施例中，“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是在一些实施例中还包括其他没有列出的步骤或单元，或在一些实施例中还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例中，“信息(information)”，“信号(signal)”，“消息(message)”，“信道(channel)”、“信令(singalling)”、“消息(message)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是， 在不强调其区别时，其所要表达的含义是一致的。
在本申请实施例中，有时候下标如W 1可能会笔误为非下标的形式如W1，在不强调其区别时，其所要表达的含义是一致的。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (36)

  1. 一种资源调度方法，其特征在于，所述资源调度方法包括：
    第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息；其中，所述上行信道在时域上位于所述下行信道之后；
    所述第一设备在所述下行信道上向所述第二设备下发下行数据包；
    所述第一设备在所述上行信道上接收所述第二设备上报的上行数据包。
  2. 根据权利要求1所述的资源调度方法，其特征在于，所述下行信道包括物理下行共享信道PDSCH，所述下行信道的调度信息包括所述PDSCH的索引；
    所述上行信道包括物理上行共享信道PUSCH，所述上行信道的调度信息包括如下之一：
    所述PUSCH的第一索引；其中，所述第一索引用于确定所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数；
    所述PUSCH的第二索引和起始时隙；其中，所述第二索引用于确定所述PUSCH的资源配置类型、起始符号和符号个数；
    所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
  3. 根据权利要求2所述的资源调度方法，其特征在于，所述PUSCH与所述PDSCH在时域上满足第一预设条件；其中，所述第一预设条件为：
    Figure PCTCN2019105481-appb-100001
    其中，n PDSCH为所述PDSCH的起始时隙，n PUSCH为所述PUSCH的起始时隙，μ PDSCH为所述PDSCH的帧格式指示，μ PUSCH为所述PUSCH的帧格式指示，K 2为所述PUSCH与所述PDSCH之间的预设时隙偏移量。
  4. 根据权利要求2所述的资源调度方法，其特征在于，所述上行信道还包括物理上行控制信道PUCCH；所述PUSCH与所述PUCCH在时域上满足第二预设条件；其中，所述第二预设条件为：
    Figure PCTCN2019105481-appb-100002
    其中，n PUSCH为所述PUSCH的起始时隙，n PUCCH1为所述PUCCH的起始时隙，μ PUSCH为所述PUSCH的帧格式指示，μ PUCCH1为所述PUCCH的帧格式指示，K 3为所述PUSCH与所述PUCCH之间的预设时隙偏移量。
  5. 根据权利要求2-4中任一项所述的资源调度方法，其特征在于，所述第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，包括：
    所述第一设备在第一物理下行控制信道PDCCH上，向所述第二设备下发所述PDSCH的索引和所述PUSCH的第一索引。
  6. 根据权利要求2-4中任一项所述的资源调度方法，其特征在于，所述第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，包括：
    所述第一设备向所述第二设备下发第一无线链路控制RRC信令；其中，所述第一RRC信令承载有所述PUSCH的起始时隙；
    所述第一设备在第一物理下行控制信道PDCCH上，向所述第二设备下发所述PDSCH的索引和所述PUSCH的第二索引。
  7. 根据权利要求2-4中任一项所述的资源调度方法，其特征在于，所述第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，包括：
    所述第一设备在第一物理下行控制信道PDCCH上，向所述第二设备下发所述PDSCH的索引；
    所述第一设备向所述第二设备下发第二RRC信令；其中，所述第二RRC信令承载有所述PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
  8. 根据权利要求1所述的资源调度方法，其特征在于，所述第一设备向第二设备下发下行信道的调度信息和上行信道的调度信息，包括：
    所述第一设备在第一物理下行控制信道PDCCH上，向所述第二设备下发下行信道的调度信息；
    所述第一设备在第二PDCCH上，向所述第二设备下发上行信道的调度信息；其中，所述第二PDCCH与所述第二PDCCH之间存在预设绑定关系。
  9. 根据权利要求8所述的资源调度方法，其特征在于，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系，包括如下之一：
    所述第二PDCCH所属搜索空间与所述第一PDCCH所属搜索空间对应；
    所述第二PDCCH所属控制资源集合CORESET与所述第一PDCCH所属CORESET对应；
    所述第二PDCCH所属带宽部分BWP与所述第一PDCCH所属BWP对应；
    所述第二PDCCH所属核心载波CC与所述第一PDCCH所属CC对应。
  10. 一种资源调度方法，其特征在于，所述资源调度方法包括：
    第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息；其中，所述上行信道在时域上位于所述下行信道之后；
    所述第二设备在所述下行信道上接收所述第一设备下发的下行数据包；
    所述第二设备在所述上行信道上向所述第一设备上报上行数据包。
  11. 根据权利要求10所述的资源调度方法，其特征在于，所述下行信道包括物理下行共享信道PDSCH，所述下行信道的调度信息包括所述PDSCH的索引；
    所述上行信道包括物理上行共享信道PUSCH，所述上行信道的调度信息包括如下之一：
    所述PUSCH的第一索引；其中，所述第一索引用于确定所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数；
    所述PUSCH的第二索引和起始时隙；其中，所述第二索引用于确定所述PUSCH的资源配置类型、起始符号和符号个数；
    所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
  12. 根据权利要求11所述的资源调度方法，其特征在于，所述PUSCH与所述PDSCH在时域上满足第一预设条件；其中，所述第一预设条件为：
    Figure PCTCN2019105481-appb-100003
    其中，n PDSCH为所述PDSCH的起始时隙，n PUSCH为所述PUSCH的起始时隙，μ PDSCH为所述PDSCH的帧格式指示，μ PUSCH为所述PUSCH的帧格式指示，K 2为所述PUSCH与所述PDSCH之间的预设时隙偏移量。
  13. 根据权利要求11所述的资源调度方法，其特征在于，所述上行信道还包括物理上行控制信道PUCCH；所述PUSCH与所述PUCCH在时域上满足第二预设条件；其中，所述第二预设条件为：
    Figure PCTCN2019105481-appb-100004
    其中，n PUSCH为所述PUSCH的起始时隙，n PUCCH1为所述PUCCH的起始时隙，μ PUSCH为所述PUSCH的帧格式指示，μ PUCCH1为所述PUCCH的帧格式指示，K 3为所述PUSCH与所述PUCCH之间的预设时隙偏移量。
  14. 根据权利要求11-13中任一项所述的资源调度方法，其特征在于，所述第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，包括：
    所述第二设备在第一物理下行控制信道PDCCH上，接收所述第一设备下发的所述PDSCH的索引和所述PUSCH的第一索引。
  15. 根据权利要求11-13中任一项所述的资源调度方法，其特征在于，所述第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，包括：
    所述第二设备接收所述第一设备下发的第一无线链路控制RRC信令；其中，所述第一RRC信令承载有所述PUSCH的起始时隙；
    所述第二设备在第一物理下行控制信道PDCCH上，接收所述第一设备下发的所述PDSCH的索引和所述PUSCH的第二索引。
  16. 根据权利要求11-13中任一项所述的资源调度方法，其特征在于，所述第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，包括：
    所述第一设备在第一物理下行控制信道PDCCH上，接收所述第二设备下发的所述PDSCH的索引；
    所述第二设备接收所述第一设备下发的第二RRC信令；其中，所述第二RRC信令承载有所述PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
  17. 根据权利要求10所述的资源调度方法，其特征在于，所述第二设备接收第一设备下发的下行信道的调度信息和上行信道的调度信息，包括：
    所述第二设备在第一物理下行控制信道PDCCH上，接收所述第一设备下发的下行信道的调度信息；
    所述第二设备在第二PDCCH上，接收所述第一设备下发的上行信道的调度信息；其中，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系。
  18. 根据权利要求17所述的资源调度方法，其特征在于，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系，包括如下之一：
    所述第二PDCCH所属搜索空间与所述第一PDCCH所属搜索空间对应；
    所述第二PDCCH所属控制资源集合CORESET与所述第一PDCCH所属CORESET对应；
    所述第二PDCCH所属带宽部分BWP与所述第一PDCCH所属BWP对应；
    所述第二PDCCH所属核心载波CC与所述第一PDCCH所属CC对应。
  19. 一种第一设备，其特征在于，包括：
    发送模块，用于向第二设备下发下行信道的调度信息和上行信道的调度信息；其中，所述上行信道在时域上位于所述下行信道之后；
    所述发送模块，还用于在所述下行信道上向所述第二设备下发下行数据包；
    接收模块，用于在所述上行信道上接收所述第二设备上报的上行数据包。
  20. 根据权利要求19所述的第一设备，其特征在于，所述下行信道包括物理下行共享信道PDSCH，所述下行信道的调度信息包括所述PDSCH的索引；
    所述上行信道包括物理上行共享信道PUSCH，所述上行信道的调度信息包括如下之一：
    所述PUSCH的第一索引；其中，所述第一索引用于确定所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数；
    所述PUSCH的第二索引和起始时隙；其中，所述第二索引用于确定所述PUSCH的资源配置类型、起始符号和符号个数；
    所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
  21. 根据权利要求20所述的第一设备，其特征在于，所述PUSCH与所述PDSCH在时域上满足第一预设条件；其中，所述第一预设条件为：
    Figure PCTCN2019105481-appb-100005
    其中，n PDSCH为所述PDSCH的起始时隙，n PUSCH为所述PUSCH的起始时隙，μ PDSCH为所述PDSCH的帧格式指示，μ PUSCH为所述PUSCH的帧格式指示，K 2为所述PUSCH与所述PDSCH之间的预设时隙偏移量。
  22. 根据权利要求20所述的第一设备，其特征在于，所述上行信道还包括物理上行控制信道PUCCH；所述PUSCH与所述PUCCH在时域上满足第二预设条件；其中，所述第二预设条件为：
    Figure PCTCN2019105481-appb-100006
    其中，n PUSCH为所述PUSCH的起始时隙，n PUCCH1为所述PUCCH的起始时隙，μ PUSCH为所述PUSCH的帧格式指示，μ PUCCH1为所述PUCCH的帧格式指示，K 3为所述PUSCH与所述PUCCH之间的预设时隙偏移量。
  23. 根据权利要求20-22中任一项所述的第一设备，其特征在于，
    所述发送模块，还用于在第一物理下行控制信道PDCCH上，向所述第二设备下发所述PDSCH的索引和所述PUSCH的第一索引。
  24. 根据权利要求23所述的第一设备，其特征在于，
    所述发送模块，还用于向所述第二设备下发第一无线链路控制RRC信令；其中，所述第一RRC信令承载有所述PUSCH的起始时隙；
    所述发送模块，还用于在所述第一PDCCH上，向所述第二设备下发所述PDSCH的索引和所述PUSCH的第二索引。
  25. 根据权利要求23所述的第一设备，其特征在于，
    所述发送模块，还用于在所述第一PDCCH上，向所述第二设备下发所述PDSCH的索引；
    所述发送模块，还用于向所述第二设备下发第二RRC信令；其中，所述第二RRC信令承载有所述PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
  26. 根据权利要求19所述的第一设备，其特征在于，
    所述发送模块，还用于在第一物理下行控制信道PDCCH上，向所述第二设备下发下行信道的调度信息；
    所述发送模块，还用于在第二PDCCH上，向所述第二设备下发上行信道的调度信息；其中，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系。
  27. 根据权利要求26所述的第一设备，其特征在于，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系，包括如下之一：
    所述第二PDCCH所属搜索空间与所述第一PDCCH所属搜索空间对应；
    所述第二PDCCH所属控制资源集合CORESET与所述第一PDCCH所属CORESET对应；
    所述第二PDCCH所属带宽部分BWP与所述第一PDCCH所属BWP对应；
    所述第二PDCCH所属核心载波CC与所述第一PDCCH所属CC对应。
  28. 一种第二设备，其特征在于，包括：
    接收模块，用于接收第一设备下发的下行信道的调度信息和上行信道的调度信息；其中，所述上行信道在时域上位于所述下行信道之后；
    所述接收模块，还用于在所述下行信道上接收所述第一设备下发的下行数据包；
    发送模块，用于在所述上行信道上向所述第一设备上报上行数据包。
  29. 根据权利要求28所述的第二设备，其特征在于，所述下行信道包括物理下行共享信道PDSCH，所述下行信道的调度信息包括所述PDSCH的索引；
    所述上行信道包括物理上行共享信道PUSCH，所述上行信道的调度信息包括如下之一：
    所述PUSCH的第一索引；其中，所述第一索引用于确定所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数；
    所述PUSCH的第二索引和起始时隙；其中，所述第二索引用于确定所述PUSCH的资源配置类型、起始符号和符号个数；
    所述PUSCH的资源配置类型、起始时隙、起始符号和符号个数。
  30. 根据权利要求29所述的第二设备，其特征在于，所述PUSCH与所述PDSCH在时域上满足第一预设条件；其中，所述第一预设条件为：
    Figure PCTCN2019105481-appb-100007
    其中，n PDSCH为所述PDSCH的起始时隙，n PUSCH为所述PUSCH的起始时隙，μ PDSCH为所述PDSCH的帧格式指示，μ PUSCH为所述PUSCH的帧格式指示，K 2为所述PUSCH与所述PDSCH之间的预设时隙偏移量。
  31. 根据权利要求29所述的第二设备，其特征在于，所述上行信道还包括物理上行控制信道PUCCH；所述PUSCH与所述PUCCH在时域上满足第二预设条件；其中， 所述第二预设条件为：
    Figure PCTCN2019105481-appb-100008
    其中，n PUSCH为所述PUSCH的起始时隙，n PUCCH1为所述PUCCH的起始时隙，μ PUSCH为所述PUSCH的帧格式指示，μ PUCCH1为所述PUCCH的帧格式指示，K 3为所述PUSCH与所述PUCCH之间的预设时隙偏移量。
  32. 根据权利要求29-31中任一项所述的第二设备，其特征在于，
    所述接收模块，还用于在第一物理下行控制信道PDCCH上，接收所述第一设备下发的所述PDSCH的索引和所述PUSCH的第一索引。
  33. 根据权利要求32所述的第二设备，其特征在于，
    所述接收模块，还用于接收所述第一设备下发的第一无线链路控制RRC信令；其中，所述第一RRC信令承载有所述PUSCH的起始时隙；
    所述接收模块，还用于在第一物理下行控制信道PDCCH上，接收所述第一设备下发的所述PDSCH的索引和所述PUSCH的第二索引。
  34. 根据权利要求32所述的第二设备，其特征在于，
    所述接收模块，还用于在第一物理下行控制信道PDCCH上，接收所述第一设备下发的所述PDSCH的索引；
    所述接收模块，还用于接收所述第一设备下发的第二RRC信令；其中，所述第二RRC信令承载有所述PUSCH的资源配置类型、起始时隙、符号个数和起始符号。
  35. 根据权利要求28所述的第二设备，其特征在于，
    所述接收模块，还用于在第一物理下行控制信道PDCCH上，接收所述第一设备下发的下行信道的调度信息；
    所述接收模块，还用于在第二PDCCH上，接收所述第一设备下发的上行信道的调度信息；其中，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系。
  36. 根据权利要求35所述的第二设备，其特征在于，所述第二PDCCH与所述第一PDCCH之间存在预设绑定关系，包括如下之一：
    所述第二PDCCH所属搜索空间与所述第一PDCCH所属搜索空间对应；
    所述第二PDCCH所属控制资源集合CORESET与所述第一PDCCH所属CORESET对应；
    所述第二PDCCH所属带宽部分BWP与所述第一PDCCH所属BWP对应；
    所述第二PDCCH所属核心载波CC与所述第一PDCCH所属CC对应。
PCT/CN2019/105481 2018-09-20 2019-09-11 资源调度方法及设备 WO2020057421A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811102163.5 2018-09-20
CN201811102163.5A CN110933761B (zh) 2018-09-20 2018-09-20 资源调度方法及设备

Publications (1)

Publication Number Publication Date
WO2020057421A1 true WO2020057421A1 (zh) 2020-03-26

Family

ID=69856313

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105481 WO2020057421A1 (zh) 2018-09-20 2019-09-11 资源调度方法及设备

Country Status (2)

Country Link
CN (1) CN110933761B (zh)
WO (1) WO2020057421A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210360664A1 (en) * 2020-05-12 2021-11-18 Qualcomm Incorporated Joint shared channel timing allocation in downlink control information

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150189648A1 (en) * 2012-06-27 2015-07-02 Sharp Kabushiki Kaisha Base station device, mobile station device, wireless communication method, integrated circuit, and wireless communication system
US20180054848A1 (en) * 2016-08-18 2018-02-22 Qualcomm Incorporated Retaining access to a shared radio frequency spectrum band during an uplink control portion of a transmission structure
CN107872834A (zh) * 2016-09-28 2018-04-03 华为技术有限公司 信息传输的方法和装置
CN108023703A (zh) * 2016-11-04 2018-05-11 华为技术有限公司 通信方法和通信装置

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8855076B2 (en) * 2010-01-17 2014-10-07 Lg Electronics Inc. Method and apparatus for transmitting control information in wireless communication system
KR101799272B1 (ko) * 2010-02-03 2017-11-20 엘지전자 주식회사 무선 통신 시스템에서 제어 정보의 전송 방법 및 장치
KR101753586B1 (ko) * 2010-02-03 2017-07-04 엘지전자 주식회사 무선 통신 시스템에서 제어 정보의 전송 방법 및 장치
WO2012086883A1 (ko) * 2010-12-20 2012-06-28 엘지전자 주식회사 캐리어 접합 시스템에서, 컴포넌트 캐리어 할당 방법 및 장치
CN102711270A (zh) * 2012-06-19 2012-10-03 张家港市鸿嘉数字科技有限公司 一种物理下行控制信道的发送方法
US9756658B2 (en) * 2012-06-26 2017-09-05 Futurewei Technologies, Inc. System and method for contention-free random access
CN111278134B (zh) * 2014-07-28 2023-09-26 Lg 电子株式会社 在无线通信系统中收发无线信号的方法及其设备
JP6463480B2 (ja) * 2014-12-23 2019-02-06 エルジー エレクトロニクス インコーポレイティド 非免許帯域を支援する無線接続システムにおいて向上した物理下りリンク制御チャネルを送受信する方法及びこれを支援する装置
US10749648B2 (en) * 2015-07-14 2020-08-18 Lg Electronics Inc. Method and user equipment for receiving downlink signal, and method and base station for transmitting downlink signal
US10498497B2 (en) * 2015-09-09 2019-12-03 Lg Electronics Inc. Broadcast signal transmitting device, broadcast signal receiving device, broadcast signal transmitting method and broadcast signal receiving method
CN108370594B (zh) * 2015-12-31 2020-09-25 华为技术有限公司 数据传输处理方法、用户设备和基站
WO2017156787A1 (zh) * 2016-03-18 2017-09-21 广东欧珀移动通信有限公司 通信方法、终端设备和网络设备
US10231198B2 (en) * 2016-03-31 2019-03-12 Lg Electronics Inc. Method and user equipment for receiving downlink signal, and method and base station for transmitting downlink signal

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150189648A1 (en) * 2012-06-27 2015-07-02 Sharp Kabushiki Kaisha Base station device, mobile station device, wireless communication method, integrated circuit, and wireless communication system
US20180054848A1 (en) * 2016-08-18 2018-02-22 Qualcomm Incorporated Retaining access to a shared radio frequency spectrum band during an uplink control portion of a transmission structure
CN107872834A (zh) * 2016-09-28 2018-04-03 华为技术有限公司 信息传输的方法和装置
CN108023703A (zh) * 2016-11-04 2018-05-11 华为技术有限公司 通信方法和通信装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210360664A1 (en) * 2020-05-12 2021-11-18 Qualcomm Incorporated Joint shared channel timing allocation in downlink control information
US11871410B2 (en) * 2020-05-12 2024-01-09 Qualcomm Incorporated Joint shared channel timing allocation in downlink control information

Also Published As

Publication number Publication date
CN110933761A (zh) 2020-03-27
CN110933761B (zh) 2022-02-15

Similar Documents

Publication Publication Date Title
US11646771B2 (en) Feedback information transmission method and apparatus
WO2019137213A1 (zh) 上行控制信息传输方法和通信装置
WO2020200162A1 (zh) 确定反馈信息的方法和通信装置
WO2020143709A1 (zh) 一种信息处理方法、终端设备及网络设备
WO2020221271A1 (zh) 传输混合自动重传请求harq反馈信息的方法和通信装置
CN104662978A (zh) 资源分配方法及设备
WO2019095271A1 (zh) 资源确定方法、装置、网元及系统
US20230014182A1 (en) Harq information transmission method and apparatus
JP2022531281A (ja) マルチキャストフィードバック構成方法及び装置
WO2021031961A1 (zh) 反馈信息的传输方法及通信装置
CN111147190B (zh) 反馈应答信息的传输方法、装置及系统
US11528714B2 (en) Data transmission method and apparatus
US20180331808A1 (en) Method for hybrid automatic repeat request process, network device and terminal device
WO2021062609A1 (zh) 通信方法和通信装置
WO2019191966A1 (zh) 可靠性传输方法及相关产品
WO2021212391A1 (zh) 信息传输方法及装置
WO2020177680A1 (zh) 通信方法和通信装置
WO2020057421A1 (zh) 资源调度方法及设备
US20220368505A1 (en) Data feedback method and apparatus
WO2022151963A1 (zh) Pucch重传确定、配置方法及装置、存储介质、用户设备、网络侧设备
WO2020088517A1 (zh) 数据传输方法和设备
WO2021035541A1 (zh) 一种数据传输方法及相关设备
WO2017128512A1 (zh) 信息发送方法、信息接收方法、装置及系统
WO2020030026A1 (zh) 用于发送srs的方法和装置
WO2020168557A1 (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: 19862053

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

Country of ref document: EP

Kind code of ref document: A1