WO2021155796A1 - 调度方法、终端及网络侧设备 - Google Patents
调度方法、终端及网络侧设备 Download PDFInfo
- Publication number
- WO2021155796A1 WO2021155796A1 PCT/CN2021/075002 CN2021075002W WO2021155796A1 WO 2021155796 A1 WO2021155796 A1 WO 2021155796A1 CN 2021075002 W CN2021075002 W CN 2021075002W WO 2021155796 A1 WO2021155796 A1 WO 2021155796A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- scheduling
- scheduled
- terminal
- search space
- monitoring
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1221—Wireless traffic scheduling based on age of data to be sent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- 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/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/022—Site diversity; Macro-diversity
- H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1887—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
Definitions
- the embodiments of the present invention relate to the field of wireless communication technologies, and in particular, to a scheduling method, a terminal, and a network side device.
- the 5G New Air Interface (NR) system supports carrier aggregation (CA), which can configure and activate multiple component carriers (CC) or cells for user equipment (User Equipment, UE, also referred to as terminal), and supports Cross-carrier scheduling under CA.
- CA carrier aggregation
- CC component carriers
- UE User Equipment
- Cross-carrier scheduling under CA.
- each CC or cell can be configured with multiple control resource sets (CORESET) and multiple search spaces (SS), including public search Space (common search space, CSS) and UE-specific search space (UE-specific search space, USS).
- CORESET control resource sets
- SS search spaces
- the network can flexibly configure the number of blind checks for each search space set, and the CORESET can be flexibly associated with the search space set.
- the UE blindly detects the physical downlink control channel (PDCCH) by using various radio network temporary identifiers (RNTI), and demodulates the downlink control information (Downlink Control Information, DCI) ) To obtain the scheduling information of each cell.
- DCI Downlink Control Information
- the network can configure cross-carrier scheduling for the UE, that is, configure the control channel in other cells with better channel quality (for example, PCell) for cross-carrier scheduling Data of other cells (for example, SCell).
- the subcarrier spacing (SCS) of the scheduling cell (scheduling cell) and the scheduled cell (scheduled cell) may be the same or different.
- the scheduling cell can be in the self-scheduling mode, at this time the cell only schedules itself. If the scheduling cell is configured with cross-carrier scheduling, it can also schedule one or more scheduled cells other than itself. The scheduled cell does not have its own PDCCH and can only be scheduled by one scheduling cell.
- a cell can only be scheduled by one scheduling cell (that is, it can only be self-scheduled or scheduled by another cell), and the PCell can only be scheduled by the PCell itself. This leads to lower scheduling flexibility.
- the embodiments of the present invention provide a scheduling method, a terminal, and a network side device, which are used to solve the problem of low scheduling flexibility in related technologies that one cell can only be scheduled by one scheduling cell.
- the present invention is implemented as follows:
- an embodiment of the present invention provides a scheduling method applied to a terminal, including:
- the scheduling information of at least two scheduling objects to one scheduled object is monitored.
- an embodiment of the present invention provides a scheduling method applied to a network side device, including:
- an embodiment of the present invention provides a terminal, including:
- the monitoring module is configured to monitor the scheduling information of at least two scheduling objects to one scheduled object according to the scheduling configuration information.
- an embodiment of the present invention provides a network side device, including:
- the sending module is configured to send scheduling configuration information, where the scheduling configuration information at least includes: the configuration terminal monitors the scheduling information of at least two scheduling objects for one scheduled object.
- an embodiment of the present invention provides a terminal including a processor, a memory, and a computer program stored on the memory and capable of running on the processor.
- the computer program is executed by the processor, Implement the steps of the scheduling method of the first aspect described above.
- an embodiment of the present invention provides a network-side device, including a processor, a memory, and a computer program stored on the memory and running on the processor, and the computer program is used by the processor.
- the steps of the scheduling method of the second aspect described above are implemented during execution.
- an embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the scheduling method of the above-mentioned first aspect are implemented; Or, when the computer program is executed by a processor, the steps of the scheduling method of the second aspect described above are implemented.
- an embodiment of the present invention provides a computer program product that, when executed by at least one processor, implements the steps of the scheduling method of the first aspect; or, implements the steps of the scheduling method of the second aspect. .
- an embodiment of the present invention provides a communication device configured to execute the steps of the scheduling method of the first aspect; or, execute the steps of the scheduling method of the second aspect.
- one scheduled object can be scheduled through at least two scheduling objects.
- one cell can only be scheduled by one scheduling cell, which improves scheduling flexibility.
- FIG. 1 is a schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present invention
- FIG. 2 is a schematic flowchart of a scheduling method according to an embodiment of the present invention.
- FIG. 3 and 4 are schematic diagrams of SCell cross-carrier scheduling PCell according to an embodiment of the present invention.
- FIG. 8 is a schematic flowchart of a scheduling method according to another embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present invention.
- FIG. 11 is a schematic structural diagram of a terminal according to another embodiment of the present invention.
- FIG. 12 is a schematic structural diagram of a terminal according to another embodiment of the present invention.
- FIG. 13 is a schematic structural diagram of a network side device according to another embodiment of the present invention.
- words such as “exemplary” or “for example” are used to represent examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present invention should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
- the scheduling method, terminal, and network-side equipment provided by the embodiments of the present invention can be applied to a wireless communication system.
- the wireless communication system may adopt a 5G system, or an evolved Long Term Evolution (eLTE) system, or a subsequent evolved communication system.
- eLTE evolved Long Term Evolution
- the wireless communication system may include: a network-side device 11 and a terminal 12, and the terminal 12 may be connected to the network-side device 11.
- the connection between the above-mentioned various devices may be a wireless connection.
- a solid line is shown in FIG. 1.
- the above-mentioned communication system may include multiple terminals 12, and the network side device 11 may communicate with multiple terminals 12 (transmitting signaling or transmitting data).
- the network-side device 11 provided by the embodiment of the present invention may be a base station, which may be a commonly used base station, an evolved node base station (eNB), or a network-side device in a 5G system (for example, Next generation base station (next generation node base station, gNB) or transmission and reception point (transmission and reception point, TRP)) or cell and other equipment. Or the network side device in the subsequent evolution communication system.
- a base station which may be a commonly used base station, an evolved node base station (eNB), or a network-side device in a 5G system (for example, Next generation base station (next generation node base station, gNB) or transmission and reception point (transmission and reception point, TRP)) or cell and other equipment.
- gNB Next generation base station
- TRP transmission and reception point
- the terminal 12 provided by the embodiment of the present invention may be a mobile phone, a tablet computer, a notebook computer, an Ultra-Mobile Personal Computer (UMPC), a netbook, or a Personal Digital Assistant (PDA), etc.
- UMPC Ultra-Mobile Personal Computer
- PDA Personal Digital Assistant
- FIG. 2 is a schematic flowchart of a scheduling method according to an embodiment of the present invention.
- the scheduling method is applied to a terminal and includes:
- Step 21 Obtain scheduling configuration information
- Step 22 Monitor the scheduling information of at least two scheduling objects to one scheduled object according to the scheduling configuration information.
- one scheduled object can be scheduled through at least two scheduling objects.
- one cell can only be scheduled by one scheduling cell, which improves scheduling flexibility.
- the scheduling configuration information may be obtained by at least one of the following methods: network side configuration, pre-configuration, and protocol agreement. For example, part of the scheduling configuration information is configured by the network side, and part of the scheduling configuration information is agreed upon by the protocol.
- the scheduling object may be a cell. That is, in some embodiments of the present invention, the terminal monitors the scheduling information of at least two scheduling cells to one scheduled cell, for example, monitors the scheduling information of cell1 and cell2 to cell1, cell2, or cell3.
- the primary cell in consideration of enhancing the coverage of the control channel, the primary cell (PCell) is generally deployed on a carrier in a low frequency band.
- the bandwidth of low-band carriers is insufficient, and a large number of them have been deployed to other series (such as LTE).
- the high frequency band carrier can be configured as a secondary cell (Secondary Cell, SCell) and the PCell can be scheduled through the SCell to solve the problem of limited PCell control channel capacity and reduce the control channel PDCCH overhead.
- SCell Secondary Cell
- the scheduled object is a PCell, and the scheduled object includes an SCell.
- PCell can be self-scheduled, or it can be cross-carrier scheduling through SCell.
- the scheduling object may also be a transmission and reception point (TRP), that is, the search space of the scheduling object is associated with a specific CORESET or CORESET pool.
- TRP transmission and reception point
- Multi-TRP transmission can increase the reliability and throughput performance of transmission.
- the terminal can receive from multiple TRPs. The same data or different data.
- the scheduling method in the embodiment of the present invention can be applied to the foregoing multi-TRP transmission scenario, that is, the terminal can monitor the scheduling information of at least two TRPs to one TRP. For example, monitoring the scheduling information of TRP1 and TRP2 to TRP1, TRP2, or TRP3.
- the terminal needs to monitor the scheduling information of at least two scheduling objects for one scheduled object, if only the relevant cross-carrier scheduling framework is simply applied, the terminal demodulation complexity will be greatly increased, for example, more buffers or larger ones are required. The demodulation capability is not conducive to the realization of the terminal.
- the monitoring the scheduling information of at least two scheduling objects for one scheduled object according to the scheduling configuration information includes: The search space monitoring quantity information and/or type information in the configuration information monitors the scheduled object and/or the search space on the scheduling object.
- the search space monitoring quantity information and/or type information includes at least one of the following:
- the terminal does not monitor the UE-specific search space on the PCell (the UE-specific search space may be referred to as S-P-USS hereinafter), thereby reducing terminal implementation complexity.
- This article includes restrictions on search space monitoring type information.
- the terminal if the terminal is configured to cross-carrier scheduling the PCell through the SCell, the terminal only monitors the S-P-USS not exceeding the first value on the PCell, thereby reducing the complexity of terminal implementation. For example, each bandwidth part (BWP) on the PCell only monitors one or two S-P-USS.
- BWP bandwidth part
- This article includes search space monitoring type information and monitoring quantity information restriction conditions.
- C-RNTI cell radio network temporary identification
- MCS-C-RNTI modulation and coding scheme C-RNTI
- CS-RNTI configuration scheduling RNTI
- This article includes restrictions on search space monitoring type information.
- the number of UE-specific search spaces (the UE-specific search spaces may be referred to as C-P-USS hereinafter) monitored on the scheduling object does not exceed a second value;
- the terminal monitors no more than the second number of C-P-USS on the SCell.
- This article includes search space monitoring type information and monitoring quantity information restriction conditions.
- the terminal For example, if the terminal is configured to schedule the PCell across the carrier through the SCell, the terminal only monitors the scheduling of the PCell on a specific C-P-USS of the SCell, and the number of all monitored C-P-USS does not exceed the third value.
- This article includes search space monitoring type information and monitoring quantity information restriction conditions.
- the terminal is configured to schedule the PCell across the carrier through the SCell, the sum of the C-P-USS on the SCell and the S-P-USS on the PCell monitored by the terminal does not exceed the fourth value.
- This article includes search space monitoring type information and monitoring quantity information restriction conditions.
- the terminal is configured to schedule the PCell across the carrier through the SCell, the sum of the C-P-USS on the SCell monitored by the terminal and the CSS on the PCell does not exceed the fifth value.
- This article is the restriction conditions for search space monitoring type information and monitoring quantity information.
- the terminal is configured to schedule the PCell across the carrier through the SCell, the sum of the C-P-USS on the SCell monitored by the terminal and the SS on the PCell does not exceed the sixth value.
- This article includes search space monitoring type information and monitoring quantity information restriction conditions.
- the foregoing monitoring quantity information and/or type information restriction conditions can reduce the number of search spaces that the terminal monitors at the same time while maintaining scheduling flexibility, and reduce the complexity of terminal implementation.
- the monitoring the scheduling information of at least two scheduling objects for one scheduled object according to the scheduling configuration information includes: according to the scheduling configuration information
- the search space monitoring sequence information in, monitors the scheduled object and/or the search space on the scheduled object.
- the search space monitoring sequence information includes one of the following:
- the terminal does not monitor any search space on the PCell and the C-P-USS on the SCell at the same time. Or, the terminal does not monitor the S-P-USS on the PCell and the C-P-USS on the SCell at the same time.
- the priority rule includes one of the following:
- the specific object is, for example, PCell.
- the foregoing search space monitoring sequence information restriction conditions can prevent the terminal from simultaneously processing scheduling instructions from two scheduling objects, thereby simplifying the implementation of the terminal.
- the monitoring the scheduling information of at least two scheduling objects to one scheduled object according to the scheduling configuration information includes: according to the unicast in the scheduling configuration information
- the scheduling quantity information and/or type information monitors the unicast scheduling of the scheduled object.
- the unicast scheduling quantity information and/or type information includes one of the following:
- the terminal monitors the unicast scheduling of one or two associated PCells at most.
- each object can only monitor at most one unicast schedule associated with the scheduled object;
- the terminal can only monitor the unicast scheduling of at most one associated PCell on each Cell (PCell and Scell).
- the terminal preferentially monitors the specific type of unicast scheduling associated with the PCell.
- the specific type of unicast scheduling includes: unicast scheduling of a specific DCI format, such as fallback DCI (DCI format 1_0 or 0_0, etc.), or scheduling DCI of multiple cells at the same time.
- a specific DCI format such as fallback DCI (DCI format 1_0 or 0_0, etc.)
- the above-mentioned quantity information and/or type information restriction conditions of unicast scheduling can prevent the terminal from processing scheduling instructions from two scheduling objects at the same time, ensuring that the terminal only needs to demodulate one unicast scheduling at a time, thereby simplifying the implementation of the terminal and reducing the function. Consumption.
- the specific time includes one of the following:
- the start time and/or length of the specific time interval is related to the parameters of at least two scheduling objects, for example, related to the numerology (numerical configuration) or SCS of the scheduling cell.
- the specific time interval may be, for example, the time interval between PDCCH listening opportunities of two scheduling objects.
- PDSCH Physical Downlink Shared Channel
- PUSCH Physical Uplink Shared Channel
- the scheduling configuration information further includes: for multiple transmissions of the same HARQ process or the same TB, only scheduling from the same object is allowed. This prevents the terminal's soft buffer from simultaneously processing scheduling instructions from two scheduling objects, which simplifies the terminal's buffer management.
- the scheduling configuration information further includes: if the ID of the first search space on the scheduled object is the same as the ID of the second search space on the scheduling object, but the first search space If the type of the search space is a public search space, it is considered that the first search space and the second search space have no association relationship.
- the terminal is configured to schedule the PCell through SCell cross-carrier, for the SS on the PCell and any SS on the SCell, if the SS ID is the same, but the type of the SS is CSS, it is considered that the PCell and the SCell have the same ID
- the SS has no association relationship, and the configuration field of the search space of the CSS is valid, that is, only the USS configured with the SCell is allowed to perform cross-carrier scheduling of the USS of the PCell, which can simplify the scheduling management of the terminal.
- the scheduling method further includes:
- terminal capabilities where the terminal capabilities include at least one of the following:
- the length of a specific time interval or monitoring timer is the length of a specific time interval or monitoring timer.
- the terminal when the number of C-P-USS reported by the terminal is 0, it means that the terminal does not support scheduling the scheduled object through the scheduling object.
- the Pcell is mainly scheduled by the PCell itself and the Scell at the same time as an example.
- the above scheduling method of the present invention is applicable to any scenario where one cell is scheduled by two (or more) cells (for example, one Scell is scheduled by two (or more) cells). Pcell and Scell are scheduled at the same time, or one Scell is scheduled at the same time by two Scells).
- the DCI for cross-carrier scheduling may be the DCI for scheduling one cell alone, or the DCI for scheduling multiple cells at the same time.
- a special DCI can schedule both Scell and Pcell data at the same time.
- an embodiment of the present invention also provides a scheduling method applied to a network side device, including:
- Step 81 Send scheduling configuration information, where the scheduling configuration information at least includes: the configuration terminal monitors scheduling information of at least two scheduling objects for one scheduled object.
- the scheduling configuration information further includes at least one of the following:
- Quantity information and/or type information of unicast scheduling are Quantity information and/or type information of unicast scheduling
- the scheduling method further includes:
- the terminal capabilities include at least one of the following:
- the length of a specific time interval or monitoring timer is the length of a specific time interval or monitoring timer.
- Embodiment 1 of the present invention is a diagrammatic representation of Embodiment 1 of the present invention.
- the network side device configures Pcell and Scell for the terminal, and configures the terminal to schedule the Pcell across carriers through the Scell.
- the terminal only monitors the CSS (Common Search Space) on the Pcell, and does not monitor the C-RNTI (Cell Radio Network Temporary Identity) in the CSS, and only monitors the C-RNTI scheduling on the cross-carrier scheduling Pcell on the Scell.
- CSS Common Search Space
- C-RNTI Cell Radio Network Temporary Identity
- the terminal only needs to monitor the broadcast or multicast of CSS on the Pcell, thereby reducing the buffer management of the terminal, reducing the cross-process interaction between the Pcell and the different cells of the Scell, and thereby reducing the implementation complexity of the terminal to the greatest extent. .
- the protocol stipulates the maximum number of C-P-USS and S-P-USS that the terminal needs to monitor, or the terminal's ability to report the maximum number of C-P-USS and S-P-USS that the terminal supports to monitor.
- the network side configures Pcell and Scell for the terminal, and Scell schedules Pcell across carriers through C-P-USS, and at the same time configures S-P-USS on Pcell for self-scheduling. And the number of C-P-USS and S-P-USS does not exceed the maximum number of C-P-USS and S-P-USS monitored by the terminal.
- the terminal only monitors the CSS on the Pcell, and can monitor the C-RNTI in the CSS and S-P-USS. In order to avoid that the terminal needs to monitor the self-scheduling of the Pcell and the cross-carrier scheduling of the Scell to the Pcell at the same time,
- the network side does not allow the configuration of C-P-USS and S-P-USS to overlap (or conflict);
- the terminal when CP-USS and SP-USS overlap (or conflict), the terminal only monitors the scheduling of one of the cells, for example, only monitors the self-scheduling of Pcell (because Pcell has better coverage performance, which can ensure scheduling reliability ), or only monitor the scheduling of the cell where the SS with the lowest ID in the overlapping SS is located (thereby the network side can flexibly choose which cell to preferentially schedule by configuring the SS ID).
- the HARQ process of Pcell self-scheduled Pcell is different from the HARQ process of Scell cross-carrier scheduling Pcell;
- scheduling can only be performed from one cell. For example, if the Pcell schedules the initial transmission of TB-1, the retransmission of the subsequent TB-1 can only continue to be self-scheduled from the Pcell.
- the implementation complexity of the terminal can be reduced to a certain extent.
- the network side configures the Pcell and Scell for the terminal, and the Scell schedules the Pcell through CP-USS across carriers, and at the same time configures the SP-USS on the Pcell for self-scheduling, in order to avoid the need for the terminal to monitor the self-scheduling and Scell of the Pcell at the same time
- Cross-carrier scheduling for Pcell
- the maximum number of unicast DCI that the terminal monitors on each scheduling cell can be specified.
- the terminal can monitor at most one Pcell self-scheduled DCI, and/or one Scell cross-carrier scheduling DCI of the Pcell;
- the terminal only needs to monitor one of the DCI of the Pcell self-scheduled DCI or the Scell cross-carrier scheduling Pcell at the following moments (that is, as long as the terminal detects a valid DCI for scheduling the Pcell from a cell, it will no longer detect the DCI of the scheduling Pcell ):
- a time window for example, in every X radio frames or subframes or time slots or OFDM symbols, specifically, if the SCS of Pcell and Scell are different, the length of the time window is different according to different SCS;
- processing time across different scheduling cells is reserved for the terminal.
- a PDCCH monitoring opportunity with the same earliest start position of the PDSCH/PUSCH that can be scheduled;
- the terminal only needs to monitor one effective scheduling DCI in the monitoring opportunities of slot M and slot Mk.
- a, b, and k are the length of the time domain, and the unit may be a subframe, a time slot, or an OFDM symbol, etc., which is not limited in the present invention.
- the network side configures Pcell and Scell for the terminal, and configures the DCI format 1_a on the Pcell, the PDSCH of Pcell and Scell can be scheduled at the same time, and the self-scheduled DCI format 1_1 is configured for scheduling Scell (can be self-scheduled or Cross-carrier scheduling).
- the terminal can support one cell (or TRP) to be scheduled by at least two scheduling cells (or TRP), while maintaining scheduling flexibility, reducing the number of SSs that the terminal monitors at the same time and the amount of detection
- the number of DCIs can prevent the terminal from processing scheduling instructions from two scheduling objects at the same time, ensuring that the terminal only needs to demodulate one unicast scheduling at a time, thereby simplifying terminal implementation and reducing power consumption.
- an embodiment of the present invention also provides a terminal 90, including:
- the obtaining module 91 is used to obtain scheduling configuration information
- the monitoring module 92 is configured to monitor the scheduling information of at least two scheduling objects for one scheduled object according to the scheduling configuration information.
- the monitoring module 92 is configured to monitor the scheduled object and/or the search space on the scheduling object according to the search space monitoring quantity information and/or type information in the scheduling configuration information.
- the search space monitoring quantity information and/or type information includes at least one of the following:
- the number of UE-specific search spaces monitored on the scheduled object does not exceed the first value
- the number of UE-specific search spaces monitored on the scheduling object does not exceed a second value
- the sum of the number of UE-specific search spaces monitored on the scheduled object and the number of UE-specific search spaces monitored on the scheduled object does not exceed a fourth value
- the sum of the number of public search spaces monitored on the scheduled object and the number of UE-specific search spaces monitored on the scheduled object does not exceed a fifth value
- the sum of the number of search spaces monitored on the scheduled object and the number of UE-specific search spaces monitored on the scheduled object does not exceed a sixth value.
- the monitoring module 92 is configured to monitor the scheduled object and/or the search space on the scheduling object according to the search space monitoring sequence information in the scheduling configuration information.
- the search space monitoring sequence information includes one of the following:
- the priority rule includes one of the following:
- the monitoring module 92 is configured to monitor the unicast scheduling of the scheduled object according to the quantity information and/or type information of the unicast scheduling in the scheduling configuration information.
- the unicast scheduling quantity information and/or type information includes one of the following:
- each object can monitor at most one unicast schedule associated with the scheduled object
- priority is given to monitoring the specific type of unicast scheduling associated with the scheduled object.
- the specific type of unicast scheduling includes: unicast scheduling of a specific DCI format.
- the specific time includes one of the following:
- PDCCH monitoring opportunities with the same earliest start position of PDSCH or PUSCH that can be scheduled
- the scheduling configuration information further includes: for multiple transmissions of the same HARQ process or the same TB, only scheduling from the same object is allowed.
- the scheduling configuration information further includes: if the ID of the first search space on the scheduled object is the same as the ID of the second search space on the scheduling object, but the type of the first search space is public Search space, it is considered that the first search space and the second search space have no association relationship.
- the terminal further includes:
- the reporting module is used to report terminal capabilities, and the terminal capabilities include at least one of the following:
- the length of a specific time interval or monitoring timer is the length of a specific time interval or monitoring timer.
- the scheduled object is PCell, and the scheduled object includes SCell.
- the terminal provided in the embodiment of the present invention can implement the various processes implemented by the terminal in the method embodiments of FIG. 2 to FIG. 7. To avoid repetition, details are not described herein again.
- an embodiment of the present invention also provides a network side device 100, including:
- the sending module 101 is configured to send scheduling configuration information, where the scheduling configuration information at least includes: the configuration terminal monitors scheduling information of at least two scheduling objects for one scheduled object.
- the scheduling configuration information further includes at least one of the following:
- Quantity information and/or type information of unicast scheduling are Quantity information and/or type information of unicast scheduling
- the sending module is further configured to send scheduling configuration information according to the terminal capabilities reported by the terminal;
- the terminal capabilities include at least one of the following:
- the length of a specific time interval or monitoring timer is the length of a specific time interval or monitoring timer.
- the terminal 110 includes but is not limited to: a radio frequency unit 111, a network module 112, an audio output unit 113, an input unit 114, a sensor 115, a display unit 116, User input unit 117, interface unit 118, memory 119, processor 1110, power supply 1111 and other components.
- a radio frequency unit 111 for implementing various embodiments of the present invention.
- the terminal 110 includes but is not limited to: a radio frequency unit 111, a network module 112, an audio output unit 113, an input unit 114, a sensor 115, a display unit 116, User input unit 117, interface unit 118, memory 119, processor 1110, power supply 1111 and other components.
- the terminal structure shown in FIG. 11 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components.
- the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer
- the processor 1110 is configured to obtain scheduling configuration information; according to the scheduling configuration information, monitor scheduling information of at least two scheduling objects for one scheduled object.
- the radio frequency unit 111 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the base station, it is sent to the processor 1110 for processing; Uplink data is sent to the base station.
- the radio frequency unit 111 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
- the radio frequency unit 111 can also communicate with the network and other devices through a wireless communication system.
- the terminal provides users with wireless broadband Internet access through the network module 112, such as helping users to send and receive emails, browse web pages, and access streaming media.
- the audio output unit 113 may convert the audio data received by the radio frequency unit 111 or the network module 112 or stored in the memory 119 into an audio signal and output it as sound. Moreover, the audio output unit 113 may also provide audio output related to a specific function performed by the terminal 110 (for example, call signal reception sound, message reception sound, etc.).
- the audio output unit 113 includes a speaker, a buzzer, a receiver, and the like.
- the input unit 114 is used to receive audio or video signals.
- the input unit 114 may include a graphics processing unit (GPU) 1141 and a microphone 1142, and the graphics processor 1141 is configured to monitor images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
- the processed image frame can be displayed on the display unit 116.
- the image frame processed by the graphics processor 1141 may be stored in the memory 119 (or other storage medium) or sent via the radio frequency unit 111 or the network module 112.
- the microphone 1142 can receive sound, and can process such sound into audio data.
- the processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 111 for output in the case of a telephone call mode.
- the terminal 110 also includes at least one sensor 115, such as a light sensor, a motion sensor, and other sensors.
- the light sensor includes an ambient light sensor and a proximity sensor.
- the ambient light sensor can adjust the brightness of the display panel 1161 according to the brightness of the ambient light.
- the proximity sensor can close the display panel 1161 and/or when the terminal 110 is moved to the ear. Or backlight.
- the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify terminal posture (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; sensor 115 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared Sensors, etc., will not be repeated here.
- the display unit 116 is used to display information input by the user or information provided to the user.
- the display unit 116 may include a display panel 1161, and the display panel 1161 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
- LCD liquid crystal display
- OLED organic light-emitting diode
- the user input unit 117 may be used to receive inputted number or character information, and generate key signal input related to user settings and function control of the terminal.
- the user input unit 117 includes a touch panel 1171 and other input devices 1172.
- the touch panel 1171 also called a touch screen, can collect user touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 1171 or near the touch panel 1171. operate).
- the touch panel 1171 may include two parts: a touch detection device and a touch controller.
- the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 1110, the command sent by the processor 1110 is received and executed.
- the touch panel 1171 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
- the user input unit 117 may also include other input devices 1172.
- other input devices 1172 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
- the touch panel 1171 can cover the display panel 1161.
- the touch panel 1171 detects a touch operation on or near it, it transmits it to the processor 1110 to determine the type of the touch event, and then the processor 1110 determines the type of the touch event according to the touch.
- the type of event provides corresponding visual output on the display panel 1161.
- the touch panel 1171 and the display panel 1161 are used as two independent components to implement the input and output functions of the terminal, but in some embodiments, the touch panel 1171 and the display panel 1161 can be integrated. Realize the input and output functions of the terminal, the specifics are not limited here.
- the interface unit 118 is an interface for connecting an external device with the terminal 110.
- the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
- the interface unit 118 may be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal 110 or may be used to communicate between the terminal 110 and the external device. Transfer data between.
- the memory 119 can be used to store software programs and various data.
- the memory 119 may mainly include a program storage area and a data storage area.
- the program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc.
- the memory 119 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
- the processor 1110 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal. Various functions of the terminal and processing data, so as to monitor the terminal as a whole.
- the processor 1110 may include one or more processing units; preferably, the processor 1110 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem The processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 1110.
- the terminal 110 may also include a power source 1111 (such as a battery) for supplying power to various components.
- a power source 1111 such as a battery
- the power source 1111 may be logically connected to the processor 1110 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. Function.
- the terminal 110 includes some functional modules not shown, which will not be repeated here.
- an embodiment of the present invention also provides a terminal 120, including a processor 121, a memory 122, a computer program stored on the memory 122 and running on the processor 121, and the computer program is
- the processor 121 implements each process of the foregoing scheduling method embodiment applied to a terminal during execution, and can achieve the same technical effect. To avoid repetition, details are not described herein again.
- an embodiment of the present invention also provides a network side device 130, including a processor 131, a memory 132, a computer program stored in the memory 132 and running on the processor 131, the computer
- a network side device 130 including a processor 131, a memory 132, a computer program stored in the memory 132 and running on the processor 131, the computer
- the program is executed by the processor 131, each process of the foregoing scheduling method embodiment applied to a network-side device is realized, and the same technical effect can be achieved. To avoid repetition, details are not described herein again.
- the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
- a computer program is stored on the computer-readable storage medium.
- the computer program is executed by a processor, each process of the foregoing scheduling method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, I won’t repeat it here.
- the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
- the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present invention.
- a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (39)
- 一种调度方法,应用于终端,包括:获取调度配置信息;根据所述调度配置信息,监听至少两个调度对象对一个被调度对象的调度信息。
- 如权利要求1所述的调度方法,其中,所述根据所述调度配置信息,监听至少两个调度对象对一个被调度对象的调度信息包括:根据所述调度配置信息中的搜索空间监听数量信息和/或类型信息,监听被调度对象和/或所述调度对象上的搜索空间。
- 如权利要求2所述的调度方法,其中,所述搜索空间监听数量信息和/或类型信息包括以下至少之一:不在所述被调度对象上监听UE特定搜索空间;在所述被调度对象上监听的UE特定搜索空间的个数不超过第一数值;在所述被调度对象的公共搜索空间上不监听单播调度;在所述调度对象上监听的UE特定搜索空间的个数不超过第二数值;只在所述调度对象上监听特定的UE特定搜索空间,且监听的UE特定搜索空间的个数不超过第三数值;在所述被调度对象上监听的UE特定搜索空间与在所述调度对象上监听的UE特定搜索空间的个数之和不超过第四数值;在所述被调度对象上监听的公共搜索空间与所述调度对象上监听的UE特定搜索空间的个数之和不超过第五数值;在所述被调度对象上监听的搜索空间与所述调度对象上监听的UE特定搜索空间的个数之和不超过第六数值。
- 如权利要求1所述的调度方法,其中,所述根据所述调度配置信息,监听至少两个调度对象对一个被调度对象的调度信息包括:根据所述调度配置信息中的搜索空间监听顺序信息,监听被调度对象和/或所述调度对象上的搜索空间。
- 如权利要求4所述的调度方法,其中,所述搜索空间监听顺序信息包 括以下之一:在特定时间内,不同时监听所述被调度对象上的搜索空间与所述调度对象上的搜索空间;在特定时间内,根据优先级规则监听所述被调度对象和所述调度对象上所有调度所述被调度对象的搜索空间。
- 如权利要求5所述的调度方法,其中,所述优先级规则包括以下之一:优先监听公共搜索空间;优先监听特定对象上的搜索空间;优先监听最低或最高ID的搜索空间;优先监听关联特定DCI格式的搜索空间;根据ID顺序监听搜索空间。
- 如权利要求1所述的调度方法,其中,所述根据所述调度配置信息,监听至少两个调度对象对一个被调度对象的调度信息包括:根据所述调度配置信息中的单播调度的数量信息和/或类型信息,监听被调度对象的单播调度。
- 如权利要求7所述的调度方法,其中,所述单播调度数量信息和/或类型信息包括以下之一:在特定时间内,最多监听一个或两个关联所述被调度对象的单播调度;在特定时间内,每个对象上最多只监听一个关联所述被调度对象的单播调度;在特定时间内,优先监听关联所述被调度对象的特定类型的单播调度。
- 如权利要求8所述的调度方法,其中,所述特定类型的单播调度包括:特定DCI格式的单播调度。
- 如权利要求5或8所述的调度方法,其中,所述特定时间包括以下之一:同一时刻;同一个时隙内;特定时间间隔内;调度的PDSCH或PUSCH的最早起始位置相同的PDCCH监听机会;监听定时器生效时间内。
- 如权利要求1所述的调度方法,其中,所述调度配置信息还包括:对于同一个HARQ进程或同一个TB的多次传输,只允许从相同的所述调度对象上调度。
- 如权利要求1所述的调度方法,其中,所述调度配置信息还包括:若所述被调度对象上的第一搜索空间与所述调度对象上的第二搜索空间的ID相同,但所述第一搜索空间的类型为公共搜索空间,则认为所述第一搜索空间和所述第二搜索空间没有关联关系。
- 如权利要求3或8所述的调度方法,其中,还包括:上报终端能力,所述终端能力包括以下至少之一:所述终端支持的搜索空间监听数量;所述终端支持的单播调度的数量;所述终端是否支持通过所述调度对象调度所述被调度对象;每个对象关联的HARQ进程数量;调度的PDSCH或PUSCH的最早起始位置;特定时间间隔或监听定时器的长度。
- 如权利要求1所述的调度方法,其中,所述被调度对象为PCell,所述调度对象包括SCell。
- 一种调度方法,应用于网络侧设备,包括:发送调度配置信息,所述调度配置信息至少包括:配置终端监听至少两个调度对象对一个被调度对象的调度信息。
- 如权利要求15所述的调度方法,其中,所述调度配置信息还包括以下至少之一:搜索空间监听数量信息和/或类型信息;搜索空间监听顺序信息;单播调度的数量信息和/或类型信息;调度的DCI格式。
- 如权利要求15或16所述的调度方法,其中,还包括:根据终端上报的终端能力,发送调度配置信息;所述终端能力包括以下至少之一:所述终端支持的搜索空间监听数量;所述终端支持的单播调度的数量;所述终端是否支持通过所述调度对象调度所述被调度对象;每个对象关联的HARQ进程数量;调度的PDSCH或PUSCH的最早起始位置;特定时间间隔或监听定时器的长度。
- 一种终端,包括:获取模块,用于获取调度配置信息;监听模块,用于根据所述调度配置信息,监听至少两个调度对象对一个被调度对象的调度信息。
- 如权利要求18所述的终端,其中,所述监听模块用于根据所述调度配置信息中的搜索空间监听数量信息和/或类型信息,监听被调度对象和/或所述调度对象上的搜索空间。
- 如权利要求19所述的终端,其中,所述搜索空间监听数量信息和/或类型信息包括以下至少之一:不在所述被调度对象上监听UE特定搜索空间;在所述被调度对象上监听的UE特定搜索空间的个数不超过第一数值;在所述被调度对象的公共搜索空间上不监听单播调度;在所述调度对象上监听的UE特定搜索空间的个数不超过第二数值;只在所述调度对象上监听特定的UE特定搜索空间,且监听的UE特定搜索空间的个数不超过第三数值;在所述被调度对象上监听的UE特定搜索空间与在所述调度对象上监听的UE特定搜索空间的个数之和不超过第四数值;在所述被调度对象上监听的公共搜索空间与所述调度对象上监听的UE特定搜索空间的个数之和不超过第五数值;在所述被调度对象上监听的搜索空间与所述调度对象上监听的UE特定搜索空间的个数之和不超过第六数值。
- 如权利要求18所述的终端,其中,所述监听模块用于根据所述调度 配置信息中的搜索空间监听顺序信息,监听被调度对象和/或所述调度对象上的搜索空间。
- 如权利要求21所述的终端,其中,所述搜索空间监听顺序信息包括以下之一:在特定时间内,不同时监听所述被调度对象上的搜索空间与所述调度对象上的搜索空间;在特定时间内,根据优先级规则监听所述被调度对象和所述调度对象上所有调度所述被调度对象的搜索空间。
- 如权利要求22所述的终端,其中,所述优先级规则包括以下之一:优先监听公共搜索空间;优先监听特定对象上的搜索空间;优先监听最低或最高ID的搜索空间;优先监听关联特定DCI格式的搜索空间;根据ID顺序监听搜索空间。
- 如权利要求18所述的终端,其中,所述监听模块用于根据所述调度配置信息中的单播调度的数量信息和/或类型信息,监听被调度对象的单播调度。
- 如权利要求24所述的终端,其中,所述单播调度数量信息和/或类型信息包括以下之一:在特定时间内,最多监听一个或两个关联所述被调度对象的单播调度;在特定时间内,每个对象上最多只监听一个关联所述被调度对象的单播调度;在特定时间内,优先监听关联所述被调度对象的特定类型的单播调度。
- 如权利要求25所述的终端,其中,所述特定类型的单播调度包括:特定DCI格式的单播调度。
- 如权利要求22或25所述的终端,其中,所述特定时间包括以下之一:同一时刻;同一个时隙内;特定时间间隔内;调度的PDSCH或PUSCH的最早起始位置相同的PDCCH监听机会;监听定时器生效时间内。
- 如权利要求18所述的终端,其中,所述调度配置信息还包括:对于同一个HARQ进程或同一个TB的多次传输,只允许从相同的所述调度对象上调度。
- 如权利要求18所述的终端,其中,所述调度配置信息还包括:若所述被调度对象上的第一搜索空间与所述调度对象上的第二搜索空间的ID相同,但所述第一搜索空间的类型为公共搜索空间,则认为所述第一搜索空间和所述第二搜索空间没有关联关系。
- 如权利要求20或25所述的终端,其中,还包括:上报模块,用于上报终端能力,所述终端能力包括以下至少之一:所述终端支持的搜索空间监听数量;所述终端支持的单播调度的数量;所述终端是否支持通过所述调度对象调度所述被调度对象;每个对象关联的HARQ进程数量;调度的PDSCH或PUSCH的最早起始位置;特定时间间隔或监听定时器的长度。
- 如权利要求18所述的终端,其中,所述被调度对象为PCell,所述调度对象包括SCell。
- 一种网络侧设备,包括:发送模块,用于发送调度配置信息,所述调度配置信息至少包括:配置终端监听至少两个调度对象对一个被调度对象的调度信息。
- 如权利要求32所述的网络侧设备,其中,所述调度配置信息还包括以下至少之一:搜索空间监听数量信息和/或类型信息;搜索空间监听顺序信息;单播调度的数量信息和/或类型信息;调度的DCI格式。
- 如权利要求32或33所述的网络侧设备,其中,所述发送模块还用于根据终端上报的终端能力,发送调度配置信息;所述终端能力包括以下至少之一:所述终端支持的搜索空间监听数量;所述终端支持的单播调度的数量;所述终端是否支持通过所述调度对象调度所述被调度对象;每个对象关联的HARQ进程数量;调度的PDSCH或PUSCH的最早起始位置;特定时间间隔或监听定时器的长度。
- 一种终端,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所述处理器执行时实现如权利要求1至14中任一项所述的调度方法的步骤。
- 一种网络侧设备,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所述处理器执行时实现如权利要求15至17中任一项所述的调度方法的步骤。
- 一种计算机可读存储介质,所述计算机可读存储介质上存储计算机程序,所述计算机程序被处理器执行时实现如权利要求1至14中任一项所述的调度方法的步骤;或者,所述计算机程序被处理器执行时实现如权利要求15至17中任一项所述的调度方法的步骤。
- 一种计算机程序产品,所述程序产品被至少一个处理器执行时实现如权利要求1至14中任一项所述的调度方法的步骤;或者,实现如权利要求15至17中任一项所述的调度方法的步骤。
- 一种通信设备,所述通信设备被配置为用于执行如权利要求1至14中任一项所述的调度方法的步骤;或者,执行如权利要求15至17中任一项所述的调度方法的步骤。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/881,868 US20220377779A1 (en) | 2020-02-06 | 2022-08-05 | Scheduling method, terminal, and network side device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010081515.4 | 2020-02-06 | ||
CN202010081515.4A CN113225817B (zh) | 2020-02-06 | 2020-02-06 | 调度方法、终端及网络侧设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/881,868 Continuation US20220377779A1 (en) | 2020-02-06 | 2022-08-05 | Scheduling method, terminal, and network side device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021155796A1 true WO2021155796A1 (zh) | 2021-08-12 |
Family
ID=77085589
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/075002 WO2021155796A1 (zh) | 2020-02-06 | 2021-02-03 | 调度方法、终端及网络侧设备 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20220377779A1 (zh) |
CN (1) | CN113225817B (zh) |
WO (1) | WO2021155796A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11751193B2 (en) * | 2021-01-14 | 2023-09-05 | Qualcomm Incorporated | Scheduling order for a scheduled cell having downlink control information from multiple scheduling cells |
WO2023206306A1 (zh) * | 2022-04-28 | 2023-11-02 | 富士通株式会社 | 数据接收方法、数据发送方法以及装置 |
CN115398833A (zh) * | 2022-07-27 | 2022-11-25 | 北京小米移动软件有限公司 | 信息监听、信息发送方法及装置、存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150305000A1 (en) * | 2013-09-16 | 2015-10-22 | Nec Corporation | Methods and apparatus relating to lte fdd-tdd inter-system carrier aggregation in advanced wireless communication systems |
CN105682243A (zh) * | 2016-03-25 | 2016-06-15 | 宇龙计算机通信科技(深圳)有限公司 | 一种调度信令的配置方法、接收方法和相关设备 |
US20170331597A1 (en) * | 2012-02-14 | 2017-11-16 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting uplink and downlink data in tdd system |
US20180152954A1 (en) * | 2015-08-07 | 2018-05-31 | Alexander Golitschek Edler Von Elbwart | Self- and cross- carrier scheduling |
CN110475356A (zh) * | 2018-05-11 | 2019-11-19 | 维沃移动通信有限公司 | 确定下行控制信息的方法和设备 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016119882A1 (en) * | 2015-01-30 | 2016-08-04 | Nokia Solutions And Networks Oy | Carrier aggregation with cross-carrier scheduling |
CN110662228B (zh) * | 2018-06-29 | 2021-02-12 | 维沃移动通信有限公司 | 跨载波调度的pdcch候选分配方法、设备和存储介质 |
CN111132344B (zh) * | 2019-12-27 | 2023-01-17 | 北京紫光展锐通信技术有限公司 | 跨载波调度方法、装置及存储介质 |
-
2020
- 2020-02-06 CN CN202010081515.4A patent/CN113225817B/zh active Active
-
2021
- 2021-02-03 WO PCT/CN2021/075002 patent/WO2021155796A1/zh active Application Filing
-
2022
- 2022-08-05 US US17/881,868 patent/US20220377779A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170331597A1 (en) * | 2012-02-14 | 2017-11-16 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting uplink and downlink data in tdd system |
US20150305000A1 (en) * | 2013-09-16 | 2015-10-22 | Nec Corporation | Methods and apparatus relating to lte fdd-tdd inter-system carrier aggregation in advanced wireless communication systems |
US20180152954A1 (en) * | 2015-08-07 | 2018-05-31 | Alexander Golitschek Edler Von Elbwart | Self- and cross- carrier scheduling |
CN105682243A (zh) * | 2016-03-25 | 2016-06-15 | 宇龙计算机通信科技(深圳)有限公司 | 一种调度信令的配置方法、接收方法和相关设备 |
CN110475356A (zh) * | 2018-05-11 | 2019-11-19 | 维沃移动通信有限公司 | 确定下行控制信息的方法和设备 |
Non-Patent Citations (5)
Title |
---|
SAMSUNG: "Cross-carrier scheduling of PUSCH for TDD CA", 3GPP DRAFT; R1-120160 PUSCH CROSS CARRIER SCHEDULING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Dresden, Germany; 20120206 - 20120210, 31 January 2012 (2012-01-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050562730 * |
SAMSUNG: "Pcell vs. Scell based timing in case of PDSCH cross-carrier scheduling", 3GPP DRAFT; R1-122224 PCELL VS SCELLL_R2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, Czech Republic; 20120521 - 20120525, 12 May 2012 (2012-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050600488 * |
VIVO: "Discussion on Scell scheduling P(S)cell", 3GPP DRAFT; R1-2005409, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051917434 * |
ZTE CORPORATION: "Remaining issues on cross-carrier scheduling", 3GPP DRAFT; R1-1911974, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20191118 - 20191122, 9 November 2019 (2019-11-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051823155 * |
ZTE: "Discussion on Cross-Carrier Scheduling from SCell to PCell", 3GPP DRAFT; R1-2005440, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051917465 * |
Also Published As
Publication number | Publication date |
---|---|
CN113225817B (zh) | 2023-04-07 |
US20220377779A1 (en) | 2022-11-24 |
CN113225817A (zh) | 2021-08-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020216293A1 (zh) | 信道监听方法、终端及网络设备 | |
US20220141866A1 (en) | Resource configuration method, information transmission method, and related device | |
WO2020011180A1 (zh) | 信道检测指示方法、终端及网络设备 | |
WO2021155796A1 (zh) | 调度方法、终端及网络侧设备 | |
WO2019128578A1 (zh) | 控制信道监听方法、监听指示方法、终端及网络设备 | |
WO2021218742A1 (zh) | 信息反馈、资源调度方法、终端及网络设备 | |
US20210227531A1 (en) | Uplink information sending method and terminal | |
WO2020011181A1 (zh) | 信道检测指示方法、终端及网络设备 | |
WO2020147817A1 (zh) | 随机接入过程的信息传输方法及终端 | |
US20220014343A1 (en) | Indication method, terminal device, and network-side device | |
WO2021129507A1 (zh) | 唤醒信号配置方法、唤醒信号处理方法及相关设备 | |
US20220141824A1 (en) | Carrier aggregation parameter configuration method, device, and system | |
WO2021197202A1 (zh) | Harq-ack反馈的触发方法、反馈方法及设备 | |
WO2021147761A1 (zh) | 上行传输处理方法及装置、终端 | |
WO2021052420A1 (zh) | 信道监听控制方法和终端 | |
WO2021027475A1 (zh) | 信息传输方法及终端 | |
WO2021063281A1 (zh) | 旁链路资源的确定方法及终端 | |
WO2021147778A1 (zh) | 承载建立方法、配置方法、终端及网络侧设备 | |
WO2021155787A1 (zh) | Bwp切换方法、终端和网络侧设备 | |
WO2021129508A1 (zh) | 唤醒信号处理方法、唤醒信号配置方法及相关设备 | |
WO2021115361A1 (zh) | 发送方法、接收方法、网络设备及终端 | |
WO2021057779A1 (zh) | 混合自动重传请求应答反馈的获取、发送、终端及网络侧设备 | |
WO2020119243A1 (zh) | 物理上行控制信道传输方法、网络侧设备和终端 | |
WO2021068876A1 (zh) | 信息传输、接收方法、终端及网络侧设备 | |
WO2021147794A1 (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: 21750681 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: 21750681 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20/02/2023) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21750681 Country of ref document: EP Kind code of ref document: A1 |